Date: Mon, 01 Dec 2003 23:06:54 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Melvyn Sopacua <freebsd-current@webteckies.org> Cc: Current <freebsd-current@FreeBSD.ORG> Subject: Re: -current lockup (how to diagnose?) Message-ID: <7misl0bpj5.wl@black.imgsrc.co.jp> In-Reply-To: <200312011440.01262.freebsd-current@webteckies.org> References: <200312010802.hB182XfH008722@spider.deepcore.dk> <200312011440.01262.freebsd-current@webteckies.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Mon, 1 Dec 2003 14:39:56 +0100,
Melvyn Sopacua wrote:
> > > 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.
>
> But ssh *to* the box doesn't right?
Yes.
> I've had this on -STABLE as well and indeed KDE seems to be related. Also, I
> recall this to happen during the security check or rebuilding the locate
> database. I haven't seen this once I installed more memory.
>
> A good tell-tale is:
> * Switch to the console.
> * Select another VT, via ALT-F2
> * Type in the login name and press enter
>
> You won't get a passwd prompt.
Yes, I can see the same situation.
> Most of the time I got outof it, by CTRL-ALT-F1 and CTRL-C.
Hmm, I'll try next time.
> I think I have a weekly run report somewhere, reporting 'vm exhaustion'
> errors. I can dig it up if it's helpful.
> At the time, the box had 128Megs of RAM and 256MB swap, P-III 450.
My box has 2GB memory, so it would be enough. My box makes world and
release nightly and it locks usually at that time.
Anyway, I'm waiting for next lock ups. :-)
--
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7misl0bpj5.wl>