Berck E. Nash wrote:
Greetings,
I get a few million of these on boot-- the system never actually boots.
Works fine in 2.6.23-rc7.
[ 50.456012] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 50.462484] ata2.00: irq_stat 0x40000001
[ 50.466441] ata2.00: cmd e5/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 0x0 data 0
[ 50.466442] res 51/04:00:01:01:80/00:00:00:00:00/a0 Emask
0x1 (device error)
[ 50.481914] ata2.00: status: {DRDY ERR }
[ 50.485876] ata2.00: error: {ABRT }
[ 50.489533] ata2.00: configured for UDMA/133
[ 50.493839] ata2: EH complete
I've attached the entire dmesg and lspci.
Are you "git-friendly"? A few quick kernel compiles and reboots would
help us narrow down the problem, given that it's a reproducible regression.
The first step would be to clone the "upstream" branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
and see if the problem is reproducible there. If yes, then you have
narrowed down the problem to something my ATA devel tree has introduced
into -mm.
Once the blame has been squared fixed upon me :) you can use git-bisect
to locate the precise change that broke your setup.
Info at http://kerneltrap.org/node/11753 or
http://www.kernel.org/pub/software/scm/git/docs/v1.3.3/howto/isolate-bugs-with-bisect.txt
or "man git-bisect"
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
