Date: Sun, 28 Jul 2024 17:34:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255072] boot (legacy): no progress beyond 'BIOS DRIVE D: is disk1' Message-ID: <bug-255072-227-ieVXNGiDdE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255072-227@https.bugs.freebsd.org/bugzilla/> References: <bug-255072-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255072 --- Comment #47 from Warner Losh <imp@FreeBSD.org> --- Each one of these is likely a silent crash. Likely caused by the boot loader getting too big for the specific machine in question, but maybe some other regression that's not hitting other machines. I suspect that these will nev= er be fixed since the common solution is "upgrade to UEFI". If you want / need= it fixed, though, your best bet is to bisect the boot loader from "last known working one" to the first commit that breaks it. That will suggest what to = put in by way of debugging. It's something that can be done asynchronously to developer involvement. And will narrow things so we can figure it out. Tracing it to a release isn't helpful enough. There's too many commits betw= een working and not working to help. Since these messages are from /boot/loader, recovery isn't terrible. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255072-227-ieVXNGiDdE>