Date: Fri, 04 Jan 2008 23:33:37 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Anish Mistry <mistry.7@osu.edu> Cc: "David E. Thiel" <lx@redundancy.redundancy.org>, freebsd-stable@freebsd.org Subject: Re: RELENG_7 jerky mouse and skipping sound (still a problem -BETA3) Message-ID: <477EB441.704@FreeBSD.org> In-Reply-To: <200801041730.39016.mistry.7@osu.edu> References: <200710171228.39123.mistry.7@osu.edu> <477AAD89.2000808@FreeBSD.org> <477E96D2.30202@FreeBSD.org> <200801041730.39016.mistry.7@osu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Anish Mistry wrote: > On Friday 04 January 2008, Kris Kennaway wrote: >> Kris Kennaway wrote: >>> David E. Thiel wrote: >>>> On Sun, Dec 30, 2007 at 11:12:26PM +0100, Kris Kennaway wrote: >>>>>> FWIW, the problem remains for me. Still terrible performance >>>>>> during compiles. >>>>> OK. Instead of going over all of the usual questions again, >>>>> can you point me to a previous mail in which you explain your >>>>> observations and test results in detail? >>>> The most recent is >>>> http://marc.info/?l=freebsd-stable&m=119428719505129&w=2, but >>>> it started way back at >>>> http://marc.info/?l=freebsd-current&m=118998090512027&w=2. >>>> >>>> I've tried a lot of stuff in between, and all I've been able to >>>> narrow it down to is that it's not a display driver issue, and >>>> that none of my swap partition is getting used, so that's not >>>> the problem. During compiles, my UP system with ULE still gets >>>> very unresponsive when compiling, sometimes taking up to 10 >>>> seconds just to draw a new terminal window. Even changing focus >>>> with the window manager can take several seconds. I'd like to >>>> provide more info, but I'm not sure what stats are useful for >>>> this particular issue. Please let me know. dmesg is at >>>> http://redundancy.redundancy.org/dmesg.txt, and kernel config is >>>> at http://redundancy.redundancy.org/DEEPTHOUGHT. Even though I'm >>>> still getting reported 80-95% memory utilization and no paging, >>>> I'm going to get an extra gig of RAM on order to see if that >>>> improves things. 2G of ram for a desktop, what's the world >>>> coming to? ;) >>> OK, can you obtain a schedgraph trace when the problem is >>> manifesting? See /usr/src/tools/sched/ and previous discussion in >>> this or related threads. >> Anyone? Time is rapidly running out to get this fixed in time for >> 7.0-RELEASE, so we need this trace ASAP. > http://am-productions.biz/docs/ktr.out.gz > > Is there a way to export the graph once I'm looking in it in > schedgraph.py? The ktr.out is all we need, thanks. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?477EB441.704>