Unkillable KSE threaded proc
julian at elischer.org
Tue Sep 14 00:48:56 PDT 2004
Andrew Gallatin wrote:
> Julian Elischer writes:
> > I think that this would possibly GO AWAY of you disab;ed preemption.
> > which would make it very hard to debug :-)
> Nope, still happens w/o preempt.. And its the "worse" problem of deadlocking
> the system rather than just having the process fail to exit.
> db> ps
> pid proc uarea uid ppid pgrp flag stat wmesg wchan cmd
> 579 c37e41c0 e8855000 1387 578 579 0004002 [SLPQ ttyin 0xc17df810][SLP] csh
> 578 c1817540 e671a000 1387 576 576 0000100 [SLPQ select 0xc06cb704][SLP] sshd
> 576 c37e4540 e8857000 0 451 576 0000100 [SLPQ sbwait 0xc1983e84][SLP] sshd
> 566 c1a1fc40 e67ba000 1387 1 564 000c482 (threaded) mx_pingpong
> thread 0xc37944b0 ksegrp 0xc1a20460 [CPU 0]
> thread 0xc3794640 ksegrp 0xc1a20460 [SUSP]
> thread 0xc187e320 ksegrp 0xc1a20460 [RUNQ]
> thread 0xc187e4b0 ksegrp 0xc187fee0 [CPU 1]
can you reconfirm that this probelm exists without preemption with today's -current?
More information about the freebsd-threads