Date: Fri, 3 Mar 2017 12:22:04 +0300 From: Alex Deiter <alex.deiter@gmail.com> To: Chris H <bsd-lists@bsdforge.com> Cc: freebsd-current <freebsd-current@freebsd.org>, dexuan@freebsd.org Subject: Re: Boot failure - svn up from this morning Message-ID: <E46FA7A7-9B98-4104-A41B-1BBFB121ECD0@gmail.com> In-Reply-To: <a49d5cc64aeb8fd414d3e04073d05474@ultimatedns.net> References: <alpine.BSF.2.20.1703022145590.27580@mail.neu.net> <ad4fcc3e2df6b2fc422004621c2de329@ultimatedns.net> <4D3C46D7-3EBF-47AE-BFFE-37ECEA4721FD@gmail.com> <a49d5cc64aeb8fd414d3e04073d05474@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, The same issue with FreeBSD 12.0-CURRENT-r314563: elf64_loadimage: could not read symbols - skipped! http://picpaste.com/IMG_1764-vfZl1l5o.JPG I suspect regression after:=20 Revision 314547 - Directory Listing=20 Modified Thu Mar 2 07:25:50 2017 UTC (25 hours, 54 minutes ago) by = dexuan loader.efi: reduce the size of the staging area if necessary The loader assumes physical memory in [2MB, 2MB + EFI_STAGING_SIZE) is Conventional Memory, but actually it may not, e.g. in the case of Hyper-V Generation-2 VM (i.e. UEFI VM) running on Windows Server 2012 R2 host, there is a BootServiceData memory block at the address 47.449MB and the memory is not writable. Without the patch, the loader will crash in efi_copy_finish(): see PR 211746. The patch verifies the end of the staging area, and reduces its size if necessary. This way, the loader will not try to write into the BootServiceData memory any longer. Thank Marcel Moolenaar for helping me on this issue! The patch also allocates the staging area in the first 1GB memory. See the comment in the patch for this. PR: 211746 Reviewed by: marcel, kib, sephe Approved by: sephe (mentor) MFC after: 2 weeks Sponsored by: Microsoft Differential Revision:=09 https://reviews.freebsd.org/D9686 Alex Deiter alex.deiter@gmail.com > On 3 Mar 2017, at 09:20, Chris H <bsd-lists@bsdforge.com> wrote: >=20 > On Thu, 2 Mar 2017 21:32:39 -0800 "Ngie Cooper (yaneurabeya)" > <yaneurabeya@gmail.com> wrote >=20 >>> On Mar 2, 2017, at 21:16, Chris H <bsd-lists@bsdforge.com> wrote: >>>=20 >>> On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN <andy@neu.net> wrote >>>=20 >>>> Hi: >>>>=20 >>>> I'm having a major problem after updating a 12-current machine = today. >>>> After buildworld/kernel/install cycle on reboot I'm getting the = following >>>> failure: >>>>=20 >>>> "/boot/kernel/kernel text=3D0xb7716f data=3D0x100548+0x398358 >>>> elf64_loadimage: read failed >>>> can't load file '/boot/kernel/kernel': input/output error >>>> can't load file '/boot/kernel/kernel': input/output error >>>>=20 >>>> OK boot kernel.old >>>> elf64_loadimage: read failed >>>> can't load file '/boot/kernel.old/kernel': input/output error >>>> can't load file '/boot/kernel.old/kernel': input/output error" >>>>=20 >>>> I have never experienced this failure before, and don't know how to >>>> proceed. Any help recovering from this would be greatly = appreciated. >>>> Thanks in advance. >>>=20 >>> I don't suppose you could post the output of >>> uname -a >>>=20 >>> and maybe a copy of dmesg(8) could you? >>=20 >> That would be good, but I don=E2=80=99t know if it=E2=80=99s possible = (the OP is noting >> that the boot is broken when executing loader(8)..). -Ngie >=20 > Indeed. But that doesn't stop the OP from booting from the > install media. ;-) :-) >=20 > --Chris >=20 >=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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E46FA7A7-9B98-4104-A41B-1BBFB121ECD0>