public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: pat@cs.curtin.edu.au (Patrick Clohessy)
Cc: linux-kernel@vger.kernel.org
Subject: Re: spurious 8259A interrupt: IRQ7
Date: Mon, 8 Jul 2002 10:27:41 +0100 (BST)	[thread overview]
Message-ID: <200207080927.KAA00734@darkstar.example.net> (raw)
In-Reply-To: <3D2957A9.6D90A916@cs.curtin.edu.au> from "Patrick Clohessy" at Jul 08, 2002 05:13:13 PM

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.

  reply	other threads:[~2002-07-08  9:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08  9:13 spurious 8259A interrupt: IRQ7 Patrick Clohessy
2002-07-08  9:27 ` jbradford [this message]
2002-07-08 10:05 ` Tomas Szepe
  -- strict thread matches above, loose matches on Subject: below --
2002-07-08 12:30 Petr Vandrovec
2005-04-14 17:11 Lee Revell
2005-04-14 20:43 ` Bjorn Helgaas
2005-04-14 20:56   ` Lee Revell
2005-04-14 21:03     ` Bjorn Helgaas
2005-05-22 22:41       ` Jesper Juhl
2006-01-15 17:11 Jiri Slaby
2006-01-15 17:21 ` Jiri Slaby
2006-01-15 21:12   ` Jan Engelhardt
2006-01-15 22:21     ` Jiri Slaby
2006-01-20 17:55 ` Jiri Slaby

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=200207080927.KAA00734@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pat@cs.curtin.edu.au \
    /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