public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: cw@f00f.org (Chris Wedgwood),
	swsnyder@home.com,
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
	alan@lxorguk.ukuu.org.uk
Subject: Re: "APIC error on CPUx" - what does this mean?
Date: Mon, 7 Jan 2002 17:58:14 +0100	[thread overview]
Message-ID: <E3B8D7A16F6@vcnet.vc.cvut.cz> (raw)

On  7 Jan 02 at 13:33, Alan Cox wrote:
> > 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.
> 
> Are you using an AMD northbridge and VIA southbridge together ?

No. It is fully-VIA motherboard (Asus A7V), VIA KT133 as a northbridge 
and VIA686A as a southbridge, with 1GHz Athlon. And spurious IRQ happen 
when either of (massive) IRQ sources (Promise UDMA, tulip-based network 
card, an es137x soundcard) emits interrupts.

Problem is best visible when Promise is used in PIO mode with block size=512,
as in such case you can get thousands of IRQs from Promise in second, and
tenths of spurious IRQ7. But even if Promise emits in average one IRQ each 
second (== idle system with running cron and atime updates on), I get 
~10 of spurious IRQ7 during one hour.

I can get complete lspci -vvv at home, if you want.
                                                Best regards,
                                                    Petr Vandrovec
                                                    vandrove@vc.cvut.cz
                                                    

             reply	other threads:[~2002-01-07 16:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 16:58 Petr Vandrovec [this message]
2002-01-08 12:12 ` "APIC error on CPUx" - what does this mean? Maciej W. Rozycki
2002-01-08 12:30   ` 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 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-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=E3B8D7A16F6@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