From owner-freebsd-current Sat Jun 26 6:36: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 9F00914EE9 for ; Sat, 26 Jun 1999 06:35:56 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: from scones.sup.scc.nl (i025.ztm.euronet.nl [194.134.112.26]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id PAA06047 from for ; Sat, 26 Jun 1999 15:35:52 +0200 (MET DST) Received: (from daemon@localhost) by scones.sup.scc.nl (8.9.3/8.9.3) id PAA53480 for current@FreeBSD.ORG; Sat, 26 Jun 1999 15:27:46 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by scones.sup.scc.nl with netnews for current@FreeBSD.ORG (current@FreeBSD.ORG) To: current@FreeBSD.ORG Date: Sat, 26 Jun 1999 15:27:43 +0200 From: Marcel Moolenaar Message-ID: <3774D54F.74B6F2C4@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19990624100825.G417@freebie.lemis.com>, <19990624104502.N417@freebie.lemis.com> Subject: Re: ktrace causes kernel panic Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: [snip] > >>> Using a recent (few days) -current I had a process lock up on me > >>> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > >>> while. When I issued a 'ktrace -C' in another screen, everything froze and > >>> the kernel panic'ed. I dropped to the debugger on the console and it was > >>> definintely ktrace that caused the panic. > >> [snip] > Not much. You'll need to get a dump. I got spontaneous reboots on -stable as well. That was just before my vacation. I'll try to dig into it mysel, aAs soon as I recovered from my vacation :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message