Date: Mon, 24 Jul 2006 17:19:22 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org, Yablochkin Walery <orm_vartis@freemail.ru> Cc: current@freebsd.org Subject: Re: Panic on amd64 (and i386?) Message-ID: <200607241719.23168.jhb@freebsd.org> In-Reply-To: <132106974.20060723214923@bk.ru> References: <20060723124037.GI64253@submonkey.net> <132106974.20060723214923@bk.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 23 July 2006 13:49, Walery wrote: > Sorry, my english is bad :( > > pcpu.h is broken? Nah, not in your case. > Panic on pcpu.h:166 on my i386-box on high load (make -j3 buildworld + xmms music + > glxgears full screen): > > at /usr/home/cvs-snap/freebsd/current/src/sys/i386/i386/trap.c:279 > #5 0xc068a69a in calltrap () at /usr/home/cvs-snap/freebsd/current/src/sys/i386/i386/exception.s:138 > #6 0xc0531cbb in propagate_priority (td=0xc4172b40) > at /usr/home/cvs-snap/freebsd/current/src/sys/kern/subr_turnstile.c:246 This is generally the result of a thread sleeping while holding a mutex. If your sources are up to date then it should have spit out a stack trace of the misbehaving thread on the console before panic'ing. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607241719.23168.jhb>