From: "Adam J. Richter" <adam@yggdrasil.com>
To: felix-linuxkernel@fefe.de, linux-kernel@vger.kernel.org
Cc: greg@kroah.com
Subject: Re: usb broken in 2.5?
Date: Tue, 14 Jan 2003 11:35:42 -0800 [thread overview]
Message-ID: <200301141935.LAA00806@adam.yggdrasil.com> (raw)
Greg KH wrote:
>On Tue, Jan 14, 2003 at 03:44:35AM +0100, Felix von Leitner wrote:
>> In 2.5.57 USB does not work. [...]
>This sounds like the old iterrupt routing problem that ACPI causes at
>times, and not a USB problem (the interrupts aren't getting to the
>controller, nothing the USB controller can do about that...)
In case it helps you to know this, I'm looking into a similar
problem in 2.5.57-58 which may be related to what you (Felix) are
reporting.
For some reason that I haven't figured out, USB keyboard and
mouse that are recognized in 2.5.56 are not recognized by 2.5.57 or
2.5.58, even though lsusb sees them. This is the case on the two
different systems that I tried (with a different keyboard and
a different mouse).
There were no changes to drivers/acpi between 2.5.56 and
2.5.57, and booting with acpi=off does not eliminate this problem.
There were few changes to usb between 2.5.56 and 2.5.57. So, I
suspect that USB no longer working is a side-effect of some other
change.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-01-14 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 19:35 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 2:52 "PCI BIOS passed nonexistant PCI bus 0" Felix von Leitner
2003-01-14 2:44 ` usb broken in 2.5? Felix von Leitner
2003-01-14 4:09 ` Felix von Leitner
2003-01-14 14:55 ` Greg KH
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=200301141935.LAA00806@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=felix-linuxkernel@fefe.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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).