Hello,
did anyone have the opportunity to test operation with a MV88SX6081 SATA
controller on FreeBSD 8.0 ? My amd64 dual-Opteron (using 4G ECC RAM)
system just works fine with it on FreeBSD 7.2, but can't handle any
high-speed disk I/O when booting with a FreeBSD 8.0 kernel.
I have two controlle
In message <4b13159d.9010...@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 unus
Dieter wrote:
> In message <4b13159d.9010...@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 fi
In message <4b1392cf.5090...@darkbsd.org>, Stephane LAPIE writes:
> >> Therefore, I am inclined to think the motherboard/memory (a "TYAN
> >> Thunder K8WE S2895") would be at fault here,
> >=20
> > I have been told that Tyan does a good job with memory, although even
> > assuming that's true it co
Dieter wrote:
> That sounds like a major clue that you probably have a very bad stick
> of memory (probably a hard error). I would try booting with just 1 stick
> at a time (or whatever the minimum is for your board) and isolate the bad
> stick.
>
> Most likely with 7.2 something landed on the ba
Stephane LAPIE wrote:
> Dieter wrote:
>> In message <4b13159d.9010...@darkbsd.org>, Stephane LAPIE writes:
>> And there are these, which you didn't mention:
>>> ad1: FAILURE - SET_MULTI status=3D51 error=3D4
>>> ad12: FAILURE - SET_MULTI status=3D51 error=3D4
>> (No, I don't know what that means, s
