Re: MSI broken in libata?

From: Robert Hancock
Date: Mon Jan 18 2010 - 21:04:18 EST

On 01/18/2010 02:51 PM, Torsten Kaiser wrote:
On Sun, Jan 17, 2010 at 10:11 PM, Torsten Kaiser
<just.for.lkml@xxxxxxxxxxxxxx> wrote:
What was different between -rc4 and my earlier tests was, that there
where additional error messages from do_IRQ.

[ 112.382903] do_IRQ: 0.165 No irq handler for vector (irq -1)
[ 112.382923] do_IRQ: 3.165 No irq handler for vector (irq -1)
[ 112.382939] do_IRQ: 1.165 No irq handler for vector (irq -1)
[ 112.382957] do_IRQ: 2.165 No irq handler for vector (irq -1)
[ 143.010051] ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
[ 143.010060] ata2.00: failed command: READ FPDMA QUEUED
[ 143.010071] ata2.00: cmd 60/00:00:ad:71:d9/01:00:01:00:00/40 tag 0
ncq 131072 in
[ 143.010073] res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask
0x4 (timeout)
[ 143.010079] ata2.00: status: { DRDY }
[ 143.010083] ata2.00: failed command: READ FPDMA QUEUED
[ 143.010092] ata2.00: cmd 60/00:08:ad:70:d9/01:00:01:00:00/40 tag 1
ncq 131072 in
[ 143.010095] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[ 143.010099] ata2.00: status: { DRDY }
[ 143.010108] ata2: hard resetting link

I will look, if I can find out, where the do_IRQ error comes from and
why I didn't see it with -rc1 to -rc3.

OK, this has nothing to do with -rc3 vs. -rc4.
If I kill the drive with reading a 1GB file with dd, I get the above
errors, include the one from do_IRQ.
If I kill the drive with writing a 1GB file with dd, I do not get the
do_IRQ error.
As I tested the earlier -rcs only with writes, I didn't see it there.
(Its not even in the old logs that contain the libata errors)

Should I try to put some printks in arch/x86/kernel/apic/io_apic.c
__assign_irq_vector() or is there a better way to look at the irq

Might not be a bad idea. Something definitely seems to be banging on vector 165. Any references to 165 in dmesg prior to that? I wonder where that is coming from..
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at