[lkml]   [2005]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: spurious 8259A interrupt: IRQ7
On 4/14/05, Bjorn Helgaas <> wrote:
> On Thu, 2005-04-14 at 16:56 -0400, Lee Revell wrote:
> > Is the VIA IRQ fixup related to the "spurious interrupts" messages in
> > any way? Googling the 2.4 threads on the issue gave me the impression
> > that it's related to broken hardware. I think excessive disk activity
> > might trigger it.
> If you need the VIA IRQ fixup and don't have it, I would expect
> some interrupt to be routed to the wrong IRQ. That might give
> you a "spurious interrupt" on the wrong IRQ, but your device would
> probably just not work at all.

For what it's worth I'll chime in with my own info on this subject.

I also see the
spurious 8259A interrupt: IRQ7.
messages from time to time. Actually I got one just a little while ago :
$ dmesg | grep spurious
[18994.222451] spurious 8259A interrupt: IRQ7.
The system seems to be in good shape - it has never caused me any
actual trouble.

As for the via irq fixup I see this :
$ dmesg | grep -i fixup
[ 74.629393] PCI: Via PIC IRQ fixup for 0000:00:09.0, from 255 to 3

The hardware is a ASUS A7M266 mobo with a AMD Athlon (t-bird) 1.4GHz CPU.

The kernel is 2.6.12-rc4-mm2 :
$ uname -a
Linux dragon 2.6.12-rc4-mm2 #2 Mon May 16 18:14:13 CEST 2005 i686
unknown unknown GNU/Linux

I've seen some references to APIC for this issue, so here are the APIC
related settings in my .config :

juhl@dragon:~/download/kernel/linux-2.6.12-rc4-mm2$ grep -i APIC .config
# CONFIG_X86_UP_APIC is not set

Jesper Juhl <>
Don't top-post
Plain text mails only, please
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-05-23 00:45    [W:0.040 / U:4.188 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site