From: Len Brown <len.brown@intel.com>
To: Jonathan Filiatrault <lintuxicated@yahoo.ca>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [2.6.7] Ehci controller interrupts like crazy on nforce2
Date: 10 Jul 2004 22:40:50 -0400 [thread overview]
Message-ID: <1089513649.32038.55.camel@dhcppc2> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FFA43@hdsmsx403.hd.intel.com>
On Thu, 2004-07-08 at 21:16, Jonathan Filiatrault wrote:
> Here it is: another nforce2 hardware bug. The ehci controller seems to
> send a massive number of interrupts to the kernel (264379 per second).
> This uses about 5 to 10% of the cpu. This shows up in top in the
> "hi"(hard interrupts) indicator. Nothing unusual shows up in the
> kernel
> log. My system has an Asus A7N8X Nforce2 Board with an Athlon XP 2800+
> mounted on it.
>
> [joe@omega3:~]$ cat /proc/interrupts ; sleep 1; cat /proc/interrupts
> CPU0
> 0: 583513 XT-PIC timer
Please boot with "acpi_skip_timer_override" to fix your IRQ0.
Yes, this workaround should be invoked automatically for you.
No, it probably will not help your EHCI problem.
-Len
> 1: 1279 IO-APIC-edge i8042
> 7: 137293 IO-APIC-edge parport0
> 8: 0 IO-APIC-edge rtc
> 9: 0 IO-APIC-level acpi
> 14: 41463 IO-APIC-edge ide0
> 15: 23 IO-APIC-edge ide1
> 17: 9 IO-APIC-level EMU10K1
> 18: 18584 IO-APIC-level eth0
> 20: 121541873 IO-APIC-level ehci_hcd
> 21: 0 IO-APIC-level ohci_hcd
> 22: 0 IO-APIC-level ohci_hcd
> NMI: 0
> LOC: 583348
> ERR: 0
> MIS: 0
> CPU0
next parent reply other threads:[~2004-07-11 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FFA43@hdsmsx403.hd.intel.com>
2004-07-11 2:40 ` Len Brown [this message]
2004-07-09 1:16 [2.6.7] Ehci controller interrupts like crazy on nforce2 Jonathan Filiatrault
2004-07-09 3:10 ` Kalin KOZHUHAROV
2004-07-11 12:09 ` Daniel Schmitt
2004-07-11 15:28 ` Jonathan Filiatrault
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=1089513649.32038.55.camel@dhcppc2 \
--to=len.brown@intel.com \
--cc=lintuxicated@yahoo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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