February 2025 - openSUSE Users - openSUSE Mailing Lists

[oS-en] kernel problem, machine locks
by Carlos E. R. 11 Mar '25

11 Mar '25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was watching tv, was going to bed, went to hibernate computer: it was beeping every few seconds, and keyboard was locked. I had to hit hardware reset. I saw this on the log, going on for about two hours: Feb 17 00:27:05 Telcontar getnews.timer[20191]: Fetchnews run ok. Feb 17 00:27:05 Telcontar systemd[1]: leafnode-hourly.service: Deactivated successfully. Feb 17 00:27:47 Telcontar kernel: clocksource: Long readout interval, skipping watchdog check: cs_nsec: 1218883831 wd_nsec: 1218882986 Feb 17 00:27:56 Telcontar kernel: clocksource: Long readout interval, skipping watchdog check: cs_nsec: 3150770243 wd_nsec: 3150768044 Feb 17 00:28:42 Telcontar kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=14910, emitted seq=14910 Feb 17 00:28:42 Telcontar kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Feb 17 00:28:42 Telcontar kernel: ------------[ cut here ]------------ Feb 17 00:28:42 Telcontar kernel: WARNING: CPU: 3 PID: 19833 at ../include/linux/dma-fence.h:580 amdgpu_job_timedout+0x1f8/0x230 [amdgpu] Feb 17 00:28:42 Telcontar kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs snd_seq_dummy snd_hrtimer vmw_vsock_vmci_transport vsock vmw_vmci xt_tcpudp nf_nat_ftp nf_nat_sip nf_conntrack_ftp nf_conntrack_sip nf_conntrack_netbios_ns nf_conntrack_broadcast nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 n> Feb 17 00:28:42 Telcontar kernel: raid6_pq libcrc32c dm_mod amdgpu intel_rapl_msr ppdev snd_hda_codec_realtek snd_hda_codec_generic battery snd_hda_codec_hdmi amd_atl drm_exec intel_rapl_common amdxcp drm_buddy edac_mce_amd gpu_sched snd_hda_intel i2c_algo_bit drm_suballoc_helper snd_intel_dspcfg snd_intel_sdw_acpi drm_display_helper r8169 kvm_amd snd_hda_codec drm_ttm_h> Feb 17 00:28:42 Telcontar kernel: scsi_dh_rdac scsi_dh_alua crypto_simd nvme_auth sg t10_pi cryptd ccp usbcore crc64_rocksoft_generic scsi_mod sp5100_tco(n) crc64_rocksoft crc64 wmi msr efivarfs Feb 17 00:28:42 Telcontar kernel: Unloaded tainted modules: msi_ec(n):1 Feb 17 00:28:42 Telcontar kernel: Supported: No, Unsupported modules are loaded Feb 17 00:28:42 Telcontar kernel: CPU: 3 PID: 19833 Comm: kworker/u64:0 Tainted: G OE n 6.4.0-150600.23.38-default #1 SLE15-SP6 46e958e1e6a4044cfee7b3413eeabfe5a22d6494 Feb 17 00:28:42 Telcontar kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.40 11/06/2019 Feb 17 00:28:42 Telcontar kernel: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] Feb 17 00:28:42 Telcontar kernel: RIP: 0010:amdgpu_job_timedout+0x1f8/0x230 [amdgpu] Feb 17 00:28:42 Telcontar kernel: Code: 8b 7b 88 48 8d 55 80 4c 89 e6 e8 d3 9d db ff 85 c0 0f 84 3e ff ff ff 89 c6 48 c7 c7 18 47 df c1 e8 8d e8 b8 fa e9 2b ff ff ff <0f> 0b e9 f2 fe ff ff e8 4c 40 f3 fa 49 8b 44 24 18 48 c7 c6 10 b2 Feb 17 00:28:42 Telcontar kernel: RSP: 0018:ffffabe563f3fdc0 EFLAGS: 00010202 Feb 17 00:28:42 Telcontar kernel: RAX: ffff91148029f780 RBX: ffff911316e24ef8 RCX: 0000000000000027 Feb 17 00:28:42 Telcontar kernel: RDX: 0000000000000001 RSI: 00000000fffeffff RDI: ffff91215e1a3508 Feb 17 00:28:42 Telcontar kernel: RBP: ffffabe563f3fe50 R08: 0000000000000000 R09: c0000000fffeffff Feb 17 00:28:42 Telcontar kernel: R10: ffffabe563f3fe70 R11: ffffabe563f3fb90 R12: ffff9113a7a33000 Feb 17 00:28:42 Telcontar kernel: R13: ffff911316e00000 R14: ffff9113a7a33000 R15: ffff91118b08d900 Feb 17 00:28:42 Telcontar kernel: FS: 0000000000000000(0000) GS:ffff91215e180000(0000) knlGS:0000000000000000 Feb 17 00:28:42 Telcontar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 00:28:42 Telcontar kernel: CR2: 00007fc68afe5fa0 CR3: 0000000227544000 CR4: 0000000000350ee0 Feb 17 00:28:42 Telcontar kernel: Call Trace: Feb 17 00:28:42 Telcontar kernel: <TASK> Feb 17 00:28:42 Telcontar kernel: ? __warn+0x7d/0x140 Feb 17 00:28:42 Telcontar kernel: ? amdgpu_job_timedout+0x1f8/0x230 [amdgpu 90e289b9939e2e42904549b39c68f0f830f1416f] Feb 17 00:28:42 Telcontar kernel: ? report_bug+0xfb/0x1e0 Feb 17 00:28:42 Telcontar kernel: ? handle_bug+0x44/0x80 Feb 17 00:28:42 Telcontar kernel: ? exc_invalid_op+0x13/0x60 Feb 17 00:28:42 Telcontar kernel: ? asm_exc_invalid_op+0x16/0x20 Feb 17 00:28:42 Telcontar kernel: ? amdgpu_job_timedout+0x1f8/0x230 [amdgpu 90e289b9939e2e42904549b39c68f0f830f1416f] Feb 17 00:28:42 Telcontar kernel: ? __update_idle_core+0x5d/0xc0 Feb 17 00:28:42 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 00:28:42 Telcontar kernel: ? finish_task_switch+0x8a/0x2d0 Feb 17 00:28:42 Telcontar kernel: ? drm_sched_job_timedout+0x68/0xd0 [gpu_sched 25239add3a906380d8957fb09d365791faaca961] Feb 17 00:28:42 Telcontar kernel: ? __pfx_amdgpu_job_timedout+0x10/0x10 [amdgpu 90e289b9939e2e42904549b39c68f0f830f1416f] Feb 17 00:28:42 Telcontar kernel: drm_sched_job_timedout+0x68/0xd0 [gpu_sched 25239add3a906380d8957fb09d365791faaca961] Feb 17 00:28:42 Telcontar kernel: process_one_work+0x226/0x460 Feb 17 00:28:42 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:28:42 Telcontar kernel: worker_thread+0x2a/0x3b0 Feb 17 00:28:42 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:28:42 Telcontar kernel: kthread+0xe1/0x120 Feb 17 00:28:42 Telcontar kernel: ? __pfx_kthread+0x10/0x10 Feb 17 00:28:42 Telcontar kernel: ret_from_fork+0x2c/0x50 Feb 17 00:28:42 Telcontar kernel: </TASK> Feb 17 00:28:42 Telcontar kernel: ---[ end trace 0000000000000000 ]--- Feb 17 00:28:42 Telcontar kernel: amdgpu 0000:27:00.0: amdgpu: GPU reset begin! Feb 17 00:29:02 Telcontar kernel: clocksource: Long readout interval, skipping watchdog check: cs_nsec: 11406283928 wd_nsec: 11406277123 Feb 17 00:29:05 Telcontar kernel: amdgpu 0000:27:00.0: amdgpu: Guilty job already signaled, skipping HW reset Feb 17 00:29:05 Telcontar kernel: amdgpu 0000:27:00.0: amdgpu: GPU reset(1) succeeded! Feb 17 00:30:01 Telcontar CRON[20396]: (root) CMD ([ -x /usr/lib64/sa/sa1 ] && exec /usr/lib64/sa/sa1 1 1) Feb 17 00:30:01 Telcontar CRON[20393]: (root) CMDEND ([ -x /usr/lib64/sa/sa1 ] && exec /usr/lib64/sa/sa1 1 1) Feb 17 00:30:43 Telcontar systemd[1]: Started Session c101 of User cer. Feb 17 00:34:43 Telcontar fetchnews[20707]: fetchnews: 0 articles and 0 headers fetched, 0 killed, 0 posted, in 143 seconds Feb 17 00:34:45 Telcontar getnews.timer[20849]: Fetchnews run ok. Feb 17 00:34:45 Telcontar systemd[1]: leafnode-hourly.service: Deactivated successfully. Feb 17 00:34:49 Telcontar rtkit-daemon[5348]: The canary thread is apparently starving. Taking action. Feb 17 00:34:49 Telcontar rtkit-daemon[5348]: Demoting known real-time threads. Feb 17 00:34:49 Telcontar rtkit-daemon[5348]: Successfully demoted thread 29270 of process 28237. Feb 17 00:34:49 Telcontar rtkit-daemon[5348]: Successfully demoted thread 27128 of process 27015. Feb 17 00:34:49 Telcontar rtkit-daemon[5348]: Successfully demoted thread 26748 of process 26598. Feb 17 00:34:49 Telcontar rtkit-daemon[5348]: Demoted 3 threads. Feb 17 00:35:20 Telcontar rtkit-daemon[5348]: The canary thread is apparently starving. Taking action. Feb 17 00:35:20 Telcontar rtkit-daemon[5348]: Demoting known real-time threads. Feb 17 00:35:20 Telcontar rtkit-daemon[5348]: Successfully demoted thread 29270 of process 28237. Feb 17 00:35:20 Telcontar rtkit-daemon[5348]: Successfully demoted thread 27128 of process 27015. Feb 17 00:35:20 Telcontar rtkit-daemon[5348]: Successfully demoted thread 26748 of process 26598. Feb 17 00:35:20 Telcontar rtkit-daemon[5348]: Demoted 3 threads. Feb 17 00:36:28 Telcontar rtkit-daemon[5348]: The canary thread is apparently starving. Taking action. Feb 17 00:36:28 Telcontar rtkit-daemon[5348]: Demoting known real-time threads. Feb 17 00:36:28 Telcontar rtkit-daemon[5348]: Successfully demoted thread 29270 of process 28237. Feb 17 00:36:28 Telcontar rtkit-daemon[5348]: Successfully demoted thread 27128 of process 27015. Feb 17 00:36:28 Telcontar rtkit-daemon[5348]: Successfully demoted thread 26748 of process 26598. Feb 17 00:36:28 Telcontar rtkit-daemon[5348]: Demoted 3 threads. Feb 17 00:38:35 Telcontar kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 21s! [kworker/u64:4:19295] Feb 17 00:38:35 Telcontar kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs snd_seq_dummy snd_hrtimer vmw_vsock_vmci_transport vsock vmw_vmci xt_tcpudp nf_nat_ftp nf_nat_sip nf_conntrack_ftp nf_conntrack_sip nf_conntrack_netbios_ns nf_conntrack_broadcast nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 n> Feb 17 00:38:35 Telcontar kernel: raid6_pq libcrc32c dm_mod amdgpu intel_rapl_msr ppdev snd_hda_codec_realtek snd_hda_codec_generic battery snd_hda_codec_hdmi amd_atl drm_exec intel_rapl_common amdxcp drm_buddy edac_mce_amd gpu_sched snd_hda_intel i2c_algo_bit drm_suballoc_helper snd_intel_dspcfg snd_intel_sdw_acpi drm_display_helper r8169 kvm_amd snd_hda_codec drm_ttm_h> Feb 17 00:38:35 Telcontar kernel: scsi_dh_rdac scsi_dh_alua crypto_simd nvme_auth sg t10_pi cryptd ccp usbcore crc64_rocksoft_generic scsi_mod sp5100_tco(n) crc64_rocksoft crc64 wmi msr efivarfs Feb 17 00:38:35 Telcontar kernel: Unloaded tainted modules: msi_ec(n):1 Feb 17 00:38:35 Telcontar kernel: Supported: No, Unsupported modules are loaded Feb 17 00:38:35 Telcontar kernel: CPU: 6 PID: 19295 Comm: kworker/u64:4 Tainted: G W OE n 6.4.0-150600.23.38-default #1 SLE15-SP6 46e958e1e6a4044cfee7b3413eeabfe5a22d6494 Feb 17 00:38:35 Telcontar kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.40 11/06/2019 Feb 17 00:38:35 Telcontar kernel: Workqueue: writeback wb_workfn (flush-259:0) Feb 17 00:38:35 Telcontar kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x238/0x2c0 Feb 17 00:38:35 Telcontar kernel: Code: 83 c5 01 41 c1 e4 10 41 c1 e5 12 45 09 ec 44 89 e0 c1 e8 10 66 87 45 02 89 c2 c1 e2 10 85 d2 75 39 31 d2 eb 02 f3 90 8b 45 00 <66> 85 c0 75 f6 89 c1 66 31 c9 41 39 cc 74 5f 48 85 d2 c6 45 00 01 Feb 17 00:38:35 Telcontar kernel: RSP: 0018:ffffabe56315fad0 EFLAGS: 00000202 Feb 17 00:38:35 Telcontar kernel: RAX: 0000000000180001 RBX: ffff91215e336f00 RCX: 0000000000000000 Feb 17 00:38:35 Telcontar kernel: RDX: ffff91215e436f00 RSI: 0000000000100000 RDI: ffff911361408458 Feb 17 00:38:35 Telcontar kernel: RBP: ffff911361408458 R08: ffff911361408428 R09: 0000000000035900 Feb 17 00:38:35 Telcontar kernel: R10: ffffabe54b9efb78 R11: 00000000000002af R12: 00000000001c0000 Feb 17 00:38:35 Telcontar kernel: R13: 00000000001c0000 R14: ffffabe56315fb50 R15: 00000001010c731b Feb 17 00:38:35 Telcontar kernel: FS: 0000000000000000(0000) GS:ffff91215e300000(0000) knlGS:0000000000000000 Feb 17 00:38:35 Telcontar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 00:38:35 Telcontar kernel: CR2: 00007ff08ac07fc0 CR3: 00000003fbf20000 CR4: 0000000000350ee0 Feb 17 00:38:35 Telcontar kernel: Call Trace: Feb 17 00:38:35 Telcontar kernel: <IRQ> Feb 17 00:38:35 Telcontar kernel: ? watchdog_timer_fn+0x1ae/0x210 Feb 17 00:38:35 Telcontar kernel: ? __pfx_watchdog_timer_fn+0x10/0x10 Feb 17 00:38:35 Telcontar kernel: ? __hrtimer_run_queues+0x111/0x280 Feb 17 00:38:35 Telcontar kernel: ? hrtimer_interrupt+0xe5/0x250 Feb 17 00:38:35 Telcontar kernel: ? __sysvec_apic_timer_interrupt+0x5a/0x120 Feb 17 00:38:35 Telcontar kernel: ? sysvec_apic_timer_interrupt+0x4b/0x90 Feb 17 00:38:35 Telcontar kernel: </IRQ> Feb 17 00:38:35 Telcontar kernel: <TASK> Feb 17 00:38:35 Telcontar kernel: ? asm_sysvec_apic_timer_interrupt+0x16/0x20 Feb 17 00:38:35 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x238/0x2c0 Feb 17 00:38:35 Telcontar kernel: _raw_spin_lock+0x25/0x30 Feb 17 00:38:35 Telcontar kernel: __wb_update_bandwidth+0x3c/0x1c0 Feb 17 00:38:35 Telcontar kernel: wb_update_bandwidth+0x4e/0x70 Feb 17 00:38:35 Telcontar kernel: do_writepages+0x18e/0x1b0 Feb 17 00:38:35 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x235/0x2c0 Feb 17 00:38:35 Telcontar kernel: __writeback_single_inode+0x41/0x350 Feb 17 00:38:35 Telcontar kernel: writeback_sb_inodes+0x1d7/0x470 Feb 17 00:38:35 Telcontar kernel: __writeback_inodes_wb+0x5f/0xd0 Feb 17 00:38:35 Telcontar kernel: wb_writeback+0x281/0x300 Feb 17 00:38:35 Telcontar kernel: wb_workfn+0x1f5/0x470 Feb 17 00:38:35 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 00:38:35 Telcontar kernel: ? __schedule+0x389/0x1540 Feb 17 00:38:35 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 00:38:35 Telcontar kernel: process_one_work+0x226/0x460 Feb 17 00:38:35 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:38:35 Telcontar kernel: worker_thread+0x2a/0x3b0 Feb 17 00:38:35 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:38:35 Telcontar kernel: kthread+0xe1/0x120 Feb 17 00:38:35 Telcontar kernel: ? __pfx_kthread+0x10/0x10 Feb 17 00:38:35 Telcontar kernel: ret_from_fork+0x2c/0x50 Feb 17 00:38:35 Telcontar kernel: </TASK> Feb 17 00:38:36 Telcontar systemd[1]: Started fetching news messages spool hourly. Feb 17 00:38:37 Telcontar fetchnews[21098]: config: debugmode is 1001 Feb 17 00:38:37 Telcontar fetchnews[21098]: fetchnews: version 2.0.0.alpha202101; verbosity level is 0; debugging level is 1001 Feb 17 00:38:37 Telcontar fetchnews[21098]: fetchnews mode: get articles, get headers, get bodies, post articles Feb 17 00:38:37 Telcontar fetchnews[21098]: last active refetch 71 days ago. Feb 17 00:38:37 Telcontar fetchnews[21098]: lockfile_exists(timeout=5), fqdn="Telcontar.valinor" Feb 17 00:38:54 Telcontar systemd[1]: Starting Check if mainboard battery is Ok... Feb 17 00:39:01 Telcontar fetchnews[21098]: expiring interesting.groups Feb 17 00:39:01 Telcontar fetchnews[21098]: reading /var/spool/news/leaf.node/groupinfo and /etc/leafnode/local.groups Feb 17 00:39:01 Telcontar fetchnews[21098]: found 0 articles in in.coming. Feb 17 00:39:01 Telcontar fetchnews[21098]: News.Individual.NET: connecting to port nntp Feb 17 00:39:14 Telcontar systemd[1]: check-battery.service: Deactivated successfully. Feb 17 00:39:15 Telcontar rtkit-daemon[5348]: The canary thread is apparently starving. Taking action. Feb 17 00:39:15 Telcontar rtkit-daemon[5348]: Demoting known real-time threads. Feb 17 00:39:15 Telcontar rtkit-daemon[5348]: Successfully demoted thread 29270 of process 28237. Feb 17 00:39:15 Telcontar rtkit-daemon[5348]: Successfully demoted thread 27128 of process 27015. Feb 17 00:39:15 Telcontar rtkit-daemon[5348]: Successfully demoted thread 26748 of process 26598. Feb 17 00:39:15 Telcontar rtkit-daemon[5348]: Demoted 3 threads. Feb 17 00:39:29 Telcontar kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [kworker/u64:4:19295] Feb 17 00:39:15 Telcontar rtkit-daemon[5348]: Demoted 3 threads. Feb 17 00:39:29 Telcontar kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [kworker/u64:4:19295] Feb 17 00:39:29 Telcontar kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs snd_seq_dummy snd_hrtimer vmw_vsock_vmci_transport vsock vmw_vmci xt_tcpudp nf_nat_ftp nf_nat_sip nf_conntrack_ftp nf_conntrack_sip nf_conntrack_netbios_ns nf_conntrack_broadcast nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 n> Feb 17 00:39:29 Telcontar kernel: raid6_pq libcrc32c dm_mod amdgpu intel_rapl_msr ppdev snd_hda_codec_realtek snd_hda_codec_generic battery snd_hda_codec_hdmi amd_atl drm_exec intel_rapl_common amdxcp drm_buddy edac_mce_amd gpu_sched snd_hda_intel i2c_algo_bit drm_suballoc_helper snd_intel_dspcfg snd_intel_sdw_acpi drm_display_helper r8169 kvm_amd snd_hda_codec drm_ttm_h> Feb 17 00:39:29 Telcontar kernel: scsi_dh_rdac scsi_dh_alua crypto_simd nvme_auth sg t10_pi cryptd ccp usbcore crc64_rocksoft_generic scsi_mod sp5100_tco(n) crc64_rocksoft crc64 wmi msr efivarfs Feb 17 00:39:29 Telcontar kernel: Unloaded tainted modules: msi_ec(n):1 Feb 17 00:39:29 Telcontar kernel: Supported: No, Unsupported modules are loaded Feb 17 00:39:29 Telcontar kernel: CPU: 6 PID: 19295 Comm: kworker/u64:4 Tainted: G W OEL n 6.4.0-150600.23.38-default #1 SLE15-SP6 46e958e1e6a4044cfee7b3413eeabfe5a22d6494 Feb 17 00:39:29 Telcontar kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.40 11/06/2019 Feb 17 00:39:29 Telcontar kernel: Workqueue: writeback wb_workfn (flush-259:0) Feb 17 00:39:29 Telcontar kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x235/0x2c0 Feb 17 00:39:29 Telcontar kernel: Code: eb f5 41 83 c5 01 41 c1 e4 10 41 c1 e5 12 45 09 ec 44 89 e0 c1 e8 10 66 87 45 02 89 c2 c1 e2 10 85 d2 75 39 31 d2 eb 02 f3 90 <8b> 45 00 66 85 c0 75 f6 89 c1 66 31 c9 41 39 cc 74 5f 48 85 d2 c6 Feb 17 00:39:29 Telcontar kernel: RSP: 0018:ffffabe56315fad0 EFLAGS: 00000202 Feb 17 00:39:29 Telcontar kernel: RAX: 0000000000080001 RBX: ffff91215e336f00 RCX: 0000000000000000 Feb 17 00:39:29 Telcontar kernel: RDX: ffff91215e036f00 RSI: 0000000000300000 RDI: ffff911361408458 Feb 17 00:39:29 Telcontar kernel: RBP: ffff911361408458 R08: ffff911361408428 R09: 0000000000035900 Feb 17 00:39:29 Telcontar kernel: R10: ffffabe54bfb7858 R11: 00000000000002fa R12: 00000000001c0000 Feb 17 00:39:29 Telcontar kernel: R13: 00000000001c0000 R14: ffffabe56315fb50 R15: 00000001010ca091 Feb 17 00:39:29 Telcontar kernel: FS: 0000000000000000(0000) GS:ffff91215e300000(0000) knlGS:0000000000000000 Feb 17 00:39:29 Telcontar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 00:39:29 Telcontar kernel: CR2: 000005d3fcea1000 CR3: 000000026fbee000 CR4: 0000000000350ee0 Feb 17 00:39:29 Telcontar kernel: Call Trace: Feb 17 00:39:29 Telcontar kernel: <IRQ> Feb 17 00:39:29 Telcontar kernel: ? watchdog_timer_fn+0x1ae/0x210 Feb 17 00:39:29 Telcontar kernel: ? __pfx_watchdog_timer_fn+0x10/0x10 Feb 17 00:39:29 Telcontar kernel: ? __hrtimer_run_queues+0x111/0x280 Feb 17 00:39:29 Telcontar kernel: ? hrtimer_interrupt+0xe5/0x250 Feb 17 00:39:29 Telcontar kernel: ? __sysvec_apic_timer_interrupt+0x5a/0x120 Feb 17 00:39:29 Telcontar kernel: ? sysvec_apic_timer_interrupt+0x4b/0x90 Feb 17 00:39:29 Telcontar kernel: </IRQ> Feb 17 00:39:29 Telcontar kernel: <TASK> Feb 17 00:39:29 Telcontar kernel: ? asm_sysvec_apic_timer_interrupt+0x16/0x20 Feb 17 00:39:29 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x235/0x2c0 Feb 17 00:39:29 Telcontar kernel: _raw_spin_lock+0x25/0x30 Feb 17 00:39:29 Telcontar kernel: __wb_update_bandwidth+0x3c/0x1c0 Feb 17 00:39:29 Telcontar kernel: wb_update_bandwidth+0x4e/0x70 Feb 17 00:39:29 Telcontar kernel: do_writepages+0x18e/0x1b0 Feb 17 00:39:29 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x235/0x2c0 Feb 17 00:39:29 Telcontar kernel: __writeback_single_inode+0x41/0x350 Feb 17 00:39:29 Telcontar kernel: writeback_sb_inodes+0x1d7/0x470 Feb 17 00:39:29 Telcontar kernel: __writeback_inodes_wb+0x5f/0xd0 Feb 17 00:39:29 Telcontar kernel: wb_writeback+0x281/0x300 Feb 17 00:39:29 Telcontar kernel: wb_workfn+0x1f5/0x470 Feb 17 00:39:29 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 00:39:29 Telcontar kernel: ? __schedule+0x389/0x1540 Feb 17 00:39:29 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 00:39:29 Telcontar kernel: process_one_work+0x226/0x460 Feb 17 00:39:29 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:39:29 Telcontar kernel: worker_thread+0x2a/0x3b0 Feb 17 00:39:29 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:39:29 Telcontar kernel: kthread+0xe1/0x120 Feb 17 00:39:29 Telcontar kernel: ? __pfx_kthread+0x10/0x10 Feb 17 00:39:29 Telcontar kernel: ret_from_fork+0x2c/0x50 Feb 17 00:39:29 Telcontar kernel: </TASK> Feb 17 00:39:21 Telcontar fetchnews[21098]: trying: address 130.133.4.11 port 119... Feb 17 00:39:23 Telcontar fetchnews[21098]: connected: address 130.133.4.11 port 119. Feb 17 00:39:33 Telcontar rtkit-daemon[5348]: The canary thread is apparently starving. Taking action. Feb 17 00:39:33 Telcontar rtkit-daemon[5348]: Demoting known real-time threads. Feb 17 00:39:33 Telcontar rtkit-daemon[5348]: Successfully demoted thread 29270 of process 28237. Feb 17 00:39:33 Telcontar rtkit-daemon[5348]: Successfully demoted thread 27128 of process 27015. Feb 17 00:39:33 Telcontar rtkit-daemon[5348]: Successfully demoted thread 26748 of process 26598. Feb 17 00:39:33 Telcontar rtkit-daemon[5348]: Demoted 3 threads. Feb 17 00:39:54 Telcontar kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [kworker/u64:4:19295] Feb 17 00:39:54 Telcontar kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs snd_seq_dummy snd_hrtimer vmw_vsock_vmci_transport vsock vmw_vmci xt_tcpudp nf_nat_ftp nf_nat_sip nf_conntrack_ftp nf_conntrack_sip nf_conntrack_netbios_ns nf_conntrack_broadcast nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 n> Feb 17 00:40:21 Telcontar kernel: raid6_pq libcrc32c dm_mod amdgpu intel_rapl_msr ppdev snd_hda_codec_realtek snd_hda_codec_generic battery snd_hda_codec_hdmi amd_atl drm_exec intel_rapl_common amdxcp drm_buddy edac_mce_amd gpu_sched snd_hda_intel i2c_algo_bit drm_suballoc_helper snd_intel_dspcfg snd_intel_sdw_acpi drm_display_helper r8169 kvm_amd snd_hda_codec drm_ttm_h> Feb 17 00:40:21 Telcontar kernel: scsi_dh_rdac scsi_dh_alua crypto_simd nvme_auth sg t10_pi cryptd ccp usbcore crc64_rocksoft_generic scsi_mod sp5100_tco(n) crc64_rocksoft crc64 wmi msr efivarfs Feb 17 00:40:21 Telcontar kernel: Unloaded tainted modules: msi_ec(n):1 Feb 17 00:40:21 Telcontar kernel: Supported: No, Unsupported modules are loaded Feb 17 00:40:21 Telcontar kernel: CPU: 6 PID: 19295 Comm: kworker/u64:4 Tainted: G W OEL n 6.4.0-150600.23.38-default #1 SLE15-SP6 46e958e1e6a4044cfee7b3413eeabfe5a22d6494 Feb 17 00:40:21 Telcontar kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.40 11/06/2019 Feb 17 00:40:21 Telcontar kernel: Workqueue: writeback wb_workfn (flush-259:0) Feb 17 00:40:21 Telcontar kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 00:40:21 Telcontar kernel: Code: c1 ea 12 83 e0 03 83 ea 01 48 c1 e0 05 48 63 d2 48 05 00 6f 03 00 48 03 04 d5 60 1c ec bc 48 89 18 8b 43 08 85 c0 75 09 f3 90 <8b> 43 08 85 c0 74 f7 48 8b 13 48 85 d2 74 94 0f 0d 0a eb 8f b9 01 Feb 17 00:40:21 Telcontar kernel: RSP: 0018:ffffabe56315fad0 EFLAGS: 00000246 Feb 17 00:40:21 Telcontar kernel: RAX: 0000000000000000 RBX: ffff91215e336f00 RCX: 0000000000000000 Feb 17 00:40:21 Telcontar kernel: RDX: 0000000000000004 RSI: 0000000000140000 RDI: ffff911361408458 Feb 17 00:40:21 Telcontar kernel: RBP: ffff911361408458 R08: ffff911361408428 R09: 000000000000983c Feb 17 00:40:21 Telcontar kernel: R10: ffffabe56547fbc0 R11: 000000000000023e R12: 00000000001c0000 Feb 17 00:40:21 Telcontar kernel: R13: 00000000001c0000 R14: ffffabe56315fb50 R15: 00000001010cb8f6 Feb 17 00:40:21 Telcontar kernel: FS: 0000000000000000(0000) GS:ffff91215e300000(0000) knlGS:0000000000000000 Feb 17 00:40:21 Telcontar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 00:40:21 Telcontar kernel: CR2: 00007fe9989b9014 CR3: 00000002584c0000 CR4: 0000000000350ee0 Feb 17 00:40:21 Telcontar kernel: Call Trace: Feb 17 00:40:21 Telcontar kernel: <IRQ> Feb 17 00:40:21 Telcontar kernel: ? watchdog_timer_fn+0x1ae/0x210 Feb 17 00:40:21 Telcontar kernel: ? __pfx_watchdog_timer_fn+0x10/0x10 Feb 17 00:40:21 Telcontar kernel: ? __hrtimer_run_queues+0x111/0x280 Feb 17 00:40:21 Telcontar kernel: ? hrtimer_interrupt+0xe5/0x250 Feb 17 00:40:21 Telcontar kernel: ? __sysvec_apic_timer_interrupt+0x5a/0x120 Feb 17 00:40:21 Telcontar kernel: ? sysvec_apic_timer_interrupt+0x4b/0x90 Feb 17 00:40:21 Telcontar kernel: </IRQ> Feb 17 00:40:21 Telcontar kernel: <TASK> Feb 17 00:40:21 Telcontar kernel: ? asm_sysvec_apic_timer_interrupt+0x16/0x20 Feb 17 00:40:21 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 00:40:21 Telcontar kernel: _raw_spin_lock+0x25/0x30 Feb 17 00:40:21 Telcontar kernel: __wb_update_bandwidth+0x3c/0x1c0 Feb 17 00:40:21 Telcontar kernel: wb_update_bandwidth+0x4e/0x70 Feb 17 00:40:21 Telcontar kernel: do_writepages+0x18e/0x1b0 Feb 17 00:40:21 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x235/0x2c0 Feb 17 00:40:21 Telcontar kernel: __writeback_single_inode+0x41/0x350 Feb 17 00:40:21 Telcontar kernel: writeback_sb_inodes+0x1d7/0x470 Feb 17 00:40:21 Telcontar kernel: __writeback_inodes_wb+0x5f/0xd0 Feb 17 00:40:21 Telcontar kernel: wb_writeback+0x281/0x300 Feb 17 00:40:21 Telcontar kernel: wb_workfn+0x1f5/0x470 Feb 17 00:40:21 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 00:40:21 Telcontar kernel: ? __schedule+0x389/0x1540 Feb 17 00:40:21 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 00:40:21 Telcontar kernel: process_one_work+0x226/0x460 Feb 17 00:40:21 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:40:21 Telcontar kernel: worker_thread+0x2a/0x3b0 Feb 17 00:40:21 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 00:40:21 Telcontar kernel: kthread+0xe1/0x120 Feb 17 00:40:21 Telcontar kernel: ? __pfx_kthread+0x10/0x10 Feb 17 00:40:21 Telcontar kernel: ret_from_fork+0x2c/0x50 Feb 17 00:40:21 Telcontar kernel: </TASK> Feb 17 00:40:21 Telcontar kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 21s! [kworker/u64:4:19295] Feb 17 00:40:21 Telcontar kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs snd_seq_dummy snd_hrtimer vmw_vsock_vmci_transport vsock vmw_vmci xt_tcpudp nf_nat_ftp nf_nat_sip nf_conntrack_ftp nf_conntrack_sip nf_conntrack_netbios_ns nf_conntrack_broadcast nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 n> ... Feb 17 02:38:07 Telcontar kernel: ret_from_fork+0x2c/0x50 Feb 17 02:38:07 Telcontar kernel: </TASK> Feb 17 02:38:07 Telcontar kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 21s! [kworker/4:1:20203] Feb 17 02:38:07 Telcontar kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs snd_seq_dummy snd_hrtimer vmw_vsock_vmci_transport vsock vmw_vmci xt_tcpudp nf_nat_ftp nf_nat_sip nf_conntrack_ftp nf_conntrack_sip nf_conntrack_netbios_ns nf_conntrack_broadcast nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 n> Feb 17 02:38:07 Telcontar kernel: raid6_pq libcrc32c dm_mod amdgpu intel_rapl_msr ppdev snd_hda_codec_realtek snd_hda_codec_generic battery snd_hda_codec_hdmi amd_atl drm_exec intel_rapl_common amdxcp drm_buddy edac_mce_amd gpu_sched snd_hda_intel i2c_algo_bit drm_suballoc_helper snd_intel_dspcfg snd_intel_sdw_acpi drm_display_helper r8169 kvm_amd snd_hda_codec drm_ttm_h> Feb 17 02:38:07 Telcontar kernel: scsi_dh_rdac scsi_dh_alua crypto_simd nvme_auth sg t10_pi cryptd ccp usbcore crc64_rocksoft_generic scsi_mod sp5100_tco(n) crc64_rocksoft crc64 wmi msr efivarfs Feb 17 02:38:07 Telcontar kernel: Unloaded tainted modules: msi_ec(n):1 Feb 17 02:38:07 Telcontar kernel: Supported: No, Unsupported modules are loaded Feb 17 02:38:07 Telcontar kernel: CPU: 4 PID: 20203 Comm: kworker/4:1 Tainted: G W OEL n 6.4.0-150600.23.38-default #1 SLE15-SP6 46e958e1e6a4044cfee7b3413eeabfe5a22d6494 Feb 17 02:38:07 Telcontar kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.40 11/06/2019 Feb 17 02:38:07 Telcontar kernel: Workqueue: inode_switch_wbs inode_switch_wbs_work_fn Feb 17 02:38:07 Telcontar kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 02:38:07 Telcontar kernel: Code: c1 ea 12 83 e0 03 83 ea 01 48 c1 e0 05 48 63 d2 48 05 00 6f 03 00 48 03 04 d5 60 1c ec bc 48 89 18 8b 43 08 85 c0 75 09 f3 90 <8b> 43 08 85 c0 74 f7 48 8b 13 48 85 d2 74 94 0f 0d 0a eb 8f b9 01 Feb 17 02:38:07 Telcontar kernel: RSP: 0018:ffffabe56449fda0 EFLAGS: 00000246 Feb 17 02:38:07 Telcontar kernel: RAX: 0000000000000000 RBX: ffff91215e236f00 RCX: ffff9113d8951008 Feb 17 02:38:07 Telcontar kernel: RDX: 000000000000000a RSI: 00000000002c0000 RDI: ffff911361408458 Feb 17 02:38:07 Telcontar kernel: RBP: ffff911361408458 R08: ffff911312a82204 R09: ffff91215edfecc0 Feb 17 02:38:07 Telcontar kernel: R10: 8080808080808080 R11: 0000000000000010 R12: 0000000000140000 Feb 17 02:38:07 Telcontar kernel: R13: 0000000000140000 R14: ffff911361408400 R15: ffff91142ece3c00 Feb 17 02:38:07 Telcontar kernel: FS: 0000000000000000(0000) GS:ffff91215e200000(0000) knlGS:0000000000000000 Feb 17 02:38:07 Telcontar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 02:38:07 Telcontar kernel: CR2: 0000276684f6c000 CR3: 0000000438afe000 CR4: 0000000000350ee0 Feb 17 02:38:07 Telcontar kernel: Call Trace: Feb 17 02:38:07 Telcontar kernel: <IRQ> Feb 17 02:38:07 Telcontar kernel: ? watchdog_timer_fn+0x1ae/0x210 Feb 17 02:38:07 Telcontar kernel: ? __pfx_watchdog_timer_fn+0x10/0x10 Feb 17 02:38:07 Telcontar kernel: ? __hrtimer_run_queues+0x111/0x280 Feb 17 02:38:07 Telcontar kernel: ? hrtimer_interrupt+0xe5/0x250 Feb 17 02:38:07 Telcontar kernel: ? __sysvec_apic_timer_interrupt+0x5a/0x120 Feb 17 02:38:07 Telcontar kernel: ? sysvec_apic_timer_interrupt+0x4b/0x90 Feb 17 02:38:07 Telcontar kernel: </IRQ> Feb 17 02:38:07 Telcontar kernel: <TASK> Feb 17 02:38:07 Telcontar kernel: ? asm_sysvec_apic_timer_interrupt+0x16/0x20 Feb 17 02:38:07 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 02:38:07 Telcontar kernel: _raw_spin_lock+0x25/0x30 Feb 17 02:38:07 Telcontar kernel: inode_switch_wbs_work_fn+0x647/0x770 Feb 17 02:38:07 Telcontar kernel: ? __schedule+0x389/0x1540 Feb 17 02:38:07 Telcontar kernel: process_one_work+0x226/0x460 Feb 17 02:38:07 Telcontar kernel: worker_thread+0x2a/0x3b0 Feb 17 02:38:07 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 02:38:07 Telcontar kernel: kthread+0xe1/0x120 Feb 17 02:38:07 Telcontar kernel: ? __pfx_kthread+0x10/0x10 Feb 17 02:38:07 Telcontar kernel: ret_from_fork+0x2c/0x50 Feb 17 02:38:07 Telcontar kernel: </TASK> Feb 17 02:38:07 Telcontar kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 3-.... } 19075 jiffies s: 5005 root: 0x1/. Feb 17 02:38:07 Telcontar kernel: rcu: blocking rcu_node structures (internal RCU debug): l=1:0-15:0x8/. Feb 17 02:38:07 Telcontar kernel: Sending NMI from CPU 9 to CPUs 3: Feb 17 02:38:07 Telcontar kernel: NMI backtrace for cpu 3 Feb 17 02:38:07 Telcontar kernel: CPU: 3 PID: 19295 Comm: kworker/u64:4 Tainted: G W OEL n 6.4.0-150600.23.38-default #1 SLE15-SP6 46e958e1e6a4044cfee7b3413eeabfe5a22d6494 Feb 17 02:38:07 Telcontar kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.40 11/06/2019 Feb 17 02:38:07 Telcontar kernel: Workqueue: writeback wb_workfn (flush-259:0) Feb 17 02:38:07 Telcontar kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 02:38:07 Telcontar kernel: Code: c1 ea 12 83 e0 03 83 ea 01 48 c1 e0 05 48 63 d2 48 05 00 6f 03 00 48 03 04 d5 60 1c ec bc 48 89 18 8b 43 08 85 c0 75 09 f3 90 <8b> 43 08 85 c0 74 f7 48 8b 13 48 85 d2 74 94 0f 0d 0a eb 8f b9 01 Feb 17 02:38:07 Telcontar kernel: RSP: 0018:ffffabe56315fad0 EFLAGS: 00000246 Feb 17 02:38:07 Telcontar kernel: RAX: 0000000000000000 RBX: ffff91215e1b6f00 RCX: 0000000000000000 Feb 17 02:38:07 Telcontar kernel: RDX: 0000000000000008 RSI: 0000000000240000 RDI: ffff911361408458 Feb 17 02:38:07 Telcontar kernel: RBP: ffff911361408458 R08: ffff911361408428 R09: 00000000000006c5 Feb 17 02:38:07 Telcontar kernel: R10: ffffabe54b5afb88 R11: 000000000000004b R12: 0000000000100000 Feb 17 02:38:07 Telcontar kernel: R13: 0000000000100000 R14: ffffabe56315fb50 R15: 000000010124576b Feb 17 02:38:07 Telcontar kernel: FS: 0000000000000000(0000) GS:ffff91215e180000(0000) knlGS:0000000000000000 Feb 17 02:38:07 Telcontar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 02:38:07 Telcontar kernel: CR2: 000003418b86f000 CR3: 0000000146382000 CR4: 0000000000350ee0 Feb 17 02:38:07 Telcontar kernel: Call Trace: Feb 17 02:38:07 Telcontar kernel: <NMI> Feb 17 02:38:07 Telcontar kernel: ? nmi_cpu_backtrace+0x8d/0x100 Feb 17 02:38:07 Telcontar kernel: ? nmi_cpu_backtrace_handler+0xd/0x20 Feb 17 02:38:07 Telcontar kernel: ? nmi_handle+0x68/0x150 Feb 17 02:38:07 Telcontar kernel: ? default_do_nmi+0x49/0x100 Feb 17 02:38:07 Telcontar kernel: ? exc_nmi+0x1ca/0x270 Feb 17 02:38:07 Telcontar kernel: ? end_repeat_nmi+0x16/0x67 Feb 17 02:38:07 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 02:38:07 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 02:38:07 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x292/0x2c0 Feb 17 02:38:07 Telcontar kernel: </NMI> Feb 17 02:38:07 Telcontar kernel: <TASK> Feb 17 02:38:07 Telcontar kernel: _raw_spin_lock+0x25/0x30 Feb 17 02:38:07 Telcontar kernel: __wb_update_bandwidth+0x3c/0x1c0 Feb 17 02:38:07 Telcontar kernel: wb_update_bandwidth+0x4e/0x70 Feb 17 02:38:07 Telcontar kernel: do_writepages+0x18e/0x1b0 Feb 17 02:38:07 Telcontar kernel: ? native_queued_spin_lock_slowpath+0x235/0x2c0 Feb 17 02:38:07 Telcontar kernel: __writeback_single_inode+0x41/0x350 Feb 17 02:38:07 Telcontar kernel: writeback_sb_inodes+0x1d7/0x470 Feb 17 02:38:07 Telcontar kernel: __writeback_inodes_wb+0x5f/0xd0 Feb 17 02:38:07 Telcontar kernel: wb_writeback+0x281/0x300 Feb 17 02:38:07 Telcontar kernel: wb_workfn+0x1f5/0x470 Feb 17 02:38:07 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 02:38:07 Telcontar kernel: ? __schedule+0x389/0x1540 Feb 17 02:38:07 Telcontar kernel: ? srso_return_thunk+0x5/0x5f Feb 17 02:38:07 Telcontar kernel: process_one_work+0x226/0x460 Feb 17 02:38:07 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 02:38:07 Telcontar kernel: worker_thread+0x2a/0x3b0 Feb 17 02:38:07 Telcontar kernel: ? __pfx_worker_thread+0x10/0x10 Feb 17 02:38:07 Telcontar kernel: kthread+0xe1/0x120 Feb 17 02:38:07 Telcontar kernel: ? __pfx_kthread+0x10/0x10 Feb 17 02:38:07 Telcontar kernel: ret_from_fork+0x2c/0x50 Feb 17 02:38:07 Telcontar kernel: </TASK> Feb 17 02:38:07 Telcontar kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 24s! [kworker/1:1:20190] Feb 17 02:38:07 Telcontar kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs snd_seq_dummy snd_hrtimer vmw_vsock_vmci_transport vsock vmw_vmci xt_tcpudp nf_nat_ftp nf_nat_sip nf_conntrack_ftp nf_conntrack_sip nf_conntrack_netbios_ns nf_conntrack_broadcast nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 n> Feb 17 02:38:41 Telcontar systemd-journald[25160]: Journal stopped - -- Cheers Carlos E. R. (from openSUSE Leap 15.6 at Legolas) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZ7KZYhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVXzUAn1T3LD9i4/zMMhbNgS3O EBQ4yavQAJ9o+5a0uzIoEOZTS4oh46c4ICJOiQ== =kIsD -----END PGP SIGNATURE-----

