https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285867
Mark Millard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #16 from Mark Millard <[email protected]> --- (In reply to Henrich Hartzer from comment #15) Can you capture and upload verbose boot output for folks to look at, say via kern.smp.disabled=1 use or full safe mode? (dmesg -a output) Another option might be USB boot media that could later be examined from a working system. ( /mnt/var/log/messages ) The boot would have to get far enough along to have updated the file. A serial console capture would be nice but may be unlikely. Part of what I wonder about is what such reports about memory address ranges when you have 8 GiBytes of RAM --if such information can be captured. Folks with appropriate background might be able to note if there are any oddities not handled by FreeBSD. Another idea would be to substitute the UEFI loader from FreeBSD 4.1-RELEASE to see if the problem is FreeBSD-loader-vintage specific in some way rather than just FreeBSD-kernel-specific. -- You are receiving this mail because: You are the assignee for the bug.
