Date: Fri, 19 Oct 2001 13:59:13 -0400 From: Bill Moran <wmoran@iowna.com> To: Bjarne Wichmann Petersen <mekanix@privat.dk>, freebsd-stable@freebsd.org Subject: Re: spontaneous crashes with STABLE Message-ID: <01101913591302.00703@proxy.the-i-pa.com> In-Reply-To: <20011019082546.TUDT23247.fepA.post.tele.dk@there> References: <20011018125533.OPYG1982.fepF.post.tele.dk@there> <01101819083401.00322@proxy.the-i-pa.com> <20011019082546.TUDT23247.fepA.post.tele.dk@there>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 19 October 2001 04:28, Bjarne Wichmann Petersen wrote: > On Friday 19 October 2001 01:08, Bill Moran wrote: > > The problem here appears to be that you're not in the right directory to > > find kernel.debug, or that kernel.debug doesn't exist. Without it, gdb > > Found out I needed to build the kernel "the old way" ;) I wasn't aware that was necessary. > Now I get this: > > (kgdb) symbol-file kernel.debug > Reading symbols from kernel.debug...done. > (kgdb) exec-file /var/crash/kernel.0 > (kgdb) core-file /var/crash/vmcore.0 > IdlePTD 5177615 > initial pcb at 4232a0 > panic messages: > --- > dmesg: kvm_read: invalid address (c041b600) > --- > #0 0x0 in ?? () Type "where" at the gdb prompt. This will give enough information to start tracking things down. You'll probably want to capture the entire gdb session with script(1) so you can cut/paste it into future eamils. Here's some more info on the process: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Depending on your level of programming knowledge, the output from gdb may or may not make sense to you. Personally, I know enough to look intelligent to newbies but stupid to kernel hackers. One way or the other, you should be able to guess by the names that come up whether the panic originated with the filesystem code, or the network code, etc. Once you have that info, post the details back to this list with a better subject ... i.e. "panic in ffs_blk_free" or whatever. This will set off warning lights for the people who are familiar with that section of the code and get you replies from folks who really understand what's going on in that section of the code. If posting in that manner doesn't get anywhere after a few days (remember, not everyone reads and responds to their email on a daily basis) try posting the same message to freebsd-hackers@freebsd.org and/or do some research and find out who's in charge of maintaining that section of the code and email them directly. Good luck. -- Bill Moran Potential Technology technical services (412) 793-4257 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01101913591302.00703>