From owner-freebsd-current@FreeBSD.ORG Wed Sep 28 06:24:22 2005 Return-Path: X-Original-To: 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 5CB5C16A41F; Wed, 28 Sep 2005 06:24:22 +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 4CA0A43D48; Wed, 28 Sep 2005 06:24:20 +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 j8S6O9Y4016292; Wed, 28 Sep 2005 00:24:09 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <433A3708.6000403@samsco.org> Date: Wed, 28 Sep 2005 00:24:08 -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 Teterin References: <200509280619.j8S6Jn5p051008@corbulon.video-collage.com> In-Reply-To: <200509280619.j8S6Jn5p051008@corbulon.video-collage.com> 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-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: Wed, 28 Sep 2005 06:24:22 -0000 Mikhail Teterin wrote: >>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. > > > I tried to set up the serial console today and could not. What I thought > is a null modem cable, apparently, is not... > > Is there not a single person on these lists with an amd64 already > connected via a serial console? The bug is extremely easy to reproduce > -- just try to run timidity from inside gdb, stop it, and try to exit... > > I do not see this bug in the 6.0R/todo.html and am worried, 6.0 will > ship with the bug in it... > > -mi It's very hard to put entries in the TODO list that are not confirmed or characterized. This isn't a criticism of you, just a fact that we can't assign priority to bugs that we simply have little information on. Scott