Date: Mon, 2 Oct 2006 15:23:49 -0400 From: Vivek Khera <vivek@khera.org> To: stable@freebsd.org Subject: Re: ffs snapshot lockup Message-ID: <847DD3A5-D5DD-4D3E-B755-64B13D1DA506@khera.org> In-Reply-To: <20060922203654.GA65693@xor.obsecurity.org> References: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> <20060922190328.GA64849@xor.obsecurity.org> <555B84D2-520F-44D6-84D6-CF9CE7EE47C7@khera.org> <20060922203654.GA65693@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-11--1026280095 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 22, 2006, at 4:36 PM, Kris Kennaway wrote: > Start by enabling INVARIANTS, INVARIANT_SUPPORT, DEBUG_LOCKS and > DEBUG_VFS_LOCKS, then run 'show lockedvnods' and 'alltrace' in DDB > (spammy, need that serial console), or at least trace the running > processes (show allpcpu) and those listed in lockedvnods. Then call > doadump and save the core+kernel.debug when you reboot. Well, what an exciting weekend we had! Three lockups/panics: two during running a dump (mksnap_ffs seems to be the culprit) and one running background fsck after rebooting from the prior crash. Details are posted at http://vivek.khera.org/scratch/crashlogs/ I have the crashdumps available to a kernel hacker upon request (i'd rather not make them generally available to the public...) --Apple-Mail-11--1026280095--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?847DD3A5-D5DD-4D3E-B755-64B13D1DA506>