Messages in this thread | | | Date | Thu, 18 May 2006 12:10:15 +0100 | From | Russell King <> | Subject | Re: pcmcia oops on 2.6.17-rc[12] |
| |
On Mon, May 15, 2006 at 11:00:44PM +0100, Russell King wrote: > On Mon, May 15, 2006 at 11:07:08PM +0100, Alan Cox wrote: > > On Llu, 2006-05-08 at 17:34 +0100, Russell King wrote: > > > > So 8250 is requesting an IRQ for non-sharing mode and it's actually > > > > failing, because something else is already using that IRQ. The difference > > > > is that the kernel now generates a warning when this happens. > > > > > > Maybe someone is clearing the UPF_SHARE_IRQ flag? Which port is this? > > > > Its a bug in the PCMCIA code. Its the one I hit with the IDE code. > > Asking for a private IRQ is not always honoured. > > Not in this case - the call trace is definitely a result of setserial > being used. serial_cs _always_ registers ports with 8250 with the > share IRQ flag set.
Given that no one has responded to my comments on this, I take it that this is a case of user error or distro scripting error.
setserial should never be used to clear the shared IRQ flag bit unless there's a very good reason (eg, the admin knows that the IRQ should not be shared.)
-- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |