> On Mon, Jan 07, 2002 at 02:16:28PM +0100, Petr Vandrovec wrote:
> > Nope. Probably when CPU is in local APIC mode, it acknowledges interrupts
> > to chipset with different timming, and from time to time CPU still
> > sees IRQ pending, so it asks for vector, but as chipset has no
> > interrupt pending, it answers with IRQ7. I did no analysis to find
> > whether IRQ7 happens directly when we send confirmation to 8259,
> > or whether it happens due to some noise on IRQ line.
> > AFAIK it happens only on VIA based boards, and only if (AMD) CPU is using
> > APIC.
> My system is based on AMD's own 750 Irongate chipset, and it produces
> both the initial spurious IRQ7 message and plentiful "ERR" interrupts:
All my machines (from SiS 735, over Intel-BX to older Aladin-5
(super7) boxes) producing such "spurious IRQ7" with the actual 2.4.16
or 2.4.17 kernels ...
> srwalter@hapablap:~$ uptime
> 11:31am up 42 days, 18:19, 1 user, load average: 1.04, 1.02, 1.00
> srwalter@hapablap:~$ cat /proc/interrupts | grep ERR
> ERR: 67169
> In a time of universal deceit, telling the truth is a revolutionary act.
> -- George Orwell
> He's alive. He's alive! Oh, that fellow at RadioShack said I was mad!
> Well, who's mad now?
> -- Montgomery C. Burns
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to firstname.lastname@example.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/