All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils@kernelconcepts.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.17[16] USB problem
Date: Wed, 13 Feb 2002 19:16:51 +0100	[thread overview]
Message-ID: <20020213191651.5c3dfd5e.nils@kernelconcepts.de> (raw)

Hi all!
I recently see a strange USB problem which I find in 2.4.17 and 2.4.16 and
maybe even earlier.
What happens is that a special device attached via a USB HUB is not
detected anymore, specifically usb.c claims that it cannot set the new
address.
The strange thing is:
- It worked with that device (Brainboxes Bluetooth USB dongle) with
earlier kernels.
- The device works when directly connected (and not via extra HUB).
- hub.c tells me that it HAS successfully assigned a new address to that
device!
- And above all, only that special device is affected. All other devices I
have to test (USB mouse and USB webcam) work perfectly.

The error messages also show a strange behaviour of the Linux USB system:
Why does hub.c set the address and then usb.c tries the same again?

I am sure not I am not suffering the earlier mentioned "device not
accepting new address" problem due to interrupt routing problems (since
all other devices work and the machine I am using is a UP notebook).
And I am also sure that this device used to work connected to the HUB with
earlier USB releases.

So please if anyone has new insights on this problem please CC me since I
am not subscribed to lkml...
Many thanks in advance!
CU
  nils faerber

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--

             reply	other threads:[~2002-02-13 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 18:16 Nils Faerber [this message]
2002-02-13 19:02 ` 2.4.17[16] USB problem Greg KH
2002-02-13 22:41 ` Martin Diehl

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=20020213191651.5c3dfd5e.nils@kernelconcepts.de \
    --to=nils@kernelconcepts.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.