From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Gu, Mingkun" <Mingkun.Gu@gtech.com>
Cc: linux-kernel@vger.kernel.org, "Greg KH" <greg@kroah.com>
Subject: Re: Help: undesired 10 seconds delay in creating USB devices
Date: Thu, 23 Oct 2008 22:30:27 +0200 [thread overview]
Message-ID: <ac3eb2510810231330g791f4f35uf43efddaa3aeed@mail.gmail.com> (raw)
In-Reply-To: <32C88E5279F5DD46B7237443CD61E67901E455BC@cspmail02.gtk.gtech.com>
On Thu, Oct 23, 2008 at 22:04, Gu, Mingkun <Mingkun.Gu@gtech.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?
>> >> >
>> >>
>> >> [MKGU>] Yes. It seems related to udev.
>> >>
>> >> > > > 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.
>> >> >
>> >>
>> >> [MKGU>] Yes, I ran "udevmonitor" and captured the following
> messages:
>> >> UEVENT[1224775488.005799] remove /class/usb/usbled0 (usb)
>> >> UEVENT[1224775488.007901] remove /class/usb (class)
>> >> UEVENT[1224775488.011992] remove
>> >> /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0 (usb)
>> >> UEVENT[1224775488.019706] remove
>> >> /devices/pci0000:00/0000:00:1d.1/usb3/3-1 (usb)
>> >> UEVENT[1224775496.176576] add
>> >> /devices/pci0000:00/0000:00:1d.1/usb3/3-1 (usb)
>> >> UEVENT[1224775496.181732] add
>> >> /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0 (usb)
>> >> UEVENT[1224775496.186031] add /class/usb/usbled0 (usb)
>> >
>> > Then I suggest filing a bug with your distro to get this looked at,
> as
>> > they are responsible for the udev scripts here, nothing wrong with
> your
>> > kernel :)
>>
>> You don't have UDEV[...] events here? The interesting output of
>> udevmonitor would the timing difference between the kernel events and
>> the udev events, but you completely miss the udev ones.
>>
>
> [MKGU>] Yes, I don't have UDEV[...] events captured. That's all what I
> captured. I was using "udevmonitor" in the udev-113 package.
>> What version of udev, and which distro is that?
>
> [MKGU>] I am not sure what version of my udev in use on the system. How
> can I check its version? I am using kernel 2.6.21.7-cfs-v22.
/sbin/udevd -V
or
udevinfo -V
> [MKGU>] In reply to your question in another email, I did not find the
> line containing the string WAIT_FOR_SYSFS= in all *.rules files under
> /etc/udev/ and /etc/udev/rules.d/.
Ok, sounds good. The default WAIT_FOR_SYSFS timeout is 10 seconds, so
that would be the usual suspect.
Kay
prev parent reply other threads:[~2008-10-23 20:30 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
[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 [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=ac3eb2510810231330g791f4f35uf43efddaa3aeed@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®