From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: timeout udevd too hort
Date: Thu, 01 Apr 2004 01:07:26 +0000 [thread overview]
Message-ID: <20040401010726.GC13247@vrfy.org> (raw)
Bahh, I thought we introduced a bug in udevd with the recent changes,
but it seems I have a really slow device here.
We currently have a event timeout of 5 seconds to wait for a missing
event. I can catch it by activating my Thinkpad's builtin bluetooth
hardware. Sometimes the kernel needs 6 seconds to submit all the
hotplug events for this device.
Should we increase it to 10 seconds?
thanks,
Kay
device:
Bus 001 Device 004: ID 0aec:3260 Neodio Technologies Corp.
udevdsend log:
Apr 1 02:54:08 pim udevsend[12119]: main: version 023_bk
Apr 1 02:54:08 pim udevsend[12119]: main: subsystem = 'tty'
Apr 1 02:54:08 pim udevsend[12119]: main: DEVPATH = '/class/tty/ttyUB0'
Apr 1 02:54:08 pim udevsend[12119]: main: ACTION = 'remove'
Apr 1 02:54:08 pim udevsend[12119]: main: SEQNUM = '340'
Apr 1 02:54:08 pim udevsend[12120]: main: version 023_bk
Apr 1 02:54:08 pim udevsend[12120]: main: subsystem = 'usb'
Apr 1 02:54:08 pim udevsend[12120]: main: DEVPATH = '/devices/pci0000:00/0000:00:1d.2/usb4/4-1'
Apr 1 02:54:08 pim udevsend[12120]: main: ACTION = 'remove'
Apr 1 02:54:08 pim udevsend[12120]: main: SEQNUM = '344'
Apr 1 02:54:09 pim udevsend[12133]: main: version 023_bk
Apr 1 02:54:09 pim udevsend[12133]: main: subsystem = 'usb'
Apr 1 02:54:09 pim udevsend[12133]: main: DEVPATH = '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1'
Apr 1 02:54:09 pim udevsend[12133]: main: ACTION = 'remove'
Apr 1 02:54:09 pim udevsend[12133]: main: SEQNUM = '342'
Apr 1 02:54:10 pim udevsend[12136]: main: version 023_bk
Apr 1 02:54:10 pim udevsend[12136]: main: subsystem = 'usb'
Apr 1 02:54:10 pim udevsend[12136]: main: DEVPATH = '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.2'
Apr 1 02:54:10 pim udevsend[12136]: main: ACTION = 'remove'
Apr 1 02:54:10 pim udevsend[12136]: main: SEQNUM = '343'
Apr 1 02:54:13 pim udevsend[12141]: main: version 023_bk
Apr 1 02:54:13 pim udevsend[12141]: main: subsystem = 'usb'
Apr 1 02:54:13 pim udevsend[12141]: main: DEVPATH = '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0'
Apr 1 02:54:13 pim udevsend[12141]: main: ACTION = 'remove'
Apr 1 02:54:13 pim udevsend[12141]: main: SEQNUM = '341'
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-04-01 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 1:07 Kay Sievers [this message]
2004-04-01 6:40 ` timeout udevd too hort Greg KH
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=20040401010726.GC13247@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).