From: cheuche+lkml@free.fr
To: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ?
Date: Thu, 4 Dec 2003 21:02:08 +0100 [thread overview]
Message-ID: <20031204200208.GA4167@localnet> (raw)
In-Reply-To: <20031204175548.GB10471@forming>
Hello,
Along with the lockups already described here, I've noticed an
unidentified source of interrupts on IRQ7. Several people posted their
/proc/interrupts but it only shows interrupts a driver registered and is
using. I noticed a non-constant stream of interrupts on IRQ7 using sar
and I am also able to see it under /proc/interrupts when loading
parport_pc with options to get the driver using the interrupt. However
it is not related to the parallel port because putting it on IRQ5 or
disabling it in the BIOS does not affect the stream of interrupts on
IRQ7. I wonder if people experiencing lockup problems also have these
noise interrupts, and I don't know if this has something to do with the
lockups or if it is an independant problem.
Of course, booting with noapic nolapic, the system is rock-solid, and
the interrupt counter on IRQ7 stays solidly at 1 (should it be 0 ?),
until I use something on the parallel port of course.
Motherboard : abit nfs7-s v2.0, nforce2 chipset
Kernels : 2.6.0-test9, 2.6.0-test10, 2.6.0-test10-mm1, 2.6.0-test11
/proc/interrupts with apic+lapic, shortly after boot, already 408
interrupts on IRQ7 :
CPU0
0: 121148 XT-PIC timer
1: 279 IO-APIC-edge i8042
2: 0 XT-PIC cascade
7: 408 IO-APIC-edge parport0
8: 4 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
14: 2591 IO-APIC-edge ide0
15: 2916 IO-APIC-edge ide1
16: 47 IO-APIC-level eth0
18: 0 IO-APIC-level EMU10K1
19: 4373 IO-APIC-level mga@PCI:2:0:0
20: 31 IO-APIC-level ohci-hcd
21: 0 IO-APIC-level ehci_hcd, NVidia nForce2
22: 0 IO-APIC-level ohci-hcd
NMI: 0
LOC: 120982
ERR: 0
MIS: 0
/proc/interrupts with noapic and nolapic, with IRQ7 showing only 1
interrupt since boot :
CPU0
0: 803521 XT-PIC timer
1: 1446 XT-PIC i8042
2: 0 XT-PIC cascade
5: 54875 XT-PIC mga@PCI:2:0:0
7: 1 XT-PIC parport0
8: 4 XT-PIC rtc
9: 0 XT-PIC acpi
10: 16027 XT-PIC ohci_hcd,eth0, NVidia nForce2
11: 1903732 XT-PIC bttv0, ehci_hcd, EMU10K1
12: 9416 XT-PIC ohci_hcd
14: 8513 XT-PIC ide0
15: 3910 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
Mathieu
next prev parent reply other threads:[~2003-12-04 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 12:17 NForce2 pseudoscience stability testing (2.6.0-test11) b
2003-12-04 15:19 ` Craig Bradney
2003-12-04 16:32 ` Josh McKinney
2003-12-04 17:08 ` Julien Oster
2003-12-04 17:55 ` Josh McKinney
2003-12-04 20:02 ` cheuche+lkml [this message]
2003-12-04 20:48 ` NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ? Bob
2003-12-04 23:05 ` Jesse Allen
2003-12-04 23:14 ` Prakash K. Cheemplavam
2003-12-04 23:21 ` Craig Bradney
2003-12-04 23:36 ` Prakash K. Cheemplavam
2003-12-05 5:47 ` Bob
2003-12-05 7:01 ` Craig Bradney
2003-12-05 12:33 ` Prakash K. Cheemplavam
2003-12-05 8:16 ` cheuche+lkml
2003-12-05 13:28 ` NForce2 pseudoscience stability testing (2.6.0-test11) Pat Erley
2003-12-05 5:56 NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ? b
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=20031204200208.GA4167@localnet \
--to=cheuche+lkml@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).