Re: spurious 8259A interrupt: IRQ7
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious 8259A interrupt: IRQ7
On Thu, 2005-04-14 at 14:43 -0600, Bjorn Helgaas wrote: > On Thu, 2005-04-14 at 13:11 -0400, Lee Revell wrote: > > I get this message occasionally on both my machines. I googled and saw > > some references to this message on 2.4 but nothing for 2.6. Some of the > > references were to APIC, which I don't have enabled. > > > > Both machines are using VIA chipsets and display the "VIA IRQ fixup" > > message on boot. I think this behavior started about the same time that > > message started to appear. > > The VIA IRQ fixup in 2.6.11 is broken. It works for some, but > not all boxes with VIA hardware. > > There's a fix in 2.6.12-rc2-mm3. Actually, I doubt that it will > help you, though -- the 2.6.11 breakage is such that some machines > that need the fixup don't get it (and don't print the "VIA IRQ > fixup message"). > 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. Anyway it's low priority as the message appears to be completely harmless. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious 8259A interrupt: IRQ7
On Thu, 2005-04-14 at 13:11 -0400, Lee Revell wrote: > I get this message occasionally on both my machines. I googled and saw > some references to this message on 2.4 but nothing for 2.6. Some of the > references were to APIC, which I don't have enabled. > > Both machines are using VIA chipsets and display the "VIA IRQ fixup" > message on boot. I think this behavior started about the same time that > message started to appear. The VIA IRQ fixup in 2.6.11 is broken. It works for some, but not all boxes with VIA hardware. There's a fix in 2.6.12-rc2-mm3. Actually, I doubt that it will help you, though -- the 2.6.11 breakage is such that some machines that need the fixup don't get it (and don't print the "VIA IRQ fixup message"). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious 8259A interrupt?
> > Initializing CPU#0 > > You are using a SMP kernel on a `386 UP machine. That tends to make > these burps show up. It is harmless, though. It says this either way > > Console: colour VGA+ 80x25 > > Calibrating delay loop... 3.10 BogoMIPS > > This shows something I don't understand. Either the counter wrapped, > a timer is mis-programmed, or the CPU clock speed is about 1.5 MHz. 3 bogomips is right for a 386SX > You should look into this. Older kernels generally show the BogoMIPS > as being about equal to the CPU clock speed +/- 20%. Newer kernels > generally show it being about 2 times the clock speed +/- 20%. Only if they have a TSC - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: spurious 8259A interrupt?
On Mon, 9 Oct 2000, Daniel Lange wrote: > Periodically, I get the following error with the 2.4.0test9 kernel: > > spurious 8259A interrupt: IRQ7. > [SNIPPED...] This will sometimes happen with the 8259A and really should not even be logged. There is a default handler for all interrupts. If this handler gets control from an unallocated interrupt, it writes this message, ACKs the interrupt, then returns. > Initializing CPU#0 You are using a SMP kernel on a `386 UP machine. That tends to make these burps show up. It is harmless, though. > Console: colour VGA+ 80x25 > Calibrating delay loop... 3.10 BogoMIPS This shows something I don't understand. Either the counter wrapped, a timer is mis-programmed, or the CPU clock speed is about 1.5 MHz. You should look into this. Older kernels generally show the BogoMIPS as being about equal to the CPU clock speed +/- 20%. Newer kernels generally show it being about 2 times the clock speed +/- 20%. > CPU: 386 > Checking 'hlt' instruction... OK. > Checking for popad bug... Buggy. I have one of these too. Cheers, Dick Johnson Penguin : Linux version 2.2.17 on an i686 machine (801.18 BogoMips). "Memory is like gasoline. You use it up when you are running. Of course you get it all back when you reboot..."; Actual explanation obtained from the Micro$oft help desk. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: spurious 8259A interrupt?
> important here (and it could just be a simple configuration error.) > Still, unless I'm mistaken, isn't an 8259A a UART, which should be related > to the serial port? Seems odd it would show up on IRQ 7... 8259A is the interrupt controller on a PC. (A pair of them actually). They raise IRQ 7 if they get a spurious interrupt. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
