Robert Hancock wrote:
On 06/16/2010 05:30 AM, Erik Rull wrote:
I need some ideas where to continue my search - I think that it is
somewhere in the libata that blocks this interrupt. /proc/interrupts
shows up no interrupt neither that #15 is used.
If no driver attaches to the device and nothing is reported in
/proc/interrupts then nothing should be blocking the interrupt
driver-wise. I suspect the problem might be elsewhere, like the IRQ
routing or something..
Hm interesting. Is there a way to debug/see the IRQ routing somehow or
somewhere? I've found another possiblity of watching incoming interrupts
via /proc/stats but there is also nothing happening (The number that
belongs to IRQ15 remains on 0).
Best regards,
Erik
--
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
