Hi
I was just wondering if anyone could help me solve a problem I'm having.
I have installed red hat 7.3 with kernel version 2.4.18 on an AMD Duron
1100 with a ASUS A7V133-C Motherboard, 32MB TNT2 and a 20 GIG Maxtor
Viper HD. Whenever the machine boots up, the following error appears :
spurious 8259A interrupt: IRQ7
I have read through quite a few mailing lists and other sources but
can't find an adequate solution. One solution I found was to turn off
Local APIC support and IO-APIC support in the kernel, which I tried and
it worked, but I'd rather not do this. I realise the error isn't of a
huge concern but it's still annoying having it appear everytime the
machine boots up.
Any help will be greatly appreciated.
Thanks
--
Patrick Clohessy
Curtin University of Technology
School of Computing
Tel: +61 8 9266 2986
email: [email protected]
Hi,
> I was just wondering if anyone could help me solve a problem I'm having.
> I have installed red hat 7.3 with kernel version 2.4.18 on an AMD Duron
> 1100 with a ASUS A7V133-C Motherboard, 32MB TNT2 and a 20 GIG Maxtor
> Viper HD. Whenever the machine boots up, the following error appears :
>
> spurious 8259A interrupt: IRQ7
>
> I have read through quite a few mailing lists and other sources but
> can't find an adequate solution. One solution I found was to turn off
> Local APIC support and IO-APIC support in the kernel, which I tried and
> it worked, but I'd rather not do this. I realise the error isn't of a
> huge concern but it's still annoying having it appear everytime the
> machine boots up.
>
> Any help will be greatly appreciated.
Why not just comment out the line in the kernel source that prints the error? I know it sounds stupid, but it will solve your problem :-).
John.
> I have read through quite a few mailing lists and other sources but
> can't find an adequate solution. One solution I found was to turn off
> Local APIC support and IO-APIC support in the kernel, which I tried and
> it worked, but I'd rather not do this. I realise the error isn't of a
> huge concern but it's still annoying having it appear everytime the
> machine boots up.
Your fix is to just realize that this is a mere warning -- Nothing's
wrong with your setup.
If you dig out a thread that came through here abt. two months ago,
you'll find a comprehensive explanation of what the message means.
T.
On 8 Jul 02 at 12:05, Tomas Szepe wrote:
> > I have read through quite a few mailing lists and other sources but
> > can't find an adequate solution. One solution I found was to turn off
> > Local APIC support and IO-APIC support in the kernel, which I tried and
> > it worked, but I'd rather not do this. I realise the error isn't of a
> > huge concern but it's still annoying having it appear everytime the
> > machine boots up.
>
> Your fix is to just realize that this is a mere warning -- Nothing's
> wrong with your setup.
>
> If you dig out a thread that came through here abt. two months ago,
> you'll find a comprehensive explanation of what the message means.
Fortunately... since kernel HZ changed to 1000Hz, I have about two these
spurious interrupts delivered to the CPU on my A7V each second. Fortunately
they are always really spurious, not misdelivered other interrupts, but
seeing values like 10000 in ERR field in /proc/interrupts is something new
to me ;-) Maybe VIA or AMD should really clarify what's the problem.
Petr Vandrovec