Date: Thu, 24 Jan 2008 06:58:02 -0700 From: Joe Peterson <joe@skyrush.com> To: Sam Leffler <sam@errno.com> Cc: freebsd-stable@freebsd.org Subject: Re: New KTR trace for mouse freezing/stuttering in 7.0-RC1 Message-ID: <4798996A.6040103@skyrush.com> In-Reply-To: <47987511.6070201@errno.com> References: <1199812249.96494.133.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> <1200847317.64691.33.camel@predator-ii.buffyverse> <1201095768.349.21.camel@predator-ii.buffyverse> <47975CFE.4070000@skyrush.com> <20080123135705.3ff903e4@linwhf.opal.com> <479794E3.5060307@skyrush.com> <20080123161128.01040b96@linwhf.opal.com> <4797B041.2020700@skyrush.com> <20080123174820.08ba33ad@linwhf.opal.com> <4797DE22.6020508@skyrush.com> <4797F0D7.8020702@skyrush.com> <47981DC7.2030706@skyrush.com> <47987511.6070201@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sam Leffler wrote: >> http://www.skyrush.com/downloads/ktr_ule_4.out >> > I don't see what it is > from the trace data. It sort of looks like the last thing that ran is > the swi4 which is likely a callout (need to check the log file contents > to be certain). If the callback function does something it wouldn't > necessarily be visible in the schedgraph plot. If you could stick a > dmesg from booting out in the same spot it might be worthwhile. OK, I just ran a dmesg and put it up there: http://www.skyrush.com/downloads/dmesg_4.out The WRITE_DMA messages are not time-correlated with this issue; I don't like the looks of those either, but that's a different issue to look into... > Also if > you rebuild the kernel the kernel with DIAGNOSTIC then softclock() will > complain about callouts that take longer than 2ms to run. OK, recompiling now... Will the new messages appear in dmesg, or in a log file? > This might > generate too much noise in which case you can adjust the threshold by > editing the code in sys/kern/kern_timeout.c. Cool - thanks for looking at this, and I will let you know what I find! Do I need to make another trace concurrently, or should I just repeat the test procedure and see if I get new messages? -Thanks, Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4798996A.6040103>