mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Martin Wilck <Martin.Wilck@fujitsu-siemens.com>,
	Ingo Molnar <mingo@elte.hu>,
	Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Severe IRQ problems on Foster (P4 Xeon) system
Date: Thu, 21 Mar 2002 15:35:33 -0800	[thread overview]
Message-ID: <20020321233533.GB785@holomorphy.com> (raw)
In-Reply-To: <20020320202401.GA785@holomorphy.com> <Pine.LNX.4.44.0203210849320.32455-100000@netfinity.realnet.co.sz>

On Wed, 20 Mar 2002, William Lee Irwin III wrote:
>> There is/was at least one simulator that shoots the kernel (and
>> everything else) dead in response to frobbing the PIC while the local
>> APIC timer etc. are going, and I wouldn't be surprised if there were
>> some real hardware that did so as well.

On Thu, Mar 21, 2002 at 08:54:53AM +0200, Zwane Mwaikambo wrote:
> The problem was that the the simulator didn't support polling mode, which 
> linux 2.4 seems to use for handling the timer interrupt. The simulator PIC 
> implementation wasn't complete if it didn't support polling mode. You 
> shouldn't see this on real hardware.

Polling mode on the PIC wasn't there, true, so it did trigger a
simulator bug -- but the PIC should never have been touched. It was
using the local APIC timer etc. Or at least it certainly seems
counterintuitive to me that the PIC is set into polling mode and EOI'd
when the local APIC is whose timer is used and is where the interrupt
came from. We're using the APIC... why are we touching the PIC?


Cheers,
Bill

  reply	other threads:[~2002-03-21 23:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 19:11 Martin Wilck
2002-03-13 19:10 ` Ingo Molnar
2002-03-13 22:22   ` Bill Davidsen
2002-03-13 22:51     ` Alan Cox
2002-03-14  5:29       ` rddunlap
2002-03-14 14:26         ` Alan Cox
2002-03-15  7:55     ` Ingo Molnar
2002-03-14 13:29   ` Martin Wilck
2002-03-14 14:34     ` Martin J. Bligh
2002-03-14 18:22     ` Martin J. Bligh
2002-03-15  7:50       ` Ingo Molnar
2002-03-15  7:43     ` Ingo Molnar
2002-03-15 18:08       ` Martin J. Bligh
2002-03-19 13:38         ` Maciej W. Rozycki
2002-03-19 13:11   ` Maciej W. Rozycki
2002-03-27 17:35   ` Steffen Persvold
2002-03-19 14:32 ` Maciej W. Rozycki
2002-03-19 16:39   ` Martin Wilck
2002-03-19 23:28     ` Pavel Machek
2002-03-20  7:52       ` Martin Wilck
2002-03-20 13:27         ` Maciej W. Rozycki
2002-03-20 13:47           ` Martin Wilck
2002-03-20 14:13             ` Maciej W. Rozycki
2002-03-20 14:29           ` Alan Cox
2002-03-21 18:53           ` Martin Wilck
2002-03-20 13:52     ` Maciej W. Rozycki
2002-03-20 16:19       ` Martin Wilck
2002-03-21 13:03         ` Maciej W. Rozycki
2002-03-20 20:24   ` William Lee Irwin III
2002-03-21  6:54     ` Zwane Mwaikambo
2002-03-21 23:35       ` William Lee Irwin III [this message]
2002-03-22  0:18         ` Maciej W. Rozycki

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=20020321233533.GB785@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=Martin.Wilck@fujitsu-siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=mingo@elte.hu \
    --cc=zwane@linux.realnet.co.sz \
    /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®