public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: 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: Wed, 20 Mar 2002 12:24:01 -0800	[thread overview]
Message-ID: <20020320202401.GA785@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203131912140.1477-100000@biker.pdb.fsc.net> <Pine.GSO.3.96.1020319145208.12399I-100000@delta.ds2.pg.gda.pl>

On Tue, Mar 19, 2002 at 03:32:22PM +0100, Maciej W. Rozycki wrote:
>  The value is correct as after issuing the poll i8259 command the next
> read cycle to the PIC returns an IRQ level (0x07 = no IRQ active; it
> shouldn't happen here -- 0x80 is expected for active IRQ 0). 

On Wed, 13 Mar 2002, Martin Wilck wrote:
>> inb(0x20) call is not captured in our protocol, it must occur long after
>> the error. (We saw normal execution of the above code fragment where
>> there is ~1us between the outb and inb, where it is >120us here).


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.

(this is the code under if (timer_ack) in do_timer_interrupt())


Cheers,
Bill

  parent reply	other threads:[~2002-03-20 20:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 19:11 Severe IRQ problems on Foster (P4 Xeon) system 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 [this message]
2002-03-21  6:54     ` Zwane Mwaikambo
2002-03-21 23:35       ` William Lee Irwin III
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=20020320202401.GA785@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 \
    /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