Date: Wed, 19 Dec 2007 12:06:59 -0500 From: Mark Fullmer <maf@eng.oar.net> To: Bruce Evans <brde@optusnet.com.au> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Packet loss every 30.999 seconds Message-ID: <814DB7A9-E64F-4BCA-A502-AB5A6E0297D3@eng.oar.net> In-Reply-To: <20071220011626.U928@besplex.bde.org> References: <D50B5BA8-5A80-4370-8F20-6B3A531C2E9B@eng.oar.net> <20071217102433.GQ25053@tnn.dglawrence.com> <CD187AD1-8712-418F-9F49-FA3407BA1AC7@eng.oar.net> <20071220011626.U928@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 19, 2007, at 9:54 AM, Bruce Evans wrote: > On Tue, 18 Dec 2007, Mark Fullmer wrote: > >> A little progress. >> >> I have a machine with a KTR enabled kernel running. >> >> Another machine is running David's ffs_vfsops.c's patch. >> >> I left two other machines (GENERIC kernels) running the packet >> loss test >> overnight. At ~ 32480 seconds of uptime the problem starts. This >> is really > > Try it with "find / -type f >/dev/null" to duplicate the problem > almost > instantly. I was able to verify last night that (cd /; tar -cpf -) > all.tar would trigger the problem. I'm working getting a test running with David's ffs_sync() workaround now, adding a few counters there should get this narrowed down a little more. Thanks for the other info on timer resolution, I overlooked clock_gettime(). -- mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?814DB7A9-E64F-4BCA-A502-AB5A6E0297D3>