From: Michel Bouissou <michel@bouissou.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble
Date: Tue, 12 Jul 2005 22:40:53 +0200 [thread overview]
Message-ID: <200507122240.53390@totor.bouissou.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0507121440020.6281-100000@iolanthe.rowland.org>
Le Mardi 12 Juillet 2005 20:57, Alan Stern a écrit :
> On the other hand, _something_ was generating an interrupt request that
> got mapped to IRQ 21 by the hardware. And these requests do seem to be
> associated with USB activity. Maybe the EHCI controller is responsible?
> One of your postings showed both uhci_hcd:usb2 and ehci_hcd:usb4 mapped to
> IRQ 11. That could indicate a shared signal line, which is currently
> being mapped incorrectly.
>
> You can test this a couple of ways. The easiest is to rmmod ehci_hcd, or
> prevent it from being loaded in the first place, by renaming
> /lib/modules/.../drivers/usb/host/ehci_hcd.ko so that modprobe can't find
> it. Also your BIOS may offer the option of disabling USB 2.0 support
> entirely. Try doing this under the kernel that has the test patch
> installed.
I've tested as you suggest :
- Disabled USB 2.0 in BIOS
- Renamed ehci_hcd.ko so that modprobe can't find it
- Booted the test-patched kernel with same options as previously, MOUSE
UNPLUGGED.
- After boot "cat /proc/interrupts" shows "0" count for IRQ 21
- Nothing special isn't logged anymore in dmesg or /var/log/messages.
- Plugging / unplugging the mouse or other devices doesn't cause anything
visible to happen. Nothing gets logged, IRQ 21 counter stays at 0. I could as
well not have done it ;-)
> Without ehci_hcd loaded, the EHCI controller should not generate any
> interrupt requests. If your problem then goes away, and plugging or
> unplugging the mouse doesn't cause anything unusual to happen, that will
> be a pretty clear indication.
Well, so that's a pretty clear indication, but surely clearer to you than to
me ;-)
So, what's up, doc ? ;-))
--
Michel Bouissou <michel@bouissou.net> OpenPGP ID 0xDDE8AC6E
next prev parent reply other threads:[~2005-07-12 20:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 18:50 Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble Protasevich, Natalie
2005-07-11 9:06 ` Michel Bouissou
2005-07-11 18:36 ` Alan Stern
2005-07-11 19:33 ` [SOLVED ??] " Michel Bouissou
2005-07-11 19:43 ` Alan Stern
2005-07-11 20:02 ` Michel Bouissou
2005-07-11 20:16 ` Alan Stern
2005-07-11 20:46 ` Michel Bouissou
2005-07-11 20:58 ` Michel Bouissou
2005-07-11 21:21 ` [NOT solved] " Michel Bouissou
2005-07-11 21:21 ` [SOLVED ??] " Alan Stern
2005-07-11 21:34 ` Michel Bouissou
2005-07-12 1:54 ` Alan Stern
2005-07-12 7:54 ` Michel Bouissou
2005-07-12 14:12 ` Alan Stern
2005-07-12 17:03 ` Michel Bouissou
2005-07-12 18:15 ` Alan Stern
2005-07-12 18:16 ` Michel Bouissou
2005-07-12 18:57 ` Alan Stern
2005-07-12 20:40 ` Michel Bouissou [this message]
2005-07-12 21:37 ` Alan Stern
2005-07-12 22:01 ` Michel Bouissou
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 23:16 Protasevich, Natalie
2005-07-13 6:46 ` Michel Bouissou
2005-07-12 21:02 Protasevich, Natalie
2005-07-10 8:11 Michel Bouissou
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=200507122240.53390@totor.bouissou.net \
--to=michel@bouissou.net \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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