From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: 2.6.10 IRQ 18 issues gone away
Date: Sun, 02 Jan 2005 23:22:05 -0500 [thread overview]
Message-ID: <41D8C86D.4090603@tmr.com> (raw)
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
reply other threads:[~2005-01-03 4:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41D8C86D.4090603@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox