[CLOSE/Unable to find cause]Random kernel panics without log's

Hubbleexplorer · 2023-08-07 11:28:27

seth wrote:

Keep PD masked for a week, if you don't get the kernel panic again, unmask it again and see whether that quickly returns the panic.
Has this btw. always happened on battery or also on AC?
Otherwise the brightness control might be the trigger, https://wiki.archlinux.org/title/Backli … interfaces

Ok i will keep it masked for now.
The crashes happend on battery and on AC, but i where a lot more common in AC

Hubbleexplorer · 2023-08-10 01:27:14

4 days without crash until now, it started to crash again

seth · 2023-08-10 05:51:22

So powerdevil is a red herring.
Did I ask about the weather at your location? Cold, hot, moist, dry?
Any drastic changes recently?

Hubbleexplorer · 2023-08-10 10:53:26

seth wrote:

So powerdevil is a red herring.
Did I ask about the weather at your location? Cold, hot, moist, dry?
Any drastic changes recently?

Well it's been very hot the last few days but the PC isn't overheating, at least the sensors don't show any overheating

seth · 2023-08-10 12:42:26

Ok, but it would have been stable during that hot period?
Would have been more like "it's been really hot and dry but yesterday it started to rain and now I'm living in a sauna"…

Hubbleexplorer · 2023-08-10 13:31:46

seth wrote:

Ok, but it would have been stable during that hot period?
Would have been more like "it's been really hot and dry but yesterday it started to rain and now I'm living in a sauna"…

It was stable while was really hot, now it's still hot but not as much, the humidity as not change is basically the same

seth · 2023-08-10 17:33:34

Do you have a fan heater?
(Have you ever opened or tampered w/ the system? Coud some element be under tension?)

Hubbleexplorer · 2023-08-10 17:56:04

So if i can't even begging to understand what is wrong with the pc, i will try to fix every error in the journactl and dmeg's, even if they appear before the crashes

 sudo journalctl -p 3 -xb                 

[sudo] password for hubble: 
Aug 10 18:50:48 hubble kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20230331/dswload2-162)
Aug 10 18:50:48 hubble kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230331/psobject-220)
Aug 10 18:50:49 hubble kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20230331/psargs-330)
Aug 10 18:50:49 hubble kernel: ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
Aug 10 18:50:49 hubble kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Aug 10 18:50:49 hubble kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Aug 10 18:50:49 hubble kernel: 
Aug 10 18:50:49 hubble kernel: amd_gpio AMDI0030:00: Invalid config param 0014
Aug 10 18:50:49 hubble kernel: amd_gpio AMDI0030:00: Invalid config param 0001
Aug 10 18:50:50 hubble kernel: Bluetooth: hci0: Reading supported features failed (-16)
Aug 10 18:50:50 hubble systemctl[663]: Failed to start nvidia-powerd.service: Unit nvidia-powerd.service is masked.
Aug 10 18:50:51 hubble kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Aug 10 18:50:51 hubble kernel: ucsi_ccg 6-0008: i2c_transfer failed -110
Aug 10 18:50:51 hubble kernel: ucsi_ccg 6-0008: ucsi_ccg_init failed - -110
Aug 10 18:50:55 hubble kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
Aug 10 18:51:00 hubble bluetoothd[611]: Failed to add UUID: Authentication Failed (0x05)
Aug 10 18:51:00 hubble kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 10 18:51:00 hubble kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 10 18:51:02 hubble kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 10 18:51:02 hubble kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 10 18:51:02 hubble bluetoothd[611]: Failed to add UUID: Authentication Failed (0x05)
Aug 10 18:51:04 hubble bluetoothd[611]: Failed to add UUID: Authentication Failed (0x05)
Aug 10 18:51:04 hubble kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 10 18:51:04 hubble kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 10 18:51:06 hubble bluetoothd[611]: Failed to add UUID: Authentication Failed (0x05)
Aug 10 18:51:06 hubble kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 10 18:51:06 hubble kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 10 18:51:07 hubble konsole[2249]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Aug 10 18:51:07 hubble konsole[2249]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Aug 10 18:51:08 hubble bluetoothd[611]: Failed to add UUID: Authentication Failed (0x05)
Aug 10 18:51:08 hubble kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 10 18:51:08 hubble kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 10 18:51:08 hubble kernel: Bluetooth: hci0: Resetting usb device.
Aug 10 18:51:09 hubble kernel: Bluetooth: hci0: Reading supported features failed (-16)
Aug 10 18:51:11 hubble sudo[2513]: pam_unix(sudo:auth): conversation failed
Aug 10 18:51:11 hubble sudo[2513]: pam_unix(sudo:auth): auth could not identify password for [hubble]
Arch_Linux_Hubble ~ $: sudo dmesg | grep -i error