2 3

Screen no longer blanking - Leap 15.6 KDE
by James Knott 10 Mar '25

10 Mar '25

For some reason my screen no longer blanks after a period of inactivity. Screen Energy Saving is enabled to switch off after 15 minutes. This worked until recently and there were some recent updates. Has anyone else experienced this? tnx jk

4 19

[oS-en] I need to purge the journal for a bugzilla
by Carlos E. R. 05 Mar '25

05 Mar '25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I need to purge the output from journalctl before posting it in a bugzilla. I want to remove mail and news entries. News entries add up to megabytes, and mail is private. I do: journalctl --boot=-2 | grep -v "texpire\[" | grep -v "fetchnews\[" > journal_nonews But this doesn't work on multiline reports like these: Feb 18 12:32:00 Telcontar fetchnews[15388]: sent ARTICLE 321110 command, in pipe: 2 Feb 18 12:32:00 Telcontar fetchnews[15388]: sent ARTICLE 321111 command, in pipe: 3 Feb 18 12:32:00 Telcontar fetchnews[15388]: store: try filters on header "Path: uni-berlin.de!fu-berlin.de!eternal-september.org!feeder3.eternal-september.org!news.et> From: Boris <Boris(a)invalid.invalid> Newsgroups: alt.comp.hardware Subject: Re: How Do SSDs Wear Out? Date: Tue, 18 Feb 2025 01:42:22 -0000 (UTC) Organization: A noiseless patient Spider Lines: 213 Message-ID: <XnsB289B41E2295ABorisinvalidinvalid(a)135.181.20.170> References: <XnsB285DDB4AC76FBorisinvalidinvalid(a)135.181.20.170> <vomtr3$3cnqe$1(a)dont-email.me> Injection-Date: Tue, 18 Feb 2025 02:42:23 +0100 (CET) Injection-Info: dont-email.me; posting-host="c64b607c5d3255373c7670fad39a075e"; logging-data="1481251"; mail-compla> User-Agent: Xnews/2006.08.24 Cancel-Lock: sha1:mPni5aIW+7kzN+kq1TNpc4DGcSg= Xref: uni-berlin.de alt.comp.hardware:321109 " Feb 18 12:32:00 Telcontar fetchnews[15388]: killfilter: trying filter for .* Feb 18 12:32:00 Telcontar fetchnews[15388]: pcre filter: /^From:.*APKr@domein\.nl.*/ did not match How can I remove an entire "facility" from journalctl? I did not find that in the manual. I see how to include a facility, but not how to remove one. Or, a grep recipe that cleans a multiline entry. I would use the syslog instead, which is already filtered, but it appears that the syslog doesn't contain all boot and kernel messages. I googled. Found <https://askubuntu.com/questions/1464751/telling-journalctl-to-show-all-but-…> where it seems the way is to do: journalctl --facility=kern,user,mail,....,local7 listing all facilities except mail and news. So I try: journalctl --boot=-2 --facility=auth,authpriv,cron,daemon,ftp,kern,local0,local1,local2,local3,local4,local5,local6,local7,lpr,mail,news,syslog,user,uucp > journal_purged and compare to the output from: journalctl --boot=-2 I get: -rw-r--r-- 1 cer users 23299642 Feb 26 12:34 journal_all -rw-r--r-- 1 cer users 18743605 Feb 26 13:02 journal_purged Both files should be the same, but they are not. Am I missing some facility? I use "meld" to find out the differences. Lines like this are missing: Feb 18 12:17:58 Telcontar sddm[2599]: Initializing... That's fac 1. kern? -rw-r--r-- 1 cer users 23299642 Feb 26 12:34 journal_all -rw-r--r-- 1 cer users 18743605 Feb 26 13:12 journal_purged Still lines missing, and it is still sddm: Feb 18 12:17:58 Telcontar sddm[2599]: Initializing... Read the manual again. --facility= Filter output by syslog facility. Takes a comma-separated list of numbers or facility names. The names are the usual syslog facilities as documented in syslog(3). --facility=help may be used to display a list of known facility names and exit. Let's try. Telcontar:~ # journalctl --facility=help Available facilities: kern user mail daemon auth syslog lpr news uucp cron authpriv ftp 12 13 14 15 local0 local1 local2 local3 local4 local5 local6 local7 Telcontar:~ # So I run journalctl --boot=-2 --facility=kern,user,mail,daemon,auth,syslog,lpr,news,uucp,cron,authpriv,ftp,12,13,14,15,local0,local1,local2,local3,local4,local5,local6,local7 > journal_purged Sigh. Still parts are missing: -rw-r--r-- 1 cer users 23299642 Feb 26 12:34 journal_all -rw-r--r-- 1 cer users 18743605 Feb 26 13:20 journal_purged It is still the sddm entries missing. I know it is fac=1 by comparison with my syslog: <1.4> 2025-02-24T01:03:30.963177+01:00 Telcontar sddm 2599 - - Signal received: SIGTERM *..... I print the <fac.prio> numbers. I will have to report with megabytes missing, from those unknown entries. Must be a bug with journalctl. Removing mail and news makes a difference in size: -rw-r--r-- 1 cer users 23299642 Feb 26 12:34 journal_all -rw-r--r-- 1 cer users 3777192 Feb 26 13:24 journal_purged But there are also those unknown entries, also megabytes lost. - -- Cheers Carlos E. R. (from 15.6 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZ78L/Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVoLcAni8/2Z/Qf+YbtY1uUrrn Hg8clOdzAJ9hE86ZjY0vH2+QrTAPvc3R60c6Cg== =AguY -----END PGP SIGNATURE-----

