https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #50 from sp...@itl.ua ---
(In reply to Toomas Soome from comment #45)
> Unfortunately, with those legacy cases, we really can not fix it just by
> reading and changing the code -- we need to understand under which conditions
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #49 from Cy Schubert ---
(In reply to Warner Losh from comment #48)
You were right, partially. I tested using my disaster recover USB disk (with
MBR), which contains a fully installed FreeBSD 15-CURRENT on UFS2, with a ZFS
pool
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #48 from Warner Losh ---
the other thing to try is to boot /boot/loader_4th or /boot/loader_simp from
the boot2 boot blocks (you have to interrupt at the right place). Those are
smaller and might help determine if it's size or c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #47 from Warner Losh ---
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 sus
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #46 from Cy Schubert ---
(In reply to Toomas Soome from comment #45)
As a developer I totally get it.
I did manage to capture a photo of seven "disk0:Read NNN sectors..." messages
before it disappeared.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
Toomas Soome changed:
What|Removed |Added
CC||tso...@me.com
--- Comment #45 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #44 from Cy Schubert ---
I just received one of these (840 G5). The 15-CURRENT memstick.img boots nicely
in EFI mode. In legacy mode attempting to boot a clone of my Acer laptop's
disk, I believe (because it flashes a couple of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #43 from sp...@itl.ua ---
Booting from the image
FreeBSD-14.0-ALPHA4-amd64-20230901-4c3f144478d4-265026-mini-memstick.img
gives the same effect on my HP EliteBook as I've reported previously - reboots
while AHCI mode is set in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #42 from Graham Perrin ---
(In reply to NoahD from comment #37)
> … not able to use the legacy BIOS boot for nvme. …
(In reply to NoahD from comment #41)
> … 14.0-CURRENT #1 plus-RELENG_23_05-n256102-7cd3d043045: Mon
> May 2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #41 from NoahD ---
(In reply to Graham Perrin from comment #40)
FreeBSD pfsense.darkkdomain.lan 14.0-CURRENT FreeBSD 14.0-CURRENT #1
plus-RELENG_23_05-n256102-7cd3d043045: Mon May 22 15:33:52 UTC 2023
root@freebsd:/var/jenk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #40 from Graham Perrin ---
(In reply to NoahD from comment #39)
uname -aKU
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
--- Comment #39 from NoahD ---
(In reply to Graham Perrin from comment #38)
FreeBSD 14.0-CURRENT amd64
That's all it says when I use uname -mrs
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255072
Graham Perrin changed:
What|Removed |Added
Keywords||needs-qa
Component|standa
13 matches
Mail list logo
