bin/164526: kill(1) can not kill process despite on -KILL
kes-kes at yandex.ru
Sat Jan 28 22:10:11 UTC 2012
The following reply was made to PR bin/164526; it has been noted by GNATS.
From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes at yandex.ru>
To: Jilles Tjoelker <jilles at stack.nl>
Cc: bug-followup at FreeBSD.org
Subject: Re: bin/164526: kill(1) can not kill process despite on -KILL
Date: Sun, 29 Jan 2012 00:07:03 +0200
Âû ïèñàëè 28 ÿíâàðÿ 2012 ã., 20:24:07:
>> [stuck process cannot be killed, system hangs when reboot is
JT> A signal cannot forcibly kill a process that is stuck in the kernel.
JT> Allowing this would put the integrity of the kernel data structures at
JT> risk and likely cause hangs, data corruption or panics later on.
JT> If a process is stuck in the kernel for a long time, this can be things
JT> like broken hardware, a non-responsive NFS server or a bug.
JT> A state 'T' (stopped) probably means the process is multi-threaded and
JT> is trying to suspend but one or more threads will not cooperate
JT> (non-interruptible sleep or running in the kernel).
JT> Useful commands to obtain more information (supposing pid is 45471):
JT> ps Hl45471
JT> procstat -k 45471
JT> Of course, this does not help if you already rebooted.
that was happen when: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/164145
kern/164145: [netisr] when one of netisr threads take 100% system is going to work unstable
at this moment I try to restart 'radiusd' and it was STOPped forever
even when I try to reboot (((( whole system is stopped
so I need to travel to server to turn it OFF.
may be in this state just 'jmp BOOTSYSTEM_FROM_BEGINNING'
(sorry, do no remember address to start BIOS POST)
and do not allow to hangs forever.
Êîíüêîâ mailto:kes-kes at yandex.ru
More information about the freebsd-bugs