From owner-freebsd-stable@FreeBSD.ORG Wed Feb 15 07:43:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B04016A44A for ; Wed, 15 Feb 2006 07:43:31 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8231143D46 for ; Wed, 15 Feb 2006 07:43:30 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail07.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k1F7hMIq027820 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Feb 2006 18:43:23 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k1F7hMnh001033; Wed, 15 Feb 2006 18:43:22 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k1F7hM5Q001032; Wed, 15 Feb 2006 18:43:22 +1100 (EST) (envelope-from peter) Date: Wed, 15 Feb 2006 18:43:22 +1100 From: Peter Jeremy To: Joseph Olatt Message-ID: <20060215074322.GA684@turion.vk2pj.dyndns.org> References: <20060213194406.A29000@eskimo.com> <20060214090748.GA900@turion.vk2pj.dyndns.org> <20060214200154.A3559@eskimo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060214200154.A3559@eskimo.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: kernel panic on 6.1-PRERELEASE with Lexar Jumpdrive2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2006 07:43:31 -0000 On Tue, 2006-Feb-14 20:01:54 -0800, Joseph Olatt wrote: >Using Peter Jeremy's suggestion, I was able to get a backtrace. Since I >couldn't figure out an easier way to capture the backtrace, I >transcribed by hand from the console. A serial console would be much easier if you've got another system with a serial port. Whilst the backtrace is a start, you've left out the actual panic message and associated register dump. Is it a 'panic' or some sort of trap? I don't quickly see call to panic() in probedone(). Whilst you're at it, if you have a debug kernel, can you try running kgdb on it and "list *0xZZZZZZZZ" where ZZZZZZZZ is the eip value listed in the kernel trap message (if any) [not the 'trap 0x1' in the backtrace]. >I still wish I could get the system to dump and save the core. I still >haven't figured out why the system freezes in the middle of a core dump. Are you dumping to an ATA or SCSI disk? If the latter, it's possible that the panic has upset the CAM subsystem (though this isn't supposed to happen). -- Peter Jeremy