[    0.332782] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20230331/dswload2-162)
[    0.332789] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230331/psobject-220)
[    0.437686] ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20230331/psargs-330)
[    0.437694] ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[    0.789171] RAS: Correctable Errors collector initialized.
[    9.371728] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    9.586253] Bluetooth: hci0: Error reading debug features
[   10.361270] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
[   10.361299] ucsi_ccg: probe of 6-0008 failed with error -110
[   14.530336] ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
[   28.207188] Bluetooth: hci0: Error reading debug features

this will be probably just a waste of time but nothing else to do but this

seth · 2023-08-10 18:14:55

Aug 10 18:50:48 hubble kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20230331/dswload2-162)
Aug 10 18:50:48 hubble kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230331/psobject-220)
Aug 10 18:50:49 hubble kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20230331/psargs-330)
Aug 10 18:50:49 hubble kernel: ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20230331/psparse-529)

ACPI implementation errors are common adn typically harmless, there's nothing but a UEFI update to fix that.

Aug 10 18:50:49 hubble kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Aug 10 18:50:49 hubble kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0

https://bbs.archlinux.org/viewtopic.php … 9#p2081649

Aug 10 18:50:49 hubble kernel: amd_gpio AMDI0030:00: Invalid config param 0014
Aug 10 18:50:49 hubble kernel: amd_gpio AMDI0030:00: Invalid config param 0001

https://gitlab.freedesktop.org/drm/amd/-/issues/2723
"harmless and noisy"

Aug 10 18:50:50 hubble systemctl[663]: Failed to start nvidia-powerd.service: Unit nvidia-powerd.service is masked.
Aug 10 18:50:51 hubble kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Aug 10 18:50:51 hubble kernel: ucsi_ccg 6-0008: i2c_transfer failed -110
Aug 10 18:50:51 hubble kernel: ucsi_ccg 6-0008: ucsi_ccg_init failed - -110
Aug 10 18:50:55 hubble kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed

nvidia specific, common, you can ignore that.
ucsi is for usb-c controllers

Aug 10 18:50:50 hubble kernel: Bluetooth: hci0: Reading supported features failed (-16)
Aug 10 18:51:00 hubble bluetoothd[611]: Failed to add UUID: Authentication Failed (0x05)
Aug 10 18:51:00 hubble kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 10 18:51:00 hubble kernel: Bluetooth: hci0: command 0x0c24 tx timeout

No idea out of context, obviously bluetooth related.

Aug 10 18:51:07 hubble konsole[2249]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Aug 10 18:51:07 hubble konsole[2249]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.

kf.xmlgui warns that konsole sets shortcuts the "wrong" way. ludicrous userspace process "bug"

Aug 10 18:51:11 hubble sudo[2513]: pam_unix(sudo:auth): conversation failed
Aug 10 18:51:11 hubble sudo[2513]: pam_unix(sudo:auth): auth could not identify password for [hubble]

No idea out of context, did you ctrl+c sudo?

this will be probably just a waste of time

Somewhat, but not much time, apparently.

For recap: you tried to disable the hybrid graphics and there's no parallel windows installation?

I was btw. kind half-serious about the fan heater, if you cannot reproduce the issue when warming up the case, that's obviously a very strong hint.
Any idea what else might have been different during the good run? Was the laptop in a different location (some EM interference at play, maybe?)

Hubbleexplorer · 2023-08-11 07:57:30

seth wrote:

