Date: Fri, 11 Jan 2008 12:49:29 -0500 From: "J.R. Oldroyd" <fbsd@opal.com> To: freebsd-stable@freebsd.org Subject: Re: RELENG_7 2008/01/10 desktop system also periodically freezes Message-ID: <20080111124929.4aed2471@linwhf.opal.com> In-Reply-To: <4785C9FC.4090102@FreeBSD.org> References: <1199812249.96494.133.camel@predator-ii.buffyverse> <4783C8A8.2090705@raad.tartu.ee> <4783D41B.3000204@FreeBSD.org> <4783D748.1050401@raad.tartu.ee> <4783D824.1050502@FreeBSD.org> <4783DB72.6030605@raad.tartu.ee> <4783DCAA.1080108@FreeBSD.org> <4783EA7E.1050008@raad.tartu.ee> <4783ED15.1060606@FreeBSD.org> <20080109141859.74d08743@linwhf.opal.com> <478522B5.5030101@FreeBSD.org> <20080109235819.7707133d@linwhf.opal.com> <4785C9FC.4090102@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Thu, 10 Jan 2008 08:32:12 +0100, Kris Kennaway <kris@freebsd.org> wrote:
>
> J.R. Oldroyd wrote:
> > On Wed, 09 Jan 2008 20:38:29 +0100, Kris Kennaway <kris@freebsd.org> wrote:
> >>
> >> OK, same requests as to the others then.
> >>
> >
> > I presume you mean hwpmc...
>
> LOCK_PROFILING, sched_graph, hwpmc.
>
Quick update on this so that folk know what's going on.
Firstly, I've updated the code here to RELENG_7 csup'd yesterday and
if I run a "normal" kernel, without debugging, I do see the same freezes
with that, too.
Secondly, I am unable to process hwpcm dumps using pmcstat because it
core dumps when using the "-R" option to decode a dump. I will talk to
jkoshy@ about that.
I am now running a kernel with LOCK_PROFILING. I am able to create a
freeze due to the softupdate activity by removing a large file; a lock
profile captured surrounding such a freeze can be seen here:
http://opal.com/jr/freebsd/releng_7-freeze/200801111135-softupdate.txt
This is easily repeatable. The sequence is:
create 1.5GB file
sysctl debug.lock.prof.enable=1
rm file
... wait, moving mouse until it freezes then unfreezes ...
sysctl debug.lock.prof.enable=0
sysctl debug.lock.prof.stats
Kostik, is this of any help to you?
I have yet to experience a "random" freeze not directly attributable
to a softupdate while running the lock profiling. I am running with
lock profiling on, and resetting the profiling counters once a minute.
Yesterday and this morning, I've run for quite a while now with lock
profiling on but without a "random" freeze. I'll wait some more, but
I'm hoping that enabling the lock profiling hasn't masked the freeze.
I'll post again when I see one..
-jr
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
iD8DBQFHh6wpls33urr0k4kRAsXdAJ9h67XcwRkRRfmqXjx10yVNXoDS3ACfUArw
5OyxCn3OCc3f2pa/+hWNH0k=
=0L4D
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080111124929.4aed2471>