From owner-freebsd-current Wed Mar 12 13:44:17 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E49437B401 for ; Wed, 12 Mar 2003 13:44:15 -0800 (PST) Received: from pop017.verizon.net (pop017pub.verizon.net [206.46.170.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8354343F75 for ; Wed, 12 Mar 2003 13:44:14 -0800 (PST) (envelope-from bleez@verizon.net) Received: from gravy.kishka.net ([151.197.249.111]) by pop017.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030312214413.INNL2095.pop017.verizon.net@gravy.kishka.net> for ; Wed, 12 Mar 2003 15:44:13 -0600 Received: from localhost (localhost [127.0.0.1]) by gravy.kishka.net (8.12.8/8.12.8) with ESMTP id h2CLiBji001279 for ; Wed, 12 Mar 2003 16:44:12 -0500 (EST) (envelope-from bleez@verizon.net) Date: Wed, 12 Mar 2003 16:44:11 -0500 (EST) From: Bryan Liesner X-X-Sender: root@gravy.kishka.net To: freebsd-current@freebsd.org Subject: Re: Still getting panic on boot. (fwd) Message-ID: <20030312164329.E1278@gravy.kishka.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Info: Submitted using SMTP AUTH at pop017.verizon.net from [151.197.249.111] at Wed, 12 Mar 2003 15:44:13 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG oops, didn't cc this to the list ---------- Forwarded message ---------- Date: Wed, 12 Mar 2003 15:50:01 -0500 (EST) From: Bryan Liesner To: Shizuka Kudo Subject: Re: Still getting panic on boot. On Wed, 12 Mar 2003, Shizuka Kudo wrote: > > --- walt wrote: > > 04:00 GMT Mar 12: > > > > Just cvsup'd and rebuilt with same result as 12 hours ago -- > > I see a kernel panic "page fault while in kernel mode" just > > after attempting to mount the root filesystem. > > > > The kernel from yesterday works fine and when I reboot the > > filesystems come up clean, so the new kernel nevers writes > > to disk, apparently. > > > > Am I the only one seeing this? > > I saw the same here. However, after reboot with the same faulty kernel, it may not panic but > doesn't have the /dev/null entry which makes the bootup process failed. In addition, my -current > was cvsup'd about four hours ago. > I'm seeing the same thing - /dev/null disappeared. I also saw in my nightly scripts that 'tee /dev/stderr' failed as well. It seems fairly random. X wouldn't start, complaining that /dev/vga doesn't exist. I did a cvsup by date/time: *default release=cvs date=2003.03.10.12.00.00 tag=. That seems to put things right. There were some kern commits shortly after that time that caused this weirdness. I've been really busy at work fixing a billion bugs for c client rollout - no time for a backtrace... ( the bugs aren't mine - I write perfect code every time :) ) -- ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@verizon.net Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message