From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 28 22:10:11 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE74E106564A for ; Sat, 28 Jan 2012 22:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B7C368FC13 for ; Sat, 28 Jan 2012 22:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0SMABwF080595 for ; Sat, 28 Jan 2012 22:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0SMABi1080594; Sat, 28 Jan 2012 22:10:11 GMT (envelope-from gnats) Date: Sat, 28 Jan 2012 22:10:11 GMT Message-Id: <201201282210.q0SMABi1080594@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= Cc: Subject: Re: bin/164526: kill(1) can not kill process despite on -KILL X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 22:10:11 -0000 The following reply was made to PR bin/164526; it has been noted by GNATS. From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= To: Jilles Tjoelker Cc: bug-followup@FreeBSD.org Subject: Re: bin/164526: kill(1) can not kill process despite on -KILL Date: Sun, 29 Jan 2012 00:07:03 +0200 Здравствуйте, Jilles. Вы писали 28 января 2012 г., 20:24:07: >> [stuck process cannot be killed, system hangs when reboot is >> attempted] 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@yandex.ru