Date: Tue, 3 Feb 2009 04:19:33 -0800 From: Sergey S <ad.sergey@gmail.com> To: Mikolaj Golub <to.my.trociny@gmail.com> Cc: remko@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: misc/131290: How to completely freeze FreeBSD 7.1 under a non-privileged user Message-ID: <ab09a9970902030419j92add19y837afc7aa871aabb@mail.gmail.com> In-Reply-To: <817i47oibn.fsf@zhuzha.ua1> References: <200902021314.n12DEwd3098744@freefall.freebsd.org> <ab09a9970902021213h6e58a1b4o56bcfabb2e5da3e6@mail.gmail.com> <817i47oibn.fsf@zhuzha.ua1>
next in thread | previous in thread | raw e-mail | index | archive | help
--0016e6dd98f11ca30e046202af46 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Help. Thanks for your answer. > I have tried your scripts and have not managed to reproduce the hang, even > running the loop script without sleep. It's very strange, because the bug is 100% reprodusable to me (on two separate computers) :( > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html Thanks for your suggestion. I hope it will help. > But I would recommend you to start from simpler techniques, e.g. running in > parallel top and other system utilities and writing the output to the file for > further investigation. Something like this: > > top -b -s1 -S -d1000 1000 > top.output & > ./gistfile1.sh I've done it. gzipped top.output is attached to this letter. -- Sergey --0016e6dd98f11ca30e046202af46--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab09a9970902030419j92add19y837afc7aa871aabb>