From owner-freebsd-bugs@freebsd.org  Sun Jan  3 04:09:20 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 9D135A608ED
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun,  3 Jan 2016 04:09:20 +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 8D8A91BF2
 for <freebsd-bugs@FreeBSD.org>; Sun,  3 Jan 2016 04:09:20 +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 u0349KYY041436
 for <freebsd-bugs@FreeBSD.org>; Sun, 3 Jan 2016 04:09:20 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 205800] random device not loaded; using insecure entropy
Date: Sun, 03 Jan 2016 04:09:20 +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: 10.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: marieheleneka@gmail.com
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-205800-8-NJqwuTuq56@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205800-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-205800-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.20
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: Sun, 03 Jan 2016 04:09:20 -0000

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

--- Comment #4 from Marie Helene Kvello-Aune <marieheleneka@gmail.com> ---
I'm writing this update because I said I would, even though I realize now t=
hat
the dmesg output on 11-CURRENT is irrelevant to this PR due to what looks l=
ike
substancial changes in the /dev/random subsystem between 10-STABLE and
11-CURRENT, which is not entirely unexpected.

Even though the same message appears on several generations and classes of
Intel hardware, it might be useful if someone could check if this happens on
AMD hardware as well.

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