Date: Thu, 09 Jul 2009 20:35:06 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Thomas Ronner <thomas@ronner.org> Cc: freebsd-stable@freebsd.org Subject: Re: ZFS: zpool scrub lockup Message-ID: <4A562A4A.2000201@icyb.net.ua> In-Reply-To: <4A5626FC.5000306@ronner.org> References: <1247085058.6197.18.camel@bugstore> <4A55F96B.6070303@icyb.net.ua> <4A560E2F.1050906@ronner.org> <4A5626FC.5000306@ronner.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 09/07/2009 20:21 Thomas Ronner said the following: > I put the following in my kernel config: > > # debugging > options KDB > options DDB > options GDB > options BREAK_TO_DEBUGGER > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_KDB > options DEBUG_VFS_LOCKS > options DIAGNOSTIC > options SW_WATCHDOG > > When I send a BREAK from my serial console it enters the debugger, so > that works. But when I start ZFS (/etc/rc.d/zfs start) it freezes again > and BREAK doesn't enter the debugger. I'll try playing with the watchdog > now, but I doubt this will help. Any clues? > For watchdog to fire it first needs to be enabled, e.g. by starting watchdogd. Try to run /etc/rd.d/watchdogd onestart before zfs start and then wait for about 16 seconds (default timeout). If that doesn't help, then it seems that the only option would be debugging via serial console. Or manually generating NMI, if your system has an NMI button/switch/jumper. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A562A4A.2000201>