Date: Mon, 27 Sep 2004 13:40:20 GMT From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: freebsd-i386@FreeBSD.org Subject: Re: i386/71392: 5.3-Beta2 crash: 'no buffers busy' after final sync Message-ID: <200409271340.i8RDeKxB041976@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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 <db@traceroute.dk>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: i386/71392: 5.3-Beta2 crash: 'no buffers busy' after final sync
Date: Mon, 27 Sep 2004 15:37:21 +0200
db <db@traceroute.dk> writes:
> Upgraded to 5.3-Beta5, problem is still there. This is the last
> beta, so how can a bug like this still be unhandled?
Because you didn't volunteer to track it down and fix it.
Sniping aside, three points:
1) "No buffers busy after final sync" is not a bug. You should get
that message every time you shut down.
2) Since the kernel panic you are experiencing occurrs after final
sync on poweroff, and therefore does not cause significant loss of
function or (more importantly) data corruption, it is not a high-
priority issue.
3) You did not follow the documented procedure for reporting a kernel
panic. Section 18 of the FAQ contains instructions for producing
a backtrace, which is the minimum information required.
You can't expect a misfiled and incomplete report of a low-priority
issue to be fast-tracked ahead of the 4,415 other open bug reports in
our database, or even the 3,078 that aren't filed under doc or ports.
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.
DES
--=20
Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409271340.i8RDeKxB041976>