From owner-freebsd-i386@FreeBSD.ORG Mon Sep 27 15:00:50 2004 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7668716A4CE for ; Mon, 27 Sep 2004 15:00:50 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6978E43D2F for ; Mon, 27 Sep 2004 15:00:50 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8RF0opR050453 for ; Mon, 27 Sep 2004 15:00:50 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8RF0ofb050452; Mon, 27 Sep 2004 15:00:50 GMT (envelope-from gnats) Date: Mon, 27 Sep 2004 15:00:50 GMT Message-Id: <200409271500.i8RF0ofb050452@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Subject: Re: i386/71392: 5.3-Beta2 crash X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2004 15:00:50 -0000 The following reply was made to PR i386/71392; it has been noted by GNATS. From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: db Cc: freebsd-gnats-submit@freebsd.org Subject: Re: i386/71392: 5.3-Beta2 crash Date: Mon, 27 Sep 2004 17:00:04 +0200 db writes: > On Monday 27 September 2004 15:37, you wrote: > > 1) "No buffers busy after final sync" is not a bug. You should get > > that message every time you shut down. > I didn't write "No buffers busy after final sync", someone at FreeBSD did. Sorry, I'll correct the synopsis. > What have I learned from the above? Well, most users would think > "hm, nobody cares, I gonna stop writing bug reports", but I decided > it give it another try. You're right, most developers don't care about PRs filed against -CURRENT. I assume that you read the freebsd-current mailing list, and that you reported your problems there? > > In closing, the panic you get when trying to power your system off is > > mostly likely related to ACPI - either a bug in the ACPI code, or > > (more likely) a bug in your system's DSDT. Try booting with ACPI > > disabled. > Maybe a stupid question, but how? I found Select "Boot FreeBSD with ACPI disabled" in the boot menu. > http://www.freebsd.org/cgi/man.cgi?query=3Dacpi&sektion=3D4 and it says: > "To disable the acpi driver completely, set the kernel environment > variable hint.acpi.0.disabled to 1", but I haven't got that one. > > I got: > [list of sysctl variables] man device.hints man loader.conf DES --=20 Dag-Erling Sm=F8rgrav - des@des.no