Date: Sun, 16 Nov 2003 14:30:20 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: davidxu@freebsd.org Subject: Re: KSE/ia64 broken Message-ID: <Pine.GSO.4.10.10311161414290.29933-100000@pcnet5.pcnet.com> In-Reply-To: <20031116182219.GB60377@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 16 Nov 2003, Marcel Moolenaar wrote: > On Sun, Nov 16, 2003 at 12:18:33PM -0500, Daniel Eischen wrote: > > > > Are you sure there's not an ia64 kernel bug or ia64 context > > restoring bug? > > There's nothing pointing in that direction yet. I keep thinking > that the case is related to having TP per thread on ia64, while > it's per KSE on i386. If you noop the spinlock/spinunlock, the problem still occurs. > > The critical region may be the malloc spinlock being held > > and the reason it blocked perhaps due to a page fault. Is > > it possible that the blocked context is incorrectly marked, > > or that it is just not being resumed properly? > > The likelylood that it's incorrectly marked is larger than > the likelyhood that it's improperly resumed. What should I be looking at, [um]c_flags? $ simple Found completed thread 6000000000014000, uc_flags 0x0, mc_flags 0x8, name initial thread Switching out thread 6000000000014000, state 0 Threads in waiting queue: Found completed thread 6000000000014000, uc_flags 0x0, mc_flags 0x3, name initial thread Switching out thread 6000000000014000, state 0 Threads in waiting queue: Found completed thread 6000000000014000, uc_flags 0x0, mc_flags 0x3, name initial thread Switching out thread 6000000000014000, state 0 Threads in waiting queue: Found completed thread 6000000000014000, uc_flags 0x0, mc_flags 0x3, name initial thread Switching out thread 6000000000014000, state 0 Threads in waiting queue: ... -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10311161414290.29933-100000>