From owner-freebsd-bugs@freebsd.org  Mon Jan  4 23:36: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 3DDECA62A77
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon,  4 Jan 2016 23:36: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 240B01F0F
 for <freebsd-bugs@FreeBSD.org>; Mon,  4 Jan 2016 23:36: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 u04Na5Ba078871
 for <freebsd-bugs@FreeBSD.org>; Mon, 4 Jan 2016 23:36:06 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 198062] FreeBSD 10.1-RELEASE kernel freezes on 'pci0: <ACPI PCI
 bus> on pcib0'
Date: Mon, 04 Jan 2016 23:36:05 +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.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jhkingsr@gmail.com
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198062-8-Hzjjgx5wOk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198062-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-198062-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: Mon, 04 Jan 2016 23:36:06 -0000

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

--- Comment #16 from Joseph King <jhkingsr@gmail.com> ---
(In reply to John Baldwin from comment #15)

I'm using the install ISO images of FreeBSD 10.x-64 bit line... now if the
system refuses to boot the install disc completely... How exactly do you
recommend using this "patch" which isn't a patch. I have even tried the ins=
tall
the OS using a different machine then bring the fresh installed drive back =
into
the server and it crashes just as horribly as a back door approach possibly
around this issue. Is this the method I should use to try out this "patch"
which isn't a patch.

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