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: [NOT solved] Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble
Date: Mon, 11 Jul 2005 23:21:53 +0200 [thread overview]
Message-ID: <200507112321.53413@totor.bouissou.net> (raw)
In-Reply-To: <200507112258.53906@totor.bouissou.net>
Le Lundi 11 Juillet 2005 22:58, Michel Bouissou a écrit :
>
> Oh no :-(
Well, I give up for tonight :-(
This time I rebooted with the mouse disabled in BIOS, with the usb-handoff
option, with the scanner unplugged... And it went wrong simply by itself.
"irq 21: nobody cared!"
The only thing I'm sure about is that there is something either with UP
IO-APIC support, or with the uhci_hcd module.
When both are combined, as you can see, this is completely unstable. One time
it works, one time it doesn't.
But if I use a kernel compiled without UP IO-APIC, or if I boot an
IO-APIC-capable kernel with the "noapic" option, then the problem is gone,
and it is stable (really, this time).
But of course, I don't have no IO-APIC anymore...
[root@totor etc]# cat /proc/interrupts
CPU0
0: 423482 XT-PIC timer
1: 1083 XT-PIC i8042
2: 0 XT-PIC cascade
4: 1106 XT-PIC serial
7: 1543 XT-PIC parport0
10: 3527 XT-PIC uhci_hcd:usb3, eth0, eth1, VIA8233
11: 24934 XT-PIC ide0, ide1, ide2, ide3, uhci_hcd:usb2,
ehci_hcd:usb4
12: 13809 XT-PIC uhci_hcd:usb1, nvidia
14: 3245 XT-PIC ide4
15: 3254 XT-PIC ide5
NMI: 0
LOC: 423403
ERR: 270
Cheers.
--
Michel Bouissou <michel@bouissou.net> OpenPGP ID 0xDDE8AC6E
next prev parent reply other threads:[~2005-07-11 21:26 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 ` Michel Bouissou [this message]
2005-07-11 21:21 ` 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 21:25 [NOT solved] " Protasevich, Natalie
2005-07-11 22:01 ` Michel Bouissou
2005-07-11 23:41 Protasevich, Natalie
2005-07-12 7:52 ` 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=200507112321.53413@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;
as well as URLs for NNTP newsgroup(s).