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

Hubbleexplorer · 2023-06-30 11:35:06

Hello,so my Asus a15 FA506IU_FA506IU with the latest kernel (6.3.9-arch1-1) from a few weeks ago is randomly crashing without warning, the caps lock starts blinking and after rebooting the logs are empty
The first crash in the link is at "11:54:08" and the other at "12:09:42"

Jun 30 11:54:05 hubble pacman[5066]: Running 'pacman --sync -- extra/ethtool extra/pyqt-builder extra/sip extra/python-pyqt5-sip extra/python-pyqt5 extra/qwt'
Jun 30 11:54:07 hubble pacman[5066]: transaction started
Jun 30 11:54:07 hubble pacman[5066]: installed ethtool (1:6.3-1)
Jun 30 11:54:07 hubble pacman[5066]: installed pyqt-builder (1.15.1-1)
Jun 30 11:54:07 hubble pacman[5066]: installed sip (6.7.9-2)
Jun 30 11:54:07 hubble pacman[5066]: installed python-pyqt5-sip (12.12.1-2)
Jun 30 11:54:07 hubble pacman[5066]: installed python-pyqt5 (5.15.9-2)
Jun 30 11:54:08 hubble pacman[5066]: installed qwt (6.2.0-1)
Jun 30 11:54:08 hubble pacman[5066]: transaction completed
Jun 30 11:54:08 hubble pacman[5066]: running '30-systemd-update.hook'...
Jun 30 11:54:08 hubble sudo[5065]: pam_unix(sudo:session): session closed for user root
Jun 30 11:54:08 hubble dbus-daemon[721]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.148' (uid=0 pid=5141 comm="sudo pacman --database --asdeps -- ethtool pyqt-bu")
Jun 30 11:54:08 hubble dbus-daemon[721]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jun 30 11:54:08 hubble sudo[5141]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Jun 30 11:54:08 hubble sudo[5141]:   hubble : TTY=pts/1 ; PWD=/home/hubble ; USER=root ; COMMAND=/usr/bin/pacman --database --asdeps -- ethtool pyqt-builder sip python-pyqt5-sip python-pyqt5 qwt
Jun 30 11:54:08 hubble sudo[5141]: pam_unix(sudo:session): session opened for user root(uid=0) by hubble(uid=1000)
Jun 30 11:54:08 hubble pacman[5142]: Running 'pacman --database --asdeps -- ethtool pyqt-builder sip python-pyqt5-sip python-pyqt5 qwt'
Jun 30 11:54:08 hubble sudo[5141]: pam_unix(sudo:session): session closed for user root
-- Boot 91b004a6060a4dbaa716c36d5e17ed92 --
Jun 30 11:54:51 hubble kernel: Linux version 6.3.9-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Wed, 21 Jun 2023 20:46:20 +0000
Jun 30 11:54:51 hubble kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=449b6366-7261-4817-8a7a-b83c38c3e71d rw loglevel=3 quiet splash modprobe.blacklist=nouveau resume=/dev/nvme0n1p2
Jun 30 11:54:51 hubble kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 30 11:54:51 hubble kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 30 11:54:51 hubble kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 30 11:54:51 hubble kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 30 11:54:51 hubble kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.

The other crash

Jun 30 12:09:02 hubble rtkit-daemon[1107]: Supervising 7 threads of 5 processes of 1 users.
Jun 30 12:09:02 hubble rtkit-daemon[1107]: Supervising 7 threads of 5 processes of 1 users.
Jun 30 12:09:32 hubble kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=f8:94:c2:14:11:17:7c:9a:54:10:4f:14:08:00 SRC=198.252.206.25 DST=192.168.0.21 LEN=113 TOS=0x08 PREC=0x60 TTL=53 ID=25340 DF PROTO=TCP SPT=443 DPT=45012 WINDOW=62 RES=0x00 ACK PSH URGP=0 
Jun 30 12:09:42 hubble rtkit-daemon[1107]: Supervising 7 threads of 5 processes of 1 users.
Jun 30 12:09:42 hubble rtkit-daemon[1107]: Supervising 7 threads of 5 processes of 1 users.
-- Boot b634e6e95ac7407db3d16aa4609d632f --
Jun 30 12:10:13 hubble kernel: Linux version 6.3.9-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Wed, 21 Jun 2023 20:46:20 +0000
Jun 30 12:10:13 hubble kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=449b6366-7261-4817-8a7a-b83c38c3e71d rw loglevel=3 quiet splash modprobe.blacklist=nouveau resume=/dev/nvme0n1p2
Jun 30 12:10:13 hubble kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'

