From owner-freebsd-current@FreeBSD.ORG Thu Dec 19 22:36:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5BC40E31 for ; Thu, 19 Dec 2013 22:36:10 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3265F1026 for ; Thu, 19 Dec 2013 22:36:10 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1627FB958; Thu, 19 Dec 2013 17:36:09 -0500 (EST) From: John Baldwin To: "Poul-Henning Kamp" Subject: Re: r259072 is not a happy camper... Date: Thu, 19 Dec 2013 16:06:26 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <27325.1386444776@critter.freebsd.dk> <201312181458.20649.jhb@freebsd.org> <75109.1387406757@critter.freebsd.dk> In-Reply-To: <75109.1387406757@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201312191606.26963.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 19 Dec 2013 17:36:09 -0500 (EST) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 22:36:10 -0000 On Wednesday, December 18, 2013 5:45:57 pm Poul-Henning Kamp wrote: > In message <201312181458.20649.jhb@freebsd.org>, John Baldwin writes: > > >> >Does it get a crashdump if you try? > >> > >> No :-( > >> > >> There may be a connection to unclean UFS filesystems (SU + TRIM, no J). > > > >Is this reproducible? > > Not really. > > It seems to happen at random, usually shortly after boot and as I > mentioned, there is some indications of it being related to munged > filesystems. > > Amongst these indications: > > Booting single-user and running fsck (without -p) almost always > prevents it from happening until after next crash, and I think all > the backtraces I've see have been UFS or maybe even WITNESS+UFS > related. > > If it is WITNESS related, the serial console is obviously a > prime suspect... > > But all that said, I havn't seen it for a couple of days... Humm. I'm kind of out of ideas then. -- John Baldwin