me again, I've spent the day compiling aerc; we'll see how it goes.
I see that it was not a good idea to send so many images unsolicited to the
mailing list; my thought process was that the docs say a legible photo is OK in
the case of a kernel trace. I'll start with text going forward.
Here is the information from the kernel panic in which I hadn't logged in:
aml_rwgen: unregistered RegionSpace 0x5
0xffff800001955008 cnt:01 stk:00 !!type: 0
Not Integer
22c5a Called: \_SB_.PC00.LPCB.EC0V.SNTM
22cab Called: \_SB_.PC00.LPCB.EC0_._Q77
panic: aml_die aml_eval:3664
Stopped at db_enter+0x14: popq %rbp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*195263 48102 0 0x14000 0x40000200 0K acpi0
220971 51719 0 0x14000 0x200 2 sensors
db_enter() at db_enter+0x14
panic(-) at panic+0xd5
aml_nodename(-) at aml_nodename
aml_eval(-) at aml_eval+0x4b7
aml_parse(-) at aml_parse+0x2675
aml_parse(-) at aml_parse+0x474
aml_eval(-) at aml_eval+0x31d
aml_parse(-) at aml_parse+0x2675
aml_eval(-) at aml_eval+0x31d
aml_evalnode(-) at aml_evalnode+0xaf
acpiec_gpehandler(-) at aml_acpiec_gpehandler+0x7f
acpi_thread(-) at acpi_thread+0x211
end trace frame: 0x0, count: 3
I will additionally copy the arguments in the trace or do any sort of
decompilation yall might want. Thank you for your time.
