Date: Mon, 12 Jun 2006 21:10:25 +0200 From: Lars Engels <lars.engels@0x20.net> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Kernel Panic Message-ID: <20060612191025.GD46563@e.0x20.net> In-Reply-To: <20060612194541.L34121@fledge.watson.org> References: <20060612182404.GC46563@e.0x20.net> <20060612194541.L34121@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, Jun 12, 2006 at 07:47:32PM +0100, Robert Watson wrote: > > > It looks like there is a problem with the stack trace from kgdb. Is there > any chance your kernel and kernel.debug are out of sync? Today I removed DDB and GDB from the kernel, because with it no kernel dumps were created. To build it, i used -DNO_CLEAN. Can this cause the kernel to get out of sync with kernel.debug? > Does this box have a serial port? If so, you might want to try setting up > a serial console for it with a null modem cable to an adjacent box. DDB > may be able to get a more reliable stack trace than the kernel dump. Looks > like a bug in some or another sysctl handler -- a stack trace from DDB may > be sufficient to debug it without a working core. Unfortunately no. It is a notebook without serial ports. It has a IEE1394 Port which could be used with DDB but I don't have a second box with Firewire. I also have a new kernel dump which shows gkrellm as current process. Can it still be a bug in sysctl? current process. Can it still be a bug in sysctl? -- Lars Engels E-Mail: lars.engels@0x20.net [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEjbwhKc512sD3afgRAjmaAJ9Oxa0yhmdo+goNIKisl2M125xNaACgrhAy LlMmVYdRl8GenXgkmxo2GUE= =l2uM -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060612191025.GD46563>