Charles Sprickman wrote:
On Tue, 6 Jul 2004, Ken Smith wrote:
On Tue, Jul 06, 2004 at 06:35:27PM -0700, Doug White wrote:
There was a nasty bug just about as 4.10 went out the door with the twe
driver. I thought the fix went into the release, though. If you get a
chance you might try moving up to the -stable version of src/sys/dev/twe
and see if that fixes your issues in 4.10.
It was actually the first thing we did as an Errata Notice. If you
normally track the Security Fix branches you can use the same mechanism
(cvsup to RELENG_4_10 in this case) to get the twe fix. See:
ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-04:01.twe.asc
Excellent, next time I'm onsite I'll give it a try (the box is remote, and
last time it locked up hard).
Thanks,
Charles
for the Errata Notice.
The original patch (early May) didn't fix it for us...
However, I have just updated and checked the sources again, and there
were further changes after the patch that I applied.
We still have two machines that exhibit this behaviour from time to
time - I'll update them and see if that fixes it. If it doesn't, I
will be able to get crashdumps. (We've also got SCSI disks in the
machines in question).
Thanks for the additional info.
BTW on one occasion, we fixed the *symptoms* of our problem by
repairing a disk that had bad sectors. (This didn't show up in error
messages from the twe driver - only when we scanned the disk using
Maxtor's PowerMax tools. After remapping the sector and rebuilding the
array - the problem disappeared).
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
