| 1 |
Michael George ha scritto: |
| 2 |
> On Mon, Jul 09, 2007 at 06:46:38PM -0500, Albert Hopkins wrote: |
| 3 |
>> On Mon, 2007-07-09 at 19:26 -0400, Michael George wrote: |
| 4 |
>> |
| 5 |
>> What state is the process in? If it's in an "Uninterruptible sleep" (D) |
| 6 |
>> mode then it won't die/continue until it gets whatever I/O it's |
| 7 |
>> expecting. If it doesn't (e.g. there's something wrong with the device |
| 8 |
>> it's held on to) then you'll probably have to reboot. |
| 9 |
>> |
| 10 |
>> http://linuxgazette.net/issue83/tag/6.html |
| 11 |
> |
| 12 |
> Yes, it was in state D. I could see it was hald, but I don't know what |
| 13 |
> device it was waiting on. My 3Ware controller had no complaints, and I |
| 14 |
> don't think hald was managing my other HDD. There had been no removable |
| 15 |
> disks in drives for days. |
| 16 |
> |
| 17 |
> Very odd... |
| 18 |
> |
| 19 |
|
| 20 |
I had the same problem: |
| 21 |
|
| 22 |
hald was sucking 99% cpu, removables devices didn't work |
| 23 |
and launching hald from terminal with the option "--daemon=no |
| 24 |
--verbose=yes" i discovered it was on a infinite loop echo-ing |
| 25 |
something about rules so I got in /etc/udev/rules.d |
| 26 |
and found (by probing one by one) 99-libgphoto2.rules that |
| 27 |
was HALS's murder. |
| 28 |
|
| 29 |
I hope it's useful for you |
| 30 |
|
| 31 |
Alessandro |
| 32 |
-- |
| 33 |
gentoo-user@g.o mailing list |
Archives