Re: do_IRQ: 0.165 No irq handler for vector (irq -1)

[Eric W. Biederman]

Tejun Heo <tj@xxxxxxxxxx> writes:

> Hello, Torsten.
>
> On 01/31/2010 10:02 PM, Torsten Kaiser wrote:
>> I'm still trying to get the MSI support for sata_sil24, that was added
>> in 2.6.33-rc1, to work. But even with -rc6 it still shows the same
>> errors.
>> 
>> The current best guess is, that there is something fishy going on in
>> the IRQ system, as the only error messages before the libata timeouts
>> start are:
>> 
>> [   86.463814] do_IRQ: 0.165 No irq handler for vector (irq -1)
>> [   86.463832] do_IRQ: 3.165 No irq handler for vector (irq -1)
>> [   86.463848] do_IRQ: 1.165 No irq handler for vector (irq -1)
>> [   86.463867] do_IRQ: 2.165 No irq handler for vector (irq -1)
>> 
>> (Thats why I added CCs for get_maintainer.pl -f arch/x86/kernel/apic/io_apic.c)

Fascinating I think get_maintainer.pl missed the maintainers.

>> To get these errors I only boot with sata_sil24.msi=1 and then do: dd
>> if=1GB-file-on-ro-mounted-xfs-fs of=/dev/null bs=1k
>> 
>> Writing with enabled MSI also fails with timeouts, but in this case
>> there is no error from do_IRQ.
>
> It might be that the silicon implements MSI incorrectly and ends up
> sending out invalid MSI packets under certain circumstances.  The
> silicon hasn't changed for quite some time now and back when it came
> out MSI wasn't too popular and I don't think SIMG's proprietary
> drivers use it, so it's quite possible that the feature simply is
> broken.  Is there any specific reason why you want to enable MSI
> support?  It's not like MSI brings any actual benefit when the
> compatibility hardware is already there.

It also seems possible that some of the recent irq handling changes
missed something.

Usually the message "No irq handler for vector (irq -1)" means that the irq
was delivered to a cpu that was not ready for it.  I see that vector 165
is being delivered on all of the different cpus with vector 165,
and that you are getting interrupts delivered most of the time.

This smells like the initialization problems I was seeing in another
thread.  Suresh?

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/