has i was writing this post it crash yet again, also without any information

Jun 30 12:27:17 hubble kate[5076]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Jun 30 12:27:17 hubble kate[5076]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Jun 30 12:27:17 hubble kate[5076]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Jun 30 12:27:17 hubble kate[5076]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Jun 30 12:27:17 hubble kate[5076]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Jun 30 12:27:28 hubble touchegg[749]: libinput error: event13 - ELAN1203:00 04F3:307A Touchpad: kernel bug: Touch >
Jun 30 12:27:28 hubble touchegg[749]: See https://wayland.freedesktop.org/libinput/doc/1.23.0/touchpad-jumping-cur>
Jun 30 12:27:30 hubble wpa_supplicant[837]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-62 noise=9999 txrate=>
Jun 30 12:27:50 hubble rtkit-daemon[1124]: Supervising 7 threads of 5 processes of 1 users.
Jun 30 12:27:50 hubble rtkit-daemon[1124]: Supervising 7 threads of 5 processes of 1 users.

I already run some hardware check's like memtest86+ because i was thinking of faulty ram but after 5 pass without errors stop it.
Help is need because I'm going insane with this.
Thank you for your time

Last edited by Hubbleexplorer (2023-08-15 16:03:14)

GeneArch · 2023-06-30 12:08:55

Very frustrating when no information.

Shooting in the dark but couple thoughts, since the crash is so hard and kernel is not reporting anything, wonder if could be gpu related.

- I notice you blacklisted nouveau. Are you using nvidia out-of-tree drivers or are you ignoring the nvidia GPU completely and using onboard GPU like intel or radeon?
If using nvidia, if were me, I'd try removing the nvidia driver and see if it continues to happen. I would also double check whatever nvidia drivers are compatible with the kernel you're using.

- Also seems you may be using wayland, so just to confirm that you don't have any old xf86-xxx drivers by chance.

- I see you have hibernation turned on (kernel resume=/dev/xxx) - was there any chance the machine hibernated and resumed (or crashed on resume) any time before the crash? There have been some issues with resume, which I believe are fixed in 6.4 (now in testing). May be related. Might be worthwhile turning off hibernation and if you like, just using suspend (sleep) instead.

Last edited by GeneArch (2023-06-30 12:09:55)

Hubbleexplorer · 2023-06-30 12:33:33

GeneArch wrote:

Very frustrating when no information.
Shooting in the dark but couple thoughts, since the crash is so hard and kernel is not reporting anything, wonder if could be gpu related.
- I notice you blacklisted nouveau. Are you using nvidia out-of-tree drivers or are you ignoring the nvidia GPU completely and using onboard GPU like intel or radeon?
If using nvidia, if were me, I'd try removing the nvidia driver and see if it continues to happen. I would also double check whatever nvidia drivers are compatible with the kernel you're using.
- Also seems you may be using wayland, so just to confirm that you don't have any old xf86-xxx drivers by chance.
- I see you have hibernation turned on (kernel resume=/dev/xxx) - was there any chance the machine hibernated and resumed (or crashed on resume) any time before the crash? There have been some issues with resume, which I believe are fixed in 6.4 (now in testing). May be related. Might be worthwhile turning off hibernation and if you like, just using suspend (sleep) instead.

The driver nvidia driver I'm using the proprietary nvidia driver from the extra repository https://archlinux.org/packages/extra/x86_64/nvidia/, i can try to remove and just leave the radeon graphics but if's that others users should have reported already
I'm not using wayland but were are the xf86 drivers

Arch_Linux_Hubble ~ $: pacman -Q | grep xf86
lib32-libxxf86vm 1.1.5-1
libxxf86vm 1.1.5-1
xf86-input-libinput 1.3.0-1
xf86-video-amdgpu 23.0.0-1
xf86-video-vesa 2.6.0-1

In term of hibernation, no the computer hasn't hibernate in 2 week's is always been shutdown.

Last edited by Hubbleexplorer (2023-06-30 12:35:28)

Hubbleexplorer · 2023-06-30 13:11:37

Hubbleexplorer wrote:

