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: [SOLVED ??] Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble
Date: Mon, 11 Jul 2005 23:34:30 +0200 [thread overview]
Message-ID: <200507112334.30680@totor.bouissou.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0507111713320.14116-100000@iolanthe.rowland.org>
Le Lundi 11 Juillet 2005 23:21, Alan Stern a écrit :
> Don't jump to hasty conclusions. Problems like this are often caused by
> unrelated things that you wouldn't suspect at first.
I know... Been working with computers for... Uh... 25 years ?
> Getting something to work once doesn't mean the problem has been fixed.
That's so sadly right ;-)
> And you can be fooled by coincidences. (I would be surprised if that event
> above was really caused by plugging in the scanner, unless your UHCI
> hardware is broken.)
I don't believe the hardware is broken, as it's been running for more than 2
years 100% stable with a 24/7/365 uptime. And with me plugging and unplugging
USB devices...
Never had a single problem of the kind with any 2.4.x kernel. Get those
problems only with 2.6.x kernels, and, in 2.6.12, only when UP IO-APIC is
enabled (which ran perfectly good in 2.4).
So the problem is circled to 2.6 kernel, uhci_hcd and UP IO-APIC.
> One thing you might try, time-consuming though it will be, is to remove or
> disable as much hardware as possible from your system. If you can
> reliably determine that the problem occurs only when one particular piece
> of hardware is enabled, then you'll know how to proceed.
I can hardly remove my VIA chipset from the mobo, and the USB thing is in the
VIA thing ;-))
And I'm afraid I won't have the time to play that much with hardware, besides
the fact that this is supposed to be a server which usually has uptimes over
90 days rather than reboot-for-testing-the-damn-kernel-once-again ;-))
But I'm pretty sure this is no hardware problem, unless 2.6 considers "bad
hardware" what 2.4 used to consider "nice hardware"...
Cheers.
--
Michel Bouissou <michel@bouissou.net> OpenPGP ID 0xDDE8AC6E
next prev parent reply other threads:[~2005-07-11 21:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 18:50 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 [this message]
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=200507112334.30680@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
all inboxes | Powered by JetHome®