i386/71392: 5.3-Beta2 crash: 'no buffers busy' after final sync

Dag-Erling Smørgrav des at des.no
Mon Sep 27 06:40:24 PDT 2004


The following reply was made to PR i386/71392; it has been noted by GNATS.

From: des at des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=)
To: db <db at traceroute.dk>
Cc: freebsd-gnats-submit at 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 at 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 at des.no


More information about the freebsd-i386 mailing list