The driver nvidia driver I'm using the proprietary nvidia driver from the extra repository https://archlinux.org/packages/extra/x86_64/nvidia/, i can try to remove and just leave the radeon graphics but if's that others users should have reported already
I'm not using wayland but were are the xf86 drivers
Arch_Linux_Hubble ~ $: pacman -Q | grep xf86
lib32-libxxf86vm 1.1.5-1
libxxf86vm 1.1.5-1
xf86-input-libinput 1.3.0-1
xf86-video-amdgpu 23.0.0-1
xf86-video-vesa 2.6.0-1
In term of hibernation, no the computer hasn't hibernate in 2 week's is always been shutdown.

Quick update it crash again with the nvidia driver uninstalled so is not that one.
Now i will try to remove xf86-video-amdgpu 23.0.0-1 and xf86-video-vesa 2.6.0-1.

Last edited by Hubbleexplorer (2023-06-30 13:14:29)

GeneArch · 2023-06-30 19:26:28

Hubbleexplorer wrote:

Quick update it crash again with the nvidia driver uninstalled so is not that one.
Now i will try to remove xf86-video-amdgpu 23.0.0-1 and xf86-video-vesa 2.6.0-1.

Let us know if it helps any.

Hubbleexplorer · 2023-07-01 17:22:04

New update
After uninstalling 86-video-amdgpu 23.0.0-1 and xf86-video-vesa 2.6.0-1 no crashes happen in a day. I will maintain this topic open more 2-3 day to be sure is solved after that i will be considering it solved

GeneArch · 2023-07-01 18:06:19

Hey excellent news - fingers crossed it stays that way - I got a coffee says it does

Hubbleexplorer · 2023-07-02 00:40:37

Sad news after 13 hours of not crashing it crash again without warning

Jul 02 01:38:05 hubble kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:7c:9a:54:10:4f:14:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 
Jul 02 01:38:05 hubble kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:fb:1a:5b:da:20:b6:79:08:00 SRC=192.168.0.13 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=4666 PROTO=2 
Jul 02 01:38:06 hubble kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:7f:ff:fa:7c:9a:54:10:4f:16:08:00 SRC=192.168.0.10 DST=239.255.255.250 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
Jul 02 01:38:21 hubble wpa_supplicant[836]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-76 noise=9999 txrate=866700
Jul 02 01:38:23 hubble wpa_supplicant[836]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-76 noise=9999 txrate=866700
Jul 02 01:38:25 hubble plasmashell[41778]: [+] cef_urlrequest_create:         https://spclient.wg.spotify.com/played-state/v1/items?fromTimestamp=1675128759133
Jul 02 01:38:25 hubble plasmashell[41778]: [+] cef_urlrequest_create:         https://i.scdn.co/image/ab67616d0000b27340500f6856178be3539410b2
Jul 02 01:38:25 hubble plasmashell[41778]: [+] cef_urlrequest_create:         https://spclient.wg.spotify.com/extended-metadata/v0/extended-metadata

so for now i still dont know what is causing this, maybe some one could suggest hardware tests to be sure if not the fault of the hardware

edit

It crash again but this time the screen went dark and the led that shows the kernel panic didn't light up or blink

Jul 02 02:31:33 hubble plasmashell[2760]: [+] cef_urlrequest_create:         https://spclient.wg.spotify.com/played-state/v1/items?fromTimestamp=1675128759133
Jul 02 02:32:19 hubble touchegg[741]: libinput error: event13 - ELAN1203:00 04F3:307A Touchpad: kernel bug: Touch jump detected and discarded.
Jul 02 02:32:19 hubble touchegg[741]: See https://wayland.freedesktop.org/libinput/doc/1.23.0/touchpad-jumping-cursors.html for details
Jul 02 02:32:41 hubble kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:7c:9a:54:10:4f:14:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 
Jul 02 02:32:48 hubble wpa_supplicant[822]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-74 noise=9999 txrate=866700
Jul 02 02:32:51 hubble wpa_supplicant[822]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise=9999 txrate=866700
Jul 02 02:32:53 hubble wpa_supplicant[822]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=866700

Last edited by Hubbleexplorer (2023-07-02 01:36:50)

Berbigou · 2023-07-02 14:24:10

Hello,
my ASUS VivoBook X412D with 6.3.9-arch1-1 has random unlogged crashes too, with or without CAPS LED blinking.

I'm not very used to this kind of investigation, I can give every log needed, but please give me the commands to put.

Many thanks to those reading.

Hubbleexplorer · 2023-07-02 14:41:25

Berbigou wrote:

Hello,
my ASUS VivoBook X412D with 6.3.9-arch1-1 has random unlogged crashes too, with or without CAPS LED blinking.
I'm not very used to this kind of investigation, I can give every log needed, but please give me the commands to put.
Many thanks to those reading.

Humm interesting, could you give me an

sudo journalctl --boot=-1

the -1 is the last boot alter this to match the boot that where crash corrected, just give the last few lines

Berbigou · 2023-07-02 15:39:45

Thank you for replying:
sudo journalctl --boot=-1 (precedent boot was indeed a failure)

juil. 02 16:05:01 Ber-Port-L systemd-modules-load[187]: Inserted module 'vboxnetadp'
juil. 02 16:05:01 Ber-Port-L kernel: VBoxNetAdp: Successfully started.
juil. 02 16:05:01 Ber-Port-L systemd-modules-load[187]: Inserted module 'vboxnetflt'
juil. 02 16:05:01 Ber-Port-L kernel: VBoxNetFlt: Successfully started.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
juil. 02 16:05:01 Ber-Port-L systemd[1]: modprobe@drm.service: Deactivated successfully.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Finished Load Kernel Module drm.
juil. 02 16:05:01 Ber-Port-L systemd[1]: modprobe@fuse.service: Deactivated successfully.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Finished Load Kernel Module fuse.
juil. 02 16:05:01 Ber-Port-L systemd[1]: modprobe@loop.service: Deactivated successfully.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Finished Load Kernel Module loop.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Finished Load Kernel Modules.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Finished Remount Root and Kernel File Systems.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Finished Coldplug All udev Devices.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Mounting FUSE Control File System...
juil. 02 16:05:01 Ber-Port-L systemd[1]: Mounting Kernel Configuration File System...
juil. 02 16:05:01 Ber-Port-L systemd[1]: First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
juil. 02 16:05:01 Ber-Port-L systemd[1]: Rebuild Hardware Database was skipped because no trigger condition checks were met.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Starting Flush Journal to Persistent Storage...
juil. 02 16:05:01 Ber-Port-L systemd[1]: Starting Load/Save OS Random Seed...
juil. 02 16:05:01 Ber-Port-L systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met.
juil. 02 16:05:01 Ber-Port-L systemd[1]: Starting Apply Kernel Variables...
juil. 02 16:05:01 Ber-Port-L systemd-journald[186]: Time spent on flushing to /var/log/journal/08c8f13f92644e019ed7d2a4aeb35eb1 is 47.102ms for 828 entries.

seth · 2023-07-02 16:04:34

Please post your complete system journal for the boot:

sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io

Try to reboot w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

The usual suspects:
--------------------------
https://wiki.archlinux.org/title/Solid_ … leshooting (APST & IOMMU, the tail of your journal looks like a system update, so that's interesting…)
In case this is a ryzen system, https://wiki.archlinux.org/title/Ryzen#Troubleshooting (processor.max_cstate=1 and the curve optimizer)

Hubbleexplorer · 2023-07-02 16:17:44

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io
Try to reboot w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
The usual suspects:
--------------------------
https://wiki.archlinux.org/title/Solid_ … leshooting (APST & IOMMU, the tail of your journal looks like a system update, so that's interesting…)
In case this is a ryzen system, https://wiki.archlinux.org/title/Ryzen#Troubleshooting (processor.max_cstate=1 and the curve optimizer)

ok here is the last crash boot complete, i will post again when the pc crashes with the SysRq keys.
http://ix.io/4zBr

Last edited by Hubbleexplorer (2023-07-02 16:17:57)

Berbigou · 2023-07-02 16:43:31

Here is mine :
http://ix.io/4zBu

seth · 2023-07-02 16:55:04

@Berbigou, also see https://bbs.archlinux.org/viewtopic.php?id=286843
@Hubbleexplorer,

Hello,so my Asus a15 FA506IU_FA506IU with the latest kernel (6.3.9-arch1-1) from a few weeks ago

ie. this is a recent regression?
=> https://bbs.archlinux.org/viewtopic.php?id=286536 try to downgrade the nvidia driver to 530xx (use nvidia-dkms in order to keep the current kernel, otherwise youÄ'd have to downgrade that to the version matching the prebuilt nvidia module)

Hubbleexplorer · 2023-07-03 13:53:42

seth wrote:

