From owner-freebsd-bugs@freebsd.org  Tue Jan  3 12:17:28 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 740CEC9D07C
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  3 Jan 2017 12:17:28 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 6389E1D1D
 for <freebsd-bugs@FreeBSD.org>; Tue,  3 Jan 2017 12:17:28 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v03CHR7n048522
 for <freebsd-bugs@FreeBSD.org>; Tue, 3 Jan 2017 12:17:28 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 215715] cond_test:cond_timedwait_race crashes with SIGSEGV
 periodically when calling binuptime
Date: Tue, 03 Jan 2017 12:17:28 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-215715-8-3cW1FRI03E@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215715-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-215715-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 12:17:28 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215715

--- Comment #4 from Konstantin Belousov <kib@FreeBSD.org> ---
I do not see how the backtrace you posted has anything to do with eventtime=
rs.=20
But it might be relevant for timecounter HPET hardware.  Please show sysctl
kern.timecounter output on your test machine.

In fact, I do see an issue in multithreaded program which happens to execute
e.g. gettimeofday(2) in two threads in parallel, regardless of your test
program.  If your machine uses HPET for timecounter, please test the patch
attached.

In fact, using LAPIC for eventtimers and HPET for timecounter is very weird
configuration.  Also weird is that there is no HPET in the eventtimers hw l=
ist.
Is it VM ? Show verbose dmesg.

BTW, core file does not have any use outside of your machine.

--=20
You are receiving this mail because:
You are the assignee for the bug.=