From owner-freebsd-bugs@freebsd.org  Tue May  3 20:21:06 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 B61F5B2CC2B
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  3 May 2016 20:21:06 +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 A5FDE11DC
 for <freebsd-bugs@FreeBSD.org>; Tue,  3 May 2016 20:21:06 +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 u43KL6ug099969
 for <freebsd-bugs@FreeBSD.org>; Tue, 3 May 2016 20:21:06 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 209222] 11.0-CURRENT -r298793 automatic shutdown for "kernel:
 ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling
 (20160422/evevent-323)" and more under virtual box
Date: Tue, 03 May 2016 20:21:06 +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: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: markmi@dsl-only.net
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-209222-8-KGMO1mPK7y@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209222-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-209222-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.22
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 May 2016 20:21:06 -0000

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

--- Comment #4 from Mark Millard <markmi@dsl-only.net> ---
(In reply to Mark Millard from comment #3)

In reply to John B. Jung-uk Kim wrote that there now is an upstream patch
available:



FYI, the upstream was notified and a patch is available from here:

https://github.com/acpica/acpica/pull/138

Jung-uk Kim



So maybe this bug (209222) should stick around to be tied to having the
upstream fix in place, not just a work around.

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