Re: 2.6.8 error message - irq 7: nobody cared

From: stan (stanb_at_panix.com)
Date: 02/19/05

  • Next message: Joe Mc Cool: "cannot export / directory" 
    Date: Sat, 19 Feb 2005 16:31:33 -0500
To: debian-user@lists.debian.org

    On Sat, Feb 19, 2005 at 08:57:51PM +0000, Ray Curd wrote:
    > Hello to all,
    >
    > I recently upgraded to the 2.6.8 kernel and everything went fine but
    > then I started getting these intermitent error messages on the
    > console
    >
    > irq 7: nobody cared!
    > [__report_bad_irq+42/144] __report_bad_irq+0x2a/0x90
    > [note_interrupt+108/160] note_interrupt+0x6c/0xa0
    > [do_IRQ+289/304] do_IRQ+0x121/0x130
    > [common_interrupt+24/32] common_interrupt+0x18/0x20
    > [__do_softirq+48/128] __do_softirq+0x30/0x80
    > [do_softirq+38/48] do_softirq+0x26/0x30
    > [do_IRQ+253/304] do_IRQ+0xfd/0x130
    > [common_interrupt+24/32] common_interrupt+0x18/0x20
    > [default_idle+35/48] default_idle+0x23/0x30
    > [cpu_idle+44/64] cpu_idle+0x2c/0x40
    > [start_kernel+410/480] start_kernel+0x19a/0x1e0
    > [unknown_bootoption+0/352] unknown_bootoption+0x0/0x160
    > [__crc_get_wchan+3875811/6133658] (ide_intr+0x0/0x190 [ide_core])
    > Disabling IRQ #7
    >
    > Sometimes it was just the Disabling IRQ #7 on its own, and they
    > occured about every two minutes, They didn't happen every time one
    > day I ran without any at all. There was no other effects on my m/c as
    > far as I could tell and at the moment I have returned to 2.4.27 with
    > no sign of them at all.
    >
    A start might be to cat < /proc/interupts, and see what IRQ7 is assigned
    to. 

    -- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
						-- Benjamin Franklin
-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Joe Mc Cool: "cannot export / directory"