From: Oliver Paschke <elfy666@gmx.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev fails to add/remove devices
Date: Fri, 26 Mar 2004 20:13:39 +0000 [thread overview]
Message-ID: <20040326211339.602d8062.elfy666@gmx.de> (raw)
In-Reply-To: <20040326180855.37deecab.elfy666@gmx.de>
On Fri, 26 Mar 2004 18:39:58 +0100
Kay Sievers <kay.sievers@vrfy.org> wrote:
> What says your syslog after doing this as root?
These are my results for the manual send calls:
ACTIONd DEVPATH=/test /sbin/udevsend test
Mar 26 20:40:03 pandora udevsend[1233]: main: version 023
Mar 26 20:40:03 pandora udevsend[1233]: main: subsystem = 'test'
Mar 26 20:40:03 pandora udevsend[1233]: main: DEVPATH = '/test'
Mar 26 20:40:03 pandora udevsend[1233]: main: ACTION = 'add'
Mar 26 20:40:03 pandora udevsend[1233]: main: SEQNUM = '-1'
Mar 26 20:40:03 pandora udev[1234]: get_dirs: sysfs_path='/sys'
Mar 26 20:40:03 pandora udev[1234]: parse_config_file: reading '/etc/udev/udev.conf' as config file
Mar 26 20:40:03 pandora udevd[226]: udev_run: => exec seq -1 [1234] working at '/test'
Mar 26 20:40:03 pandora udevd[226]: exec_queue_manager: moved seq -1 to running list
Mar 26 20:40:03 pandora udevd[226]: udev_done: <= exec seq -1 came back
SEQNUM\x1000000 ACTIONd DEVPATH=/test /sbin/udevsend test
Mar 26 20:40:38 pandora udevsend[1243]: main: version 023
Mar 26 20:40:38 pandora udevsend[1243]: main: subsystem = 'test'
Mar 26 20:40:38 pandora udevsend[1243]: main: DEVPATH = '/test'
Mar 26 20:40:38 pandora udevsend[1243]: main: ACTION = 'add'
Mar 26 20:40:38 pandora udevsend[1243]: main: SEQNUM = '1000000'
Mar 26 20:40:38 pandora udevd[226]: msg_queue_insert: queued message seq 1000000
Mar 26 20:40:38 pandora udevd[226]: msg_queue_manager: msg queue manager, next expected is 0
Mar 26 20:40:38 pandora udevd[226]: msg_dump_queue: sequence 116 in queue
[...]
Mar 26 20:40:38 pandora udevd[226]: msg_dump_queue: sequence 153 in queue
Mar 26 20:40:38 pandora udevd[226]: msg_dump_queue: sequence 1000000 in queue
Mar 26 20:40:38 pandora udevd[226]: msg_queue_manager: next event expires in 3199 seconds
Seems like some problem with udevd handeling the sequence numbers..
> > Mar 26 16:53:08 pandora udevd[226]: msg_queue_manager: next event expires in 2907 seconds
> Huh, what's this 2907 seconds? Sounds a bit too much :)
This seems to be the problem with udevd queueing the event forever.
> > Mar 26 16:51:00 pandora udev[1412]: udev_add_device: udevdb_add_dev failed, but we are going to try to create the node anyway. But remove might not work properly for this device.
>
> Are you sure, that you have removed to old db after upgrading?
> Normally 'make install' should do this.
I resolved this issue by increasing the size of my tmpfs mounted /dev. The db grew too big for the 100k size limit.
thanks,
Oli
-------------------------------------------------------
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 prev parent reply other threads:[~2004-03-26 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 17:08 udev fails to add/remove devices Oliver Paschke
2004-03-26 17:39 ` Kay Sievers
2004-03-26 20:05 ` Treeve Jelbert
2004-03-26 20:13 ` Oliver Paschke [this message]
2004-03-26 20:42 ` Oliver Paschke
2004-03-26 21:28 ` Oliver Paschke
2004-03-26 21:57 ` Kay Sievers
2004-03-27 12:55 ` Treeve Jelbert
2004-03-27 19:02 ` 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=20040326211339.602d8062.elfy666@gmx.de \
--to=elfy666@gmx.de \
--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).