Michael George ha scritto:
On Mon, Jul 09, 2007 at 06:46:38PM -0500, Albert Hopkins wrote:
On Mon, 2007-07-09 at 19:26 -0400, Michael George wrote:
What state is the process in? If it's in an "Uninterruptible sleep" (D)
mode then it won't die/continue until it gets whatever I/O it's
expecting. If it doesn't (e.g. there's something wrong with the device
it's held on to) then you'll probably have to reboot.
http://linuxgazette.net/issue83/tag/6.html
Yes, it was in state D. I could see it was hald, but I don't know what
device it was waiting on. My 3Ware controller had no complaints, and I
don't think hald was managing my other HDD. There had been no removable
disks in drives for days.
Very odd...
I had the same problem:
hald was sucking 99% cpu, removables devices didn't work
and launching hald from terminal with the option "--daemon=no
--verbose=yes" i discovered it was on a infinite loop echo-ing
something about rules so I got in /etc/udev/rules.d
and found (by probing one by one) 99-libgphoto2.rules that
was HALS's murder.
I hope it's useful for you
Alessandro
--
[EMAIL PROTECTED] mailing list
