Date: Mon, 7 Mar 2016 08:41:10 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Julian Elischer <julian@FreeBSD.ORG> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r296428 - head/sys/boot/common Message-ID: <AC0A9708-B618-4D05-8532-BD451AB94A60@FreeBSD.org> In-Reply-To: <56DCD52F.4010709@freebsd.org> References: <201603061557.u26FvhMi033982@repo.freebsd.org> <56DCD52F.4010709@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_4A2362DC-FF43-4011-B769-2B8EF67F4E4D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 07 Mar 2016, at 02:11, Julian Elischer <julian@FreeBSD.ORG> wrote: >=20 > On 6/03/2016 7:57 AM, Dimitry Andric wrote: >> Author: dim >> Date: Sun Mar 6 15:57:43 2016 >> New Revision: 296428 >> URL: https://svnweb.freebsd.org/changeset/base/296428 >>=20 >> Log: >> Since kernel modules can now contain sections of type = SHT_AMD64_UNWIND, >> the boot loader should not skip over these anymore while loading = images. >> Otherwise the kernel can still panic when it doesn't find the = .eh_frame >> section belonging to the .rela.eh_frame section. >> Unfortunately this will require installing boot loaders from = sys/boot >> before attempting to boot with a new kernel. >=20 > what happens to someone who doesn't replace their bootblocks? > Or is this just the loader? This just about the loaders, e.g. loader, loader.efi and zfsloader. > The general way we have handled this sort of thing in the past is that = we do something > that produces a nagging message for a decent time before it becomes = mandatory. >=20 > I don't like the idea of people being caught unaware by this.. >=20 > Can you please give a more detailed description of what happens? If you preload modules with .eh_frame sections in them (such as aesni.ko) from your loader.conf, your kernel will panic very early in the boot. If you don't preload any modules, or load only modules without .eh_frame sections (most of of them), there is no issue at all. -Dimitry --Apple-Mail=_4A2362DC-FF43-4011-B769-2B8EF67F4E4D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.29 iEYEARECAAYFAlbdMJwACgkQsF6jCi4glqNmnwCghjU+Gnvlp0htxawIFeEwm4Pp eeAAoNfuD4Ak1gyuKmjJKA8QixQ/Mo7p =H4e8 -----END PGP SIGNATURE----- --Apple-Mail=_4A2362DC-FF43-4011-B769-2B8EF67F4E4D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC0A9708-B618-4D05-8532-BD451AB94A60>