Red Hat Bugzilla – Bug 136626
hald gives timeout message every second
Last modified: 2013-03-05 22:41:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Description of problem:
Every second hald writes a line similar to the following to syslog:
hald: Timed out waiting for hotplug event 386
The numbers increase for every line. For most of these lines there is
no according hotplug event recorded in the syslog file. The first
occurance is this pair (triggered by system startup)
Oct 21 12:21:03 nausicaa default.hotplug: arguments (vc) env
(OLDPWD=/ DEVPATH=/class/vc/vcs6 PATH=/bin:/sbin:/usr/sbin:/usr/b
in ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 SEQNUM=298 _=/bin/env)
Oct 21 12:21:05 nausicaa hald: Timed out waiting for hotplug
After this a hald line is recorded every second.
Restarting the haldaemon service takes care of the problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot system, observe syslog
Actual Results: hald records timeout events every second
Expected Results: No timeouts? At least I did not get them earlier.
Hmm; this looks difficult to reproduce; a few questions/requests:
1. I suppose disabling the hal daemon and running 'hald --daemon=no
--verbose=yes' wont give the timeouts? If it does, please attach the
output to this bug report
2. Please attach the output lshal
3. Do you have hardware using the prism54 driver? (See bug 135202)
4. Does the hald work as expected when emitting these messages?
5. Will plugging in a USB device stop the emission of these messages?
So, basically I'm looking for a way to get the debug output from the
hal daemon when this happens. One way is to modify your
/etc/init.d/haldaemon init script, e.g. temporarily change this line
daemon --check $servicename $processname
/usr/sbin/hald --daemon=no --verbose=yes 2> /tmp/hald_output &
and reboot. Then attach /tmp/hald_output (remember to change it back).
How do I determine if the hal daemon "works as expected"?
OK, all this seems to be subject to some timing issue.
a) If I disable hal via chkconfig and start the daemon manually after
the system has finished booting, the effect does not occur (this might
explain why restarting the daemon fixes it)
b) Booting with a CD in a CD drive causes the effect to disappear.
c) Plugging in USB devices does not fix it.
d) I do not have any wireless stuff in this machine.
e) hal adds devices to /etc/fstab in any case, so I think it works.
f) I was able to capture the error in debugging mode, output is attached.
Created attachment 105640 [details]
Created attachment 105641 [details]
Thanks for the traces; please try the RPMS here
and see if the problem is solved.
hal-0.4.0-5b seems to fix it.
Thanks, this fix is in hal-0.4.0-8 available here
which will hopefully make FC3.