From owner-freebsd-current Sun Sep 28 00:14:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA14019 for current-outgoing; Sun, 28 Sep 1997 00:14:43 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@spain-21.ppp.hooked.net [206.169.228.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA14013 for ; Sun, 28 Sep 1997 00:14:39 -0700 (PDT) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id AAA00595 for ; Sun, 28 Sep 1997 00:15:00 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 28 Sep 1997 00:15:00 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org Reply-To: Alex To: current@freebsd.org Subject: Login is causing the kernel to panic :( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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? - alex