NovaCustom NV41 Series: doesn't reboot after S3 suspend

[wessel-novacustom]

Qubes OS release

Qubes OS R4.2.3

Brief summary

The laptop does not reboot if S3 suspend has been triggered before.

This happens on a new clean installation, kernel version 6.6. Dasharo version v1.7.2.

Steps to reproduce

1. Set S3 suspend-to-RAM in the UEFI firmware settings. Save the settings with F10 --> Y --> Enter --> Ctrl + Alt + Del.
2. Boot to Qubes OS.
3. Trigger S3 suspending in whatever way (closing lid or via GUI).
4. Reboot the laptop.

Expected behavior

The laptop reboots.

Actual behavior

The screen remains black and the laptop doesn't restart.

The laptop needs a forced restart by holding the power button until it switches off, then start again by pressing the power button normally.

Video

no-reboot-after-S3.mp4

[marmarek]

Native Linux (same kernel) reboots just fine, so it it something related to Xen.
I tried already reboot=acpi option (common workaround for broken firmware), but it didn't help

[marmarek]

I checked also that generally runtime services work after suspend (at least GetVariable works).

[wessel-novacustom]

If it's firmware related, please let me know and I will move the issue to Dasharo.

[marmarek]

I tried the same on MSI and got similar failure. But here I got more logs:

(XEN) Hardware Dom0 shutdown: rebooting machine
CPU Index 0 - APIC 0 Unexpected Exception:13 @ 10:46f2b5e1 - Halting
Code: 0 eflags: 00010002 cr2: 00000000
eax: 00000005 ebx: 46f210a0 ecx: 0000003a edx: 00000000
edi: 00000005 esi: 00000000 ebp: 469a19f8 esp: 469a19dc

0x46f2b5a0:	46 ff 50 14 59 59 c3 55 
0x46f2b5a8:	8b ec 83 ec 14 56 57 8b 
0x46f2b5b0:	f2 89 4d fc 8b 4d fc 0f 
0x46f2b5b8:	32 ff 75 10 8b ce ff 75 
0x46f2b5c0:	0c 52 8b 55 08 50 e8 9e 
0x46f2b5c8:	00 00 00 8b f8 8b f2 83 
0x46f2b5d0:	c4 10 89 7d f0 89 75 f4 
0x46f2b5d8:	8b 55 f4 8b 45 f0 8b 4d 
0x46f2b5e0:	fc 0f 30 8b c7 8b d6 5f 
0x46f2b5e8:	5e c9 c3 53 56 57 6a fe 
0x46f2b5f0:	8b da 8b f1 8b 4c 24 14 
0x46f2b5f8:	83 c8 ff 8b 54 24 1c 5f 
0x46f2b600:	d3 e7 8b cb d3 e0 f7 d7 
0x46f2b608:	23 c7 d3 e2 f7 d0 23 d7 
0x46f2b610:	5f 23 c6 5e 0b c2 5b c3 
0x46f2b618:	55 8b ec 83 ec 10 83 4d 
0x469a1a58:	0x46ba00b0
0x469a1a54:	0x01000000
0x469a1a50:	0x00000006
0x469a1a4c:	0x46f24000
0x469a1a48:	0x00000007
0x469a1a44:	0x46f210a0
0x469a1a40:	0x0000000b
0x469a1a3c:	0x46f2ba25
0x469a1a38:	0x469a1a60
0x469a1a34:	0x00000000
0x469a1a30:	0x00000000
0x469a1a2c:	0x46f25000
0x469a1a28:	0x46f2b93b
0x469a1a24:	0x46f2920b
0x469a1a20:	0x00000100
0x469a1a1c:	0x469a1a38
0x469a1a18:	0x46f2920b
0x469a1a14:	0x46f25000
0x469a1a10:	0x46f25000
0x469a1a0c:	0x46f26000
0x469a1a08:	0x00000000
0x469a1a04:	0x00000000
0x469a1a00:	0x00000001
0x469a19fc:	0x46f291f8
0x469a19f8:	0x469a1a58 <-ebp
0x469a19f4:	0x0000003a
0x469a19f0:	0xffffffff
0x469a19ec:	0x00000000
0x469a19e8:	0x00000005
0x469a19e4:	0x00000003
0x469a19e0:	0x00000006
0x469a19dc:	0x46f24000 <-esp

[marmarek]

And on StarBook (also with coreboot, but not Dasharo) it works fine.

There are some more differences in hardware (for example 13th gen CPU vs 12th gen in NV41), but it still looks like some issue with Dasharo (or, less likely, a Xen issue that manifest itself only with Dasharo).

[wessel-novacustom]

And on StarBook (also with coreboot, but not Dasharo) it works fine.

There are some more differences in hardware (for example 13th gen CPU vs 12th gen in NV41), but it still looks like some issue with Dasharo (or, less likely, a Xen issue that manifest itself only with Dasharo).

Still, it doesn't happen on Ubuntu or Fedora. Nevertheless, I will inform the Dasharo team to check what they can do.

[wessel-novacustom]

Dasharo/dasharo-issues#1097