Date: Wed, 24 Mar 2021 00:52:29 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-current@freebsd.org Cc: Warner Losh <imp@FreeBSD.org>, Ryan Moeller <freqlabs@FreeBSD.org> Subject: Re: 13.0-RELEASE schedule update: PR 251866 (unable to boot some modern hardware) Message-ID: <0d13be78-78a7-e25f-4866-282db8aa8de0@gmail.com> In-Reply-To: <35911aaf-cd1f-4085-644f-f9be53bd0a0b@gmail.com> References: <20210323185731.GV92054@FreeBSD.org> <35911aaf-cd1f-4085-644f-f9be53bd0a0b@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/03/2021 00:42, Graham Perrin wrote: > On 23/03/2021 18:57, Glen Barber wrote: >> At least one issue has been brought to our attention that affects new >> installations, which as we currently have no precedent for re-rolling >> ISOs and/or VM images post-release, warrant adding RC4 to the 13.0 >> schedule. >> >> Please be advised that we are still only accepting critical changes >> only, with the exception of a few post-RC3 requests for approval that >> have trickled in. > > … > > I should probably plead for the essence of > <https://cgit.freebsd.org/src/commit/?id=b304cd9789ca7ff3df629af42a976450e8660a11>, > very recently committed to stable/12, to be committed to releng/13.0 > and main. > > If I understand correctly, the effects of PR 251866 > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866>; are not > limited to vmware. > > The same symptoms – essentially, unable to boot – are seen with (for > example) HP ProBook 440 G7. > > Thanks > Sorry! Ignore the suggestion. <https://cgit.freebsd.org/src/commit/?id=4d6047edb675e52b8fad57135ab3ded8e66d0dac>; is already in main. Maybe we need to find (or create) a separate bug for hardware not booting with the same symptoms. Not expecting a fix in time for 13.0.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0d13be78-78a7-e25f-4866-282db8aa8de0>