public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: usb broken in 2.5?
Date: Tue, 14 Jan 2003 03:44:35 +0100	[thread overview]
Message-ID: <20030114024435.GA1293@fefe.de> (raw)

In 2.5.57 USB does not work.  The mainboard devices are still detected,
and apparently also the USB devices are found, but then the USB code
tries to remap them and fails.  It tries again with 1.5 Mb/s and fails
again.

> usb_control/bulk_msg: timeout
> usb.c: USB device not accepting new address=3 (error=-110)

The same problem also happens with the WOLK kernel patch, which appears
to also include a newer version of the USB code.

This is an excerpt from /proc/pci:

  Bus  0, device  16, function  0:
    USB Controller: VIA Technologies, Inc. USB (rev 128).
      IRQ 21.
      Master Capable.  Latency=32.
      I/O at 0xdc00 [0xdc1f].
  Bus  0, device  16, function  1:
    USB Controller: VIA Technologies, Inc. USB (#2) (rev 128).
      IRQ 21.
      Master Capable.  Latency=32.
      I/O at 0xe000 [0xe01f].
  Bus  0, device  16, function  2:
    USB Controller: VIA Technologies, Inc. USB (#3) (rev 128).
      IRQ 21.
      Master Capable.  Latency=32.
      I/O at 0xe400 [0xe41f].
  Bus  0, device  16, function  3:
    USB Controller: VIA Technologies, Inc. USB 2.0 (rev 130).
      IRQ 19.
      Master Capable.  Latency=32.
      Non-prefetchable 32 bit memory at 0xe6033000 [0xe60330ff].

Any ideas?  On 2.5 and WOLK the kernel also says that no IRQ is know and
that it is using ACPI to route the IRQs.

Felix

         reply	other threads:[~2003-01-14  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  2:52 "PCI BIOS passed nonexistant PCI bus 0" Felix von Leitner
2003-01-14  2:44 ` Felix von Leitner [this message]
2003-01-14  4:09   ` usb broken in 2.5? Felix von Leitner
2003-01-14 14:55   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-01-14 19:35 Adam J. Richter

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=20030114024435.GA1293@fefe.de \
    --to=felix-linuxkernel@fefe.de \
    --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