[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4693CE7A.5070502@rtr.ca>
Date: Tue, 10 Jul 2007 14:22:50 -0400
From: Mark Lord <lkml@....ca>
To: Bruce Allen <ballen@...vity.phys.uwm.edu>, Mark Lord <liml@....ca>,
David Greaves <david@...eaves.com>,
Douglas Gilbert <dougg@...que.net>,
Tejun Heo <htejun@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Kai Makisara <Kai.Makisara@...umbus.fi>,
Jeff Garzik <jeff@...zik.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Klaus Fuerstberger <kfuerstberger@...or.de>,
Jan Dvorak <fermentol@...il.com>,
Smartmontools Mailing List
<smartmontools-support@...ts.sourceforge.net>,
Bruce Allen <bruce.allen@....mpg.de>
Subject: Re: [smartmontools-support] SMART problems in 2.6.22
Adam Spiers wrote:
> On Sun, Jul 08, 2007 at 08:14:10PM -0500, Bruce Allen wrote:
>> On Sun, 8 Jul 2007, Bruce Allen wrote:
>>..
>> http://article.gmane.org/gmane.linux.utilities.smartmontools/4704/match=diamondmax
>>
>> Again, this indicates that SMART is enabled. But it's not clear what the
>> kernel version here is. The report indicates that the problem started
>> with an FC7 kernel upgrade
So it's a bug in the sata_nv.c port driver.
In particular, I see this in the bug report:
>Jun 30 10:23:42 atlantic kernel: ata1: EH in ADMA mode, notifier 0x1 notifier_error 0x0 gen_ctl 0x1501000 status 0x1540 next cpb count 0x0 next cpb idx 0x0
That looks a bit strange, because the driver goes to some effort
to prevent these kind of commands from ever being issued "in ADMA mode",
precisely because there's no way to do a tf_read in that mode.
Mmm.. buggy somewhere in there.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists