From owner-freebsd-bugs@freebsd.org  Wed Oct 11 00:32:33 2017
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 14E45E4184A
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 11 Oct 2017 00:32: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 0335F72AF3
 for <freebsd-bugs@FreeBSD.org>; Wed, 11 Oct 2017 00:32: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 v9B0WWlR036553
 for <freebsd-bugs@FreeBSD.org>; Wed, 11 Oct 2017 00:32:32 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 214718] x86bios panics at boot if it cannot obtain memory
Date: Wed, 11 Oct 2017 00:32: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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: commit-hook@freebsd.org
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-214718-8-uLxiNVG8O6@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214718-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-214718-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.23
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: Wed, 11 Oct 2017 00:32:33 -0000

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

--- Comment #3 from commit-hook@freebsd.org ---
A commit references this bug:

Author: emaste
Date: Wed Oct 11 00:31:54 UTC 2017
New revision: 324510
URL: https://svnweb.freebsd.org/changeset/base/324510

Log:
  MFC r309151: Use explicit 0x200000 for the amd64 kernel physaddr

  (instead of MAXPAGESIZE)

  MAXPAGESIZE is not well defined by the GNU ld documentation.
  Different linkers, and different versions of the same linker, use
  different MAXPAGESIZE values. Current versions of GNU gold and LLVM's
  lld use 4K. When set to 4K the kernel panics at boot due to an issue
  with x86bios.

  Here we want the kernel physaddr to be the amd64 superpage size, so use
  that value (2MB) explicitly. With this change GNU gold and LLVM lld can
  link a working amd64 kernel.

  PR:           214718 (x86bios)
  Sponsored by: The FreeBSD Foundation

Changes:
_U  stable/11/
  stable/11/sys/conf/ldscript.amd64

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