Marvell MV88SX6081 on FreeBSD 8.0-RELEASE

[Stephane LAPIE]

Dieter wrote:
> In message <4B13159D.9010504 at darkbsd.org>, Stephane LAPIE writes:
> 
>> On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O
>> bursts (confirmed with zpool iostat), before totally freezing down and
>> locking the ZFS pool (the system is still up and only ZFS based file
>> systems are unusable in this state), probably to avoid data corruption.
>> Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)"
>> error message showing up, on a random hard disk.
> 
> And there are these, which you didn't mention:
>> ad1: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
>> ad12: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
> (No, I don't know what that means, sorry.)

Ah, actually I do have an idea as to what these are about : These two
disks are SSDs I'm using in my ZFS pool as cache devices. So I guess
this is the kind of error that says "I tried to use an access mode this
device was not designed for". In the same fashion, I also get such error
messages when trying SMART checks on ad0, which is a flash card.

ad0: FAILURE - SMART status=51<READY,DSC,ERROR> error=4<ABORTED>

So, I think these could safely be discarded under "not a normal disk
device". (Unless I'm completely mistaken about this...)

>> ad18: 1430799MB <Seagate ST31500341AS CC1H> at ata9-master SATA300
>> ad20: 1430799MB <Seagate ST31500341AS SD1A> at ata10-master SATA300
> 
> How old is the SD1A disk?  As you may know, Seagate had various troubles
> with the .11 firmware.  I have some of the ST31500341AS CC1H and mine are
> new enough that they are supposed to be ok.

I bought all these disks at roughly the same time around April, but
strangely got an odd one in the lot and didn't bother to change it.

From what I checked with the Seagate page about the firmware issues,
SD1A is not affected. I also have three spare disks in a drawer in case
a problem occurs.

>> Therefore, I am inclined to think the motherboard/memory (a "TYAN
>> Thunder K8WE S2895") would be at fault here,
> 
> I have been told that Tyan does a good job with memory, although even
> assuming that's true it could still be a memory problem.  My Tyan
> board has a memory scrubbing feature that can be turned on in
> firmware, but I've never tried it.  Also, you could try rotating the
> SIMMs and see if anything changes.

The memory is brand new, from Corsair. I tried swapping the sticks
(while still using the same slots) and strangely enough, some
combinations just... don't boot at all.

Also, completely unrelated to the SATA controller, some quirks on this
motherboard (though at BIOS level) have been annoying me quite a lot :
- Booting FreeBSD from anything besides an IDE device has a 80% chance
of freezing the computer at BTX level.
- Sometimes the Option ROMs (this including the VGA card) are not loaded
properly because of an "out of memory" problem at BIOS level.

However, once the system is booted, it can go on for several months.
(Though, I have witnessed one "Fatal error 12: Page fault"-type kernel
panic in six months)

Thanks again for your time.
-- 
Stephane LAPIE, EPITA SRS, Promo 2005
"Even when they have digital readouts, I can't understand them."
--MegaTokyo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20091130/d36548af/signature.pgp