From owner-freebsd-current Sun Mar 16 15:31:54 2003 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 8FA5237B401 for ; Sun, 16 Mar 2003 15:31:49 -0800 (PST) Received: from asylum.org (asylum.org [208.13.58.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84A1043F75 for ; Sun, 16 Mar 2003 15:31:48 -0800 (PST) (envelope-from dave@asylum.org) Received: from p139.asylum.org (p139.asylum.org [208.13.58.139]) by asylum.org (8.11.6/8.11.6) with ESMTP id h2GNVlk91026 for ; Sun, 16 Mar 2003 18:31:47 -0500 (EST) (envelope-from dave@asylum.org) Message-Id: <5.1.0.14.2.20030316182645.03706db8@asylum.org> X-Sender: dave@asylum.org X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 16 Mar 2003 18:32:01 -0500 To: current@FreeBSD.ORG From: dave Subject: Re: ACPI errors and panic In-Reply-To: <20030316225613.M58621@xtaz.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 06:04 PM 3/16/2003, Matt wrote: >Hi, > >I have just recently installed -CURRENT on my desktop as I've been using it >succesfully on a server for months now. However this desktop has much more >advanced hardware. Whilst it does work perfectly and I have device support for >everything I get a lot of ACPI errors on bootup and also a panic when I try to >reboot it, though luckily after it's synced the disks. > >I have saved the dmesg output to http://tao.xtaz.co.uk/dmesg.txt > >I was wondering if somebody could tell me what all those errors (and the >random gibberish at the top) is about. I also assume that the panic happens >right as the o/s tries to reset the system. I've tried turning off acpi in the >bios but freebsd still see's it all and it has no affect. Is there anything I >can do regarding sysctl.conf etc to prevent all this? Or alternatively if >there is a problem do you know how to go abotu fixing it rather than just >trynig to disable it? Matt, It seems like the fix right now is to disable it. Put this line: hint.acpi.0.disabled="1" in /boot/device.hints dave racette To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message