…not linked to your current issue but only one of them should be running.
Creating a bootable usb you mean? I can check that. I will try the KDE version first and if that doesn’t work, I will check the XFCE version.
I wasn’t aware of that, which one is recommended and how can I turn it on/off?
–edit
I saw this forum thread: PulseAudio vs. PipeWire - Which To Use?, will read it in the morning
I have checked with a bootable usb (altest iso download), that works… with linux515. It starts and loads the desktop and I can browse with firefox.
I have a similar issue - what I see in common is a ryzen CPU ( 5800x ) in my case, and the RX6800xt, 5.15 received a lot of amdgpu work as well. In my case sometimes i make it to the desktop but all of a sudden tasks start to timeout and the system becomes unresponsive. One thing to note, when it’s in that state, even lspci hangs. Reverting to 5.14 fixed the problem for now.
I saw this post, [Stable Update] 2021-12-10 - Kernels, Systemd, LibreOffice, Plasma, Browser, Thunderbird - #180 by Zinnaca, and got me thinking what do I have in my fstab file. I have network shares to my nas in there for mounting at boot, e.g.: //192.165.173.100/Documents /mnt/nas/documents cifs uid=1000,gid=1000,defaults,workgroup=WORKGROUP,credentials=/home/user/.smbnasuser,_netdev 0 0
When I turn all those network share off by commenting them, I can access linux515 like nothing has happened… but another problem, on shutting down, it takes over 10 min. before the below image disappears (screen goes in sleeping mode), but my machine stays on…
@philm
Is there something to make it work with shares and what about the shutting down?
Switching back to linux514 for now. Then at least I can access my network shares on boot and it shutdowns within seconds.
Interesting finding, I do have a network mount too although it’s on nfs.
Then wait until kernel 5.15 reaches version > 5.15.10.
And you can create a boot stick with ventoy. It is easy to use.
I have the same issue since launch of the 5.15 kernel. I’ve been sticking with 5.14. However, after updating yesterday, 5.14 caught this bug as well. Something between 5.14.18 and 5.14.21 broke my system and I had to roll back my kernel to make it usable again.
In my case, I can get to the login screen on 5.15/5.14.21 and everything looks OK. But, as soon as I log in via the GUI, it takes about 20 seconds to load and then when it finally does, I have no WiFi (but bluetooth shows up) and processes start to slowly hang. I can’t even reboot the machine without having to Alt+Printscreen+S,U,B. And, if I don’t fully power off my power supply for a few seconds, I will not be able to unlock my encryption at reboot.
I attempted to use dmesg to read the kernel log, but that hangs as well, so I have no way of reading kernel messages. The log doesn’t even seem to be saved by journalctl, since I can’t even access the log by chrooting into my install from a live environment.
Overall, this bug is very annoying.
I had read the AMD SME was disabled by default due to kernel issues, and my command line has mem_encrypt=1, but even after removing that option (and disabling it in the UEFI) there is no change.
I’m not sure if this is pertinent, but my board is a Gigabyte X570 AORUS Master with F35 BIOS.
You mean for both my problems, network shares on boot and shutting down my system?
I have created it with the terminal to test if my system would run the bootable usb with linux515, I will look into ventoy!
I have the same issues, but I don’t have mem_ecrypt=on or mem_encrypt=1
I was going to try to see which exact kernel revision (and then patch) caused the issue, but I can’t get 5.14.19 to boot after building it. Probably something I’m doing wrong. But then again, after seeing how many patches went into 5.14.19, I’m kind of glad I’m not putting that much time into it – I actually want to use my computer today. I guess I’ll just lock my kernel 
I hoped I could go back to linux510 when 514 will be removed, but I can’t even do that atm… Because when I boot with linux510, it change my current resolution and in the end my monitors don’t get any input and goes in standby and I don’t get it on anymore.
But I think that’s more a GPU related issue then the network shares. I need to test that more, but don’t have much time…
Disabling distro patches on 5.14.21 seems to work, so it has to do with one of the distro patches, it seems like. Now, I’m trying to isolate the issue to figure out which ones.
Nope, that wasn’t the issue. I’m stumped at this point. I’m running 5.14.21 now without any issues now after self-building the kernel. My best guess is that the build system messed something up with the distributed binary? Guess I’ll try self-building 5.15 and see if I continue to have issues.
Now that I got 5.14 working, I tried self-building 5.15.8 but no dice – same issue.
The new Pop_OS! 21.10 LiveCD with kernel 5.15.5 boots up and doesn’t give me any weird issues, which makes be believe that this is Manjaro-specific.
So, I rolled the Manjaro kernel all the way back to 5.15.0 which actually works! I just had to bump it one more version to 5.15.1 for it to break again. So, seems like the issue is between 5.15.0 and 5.15.1. On Manjaro’s side, the only real change was to the futex patch – I wonder if that might be the culprit? Building now without that patch…
No dice on the futex patch, but I did recover these kernel logs. I had to unlock my root account since even sudo hangs, which is why I was unable to even see the logs before. These messages are for 5.16, but 5.15.1 had the same errors.
Excerpt of dmesg:
[ 245.689021] INFO: task kworker/7:1:282 blocked for more than 122 seconds.
[ 245.689027] Not tainted 5.16.0-1-MANJARO #1
[ 245.689029] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689030] task:kworker/7:1 state:D stack: 0 pid: 282 ppid: 2 flags:0x00004000
[ 245.689035] Workqueue: pm pm_runtime_work
[ 245.689041] Call Trace:
[ 245.689042] <TASK>
[ 245.689045] __schedule+0x307/0x10e0
[ 245.689052] ? update_load_avg+0x7e/0x600
[ 245.689056] schedule+0x4b/0xd0
[ 245.689058] schedule_preempt_disabled+0x11/0x20
[ 245.689061] __mutex_lock.constprop.0+0x256/0x450
[ 245.689066] rtl8169_runtime_suspend+0x19/0x70 [r8169 96a8125af3e9c3adc7f649de37220f6dfc45dc79]
[ 245.689073] pci_pm_runtime_suspend+0x5e/0x180
[ 245.689076] ? pci_dev_put+0x20/0x20
[ 245.689079] __rpm_callback+0x44/0x120
[ 245.689083] rpm_callback+0x35/0x70
[ 245.689085] ? pci_dev_put+0x20/0x20
[ 245.689087] rpm_suspend+0x177/0x750
[ 245.689090] pm_runtime_work+0x53/0xa0
[ 245.689092] process_one_work+0x1e8/0x3c0
[ 245.689095] worker_thread+0x50/0x3c0
[ 245.689096] ? rescuer_thread+0x390/0x390
[ 245.689098] kthread+0x15c/0x180
[ 245.689101] ? set_kthread_struct+0x50/0x50
[ 245.689103] ret_from_fork+0x22/0x30
[ 245.689108] </TASK>
[ 245.689113] INFO: task kworker/u64:4:317 blocked for more than 122 seconds.
[ 245.689115] Not tainted 5.16.0-1-MANJARO #1
[ 245.689116] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689117] task:kworker/u64:4 state:D stack: 0 pid: 317 ppid: 2 flags:0x00004000
[ 245.689120] Workqueue: netns cleanup_net
[ 245.689124] Call Trace:
[ 245.689125] <TASK>
[ 245.689126] __schedule+0x307/0x10e0
[ 245.689128] ? schedule+0x4b/0xd0
[ 245.689131] ? wq_worker_running+0xa/0x40
[ 245.689134] schedule+0x4b/0xd0
[ 245.689136] schedule_preempt_disabled+0x11/0x20
[ 245.689138] __mutex_lock.constprop.0+0x256/0x450
[ 245.689142] cfg80211_pernet_exit+0xf/0x70 [cfg80211 ae7d22c497a326c6721c15b3b45ed901d66eca80]
[ 245.689170] ops_exit_list+0x33/0x70
[ 245.689173] cleanup_net+0x213/0x3c0
[ 245.689175] process_one_work+0x1e8/0x3c0
[ 245.689178] worker_thread+0x50/0x3c0
[ 245.689179] ? rescuer_thread+0x390/0x390
[ 245.689181] kthread+0x15c/0x180
[ 245.689183] ? set_kthread_struct+0x50/0x50
[ 245.689186] ret_from_fork+0x22/0x30
[ 245.689189] </TASK>
[ 245.689192] INFO: task kworker/u64:13:338 blocked for more than 122 seconds.
[ 245.689193] Not tainted 5.16.0-1-MANJARO #1
[ 245.689194] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689194] task:kworker/u64:13 state:D stack: 0 pid: 338 ppid: 2 flags:0x00004000
[ 245.689198] Workqueue: events_power_efficient reg_check_chans_work [cfg80211]
[ 245.689224] Call Trace:
[ 245.689225] <TASK>
[ 245.689226] __schedule+0x307/0x10e0
[ 245.689229] ? update_load_avg+0x7e/0x600
[ 245.689231] schedule+0x4b/0xd0
[ 245.689233] schedule_preempt_disabled+0x11/0x20
[ 245.689236] __mutex_lock.constprop.0+0x256/0x450
[ 245.689238] ? __switch_to_asm+0x42/0x70
[ 245.689241] reg_check_chans_work+0x2d/0x3c0 [cfg80211 ae7d22c497a326c6721c15b3b45ed901d66eca80]
[ 245.689268] process_one_work+0x1e8/0x3c0
[ 245.689270] worker_thread+0x50/0x3c0
[ 245.689271] ? rescuer_thread+0x390/0x390
[ 245.689273] kthread+0x15c/0x180
[ 245.689275] ? set_kthread_struct+0x50/0x50
[ 245.689278] ret_from_fork+0x22/0x30
[ 245.689281] </TASK>
[ 245.689328] INFO: task NetworkManager:2292 blocked for more than 122 seconds.
[ 245.689330] Not tainted 5.16.0-1-MANJARO #1
[ 245.689330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689331] task:NetworkManager state:D stack: 0 pid: 2292 ppid: 1 flags:0x00000000
[ 245.689333] Call Trace:
[ 245.689334] <TASK>
[ 245.689335] __schedule+0x307/0x10e0
[ 245.689337] ? ip6_mtu+0x42/0x80
[ 245.689341] schedule+0x4b/0xd0
[ 245.689343] schedule_preempt_disabled+0x11/0x20
[ 245.689345] __mutex_lock.constprop.0+0x256/0x450
[ 245.689347] ? security_capable+0x36/0x60
[ 245.689350] rtnetlink_rcv_msg+0x10b/0x3a0
[ 245.689354] ? rtnl_calcit.isra.0+0x160/0x160
[ 245.689357] netlink_rcv_skb+0x5b/0x110
[ 245.689360] netlink_unicast+0x246/0x360
[ 245.689362] netlink_sendmsg+0x24f/0x4b0
[ 245.689364] sock_sendmsg+0x64/0x70
[ 245.689368] ____sys_sendmsg+0x266/0x2a0
[ 245.689371] ___sys_sendmsg+0xa3/0x100
[ 245.689376] __sys_sendmsg+0x81/0xe0
[ 245.689378] do_syscall_64+0x5c/0x90
[ 245.689381] ? syscall_exit_to_user_mode+0x23/0x50
[ 245.689384] ? do_syscall_64+0x69/0x90
[ 245.689386] ? do_syscall_64+0x69/0x90
[ 245.689387] ? do_syscall_64+0x69/0x90
[ 245.689389] ? do_syscall_64+0x69/0x90
[ 245.689391] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 245.689393] RIP: 0033:0x7fac827fe56d
[ 245.689395] RSP: 002b:00007ffe92ae9b00 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
[ 245.689397] RAX: ffffffffffffffda RBX: 000000000000003a RCX: 00007fac827fe56d
[ 245.689398] RDX: 0000000000000000 RSI: 00007ffe92ae9b40 RDI: 000000000000000c
[ 245.689399] RBP: 00005621d0a4e030 R08: 0000000000000000 R09: 0000000000000000
[ 245.689400] R10: 0000000000000078 R11: 0000000000000293 R12: 0000000000000000
[ 245.689401] R13: 00007ffe92ae9c78 R14: 00007ffe92ae9c74 R15: 0000000000000000
[ 245.689402] </TASK>
[ 245.689406] INFO: task nodedev-init:8692 blocked for more than 122 seconds.
[ 245.689407] Not tainted 5.16.0-1-MANJARO #1
[ 245.689407] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689408] task:nodedev-init state:D stack: 0 pid: 8692 ppid: 1 flags:0x00004000
[ 245.689409] Call Trace:
[ 245.689410] <TASK>
[ 245.689411] __schedule+0x307/0x10e0
[ 245.689413] schedule+0x4b/0xd0
[ 245.689415] schedule_preempt_disabled+0x11/0x20
[ 245.689416] __mutex_lock.constprop.0+0x256/0x450
[ 245.689420] igb_resume+0xff/0x1e0 [igb dc0f69ebe9947076b314a1b66c852f2ca3d6e298]
[ 245.689429] pci_pm_runtime_resume+0xaa/0xd0
[ 245.689431] ? pci_pm_freeze_noirq+0x110/0x110
[ 245.689432] __rpm_callback+0x44/0x120
[ 245.689434] ? pci_pm_freeze_noirq+0x110/0x110
[ 245.689435] rpm_callback+0x35/0x70
[ 245.689436] rpm_resume+0x569/0x810
[ 245.689438] __pm_runtime_resume+0x4a/0x80
[ 245.689439] dev_ethtool+0x126/0x2f10
[ 245.689441] ? terminate_walk+0xe5/0xf0
[ 245.689444] ? path_openat+0xa5e/0x1030
[ 245.689447] ? kmem_cache_alloc+0x199/0x320
[ 245.689450] dev_ioctl+0x1c3/0x590
[ 245.689452] ? _copy_from_user+0x28/0x80
[ 245.689455] sock_do_ioctl+0xef/0x130
[ 245.689458] sock_ioctl+0x135/0x350
[ 245.689460] __x64_sys_ioctl+0x8e/0xd0
[ 245.689463] do_syscall_64+0x5c/0x90
[ 245.689464] ? syscall_exit_to_user_mode+0x23/0x50
[ 245.689466] ? do_syscall_64+0x69/0x90
[ 245.689468] ? syscall_exit_to_user_mode+0x23/0x50
[ 245.689470] ? do_syscall_64+0x69/0x90
[ 245.689471] ? do_syscall_64+0x69/0x90
[ 245.689473] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 245.689474] RIP: 0033:0x7f1ecf22759b
[ 245.689475] RSP: 002b:00007f1e8d7f9948 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 245.689476] RAX: ffffffffffffffda RBX: 00007f1e8d7f99f0 RCX: 00007f1ecf22759b
[ 245.689477] RDX: 00007f1e8d7f99c0 RSI: 0000000000008946 RDI: 000000000000001b
[ 245.689478] RBP: 000000000000001b R08: 0000000000000000 R09: 00007f1e74000080
[ 245.689479] R10: 00007f1e742ce250 R11: 0000000000000246 R12: 00007f1e8d7f99c0
[ 245.689480] R13: 00007f1e8d7f9998 R14: 00007f1e742cd8d0 R15: 00007f1e8d7f9a20
[ 245.689481] </TASK>
[ 245.689485] INFO: task wpa_supplicant:5247 blocked for more than 122 seconds.
[ 245.689485] Not tainted 5.16.0-1-MANJARO #1
[ 245.689486] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689486] task:wpa_supplicant state:D stack: 0 pid: 5247 ppid: 1 flags:0x00000000
[ 245.689488] Call Trace:
[ 245.689488] <TASK>
[ 245.689489] __schedule+0x307/0x10e0
[ 245.689491] ? free_unref_page+0xbd/0x140
[ 245.689494] ? __nla_validate_parse+0x880/0xc10
[ 245.689497] schedule+0x4b/0xd0
[ 245.689499] schedule_preempt_disabled+0x11/0x20
[ 245.689500] __mutex_lock.constprop.0+0x256/0x450
[ 245.689503] nl80211_pre_doit+0x16/0x160 [cfg80211 ae7d22c497a326c6721c15b3b45ed901d66eca80]
[ 245.689526] genl_family_rcv_msg_doit+0xe7/0x170
[ 245.689528] genl_rcv_msg+0xeb/0x1f0
[ 245.689530] ? nl80211_dump_station+0x2a0/0x2a0 [cfg80211 ae7d22c497a326c6721c15b3b45ed901d66eca80]
[ 245.689552] ? nl80211_send_station+0x1110/0x1110 [cfg80211 ae7d22c497a326c6721c15b3b45ed901d66eca80]
[ 245.689572] ? genl_get_cmd+0x100/0x100
[ 245.689573] netlink_rcv_skb+0x5b/0x110
[ 245.689575] genl_rcv+0x24/0x40
[ 245.689576] netlink_unicast+0x246/0x360
[ 245.689578] netlink_sendmsg+0x24f/0x4b0
[ 245.689580] sock_sendmsg+0x64/0x70
[ 245.689582] ____sys_sendmsg+0x266/0x2a0
[ 245.689584] ___sys_sendmsg+0xa3/0x100
[ 245.689588] __sys_sendmsg+0x81/0xe0
[ 245.689590] do_syscall_64+0x5c/0x90
[ 245.689591] ? do_syscall_64+0x69/0x90
[ 245.689593] ? do_syscall_64+0x69/0x90
[ 245.689594] ? irqtime_account_irq+0x40/0xc0
[ 245.689596] ? __do_softirq+0x176/0x2ca
[ 245.689599] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 245.689600] RIP: 0033:0x7f591b3a1cc7
[ 245.689601] RSP: 002b:00007ffc191d07c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 245.689602] RAX: ffffffffffffffda RBX: 000055cf16da27c0 RCX: 00007f591b3a1cc7
[ 245.689603] RDX: 0000000000000000 RSI: 00007ffc191d0800 RDI: 0000000000000006
[ 245.689604] RBP: 000055cf16da26d0 R08: 0000000000000004 R09: 00007f591b462a60
[ 245.689605] R10: 00007ffc191d08d4 R11: 0000000000000246 R12: 000055cf16de0660
[ 245.689605] R13: 00007ffc191d0800 R14: 00007ffc191d08d4 R15: 000055cf16df0db0
[ 245.689607] </TASK>
[ 245.689623] INFO: task geoclue:8289 blocked for more than 122 seconds.
[ 245.689624] Not tainted 5.16.0-1-MANJARO #1
[ 245.689624] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689625] task:geoclue state:D stack: 0 pid: 8289 ppid: 1 flags:0x00000000
[ 245.689626] Call Trace:
[ 245.689626] <TASK>
[ 245.689627] __schedule+0x307/0x10e0
[ 245.689629] ? do_sys_poll+0x52c/0x5f0
[ 245.689631] schedule+0x4b/0xd0
[ 245.689633] schedule_preempt_disabled+0x11/0x20
[ 245.689635] __mutex_lock.constprop.0+0x256/0x450
[ 245.689637] __netlink_dump_start+0xc2/0x2e0
[ 245.689638] ? rtnl_fill_link_ifmap+0xa0/0xa0
[ 245.689640] rtnetlink_rcv_msg+0x2a3/0x3a0
[ 245.689642] ? rtnl_fill_link_ifmap+0xa0/0xa0
[ 245.689644] ? rtnl_calcit.isra.0+0x160/0x160
[ 245.689646] netlink_rcv_skb+0x5b/0x110
[ 245.689648] netlink_unicast+0x246/0x360
[ 245.689649] netlink_sendmsg+0x24f/0x4b0
[ 245.689651] sock_sendmsg+0x64/0x70
[ 245.689653] __sys_sendto+0x128/0x1a0
[ 245.689656] __x64_sys_sendto+0x20/0x40
[ 245.689658] do_syscall_64+0x5c/0x90
[ 245.689659] ? syscall_exit_to_user_mode+0x23/0x50
[ 245.689661] ? do_syscall_64+0x69/0x90
[ 245.689663] ? syscall_exit_to_user_mode+0x23/0x50
[ 245.689664] ? do_syscall_64+0x69/0x90
[ 245.689666] ? do_syscall_64+0x69/0x90
[ 245.689667] ? do_syscall_64+0x69/0x90
[ 245.689669] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 245.689670] RIP: 0033:0x7fe613076c5c
[ 245.689671] RSP: 002b:00007ffcd8e9fef0 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
[ 245.689672] RAX: ffffffffffffffda RBX: 00007fe600008670 RCX: 00007fe613076c5c
[ 245.689672] RDX: 0000000000000014 RSI: 00007ffcd8e9ff70 RDI: 0000000000000007
[ 245.689673] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
[ 245.689674] R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000014
[ 245.689675] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000001407a28
[ 245.689676] </TASK>
[ 245.689695] INFO: task ip:8717 blocked for more than 122 seconds.
[ 245.689696] Not tainted 5.16.0-1-MANJARO #1
[ 245.689696] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.689696] task:ip state:D stack: 0 pid: 8717 ppid: 2366 flags:0x00000000
[ 245.689698] Call Trace:
[ 245.689699] <TASK>
[ 245.689699] __schedule+0x307/0x10e0
[ 245.689701] ? __blk_mq_sched_dispatch_requests+0x112/0x160
[ 245.689704] schedule+0x4b/0xd0
[ 245.689706] schedule_preempt_disabled+0x11/0x20
[ 245.689707] __mutex_lock.constprop.0+0x256/0x450
[ 245.689710] rtnetlink_rcv_msg+0x10b/0x3a0
[ 245.689712] ? rtnl_calcit.isra.0+0x160/0x160
[ 245.689714] netlink_rcv_skb+0x5b/0x110
[ 245.689716] netlink_unicast+0x246/0x360
[ 245.689717] netlink_sendmsg+0x24f/0x4b0
[ 245.689719] sock_sendmsg+0x64/0x70
[ 245.689721] __sys_sendto+0x128/0x1a0
[ 245.689724] __x64_sys_sendto+0x20/0x40
[ 245.689725] do_syscall_64+0x5c/0x90
[ 245.689726] ? syscall_exit_to_user_mode+0x23/0x50
[ 245.689728] ? exc_page_fault+0x72/0x180
[ 245.689730] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 245.689732] RIP: 0033:0x7f29b4659c10
[ 245.689732] RSP: 002b:00007ffe789e5f18 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
[ 245.689733] RAX: ffffffffffffffda RBX: 00007ffe789e6618 RCX: 00007f29b4659c10
[ 245.689734] RDX: 0000000000000020 RSI: 00007ffe789e5f30 RDI: 0000000000000003
[ 245.689735] RBP: 000055d63f1e2020 R08: 0000000000000000 R09: 0000000000000000
[ 245.689736] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
[ 245.689736] R13: 0000000000000001 R14: 00007ffe789e7e77 R15: 00007ffe789e7e77
[ 245.689738] </TASK>
[ 368.779147] INFO: task kworker/7:1:282 blocked for more than 245 seconds.
[ 368.779153] Not tainted 5.16.0-1-MANJARO #1
[ 368.779155] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 368.779156] task:kworker/7:1 state:D stack: 0 pid: 282 ppid: 2 flags:0x00004000
[ 368.779161] Workqueue: pm pm_runtime_work
[ 368.779167] Call Trace:
[ 368.779168] <TASK>
[ 368.779172] __schedule+0x307/0x10e0
[ 368.779178] ? update_load_avg+0x7e/0x600
[ 368.779182] schedule+0x4b/0xd0
[ 368.779184] schedule_preempt_disabled+0x11/0x20
[ 368.779187] __mutex_lock.constprop.0+0x256/0x450
[ 368.779192] rtl8169_runtime_suspend+0x19/0x70 [r8169 96a8125af3e9c3adc7f649de37220f6dfc45dc79]
[ 368.779198] pci_pm_runtime_suspend+0x5e/0x180
[ 368.779202] ? pci_dev_put+0x20/0x20
[ 368.779205] __rpm_callback+0x44/0x120
[ 368.779207] rpm_callback+0x35/0x70
[ 368.779209] ? pci_dev_put+0x20/0x20
[ 368.779211] rpm_suspend+0x177/0x750
[ 368.779214] pm_runtime_work+0x53/0xa0
[ 368.779216] process_one_work+0x1e8/0x3c0
[ 368.779219] worker_thread+0x50/0x3c0
[ 368.779221] ? rescuer_thread+0x390/0x390
[ 368.779222] kthread+0x15c/0x180
[ 368.779226] ? set_kthread_struct+0x50/0x50
[ 368.779228] ret_from_fork+0x22/0x30
[ 368.779233] </TASK>
[ 368.779237] INFO: task kworker/u64:4:317 blocked for more than 245 seconds.
[ 368.779239] Not tainted 5.16.0-1-MANJARO #1
[ 368.779240] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 368.779240] task:kworker/u64:4 state:D stack: 0 pid: 317 ppid: 2 flags:0x00004000
[ 368.779244] Workqueue: netns cleanup_net
[ 368.779248] Call Trace:
[ 368.779249] <TASK>
[ 368.779250] __schedule+0x307/0x10e0
[ 368.779253] ? schedule+0x4b/0xd0
[ 368.779255] ? wq_worker_running+0xa/0x40
[ 368.779258] schedule+0x4b/0xd0
[ 368.779260] schedule_preempt_disabled+0x11/0x20
[ 368.779263] __mutex_lock.constprop.0+0x256/0x450
[ 368.779266] cfg80211_pernet_exit+0xf/0x70 [cfg80211 ae7d22c497a326c6721c15b3b45ed901d66eca80]
[ 368.779294] ops_exit_list+0x33/0x70
[ 368.779297] cleanup_net+0x213/0x3c0
[ 368.779300] process_one_work+0x1e8/0x3c0
[ 368.779302] worker_thread+0x50/0x3c0
[ 368.779304] ? rescuer_thread+0x390/0x390
[ 368.779305] kthread+0x15c/0x180
[ 368.779308] ? set_kthread_struct+0x50/0x50
[ 368.779310] ret_from_fork+0x22/0x30
[ 368.779314] </TASK>
There is someone over at the eos forums that same issue and similar hardware.
Seems he tried linux-zen and the regular arch kernels. So most likely not an issue with specific manjaro patches.
https://forum.endeavouros.com/t/system-soft-lock-on-kernel-5-15/20970
Thanks for the tip! Glad to see there are other in our camp. I noticed that, on my machine, these hangs would typically come from network-related drivers. Things such as ‘igb’, ‘rtl8169’ and ‘cfg80211’. Though, not sure why it would effect programs like ‘sudo’, except that I know it tries to do host resolution.
For me, 5.15.0 works OK, but 5.15.1 is broken. There is a small handful of changes that were made, but nothing effecting networking 
I don’t think it’s Manjaro specific either. I had Ubuntu mate installed with a self compiled 5.15.x when the problem started. Things got so confusing that I opted to reinstall with Manjaro, all good until i tried 5.15 again. As pointed out before, 5.15.0 was ok for me and I think it happened when i updated it to 5.15.4 from there. So maybe the issue appeared between .0 and .4.
PS. I was going to give .8 a shot too so thanks for saving me the time chuck_r.
In my case , lspci is hanging, ifconfig is hanging so i thought my Intel NIC was bad, I replaced it with a new one ( still with the igb driver ), but the problem persisted and that’s when I started to look at a software issue.
If anything , I’ll see if i can recompile 5.15.0 and move through .1 and .2 to see when the problem appears.