Date: Wed, 17 Nov 2010 00:23:19 -0500 From: jhell <jhell@DataIX.net> To: Adam Stylinski <stylinae@mail.uc.edu> Cc: freebsd-stable@freebsd.org Subject: Re: STABLE panics/hardlocks when savage module is inserted Message-ID: <4CE366C7.1030104@DataIX.net> In-Reply-To: <AANLkTik2wovxHG58xC4Rdo85gc%2BVR=u-9ycqtZ-p7LbW@mail.gmail.com> References: <AANLkTik2wovxHG58xC4Rdo85gc%2BVR=u-9ycqtZ-p7LbW@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/16/2010 23:12, Adam Stylinski wrote: > I hate to be the guy who gripes on the mailing list about his dinosaur video > card's drivers crashing his system, but it's possible this could be an issue > of a wider scope. When I kldload savage the system hardlocks. Not exactly > sure if it's panicking or not, however I do have a serial port, so maybe I > can setup a serial console and compile the kernel with debugger support to > try and get a backtrace. > > Anybody have any pointers? This should give you enough of an overview of how to obtain and report the information you obtain for debugging kernel problems. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html The generic kernel configuration for the most part should be enough information to start for most cases and this would at least give you a starting point. Using a GENERIC kernel from a release or a snapshot too would also help to determine if its a problem as part of the project or a configuration mistake you might have made in your custom kernel. -- jhell,v
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CE366C7.1030104>