3 10

[oS-EN] ffmpeg versions
by Carlos E. R. 03 Mar '25

03 Mar '25

Hi, I suddenly noticed there are several versions of ffmpeg available. I have "ffmpeg-3" installed, but I see "ffmpeg-4", "ffmpeg-6", and "ffmpeg-7". What are the main differences, should I update to the latest, or is it a devel version? I am quite confused. -- Cheers / Saludos, Carlos E. R. (from Telcontar, using openSUSE Leap 15.6)

3 17

TW - How to fix display-manager so starting doesn't move tty1 to tty2 and put syslog on tty1?
by David C. Rankin 01 Mar '25

01 Mar '25

All, Devs, I'm currently booting to multi-user target due to the i915 issue on this box. I needed to start icewm, but using startx calling icewm-session in .xinitrc didn't fully set the environment for icewm. So I started the display-manager and then started icewm. (I needed it because there is no yast-firewall in the text based yast) When you start display-manager, your login on tty1 is moved to tty2 and syslog is displayed on tty1, lightdm/X is on vt7. When done in icewm, I need to stop the display-manager to prevent the box from rebooting when dpms is triggered by lightdm. When I stop display-manager (lightdm), the changes to the virtual terminals made be display-manager onstart and not undone and you are left with syslog scrolling on tty1 (vt1) and your session that was on tty1 now on tty2. (1) How can I tell display-manager on start to leave vt1 alone and don't put the syslog there (it used to always be on vt12) and leave my active login on tty1 alone and don't move it to tty2? This should be configurable in some way. Arch doesn't touch tty1/vt1 when launching display-manager. So this is some config made somewhere -- but where? -- David C. Rankin, J.D.,P.E.

