From owner-freebsd-current@FreeBSD.ORG Fri Sep 3 17:21:29 2004 Return-Path: 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 51DDB16A4CE; Fri, 3 Sep 2004 17:21:29 +0000 (GMT) Received: from cpanel.ezone.ru (cpanel.ezone.ru [213.85.31.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0876343D2F; Fri, 3 Sep 2004 17:21:28 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [81.195.2.185] (ppp2-185.pppoe.mtu-net.ru [81.195.2.185]) (authenticated bits=0) by cpanel.ezone.ru (8.13.1/8.12.11) with ESMTP id i83HLFnF088202; Fri, 3 Sep 2004 21:21:20 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <4138A806.9020105@mcsi.pp.ru> Date: Fri, 03 Sep 2004 21:21:10 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040810 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Nate Lawson References: <4137EA5C.30606@mcsi.pp.ru> <200409031023.55561.jhb@FreeBSD.org> <4138A524.8080107@root.org> In-Reply-To: <4138A524.8080107@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mail3.ezone.ru cc: current@FreeBSD.org cc: John Baldwin Subject: Re: panic on shutdown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2004 17:21:29 -0000 Nate Lawson wrote: > John Baldwin wrote: > >> On Thursday 02 September 2004 11:51 pm, Maxim Maximov wrote: >> >>> Hello. >>> >>> I just got this panic on shutdown using Power button, hand >>> transcribed: >>> >>> Syncing disks: >>> No buffers busy after final sync >>> Uptime: 21m53s >>> Powering system off using ACPI >>> >>> panic: lock (sleep mutex) Giant not locked @ >>> /usr/src/sys/kern/kern_timeout.c:279 >>> >>> cpuid = 0 >>> KDB: enter: panic >>> ACPI power-off failed - timeout >>> >>> Rebooting... >>> cpu_reset: called on cpu#1 >>> cpu_reset: Stopping other CPUs >>> >>> Here it hung until I pressed Power button again. Then it shut down. >> >> >> Looks like the timeout/callout routine dropped Giant more than it >> acquired it. > > > I don't see how this could be triggered by ACPI. If you reboot the > system with ACPI disabled (or enabled), do you also get this message? My system can't boot with ACPI disabled. Also I want to mention that this panic is rare. I've seen it about 10 times in 2-3 months of everyday rebooting. And by the way, the command issued to shut the system down was 'halt -p' > We > don't acquire or release Giant explicitly and the device and interrupt > are both marked MPSAFE. Well, we use Giant for busdma to set up the 1 > MB trampoline in low memory for resume but that shouldn't affect this > unless there's a bug in busdma. > > BTW, why doesn't "panic" from the debugger prompt actually reset the > system any more? > > -Nate -- Maxim Maximov