From owner-freebsd-current@freebsd.org Tue Oct 18 12:20:27 2016 Return-Path: Delivered-To: freebsd-current@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 86774C14661 for ; Tue, 18 Oct 2016 12:20:27 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A43186C for ; Tue, 18 Oct 2016 12:20:26 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bwTNT-002NUk-Bo>; Tue, 18 Oct 2016 14:20:19 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bwTNT-000TQC-3t>; Tue, 18 Oct 2016 14:20:19 +0200 Date: Tue, 18 Oct 2016 14:20:13 +0200 From: "O. Hartmann" To: freebsd-current Subject: Re: CURRENT [r307305]: Crashing Message-ID: <20161018142013.5d8265d2@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20161015102242.3c0f2fbb.ohartman@zedat.fu-berlin.de> References: <20161014104833.7a2ac588@freyja.zeit4.iv.bundesimmobilien.de> <20161015102242.3c0f2fbb.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 18 Oct 2016 12:20:27 -0000 On Sat, 15 Oct 2016 10:22:42 +0200 "O. Hartmann" wrote: > Am Fri, 14 Oct 2016 10:48:33 +0200 > "O. Hartmann" schrieb: > > > Systems I updated to recent CURRENT start crashing spontaneously. > > > > recent crashing system is on > > 12.0-CURRENT FreeBSD 12.0-CURRENT #11 r307305: Fri Oct 14 08:37:59 CEST 2016 > > > > other (no access since it is remote and not accessible until later the day) > > has been updated ~ 12 hours ago and it is alos rebooting/crashing without > > any warnings. Can be triggered on heavy load. > > > > Only system with r307263 and stable so far is an older two-socket XEON > > Core2Duao based machine, all crashing boxes have CPUs newer or equal than > > IvyBridge. > > > > Does anyone also see these crashes? I tried to compile a debug kernel on one > > host, but that's the remote machine I have access to later, it failed > > compiling the kernel - under load it crashed often. After ZFS scrubbing > > kickied in, it vanished from the net ;-/ > > > > kind regards, > > oh > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Still 307341 is crashing undpredicted ( FreeBSD 12.0-CURRENT #5 r307341: Sat > Oct 15 09:36:16 CEST 2016). > > I'm back to r307157, which seems to be "stable". > While I tried to reproduce and bisect the crashes, I face now a strange situation. With ~r307318, UEFI booting boxes (one workstation with ZFS, a laptop, no ZFS) do not fail/crash/reboot anymore. The picture is different for all non-UEFI systems. They still crash/reboot (two servers, both ZFS, one workstation, with ZFS) after a while: sometimes minutes, sometimes 2 or more hours. Those boxes crashes with CURRENT > r307157, even the most recent r307555, while this seems stable on UEFI booting systems.