Dnia Mon, Oct 13, 2003 at 02:51:43PM -0700, Lee Damon napisal:
Anyone tried going forward to 1.8?
I just tried 1.8, it did not fix the problem. Symtoms are still the same,
I use 1.8 and is working without problem.
--
Jacek Serwatynski [EMAIL PROTECTED] | PGP_key: www.trynet.eu.org/pub.key
Anyone tried going forward to 1.8?
I just tried 1.8, it did not fix the problem. Symtoms are still the same,
I noticed that ata-queue.c had a .rej so in a fit of lets make sure
everything is validness I deleted my /usr/src tree and re-sup'd the
entire thing, then built.
Between that and
From: Steve Ames [EMAIL PROTECTED]
Anyone tried going forward to 1.8?
Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to
confirm that that's the last working version for me too.
Please DO NOT send me ANY email directly unless it's a privacy issue.
Reply-to
From: Rob MacGregor [EMAIL PROTECTED]
Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to
confirm that that's the last working version for me too.
Backing out to 1.6 fixes the problem for me too...
Please DO NOT send me ANY email directly unless it's a privacy issue.
Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.
reverting to version 1.6) makes the problem go away.
I upgraded from an Oct 1 - Oct 12 kernel and saw the same hang.
Backing out r1.6 fixed it for me too.
Anyone tried going forward to 1.8?
I just tried 1.8, it
Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.
reverting to version 1.6) makes the problem go away.
I upgraded from an Oct 1 - Oct 12 kernel and saw the same hang.
Backing out r1.6 fixed it for me too.
me too
Anyone tried going forward to 1.8?
