Date: Sat, 27 Mar 1999 18:12:17 +1100 From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.ORG, shalunov@att.com Subject: Re: kern/10545: When a fork/exec stress test is run, the machine locks up Message-ID: <199903270712.SAA17025@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
> > I've tried your stress test on my 4.0-CURRENT box (built today) and I > > don't get a lock-up. Instead, I get thousands of these after the first > > few seconds: The kernel virtual address space increase may hide the bug. You should get the full proc table message or hit some other resource limit in a controlled way in all configurations. > What results do you get for the default run (without arguments)? > > > Mar 26 03:15:15 axl /kernel: proc: table i > > Mar 26 03:15:15 axl /kernel: proc: table is full > > Mar 26 03:15:15 axl last message repeated 43 times > > Mar 26 03:15:15 axl /kernel: p > > Mar 26 03:15:15 axl /kernel: proc: table is full > > [...] > > I would expect something like this. (I don't quite understand why > syslogd is missing *parts* of messages--I would expect it either to > get message or to lose it,--but that's another story.) syslogd was broken by making the kernel message buffer size a variable without doing the work to actually support this (syslogd needs to use something more like getc() than read() to read the message buffer). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903270712.SAA17025>