From owner-freebsd-current@FreeBSD.ORG Mon Jun 12 20:29:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C652A16A41B; Mon, 12 Jun 2006 20:29:43 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.67.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC84C43D62; Mon, 12 Jun 2006 20:29:40 +0000 (GMT) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id AB27533C03; Mon, 12 Jun 2006 22:29:39 +0200 (CEST) Date: Mon, 12 Jun 2006 22:29:39 +0200 From: Lars Engels To: Robert Watson , freebsd-current@freebsd.org Message-ID: <20060612202939.GE46563@e.0x20.net> Mail-Followup-To: Lars Engels , Robert Watson , freebsd-current@freebsd.org References: <20060612182404.GC46563@e.0x20.net> <20060612194541.L34121@fledge.watson.org> <20060612191025.GD46563@e.0x20.net> <20060612195750.GG1226@roadrunner.aventurien.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9ADF8FXzFeE7X4jE" Content-Disposition: inline In-Reply-To: <20060612195750.GG1226@roadrunner.aventurien.local> X-Editor: VIM - Vi IMproved 6.4 User-Agent: Mutt/1.5.11 Cc: Subject: Re: Kernel Panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2006 20:29:43 -0000 --9ADF8FXzFeE7X4jE Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 12, 2006 at 09:57:50PM +0200, Ulrich Spoerlein wrote: > Lars Engels wrote: > > 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?=20 >=20 > Could very well be, I also encountered two or three panics on RELENG_6 > after running 'sysctl -a', sadly no backtraces available. I suppose that gkrellm gets its information with sysctl and that this can cause the panic. >=20 > This only happend though, after I plugged and unplugged some USB > devices. Perhaps I'll find some time to investigate these panics. No USB devices connected here... Now I built a new kernel with KDB and DDB, got another panic but no crashdump. Am I missing something to use DDB? Or is DDB remote-only? I attached the output of boot -v and my kernel config, perhaps that=20 can help. --=20 Lars Engels E-Mail: lars.engels@0x20.net =09 --9ADF8FXzFeE7X4jE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEjc6zKc512sD3afgRAkctAJ99THaFjkYnuUzlOIWOGzU8llG4GwCfcxbb ZvfeFMSoyw7TiBitWLscsH8= =TV1s -----END PGP SIGNATURE----- --9ADF8FXzFeE7X4jE--