2.6.10 IRQ 18 issues gone away

From: Bill Davidsen (davidsen_at_tmr.com)
Date: 01/03/05

  • Next message: Jim Nelson: "Re: printk loglevel policy?"
    Date:	Sun, 02 Jan 2005 23:22:05 -0500
    To: Linux Kernel M/L <linux-kernel@vger.kernel.org>
    
    

    My ongoing issue with runaway IRQ 18 floods has gone away, although I am
    not totally sure they are "solved" in the usual sense. I flashed the
    latest BIOS from Asus and had various problems (P4P81019) then flashed
    one I got as a gift from a nameless source (P4P81086). That did the
    trick, all the IRQs are no longer shared, even though they worked
    perfectly as shared on 2.4.22-1.2199 (FC1) with the original BIOS.

    Since the system worked with 2.4 and not with 2.6, even though a BIOS
    change made the problem go away, I suspect that there is still some
    issue with the shared IRQ, although I am certainly NOT interested in
    going back to help find it!

    Many thanks to people who suggested BIOS upgrade as a workaround for the
    kernel, and pointed me at installing from CD instead of floppy (I don't
    have floppy). The system is now stable although there are a number of
    "not in 2.6" issues to solve eventually.

    My new interrupt map if anyone cares:
               CPU0 CPU1
      0: 4770773 4751617 IO-APIC-edge timer
      1: 8275 9223 IO-APIC-edge i8042
      8: 1 0 IO-APIC-edge rtc
      9: 0 0 IO-APIC-level acpi
     12: 52649 44985 IO-APIC-edge i8042
     14: 15451 12645 IO-APIC-edge ide0
     15: 99181 135233 IO-APIC-edge ide1
     16: 332255 330935 IO-APIC-level radeon@PCI:1:0:0
     17: 246658 257869 IO-APIC-level Intel ICH5
     22: 6069 6292 IO-APIC-level SysKonnect SK-98xx
    NMI: 0 0
    LOC: 9453797 9458470
    ERR: 0
    MIS: 0

    -
    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/


  • Next message: Jim Nelson: "Re: printk loglevel policy?"

    Relevant Pages

    • ACPI related panic
      ... latest bios + some patches to fix utallocate errors) I'm ... irq 2 ... Location Bus Device Pin Link IRQs ... device fwohci0 requested decoded memory range 0xfaffb800-0xfaffbfff ...
      (freebsd-current)
    • Re: 2.6.0-test3-mm3 reserve IRQ for isapnp
      ... >The reserve IRQ feature in your BIOS should not effect the linux kernel. ... >your ide controller. ... hub 1-0:0: enabling power on all ports ...
      (Linux-Kernel)
    • Re: Black screen on booting
      ... Check and recheck your video adapter driver and BIOS. ... Your IRQ sharing seems normal to me. ... >down overnight, but if you wait till it warms up, it will boot as follows: ...
      (microsoft.public.win2000.general)
    • Re: IRQ-Problem mit Netzwerkkarte
      ... > die Bootreihenfolge auf Floppy zuerst. ... anhand der Tabelle feststellen, ob noch ein IRQ frei ist, ... im Bios dem Slot einen IRQ zuweisen. ...
      (microsoft.public.de.german.windowsxp.sonstiges)
    • Re: IRQ-Problem mit Netzwerkkarte
      ... > die Bootreihenfolge auf Floppy zuerst. ... anhand der Tabelle feststellen, ob noch ein IRQ frei ist, ... im Bios dem Slot einen IRQ zuweisen. ...
      (microsoft.public.de.german.windowsxp.sonstiges)