From: David Zeuthen <david@fubar.dk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev infinite loop
Date: Mon, 16 Aug 2004 20:44:50 +0000 [thread overview]
Message-ID: <1092689091.3950.28.camel@localhost.localdomain> (raw)
In-Reply-To: <411C9E97.4050707@yahoo.fr>
On Mon, 2004-08-16 at 10:43 +0200, David Zeuthen wrote:
> On Mon, 2004-08-16 at 10:12 +0200, Guillaume Chazarain wrote:
> > That's bad news, it means you cannot reproduce it :(
> > Here is a tar.bz2 containing strace logs of dbus-daemon-1 and udevd.
> > There is also a dmesg
> > output, my kernel .config, /etc/udev /sys and kernel logs.
> > I see nothing wrong in them, but hopefully you will.
> >
Guillaume: I believe I've fixed this problem in the just released hal
0.2.97, at least it works nicely with my PCMCIA card reader which showed
the same issues. I see that you are running Fedora Core development;
updated hal-0.2.97 packages should appear in rawhide soon [1].
It would be great if you can test these packages ('rpm -q hal' should
report hal-0.2.97-1 or higher) and if it fails then please report the
bug to http://bugzilla.redhat.com or the hal@freedesktop.org mailing
list. If it just works, also feel free to mail me personally; I would
appreciate it! Thanks.
> This is not an udev problem; this is caused by the fact that hal polls
> your device for media; fwiw, I've seen this with the ide-cs driver as
> well when using a PCMCIA CF card reader and I'm looking into
> blacklisting such devices or at least working around issues. Please
> state your version of hal and include the output of 'lshal' so we can
> get this resolved.
>
> To me, it seems that if you do a 'dd if=/dev/hde of=/tmp/foo bsQ2
> count\x10' then it causes a all partitions on /dev/hde to be hot
> unplugged and then hot replugged. Uhm, isn't that some kind of bug in
> the driver or what.
Hotplug folks: I'd just like to note that this problem is not exclusive
to hal at all, it even applies to mount(1) if the filesystem given is
'auto', cause then mount(1) access the device file and this will cause a
hotplug removal and then a hotplug add. Specifically, using udev
callouts to get the drive serial number or volume lanel will also cause
infinite loops.
Can anyone please confirm this is a bug in the IDE subsystem?
Thanks,
David
[1] : Alternatively download the (S)RPMs from here
http://freedesktop.org/~david/rpms/
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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-08-16 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 10:57 Udev infinite loop Guillaume Chazarain
2004-08-13 16:52 ` Greg KH
2004-08-16 8:12 ` Guillaume Chazarain
2004-08-16 8:43 ` David Zeuthen
2004-08-16 20:44 ` David Zeuthen [this message]
2004-08-17 8:19 ` Guillaume Chazarain
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=1092689091.3950.28.camel@localhost.localdomain \
--to=david@fubar.dk \
--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).