mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: srwalter@yahoo.com
Cc: VANDROVE@vc.cvut.cz, linux-kernel@vger.kernel.org
Subject: Re: "APIC error on CPUx" - what does this mean?
Date: Mon, 07 Jan 2002 19:20:38 +0100 (CET)	[thread overview]
Message-ID: <20020107.192038.884040663.rene.rebe@gmx.net> (raw)
In-Reply-To: <20020107113227.A31231@hapablap.dyn.dhs.org>
In-Reply-To: <E37DB7922B4@vcnet.vc.cvut.cz> <20020107113227.A31231@hapablap.dyn.dhs.org>

From: Steven Walter <srwalter@yahoo.com>
Subject: Re: "APIC error on CPUx" - what does this mean?
Date: Mon, 7 Jan 2002 11:32:27 -0600

> On Mon, Jan 07, 2002 at 02:16:28PM +0100, Petr Vandrovec wrote:
> > 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.
> 
> My system is based on AMD's own 750 Irongate chipset, and it produces
> both the initial spurious IRQ7 message and plentiful "ERR" interrupts:

All my machines (from SiS 735, over Intel-BX to older Aladin-5
(super7) boxes) producing such "spurious IRQ7" with the actual 2.4.16
or 2.4.17 kernels ...

> srwalter@hapablap:~$ uptime
>  11:31am  up 42 days, 18:19,  1 user,  load average: 1.04, 1.02, 1.00
> srwalter@hapablap:~$ cat /proc/interrupts | grep ERR
> ERR:      67169
> -- 
> -Steven
> In a time of universal deceit, telling the truth is a revolutionary act.
> 			-- George Orwell
> He's alive.  He's alive!  Oh, that fellow at RadioShack said I was mad!
> Well, who's mad now?
> 			-- Montgomery C. Burns
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  parent reply	other threads:[~2002-01-07 18:22 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
2002-01-07 17:32 ` Steven Walter
2002-01-07 18:20 ` Rene Rebe [this message]
  -- 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=20020107.192038.884040663.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srwalter@yahoo.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®