Messages in this thread | | | From | Alistair John Strachan <> | Subject | Re: Assuming someone else called the IRQ | Date | Sat, 26 Jun 2004 18:39:39 +0100 |
| |
On Saturday 26 June 2004 18:15, Russell King wrote: > On Sat, Jun 26, 2004 at 06:08:31PM +0100, Alistair John Strachan wrote: > > Every kernel in the 2.6 serious so far has exhibited the same problem; > > after some time of running my desktop system, I get: > > > > Assuming someone else called the IRQ > >... > > 19: 8748235 IO-APIC-level ohci1394, yenta, eth0 > > You don't say what eth0 is. At a guess, it's a prism54 card, because the > only place I find that message in the kernel is in the prism54 driver: > > drivers/net/wireless/prism54/islpci_dev.c: > printk(KERN_DEBUG "Assuming someone else called the IRQ\n"); >
Yes.
> I'd imagine that the OHCI1394 generates a fair number of interrupts, > so... this highlights the problem of leaving debugging printk's, > even at KERN_DEBUG level in a driver interrupt path.
I would agree.
> > At a guess, Luis R. Rodriguez may be the maintainer for prism54, > so...
Luis, could you please look into removing this message from the sources. It causes my kernel ring buffer to be wiped fairly quickly, which is annoying for debugging development kernels.
[OT] Thanks for the reply Russell. Any chance you could look over the BIOS workaround on bugzilla while we're discussing PCMCIA? I put a patch on there that's probably a load of nonsense, and we still haven't got your opinion on the matter..
http://bugzilla.kernel.org/show_bug.cgi?id=1840
It affects very few people, but it's a safe enough workaround as I'm using it successfully as I write this.
-- Cheers, Alistair.
personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student: CS/AI Undergraduate contact: 1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - 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/
| |