From owner-freebsd-current Tue Feb 26 17:10: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from patrocles.silby.com (d19.as13.nwbl0.wi.voyager.net [169.207.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 4F8A637B405 for ; Tue, 26 Feb 2002 17:09:55 -0800 (PST) Received: from patrocles.silby.com (localhost [127.0.0.1]) by patrocles.silby.com (8.12.2/8.12.2) with ESMTP id g1QJE71L000252; Tue, 26 Feb 2002 19:14:07 GMT (envelope-from silby@silby.com) Received: from localhost (silby@localhost) by patrocles.silby.com (8.12.2/8.12.2/Submit) with ESMTP id g1QJDv67000249; Tue, 26 Feb 2002 19:14:05 GMT X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Tue, 26 Feb 2002 19:13:57 +0000 (GMT) From: Mike Silbersack To: Peter Wemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: Today's panic on boot problem In-Reply-To: <20020226233833.463723BAD@overcee.wemm.org> Message-ID: <20020226191247.S248-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Tue, 26 Feb 2002, Peter Wemm wrote: > Mike Silbersack wrote: > > I'm experiencing the same double panic on boot that PHK is now; are we the > > only ones, or is it just that nobody else has updated recently? > > If you are not using acpica, then you're probably using vm86 for pcibios > calls. I've been told that I've broken bios.c.. > > You may like to try reverting this change: > > peter 2002/02/25 13:42:23 PST > > Modified files: > sys/i386/i386 bios.c > sys/i386/include pmap.h > Log: > Tidy up some warnings > > Revision Changes Path > 1.47 +7 -6 src/sys/i386/i386/bios.c > 1.74 +1 -1 src/sys/i386/include/pmap.h > > Cheers, > -Peter I reverted that change, and the double panic still occured. :| FWIW, you're correct in that I'm not using the acpi module. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message