mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Eriksson" <nitrax@giron.wox.org>
To: "Chris Wedgwood" <cw@f00f.org>
Cc: <swsnyder@home.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	<alan@lxorguk.ukuu.org.uk>
Subject: Re: "APIC error on CPUx" - what does this mean?
Date: Mon, 7 Jan 2002 15:40:55 +0100	[thread overview]
Message-ID: <007b01c19789$50c695b0$0201a8c0@HOMER> (raw)
In-Reply-To: <E37DB7922B4@vcnet.vc.cvut.cz>

----- Original Message -----
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: "Chris Wedgwood" <cw@f00f.org>
Cc: <swsnyder@home.com>; "Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>; <alan@lxorguk.ukuu.org.uk>
Sent: Monday, January 07, 2002 2:16 PM
Subject: Re: "APIC error on CPUx" - what does this mean?


> On  8 Jan 02 at 2:08, Chris Wedgwood wrote:
> > On Mon, Jan 07, 2002 at 01:29:42PM +0100, Petr Vandrovec wrote:
> >
> >     They are spurious IRQ 7, just message is printed only once during
> >     kernel lifetime... I have about three spurious IRQ 7 per each 1000
> >     interrupts delivered to CPU. It is on A7V (Via KT133).
> >
> > Any idea _why_ these occur though?  It seems some mainboards produce a
> > plethora of these whilst others never produce these...
>
> Nope. Probably when CPU is in local APIC mode, it acknowledges interrupts
> to chipset with different timming, and from time to time CPU still
> sees IRQ pending, so it asks for vector, but as chipset has no
> interrupt pending, it answers with IRQ7. I did no analysis to find
> whether IRQ7 happens directly when we send confirmation to 8259,
> or whether it happens due to some noise on IRQ line.
>
> AFAIK it happens only on VIA based boards, and only if (AMD) CPU is using
> APIC.

This (APIC errors) happened very often with my BP6 board too, but with
recent kernels I don't get many of these messages.

As for spurious interrupts, I had these coming every five minutes on my
Cyrix 6x86/SiS 5597 box. But this "settled" when I moved the box to another
corner in the room, and also did some interior adjustments of cables and
such (it is a server running in a very crammed slimline desktop box, with a
HUB taped to the floppy mount =)

_____________________________________________________
|  Martin Eriksson <nitrax@giron.wox.org>
|  MSc CSE student, department of Computing Science
|  Umeå University, Sweden




  parent reply	other threads:[~2002-01-07 14:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 13:16 Petr Vandrovec
2002-01-07 13:33 ` Alan Cox
2002-01-07 13:42 ` Chris Wedgwood
2002-01-07 14:40 ` Martin Eriksson [this message]
2002-01-07 17:32 ` Steven Walter
2002-01-07 18:20 ` Rene Rebe
  -- strict thread matches above, loose matches on Subject: below --
2002-01-09 12:41 Petr Vandrovec
2002-01-09 14:34 ` Maciej W. Rozycki
2002-01-08 17:35 Petr Vandrovec
2002-01-07 16:58 Petr Vandrovec
2002-01-08 12:12 ` Maciej W. Rozycki
2002-01-08 12:30   ` Chris Wedgwood
2002-01-07 12:29 Petr Vandrovec
2002-01-07 13:08 ` Chris Wedgwood
2002-01-03 19:55 Steve Snyder
2002-01-03 20:10 ` listmail
2002-01-03 21:47 ` Ryan Cumming
2002-01-03 22:38 ` Alan Cox
2002-01-03 23:21   ` Pozsar Balazs
2002-01-07 10:17   ` Chris Wedgwood

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='007b01c19789$50c695b0$0201a8c0@HOMER' \
    --to=nitrax@giron.wox.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swsnyder@home.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

all inboxes | Powered by JetHome®