I guess the embedded controller is actually shutting the machine down then,
rather than just a spurious error behind reported.
--
Sent from a phone, apologies for poor formatting.
On 18 October 2021 00:44:09 Jon Fineman <j...@fineman.me> wrote:
I ran the disable command. While it was reordering the kernel it
shutoff. This time though with no temperature messages to the console.
I also tried to disable amdgpu, and got the same results.
On Sun, Oct 17, 2021 at 11:29:28PM +0100, Stuart Henderson wrote:
Please boot with "disable acpitz" like you showed in the attached file, and
generate a bug report by running sendbug as root (if you need to send from a
different system, redirect sendbug -P and move the file across and edit/send),
running it as root will include an encoded copy of the acpi tables which may
help identify what's wrong.
--
Sent from a phone, apologies for poor formatting.
On 17 October 2021 22:06:09 Jon Fineman <j...@fineman.me> wrote:
I started a new report since I have newer info. The old thread was:
https://marc.info/?l=openbsd-bugs&m=159780203127790&w=2
Again since it shuts down I can't generate a bug report from the
laptop. The original thread has a dmesg from 6.6.
In 7.0 I get the same behavior but now I get an added message to the
console:
acpitz0: critical temperature exceeded 127c, shutting down
I have attached the messages file from /var/log (it just contains the
same messages about failing to load firmware and amdgpu.
I attached a pic of the console.
My laptop is not running hot. I ran 6.6 on it fine and since Aug of
2020 I have been running Arch on it fine.
--
