From nobody@FreeBSD.org  Sun Sep  5 08:49:17 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 807C116A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  5 Sep 2004 08:49:17 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 75B5843D46
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  5 Sep 2004 08:49:17 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i858nHPG022669
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 5 Sep 2004 08:49:17 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i858nH1B022668;
	Sun, 5 Sep 2004 08:49:17 GMT
	(envelope-from nobody)
Message-Id: <200409050849.i858nH1B022668@www.freebsd.org>
Date: Sun, 5 Sep 2004 08:49:17 GMT
From: db <db@TruNet.dk>
To: freebsd-gnats-submit@FreeBSD.org
Subject: 5.3-Beta2 crash
X-Send-Pr-Version: www-2.3

>Number:         71392
>Category:       i386
>Synopsis:       5.3-Beta[2-5] crash after final sync when powering off
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 05 08:50:27 GMT 2004
>Closed-Date:    Thu Oct 27 15:16:18 GMT 2005
>Last-Modified:  Thu Oct 27 15:16:18 GMT 2005
>Originator:     db
>Release:        5.3-Beta2
>Organization:
>Environment:
FreeBSD work.trunet.dk 5.3-BETA2 FreeBSD 5.3-BETA2 #1: Sat Aug 28 21:29:15 UTC 2004     root@mack.dcsl.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
      When shutting down my computer, I sometimes get:
No buffers busy after final sync
Uptime: 1d22h4m8s

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xc
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0575abe
stack pointer = 0x10:0xd41e8cc0
frame pointer = 0x10:0xd41e8cdc
code segment = base 0x0, limit 0xffff, type 0x16
             = DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 16 (irq 5: re0)
[thread 100009]
Stopped at re_rxeof+ox2ae: movl %eax, oxc(%edi)
db>
>How-To-Repeat:
      Try shutdown -p now
>Fix:
      
>Release-Note:
>Audit-Trail:

From: db <db@TruNet.dk>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: i386/71392: 5.3-Beta2 crash
Date: Tue, 7 Sep 2004 11:41:07 +0200

 Command - Result
 shutdown -p now - Crash
 shutdown -h now - All good
 reboot -p - Crash
 reboot - All good
 
 br
 db

From: db <db@trunet.dk>
To: FreeBSD-gnats-submit@freebsd.org, freebsd-i386@freebsd.org
Cc:  
Subject: Re: i386/71392: 5.3-Beta2 crash
Date: Mon, 13 Sep 2004 18:37:18 +0200

 I've just upgraded my system to 5.3-Beta4 and now a "shutdown -p now" gives 
 me:
 
 Uptime: 1m35s
 Fatal trap 12: page fault while in kernel mode
 cpuid = 0; apic id = 00
 fault virtual address = 0xc
 fault code = supervisor write, page not present
 instruction pointer = 0x8:0xc0572654
 stack pointer = 0x10:0xd41e5cbc
 frame pointer = 0x10:0xd41e5cdc
 code segment = base 0x0, limit 0xffff, type 0x1b
              = DPL 0, pres 1, def32 1, gran 1
 processor eflags = interrupt enabled, resume, IOPL = 0
 current process = 16 (irq 5: re0)
 trap nubmer = 12
 panic: page fault
 cpuid = 0
 Uptime: 1m40s

From: db <db@traceroute.dk>
To: freebsd-gnats-submit@freebsd.org, db@trunet.dk
Cc:  
Subject: Re: i386/71392: 5.3-Beta2 crash: 'no buffers busy' after final sync
Date: Mon, 20 Sep 2004 23:33:00 +0200

 Upgraded to 5.3-Beta5, problem is still there. This is the last beta, so how 
 can a bug like this still be unhandled?
 
 br
 db

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

