From owner-freebsd-bugs@FreeBSD.ORG Wed Jun 25 13:36:54 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40DB237B405 for ; Wed, 25 Jun 2003 13:36:53 -0700 (PDT) Received: from mail.speakeasy.net (mail7.speakeasy.net [216.254.0.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB2914400E for ; Wed, 25 Jun 2003 13:36:52 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 14999 invoked from network); 25 Jun 2003 20:36:52 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 25 Jun 2003 20:36:52 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h5PKaoGI056839; Wed, 25 Jun 2003 16:36:50 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200306251517.h5PFH32P081545@freefall.freebsd.org> Date: Wed, 25 Jun 2003 16:37:03 -0400 (EDT) From: John Baldwin To: Robert Watson cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/53725: fatal trap 12 during boot, sys/dev/pci/pci.c X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 20:36:54 -0000 On 25-Jun-2003 Robert Watson wrote: > Synopsis: fatal trap 12 during boot, sys/dev/pci/pci.c > > Responsible-Changed-From-To: freebsd-bugs->jhb > Responsible-Changed-By: rwatson > Responsible-Changed-When: Wed Jun 25 08:15:39 PDT 2003 > Responsible-Changed-Why: > 1.216 was committed by jhb, and enabled PCI interrupt routing on > i386 UP machines. Hand it over to jhb, since he's most likely > to know what to do. > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=53725 Can the submitter provide a verbose boot? I think there is something in general broken with executing BIOS code in current. An Intel 865 chipset board I have here panics in the PnP BIOS probe on the last BIOS call due to what seems to be a bug in 5.x. 4.x works fine. Peter might be a good person to ask why we have issues calling the BIOS on 5.x. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/