From owner-freebsd-current@FreeBSD.ORG  Wed Apr  3 07:06:33 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 65626FE;
 Wed,  3 Apr 2013 07:06:33 +0000 (UTC) (envelope-from jh@FreeBSD.org)
Received: from gw03.mail.saunalahti.fi (gw03.mail.saunalahti.fi
 [195.197.172.111])
 by mx1.freebsd.org (Postfix) with ESMTP id 26CC88F1;
 Wed,  3 Apr 2013 07:06:32 +0000 (UTC)
Received: from jh (a91-153-115-208.elisa-laajakaista.fi [91.153.115.208])
 by gw03.mail.saunalahti.fi (Postfix) with SMTP id 720192167EF;
 Wed,  3 Apr 2013 10:06:23 +0300 (EEST)
Date: Wed, 3 Apr 2013 10:06:23 +0300
From: Jaakko Heinonen <jh@FreeBSD.org>
To: Andriy Gapon <avg@FreeBSD.org>
Subject: Re: poweroff (shutdown -p) is broken
Message-ID: <20130403070622.GB47068@jh>
References: <515B6677.2080402@gmail.com>
 <515BBA28.1020408@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <515BBA28.1020408@FreeBSD.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: deeptech71 <deeptech71@gmail.com>, freebsd-current@FreeBSD.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 07:06:33 -0000

On 2013-04-03, Andriy Gapon wrote:
> on 03/04/2013 02:15 deeptech71 said the following:
> > As of r248872, my system, when ordered to power off, stalls at the "Uptime:
> > [...]" message. Before that revision, the "Uptime" message would be followed by
> > several additional messages -- something related to "usb controllers" -- before
> > powering off.
> 
> You need to break into the ddb and examine where exactly the shutdown thread is
> stuck.

I can confirm the problem. It hangs while trying to spin down an ada(4)
disk.

Tracing pid 1 tid 100002 td 0xc72bbc00
sched_switch(c72bbc00,0,104,1b5,c6946188,...) at sched_switch+0x456/frame 0xc6ec4a98
mi_switch(104,0,c0f36d00,1f5,5c,...) at mi_switch+0x20b/frame 0xc6ec4ac8
sleepq_switch(c72bbc00,0,c0f36d00,26b,0,...) at sleepq_switch+0x1a5/frame 0xc6ec4af0
sleepq_wait(c72b573c,5c,c0d92504,0,0,...) at sleepq_wait+0x6b/frame 0xc6ec4b0c
_sleep(c72b573c,c732c974,5c,c0d92504,0,...) at _sleep+0x3f0/frame 0xc6ec4b64
cam_periph_getccb(c72b5700,480,c0d94762,c0,ea,...) at cam_periph_getccb+0xd7/frame 0xc6ec4b9c
adaspindown(c6ec4c2c,c0a130b6,0,4008,c0f306e7,...) at adaspindown+0xf1/frame 0xc6ec4bcc
adashutdown(0,4008,c0f306e7,1bc,c09e261a,...) at adashutdown+0x29/frame 0xc6ec4bd4
kern_reboot(4008,0,c0f306e7,be,bfbfd9a0,...) at kern_reboot+0x706/frame 0xc6ec4c2c
sys_reboot(c72bbc00,c6ec4ccc,c72bbcb4,c12164a0,202,...) at sys_reboot+0x6c/frame 0xc6ec4c4c
syscall(c6ec4d08) at syscall+0x2ab/frame 0xc6ec4cfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xc6ec4cfc
--- syscall (55, FreeBSD ELF32, sys_reboot), eip = 0x805c0a7, esp = 0xbfbfd86c, ebp = 0xbfbfd948 ---

-- 
Jaakko