Please have in mind that I have retyped these by hand from the screen and the
first example might
not be acurate as I've retyped it of a blurry photo I made. But the other
reboot attempts using
boot> boot -d
ddb> w db_panic 0
ddb> c
got different messages on screen some of them might be more informant than
others as the last one of these three
only had very few whitebackground places at ' [s]c[]p[]i[]ew[]s[]kb[]d[]0a '
(substituting with [] for those places
And I also made photos of these in case those could be more useful than this.
And I'm writing these because there
appears to only be a single file in /var/crash thats called minfree containing
text 4096.
So in the time being this all I have. I could reproduce some more of these
messages assuming they're useful. I'll read
these man pages related to gathering useful information in such cases for now.
Unless you've got other suggestions
0)r a t ondrm0: 1280x768, 32bpp
wsdisplay at radeondrm0 mux 1: consol e ( s t d, vh an le r u+l0axtfif n
), using wskbd0
acpi_thread(ffff80000002d170) at wsdisplay0: screen 1-5 added (std, vt100
emulation)
acr i d t hore d r + 0 x 1 b 8 R
KeSn
d trace frame: 0x0, count: 253
End of stack trace.
syncing disks... done
dumping to dev 4,1 offset 492575
//-----
radeondrm0: 1280x768, 32bpp
awcspdiiesp _ta py n a d l e a de o nd
0 mux 1: console (std, vt100 emulation), using wskbd0
acpi_thread(ffff80000002d170) at wsdisplay0: screen 1-5 added (std, vt100 acol_
t h r e a
+0x1r a d
a n d r m t : o URa
g: 0x0, count: 253 n
End of stack trace.
syncing disks... done
dumping to dev 4,1 offset 492575
dump
//----
radeondrm0: 1280x768, 32bpp
wsdisplay0 at radeon drm0 mux 1: console (std, vt100 emulation), a sc p i ew s
kb d 0a
ndler(ffff8000000028400,16,ffff80000013b000) at acpiec_gpehandler+0xff
wsdisplay0: screen 1-5 added (std, vt100 emulation)
radeondrm1: TURKS
acpi_thread(ffff80000002d170) at acpi_thread+0x1b8
end trace frame: 0x0, count: 253
End of stack trace.
syncing disks... done
dumping to dev 4,1 offset 492575
dump
Are you able to connect an external display to confirm that is the case?
Failing that or serial it should also be possible to disable panic and
get a trace via /var/crash as described in crash(8).
As this likely occurs before the rc script runs you will need to use a
kernel with the following diff or
boot> boot -d
ddb> w db_panic 0
ddb> c
Index: sys/kern/subr_prf.c
===================================================================
RCS file: /cvs/src/sys/kern/subr_prf.c,v
retrieving revision 1.102
diff -u -p -r1.102 subr_prf.c
--- sys/kern/subr_prf.c 28 Nov 2020 17:53:05 -0000 1.102
+++ sys/kern/subr_prf.c 13 Feb 2021 06:08:57 -0000
@@ -104,7 +104,7 @@ const char *faultstr; /* page fault stri
/*
* Enter ddb on panic.
*/
-int db_panic = 1;
+int db_panic = 0;
/*
* db_console controls if we can be able to enter ddb by a special key
