From: AnonimoVeneziano <voloterreno@tin.it>
To: vph@iki.fi
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Spurious 8259A interrupt: IRQ7 ????
Date: Wed, 22 Jan 2003 22:16:16 +0100 [thread overview]
Message-ID: <3E2F0A20.20603@tin.it> (raw)
In-Reply-To: <20030122200630.GA17220@vph.iki.fi>
Ville Hallivuori wrote:
>>I wouldn't necessarily assume a hardware problem (unless we also include
>>chipset oddities). I get *exactly* one message stating exactly this per
>>boot, and it always come a few seconds after loading the parport and
>>parport_pc modules.
>>
>>
>
>
>
>>Jan 20 09:20:07 testing kernel: spurious 8259A interrupt: IRQ7.
>>
>>
>
>I also see this message on every boot... I have two Soyo
>SY-KT400 Dragon Ultra mother boards, and the message appears with both
>of them. Perhaps it is some VIA oddity?. Anyhow, it does not seem to
>have any harmful effects (both boards are rock solid with 2.4.20).
>
>Dec 23 20:34:37 mood kernel: Real Time Clock Driver v1.10e
>Dec 23 20:34:37 mood kernel: spurious 8259A interrupt: IRQ7.
>
>
>
>
When I enable I/O APIC the problem disappear , it is present only if I
enable Local APIC. There is a possibility that that IRQ is an IRQ of I/O
APIC , and when it is disabled it isn't initialized with Local APIC only
. In this case the message can be ignored without any preoccupations
Bye
Marcello
next prev parent reply other threads:[~2003-01-22 21:05 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 [this message]
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
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=3E2F0A20.20603@tin.it \
--to=voloterreno@tin.it \
--cc=linux-kernel@vger.kernel.org \
--cc=vph@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.