2 2

In xterm "su: failed to execute /bin/bash: Permission denied" - pam_selinux.so (Ok from console)
by David C. Rankin 28 Feb '25

28 Feb '25

Devs, When running an xterm in fluxbox or icewm is su blocked? Attempting to su I get: $ su su: failed to execute /bin/bash: Permission denied When I'm running from a console or ssh into the box, su works just fine: 08:24 wizard:~> ssh niflheim Last login: Fri Feb 28 08:23:05 CST 2025 on tty1 Have a lot of fun... 08:24 niflheim:~> su [08:24 niflheim:/home/david] # This seems to be the result of /etc/pam.d/common-session including: session required pam_selinux.so close ... session required pam_selinux.so open I use the exact same config on my non-selinux Tumbleweed and that has no such pam_selinux.so and I experience no such problem there. I want to make this work and not disable selinux, because then I'm left with an entire filesystem full of extended attributes for selinux that need not be there. Or I have to disable selinux completely and do a massive 'find' over the entire filesystem and remove the 'security.selinux' extended attribute with setfattr -x security.selinux for every file and every directory in the filesystem. Not what I really want to do. Tumbleweed uses the following for common-session: # noc common-session session required pam_selinux.so close session required pam_limits.so session optional pam_systemd.so session required pam_unix.so try_first_pass session optional pam_umask.so session required pam_selinux.so open session optional pam_env.so The old Tumbleweed box that has no problems but uses apparmor so the pam_selinux.so can't cause problems. I've created a common-session-mod file that is a copy of common-session-pc and commented the pam_selinux.so entries and linked common-session -> common-session-mod. Now su works fine everywhere in an xterm, or console or vi ssh. Is there a better way to handle this or will this be okay? An moreover is the a better way for Tumbleweed to fix common-session-pc so this problem isn't encountered? It just seems like it is insane for selinux to allow su from console or ssh but deny access to /bin/bash if you try and su from an xterm?? -- David C. Rankin, J.D.,P.E.

