Date: Fri, 27 Jun 2008 16:21:07 +0400 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Ali Niknam <freebsd-net@transip.nl> Cc: net@freebsd.org Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state... Message-ID: <c9uXVuSzhJDd2VY%2Bhw9uuGe5NAg@3xQSkDAynh8xLl8Q/P9pjshN3Fo> In-Reply-To: <48648D70.50304@transip.nl> References: <486283B0.3060805@transip.nl> <5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc> <48648D70.50304@transip.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Ali, good day. Fri, Jun 27, 2008 at 08:49:20AM +0200, Ali Niknam wrote: > > Just a quick "me too" message: I also used to see this on my 7.x > > machines. This was with Apache servers in the proxy setup: one > > I'm wondering: where these 32 bit, or 64 bit machines? amd64. > > I had already tried to debug this situation and Mike Silbersack > > helped me with patching the kernel. At that days his patches (that > > went into 7.x) helped, but with higher request rate to the Apache, > > they seem to be back again. I can try to setup the testbed and > > verify if I will still be able to reproduce them. Will it be needed? > > > > Well, if your machine was indeed 64 bit, I for one would be very > interested in knowing if it also appears in 32 bit. Have no i386 machines to test on, sorry. Moreover, I can not yet reproduce the problem on my amd64, but I am continuing experiments. -- Eygene Remember that it is hard to read the on-line manual while single-stepping the kernel. -- FreeBSD Developers handbook
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c9uXVuSzhJDd2VY%2Bhw9uuGe5NAg>