From owner-freebsd-bugs@freebsd.org  Mon Mar  7 22:33:33 2016
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 C293CAC7E9D
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon,  7 Mar 2016 22:33:33 +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 B34AAB62
 for <freebsd-bugs@FreeBSD.org>; Mon,  7 Mar 2016 22:33:33 +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 u27MXXl2009381
 for <freebsd-bugs@FreeBSD.org>; Mon, 7 Mar 2016 22:33:33 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 207729] llvm 3.8.0 import (r296417) - panic in aesni.ko
Date: Mon, 07 Mar 2016 22:33:33 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: portmaster@bsdforge.com
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207729-8-lHIlripeVK@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207729-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-207729-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.21
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: Mon, 07 Mar 2016 22:33:33 -0000

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

--- Comment #14 from Chris Hutchinson <portmaster@bsdforge.com> ---
(In reply to Konstantin Belousov from comment #13)
> (In reply to Dimitry Andric from comment #12)
> After r296467, loader change is not critical, but desirable to have.  If =
you
> use old loader, some of your preloaded modules would not load, but kernel
> does not panic.  After the kernel booted, you can kldunload and then kldl=
oad
> the failed modules.
Thank you *very* much for the reply, Dimitry, Konstantin.
So if I'm on anything (including 11) *prior* to the landing of
r296467. A loader update *is* required. At least if one wants
to expect *normal* behavior.
At least that's how I interpret this.

Thanks again!

--Chris

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