Date: Tue, 12 Jun 2007 07:34:32 +0400 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Andre Oppermann <andre@freebsd.org> Cc: shigeaki@f.csce.kyushu-u.ac.jp, freebsd-net@freebsd.org, freebsd-current@freebsd.org, yongari@freebsd.org Subject: Re: nfe(4) strangeness on the 7-CURRENT Message-ID: <20070612033432.GK86872@void.codelabs.ru> In-Reply-To: <20070612032656.GJ86872@void.codelabs.ru> References: <20070611140644.GH86872@void.codelabs.ru> <466D9DDE.6090302@freebsd.org> <20070612032656.GJ86872@void.codelabs.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Me again. Tue, Jun 12, 2007 at 07:26:56AM +0400, Eygene Ryabinkin wrote: > Mon, Jun 11, 2007 at 09:09:18PM +0200, Andre Oppermann wrote: > > These messages are unrelated to your hardware. There you can relax. > > We have a bug in the TCP FSM state transitions which I'm currently > > tracking down that indirectly causes the log messages. You don't > > have to worry about it for your case. TCP connections work fine. > > OK, thank you! Just checked my netstat output and spotted weird lines: ----- tcp4 0 0 127.0.0.1.* 127.0.0.1.40001 CLOSED tcp4 0 0 127.0.0.1.* 127.0.0.1.40001 CLOSED ----- Can they be related to the bug you mentioned? -- Eygene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070612033432.GK86872>