From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev fails to add/remove devices
Date: Fri, 26 Mar 2004 21:57:50 +0000 [thread overview]
Message-ID: <20040326215750.GB857@vrfy.org> (raw)
In-Reply-To: <20040326180855.37deecab.elfy666@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Fri, Mar 26, 2004 at 10:28:06PM +0100, Oliver Paschke wrote:
> Applied the patch. This is what my syslog reads:
>
> Mar 26 22:14:24 pandora udevsend[1157]: main: version 023
> Mar 26 22:14:24 pandora udevsend[1157]: main: subsystem = 'test'
> Mar 26 22:14:24 pandora udevsend[1157]: main: DEVPATH = '/test'
> Mar 26 22:14:24 pandora udevsend[1157]: main: ACTION = 'add'
> Mar 26 22:14:24 pandora udevsend[1157]: main: SEQNUM = '1000000'
> Mar 26 22:14:24 pandora udevd[227]: msg_queue_insert: queued message seq 1000000
> Mar 26 22:14:24 pandora udevd[227]: msg_queue_manager: msg queue manager, next expected is 0
> Mar 26 22:14:24 pandora udevd[227]: msg_queue_manager: xxx msg age is -3484
> Mar 26 22:14:24 pandora udevd[227]: msg_dump_queue: sequence 116 in queue
> [...]
> Mar 26 22:14:24 pandora udevd[227]: msg_dump_queue: sequence 153 in queue
> Mar 26 22:14:24 pandora udevd[227]: msg_dump_queue: sequence 1000000 in queue
> Mar 26 22:14:24 pandora udevd[227]: msg_queue_manager: next event expires in 3489 seconds
> Mar 26 22:14:24 pandora udevd[227]: msg_queue_manager: xxx itimer seconds is 3489
>
> Negative message age... ?
> Could all this result from a possible bug in my glibc-3.3?
Hmm, don't know. I can't reproduce it.
Now I start to guess :)
Could you please try this.
thanks,
Kay
[-- Attachment #2: udevd.patch --]
[-- Type: text/plain, Size: 550 bytes --]
===== udevd.c 1.24 vs edited =====
--- 1.24/udevd.c Wed Mar 17 23:40:12 2004
+++ edited/udevd.c Fri Mar 26 22:29:41 2004
@@ -104,11 +104,12 @@
list_for_each_entry(loop_msg, &msg_list, list)
if (loop_msg->seqnum > msg->seqnum)
break;
- list_add_tail(&msg->list, &loop_msg->list);
- dbg("queued message seq %d", msg->seqnum);
/* store timestamp of queuing */
msg->queue_time = time(NULL);
+
+ list_add_tail(&msg->list, &loop_msg->list);
+ dbg("queued message seq %d", msg->seqnum);
/* run msg queue manager */
msg_queue_manager();
next prev parent reply other threads:[~2004-03-26 21:57 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
2004-03-26 20:42 ` Oliver Paschke
2004-03-26 21:28 ` Oliver Paschke
2004-03-26 21:57 ` Kay Sievers [this message]
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=20040326215750.GB857@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).