From owner-freebsd-current Tue Apr 18 12:35:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 042AC37B914 for ; Tue, 18 Apr 2000 12:35:39 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA57361; Tue, 18 Apr 2000 13:35:37 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA93518; Tue, 18 Apr 2000 13:35:03 -0600 (MDT) Message-Id: <200004181935.NAA93518@harmony.village.org> To: Bob Martin Subject: Re: current errors Cc: Garrett Wollman , "current@FreeBSD.ORG" In-reply-to: Your message of "Tue, 18 Apr 2000 13:31:14 CDT." <38FCA9F2.8BD91758@inu.net> References: <38FCA9F2.8BD91758@inu.net> <38FC9D51.4DD02C6E@home.com> <200004181746.NAA95609@khavrinen.lcs.mit.edu> Date: Tue, 18 Apr 2000 13:35:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38FCA9F2.8BD91758@inu.net> Bob Martin writes: : Not totally harmless. PNPBIOS is causing a conflict, which is causing a : kernel panic on my system. Since I haven't had a chance to track it : down, I can't be more specific. PNPBIOS isn't causing the conflict. It is merely allowing us to detect the conflict. PNPBIOS just reads a table from the BIOS of devices that are hard wired. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message