Date: Thu, 9 Sep 2004 15:37:51 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Julian Elischer <julian@elischer.org> Cc: freebsd-threads@freebsd.org Subject: Re: Unkillable KSE threaded proc Message-ID: <16704.45327.42494.922427@grasshopper.cs.duke.edu> In-Reply-To: <4140AA2A.90605@elischer.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer writes: > thanks, > I'm flooded with work for a couple of days.. Me too.. Sorry for the terribly latency in giving you more info. > it looks as if one ofthe threads (0xc1b614b0) has called exit, > whichmeans it is in thread_single() > waiting for all the other threads to suicide, but at least one of them > doen't want to.. > > Two of them (0xc1b61320 and 0xc2b6ce10) are refusing to finish up and exit > because they need the proc lock, which is owned by a fourth one.. > (0xc1b617d0) > > the fourth one has just preempted itself with some other thread > (3244003328 whatever that is in > hex (0xC15B9000)) do you still have the 'ps'? > what is thread (0xC15B9000)? > No, but I've got the dump. It looks like it was preempted by the fxp ethernet driver's ithread: (kgdb) p ((struct thread*)0xC15B9000)->td_proc->p_comm $7 = "irq31: fxp0\0\0\0\0\0\0\0\0" Maybe this would be easier to debug if I disabled preemption? % cat opt_sched.h #define PREEMPTION 1 #define SCHED_4BSD 1 Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16704.45327.42494.922427>