On Thu, 15 Jan 2009, Rainer Gerhards wrote: > On Fri, 2009-01-16 at 01:20 +0100, Michael Biebl wrote: >> Given the -c4 command line argument, I'd expect it to be 4.1.3. >> >> Sounds familiar to >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509292 (which is >> 3.18.6). >> >> It seems to be a more general problem with multi core (= very fast??) >> systems. > > Yes, that is what my analysis so far points to. It's also part of the > problem, because I do not have very fast hardware to reproduce the issue > (and it is also not easy to reliably reproduce if you have...). > > I've gotten a couple of reports (I think most on the mailing list) on > such problems and all they have in common is 4+ core machines. > > I'll try to get hold based on what Lorenzo submits. In his environment, > the problem seems to occur most reliably (he probably has the fastest > machine...). > > Lorenzo: details follow soon.
I just got some time to work on this sort of thing again. my test system is a 4-socket (dual core) opteron system with 16g of ram I've done a fair amount of stress testing of the system without lockups (around the time the 4.1 branch started) if you can describe a test setup I can see about reproducing it. David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
