Mark Kettenis <[email protected]> writes:

>> Date: Tue, 30 Dec 2025 07:46:16 +0100
>> From: Rafael Sadowski <[email protected]>
>> 
>> On Mon Dec 29, 2025 at 06:17:16PM -0800, [email protected] wrote:
>> >    I have the same machine and it works fine also, or at least it did last
>> >    time I tried.
>> >    Does it work if you ZZZ from the text console, right after boot?
>> >    -ml
>> 
>> Yes and no. Instead of getting stuck in the kernel boot I ends up in a
>> wired white artefact screen and then the only thing that helps is a hard
>> reset.
>> 
>> I also reset my BIOS settings to factory defaults. No changes except
>> that my OpenBSD EFI boot entry was gone.
>> 
>> Perhaps something with the GPU:
>> 
>> dmesg| grep amd
>>     [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> amdpmc0 at acpi0: PEP_
>> amdpmc0: SMU program 0 version 76.93.0
>> amdgpio0 at acpi0 GPIO uid 0 addr 0xfed81500/0x400 irq 7, 184 pins
>> amdgpu0 at pci6 dev 0 function 0 "ATI Hawk Point" rev 0xd0
>> drm0 at amdgpu0
>> amdgpu0: msi
>> amdgpu0: IP DISCOVERY GC 11.0.1 12 CU rev 0x0c
>> amdgpu0: 1920x1200, 32bpp
>> wsdisplay0 at amdgpu0 mux 1: console (std, vt100 emulation), using wskbd0
>
> My X13 Gen 4 AMD has essentially the same GPU:
>
> amdgpu0 at pci5 dev 0 function 0 "ATI Phoenix" rev 0xdd
> drm0 at amdgpu0
> amdgpu0: msi
> amdgpu0: IP DISCOVERY GC 11.0.1 12 CU rev 0x09
> amdgpu0: 1920x1200, 32bpp
>
> Hibernate "works" on this machine but:
>
> * After unhibernate, the framebuffer is filled with random crap; we
>   probably need to clear it in the driver somewhere.

Ditto on my T14Gen5.

>
> * After unhibernate, qwx(4) is somewhat hosed.  It works, but if you
>   try to down the interface, it hangs.  It seems that the "head
>   pointer" for one of the ring gets corrupted and this makes the
>   driver go into an infinite loop.  I can break into that loop using
>   CTRL-ALT-ESC though (sysctl ddb.console=1).  I'm investigating this
>   issue.

I haven't used my qwx(4) in combo with hibernate that I can recall.

>
> * Sometimes I get a kernel that always produces a 
>
>     "unhibernate failed: original kernel changed"

Ditto. Though when this happened a power cycle sometimes restored
hibernate/resume functionality for me.

>
>   message.

-- 
.... Ken

Reply via email to