[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 2.6.8 error message - irq 7: nobody cared



Ray Curd <rayjc@superdad.freeserve.co.uk> wrote in message news:<3zJS5-RW-41@gated-at.bofh.it>...
> 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.
> 
> As I feel completely out of my depth I hope someone may be able to 
> explain what may be happening.
> 
> Regards 
> 
> Ray Curd.

I have exactly the same problem and I am investigating this quite a
while. During boot time the system randomly assigns ide0 to IRQ #7 or
IRQ #14. The problem occurs only when ide0 is assigned to IRQ#7 and
then the following message is printed repeatedly on every(!) terminal
window:

  Message from syslogd@localhost at Mon Feb 21 09:29:28 2005 ...
  localhost kernel: Disabling IRQ #7

which is very annoying.
'cat /proc/interrupts' then looks like:

           CPU0
  0:    2154743          XT-PIC  timer
  1:        400    IO-APIC-edge  i8042
  7:    1506026    IO-APIC-edge  ide0
  8:          1    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 12:       2614    IO-APIC-edge  i8042
 15:      19069    IO-APIC-edge  ide1
177:          0   IO-APIC-level  ohci_hcd
185:          0   IO-APIC-level  NVIDIA nForce Audio, ohci_hcd
193:          1   IO-APIC-level  ehci_hcd
201:     188225   IO-APIC-level  eth0, radeon@PCI:2:0:0
NMI:          0
LOC:    2154588
ERR:          0
MIS:          0

I tried to use kernel parameters 'nolapic', 'noapic' (=> system does
not work at all), noacpi, pci=routeirq and nothing did help. I also
tried to disable ACPI in the BIOS.

This is a part of the 'dmesg' output of boot messages:

 NFORCE2: IDE controller at PCI slot 0000:00:09.0
 NFORCE2: chipset revision 162
 NFORCE2: not 100% native mode: will probe irqs later
 NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
 NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
 hda: HDS722580VLAT20, ATA DISK drive
 hda: IRQ probe failed (0xfffffdfc)
 Using anticipatory io scheduler
 ide0 at 0x1f0-0x1f7,0x3f6 on irq 7

'uname -a':
Linux linux10 2.6.8-2-k7 #1 Mon Jan 24 03:29:52 EST 2005 i686
GNU/Linux

(going back to i386 kernel also does not help)

Apart from the annoying messages, the system runs fine. And as I said,
rebooting the machine has a good chance to end up with hde0 on irq #14
and all the errors are gone.

Does anyone of you has a hint what else I could try to turn the errors
off?

Michael



Reply to: