From owner-freebsd-current Wed Mar 25 15:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04085 for freebsd-current-outgoing; Wed, 25 Mar 1998 15:55:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04055 for ; Wed, 25 Mar 1998 15:55:38 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id RAA12777; Wed, 25 Mar 1998 17:55:35 -0600 (CST) From: Kevin Day Message-Id: <199803252355.RAA12777@home.dragondata.com> Subject: Re: Panic while in tulip code In-Reply-To: <19980325203746.54927@jraynard.demon.co.uk> from James Raynard at "Mar 25, 98 08:37:47 pm" To: fcurrent@jraynard.demon.co.uk (James Raynard) Date: Wed, 25 Mar 1998 17:55:34 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Mar 24, 1998 at 09:48:51PM -0600, Kevin Day wrote: > > > > I received the following tonight: > > > > panic: page fault while in kernel mode > > > > This kernel is from the 14th..... > > Argh! Where have you been for the last two weeks?? > > If that's the biggest problem you're having, count yourself lucky, > back up your system while you still have a filesystem left on > it and pray that it'll stay up long enough for you to compile a new > kernel. Friday 13th was an extremely unlucky day for the -current > kernel and gave rise to floods of "Good Times Virus" lookalike mails > on this list (except they weren't fakes). How did you manage to > miss them? > > James > Sorry, ignore that... The kernel was from the 12th, but I rebuilt it on the 14th. :) I didn't miss the whole discussion. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message