From: Soeren Sonnenburg <kernel@nn7.de>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: usb devices get redetected all the time in 2.6.0-test{7,9}
Date: Thu, 30 Oct 2003 07:27:06 +0100 [thread overview]
Message-ID: <1067495225.1529.14.camel@localhost> (raw)
In-Reply-To: <20031029200112.GB4434@kroah.com>
On Wed, 2003-10-29 at 21:01, Greg KH wrote:
> On Wed, Oct 29, 2003 at 08:15:26AM +0100, Soeren Sonnenburg wrote:
> > Hi.
> >
> > When I attach a camera to a 2.4. based machine hotplug starts up some
> > script to download images of that camera and fine thats it.
> >
> > In 2.6.0-testX I see kernel messages like:
> >
> > hub 2-0:1.0: new USB device on port 1, assigned address 2
> > bus usb: add device 2-1
> > bound device '2-1' to driver 'usb'
> > bus usb: add device 2-1:1.0
> > bus usb: remove device 2-1:1.0
> > bus usb: add device 2-1:1.0
> > bus usb: remove device 2-1:1.0
> > bus usb: add device 2-1:1.0
> > bus usb: remove device 2-1:1.0
> > bus usb: add device 2-1:1.0
> > [...]
> >
> > and several of these hotplug scripts get started... Is this a wanted
> > behaviour and something has to be fixed in userspace or is it a kernel
> > bug ?
>
> Does this settle down after a bit, or does the add/remove stuff keep
> going on for a while?
I realized that when I disable the hotplug script the camera is detected
only once (as it should).
The script fetches the directory listing off the camera... thus is
probably opening+closing the device once. So I wonder whether this could
somehow trigger an usb disconnect on close() making the usb driver to
redetect the device ?!
> Can you enable CONFIG_USB_DEBUG and see if you get any more information
> in the kernel debug log as to why this is happening?
If still needed I will do.
Soeren
prev parent reply other threads:[~2003-10-30 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 7:15 usb devices get redetected all the time in 2.6.0-test{7,9} Soeren Sonnenburg
2003-10-29 20:01 ` Greg KH
2003-10-30 6:27 ` Soeren Sonnenburg [this message]
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=1067495225.1529.14.camel@localhost \
--to=kernel@nn7.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 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.