| 1 |
Hi, |
| 2 |
|
| 3 |
As far as I know, this happens, when a process waiting for a hardware |
| 4 |
resource. |
| 5 |
|
| 6 |
Maybe something happened, which blocks the hardware, that means, the |
| 7 |
kernel process never returns to the userspace. |
| 8 |
|
| 9 |
This can be caused by bad/buggy hardware or buggy driver. |
| 10 |
|
| 11 |
So, Richard is right, check your hardware, does everything work fine or not. |
| 12 |
|
| 13 |
Regards, |
| 14 |
István |
| 15 |
|
| 16 |
|
| 17 |
Richard Fish wrote: |
| 18 |
|
| 19 |
>On 11/28/05, Mark Knecht <markknecht@×××××.com> wrote: |
| 20 |
> |
| 21 |
> |
| 22 |
>>kill -15 PID |
| 23 |
>>kill -9 PID |
| 24 |
>>killall -9 process_name |
| 25 |
>> |
| 26 |
>>but none worked. To make forward progress I just rebooted. |
| 27 |
>> |
| 28 |
>> Is there some other way I could have tried killing this process? |
| 29 |
>> |
| 30 |
>> |
| 31 |
> |
| 32 |
>Nope. Usually this means something went terribly wrong in hardware. |
| 33 |
>Pullling a hard drive out of the system while it is running is an easy |
| 34 |
>way to duplicate this problem, as it will cause the kernel to enter an |
| 35 |
>interminable reset loop to try and recover. Problems with network |
| 36 |
>filesystems could also cause something similar. |
| 37 |
> |
| 38 |
>You should check dmesg output to see if the kernel is complaining |
| 39 |
>about something. |
| 40 |
> |
| 41 |
>-Richard |
| 42 |
> |
| 43 |
> |
| 44 |
> |
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-user@g.o mailing list |
Archives