From: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
To: "Michel Bouissou" <michel@bouissou.net>,
"Alan Stern" <stern@rowland.harvard.edu>, <fieroch@web.de>
Cc: <linux-kernel@vger.kernel.org>, <mingo@redhat.com>
Subject: RE: [SOLVED ??] Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble
Date: Mon, 11 Jul 2005 14:52:40 -0500 [thread overview]
Message-ID: <19D0D50E9B1D0A40A9F0323DBFA04ACCE04C49@USRV-EXCH4.na.uis.unisys.com> (raw)
> Le Lundi 11 Juillet 2005 20:36, Alan Stern a écrit :
> > It's also possible that the UHCI controllers are generating the
> > unwanted interrupt requests. You should make sure that Legacy USB
> > Support is turned off in your BIOS settings.
>
> My motherboard both holds USB 1.1 and USB 2.0 controllers. I
> don't have a "Legacy USB Support" option in my BIOS, all my
> USB options are the following:
>
> Enable USB 1.1 controller: YES (Surely relates to my
> true USB 1.1 controller)
>
> Enable USB 2.0 controller: YES (Same for the high
> speed controller ?)
>
> Enable USB keyboard: NO
>
> Enable USB mouse support: YES (Well, I have one ;-)
>
> I didn't change anything regarding these so far.
>
> > You can also try adding the "usb-handoff" kernel parameter to your
> > boot command line.
>
> Hey !! This one looks like the MIRACLE-OPTION !!
Alexander, should you try this option? (Just in case if you haven't noticed this thread)...
> I just booted using my 2.6.12 kernel patched with Nathalie's
> patches (don't know if they help in there...) and the problem
> seems to be gone !
Michel, it would be interesting to see if you have problems with the kernel that doesn't have the fix posted in that bugzilla yet, but only has my first patch.
> Nothing complains anymore about the interrupt. I have:
>
> [root@totor etc]# cat /proc/interrupts
> CPU0
> 0: 934501 IO-APIC-edge timer
> 1: 4611 IO-APIC-edge i8042
> 2: 0 XT-PIC cascade
> 4: 2779 IO-APIC-edge serial
> 7: 3 IO-APIC-edge parport0
> 14: 7909 IO-APIC-edge ide4
> 15: 7918 IO-APIC-edge ide5
> 16: 38447 IO-APIC-level nvidia
> 18: 2982 IO-APIC-level eth0, eth1
> 19: 37041 IO-APIC-level ide0, ide1, ide2, ide3, ehci_hcd:usb4
> 21: 52036 IO-APIC-level uhci_hcd:usb1,
> uhci_hcd:usb2, uhci_hcd:usb3
> 22: 2850 IO-APIC-level VIA8233
> NMI: 0
> LOC: 934453
> ERR: 0
> MIS: 0
>
>
> ...now let's see with time if this is stable...
>
> A thousand thanks for your suggestion Alan !
>
Thank you Alan! You helped me too, since my patch has broken a couple VIA chips lately. Now I know that at least the fix works...
next reply other threads:[~2005-07-11 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 19:52 Protasevich, Natalie [this message]
2005-07-11 20:13 ` [SOLVED ??] Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble Michel Bouissou
2005-07-12 7:24 ` Alexander Fieroch
-- strict thread matches above, loose matches on Subject: below --
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 ` Alan Stern
2005-07-11 21:34 ` Michel Bouissou
2005-07-12 1:54 ` Alan Stern
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=19D0D50E9B1D0A40A9F0323DBFA04ACCE04C49@USRV-EXCH4.na.uis.unisys.com \
--to=natalie.protasevich@unisys.com \
--cc=fieroch@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@bouissou.net \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).