1 1

How to move TW UEFI install off ssd1 to ssd2?
by David C. Rankin 28 Feb '25

28 Feb '25

All, I had originally bought a 1T drive and split it in half for Arch and Tumbleweed. I've installed both to test the i915 issue. However, It's a bit awkward having both on the same drive. So I bought another 1T ssd and want to move Tumbleweed off the drive it shares with Arch to it's own drive. I envision I can just copy the partitions to the new drive with gparted, etc.. (or dd for that matter), but what do I do about Grub UEFI? Right now, Tumbleweed took over the drive and installed grub to the base of the drive and added a boot manager entry booting from \EFI\opensuse\shim.efi. This is the part I'm unclear on. If I copy the partitions to the new drive, then how best to remove grub from drive 1 and activate Tumbleweed booting from drive 2? My preference would be to remove grub entirely and just use the bios boot menu to select the EFIstub to boot. Currently efibootmgr shows the 8th entry being: Boot0008 opensuse-secureboot HD(4...blah...)/File(\EFI\opensuse\shim.efi) Is it just a matter of deleting that entry and creating a new one with the new drive information? What about the "secureboot" part of it? Does efibootmgr handle that in a straight forward manner, or is there something additional required? -- David C. Rankin, J.D.,P.E.

2 1

New TW - How to stop selinux from change all dir permission back? And sshd not open after install (explicitly changed)
by David C. Rankin 28 Feb '25

