On Thu, 18 Sep 2008, Dâniel Fraga wrote: > On Wed, 17 Sep 2008 13:23:28 +0300 (EEST) > "Ilpo Järvinen" <ilpo.jarvinen@xxxxxxxxxxx> wrote: > > > There were some other timer related complications in 2.6.25 but it's so > > long time ago that I hardly remember anything about those anymore (and > > I'm not an expert on those things anyway). And it's still very open issue > > how that would cause the problem you're seeing. > > I opened a bug report to timer developers... > let's see if they can help: > > http://bugzilla.kernel.org/show_bug.cgi?id=11588 Ok. Another potential candidate might be scheduler (my wording was sloppy when I used "timer related complications" while time related was my main intention)... Anyway, if/when you succeed collecting some strace of the server processes, please let me know (though putting a full one available might not be wise thing like I said earlier). After I thought it a bit, it might be enough the start the strace with -p for all server processes of a service during a stall and then resolve it after some amount of waiting with nmap (and hope that strace doesn't resolve it by interfering something relevant :-), you will see that from the fact that it resolves without nmap then). That would probably reveal if the processes where waiting in accept() or not, and if not, where they were. -- i.
