Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Feb 2009 22:00:13 +0200
From:      Mikolaj Golub <to.my.trociny@gmail.com>
To:        Sergey S <ad.sergey@gmail.com>
Cc:        remko@freebsd.org, Mikolaj Golub <to.my.trociny@gmail.com>, freebsd-bugs@freebsd.org
Subject:   Re: misc/131290: How to completely freeze FreeBSD 7.1 under a non-privileged user
Message-ID:  <86iqnrb8aa.fsf@kopusha.onet>
In-Reply-To: <ab09a9970902030419j92add19y837afc7aa871aabb@mail.gmail.com> (Sergey S.'s message of "Tue\, 3 Feb 2009 04\:19\:33 -0800")
References:  <200902021314.n12DEwd3098744@freefall.freebsd.org> <ab09a9970902021213h6e58a1b4o56bcfabb2e5da3e6@mail.gmail.com> <817i47oibn.fsf@zhuzha.ua1> <ab09a9970902030419j92add19y837afc7aa871aabb@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Tue, 3 Feb 2009 04:19:33 -0800 Sergey S wrote:

 >> I have tried your scripts and have not managed to reproduce the hang, even
 >> running the loop script without sleep.

 SS> It's very strange, because the bug is 100% reprodusable to me (on two
 SS> separate computers) :(

Sorry, I missed previously that your system was amd64. I tried on i386 FreeBSD
7.1-STABLE. Currently, I don't have amd64 where I can install erlang and do
such tests.

 >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html

 SS> 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

 SS> I've done it. gzipped top.output is attached to this letter.

So, according to top output (I don't see the script process here) it hanged
the system in less then one second? I have observed freezes when top with -S
option froze while without -S option worked. You can try removing -S
option. But I am afraid this won't help and you will have to make the system
core dump (as described at URL above) and do post-mortem analysis of the dump.

-- 
Mikolaj Golub



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86iqnrb8aa.fsf>