Date: Sat, 29 Oct 2005 11:01:21 -0500 From: Philip Kizer <pckizer@nostrum.com> To: freebsd-current@freebsd.org Subject: Re: Problem remains with FreeBSD 6.0-RC1 as seen in RELENG_5 Message-ID: <0906B09C-B5A2-402E-BF39-57EBB20B2D4F@nostrum.com> In-Reply-To: <33E53AA7-2A01-4BBE-9674-8F54E008D0A8@nostrum.com> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> <20051019175020.S60849@fledge.watson.org> <D7CA644A-E98B-4CB6-BA4C-26CCFE63326A@nostrum.com> <20051025110453.L6720@fledge.watson.org> <2E18CEAE-2A72-4387-B92E-DAED7CC7FACD@nostrum.com> <33E53AA7-2A01-4BBE-9674-8F54E008D0A8@nostrum.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 25, 2005, at 05:07, Robert Watson wrote:
> There are a couple of possible sources, so if this is reproduceable
> and you don't mind trying some diagnostic patches, I've attached a
> first one below. This checks for the case where the looping in the
> unp_gc() routine becomes unbounded due to a possible lack of
> synchronization in the handling of marking and counting of
> marking. It needs INVARIANTS to be compiled in to work; if it
> fires, this will suggest an avenue to explore.
Well, it's been a few days since the last time I heard from anyone
that had been helping me with this and I only recall seeing one
diagnostic patch to apply (that does not seem to have been triggered
in subsequent hangs).
Have there been any more patches I've missed that would help either
the problem or diagnostics?
With that, I had another pair of examples last night again, one for
each version of the OS:
http://www.nostrum.com/hang/hang.RELENG_6-trace-2005-10-29-0.txt
http://www.nostrum.com/hang/hang.RELENG_5-trace-2005-10-29-0.txt
Any other suggestions or pointers on how to identify this livelock?
Thank you,
Philip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0906B09C-B5A2-402E-BF39-57EBB20B2D4F>