From owner-freebsd-fs@FreeBSD.ORG Fri Sep 10 06:56:47 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00C861065672 for ; Fri, 10 Sep 2010 06:56:47 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 49DD98FC15 for ; Fri, 10 Sep 2010 06:56:45 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA15504; Fri, 10 Sep 2010 09:56:42 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OtxXN-0008DH-HD; Fri, 10 Sep 2010 09:56:41 +0300 Message-ID: <4C89D6A8.1080107@icyb.net.ua> Date: Fri, 10 Sep 2010 09:56:40 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.8) Gecko/20100822 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: a.smith@ukgrid.net References: <20100909140000.5744370gkyqv4eo0@webmail2.ukgrid.net> <20100909182318.11133lqu4q4u1mw4@webmail2.ukgrid.net> In-Reply-To: <20100909182318.11133lqu4q4u1mw4@webmail2.ukgrid.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS related kernel panic X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 06:56:47 -0000 on 09/09/2010 20:23 a.smith@ukgrid.net said the following: > Quoting jdc: >> >> This is a siis(4) card -- chances are he can't turn it off. :-) We >> really need a backtrace to see what transpired. >> >> The siis(4) driver may have crashed as a result of LUN timeouts. The >> driver shouldn't panic, I agree, but the port timing out is of major >> concern. I imagine this behaviour (the crash) could be reproduced even >> if UFS2 was used and the timeout took place. > > Hi, > > as mentioned I cant currently get any back trace as the system hangs when it > starts to core dump after the panic :(. Try to add the following options to your kernel: options KDB options KDB_TRACE With these a backtrace should be printed before dumping and you should be able take a picture of your screen. -- Andriy Gapon