Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Jul 2006 09:15:33 +0200
From:      "O. Hartmann" <ohartman@uni-mainz.de>
To:        Corey Brune <mcbrune@gmail.com>
Cc:        "O. Hartmann" <ohartman@mail.uni-mainz.de>, freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org
Subject:   Re: Kill an stopped process
Message-ID:  <44A8C415.1000603@uni-mainz.de>
In-Reply-To: <562705370607021656xb9401dapdc5808df609d0e92@mail.gmail.com>
References:  <44A7AC66.3070805@mail.uni-mainz.de> <562705370607021656xb9401dapdc5808df609d0e92@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Corey Brune wrote:
> On 7/2/06, *O. Hartmann* <ohartman@mail.uni-mainz.de 
> <mailto:ohartman@mail.uni-mainz.de>> wrote:
> 
>     Sometimes it happens on my FreeBSD 6.1-STABLE/AMD box, that a process,
>     in most cases xine, firefox oder thunderbird, show status 'STOP' in top
>     and are unkillable!
>     Trying to kill them as root (sending signal 9 throught 'kill' or
>     'killall') doesn't have any effect.
> 
>     Can anyone help and tell how to kill such a job? The only way  getting
>     rid of those processes is reboot the box and this can not be the
>     right way.
> 
>     Thanks,
>     oh
>     _______________________________________________
>     freebsd-questions@freebsd.org <mailto:freebsd-questions@freebsd.org>
>     mailing list
>     http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>     <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>;
>     To unsubscribe, send any mail to
>     "freebsd-questions-unsubscribe@freebsd.org
>     <mailto:freebsd-questions-unsubscribe@freebsd.org>"
> 
> 
> A process cannot be killed in certain situations. For instance, if the 
> process is waiting on a IO request, it will block all signals until the 
> request is completed or fails. Could you mount /proc, and do a truss on 
> the process? Also, which version of FreeBSD are you running?
> 
> Thanks,
> Corey

Hello Corey.
As I wrote, the version of FreeBSD is 6.1-STABLE/AMD64 as newly built on 
yesterday.
You're right, xine was obviously waiting for some kind of I/O. I was 
reading a music file from a DVD mounted via amd automounter and after a 
short spinup the connection was lost by some unknown reasons, maybe the 
amd or faulty amd setup.
After a shutdown, the box got stuck at the point at whihc the kernel 
reports syncing done and then nothing happened for an eternity. Only a 
hardreset helped. In the meanwhile, I was capable of opening the DVD 
tray door and get the DVD.

oh



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44A8C415.1000603>