On 2009-05-10 10:25 +0200, Aurelien Jarno wrote: > On Sun, May 10, 2009 at 09:18:56AM +0200, Sven Joachim wrote: >> >> 2.6.28.10 does not show the problem (repeated the test a few dozen >> times), but all 2.6.29 kernels I've tested have it, including Debian's >> official 2.6.29-2-amd64 package. Under 2.6.30-rc5 the test fails as >> well. >> >> Which kernel do you use? > > I am using a 2.6.28-1-amd64, while the build daemons are using a > 2.6.26-2-amd64 one, that's probably why I am not able to reproduce the > problem.
It seems I found out the reason why the test fails on my system. To protect myself against fork bombs, I've put the following values into /etc/security/limits.conf: ,---- | * soft nproc 250 | * hard nproc 400 `---- Apparently these limits are too low for the high number of threads that tst-eintr1 creates, so it gets the EAGAIN error. Something regarding thread handling must have changed between 2.6.28 and 2.6.29. Looks like I have to experiment with the nproc limit, but the bug should probably be closed or reassigned to linux-2.6. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
