From owner-freebsd-bugs Thu Mar 4 17:28:48 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0C4B9150D9 for ; Thu, 4 Mar 1999 17:28:45 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id KAA05973; Fri, 5 Mar 1999 10:28:35 +0900 (JST) Message-ID: <36DF3216.FAD3C414@newsguy.com> Date: Fri, 05 Mar 1999 10:23:34 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Marijn Meijles Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/10281: Crash of 3.1-STABLE system due to scsi error. References: <199903042010.MAA31476@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marijn Meijles wrote: > > > If you're getting crashes, it would help immensely if you could provide a > > stack trace from the panic. > > > Yup, I know. I've instructed the guys at the university to write down > everything, but the crash of today just showed this and no panic. you > could only ping and it had to be rebooted. Actually, a stack trace is a little move complex than simply writing down everything. You have to make a kernel with debug symbols, install a stripped version of it, enable core dumps, and then run gdb to get the trace. Or you could enable the kernel debugger and get the trace at the time the crash happens. Either way, the handbook is your friend. There are sections on it describing exactly how you go about this. While it certainly is a pain to the uninitiated, it is invaluable in tracking bugs. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message