From owner-freebsd-usb@FreeBSD.ORG Wed Jul 16 20:49:47 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C10641065673 for ; Wed, 16 Jul 2008 20:49:47 +0000 (UTC) (envelope-from prvs=pschmehl_lists=0763be217@tx.rr.com) Received: from ip-relay-002.utdallas.edu (ip-relay-002.utdallas.edu [129.110.20.112]) by mx1.freebsd.org (Postfix) with ESMTP id 8CB4B8FC12 for ; Wed, 16 Jul 2008 20:49:47 +0000 (UTC) (envelope-from prvs=pschmehl_lists=0763be217@tx.rr.com) X-Group: RELAYLIST X-IronPort-AV: E=Sophos;i="4.31,199,1215406800"; d="scan'208";a="3839085" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-002.utdallas.edu with ESMTP; 16 Jul 2008 15:20:15 -0500 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id 7323923DE3 for ; Wed, 16 Jul 2008 15:20:16 -0500 (CDT) Date: Wed, 16 Jul 2008 15:20:15 -0500 From: Paul Schmehl To: freebsd-usb@freebsd.org Message-ID: <32370E1FFF045EDCAB01F90D@utd65257.utdallas.edu> In-Reply-To: <3a142e750807160158x150f521fv696845d77d6e3c58@mail.gmail.com> References: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu> <3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com> <3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com> <91DD32EA4C3672A46D423E44@utd65257.utdallas.edu> <3a142e750807160158x150f521fv696845d77d6e3c58@mail.gmail.com> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Crash when booting with umass device connected X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 20:49:47 -0000 --On Wednesday, July 16, 2008 10:58:53 +0200 "Paul B. Mahol" wrote: > On 7/15/08, Paul Schmehl wrote: >> --On Tuesday, July 15, 2008 11:23:09 +0200 "Paul B. Mahol" >> >> wrote: >>> >>> Look in Developers handbook for more info >>> /usr/share/doc/en/books/developers-handbook/index.html >>> >>> I think that textdumps are MFCed to STABLE. >>> Textdumps provide easy way for gathering backtraces. >> >> The problem is, I'm not getting dump files. (And dumpdev is set to AUTO - >> the >> default.) Savecore runs, but there's nothing to put in /var/crash. >> > > First, do you see kdb prompt when system panics? I'm sorry. I don't know what that means. > If not then you will need to recompile kernel with various debug stuff: > KDB, DDB, GDB, DEBUG=-g ... Well, there's a problem with that. I added option USB_DEBUG and recompiled the kernel, and now it doesn't crash. ??? I left the umass device plugged in and rebooted, so that I could show a peer the crash, and it zipped right on through without a hiccup. > Second do you have line with sw in /etc/fstab. Yes. pauls@utd65257# grep sw /etc/fstab /dev/ad8s1b none swap sw 0 0 > If not, > it is possible to set dump device manually. > You should have following lines in /etc/rc.conf: > > ddb_enable="YES" > ddb_config="/etc/ddb.conf" > > But this one is required only if you want that textdumps are > taken automaticaly after system crash. > Exploring ddb(4) is also usefull. Thanks for the tips. I'll read up on those. -- Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer.