Re: panic: process 32827(tcpblast):2 holds Giant but isn't blocked on a lock
From: John Baldwin (jhb_at_FreeBSD.org)
Date: 10/13/04
- Previous message: Robert Huff: "network slowness/freez-up since update 10/11"
- In reply to: Peter Holm: "panic: process 32827(tcpblast):2 holds Giant but isn't blocked on a lock"
- Next in thread: John Baldwin: "Re: panic: process 32827(tcpblast):2 holds Giant but isn't blocked on a lock"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: freebsd-current@FreeBSD.org Date: Wed, 13 Oct 2004 13:47:23 -0400
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 _______________________________________________ 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"
- Previous message: Robert Huff: "network slowness/freez-up since update 10/11"
- In reply to: Peter Holm: "panic: process 32827(tcpblast):2 holds Giant but isn't blocked on a lock"
- Next in thread: John Baldwin: "Re: panic: process 32827(tcpblast):2 holds Giant but isn't blocked on a lock"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
