From owner-freebsd-current@FreeBSD.ORG  Wed Dec 18 22:46:05 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 954C881C;
 Wed, 18 Dec 2013 22:46:05 +0000 (UTC)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 59BBA1EAF;
 Wed, 18 Dec 2013 22:46:05 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 486633EB56;
 Wed, 18 Dec 2013 22:45:58 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.14.7/8.14.7) with ESMTP id rBIMjvPV075110;
 Wed, 18 Dec 2013 22:45:57 GMT (envelope-from phk@phk.freebsd.dk)
To: John Baldwin <jhb@freebsd.org>
Subject: Re: r259072 is not a happy camper...
In-reply-to: <201312181458.20649.jhb@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <27325.1386444776@critter.freebsd.dk>
 <201312131620.25107.jhb@freebsd.org> <55350.1387010679@critter.freebsd.dk>
 <201312181458.20649.jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Date: Wed, 18 Dec 2013 22:45:57 +0000
Message-ID: <75109.1387406757@critter.freebsd.dk>
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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2013 22:46:05 -0000

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...

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.