From: Len Brown <len.brown@intel.com>
To: "Christian Kröner" <christian.kroener@tu-harburg.de>
Cc: linux-kernel@vger.kernel.org, Jamie Lokier <jamie@shareable.org>,
Allen Martin <AMartin@nvidia.com>,
ross@datscreative.com.au,
Linux-Nforce-Bugs <Linux-Nforce-Bugs@exchange.nvidia.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: IO-APIC on nforce2 [PATCH]
Date: 22 Apr 2004 11:27:40 -0400 [thread overview]
Message-ID: <1082647660.16337.243.camel@dhcppc4> (raw)
In-Reply-To: <200404221553.51585.christian.kroener@tu-harburg.de>
On Thu, 2004-04-22 at 09:53, Christian Kröner wrote:
> since its becoming fancy to post dmidecode output
Thanks. BTW. sending the dmidecode directly to me should be sufficient
should you have need to do so again.
> another thing i recently noticed (running 2.6.6-rc2-mm1
> now) is that the last XT-PIC interrupt is gone now. i had cascade on
> irq2
> routed as XT-PIC before, now cascade (whatever it is) doesnt exist
> anymore ;).
Yes, this is normal on ACPI+IOAPIC configs going forward
details here: http://bugzilla.kernel.org/show_bug.cgi?id=2564
> /proc/interrupts now:
>
> 0: 32184529 IO-APIC-edge timer
> 1: 1741 IO-APIC-edge i8042
> 7: 0 IO-APIC-edge parport0
> 8: 4 IO-APIC-edge rtc
> 9: 0 IO-APIC-level acpi
> 12: 9229 IO-APIC-edge i8042
> 14: 107111 IO-APIC-edge ide0
> 15: 92 IO-APIC-edge ide1
> 16: 3138 IO-APIC-level ide2, saa7134[0]
> 17: 153 IO-APIC-level CMI8738
> 19: 2732391 IO-APIC-level nvidia
> 20: 4315754 IO-APIC-level ohci_hcd, eth0
> 21: 1167427697 IO-APIC-level ehci_hcd
> 22: 79 IO-APIC-level ohci_hcd
> another thing that bugs me a little (a little offtopic here maybe), is
> the
> irq21 of ehci_hcd seems to get hit about twice as often as the timer
> irq
> although im not at all using USB... any suggestions? maybe i start a
> second
> thread on this one...
Better yet, file a bug and we'll look at your ehci interrupt issue in
detail.
thanks,
-Len
How to file a bug against ACPI:
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
For failure and success case, please attach
1. dmesg -s64000, or serial console using "debug" on cmdline.
(increase CONFIG_LOG_BUF_SHIFT if it doesn't get back to beginning)
2. /proc/interrupts
3. lspci -v
Please attach the output from acpidmp, available in /usr/sbin/, or in
pmtools:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
next prev parent reply other threads:[~2004-04-22 15:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 18:33 IO-APIC on nforce2 [PATCH] Allen Martin
2004-04-15 19:20 ` Craig Bradney
2004-04-15 19:50 ` Len Brown
2004-04-16 8:27 ` Jamie Lokier
2004-04-22 4:00 ` Len Brown
2004-04-22 13:22 ` Maciej W. Rozycki
2004-04-22 13:53 ` Christian Kröner
2004-04-22 15:27 ` Len Brown [this message]
2004-04-22 15:40 ` Maciej W. Rozycki
2004-04-22 16:15 ` Christian Kröner
-- strict thread matches above, loose matches on Subject: below --
2004-04-23 1:23 Allen Martin
2004-04-23 15:39 ` Maciej W. Rozycki
2004-04-16 16:41 Allen Martin
2004-04-14 21:01 Christian Kröner
2004-04-15 0:35 ` Peter Clifton
2004-04-15 0:29 ` Craig Bradney
2004-04-15 0:41 ` Ross Dickson
2004-04-13 1:17 IO-APIC on nforce2 Ross Dickson
2004-04-13 5:08 ` Len Brown
2004-04-13 7:03 ` Ross Dickson
2004-04-14 1:02 ` IO-APIC on nforce2 [PATCH] Len Brown
2004-04-14 5:02 ` Ross Dickson
2004-04-14 6:30 ` Jamie Lokier
2004-04-14 10:37 ` Maciej W. Rozycki
2004-04-15 19:28 ` Len Brown
2004-04-14 19:57 ` Christian Kröner
2004-04-15 0:17 ` Len Brown
2004-04-15 1:48 ` Ross Dickson
2004-04-15 17:09 ` Christian Kröner
2004-04-15 15:21 ` Zwane Mwaikambo
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=1082647660.16337.243.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=AMartin@nvidia.com \
--cc=Linux-Nforce-Bugs@exchange.nvidia.com \
--cc=christian.kroener@tu-harburg.de \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ross@datscreative.com.au \
/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