Date: Tue, 5 Apr 2005 22:22:08 +0200 From: Shaun Jurrens <shaun@shamz.net> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-stable@freebsd.org Subject: Re: recent 5.4-PRE regression: Could not resync/reset buffers Message-ID: <20050405202208.GI19717@atreides.freenix.no> In-Reply-To: <20050402234453.GA2430@xor.obsecurity.org> References: <20050401204142.GE19717@atreides.freenix.no> <20050401190457.S94922@carver.gumbysoft.com> <20050402233950.GG19717@atreides.freenix.no> <20050402234453.GA2430@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 02, 2005 at 03:44:53PM -0800, Kris Kennaway wrote: #> On Sun, Apr 03, 2005 at 01:39:50AM +0200, Shaun Jurrens wrote: #> #> > The trace doesn't look too wierd, otherwise. There was a warning about #> > having libm.so.2 and libm.so.3 causing a potential conflict during #> > compile... It seems to find the correct lib, but later also opens libm.so.2 #> #> That's a problem on your system that you should fix, then. It may not #> be the cause of this problem, but it can definitely cause problems and #> you need to rule it out. Ok, I've cleaned all of the relevant apps av libm.so.2 . The behavior still exihibits itself very often (90% of the time) but I can't catch it with ktrace. I've started playing with malloc.conf options to see if I can see if there's a problem there. It doesn't appear to be the correct approach yet, but... I can't kill then hanging mpg123 from the same tty either. It has to be killed from another prompt. #> #> Kris -- Yours truly, Shaun D. Jurrens shaun@shamz.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050405202208.GI19717>