Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Apr 2004 23:02:40 +0200
From:      Harald Schmalzbauer <h@schmalzbauer.de>
To:        freebsd-current@freebsd.org
Cc:        Dmitry Morozovsky <marck@rinet.ru>
Subject:   Re: "sleeping without a mutex" panic with FixitCD from today's SNAP
Message-ID:  <200404122302.45399.h@schmalzbauer.de>
In-Reply-To: <20040410233958.S72270@woozle.rinet.ru>
References:  <20040410134802.J60704@woozle.rinet.ru> <40780DB5.1080006@freebsd.org> <20040410233958.S72270@woozle.rinet.ru>

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

--Boundary-02=_1PweAGqEYaEHNvn
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Samstag, 10. April 2004 21:41 schrieb Dmitry Morozovsky:
> On Sat, 10 Apr 2004, Scott Long wrote:
>
> SL> Cordula's Web wrote:
> SL> >>Trying to boot freshly compiled (via current-on-stable vay, mostly
> described in SL>
> >>http://groups.google.com/groups?hl=3Den&lr=3D&ie=3DUTF-8&oe=3DUTF-8&c2c=
off=3D1&selm
>=3D20040319034905.GA975%40doom.homeunix.org) SL> >>-current LiveFS CD on t=
hree
> different machines (all i686-like, from AMD Duron SL> >>600 on VIA KT133 =
to
> AthlonXP 2k+ on nVidia nForce2; all with ATACI CD/DVD) I SL> >>got 100%
> reproducible ddb panic after mounting CD with "Fixit" menu item: SL> >>
> SL> >>panic: sleeping without a mutex
> SL> >>at line 144 in file /usr/src/sys/kern/kern_synch.c
> SL> >
> SL> >
> SL> > Same here, while trying to upgrade from 5.2.1-RELEASE to yesterday's
> SL> > and today's -CURRENT. It happens here:
> SL> >
> SL> > # make installkernel KERNCONF=3DGENERIC
> SL> > # reboot   (in single user mode)
> SL> > # mount -a
> SL> > # mergemaster -p
> SL> > # make installworld
> SL> > <panic: sleeping without a mutex
> SL> > at line 144 in file /usr/src/sys/kern/kern_synch.c>
> SL> >
> SL> > The panic is 100% reproducible.
> SL>
> SL> Providing a backtrace from the debugger here is very important.  Any
> SL> chance that you could do that?

Increadible that nobody has recognized it for that long time. I'll find a=20
spare machine tomorrow and do a backtrace (what I know about this is to typ=
e=20
"trace" after I see the ddb>. Sorry, I'm no programmer, otherwise I'd have=
=20
tried to manifest this several weeks ago.) Please correct me if you need=20
something else.
More tomorrow evening, I don't have permission to do things like that at=20
work :(

=2DHarry

>
> My chances are pretty low, as I have no -current systems runnning. I cat
> write ddb's traceback though if it's helpful (supposedly, I also can make
> serial console for that).
>
> Sincerely,
> D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
> ------------------------------------------------------------------------
> *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
> ------------------------------------------------------------------------
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

--Boundary-02=_1PweAGqEYaEHNvn
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQBAewP1Bylq0S4AzzwRAi2vAJ4wCWXMUDJuYO2OV5xvuDDHHsPlbACgj5T8
3VrZIgCKFemnzNQx43Hit/0=
=V5LF
-----END PGP SIGNATURE-----

--Boundary-02=_1PweAGqEYaEHNvn--



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