From: db <db@traceroute.dk>
To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no>
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 16:32:50 +0200

 On Monday 27 September 2004 15:37, you wrote:
 > 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.
 
 1. I'm not a C programmer.
 2. I'm not a kernel hacker.
 3. I spend all my time on school/work/lockdown (1.1.0 o it's way).
 
 So the best I can do is report the bug and do that you debuggers tell me to 
 do.
 
 > 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.
 
 I didn't write "No buffers busy after final sync", someone at FreeBSD did.
 
 >  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.
 
 Hm ok..........
 
 >  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.
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/65658
 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/65702
 
 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 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.
 
 I don't, but I except/hope a bug like this will be fixed before 5.3 is 
 released.
 
 > 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 
 http://www.freebsd.org/cgi/man.cgi?query=acpi&sektion=4 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:
 debug.acpi.acpi_ca_version: 0x20040527
 debug.acpi.semaphore_debug: 0
 hw.acpi.supported_sleep_state: S1 S4 S5
 hw.acpi.power_button_state: S5
 hw.acpi.sleep_button_state: S1
 hw.acpi.lid_switch_state: NONE
 hw.acpi.standby_state: S1
 hw.acpi.suspend_state: S3
 hw.acpi.sleep_delay: 1
 hw.acpi.s4bios: 0
 hw.acpi.verbose: 0
 hw.acpi.reset_video: 1
 hw.acpi.cpu.throttle_max: 2
 hw.acpi.cpu.throttle_state: 2
 hw.acpi.cpu.cx_supported: C1/0 C2/90
 hw.acpi.cpu.cx_lowest: C1
 hw.acpi.cpu.cx_usage: 100.00% 0.00%
 machdep.acpi_timer_freq: 3579545
 machdep.acpi_root: 1012112
 dev.acpi.0.%desc: VIA694 AWRDACPI
 dev.acpi.0.%driver: acpi
 dev.acpi.0.%parent: nexus0
 dev.acpi_sysresource.0.%desc: System Resource
 dev.acpi_sysresource.0.%driver: acpi_sysresource
 dev.acpi_sysresource.0.%location: handle=\_SB_.MEM_
 dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C01 _UID=0
 dev.acpi_sysresource.0.%parent: acpi0
 dev.acpi_sysresource.1.%desc: System Resource
 dev.acpi_sysresource.1.%driver: acpi_sysresource
 dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.SYSR
 dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=1
 dev.acpi_sysresource.1.%parent: acpi0
 dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz
 dev.acpi_timer.0.%driver: acpi_timer
 dev.acpi_timer.0.%location: unknown
 dev.acpi_timer.0.%pnpinfo: unknown
 dev.acpi_timer.0.%parent: acpi0
 dev.cpu.0.%parent: acpi0
 dev.acpi_button.0.%desc: Power Button
 dev.acpi_button.0.%driver: acpi_button
 dev.acpi_button.0.%location: handle=\_SB_.PWRB
 dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=0
 dev.acpi_button.0.%parent: acpi0
 dev.acpi_button.1.%desc: Sleep Button
 dev.acpi_button.1.%driver: acpi_button
 dev.acpi_button.1.%location: handle=\_SB_.SLPB
 dev.acpi_button.1.%pnpinfo: _HID=PNP0C0E _UID=0
 dev.acpi_button.1.%parent: acpi0
 dev.acpi_button.1.wake: 1
 dev.pcib.0.%parent: acpi0
 dev.atpic.0.%parent: acpi0
 dev.atdma.0.%parent: acpi0
 dev.attimer.0.%parent: acpi0
 dev.attimer.1.%parent: acpi0
 dev.npxisa.0.%parent: acpi0
 dev.fdc.0.%parent: acpi0
 dev.sio.0.%parent: acpi0
 dev.sio.1.%parent: acpi0
 dev.ppc.0.%parent: acpi0
 dev.psmcpnp.0.%parent: acpi0
 dev.atkbdc.0.%parent: acpi0
 
 br
 db

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
Date: Mon, 27 Sep 2004 17:00:04 +0200

 db <db@traceroute.dk> 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

From: db <db@traceroute.dk>
To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: i386/71392: 5.3-Beta2 crash
Date: Mon, 27 Sep 2004 17:39:18 +0200

 On Monday 27 September 2004 17:00, you wrote:
 > 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?
 
 Nope, normally when you report a bug to a mailling list, they tell you to use 
 pr-send.
 
 > > Maybe a stupid question, but how? I found
 >
 > Select "Boot FreeBSD with ACPI disabled" in the boot menu.
 
 Doh! Hehe, done that and when writing "shutdown -p now" it just says:
 The operating system has halted.
 Please press any key to reboot.
 
 br
 db

From: db <db@traceroute.dk>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: i386/71392: 5.3-Beta[2-5] crash after final sync when powering off
Date: Thu, 30 Sep 2004 10:22:45 +0200

 Sometimes my computer can't find my (new) Level1 gigabit card (realtek chip, 
 so it use the re driver). When my NIC is _not_ found, I can use "shutdown -p 
 now" without freebsd crashing.
 
 br
 db
State-Changed-From-To: open->closed 
State-Changed-By: remko 
State-Changed-When: Thu Oct 27 15:15:45 GMT 2005 
State-Changed-Why:  
I requested feedback from the submitted and he indicates that the problem 
is no longer acurate. So with this; close the PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71392 
>Unformatted:
