You are not logged in.
I've had this issue for a while now and I have no idea what might be causing it. When I plug or unplug my laptop's (Qosmio X300) power cord when there is a CD in the tray, hald CPU usage jumps to 100% and it stays there until I kill the process. I use KDEMod 4.4.5 power management system which changes the power scheme upon power cord (dis)connection.
Only way of killikd hald is running "killall -S SIGINT hald" as root, sending just SIGKILL won't do a thing. "ps -aux | grep hal" looks like this
root 18560 0.0 0.0 24336 1132 ? S 19:58 0:00 /usr/lib/hal/hald-addon-rfkill-killswitch
root 18567 0.0 0.0 24336 1128 ? S 19:58 0:00 /usr/lib/hal/hald-addon-generic-backlight
root 18569 0.0 0.0 24352 1132 ? S 19:58 0:00 /usr/lib/hal/hald-addon-cpufreq
hal 18570 0.0 0.0 19840 1124 ? S 19:58 0:00 /usr/lib/hal/hald-addon-acpi
root 18575 0.0 0.0 24340 1344 ? S 19:58 0:00 hald-addon-storage: polling /dev/sr0 (every 2 sec)
When hald goes crazy, I can see a gazillon of "hald-addon-storage" processes running. Another strange thing about this that sometimes (I haven't figured out any pattern yet) polling of /dev/sr0 is disabled, though I have re-enabled it multiple times. I also tried removing and installing hal again to no avail.
If there is no media in my DVD drive, everything seems to go smoothly. I haven't altered hal's config in any way and I haven't been having this issue before. I'm on 2.6.35-rc5-git4 kernel now but it was present even on 2.6.34. I'm pretty sure that kernel has nothing to do with that because I was running on 2.6.34 for a long time with no problems at all.
Thanx for your assistance.
Offline
Well, I'm having the same trouble you are. Except I thought it was randomly hald that would lock up when the laptop lost power. Thank you for pointing out it had to do with a CD being in the tray. I tracked this down to hald locking up when it is asked to change the polling state of the CD drive while a CD in inserted.
For me this was happening when the script /usr/lib/pm-utils/power.d/hal-cd-polling called hal-disable-polling. I modified that script to eject the drive before doing so and the problem stopped happening. This, of course does not fix anything. I guess it's a bug with hal itself.
Offline