From owner-freebsd-current@FreeBSD.ORG Mon Jun 28 18:59:32 2004 Return-Path: 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 BF72716A4CF; Mon, 28 Jun 2004 18:59:32 +0000 (GMT) Received: from mail.spekt.net (biggie.spekt.net [67.18.79.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C30043D1F; Mon, 28 Jun 2004 18:59:32 +0000 (GMT) (envelope-from radek@raadradd.com) Received: by mail.spekt.net (Postfix, from userid 1007) id 7505A402D; Mon, 28 Jun 2004 20:59:29 +0200 (CEST) Received: from [192.168.0.149] (port42.ds1-ba.adsl.cybercity.dk [212.242.62.43]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.spekt.net (Postfix) with ESMTP id 47321400A; Mon, 28 Jun 2004 20:59:08 +0200 (CEST) Message-ID: <40E06A5C.7050505@raadradd.com> Date: Mon, 28 Jun 2004 20:58:36 +0200 From: Radek Kozlowski User-Agent: Mozilla Thunderbird 0.7 (X11/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bryan Liesner References: <20040626115242.X570@gravy.kishka.net> <20040628190253.U658@korben.in.tern> <20040628134856.O2330@gravy.kishka.net> In-Reply-To: <20040628134856.O2330@gravy.kishka.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on biggie.spekt.net X-Spam-Status: No, hits=0.0 required=5.5 tests=none autolearn=ham version=2.63 X-Spam-Level: cc: freebsd-current@FreeBSD.org cc: Lukas Ertl Subject: Re: Panic: EHCI and umass X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 28 Jun 2004 18:59:32 -0000 On 2004.06.28 19:55, Bryan Liesner wrote: > No crashdump available. I would have loved a crashdump, it would have > saved me an hour manually transcribing the DDB trace :) > > I tried setting the no_sync_on _panic sysctl as well, but I can't coax a > coredump. I haven't been able to reliably produce a dump for quite some > time now. The system panics and then it's time to hit the reset switch. You might try call doadump() in ddb. -Radek