Why Lenovo IdeaPad Gaming 3 15ARH7 - Type 82SB NOT Support

User Support Hardware Issues
41

Not sure it’s a critical error, but at 16:53:58 there are many kernel errors traces, usually that doesn’t look good

Mar 28 16:53:58 dom0 kernel: CPU: 4 PID: 4961 Comm: qrexec-client Tainted: G        W          6.6.21-1.qubes.fc37.x86_64 #1
Mar 28 16:53:58 dom0 kernel: Hardware name: LENOVO 82SB/LNVNB161216, BIOS JNCN50WW(V2.10) 01/16/2024
Mar 28 16:53:58 dom0 kernel: RIP: e030:evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
Mar 28 16:53:58 dom0 kernel: Code: ba 01 00 00 00 be 1d 00 00 00 48 8d bb 88 00 00 00 e8 3e d3 43 c0 eb b4 8b 76 20 48 89 da 48 c7 c7 70 d2 24 c0 e8 fa cb 0c c0 <0f> 0b e9 61 ff ff ff 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90
Mar 28 16:53:58 dom0 kernel: RSP: e02b:ffffc900439a3d48 EFLAGS: 00010082
Mar 28 16:53:58 dom0 kernel: RAX: 0000000000000000 RBX: ffff88807eacc0c0 RCX: 0000000000000027
Mar 28 16:53:58 dom0 kernel: RDX: ffff888151d21588 RSI: 0000000000000001 RDI: ffff888151d21580
Mar 28 16:53:58 dom0 kernel: RBP: ffff88810b67fd80 R08: 0000000000000000 R09: ffffc900439a3be0
Mar 28 16:53:58 dom0 kernel: R10: 0000000000000003 R11: ffffffff81f46248 R12: ffff888029e3eca4
Mar 28 16:53:58 dom0 kernel: R13: ffff888029e3ed60 R14: ffff88810b67fd80 R15: ffff888029e3ec00
Mar 28 16:53:58 dom0 kernel: FS:  00007bfda317dd40(0000) GS:ffff888151d00000(0000) knlGS:0000000000000000
Mar 28 16:53:58 dom0 kernel: CS:  10000e030 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 28 16:53:58 dom0 kernel: CR2: 00005d9c4e2c0000 CR3: 0000000103e04000 CR4: 0000000000050660
Mar 28 16:53:58 dom0 kernel: Call Trace:
Mar 28 16:53:58 dom0 kernel:  <TASK>
Mar 28 16:53:58 dom0 kernel:  ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
Mar 28 16:53:58 dom0 kernel:  ? __warn+0x81/0x130
Mar 28 16:53:58 dom0 kernel:  ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
Mar 28 16:53:58 dom0 kernel:  ? report_bug+0x171/0x1a0
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? prb_read_valid+0x1b/0x30
Mar 28 16:53:58 dom0 kernel:  ? handle_bug+0x41/0x70
Mar 28 16:53:58 dom0 kernel:  ? exc_invalid_op+0x17/0x70
Mar 28 16:53:58 dom0 kernel:  ? asm_exc_invalid_op+0x1a/0x20
Mar 28 16:53:58 dom0 kernel:  ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
Mar 28 16:53:58 dom0 kernel:  ? evtchn_interrupt+0xb6/0xc0 [xen_evtchn]
Mar 28 16:53:58 dom0 kernel:  __free_irq+0x114/0x330
Mar 28 16:53:58 dom0 kernel:  free_irq+0x32/0x70
Mar 28 16:53:58 dom0 kernel:  unbind_from_irqhandler+0x31/0xb0
Mar 28 16:53:58 dom0 kernel:  evtchn_release+0x2b/0xa0 [xen_evtchn]
Mar 28 16:53:58 dom0 kernel:  __fput+0xf5/0x290
Mar 28 16:53:58 dom0 kernel:  __x64_sys_close+0x3d/0x80
Mar 28 16:53:58 dom0 kernel:  do_syscall_64+0x5f/0x90
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? syscall_exit_work+0x103/0x130
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? do_syscall_64+0x6b/0x90
Mar 28 16:53:58 dom0 kernel:  ? syscall_exit_work+0x103/0x130
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? do_syscall_64+0x6b/0x90
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? syscall_exit_work+0x103/0x130
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? do_syscall_64+0x6b/0x90
Mar 28 16:53:58 dom0 kernel:  ? __irq_exit_rcu+0x4b/0xc0
Mar 28 16:53:58 dom0 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Mar 28 16:53:58 dom0 kernel:  ? xen_pv_evtchn_do_upcall+0x54/0xb0
Mar 28 16:53:58 dom0 kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Mar 28 16:53:58 dom0 kernel: RIP: 0033:0x7bfda33049e4

although it’s already known and seems harmless Linux 6.7+ warning: "Interrupt for port 107, but apparently not enabled" · Issue #8914 · QubesOS/qubes-issues · GitHub

42

From the logs, it seems you installed Qubes OS, then had the “qubes os post installation” process that asks for templates to install and qubes settings, twice?

At 17:05:30 anaconda seems to try again to create the LVM pool…

I’d just reinstall and see if it works better :woman_shrugging:

43

I installed Qubes 3 times today. I don’t know if the error is from the hardware or from the system

44

do you get this screen exactly once? What if you uncheck debian and whonix?

45

I didn’t find any useful info there, the log just abruptly cuts off at some point e.g.:

Mar 28 17:06:18 dom0 kernel: xen-blkback: backend/vbd/1/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
Mar 28 17:06:18 dom0 kernel: xen-blkback: backend/vbd/1/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
Mar 28 17:06:18 dom0 kernel: xen-blkback: backend/vbd/1/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
Mar 28 17:06:18 dom0 kernel: xen-blkback: backend/vbd/1/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
-- Boot b96f4c37b7d24710867dcf2a52ac5a28 --
Mar 28 17:50:49 dom0 systemd-journald[261]: Received SIGTERM from PID 1 (systemd).
Mar 28 17:50:49 dom0 systemd[1]: RTC configured in localtime, applying delta of -240 minutes to system time.

Maybe there will be some useful info in the xen log files:

/var/log/xen/console/hypervisor.log*
46

I saw this screen twice and yes I chose only Fedora

47

Where can I find this file?

48

In dom0 there may be multiple files:

/var/log/xen/console/hypervisor.log
/var/log/xen/console/hypervisor.log-20240323
...
49

Type this command in the terminal ?

50

You can print it using this command:

cat /var/log/xen/console/hypervisor.log

Or you can copy it to another system and upload it here in the same way you did with journalctl.log.

51

this seems very wrong, I wonder why it appears twice…

If someone could try 4.2.1 installer, that would be nice, maybe it’s borked… there was no Release Candidate for it AFAIK…

1 Like
52

I will try installing older versions to understand where the error is

53

hypervisor.log (‏69.9 ‏ك.ب)

54

No errors there as well.
I guess it’s only possible to catch the error using serial port to debug it.

55

What do I do

56

Personally I don’t know what else to check, maybe someone else has some suggestions.
You can also open an issue on github to report this bug and attach the logs there:

1 Like
57

Thank you