Date: Sun, 13 Jan 2008 14:33:44 +1030 From: Wayne Sierke <ws@au.dyndns.ws> To: Kris Kennaway <kris@freebsd.org> Cc: Toomas Aas <toomas.aas@raad.tartu.ee>, freebsd-stable@freebsd.org Subject: Re: 6.3-PRERELEASE desktop system periodically freezes momentarily Message-ID: <1200197025.1225.17.camel@predator-ii.buffyverse> In-Reply-To: <1200156892.1196.34.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2008-01-13 at 03:24 +1030, Wayne Sierke wrote: > I added options MUTEX_PROFILING and options HWPMC_HOOKS but the system > hangs when going multi-user after printing: Entropy harvesting: > interrupts ethernet point_to_point. ^t shows it stuck in dd, ^c brings > out to sysctl [<null>] but I can't get past that and am forced to reset. > I tried rebooting without loading modules which gets around that but > then I can't get xorg to start even after loading nvidia.ko. I've seen > the comment in the NOTES section in MUTEX_PROFILING re modules, does it > mean that I won't be able to use nvidia.ko with this test kernel? If so > perhaps someone could comment on how best to proceed re gathering test > results? i.e. would it be better to just use 'nv' or 'vesa' driver for > now and get mutex stats? Or forgo that and keep 'nvidia' and just use > hwpmc, etc. > Someone replied privately and evidently I didn't make some things clear about what I did/tried. After changing the kernel config, I used appropriate incarnations of 'make buildkernel KERNCONF=' and 'make installkernel KERNCONF= KODIR=' and used 'nextboot -k'. I also tried rebuilding nvidia.ko (including when booted under the profiling kernel) but not surprisingly the resulting file was identical to the original. I've just booted into a kernel with options HWPMC_HOOKS so I'll grab some results here. Meanwhile I'll prepare a kernel with just options MUTEX_PROFILING and if I haven't heard anything different in the meantime, I'll set about checking that out without nvidia.ko. Wayne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1200197025.1225.17.camel>