From owner-freebsd-current Sun Sep 28 01:00:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA16888 for current-outgoing; Sun, 28 Sep 1997 01:00:07 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA16849 for ; Sun, 28 Sep 1997 01:00:02 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id JAA05963; Sun, 28 Sep 1997 09:59:16 +0200 (CEST) To: Alex cc: current@freebsd.org Subject: Re: Login is causing the kernel to panic :( In-reply-to: Your message of "Sun, 28 Sep 1997 00:15:00 PDT." Date: Sun, 28 Sep 1997 09:59:14 +0200 Message-ID: <5961.875433554@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message , Alex writ es: >The subject says it all. I noticed that this happens with kernels built >right around the time the vn bug(s) were introduced. Everything boots >fine until I attempt to login as any user. After hitting return the >system will hand for a while (keyboard leds respond) and the system will >eventually panic. A kernel built today booted fine once, attempts after >this panic'd. A generic kernel from quite a while back (pre poll()) works >fine but causes some lkms to complain *duh*. Rebuilding login didn't >work, and a few days ago building world bombed out, I'm currently trying >to build world to see if that would work. Any ideas? Yes, I just commited a fix to __getcwd, please try that out. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."