From owner-freebsd-current@freebsd.org Thu Mar 22 10:52:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B154F59CF0 for ; Thu, 22 Mar 2018 10:52:12 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 393D56D6D6 for ; Thu, 22 Mar 2018 10:52:12 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P5Z00P00MZC1000@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Thu, 22 Mar 2018 10:51:38 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1521715898; bh=qIc69tpv6jn/+S90Vr/noS5kCnvI2jLoJ4NimfSJBGA=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=5SFI0Iso6GBwPu8v3OIa+qkJ5WPt0FBojLDJazKuj2D3MzBNcCKqgNFTGlFjgdpeS t/JsRQQkX8jhnxLIudsGCJn8suFoVb6HMfTpAzrxVGm7EZgQVUhbRmHMJypMr18Icb pKeZ/WKwoLUZieHOAfPpVMYOvHknkQXJqwpw2uTHZqqpmz0KvNp8DE7WAxImHSarv2 C2cz/RA4hsb/BwgfztentM2Ev0Ydor3SafpwtlNzy+tvn/13AvTZ0cJKWvecVUyyMf 7t+bF07XFBOisaJMxdZCZKEGZeR3bBvCcv87g+zHDqmEnWDIAjkVosKqAT87uvGoST Cvey5oMzP7D8g== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P5Z00IPXNHX7240@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Thu, 22 Mar 2018 10:51:36 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-22_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1803220131 From: Toomas Soome Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Call for Testing: UEFI Changes Date: Thu, 22 Mar 2018 12:51:33 +0200 References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> To: FreeBSD Current In-reply-to: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> Message-id: <901CE994-0A28-4538-A4A9-A23E0B7E4879@me.com> X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 10:52:12 -0000 > On 22 Mar 2018, at 12:13, Jakob Alvermark wrote: >=20 > Hi! >=20 >=20 > Just updated to r331345. >=20 > Two problems: >=20 > 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still = included in loader.rc. Loader fails to load it and subsequently fails to = load modules. Reinstalling efi.4th problem 2 appears. >=20 >=20 > 2. Fixing problem 1 and adding efirt_load=3D"YES" to /boot/loader.conf = makes the kernel panic instantly. Photo of panic: = https://photos.app.goo.gl/ph3yQukOAUdQpsvK2 >=20 >=20 > Jakob The efi.4th was introduced and later removed by Warner, a bit too = hastily perhaps=E2=80=A6 but perhaps it is better to note the partial = revert of the removal or something like that:) rgds, toomas >=20 >=20 > On 03/22/18 01:45, Kyle Evans wrote: >> Hello! >>=20 >> A number of changes have gone in recently pertaining to UEFI booting >> and UEFI runtime services. The changes with the most damaging >> potential are: >>=20 >> We now put UEFI runtime services into virtual address mode, fixing >> runtime services with U-Boot/UEFI as well as the firmware >> implementation in many Lenovos. The previously observed behavior was = a >> kernel panic upon invocation of efibootmgr/efivar, or a kernel panic >> just loading efirt.ko or compiling EFIRT into the kernel. >>=20 >> Graphics mode selection is now done differently to avoid regression >> caused by r327058 while still achieving the same effect. The observed >> regression was that the kernel would usually end up drawing >> incorrectly at the old resolution on a subset of the screen, due to >> incorrect framebuffer information. >>=20 >> Explicit testing of these changes, the latest of which happened in >> r331326, and any feedback from this testing would be greatly >> appreciated. Testing should be done with either `options EFIRT` in >> your kernel config or efirt.ko loaded along with updated bootloader >> bits. >>=20 >> I otherwise plan to MFC commits involved with the above-mentioned >> changes by sometime in the first week of April, likely no earlier = than >> two (2) weeks from now on April 4th. >>=20 >> Thanks, >>=20 >> Kyle Evans >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail = to"freebsd-current-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"