From owner-freebsd-fs@FreeBSD.ORG Thu Sep 9 14:16:51 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 0251710656E4 for ; Thu, 9 Sep 2010 14:16:51 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by mx1.freebsd.org (Postfix) with ESMTP id A47118FC0A for ; Thu, 9 Sep 2010 14:16:50 +0000 (UTC) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA11.westchester.pa.mail.comcast.net with comcast id 4bZ41f0060vyq2s5BeGq4x; Thu, 09 Sep 2010 14:16:50 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta05.westchester.pa.mail.comcast.net with comcast id 4eGp1f00D3LrwQ23ReGq59; Thu, 09 Sep 2010 14:16:50 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 68B069B423; Thu, 9 Sep 2010 07:16:48 -0700 (PDT) Date: Thu, 9 Sep 2010 07:16:48 -0700 From: Jeremy Chadwick To: Ivan Voras Message-ID: <20100909141648.GA77376@icarus.home.lan> References: <20100909140000.5744370gkyqv4eo0@webmail2.ukgrid.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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: Thu, 09 Sep 2010 14:16:51 -0000 On Thu, Sep 09, 2010 at 04:12:18PM +0200, Ivan Voras wrote: > On 09/09/10 15:00, a.smith@ukgrid.net wrote: > >Hi, > > > >I am experiencing kernel panics when running a zfs receive. And > > Others will comment more, but... > > >siisch0: Timeout on slot 23 > >siisch0: siis_timeout is 00040000 ss 7fffffff rs 7fffffff es 00000000 > >sts 801d20 > >siisch0 ..waiting for slots 7f7fffff > > > >Fatal trap 12: page fault while in kernel mode > > >current proecess = 12 (irq256: siis0) > > ... this looks like a hardware error. > > Are you using AHCI here? Try turning it off. 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. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |