Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Apr 2004 12:55:11 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Tuc <tuc@ttsg.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Stopevent / Lock order reversal / etc
Message-ID:  <20040408195510.GA38781@xor.obsecurity.org>
In-Reply-To: <200404081259.i38CxP3l027436@himinbjorg.tucs-beachin-obx-house.com>
References:  <200404081259.i38CxP3l027436@himinbjorg.tucs-beachin-obx-house.com>

next in thread | previous in thread | raw e-mail | index | archive | help

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

On Thu, Apr 08, 2004 at 08:59:25AM -0400, Tuc wrote:
> Hi,
>=20
> 	JUST brought up a 5.2.1-R-p4 system and am putting INN on it, and
> I'm getting:
>=20
> Apr  8 08:53:54 vjofn2 kernel: Sleeping on "stopevent" with the following=
 non-sl
> eepable locks held:
> Apr  8 08:53:54 vjofn2 kernel: exclusive sleep mutex sigacts r =3D 0 (0xc=
8c90aa8)=20
> locked @ /usr/src/sys/kern/kern_condvar.c:457
> Apr  8 08:53:54 vjofn2 kernel: lock order reversal
> Apr  8 08:53:54 vjofn2 kernel: 1st 0xc8c90aa8 sigacts (sigacts) @ /usr/sr=
c/sys/k
> ern/kern_condvar.c:457
> Apr  8 08:53:54 vjofn2 kernel: 2nd 0xc89e306c process lock (process lock)=
 @ /usr
> /src/sys/kern/kern_synch.c:309
> Apr  8 08:53:54 vjofn2 kernel: Stack backtrace:
> Apr  8 08:53:54 vjofn2 kernel: Sleeping on "stopevent" with the following=
 non-sl
> eepable locks held:
> Apr  8 08:53:54 vjofn2 kernel: exclusive sleep mutex sigacts r =3D 0 (0xc=
8c90aa8)=20
> locked @ /usr/src/sys/kern/subr_trap.c:260
> Apr  8 08:53:54 vjofn2 kernel: Sleeping on "stopevent" with the following=
 non-sl
> eepable locks held:
> Apr  8 08:53:54 vjofn2 kernel: exclusive sleep mutex sigacts r =3D 0 (0xc=
8c90aa8)=20
> locked @ /usr/src/sys/kern/subr_trap.c:260
> Apr  8 08:56:10 vjofn2 kernel: Sleeping on "stopevent" with the following=
 non-sl
> eepable locks held:
> Apr  8 08:56:10 vjofn2 kernel: exclusive sleep mutex sigacts r =3D 0 (0xc=
8c90aa8)=20
> locked @ /usr/src/sys/kern/kern_condvar.c:457
> Apr  8 08:56:10 vjofn2 kernel: Sleeping on "stopevent" with the following=
 non-sl
> eepable locks held:
> Apr  8 08:56:10 vjofn2 kernel: exclusive sleep mutex sigacts r =3D 0 (0xc=
8c90aa8)=20
> locked @ /usr/src/sys/kern/subr_trap.c:260
> Apr  8 08:56:10 vjofn2 kernel: Sleeping on "stopevent" with the following=
 non-sl
> eepable locks held:
> Apr  8 08:56:10 vjofn2 kernel: exclusive sleep mutex sigacts r =3D 0 (0xc=
8c90aa8)=20
> locked @ /usr/src/sys/kern/subr_trap.c:260
>=20
> 	EH?!  What is this trying to tell me?

That you're seeing evidence of kernel bugs.  Report to
current@FreeBSD.org, although they might already be fixed in
5.2-CURRENT.

Kris

--fdj2RfSjLxBAspz7
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAda4eWry0BWjoQKURAmEHAJ9A6Y5bb3Um2wBq2r7y3hez4nlUVgCfTPxN
upplOlb9W3HedYKuvll3r7c=
=8ouD
-----END PGP SIGNATURE-----

--fdj2RfSjLxBAspz7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040408195510.GA38781>