Red Hat Bugzilla – Bug 144625
hald freezes on hal-hotplug-map callout
Last modified: 2013-03-05 22:42:40 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
hald started freezing on me after a hard reboot on the hal-hotplug-map
callout. I completely removed and reinstalled hal in case something
had become corrupted (yes, using a journalad FS, XFS in particular)
but that changed nothing.
An strace on the executable shows it freezing after forking the
callout and calling write(). The callout finishes and is left in a
zombie state. Presumably (I don't know the code) HAL is expecting to
write something to the child and is getting stuck in a race condition
when it exits unexpectedly.
Will attach a log of:
strace /usr/bin/hald --daemon=no --verbose=yes
Because HAL never finishes initializing, no HAL-using components work.
In particular, Nautilus/gnome-vfs-daemon start behaving very badly.
(Will file a separate bug.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start HAL
Created attachment 109543 [details]
log of strace hald --daemon=no --verbose=yes
Could you test this against hal-0.4.5; I've made some fixes to the
callout code that I think will fix this. 0.4.5 is available in both
Rawhide and as a FC3 update.
Created attachment 109739 [details]
log of: hald --daemon=no --verbose=yes
Created attachment 109740 [details]
log of: strace hald --daemon=no
above two logs are from hal-0.4.5-1, still seems to lock up.
Created attachment 109741 [details]
*correct* log of: strace hald --daemon=no
Is the hald process left in the D state?
There is no hal-hotplug-map callout in the latest hal in Rawhide so I can now
close this bug :-)
Anyway, now that hal is more careful wrt handling hardware, this problem
shouldn't occur anymore. If it does, feel free to reopen this bug.