From: Duncan Sands <duncan.sands@wanadoo.fr>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.5.26 hotplug failure
Date: Sun, 15 Sep 2002 23:53:41 +0200 [thread overview]
Message-ID: <200209152353.41285.duncan.sands@wanadoo.fr> (raw)
In-Reply-To: <20020718183617.GI15529@kroah.com>
On Thursday 18 July 2002 20:36, Greg KH wrote:
> On Thu, Jul 18, 2002 at 09:50:42AM +0200, Duncan Sands wrote:
> > I just gave 2.5.26 a whirl. The first thing I noticed was
> > that the hotplug system didn't run the script for my usb
> > modem...
> >
> > kernel: usb.c: USB disconnect on device 2
> > kernel: hub.c: new USB device 00:0b.0-2, assigned address 4
> > kernel: usb.c: USB device 4 (vend/prod 0x6b9/0x4061) is not claimed by
> > any active driver. /etc/hotplug/usb.agent: ... no modules for USB product
> > 6b9/4061/0
> >
> > however this works just fine with 2.4.19-rc1 and 2.5.24 (i.e. only
> > difference is the change in kernel)...
>
> But that message is from the hotplug agent, right?
>
> What kind of script used to get run, and how was it run (i.e. on network
> interface registration, etc.)
>
> thanks,
>
> greg k-h
OK, I've worked out what was wrong (patch below): /proc/bus/usb was
being unmounted by the hotplug/usb.rc script. After loading a HCD, usb.rc
executes the following lines:
if [ -d /proc/bus/usb ]; then
# If we see there are no busses, we "failed" and
# can report so even if we're partially nonmodular.
COUNT=`ls /proc/bus/usb | wc -l`
if [ $COUNT -le 2 ]; then
umount /proc/bus/usb
rmmod usbcore >/dev/null 2>&1
return 1
fi
In the 2.4 kernels, /proc/bus/usb contains at least
001 devices drivers
i.e. at least three entries. However sometime during
the 2.5 kernel series the drivers file went away. So
now there are only two entries and usb.rc unmounts
/proc/bus/usb.
A simple fix is to change the test to [ $COUNT -lt 2 ];
Duncan.
--- hotplug/usb.rc.orig 2002-09-15 23:29:14.000000000 +0200
+++ hotplug/usb.rc 2002-09-15 23:29:39.000000000 +0200
@@ -149,7 +149,7 @@
# If we see there are no busses, we "failed" and
# can report so even if we're partially nonmodular.
COUNT=`ls /proc/bus/usb | wc -l`
- if [ $COUNT -le 2 ]; then
+ if [ $COUNT -lt 2 ]; then
umount /proc/bus/usb
rmmod usbcore >/dev/null 2>&1
return 1
next prev parent reply other threads:[~2002-09-15 21:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 7:50 Duncan Sands
2002-07-18 18:36 ` Greg KH
2002-07-18 19:07 ` Duncan Sands
2002-09-15 21:53 ` Duncan Sands [this message]
2002-09-18 6:52 ` Greg KH
2002-09-18 7:15 ` [linux-usb-devel] " Brad Hards
2002-09-18 16:55 ` Greg KH
2002-09-19 7:37 ` Daniel Phillips
2002-09-19 7:45 ` Daniel Phillips
2002-09-19 7:48 ` Greg KH
2002-09-19 7:55 ` Daniel Phillips
2002-09-19 16:49 ` Greg KH
2002-09-19 20:56 ` Brad Hards
2002-09-19 23:06 ` Greg KH
2002-09-20 20:42 ` [linux-usb-devel] " David Brownell
2002-09-20 23:11 ` Greg KH
2002-09-21 2:55 ` David Brownell
2002-09-21 3:31 ` Greg KH
2002-09-21 3:58 ` David Brownell
2002-09-21 5:48 ` Greg KH
2002-09-22 1:21 ` Linus Torvalds
2002-09-24 18:26 ` Patrick Mochel
2002-09-24 18:55 ` Linus Torvalds
2002-09-24 19:29 ` Greg KH
2002-09-24 22:37 ` Patrick Mochel
2002-09-20 23:22 ` Brad Hards
2002-09-20 23:36 ` Johannes Erdfelt
2002-09-21 0:11 ` Randy.Dunlap
2002-09-21 0:25 ` Brad Hards
2002-09-21 2:36 ` David Brownell
2002-09-20 23:46 ` Patrick Mochel
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=200209152353.41285.duncan.sands@wanadoo.fr \
--to=duncan.sands@wanadoo.fr \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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®