From: "Martin Eriksson" <nitrax@giron.wox.org>
To: "Gunther Mayer" <Gunther.Mayer@t-online.de>, <root@chaos.analogic.com>
Cc: "Chris Meadors" <clubneon@hereintown.net>,
<linux-kernel@vger.kernel.org>, <martin@jtrix.com>
Subject: Re: 'spurious 8259A interrupt: IRQ7' -> read the 8259 datasheet !
Date: Fri, 30 Nov 2001 21:14:54 +0100 [thread overview]
Message-ID: <002501c179db$acff0f40$0201a8c0@HOMER> (raw)
In-Reply-To: <Pine.LNX.3.95.1011128084801.10732A-100000@chaos.analogic.com> <3C07DDC6.5FAE4E35@t-online.de>
----- Original Message -----
From: "Gunther Mayer" <Gunther.Mayer@t-online.de>
To: <root@chaos.analogic.com>
Cc: "Chris Meadors" <clubneon@hereintown.net>; "Martin Eriksson"
<nitrax@giron.wox.org>; <linux-kernel@vger.kernel.org>; <martin@jtrix.com>
Sent: Friday, November 30, 2001 8:28 PM
Subject: Re: 'spurious 8259A interrupt: IRQ7' -> read the 8259 datasheet !
> "Richard B. Johnson" wrote:
> >
> > On Wed, 28 Nov 2001, Chris Meadors wrote:
> >
> > > On Wed, 28 Nov 2001, Martin Eriksson wrote:
>
> ...
> ... rumours deleted (e.g. "printer status bits are all ORed into irq7")
> ...
>
> >From "Harris Semiconductor 82C59A Interrupt Controller Datasheet":
> If no interrupt request is present at step 4 of either sequence
> (i.e., the request was too short in duration), the 82C59A will
> issue an interrupt level 7.
Uhmm... call me slow, but I don't get it 100%... so this message has NOTHING
to do with the LPT IRQ7? It just signals this because IRQ7 is the lowest
priority IRQ on the 8259A?
>
> 1. The irq controller sees an interrupt.
> 2. The irq controller signals "there is _some_ interrupt" to the cpu.
> 3. The CPU acks via INTA
> 4. The irq controller looks if the irq is still there
> (and signals IRQ7 if the line is no longer active).
Umm.. so again.. this means that the IRQ is not held long enough for the PIC
to actually recognize *what* IRQ was asserted?
>
> You have some device which doesn't keep the IRQ raised long enough !
> (or the CPU doesn't service the irq for a too long time and the
> edge triggered irq is de-asserted or even serviced by a polling routine)
Thanks a bunch for clearing this up (this far)!!
When we get a firm indication on the 'problem', could the "spurious 8259A
interrupt" message be de-obfuscated into something less unsettling?
PS. Real Men (tm) never reads the datasheets!
_____________________________________________________
| Martin Eriksson <nitrax@giron.wox.org>
| MSc CSE student, department of Computing Science
| Umeå University, Sweden
prev parent reply other threads:[~2001-11-30 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 17:06 'spurious 8259A interrupt: IRQ7' Alex Davis
2001-11-28 0:01 ` Peter Bornemann
2001-11-28 8:58 ` szonyi calin
2001-11-28 9:31 ` Wouter van Bommel
2001-11-28 9:52 ` Martin Eriksson
2001-11-28 13:59 ` Chris Meadors
2001-11-28 14:06 ` Richard B. Johnson
2001-11-28 14:23 ` Piter Punk
2001-11-30 19:28 ` 'spurious 8259A interrupt: IRQ7' -> read the 8259 datasheet ! Gunther Mayer
2001-11-30 19:47 ` Richard B. Johnson
2001-11-30 22:44 ` Gunther Mayer
2001-11-30 20:14 ` Martin Eriksson [this message]
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='002501c179db$acff0f40$0201a8c0@HOMER' \
--to=nitrax@giron.wox.org \
--cc=Gunther.Mayer@t-online.de \
--cc=clubneon@hereintown.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@jtrix.com \
--cc=root@chaos.analogic.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