From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 22 06:36:24 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DBDB16A420; Thu, 22 Sep 2005 06:36:24 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB45A43D49; Thu, 22 Sep 2005 06:36:21 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j8M6aC4h045231; Thu, 22 Sep 2005 00:36:12 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <433250D9.8030104@samsco.org> Date: Thu, 22 Sep 2005 00:36:09 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Mikhail T." References: <200509220629.j8M6TM3F000841@blue.virtual-estates.net> In-Reply-To: <200509220629.j8M6TM3F000841@blue.virtual-estates.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: amd64@FreeBSD.org, re@FreeBSD.org, current@FreeBSD.org Subject: Re: amd64+gdb -- instant reboot (BETA5 and 4) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2005 06:36:24 -0000 Mikhail T. wrote: > Hi! > > I was trying to use gdb to debug a program (audio/timidity++) on > my 6.0-BETA4. > > It would play fine, and then I'll interrupt it with Ctrl-C to enter the > debugger. If I then try to exit the debugger, the whole system will > reboot instantaniously. > > I sync-ed to today's sources (BETA5) and added WITNESS, WITNESS_KDB, > INVARIANTS, and INVARIANT_SUPPORT (strangly, INVARIANTS requires, but > does not imply INVARIANT_SUPPORT). > > With BETA5 the story is exactly the same -- instant reboot. > > Sometimes I can see two lines of debug messages (lock order reversal?) > flushed on the console, but the machine reboots too quickly to read > them beyond: > > 1 .................... > 2 .................... > > Is this gdb misbehaviour a known problem? How can I have the system > avoid rebooting? Crash-dumping is enabled, but does not take place :-( > > Is that because timidity uses threads, perhaps? > > Thanks! > > -mi It's definitely not known. Any chance you could hook up a serial console to log the output. It'll be pretty hard to debug otherwise. Sounds like you're likely getting a triple fault. Scott