From: Nils Faerber <nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
To: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Interrupt routing problem
Date: Sun, 04 Jan 2004 17:43:57 +0100 [thread overview]
Message-ID: <1073234635.985.6.camel@localhost> (raw)
Hi!
I think my current ACPI enabled 2.4.23 kernel is doing something IMHO
not so clever concerning interrupt routing:
CPU0
0: 57158 XT-PIC timer
1: 2339 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 2707 XT-PIC usb-uhci, Ricoh Co Ltd RL5c476 II
7: 3 XT-PIC parport0
8: 194573 XT-PIC rtc
9: 12214 XT-PIC acpi, ohci1394, usb-uhci, eth0, Texas
Instruments PCI1410 PC card Cardbus Controller, orinoco_cs
11: 61791 XT-PIC Ricoh Co Ltd RL5c476 II (#2), Intel
ICH3
12: 134 XT-PIC PS/2 Mouse
14: 38295 XT-PIC ide0
15: 6607 XT-PIC ide1
As you can see most devices are routed through IRQ9. I even think that
this is not only ugly but even causes problems. For example I see
strange phenomenons concerning USB with this setup, i.e. devices
suddenly getting disconnected and reconnected again, HUBs beeing
disabled altogether, ports being disabled and so on; and yes, using uhci
instead of usb-uhci does not help any.
So my question is if I can "help" my kernel somehow to distribute the
IRQs in a more clever way.
I can remember that there were some kernel commandline options about
ACPI and PCI interrupt routing (like pci=noacpi or acpi=nopci). Are
those still valid? Would they help?
Oh, BTW, setup summary
Linux kernel 2.4.23 + swsusp
running on
Asus notebook L3800C, latest BIOS V1.21
Thanks in advance!
CU
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen D1 : +49-170-2729106
--
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next reply other threads:[~2004-01-04 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 16:43 Nils Faerber [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 2:17 Interrupt routing problem Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C75-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-06 4:10 ` Len Brown
[not found] ` <1073362251.2419.21.camel-D2Zvc0uNKG8@public.gmane.org>
2004-01-06 8:47 ` Karol Kozimor
2004-01-07 8:50 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C83-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-07 9:05 ` Karol Kozimor
[not found] ` <20040107090531.GA32086-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-07 15:34 ` Karol Kozimor
2004-01-12 5:28 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CA9-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13 8:26 ` Karol Kozimor
2004-01-13 8:50 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CC3-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13 9:00 ` Karol Kozimor
[not found] ` <20040113090003.GB3599-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-15 10:41 ` Nils Faerber
2004-01-13 9:08 Yu, Luming
2004-01-18 4:14 Yu, Luming
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=1073234635.985.6.camel@localhost \
--to=nils.faerber-t93ne7xhvje5bsectf/tx7nah6klmebb@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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