From owner-freebsd-questions@freebsd.org  Mon Nov 16 10:24:54 2015
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2512CA2EE0C
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Mon, 16 Nov 2015 10:24:54 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D839413BD
 for <freebsd-questions@freebsd.org>; Mon, 16 Nov 2015 10:24:53 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from r56.edvax.de (port-92-195-76-245.dynamic.qsc.de [92.195.76.245])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx02.qsc.de (Postfix) with ESMTPS id C13622766E;
 Mon, 16 Nov 2015 11:16:09 +0100 (CET)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id tAGAG9lM003109;
 Mon, 16 Nov 2015 11:16:09 +0100 (CET)
 (envelope-from freebsd@edvax.de)
Date: Mon, 16 Nov 2015 11:16:09 +0100
From: Polytropon <freebsd@edvax.de>
To: Gerhard Schmidt <schmidt@ze.tum.de>
Cc: freebsd-questions@freebsd.org
Subject: Re: Random Lockup with FreeBSD 10.2 on SuperMicro Boards
Message-Id: <20151116111609.a9757a4a.freebsd@edvax.de>
In-Reply-To: <5649A761.7040303@ze.tum.de>
References: <56498205.3060806@ze.tum.de> <20151116094334.GS2604@mordor.lan>
 <5649A761.7040303@ze.tum.de>
Reply-To: Polytropon <freebsd@edvax.de>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 10:24:54 -0000

On Mon, 16 Nov 2015 10:52:33 +0100, Gerhard Schmidt wrote:
> My Workstation is running 10.2 for about at least 4 Month. I've never
> had a problem event with SU+J. The difference is that on my workstation
> /var is not on a raid array. So SU+J isn't the real problem.

Maybe there's a file system inconsistency? How do you
perform file system checks (automatic in background,
which is discouraged, or in SUM, as recommended)?
I'm asking because I've noticed the following lines
in your previous message:

> Trying to mount root from ufs:/dev/raid/r0p3 [rw]...
> WARNING: / was not properly dismounted

Is /var affected as well? If yes - give it a _clean_
fsck, running in foreground on the unmounted partition.

In case you have already done this, redirect my comment
to /dev/null immediately. :-)


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...