[Bug 234606] FreeBSD 12.0 install from DVD aborts (UEFI/GPT HDD multiboot)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Jan 25 15:38:57 UTC 2020


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

Bernd Roth <gwbr0601 at yahoo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gwbr0601 at yahoo.de

--- Comment #5 from Bernd Roth <gwbr0601 at yahoo.de> ---
Hello, I'm on a Supermicro A2SDi-8C+-HLN4F + 16GB RAM with 11-RELEASE
installation that was upgraded to 12.0 RELEASE via freebsd-update. I did the
update to 12.1 before christmas but i think i haven't done a reboot because my
latest known uptime was approx. 180 days. I learned about rc.local now and
tested my setup via shutdown -r and after that i got the same failure structure
as seen on the https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200762 -
system freeze after the EFI framebuffer information lines; ending with "masks
0x...".

Still in operator PANIC mode i've got FreeBSD-12.1-RELEASE-amd64-memstick.img
up and running and managed to reduce rc.conf to minimum modules and to get
write access to /boot/loader.conf which is 

verbose_loading="YES"

now. I also tried kern.vty=sc, hw.vga.textmode=1, but with no help. The system
still freeze after the masks line. I found some other logfiles and the next
line after the masks line usually may be ---<<BOOT>>--- which is not seen here.
I noticed most of the memstick loader files in /boot/ are dated nov 01 05:14
while some of my loader files are dec 10 10:40 and others are feb 15 2019.
Meanwhile i extracted base.txz and kernel.txz from the image above into the
sytem without success.

I noticed i have 2 kernel and changed to the other one. I see it's
/boot/kernel.old/kernel now but it still freezes.

Please recheck bug report header. If this is valid to be the same bug then it
does affect me too.

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


More information about the freebsd-bugs mailing list