From owner-freebsd-current@FreeBSD.ORG Fri Sep 3 18:07:14 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 74DEB16A4CF for ; Fri, 3 Sep 2004 18:07:14 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4174543D48 for ; Fri, 3 Sep 2004 18:07:14 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 24024 invoked from network); 3 Sep 2004 18:07:14 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 3 Sep 2004 18:07:13 -0000 Received: from [10.50.41.228] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i83I79X4077042; Fri, 3 Sep 2004 14:07:10 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Fri, 3 Sep 2004 13:41:47 -0400 User-Agent: KMail/1.6.2 References: <4137EA5C.30606@mcsi.pp.ru> <4138A524.8080107@root.org> <4138A806.9020105@mcsi.pp.ru> In-Reply-To: <4138A806.9020105@mcsi.pp.ru> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409031341.47074.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Maxim Maximov cc: current@FreeBSD.org cc: Nate Lawson 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 18:07:14 -0000 On Friday 03 September 2004 01:21 pm, Maxim Maximov wrote: > 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' I would hack the timeout code to add some printf's before the mtx_unlock(&Giant) to dump the function pointer and argument if !tmtx_owned(&Giant) and then use gdb to figure out what the callout function was. I.e. something like: if (not mpsafe) { if (!mtx_owned(&Giant)) printf("func = %p, arg = %p\n", c_func, c_arg) mtx_unlock(&Giant); } -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org