From owner-freebsd-current@FreeBSD.ORG Tue May 25 07:16:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 465D216A4CE; Tue, 25 May 2004 07:16:43 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9101943D2F; Tue, 25 May 2004 07:16:42 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i4PEG6sD055251; Tue, 25 May 2004 09:16:06 -0500 (CDT) (envelope-from dan) Date: Tue, 25 May 2004 09:16:06 -0500 From: Dan Nelson To: Klaus Robert Suetterlin Message-ID: <20040525141606.GK75036@dan.emsphone.com> References: <200405250823.21605.jhb@FreeBSD.org> <200405251321.i4PDL8jF005186@robert2.mpe-garching.mpg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200405251321.i4PDL8jF005186@robert2.mpe-garching.mpg.de> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: correction: fatal trap 12 when booting without ACPI (was wrongly Re: Fatal Trap 12 that goes away with NO ACPI --- anyone interested?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2004 14:16:43 -0000 In the last episode (May 25), Klaus Robert Suetterlin said: > I'm sorry, I mixed it all up: > > - The sytem hangs with fatal trap 12 if I use default, which is > without ACPI (because my loader.conf does not contain > ``acpi_load="YES"''). > > - And it boots ok, when I choose the second (beastie boot menu) entry, > which is with ACPI _enabled_ in my case. I got this also when I was trying to get rid of some silo overflows on my laptop last night. I tried booting without ACPI and got a trap 12 in module_lookupbyname+0x13, called by the swapper process. If I had known other people were getting it I would have written down everything. -- Dan Nelson dnelson@allantgroup.com