Date: Sun, 20 Jan 2008 04:16:16 +1030 From: Wayne Sierke <ws@au.dyndns.ws> To: Kris Kennaway <kris@freebsd.org> Cc: stable@freebsd.org Subject: Re: 7.0-PRERELEASE desktop system periodically freezes momentarily Message-ID: <1200764776.48952.64.camel@predator-ii.buffyverse> In-Reply-To: <1200752559.48952.31.camel@predator-ii.buffyverse> 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> <47851247.1020306@raad.tartu.ee> <4785186E.4070609@FreeBSD.org> <47852EFF.8000103@raad.tartu.ee> <478530FC.8090701@FreeBSD.org> <478531C4.10909@raad.tartu.ee> <4785334F.205@FreeBSD.org> <47866B15.5070002@raad.tartu.ee> <47867FAD.9050701@FreeBSD.org> <1200156892.1196.34.camel@predator-ii.buffyverse> <1200197025.1225.17.camel@predator-ii.buffyverse> <4789F872.8000502@FreeBSD.org> <1200241867.1677.34.camel@predator-ii.buffyverse> <478A7014.4080804@FreeBSD.org> <1200323959.1971.27.camel@predator-ii.buffyverse> <478BC0AA.3080906@FreeBSD.org> <1200589144.7141.27.camel@predator-ii.buffyverse> <478FB18B.3090204@FreeBSD.org> <1200677810.57226.45.camel@predator-ii.buffyverse> <1200752559.48952.31.camel@predator-ii.buffyverse>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris, Another one, this time xorg for 2 seconds, approximately in the middle. I'm feeling inclined to doubt the validity of this and the previous data set, however. Looking at the tail end of each of the events in question, there is clearly activity on other processes before the supposedly long exclusive cpu event terminates. Unless this is some limitation of the schedgraph.py script, or the ktr logging mechanism, etc., then this must surely indicate that they are not valid captures? I am all the more inclined to question them because the very next capture/dump I did after the previous set was captured looked so similar to it that I felt prompted to do a diff between the files and found that they contained identical lines for the most part, with only approx every nth line being different (for n=about 4 or so - I don't recall exactly and unfortunately didn't keep that particular one). Is it sufficient to just set debug.ktr.mask to resume capturing, or is it necessary to set debug.ktr.clear? (Note that so far there has always a substantial time interval between setting the mask and clearing it again, at least some minutes and usually much more, so I've assumed that there's plenty of logging occurring to over-write the previous contents). I should also have mentioned that I'm getting these messages periodically: ums0: at uhub0 port 2 (addr 2) disconnected ums0: detached ums0: <B16_b_02 USB-PS/2 Optical Mouse, class 0/0, rev 2.00/98.02, addr 2> on uhub0 ums0: 8 buttons and Z dir. which for the moment I'm assuming are related to running the KTR-enabled kernel as I can't recall seeing these previously. http://au.dyndns.ws/public/ktr-sched-200801200336.out.bz2 Wayne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1200764776.48952.64.camel>