From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Greg KH" <greg@kroah.com>
Cc: "Gu, Mingkun" <Mingkun.Gu@gtech.com>, linux-kernel@vger.kernel.org
Subject: Re: Help: undesired 10 seconds delay in creating USB devices
Date: Thu, 23 Oct 2008 21:22:39 +0200 [thread overview]
Message-ID: <ac3eb2510810231222t4fe0f8bel2abd83e77b8471b7@mail.gmail.com> (raw)
In-Reply-To: <20081023161355.GA8171@kroah.com>
On Thu, Oct 23, 2008 at 18:13, Greg KH <greg@kroah.com> wrote:
> On Thu, Oct 23, 2008 at 01:11:00PM -0300, Gu, Mingkun wrote:
>> [MKGU>] My device driver name is "usbled". Our USB device has
>> VendorID=11b4. After I unplugged the USB cable connecting to this device
>> and kept the device driver "usbled" remaining loaded, I plugged in the
>> USB cable back to the system again. I could see the device information
>> retrieved from /proc/bus/usb/devices immediately but the device name
>> /dev/usbled0 was seen after near 10 seconds.
>
> That sounds like a udev script issue, not a kernel issue, correct?
>
>> > If you run 'udevadm monitor', does it show a 10 second delay?
>>
>> [MKGU>] I don't have the program 'udevadm' on my system.
>
> Do you have the program 'udevmonitor'? I suggest trying that.
2.6.21.7 (man, these silly numbers, no idea why people want to keep
them :)) should not be affected, as far as I know, but recent kernels
might need a one-line fix to a (broken) udev rule, no to delay
handling of some scsi devices, and wait at the wrong device for a
sysfs file which will never appear. You can try commenting out a rule
in /etc/udev/rules.d/*.rules, which has WAIT_FOR_SYSFS="ioerr_cnt" or
similar.
Kay
next prev parent reply other threads:[~2008-10-23 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32C88E5279F5DD46B7237443CD61E67901E455B9@cspmail02.gtk.gtech.com>
2008-10-23 15:22 ` Greg KH
[not found] ` <32C88E5279F5DD46B7237443CD61E67901E455BA@cspmail02.gtk.gtech.com>
2008-10-23 16:13 ` Greg KH
2008-10-23 19:22 ` Kay Sievers [this message]
[not found] ` <32C88E5279F5DD46B7237443CD61E67901E455BB@cspmail02.gtk.gtech.com>
2008-10-23 19:36 ` Greg KH
2008-10-23 19:49 ` Kay Sievers
[not found] ` <32C88E5279F5DD46B7237443CD61E67901E455BC@cspmail02.gtk.gtech.com>
2008-10-23 20:30 ` Kay Sievers
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=ac3eb2510810231222t4fe0f8bel2abd83e77b8471b7@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=Mingkun.Gu@gtech.com \
--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
all inboxes | Powered by JetHome®