Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Dec 2003 09:02:33 +0100 (CET)
From:      Soren Schmidt <sos@spider.deepcore.dk>
To:        Jun Kuriyama <kuriyama@imgsrc.co.jp>
Cc:        Current <freebsd-current@FreeBSD.ORG>
Subject:   Re: -current lockup (how to diagnose?)
Message-ID:  <200312010802.hB182XfH008722@spider.deepcore.dk>
In-Reply-To: <7mznedas57.wl@black.imgsrc.co.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
It seems Jun Kuriyama wrote:
> 
> I got lockups in recent -current box.  This box is my main workstation
> and usually be up to date kernel.
> 
> In recent days, I usually locked up.  This is not a panic, only locks
> up.  My situation is:
> 
> o KDE's clock is working.
> o KDE's virtual screen switching is working.
> o Apache does not reply on 80/tcp from remote.
> o ssh from this box is still working.
> o zsh on this box does not go next prompt when I press enter key at
>   promprt.
> 
> It looks kernel is working, but fork/exec is not working when I enter
> to this situation.

Hmm, I've been seeing something semilar a couble of times, can you do a
ps -axl and see if those processes hang around in vm ?

-Søren



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