Date: Fri, 24 Apr 2009 08:04:51 +0400 From: pluknet <pluknet@gmail.com> To: Robert Watson <rwatson@freebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: panic in soabort Message-ID: <a31046fc0904232104w380b7dabr1168b3df970c542a@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.0904231038550.54334@fledge.watson.org> References: <a31046fc0904230118m184b50adnd2cebb4d610f94ca@mail.gmail.com> <alpine.BSF.2.00.0904231038550.54334@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/4/23 Robert Watson <rwatson@freebsd.org>: > On Thu, 23 Apr 2009, pluknet wrote: > >> Please, give me comment on this. The panic is on 6.2-REL. Is it known to >> be fixed in the latter releases? > > It may well be -- there have been quite significant architectural > improvements to socket life cycle (etc) between 6.2 and 7.x releases, which > may well close the race causing this panic. However, we'll probably need to > learn a bit more in order to decide for sure. Could you convert the > trapping instruction pointer to file+offset in the source code? Looks I've lost the corresponding kernel.debug. Anyway I have such bt the first time. -- wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0904232104w380b7dabr1168b3df970c542a>