linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Michel Bouissou <michel@bouissou.net>
Cc: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>,
	<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 15:43:49 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0507111539280.6399-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <200507112133.07471@totor.bouissou.net>

On Mon, 11 Jul 2005, Michel Bouissou wrote:

> 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 ;-)

That's what I was talking about.  BIOS support for keyboard and mouse is
called "Legacy" support, because it emulates plain old non-USB AT-type 
devices.  I bet if you turned off the "Enable USB mouse support" option 
then everything would work.

> 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 !!
> 
> 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 !
> 
> 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 !

You're welcome.

> (Kernel 2.4 was working plain good without such a boot option, I didn't know 
> it existed...)

A lot has changed since 2.4... not always for the better!

Alan Stern


  reply	other threads:[~2005-07-11 19:45 UTC|newest]

Thread overview: 25+ 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 [this message]
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
2005-07-12 21:37                                 ` Alan Stern
2005-07-12 22:01                                   ` Michel Bouissou
2005-07-11 19:52 [SOLVED ??] " Protasevich, Natalie
2005-07-11 20:13 ` Michel Bouissou
2005-07-12  7:24 ` Alexander Fieroch

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=Pine.LNX.4.44L0.0507111539280.6399-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=Natalie.Protasevich@UNISYS.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@bouissou.net \
    --cc=mingo@redhat.com \
    /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).