From owner-freebsd-acpi@freebsd.org  Tue May 16 15:38:01 2017
Return-Path: <owner-freebsd-acpi@freebsd.org>
Delivered-To: freebsd-acpi@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 7D5C1D709DC
 for <freebsd-acpi@mailman.ysv.freebsd.org>;
 Tue, 16 May 2017 15:38:01 +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 6D35313F
 for <freebsd-acpi@FreeBSD.org>; Tue, 16 May 2017 15:38:01 +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 v4GFbxUg051473
 for <freebsd-acpi@FreeBSD.org>; Tue, 16 May 2017 15:38:01 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-acpi@FreeBSD.org
Subject: [Bug 207676] ACPI Exception on Skylake Systems: PCI0.XHC_.RHUB.HS11
Date: Tue, 16 May 2017 15:37:59 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jhb@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-acpi@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207676-13733-5pHe2ppzjM@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207676-13733@https.bugs.freebsd.org/bugzilla/>
References: <bug-207676-13733@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-acpi@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi/>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 May 2017 15:38:01 -0000

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

--- Comment #10 from John Baldwin <jhb@FreeBSD.org> ---
As the link to the Linux bug report noted, this was an issue fixed upstream=
 in
ACPICA, so presumably it will be fixed by an import of newer ACPICA version=
s to
FreeBSD.  FreeBSD 11-stable and 12-current already contain newer ACPICA
versions than that which was used when this bug report was opened.  Would
someone be able to test a recent snapshot of head or 11-stable?

Also, it's still not clear if there are any runtime effects apart from the
warning message during boot.

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