Cool. Didn't know if the stuff below was part of that or not.
> > irq 10: nobody cared!
> > Call Trace:
> > [<c010a2d1>] handle_IRQ_event+0x91/0x100
> > [<c010a2d9>] handle_IRQ_event+0x99/0x100
> > [<c010a4f5>] do_IRQ+0xb9/0x130
> > [<c0108f9c>] common_interrupt+0x18/0x20
> > [<c0113236>] delay_tsc+0x12/0x1c
> > [<c0201152>] __delay+0x12/0x18
> > [<c02011c1>] __const_udelay+0x21/0x30
>
> These aren't oopses. They're reports with a call trace that someone
Yeah. I realised that baout 20 seconds after I hit 'y' to send. :)
> didn't find something to service when an interrupt occurred. Earlier
> kernels ignored this condition. You can safely ignore them for now,
> but at some point they do need to be cleaned up.
Cool. I shall cease to worry then. :)
Thanks. :)
-- Martin's distress was in contrast to the bitter satisfaction of some of his fellow marines as they surveyed the scene. "The Iraqis are sick people and we are the chemotherapy," said Corporal Ryan Dupre. "I am starting to hate this country. Wait till I get hold of a friggin' Iraqi. No, I won't get hold of one. I'll just kill him." - http://www.informationclearinghouse.info/article2479.htm - 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/