From: Herman Oosthuysen <Herman@WirelessNetworksInc.com>
To: AnonimoVeneziano <voloterreno@tin.it>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Spurious 8259A interrupt: IRQ7 ????
Date: Fri, 24 Jan 2003 14:07:50 -0700 [thread overview]
Message-ID: <3E31AB26.5080508@WirelessNetworksInc.com> (raw)
In-Reply-To: <3E3199FF.3090000@tin.it>
It is a hardware 'feature', but nothing to worry about. The software
just has to live with it. This problem is as old as the PC itself,
dating back to the original IBM design from 1981.
Cheers,
--
Herman Oosthuysen
B.Eng (E), Member of IEEE
Aerospace Software Ltd
http://www.AerospaceSoftware.com
Phone: 1.403.852-5545, Fax: 1.403.241-8841
E-mail: Herman@AerospaceSoftware.com
E-mail: Herman@ARMdimension.com
AnonimoVeneziano wrote:
> I've noticed also that the number indicated by the ERR field in
> /proc/interrupts increase slowly with the time.
> But, at the end of all I haven't understood well what is this error, and
> what the ERR field indicates. And why with IO-APIC it disappears?
> (IO-APIC gives me very much problems with ACPI :-( )
>
> Bye
>
>
> AnonimoVeneziano wrote:
>
>> What does it mean this message?
>>
>> Of what problem is the signal?
>> There is a way to solve this? (Next kernel versions) or is an HW
>> problem? (Motherboard MSI KT7 Ultra)
>>
>> Thanks
>>
>> Bye
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2003-01-24 20:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 0:06 Spurious 8259A interrupt: IRQ7 ???? AnonimoVeneziano
2003-01-21 0:36 ` David D. Hagood
2003-01-21 1:43 ` Coax
2003-01-21 3:20 ` Alan
2003-01-21 5:22 ` Tupshin Harper
2003-01-21 7:00 ` Paul
2003-01-22 20:06 ` Ville Hallivuori
2003-01-22 20:53 ` Pavel Janík
2003-01-22 21:16 ` AnonimoVeneziano
2003-01-21 13:37 ` AnonimoVeneziano
2003-01-21 13:54 ` Richard B. Johnson
2003-01-21 23:53 ` Tom Vier
2003-01-23 22:14 ` Zsolt Babak
2003-01-23 23:56 ` Herman Oosthuysen
2003-01-24 19:54 ` AnonimoVeneziano
2003-01-24 21:07 ` Herman Oosthuysen [this message]
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=3E31AB26.5080508@WirelessNetworksInc.com \
--to=herman@wirelessnetworksinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=voloterreno@tin.it \
/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