Date: Fri, 10 Sep 2010 09:56:40 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: a.smith@ukgrid.net Cc: freebsd-fs@freebsd.org Subject: Re: ZFS related kernel panic Message-ID: <4C89D6A8.1080107@icyb.net.ua> In-Reply-To: <20100909182318.11133lqu4q4u1mw4@webmail2.ukgrid.net> References: <20100909140000.5744370gkyqv4eo0@webmail2.ukgrid.net> <20100909182318.11133lqu4q4u1mw4@webmail2.ukgrid.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C89D6A8.1080107>