Aug 10 18:50:48 hubble kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20230331/dswload2-162)
Aug 10 18:50:48 hubble kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230331/psobject-220)
Aug 10 18:50:49 hubble kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20230331/psargs-330)
Aug 10 18:50:49 hubble kernel: ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
ACPI implementation errors are common adn typically harmless, there's nothing but a UEFI update to fix that.
Aug 10 18:50:49 hubble kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Aug 10 18:50:49 hubble kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
https://bbs.archlinux.org/viewtopic.php … 9#p2081649
Aug 10 18:50:49 hubble kernel: amd_gpio AMDI0030:00: Invalid config param 0014
Aug 10 18:50:49 hubble kernel: amd_gpio AMDI0030:00: Invalid config param 0001
https://gitlab.freedesktop.org/drm/amd/-/issues/2723
"harmless and noisy"
Aug 10 18:50:50 hubble systemctl[663]: Failed to start nvidia-powerd.service: Unit nvidia-powerd.service is masked.
Aug 10 18:50:51 hubble kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Aug 10 18:50:51 hubble kernel: ucsi_ccg 6-0008: i2c_transfer failed -110
Aug 10 18:50:51 hubble kernel: ucsi_ccg 6-0008: ucsi_ccg_init failed - -110
Aug 10 18:50:55 hubble kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
nvidia specific, common, you can ignore that.
ucsi is for usb-c controllers
Aug 10 18:50:50 hubble kernel: Bluetooth: hci0: Reading supported features failed (-16)
Aug 10 18:51:00 hubble bluetoothd[611]: Failed to add UUID: Authentication Failed (0x05)
Aug 10 18:51:00 hubble kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 10 18:51:00 hubble kernel: Bluetooth: hci0: command 0x0c24 tx timeout
No idea out of context, obviously bluetooth related.
Aug 10 18:51:07 hubble konsole[2249]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Aug 10 18:51:07 hubble konsole[2249]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
kf.xmlgui warns that konsole sets shortcuts the "wrong" way. ludicrous userspace process "bug"
Aug 10 18:51:11 hubble sudo[2513]: pam_unix(sudo:auth): conversation failed
Aug 10 18:51:11 hubble sudo[2513]: pam_unix(sudo:auth): auth could not identify password for [hubble]
No idea out of context, did you ctrl+c sudo?
this will be probably just a waste of time
Somewhat, but not much time, apparently.
For recap: you tried to disable the hybrid graphics and there's no parallel windows installation?
I was btw. kind half-serious about the fan heater, if you cannot reproduce the issue when warming up the case, that's obviously a very strong hint.
Any idea what else might have been different during the good run? Was the laptop in a different location (some EM interference at play, maybe?)

Yes i tried to disable hybrid graphics and just run in integrated mode and no luck there, also windows is not install.
If there is some EM interference at play it will be very strange because it's crashes in very different places, only if the interference is inside the computer, and that will be hard to solve if not impossible.
Also yes i ctrl+C sudo
For a few days I won't be able to respond.

Last edited by Hubbleexplorer (2023-08-11 07:58:57)

Hubbleexplorer · 2023-08-15 15:58:44

For now i will be closing this thread, if this is a hardware problem i can't find it so i can't fix it.
If in the future i found a solution or some kind of fix i will post it here
Thank you all for your help

Axonyx · 2023-08-16 23:33:13

Fixed random reboots without logs (Legion 5 15ACH6H):

core: nomodeset nvidia-drm.modeset=1

seth · 2023-08-17 07:16:55

@Axonyx: those kernel parameters directly contradict each other, their actual impact heavily relies on the specific HW/driver config and one of them wouldn't "fix" anything for sure.

Arch Linux

#76 2023-08-07 11:28:27

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#77 2023-08-10 01:27:14

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#78 2023-08-10 05:51:22

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#79 2023-08-10 10:53:26

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#80 2023-08-10 12:42:26

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#81 2023-08-10 13:31:46

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#82 2023-08-10 17:33:34

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#83 2023-08-10 17:56:04

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#84 2023-08-10 18:14:55

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#85 2023-08-11 07:57:30

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#86 2023-08-15 15:58:44

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#87 2023-08-16 23:33:13

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

#88 2023-08-17 07:16:55

Re: [CLOSE/Unable to find cause]Random kernel panics without log's

Board footer