Re: 7.0 Release amd64 Crashes after booting on ACER Aspire

2021-10-18 Thread Manuel Jose Blanca Molinos
.Hi, if it's helpful, I had a similar experience with a laptop with an A10-9600P. The solution I found was to disable the kernel piixpm driver. This driver underwent modifications 20 months ago. I also sent information to this list with the problem when I found it. Manuel Blanca On Mon, Oct 18,

Re: 7.0 Release amd64 Crashes after booting on ACER Aspire

2021-10-18 Thread Stuart Henderson
Possibly. Also if you could download kernels from the intermediate releases on the 6.6 system (ftp.eu.openbsd.org has an archive of many versions) and save them e.g. to /bsd.67, /bsd.68 and try booting them, try to find which version the problem started with? On 2021/10/18 05:47, Jon Fineman

Re: 7.0 Release amd64 Crashes after booting on ACER Aspire

2021-10-18 Thread Jon Fineman
I still have an image for 6.6. Would a sendbug from 6.6 be a help? On Mon, Oct 18, 2021 at 09:58:47AM +0100, Stuart Henderson wrote: 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

Re: 7.0 Release amd64 Crashes after booting on ACER Aspire

2021-10-18 Thread Stuart Henderson
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 wrote: I ran the disable command. While it was reordering the kernel

Re: 7.0 Release amd64 Crashes after booting on ACER Aspire

2021-10-17 Thread Jon Fineman
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

Re: 7.0 Release amd64 Crashes after booting on ACER Aspire

2021-10-17 Thread Stuart Henderson
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