public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul <set@pobox.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Spurious 8259A interrupt: IRQ7 ????
Date: Tue, 21 Jan 2003 02:00:19 -0500	[thread overview]
Message-ID: <20030121070019.GL16611@squish.home.loc> (raw)
In-Reply-To: <3E2CD91B.2080305@tupshin.com>

Tupshin Harper <tupshin@tupshin.com>, on Mon Jan 20, 2003 [09:22:35 PM] said:
> David D. Hagood wrote:
> 
> >It is most likely a hardware problem.
> >
> 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.
> 
> one example:
> Jan 20 09:20:21 testing kernel: parport0: PC-style at 0x378 [PCSPP,EPP]
> Jan 20 09:20:21 testing kernel: parport_pc: Via 686A parallel port: io=0x378
> <snip>
> Jan 20 09:20:07 testing kernel: spurious 8259A interrupt: IRQ7.
> 
> -Tupshin
> 

	Hi;

	I see it just once every boot, and I dont have any parallel
port stuff enabled. (2.5.59)

Paul
set@pobox.com

  reply	other threads:[~2003-01-21  6:51 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 [this message]
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

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=20030121070019.GL16611@squish.home.loc \
    --to=set@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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