28 Feb '25

All, devs, New TW install today. Three issues: (1) when I change /usr/local with: chown -R :devs * chmod -R 0775 * on next reboot all the permissions are changed back to root:root 0755. How do I tell selinux to stop that? (2) During install I explicitly toggled sshd (disabled) firewall (closed) to 'enabled' and 'open'. The system came up without ssh added to any zone in the firewall. It was blocked and trying to access the box you get: $ ssh niflheim ssh: connect to host niflheim port 22: No route to host The firewall simply needed opening. Why didn't the installer do that? (3) With the HP ProOne 600 (i5-8500 Gen 9.5 graphics) box, the installer wiped out /sys/class/backlight/intel_backlight/brightness setting brightness to 0 for the install (you could still barely see it). Why would this happen? systemd has a brightness restoration service. Is this what it does the first time it doesn't have a saved value to restore? The max_brightness on this box is 120000. So if the installer is setting a default 15 (for the normal 0-20 type install), then that is basically off for this box. other note: Box still suffers the same "failed to probe LSPCON" error on boot and the resulting mess causes the Gen 9.5 intel graphics box to reboot every time any type of dpms standby/poweroff is triggered on the display - that's for another bug report. Let me know on 1,2,3 if you have additional info, thanks. -- David C. Rankin, J.D.,P.E.