@Berbigou, also see https://bbs.archlinux.org/viewtopic.php?id=286843
@Hubbleexplorer,
Hello,so my Asus a15 FA506IU_FA506IU with the latest kernel (6.3.9-arch1-1) from a few weeks ago
ie. this is a recent regression?
=> https://bbs.archlinux.org/viewtopic.php?id=286536 try to downgrade the nvidia driver to 530xx (use nvidia-dkms in order to keep the current kernel, otherwise youÄ'd have to downgrade that to the version matching the prebuilt nvidia module)

Hubbleexplorer wrote:

Quick update it crash again with the nvidia driver uninstalled so is not that one.

it shouldn't be the nvidia driver because it crash without having it installed

Berbigou · 2023-07-03 23:44:36

seth wrote:

@Berbigou, also see https://bbs.archlinux.org/viewtopic.php?id=286843

I don't have Nvidia nor Intel GPU (AMD only), I didn't touch ast, and I don't use suspend..

But kernel 6.4.1 doesn't seem to freeze, I give up 6.3.9

Thanks a lot @Seth

Hubbleexplorer · 2023-07-10 12:51:02

Still with the same problem even with 6.4 kernel.

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io
Try to reboot w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

Can't reboot with SysRq, after crash.
Also new problem sometimes crashes when in startup, no logs because journalctl didnt even register the boot

seth · 2023-07-10 14:28:11

https://wiki.archlinux.org/title/Kdump
https://wiki.archlinux.org/title/Genera … l_messages

Does it consistently crash during the boot?
What are the symptoms? Halt? Instant reboot?
Can you still boot the multi-user.target (2nd link below)? Along "nomodeset"?

Hubbleexplorer · 2023-07-10 14:56:35

seth wrote:

https://wiki.archlinux.org/title/Kdump
https://wiki.archlinux.org/title/Genera … l_messages
Does it consistently crash during the boot?
What are the symptoms? Halt? Instant reboot?

No the crash during boot is random, and it just halt's the system.

seth wrote:

Can you still boot the multi-user.target (2nd link below)? Along "nomodeset"?

i couldn't see where the boot stopped because of plymouth, i disable it now and i will wait for when it crashes again.
I will try to put kdump working if i can figure it out how it works, also how do i reboot the system in a way that kdump works, because SysRq doesn't work after the crash?

Update

So i have configure kdump but /proc/vmcore isnt created on boot dont know why and cant find why

Arch_Linux_Hubble ~ $: zgrep -E 'CONFIG_DEBUG_INFO=|CONFIG_CRASH_DUMP=|CONFIG_PROC_VMCORE=' /proc/config.gz
CONFIG_CRASH_DUMP=y
CONFIG_PROC_VMCORE=y
CONFIG_DEBUG_INFO=y
Arch_Linux_Hubble ~ $: cat /sys/kernel/kexec_crash_loaded

1

is this normal behavior or not?

Last edited by Hubbleexplorer (2023-07-10 17:00:19)

Hubbleexplorer · 2023-07-13 17:27:13

after some day i have finally caught something interesting when the pc crashes

Jul 13 16:27:27 hubble kernel: note: gfx_low[254] exited with irqs disabled
Jul 13 16:27:27 hubble kernel: note: gfx_low[254] exited with preempt_count 2
Jul 13 16:27:27 hubble kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
Jul 13 16:27:27 hubble kernel: Modules linked in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nft_masq nft_chain_nat nf_tables nfnetlink nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_>
Jul 13 16:27:27 hubble kernel:  polyval_generic asus_nb_wmi snd_hwdep uvc nvidia_uvm(POE) gf128mul videobuf2_memops bluetooth videobuf2_v4l2 asus_wmi ghash_clmulni_intel ucsi_ccg iwlwifi sha512_ssse3 r8169 videodev sp5100_tco ledtrig_a>
Jul 13 16:27:27 hubble kernel: CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Tainted: P      D    OE      6.4.2-arch1-1-kdump #1 989cf3c56bded11ab89eb8592e28e5c14d7d53c4
Jul 13 16:27:27 hubble kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506IU_FA506IU/FA506IU, BIOS FA506IU.319 04/26/2022
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x223/0x2e0

the full error journalctl its here http://ix.io/4AvN
It seems to me that something is going really wrong with amdgpu and the other thing very wrong with my wifi adapter

Last edited by Hubbleexplorer (2023-07-13 17:41:38)

seth · 2023-07-13 19:57:59

