From owner-freebsd-current@FreeBSD.ORG Mon Jan 19 18:16:23 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 16E3E16A4CE for ; Mon, 19 Jan 2004 18:16:23 -0800 (PST) Received: from web9608.mail.yahoo.com (web9608.mail.yahoo.com [216.136.129.187]) by mx1.FreeBSD.org (Postfix) with SMTP id D8BDF43D39 for ; Mon, 19 Jan 2004 18:16:21 -0800 (PST) (envelope-from chancedj@yahoo.com) Message-ID: <20040120021621.97276.qmail@web9608.mail.yahoo.com> Received: from [69.22.69.186] by web9608.mail.yahoo.com via HTTP; Mon, 19 Jan 2004 18:16:21 PST Date: Mon, 19 Jan 2004 18:16:21 -0800 (PST) From: Daryl Chance To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-972718614-1074564981=:94755" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: 5.2-RELEASE Crash [ACPI Related?] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: chancedj@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 02:16:23 -0000 --0-972718614-1074564981=:94755 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline I have a reproduceable crash from a box that i'm trying to boot 5.2-Release on. It boots fine all the time....unless I power it on and then switch over to another machine (it's on a KVM). If i wait till it should be booted then change back over, it's crashed right when it's starts to boot. Here is the verbose output: http://satan.homeip.net/~chancedj/messages I can't get any type of dump, so here's is a picture of the crash. I tried getting it to panic by waiting till the selection screen popped up and then switching back quickly....but then it locked up right after it identified the vga adapter. (I'll try and reproduce this as well). In both cases, the keyboard and machine were not responsive (I assume in the first one that the machine was responsive, but I couldn't get to it because of the keyboard not being responsive....since it booted while I was on another screen). I'm going to try and get the machine to boot using option #5 by default and see if I can get a better shot of the error. Daryl. __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus --0-972718614-1074564981=:94755--