2 7

Re: TW - How to fix display-manager so starting doesn't move tty1 to tty2 and put syslog on tty1?
by David C. Rankin 28 Feb '25

28 Feb '25

On 2/27/25 9:54 AM, paka wrote: > ** > I use sddm and do not experience your problem ??? > Wait a minute... So you can boot to multi-user (runlevel 3), then start sddm, do whatever, then stop sddm and be back in multi-user without any change to the Tumbleweed order of tty1-tty6 and vt7? That would be much different that what I see with lightdm. I haven't installed kdm yet, waiting on this i915 issue, but I can't image it doing anything different. The big issue is I disable dpms $ xset -dpms and verify with: $ xset q but with lightDM, it enables dpms regardless, and even though I have dpms disabled, lightDM still triggers display poweroff after inactivity causing this box to reboot (even in the middle of installing packages or updates) Runs forever in multi-user without issue. Runs forever in windows (months between patch Tuesday updates, being used 10 hours a day constantly), never any problems. But kernel 6.13 and dpms with this completely vanilla business-class HP ProOne 600 box, triggers a reboot every time dpms triggers a display powerdown... fun... -- David C. Rankin, J.D.,P.E.

1 0

Console screensaver - basically zero load (Goofy screensaver)
by David C. Rankin 27 Feb '25

