From: war <war@lucidpixels.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Spurious 8259A Interrupt IRQ 7
Date: Sun, 22 Jun 2003 19:27:03 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0306221924400.361@p500> (raw)
In-Reply-To: <1056322074.2075.40.camel@dhcp22.swansea.linux.org.uk>
Also, I am not sure how the IO-APIC & IRQ routing work, however, with the
ATA/100 TX1 (first generation promise controller, the interrupts are
shared differently.
Whether this makes a difference or has anything to do with the spurious
interrupts/messages, I am not sure.
Before:
# cat /proc/interrupts
CPU0
0: 6486628 XT-PIC timer
1: 6 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 647546 XT-PIC serial
5: 0 XT-PIC Crystal audio controller
8: 1 XT-PIC rtc
9: 3548883 XT-PIC eth2, eth3
11: 2601852 XT-PIC ide2, ide3, eth0, eth1
12: 38 XT-PIC PS/2 Mouse
14: 121950 XT-PIC ide0
15: 25 XT-PIC ide1
NMI: 0
LOC: 6486487
ERR: 11
MIS: 0
After:
CPU0
0: 22081 XT-PIC timer
1: 6 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 2061 XT-PIC serial
5: 0 XT-PIC Crystal audio controller
8: 1 XT-PIC rtc
9: 4233 XT-PIC eth2, eth3
10: 37 XT-PIC ide2, ide3
11: 2071 XT-PIC eth0, eth1
12: 38 XT-PIC PS/2 Mouse
14: 6037 XT-PIC ide0
15: 24 XT-PIC ide1
NMI: 0
LOC: 22032
ERR: 0
MIS: 0
Now to see if I get any more of these spurious interrupts...
On Sun, 22 Jun 2003, Alan Cox wrote:
> IRQ7 is raised if an interrupt appears and then vanishes again before it
> can be serviced. For 2.4.20/21 at least it can occur from the IDE layer
> and maybe others
>
>
next prev parent reply other threads:[~2003-06-22 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 22:20 war
2003-06-22 22:47 ` Alan Cox
2003-06-22 23:01 ` war
2003-06-22 23:27 ` war [this message]
2003-06-23 6:11 ` Felipe Alfaro Solana
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=Pine.LNX.4.56.0306221924400.361@p500 \
--to=war@lucidpixels.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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®