From owner-freebsd-current  Thu Aug 19  2:34:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.41.238])
	by hub.freebsd.org (Postfix) with ESMTP
	id BEEA714C8C; Thu, 19 Aug 1999 02:34:08 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA00248;
	Thu, 19 Aug 1999 10:07:26 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: msmith@freebsd.org
Cc: current@freebsd.org
Subject: PnP probe croaks in boot...
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Thu, 19 Aug 1999 10:07:25 +0200
Message-ID: <246.935050045@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Mike,

the PnP probe you added panics my HP800CT during boot.

With -v it prints (typed from barely legible notes:)

	PnPbios: Found PnPBiosdata 0xc00ff000
	PnPbios: Entry e8000:33e1 rev 1.0
	PnPbios: eventflag at e801b
	OEM ID 1826744e

and then panics with a pagefault at EIP: %058:0x343e, fault address
0x100e.  Adding some debugging showed me that this happens on the
very first call to bios16_call().

The funny thing is, this happens after a cold boot (hard reset),
and goes on until I have booted my /kernel.good (from before your
change) just once.  After that, and until next hard reset a -current
kernel boots just fine.

Smells like som unitialized data or something to me...

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message