On Tue, 1 Jun 2004, Ville Pätsi wrote: > I found these in syslog when looking for the Sysrq trace: > > > Jun 1 12:15:30 meri kernel: irq 7: nobody cared! > Jun 1 12:15:30 meri kernel: Call Trace: > Jun 1 12:15:30 meri kernel: [<c010634a>] __report_bad_irq+0x2a/0x90 > Jun 1 12:15:30 meri kernel: [<c010643c>] note_interrupt+0x6c/0xa0 > Jun 1 12:15:30 meri kernel: [<c0106711>] do_IRQ+0x121/0x130 > Jun 1 12:15:30 meri kernel: [<c0104a74>] common_interrupt+0x18/0x20 > Jun 1 12:15:30 meri kernel: [<c011d830>] __do_softirq+0x30/0x80 > Jun 1 12:15:30 meri kernel: [<c011d8a6>] do_softirq+0x26/0x30 > Jun 1 12:15:30 meri kernel: [<c01066ed>] do_IRQ+0xfd/0x130 > Jun 1 12:15:30 meri kernel: [<c0104a74>] common_interrupt+0x18/0x20 > Jun 1 12:15:30 meri kernel: [<e085123b>] > acpi_processor_idle+0xd2/0x1c4 [processor] > Jun 1 12:15:30 meri kernel: [<c01020bc>] cpu_idle+0x2c/0x40 > Jun 1 12:15:30 meri kernel: [<c041075a>] start_kernel+0x15a/0x180 > Jun 1 12:15:30 meri kernel: [<c04104a0>] unknown_bootoption+0x0/0x120 > Jun 1 12:15:30 meri kernel: > Jun 1 12:15:30 meri kernel: handlers: > Jun 1 12:15:30 meri kernel: [<c0281880>] (usb_hcd_irq+0x0/0x70)
Like Oliver suggested, a lot of people have been reporting these "irq x: nobody cared!" problems recently. It seems to be related to the ACPI driver; that's why booting with acpi=off might help. One person reported that building the ACPI driver into the kernel, not as a loadable module, also made a difference. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