27 Feb '25

All, Faced with a box with i915 Gen 9.5 graphics that cannot probe lspcon on boot it is left unable to run any dpms. That means no console-blanking and no X. So needing a way to prevent the cursor blinking away forever on this all-in-one HP ProOne 600 i5-8500 thing, I looked at the traditional console screen savers like cmatrix (still great looking but demands 10% of one core continually), all were either too processor intensive for my taste or had unwanted dependencies like pip, etc.. Long story short I wanted to see what could be whipped up in a half-hour or so that would change each character cell on the screen at least ever 2-3 minutes. ANSI escapes to the rescue. I came up with a small bash script that paints (erases) random lines with background colors, then erases partial random lines, bounces a 5-chracter shaded string around the screen (like a pool ball bounding off the rails) and then randomly erases blocks of the screen from cursor to the beginning or cursor to end. We will call it Rankin's Goofy Screensaver for Console. You can simply run it in an xterm too. It automatically grabs the terminal (or xterm) size using tput and then goes into its little routine that loops every 2-3 minutes. 'Q' or 'q' quits. https://paste.opensuse.org/ebef40749b02 Give it go, if for nothing else to see what can be whipped up in a few minutes in shell and runs with basically zero-load (0.3% on one core intermittently). Much better than a constant 10% :) -- David C. Rankin, J.D.,P.E.

3 3