Date: Tue, 14 Sep 2004 00:48:51 -0700 From: Julian Elischer <julian@elischer.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-threads@freebsd.org Subject: Re: Unkillable KSE threaded proc Message-ID: <4146A263.2020603@elischer.org> In-Reply-To: <16704.52569.375858.857614@grasshopper.cs.duke.edu> References: <16703.11479.679335.588170@grasshopper.cs.duke.edu> <16703.12410.319869.29996@grasshopper.cs.duke.edu> <413F55B8.50003@elischer.org> <16703.28031.454342.774229@grasshopper.cs.duke.edu> <413F8DBB.5040502@elischer.org> <16704.40876.708925.425911@grasshopper.cs.duke.edu> <4140AA2A.90605@elischer.org> <16704.45327.42494.922427@grasshopper.cs.duke.edu> <4140C04D.1060906@elischer.org> <16704.52569.375858.857614@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4146A263.2020603>