Date: Wed, 13 Oct 2004 13:47:23 -0400 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: panic: process 32827(tcpblast):2 holds Giant but isn't blocked on a lock Message-ID: <200410131347.23035.jhb@FreeBSD.org> In-Reply-To: <20041013075048.GA88808@peter.osted.lan> References: <20041013075048.GA88808@peter.osted.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 13 October 2004 03:50 am, Peter Holm wrote: > This is with GENERIC HEAD from Oct 12 12:56 UTC. More info @ > http://www.holm.cc/stress/log/cons84.html The thread is in the state TDS_CAN_RUN so it's runnable but not on a run queue or running. The only way that I know that this can happen is if priority propagation happens after the system has already panic'd in which case you are about to deadlock anyhow since you are blocking on a lock owned by a thread that will never get to run again. You can try adjusting propagate_priority() to treat TD_CAN_RUN(td) the same as TD_IS_RUNNING(td) and maybe you will get your original panic message. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410131347.23035.jhb>