From owner-freebsd-current@FreeBSD.ORG  Thu Aug 21 14:02:21 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A3A8E106567A
	for <freebsd-current@freebsd.org>; Thu, 21 Aug 2008 14:02:21 +0000 (UTC)
	(envelope-from ed@hoeg.nl)
Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211])
	by mx1.freebsd.org (Postfix) with ESMTP id 6412E8FC1C
	for <freebsd-current@freebsd.org>; Thu, 21 Aug 2008 14:02:21 +0000 (UTC)
	(envelope-from ed@hoeg.nl)
Received: by palm.hoeg.nl (Postfix, from userid 1000)
	id 6D8FB1CE61; Thu, 21 Aug 2008 16:02:20 +0200 (CEST)
Date: Thu, 21 Aug 2008 16:02:20 +0200
From: Ed Schouten <ed@80386.nl>
To: kevin <kevinxlinuz@163.com>
Message-ID: <20080821140220.GK99951@hoeg.nl>
References: <747dc8f30808201223i46ba04daw34c267574ba7cc99@mail.gmail.com>
	<20080820201226.GI99951@hoeg.nl>
	<20080820203238.GF1803@deviant.kiev.zoral.com.ua>
	<3c1674c90808201438p2751d7f7x3f5ee892310201c8@mail.gmail.com>
	<747dc8f30808210529s329bed21iea29ae5c0c28b793@mail.gmail.com>
	<48AD6EC3.5000507@163.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="+SjOtuBPz8meD6md"
Content-Disposition: inline
In-Reply-To: <48AD6EC3.5000507@163.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: 8.0-CURRENT kernel panic on system boot
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Thu, 21 Aug 2008 14:02:21 -0000


--+SjOtuBPz8meD6md
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Kevin,

* kevin <kevinxlinuz@163.com> wrote:
> Hi,
>    I update to the newest source tree and rebuild kernel(with zfs =20
> patch).kernel panic on system startup.Should I rebuild world?
> ......
> Starting gdm.
> Sleeping thread (tid 100068,pid 1145) owns a non-sleepable lock
                   ^^^^^^^^^^^^^^^^^^^
> sched_switch() at sched_switch+0x184
> mi_switch() at mi_switch+0x21b
> sleepq_switch() at sleepq_switch+0xfa
> sleepq_wait() at sleepq_wait+0x46
> _sx_slock_hard() at _sx_slock_hard+0x169
> _sx_slock() at _sx_slock+0x6b
> acct_process() at acct_process+0x24b
> exit1() at exit1+0x3e8
> sys_exit() at sys_exit+0xe
> syscall() at syscall+0x1dd
> Xfast_syscall() at Xfast_syscall+0xab
> --- syscall (1, FreeBSD ELF64, sys_exit), rip =3D 0x80094dd0c, rsp =3D =
=20
> 0x7fffffffcdf8, rbp =3D 0x62d548 ---
> panic: sleeping thread
> cpuid =3D 0
> KDB: enter: panic
> [thread pid 1143 tid 100127 ]
          ^^^^^^^^^^^^^^^^^^^

It seems like the actual problem lies within a different thread. Can you
reproduce this? If so, can you get a list of locks that was held by the
offending thread?

--=20
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/

--+SjOtuBPz8meD6md
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEUEARECAAYFAkitdWwACgkQ52SDGA2eCwX2SwCeOzkUJnTwK+XJ1gKaPbIayp3e
jkcAmIuUipL1YH3yEzb7wA2Ki2xsw3U=
=zHq/
-----END PGP SIGNATURE-----

--+SjOtuBPz8meD6md--