On Maw, 2006-05-09 at 21:48 -0400, Kevin Radloff wrote:
> ata3: PATA max PIO0 cmd 0x3100 ctl 0x310E bmdma 0x0 irq 11
> setup_irq: irq handler mismatch
Ok so we got an interrupt this time and then when we asked for it got
told "no". That still shouldn't crash but there are some lurking
problems when ata_device_add fails.
More interesting is how it can occur.
We asked for an IRQ that was "exclusive". We got given IRQ 11 which was
shared. A look at the pcmcia code suggests the new drivers/pcmcia code
is broken here: It may fall back to using an interrupt line that is
shared even when told not to.
What occurs if you change
ae.irq_flags = 0;
to
ae.irq_flags = SA_SHIRQ ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
