From owner-freebsd-current Thu Oct 15 04:59:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12011 for freebsd-current-outgoing; Thu, 15 Oct 1998 04:59:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12006 for ; Thu, 15 Oct 1998 04:59:53 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id GAA15243; Thu, 15 Oct 1998 06:59:35 -0500 (CDT) Message-ID: <19981015065935.A15239@Denninger.Net> Date: Thu, 15 Oct 1998 06:59:35 -0500 From: Karl Denninger To: stox@enteract.com Cc: current@FreeBSD.ORG Subject: Re: Uh, guys, BETA 3.0 right now panics on boot References: <19981014202222.A208@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kenneth P. Stox on Wed, Oct 14, 1998 at 11:37:37PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, if I could get a dump, or something other than "current as of last night", I would! Machine is irrelavent (it happens on both Ppro 200s and P166s). There is no dmesg; the machine panics INSTANTLY on start; as I said, you don't even get into the device probes! It sounds like the bootloader might be responsible for this - I'm going to shut off the new boot loader and see if that makes it go away. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. On Wed, Oct 14, 1998 at 11:37:37PM -0500, Kenneth P. Stox wrote: > > Karl: > You have been active here for how many years ? This is the type of > bug report one would expect from needinfo@juno.com. How about reporting > something useful ? Examples would include: machine configuration, dmesg > output, kernel configuration, what time you cvsup'ed, etc. > > BTW, I have 4 machines here, from a 486 laptop to a dual PII SMP > that I cvsup'ed early this morning and at 10PM CDT this evening, and none > exhibit the panic you describe. I am also running aout and ELF > configurations. > > I am not, as of yet, running the new boot loader, however. As we > run down to the deadline, if you have a problem, detailed bug reports are > crucial. I am sure that nobody wants to see 3.0 be released in anything > less than workable form. ( Well except the boys in Redmond, that is ) > > I am very tempted to say that if 3.0 only panics for Karl, this > might be considered a feature. ;-> > > > -Ken Stox > stox@imagescape.com > stox@fnal.gov > > On Wed, 14 Oct 1998, Karl Denninger wrote: > > > Immediate panic, no dump, "supervisor page not present". Never even starts > > probing devices. > > > > Bad, bad stuff! > > > > -- > > -- > > Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message