Date: Mon, 1 Dec 2003 09:23:21 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Jun Kuriyama <kuriyama@imgsrc.co.jp> Cc: Current <freebsd-current@FreeBSD.org> Subject: Re: -current lockup (how to diagnose?) Message-ID: <Pine.NEB.3.96L.1031201092204.74465L-100000@fledge.watson.org> In-Reply-To: <7mznedas57.wl@black.imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 1 Dec 2003, 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. > > So, what can I diagnose with this situation? Of course this box has > serial console. This could be a sign of a VM or VFS lock leak or deadlock. I'd advise hooking up a serial console, dropping to DDB over serial line, and posting the results of "ps" and "show lockedvnods". We might then ask you to use the "show locks" command on various processes. You'll need to have DDB and WITNESS compiled in. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1031201092204.74465L-100000>