public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: linux-kernel@vger.kernel.org, pat@cs.curtin.edu.au
Subject: Re: spurious 8259A interrupt: IRQ7
Date: Mon, 8 Jul 2002 14:30:59 +0200	[thread overview]
Message-ID: <A4F8F3A725D@vcnet.vc.cvut.cz> (raw)

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
                                                            

             reply	other threads:[~2002-07-08 12:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 12:30 Petr Vandrovec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-15 17:11 spurious 8259A interrupt: IRQ7 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
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
2002-07-08  9:13 Patrick Clohessy
2002-07-08  9:27 ` jbradford
2002-07-08 10:05 ` Tomas Szepe

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=A4F8F3A725D@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pat@cs.curtin.edu.au \
    --cc=szepe@pinerecords.com \
    /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