public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: "APIC error on CPUx" - what does this mean?
Date: Mon, 7 Jan 2002 13:29:42 +0100	[thread overview]
Message-ID: <E3713B21FAB@vcnet.vc.cvut.cz> (raw)

On  7 Jan 02 at 23:17, Chris Wedgwood wrote:
> On Thu, Jan 03, 2002 at 10:38:27PM +0000, Alan Cox wrote:
>     The occasional APIC error is fine (its logging a hardware event -
>     probably something that caused enough noise to lose a message and
>     retry it). The APIC bus is designed to stand these occasional
>     errors
> 
> I'm curious... is there any way to determine what is causing these?
> On a UP athlon I have:
> 
> cw:tty5@charon(cw)$ uname -r ; uptime && grep ERR /proc/interrupts
> 2.4.17-rc2
>  02:09:50 up 4 days,  5:18, 10 users,  load average: 0.00, 0.00, 0.00
> ERR:       5216
> 
> which equates several per minute at times... no funny hardware, not
> running X11, and I don't remembering seeing these a while ago on this
> same mainboard (but I never really looked either, so that might not be
> true).

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).
                                            Best regards,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz
                                                

             reply	other threads:[~2002-01-07 12:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 12:29 Petr Vandrovec [this message]
2002-01-07 13:08 ` "APIC error on CPUx" - what does this mean? Chris Wedgwood
  -- 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 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
2002-01-07 17:32 ` Steven Walter
2002-01-07 18:20   ` Rene Rebe
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=E3713B21FAB@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --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