Jul 13 12:42:03 hubble kernel: smpboot: CPU0: AMD Ryzen 9 4900H with Radeon Graphics (family: 0x17, model: 0x60, stepping: 0x1)
Jul 13 16:27:27 hubble kernel: RIP: 0010:__switch_to+0x130/0x400
Jul 13 16:27:27 hubble kernel: RIP: 0010:__switch_to+0x130/0x400
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x223/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x440
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x2a5/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0000:0x0
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0000:0x0
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x223/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x440

seth wrote:

In case this is a ryzen system, https://wiki.archlinux.org/title/Ryzen#Troubleshooting (processor.max_cstate=1 and the curve optimizer)

Hubbleexplorer · 2023-07-13 20:40:07

seth wrote:

Jul 13 12:42:03 hubble kernel: smpboot: CPU0: AMD Ryzen 9 4900H with Radeon Graphics (family: 0x17, model: 0x60, stepping: 0x1)
Jul 13 16:27:27 hubble kernel: RIP: 0010:__switch_to+0x130/0x400
Jul 13 16:27:27 hubble kernel: RIP: 0010:__switch_to+0x130/0x400
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x223/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x440
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x2a5/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0000:0x0
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0000:0x0
Jul 13 16:27:27 hubble kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x223/0x2e0
Jul 13 16:27:27 hubble kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x440

seth wrote:

In case this is a ryzen system, https://wiki.archlinux.org/title/Ryzen#Troubleshooting (processor.max_cstate=1 and the curve optimizer)

should this be just appending in ryzen 5000, not 4000, weird, i apply the fix any way to see if it works

Last edited by Hubbleexplorer (2023-07-13 20:41:50)

seth · 2023-07-13 20:45:25

Hubbleexplorer wrote:

should this be just appending in ryzen 5000, not 4000, weird, i apply the fix any way to see if it works

The series limitation (in the wiki) applies only to the undervoltage, pretty much all of them seem to have trouble w/ higher c-states and I'd not ignore the voltage situation either.
You do have https://archlinux.org/packages/core/any/amd-ucode/ ?

Chinaboy5216 · 2023-07-14 06:14:45

Seeing this happening also for some time now (blinking caps lock key from time to time when booting up), I just do hardware reset for now which seems to solve the issue.

As test i installed EndeavourOS and run it for a couple of days, same issue happened (I guess it's something or kernel related or arch base related).
A couple of days ago i did a fresh install of Arch again and had the issue again this morning. Installation done with the archinstall script (updated before running the script)

Next time it happens I'll try to get the boot log also.

amd-ucode is installed here, issue happens on the linux kernel, linux-zen kernel, linux-lts kernel

Switching from Hybrid GPU to Nvidia with the use of optimus-qt and/or envycontrol also leads to frozen system during boot (don't know however is this is related to the blinking caps lock issue, last message during boot is: usci_acpi USBC000:00: error -ETIMEDOUT: PPM init failed)

My system Tuf A15 FA506QM Ryzen 5800H Nvidia RTX 3060 Mobile / MAX - Q (bought this one in China at the time)
OS Arch with KDE desktop
Only modifications done to the system has been swap the Mediatek wifi card with an intel AX210 and add an extra nvme drive to the system (shouldn't be related to this issue but want to mention it anyway)

Arch Linux

#1 2023-06-30 11:35:06

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

#2 2023-06-30 12:08:55

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

#3 2023-06-30 12:33:33

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

#4 2023-06-30 13:11:37

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

#5 2023-06-30 19:26:28

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

#6 2023-07-01 17:22:04

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

#7 2023-07-01 18:06:19

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

#8 2023-07-02 00:40:37

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

#9 2023-07-02 14:24:10

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

#10 2023-07-02 14:41:25

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

#11 2023-07-02 15:39:45

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

#12 2023-07-02 16:04:34

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

#13 2023-07-02 16:17:44

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

#14 2023-07-02 16:43:31

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

#15 2023-07-02 16:55:04

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

#16 2023-07-03 13:53:42

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

#17 2023-07-03 23:44:36

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

#18 2023-07-10 12:51:02

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

#19 2023-07-10 14:28:11

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

#20 2023-07-10 14:56:35

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

#21 2023-07-13 17:27:13

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

#22 2023-07-13 19:57:59

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

#23 2023-07-13 20:40:07

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

#24 2023-07-13 20:45:25

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

#25 2023-07-14 06:14:45

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

Board footer