Date: Sat, 14 Sep 2002 05:20:04 -0700 (PDT) From: Hiten Pandya <hitmaster2k@yahoo.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/42770: MUTEX_DEBUG broke CURRENT kernel Message-ID: <200209141220.g8ECK4Cg017906@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/42770; it has been noted by GNATS. From: Hiten Pandya <hitmaster2k@yahoo.com> To: Dan Lukes <dan@obluda.cz>, FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/42770: MUTEX_DEBUG broke CURRENT kernel Date: Sat, 14 Sep 2002 05:15:48 -0700 (PDT) --- Dan Lukes <dan@obluda.cz> wrote: > >Number: 42770 > >Category: kern > >Synopsis: MUTEX_DEBUG broke CURRENT kernel > >Arrival-Date: Sat Sep 14 05:10:02 PDT 2002 > >Originator: Dan Lukes > >Release: FreeBSD 5.0-CURRENT i386 > >Description: > MUTEX_DEBUG cause "mutex Giant not owned at vm_map.c:383" (it's triggered > during mounting root). The content of stack: [ snip ] > >How-To-Repeat: > Compile kernel with MUTEX_DEBUG > >Fix: > workaround - doesn't compile kernel with MUTEX_DEBUG > I can't supply the fix, but see the note in mtx_validate > (kern_mutex.c) - it seems to be valid not only on alphas. Hello Dan. Problems which happen in the development (-CURRENT) version of FreeBSD should not be reported via Problem Reports. Instead, you should report these to the freebsd-current@ mailing list, which, deals with all kinds of stuff related to -CURRENT. For the problem, a fix has been committed by Julian Elischer from Jonathan Mini's perforce tree. The code in vm_map.c required that Giant be aqquired. Please update your sources, and rebuild. This PR can be closed. Thanks. -- Hiten Pandya __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209141220.g8ECK4Cg017906>