Date: Mon, 21 Jan 2008 03:11:57 +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: <1200847317.64691.33.camel@predator-ii.buffyverse> In-Reply-To: <1200764776.48952.64.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> <1200764776.48952.64.camel@predator-ii.buffyverse>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris, Latest captures (of interest) - they're not hard to come by, it seems. I see more than a couple of these every hour at least while I'm actively doing anything on this system, and I've witnessed up to two or three times that many at times. It seems my initial glee about catching Epiphany out was unfounded. Each capture has successively shown a different process/thread with the long exclusive cpu use, and the first one I've linked to here doesn't even show any active 'running' processes for the period in question, it has evolution and xorg 'yielding' and irq14 in 'runq'. The second one shows 'xorg' with exclusive 'running' for the duration. So it's proving quite variable, and after examining more than a handful of these I'm surmising that the 'freeze' is interfering with ktr logging somehow, resulting in the loss of one or more data points and resulting in the anomalous graphs as I mentioned in my previous message. I won't strive to take any more of these for now unless you indicate that you believe it could be useful. If I happen to catch any that look of particular interest I'll post them up and send links. In the meantime I'll revert to a standard GENERIC kernel, too, to gauge how much effect running with this KTR-enabled kernel on the frequency of these events, and the mouse disconnects. I'm keen to hear your take on what you think might be going on here. http://au.dyndns.ws/public/ktr-sched-200801200302.out.bz2 http://au.dyndns.ws/public/ktr-sched-200801210207.out.bz2 Wayne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1200847317.64691.33.camel>