Date: Fri, 7 Nov 2008 17:07:29 -0500 From: Rory Arms <rorya+freebsd.org@TrueStep.com> To: Ken Smith <kensmith@cse.buffalo.edu> Cc: FreeBSD-stable@FreeBSD.org Subject: Re: 6.4-RC2 crashes after a few minutes of uptime Message-ID: <510F0121-0E24-42C0-BC77-D61DF9FEA46C@TrueStep.com> In-Reply-To: <1226078239.37011.37.camel@bauer.cse.buffalo.edu> References: <9592E887-75F3-473F-9581-F9C22A9936A6@TrueStep.com> <1226078239.37011.37.camel@bauer.cse.buffalo.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2008-11-07, at 12:17 , Ken Smith wrote: > On Fri, 2008-11-07 at 00:00 -0500, Rory Arms wrote: >> Well, if I can assist with further debugging, let me know. > > The person who followed up with a list of things that *may* have made > the problem go away mentioned one of the things was disabling powerd. > Do you have that enable, and if yes would you mind disabling it to see > if that's the culprit? Hi Ken, No, it's not running powerd. Looking at the process list, it looks like GNOME has some power related processes, but I assume that's different. I don't think I'd ever even heard of powerd till now, and have now read the manual to learn about it. Well, I wonder if the panic I had yesterday a few minutes after booting RC2 was a fluke. The computer has been running so far without problems, using GNOME, on that second RC2 bootup, for almost 24 hours now. However, I still find it concerning that kgdb(1) on 6.4, hasn't been able to open any of the core dump though. If this is broken, it will be difficult to provide bug reports. I wonder if it's just something about this particular code path to panic, that's generating this, I guess, corrupt core file. Is there a key sequence, or sysctl knob perhaps, that I can use to force an artificial panic to see if the coredump generated is any different? - rory
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?510F0121-0E24-42C0-BC77-D61DF9FEA46C>