Created attachment 274437 [details] dmesg output on 4.16 RC2 Hello, I’m experiencing a bug, introduced with 4.15.4, which does block my system after a write attempt on my backup HDD, formatted in ext4. I can reproduce this on 4.15.5 too. It is still present on 4.16 RC2 but there it seems to only block applications accessing the drive, not all SATA I/O (but I’m not quite sure). In the attached log you’ll find a dmesg output, partition mount starts at line 1117, soon later, a write attempt is made. Just reading couldn’t trigger the issue in my tests.
This looks like it's a SCSI issue. The first soft lockup complaint is: [ 246.760015] INFO: task kworker/u16:2:220 blocked for more than 120 seconds. [ 246.760020] Tainted: G W 4.16.0-1-mainline #1 [ 246.760021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 246.760023] kworker/u16:2 D 0 220 2 0x80000000 [ 246.760029] Workqueue: events_freezable_power_ disk_events_workfn [ 246.760031] Call Trace: [ 246.760037] ? __schedule+0x24b/0x8a0 [ 246.760039] ? __clear_rsb+0x15/0x3d [ 246.760042] ? preempt_count_add+0x68/0xa0 [ 246.760046] schedule+0x32/0x90 [ 246.760056] scsi_block_when_processing_errors+0x4a/0x100 [scsi_mod] [ 246.760059] ? wait_woken+0x80/0x80 [ 246.760063] sd_check_events+0x75/0x1a0 [sd_mod] [ 246.760069] disk_check_events+0x69/0x150 [ 246.760072] process_one_work+0x1ce/0x3f0 [ 246.760074] worker_thread+0x2b/0x3d0 [ 246.760076] ? process_one_work+0x3f0/0x3f0 [ 246.760078] kthread+0x113/0x130 [ 246.760079] ? kthread_create_on_node+0x70/0x70 [ 246.760081] ret_from_fork+0x22/0x40 Before that there is a RCU warning which might or might not be related: [ 82.065830] WARNING: CPU: 6 PID: 54 at kernel/rcu/tree.c:2713 rcu_do_batch.isra.29+0x231/0x250 [ 82.065833] Modules linked in: tun cmac rfcomm input_leds joydev led_class bnep it87 hwmon_vid btusb btrtl btbcm btintel bluetooth amdkfd amd_iommu_v2 ecdh_generic nls_iso8859_1 cdc_acm rfkill nls_cp437 vfat fat amdgpu edac_mce_amd mousedev ext4 kvm_amd ccp crc16 mbcache mxm_wmi jbd2 kvm fscrypto snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi irqbypass crct10dif_pclmul chash gpu_sched ghash_clmulni_intel ttm snd_hda_intel pcbc snd_hda_codec drm_kms_helper snd_hda_core aesni_intel aes_x86_64 drm crypto_simd snd_hwdep glue_helper snd_pcm cryptd sp5100_tco agpgart r8169 fam15h_power snd_timer syscopyarea sysfillrect sysimgblt k10temp snd mii fb_sys_fops i2c_piix4 i2c_algo_bit soundcore evdev wmi shpchp rtc_cmos acpi_cpufreq mac_hid sch_fq_codel ecryptfs cbc encrypted_keys trusted tpm [ 82.065935] rng_core sg crypto_user ip_tables x_tables hid_generic usbhid hid btrfs xor zstd_decompress zstd_compress xxhash raid6_pq sr_mod cdrom sd_mod ohci_pci ahci xhci_pci ehci_pci libahci firewire_ohci xhci_hcd ehci_hcd ohci_hcd libata firewire_core crc_itu_t usbcore scsi_mod usb_common crc32_pclmul libcrc32c crc32c_generic crc32c_intel [ 82.065984] CPU: 6 PID: 54 Comm: rcuc/6 Not tainted 4.16.0-1-mainline #1 [ 82.065986] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS F3i 10/07/2014 [ 82.065992] RIP: 0010:rcu_do_batch.isra.29+0x231/0x250 [ 82.065994] RSP: 0018:ffffac3f41a8fe50 EFLAGS: 00010002 [ 82.065997] RAX: ffffffffffffd800 RBX: ffff8a28beda24c0 RCX: 0000000100200001 [ 82.065999] RDX: 0000000000000006 RSI: ffffac3f41a8fe50 RDI: ffff8a28beda24f8 [ 82.066004] RBP: ffff8a28beda24f8 R08: 0000000000000001 R09: ffffffff860efe39 [ 82.066006] R10: ffffac3f41a97e30 R11: 0000000000000001 R12: 0000000000000246 [ 82.066008] R13: ffffffff87052410 R14: ffffffffffffffff R15: ffffffff8609e850 [ 82.066012] FS: 0000000000000000(0000) GS:ffff8a28bed80000(0000) knlGS:0000000000000000 [ 82.066014] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 82.066019] CR2: 00007f6674e81000 CR3: 00000003cfb8e000 CR4: 00000000000406e0 [ 82.066022] Call Trace: [ 82.066033] ? rcu_cpu_kthread+0x49/0x2d0 [ 82.066039] ? sort_range+0x20/0x20 [ 82.066044] rcu_cpu_kthread+0x10d/0x2d0 [ 82.066050] ? sort_range+0x20/0x20 [ 82.066062] smpboot_thread_fn+0x19e/0x240 [ 82.066064] kthread+0x113/0x130 [ 82.066065] ? kthread_create_on_node+0x70/0x70 [ 82.066067] ret_from_fork+0x22/0x40 [ 82.066069] Code: 48 83 6c 24 18 01 e9 e8 fe ff ff 48 3b 15 50 25 f6 00 0f 8f 6b ff ff ff 48 8b 05 53 25 f6 00 48 89 83 b0 00 00 00 e9 58 ff ff ff <0f> 0b eb 8d 0f 0b e9 65 fe ff ff e8 7f b3 f8 ff 0f 1f 44 00 00 [ 82.066091] ---[ end trace e53b91b9c6245d1c ]--- Since this reliably reproduces for you with 4.15.4, if 4.15.3 was the last good version, I'd suggest doing a kernel bisection to see if you can isolate the commit which introduced the regression.
Created attachment 274471 [details] similar issue but upon writing to an ntfs volume I am experiencing similar issues recently when rhythmbox(a pod catcher) is trying to write a downloaded mp3 file to an ntfs volume. System is not fully blocked though, only all further access attempts to that ntfs volume fail during that session and upon shutdown, the system waits for Disk Manager for more than 10 minutes (did not wait much longer and did a hard reset). for dmesg output, see attachment
(In reply to Dennis Busch from comment #2) > Created attachment 274471 [details] > similar issue but upon writing to an ntfs volume > > I am experiencing similar issues recently when rhythmbox(a pod catcher) is > trying to write a downloaded mp3 file to an ntfs volume. System is not fully > blocked though, only all further access attempts to that ntfs volume fail > during that session and upon shutdown, the system waits for Disk Manager for > more than 10 minutes (did not wait much longer and did a hard reset). > > for dmesg output, see attachment possibly related to: https://bugzilla.kernel.org/show_bug.cgi?id=198861
Thanks Dennis, no problems anymore with Linux 4.15.7 and 4.16 RC3, the patches seem to have fixed this. Lucky me, no bisecting! Out of curiosity: Why does my log talk about SCSI in the first place although my disk is connected via SATA?
What a pity, after 30 min, the block came up again. Sorry! In my previous tests, it was coming rather immediately.
The bug report I linked to in comment 3 mentioned two patches ( https://patchwork.kernel.org/patch/10181165/ and https://patchwork.kernel.org/patch/10233617/ ) but neither of those appears to have been applied. I would stick to the last working kernel version for now (for me that is 4.14.19 as mentioned in that other bug report) and keep an eye on https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/ to see if anything familiar looking pops up which suggests that this particular problem was fixed ( maybe it already was but I am unable to determine for sure as I do not fully understand the issue, just have a hunch the problem is/was a locking issue in the RCU system ).
I think I'm getting similar or this same problem on ArchLinux with 4.15.7 kernel. Trying to read one file on BTRFS partition on a HDD which has unreadable sector causes kernel to lockup and I have to restart PC. dmesg [ 2253.091452] WARNING: CPU: 5 PID: 47 at kernel/rcu/tree.c:2792 rcu_do_batch.isra.28+0x231/0x250 [ 2253.091455] Modules linked in: nls_iso8859_4 nls_cp775 cfg80211 rfkill devlink nf_conntrack_netbios_ns nf_conntrack_broadcast xt_tcpudp xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables bridge stp llc iptable_filter it87 hwmon_vid saa7134_alsa saa7134 edac_mce_amd kvm_amd tveeprom v4l2_common videobuf2_dma_sg kvm videobuf2_memops snd_hda_codec_hdmi irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel [ 2253.091504] videobuf2_v4l2 snd_hda_intel pcbc raid456 async_raid6_recov async_memcpy libcrc32c async_pq async_xor async_tx aesni_intel snd_hda_codec videobuf2_core r8169 snd_hda_core md_mod snd_hwdep mxm_wmi aes_x86_64 snd_pcm wmi_bmof crypto_simd glue_helper snd_timer cryptd fam15h_power k10temp snd videodev pcspkr mii media rc_core sp5100_tco evdev i2c_piix4 soundcore wmi mac_hid shpchp rtc_cmos acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc sg crypto_user nvidia_uvm(PO) btrfs xor zstd_decompress zstd_compress xxhash raid6_pq sd_mod nvidia_drm(PO) nvidia_modeset(PO) ohci_pci ata_generic pata_acpi nvidia(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops firewire_ohci firewire_core xhci_pci crc_itu_t drm pata_atiixp ehci_pci xhci_hcd ahci ehci_hcd ohci_hcd libahci agpgart [ 2253.091572] ipmi_devintf usbcore ipmi_msghandler usb_common mvsas libsas scsi_transport_sas libata scsi_mod crc32c_generic crc32c_intel vfat fat ip_tables x_tables [ 2253.091587] CPU: 5 PID: 47 Comm: rcuc/5 Tainted: P O 4.15.7-1-ARCH #1 [ 2253.091589] Hardware name: Gigabyte Technology Co., Ltd. GA-990FXA-UD3/GA-990FXA-UD3, BIOS FFe 11/08/2013 [ 2253.091593] RIP: 0010:rcu_do_batch.isra.28+0x231/0x250 [ 2253.091595] RSP: 0018:ffffa8fe432efe50 EFLAGS: 00010002 [ 2253.091597] RAX: ffffffffffffd800 RBX: ffff9e1f2ed62380 RCX: 000000000b955e01 [ 2253.091599] RDX: 0000000000000005 RSI: ffffa8fe432efe50 RDI: ffff9e1f2ed623b8 [ 2253.091600] RBP: ffff9e1f2ed623b8 R08: 00002adf10e20800 R09: ffffffffb70ee1f9 [ 2253.091602] R10: ffffedcb8ed99000 R11: 00000000ffffff80 R12: 0000000000000246 [ 2253.091603] R13: ffffffffb8054250 R14: fffffffffffffeac R15: ffff9e1f128a3c80 [ 2253.091606] FS: 0000000000000000(0000) GS:ffff9e1f2ed40000(0000) knlGS:0000000000000000 [ 2253.091607] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2253.091609] CR2: 00007f24768d8010 CR3: 000000053a1f8000 CR4: 00000000000406e0 [ 2253.091611] Call Trace: [ 2253.091619] ? rcu_cpu_kthread+0x49/0x2d0 [ 2253.091623] ? sort_range+0x20/0x20 [ 2253.091626] rcu_cpu_kthread+0x10d/0x2d0 [ 2253.091629] ? sort_range+0x20/0x20 [ 2253.091632] smpboot_thread_fn+0x19e/0x240 [ 2253.091635] kthread+0x113/0x130 [ 2253.091638] ? kthread_create_on_node+0x70/0x70 [ 2253.091642] ret_from_fork+0x22/0x40 [ 2253.091645] Code: 48 83 6c 24 18 01 e9 e8 fe ff ff 48 3b 15 d0 5f f6 00 0f 8f 6b ff ff ff 48 8b 05 d3 5f f6 00 48 89 83 b0 00 00 00 e9 58 ff ff ff <0f> 0b eb 8d 0f 0b e9 65 fe ff ff e8 8f cc f8 ff 0f 1f 44 00 00 [ 2253.091692] ---[ end trace 43c301635fb3a898 ]--- [ 2458.658915] INFO: task btrfs-transacti:353 blocked for more than 120 seconds. [ 2458.658990] Tainted: P W O 4.15.7-1-ARCH #1 [ 2458.659046] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2458.659115] btrfs-transacti D 0 353 2 0x80000000 [ 2458.659121] Call Trace: [ 2458.659136] ? __schedule+0x24b/0x8c0 [ 2458.659142] ? percpu_counter_add_batch+0x7e/0xb0 [ 2458.659148] schedule+0x32/0x90 [ 2458.659154] io_schedule+0x12/0x40 [ 2458.659160] wait_on_page_bit+0xea/0x130 [ 2458.659166] ? add_to_page_cache_lru+0xe0/0xe0 [ 2458.659172] __filemap_fdatawait_range+0xbf/0x110 [ 2458.659180] filemap_fdatawait_range+0xe/0x20 [ 2458.659231] btrfs_wait_ordered_range+0x68/0x100 [btrfs] [ 2458.659275] __btrfs_wait_cache_io+0x42/0x1b0 [btrfs] [ 2458.659311] btrfs_start_dirty_block_groups+0x1a2/0x470 [btrfs] [ 2458.659351] btrfs_commit_transaction+0x117/0x930 [btrfs] [ 2458.659389] ? start_transaction+0x9e/0x420 [btrfs] [ 2458.659426] transaction_kthread+0x17b/0x1a0 [btrfs] [ 2458.659463] ? btrfs_cleanup_transaction+0x570/0x570 [btrfs] [ 2458.659467] kthread+0x113/0x130 [ 2458.659471] ? kthread_create_on_node+0x70/0x70 [ 2458.659475] ? do_syscall_64+0x74/0x190 [ 2458.659481] ? SyS_exit_group+0x10/0x10 [ 2458.659484] ret_from_fork+0x22/0x40 [ 2458.659495] INFO: task systemd-journal:410 blocked for more than 120 seconds. [ 2458.659559] Tainted: P W O 4.15.7-1-ARCH #1 [ 2458.659611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2458.659679] systemd-journal D 0 410 1 0x00000104 [ 2458.659683] Call Trace: [ 2458.659689] ? __schedule+0x24b/0x8c0 [ 2458.659695] ? bit_wait+0x50/0x50 [ 2458.659699] schedule+0x32/0x90 [ 2458.659703] io_schedule+0x12/0x40 [ 2458.659707] bit_wait_io+0xd/0x50 [ 2458.659712] __wait_on_bit+0x44/0x80 [ 2458.659718] ? submit_bio+0x6c/0x140 [ 2458.659722] out_of_line_wait_on_bit+0x91/0xb0 [ 2458.659727] ? bit_waitqueue+0x30/0x30 [ 2458.659763] write_all_supers+0x3b6/0xa80 [btrfs] [ 2458.659792] ? _raw_spin_lock_irq+0x1a/0x40 [ 2458.659835] ? btrfs_sync_log+0x7b7/0xaf0 [btrfs] [ 2458.659876] btrfs_sync_log+0x7b7/0xaf0 [btrfs] [ 2458.659919] ? btrfs_sync_file+0x32e/0x440 [btrfs] [ 2458.659958] btrfs_sync_file+0x32e/0x440 [btrfs] [ 2458.659965] do_fsync+0x38/0x60 [ 2458.659969] SyS_fsync+0xc/0x10 [ 2458.659973] do_syscall_64+0x74/0x190 [ 2458.659978] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 2458.659982] RIP: 0033:0x7f24764c90ec [ 2458.659984] RSP: 002b:00007ffc11e7e3e0 EFLAGS: 00000293 ORIG_RAX: 000000000000004a [ 2458.659988] RAX: ffffffffffffffda RBX: 000055a735604850 RCX: 00007f24764c90ec [ 2458.659991] RDX: 0000000000000000 RSI: 000055a735603960 RDI: 0000000000000026 [ 2458.659993] RBP: 0000000000000001 R08: 00000000000000ca R09: 00007f2470a3f9d0 [ 2458.659995] R10: 0000000000000000 R11: 0000000000000293 R12: 00007ffc11e7e540 [ 2458.659997] R13: 00007ffc11e7e538 R14: 000055a735604850 R15: 00007ffc11e7e6a8 [ 2458.660015] INFO: task WTJourn.Flusher:1149 blocked for more than 120 seconds. [ 2458.660081] Tainted: P W O 4.15.7-1-ARCH #1 [ 2458.660132] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2458.660200] WTJourn.Flusher D 0 1149 1 0x00000000 [ 2458.660204] Call Trace: [ 2458.660210] ? __schedule+0x24b/0x8c0 [ 2458.660215] ? preempt_count_add+0x68/0xa0 [ 2458.660220] schedule+0x32/0x90 [ 2458.660261] wait_ordered_extents.isra.3.constprop.7+0x337/0x3b0 [btrfs] [ 2458.660267] ? wait_woken+0x80/0x80 [ 2458.660309] btrfs_log_changed_extents+0x256/0x610 [btrfs] [ 2458.660351] ? fill_inode_item.isra.2+0x22f/0x290 [btrfs] [ 2458.660392] btrfs_log_inode+0x9ba/0xf60 [btrfs] [ 2458.660432] ? btrfs_submit_bio_hook+0x8e/0x180 [btrfs] [ 2458.660475] btrfs_log_inode_parent+0x27f/0xa40 [btrfs] [ 2458.660482] ? preempt_count_add+0x68/0xa0 [ 2458.660485] ? _raw_spin_lock+0x13/0x40 [ 2458.660488] ? preempt_count_add+0x68/0xa0 [ 2458.660491] ? _raw_spin_lock+0x13/0x40 [ 2458.660531] btrfs_log_dentry_safe+0x58/0x80 [btrfs] [ 2458.660572] btrfs_sync_file+0x2eb/0x440 [btrfs] [ 2458.660578] do_fsync+0x38/0x60 [ 2458.660582] SyS_fdatasync+0xf/0x20 [ 2458.660586] do_syscall_64+0x74/0x190 [ 2458.660590] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 2458.660593] RIP: 0033:0x7fa5ba08da7c [ 2458.660596] RSP: 002b:00007fa5b32dc710 EFLAGS: 00000293 ORIG_RAX: 000000000000004b [ 2458.660599] RAX: ffffffffffffffda RBX: 0000000000000010 RCX: 00007fa5ba08da7c [ 2458.660602] RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000000000000010 [ 2458.660604] RBP: 000000000000000a R08: 0000000000000020 R09: 0000000000000010 [ 2458.660606] R10: 6769546465726957 R11: 0000000000000293 R12: 0000000000000001 [ 2458.660608] R13: 000055e6352ab2f0 R14: 000055e635208480 R15: 00007fa5bcc5b6a7 [ 2458.660631] INFO: task netdata:1301 blocked for more than 120 seconds. [ 2458.660690] Tainted: P W O 4.15.7-1-ARCH #1 [ 2458.660741] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2458.660819] netdata D 0 1301 1 0x00000000 [ 2458.660823] Call Trace: [ 2458.660830] ? __schedule+0x24b/0x8c0 [ 2458.660835] schedule+0x32/0x90 [ 2458.660839] schedule_preempt_disabled+0x14/0x20 [ 2458.660844] __mutex_lock.isra.0+0x274/0x520 [ 2458.660877] ? btrfs_show_devname+0x28/0xf0 [btrfs] [ 2458.660907] btrfs_show_devname+0x28/0xf0 [btrfs] [ 2458.660913] show_mountinfo+0x1a2/0x290 [ 2458.660918] seq_read+0x371/0x480 [ 2458.660925] __vfs_read+0x36/0x170 [ 2458.660932] vfs_read+0x91/0x130 [ 2458.660937] SyS_read+0x52/0xc0 [ 2458.660942] do_syscall_64+0x74/0x190 [ 2458.660947] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 2458.660949] RIP: 0033:0x7fac0c978988 [ 2458.660952] RSP: 002b:00007fac0a564c90 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 [ 2458.660956] RAX: ffffffffffffffda RBX: 000055dff2ac3ec0 RCX: 00007fac0c978988 [ 2458.660958] RDX: 0000000000000200 RSI: 000055dff2ac3ec0 RDI: 0000000000000027 [ 2458.660960] RBP: 0000000000000200 R08: 0000000000000000 R09: 00000000000040b0 [ 2458.660962] R10: 000055dff2062840 R11: 0000000000000246 R12: 000000005a9ffc5b [ 2458.660964] R13: 00007fac0a565dd0 R14: 000055dff2aa6980 R15: 0000000000000001 [ 2485.422034] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating. [ 2575.674793] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 2575.674845] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 2581.542546] INFO: task btrfs-transacti:353 blocked for more than 120 seconds. [ 2581.542622] Tainted: P W O 4.15.7-1-ARCH #1 [ 2581.542675] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2581.542750] btrfs-transacti D 0 353 2 0x80000000 [ 2581.542755] Call Trace: [ 2581.542765] ? __schedule+0x24b/0x8c0 [ 2581.542770] ? percpu_counter_add_batch+0x7e/0xb0 [ 2581.542773] schedule+0x32/0x90 [ 2581.542778] io_schedule+0x12/0x40 [ 2581.542783] wait_on_page_bit+0xea/0x130 [ 2581.542787] ? add_to_page_cache_lru+0xe0/0xe0 [ 2581.542791] __filemap_fdatawait_range+0xbf/0x110 [ 2581.542796] filemap_fdatawait_range+0xe/0x20 [ 2581.542833] btrfs_wait_ordered_range+0x68/0x100 [btrfs] [ 2581.542864] __btrfs_wait_cache_io+0x42/0x1b0 [btrfs] [ 2581.542889] btrfs_start_dirty_block_groups+0x1a2/0x470 [btrfs] [ 2581.542917] btrfs_commit_transaction+0x117/0x930 [btrfs] [ 2581.542943] ? start_transaction+0x9e/0x420 [btrfs] [ 2581.542970] transaction_kthread+0x17b/0x1a0 [btrfs] [ 2581.542996] ? btrfs_cleanup_transaction+0x570/0x570 [btrfs] [ 2581.542999] kthread+0x113/0x130 [ 2581.543002] ? kthread_create_on_node+0x70/0x70 [ 2581.543005] ? do_syscall_64+0x74/0x190 [ 2581.543009] ? SyS_exit_group+0x10/0x10 [ 2581.543012] ret_from_fork+0x22/0x40 [ 2581.543019] INFO: task systemd-journal:410 blocked for more than 120 seconds. [ 2581.543065] Tainted: P W O 4.15.7-1-ARCH #1 [ 2581.543101] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2581.543148] systemd-journal D 0 410 1 0x00000104 [ 2581.543151] Call Trace: [ 2581.543156] ? __schedule+0x24b/0x8c0 [ 2581.543159] ? bit_wait+0x50/0x50 [ 2581.543162] schedule+0x32/0x90 [ 2581.543165] io_schedule+0x12/0x40 [ 2581.543168] bit_wait_io+0xd/0x50 [ 2581.543171] __wait_on_bit+0x44/0x80 [ 2581.543175] ? submit_bio+0x6c/0x140 [ 2581.543178] out_of_line_wait_on_bit+0x91/0xb0 [ 2581.543181] ? bit_waitqueue+0x30/0x30 [ 2581.543207] write_all_supers+0x3b6/0xa80 [btrfs] [ 2581.543210] ? _raw_spin_lock_irq+0x1a/0x40 [ 2581.543239] ? btrfs_sync_log+0x7b7/0xaf0 [btrfs] [ 2581.543268] btrfs_sync_log+0x7b7/0xaf0 [btrfs] [ 2581.543298] ? btrfs_sync_file+0x32e/0x440 [btrfs] [ 2581.543325] btrfs_sync_file+0x32e/0x440 [btrfs] [ 2581.543330] do_fsync+0x38/0x60 [ 2581.543333] SyS_fsync+0xc/0x10 [ 2581.543336] do_syscall_64+0x74/0x190 [ 2581.543339] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 2581.543342] RIP: 0033:0x7f24764c90ec [ 2581.543344] RSP: 002b:00007ffc11e7e3e0 EFLAGS: 00000293 ORIG_RAX: 000000000000004a [ 2581.543346] RAX: ffffffffffffffda RBX: 000055a735604850 RCX: 00007f24764c90ec [ 2581.543348] RDX: 0000000000000000 RSI: 000055a735603960 RDI: 0000000000000026 [ 2581.543350] RBP: 0000000000000001 R08: 00000000000000ca R09: 00007f2470a3f9d0 [ 2581.543351] R10: 0000000000000000 R11: 0000000000000293 R12: 00007ffc11e7e540 [ 2581.543353] R13: 00007ffc11e7e538 R14: 000055a735604850 R15: 00007ffc11e7e6a8 [ 2581.543366] INFO: task mongod:1137 blocked for more than 120 seconds. [ 2581.543407] Tainted: P W O 4.15.7-1-ARCH #1 [ 2581.543452] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2581.543501] mongod D 0 1137 1 0x00000000 [ 2581.543504] Call Trace: [ 2581.543509] ? __schedule+0x24b/0x8c0 [ 2581.543513] schedule+0x32/0x90 [ 2581.543516] rwsem_down_write_failed+0x164/0x240 [ 2581.543520] ? futex_wait+0x1c7/0x240 [ 2581.543525] ? call_rwsem_down_write_failed+0x13/0x20 [ 2581.543527] call_rwsem_down_write_failed+0x13/0x20 [ 2581.543531] down_write+0x20/0x30 [ 2581.543558] btrfs_file_write_iter+0xb6/0x650 [btrfs] [ 2581.543565] __vfs_write+0xf8/0x180 [ 2581.543570] vfs_write+0xb1/0x1a0 [ 2581.543573] SyS_pwrite64+0x90/0xb0 [ 2581.543577] do_syscall_64+0x74/0x190 [ 2581.543579] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 2581.543582] RIP: 0033:0x7fa5ba3694f3 [ 2581.543583] RSP: 002b:00007fa5b62e2880 EFLAGS: 00000293 ORIG_RAX: 0000000000000012 [ 2581.543586] RAX: ffffffffffffffda RBX: 0000000000000080 RCX: 00007fa5ba3694f3 [ 2581.543588] RDX: 0000000000000080 RSI: 000055e6370ec000 RDI: 0000000000000010 [ 2581.543589] RBP: 0000000000002300 R08: 000055e6370ec000 R09: 0000000000000884 [ 2581.543591] R10: 0000000000002300 R11: 0000000000000293 R12: 0000000000000080 [ 2581.543592] R13: 0000000040000000 R14: 000055e6351d8a00 R15: 000055e6370ec000 [ 2581.543596] INFO: task WTJourn.Flusher:1149 blocked for more than 120 seconds. [ 2581.543642] Tainted: P W O 4.15.7-1-ARCH #1 [ 2581.543677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2581.543725] WTJourn.Flusher D 0 1149 1 0x00000000 [ 2581.543727] Call Trace: [ 2581.543732] ? __schedule+0x24b/0x8c0 [ 2581.543735] ? preempt_count_add+0x68/0xa0 [ 2581.543738] schedule+0x32/0x90 [ 2581.543766] wait_ordered_extents.isra.3.constprop.7+0x337/0x3b0 [btrfs] [ 2581.543771] ? wait_woken+0x80/0x80 [ 2581.543799] btrfs_log_changed_extents+0x256/0x610 [btrfs] [ 2581.543829] ? fill_inode_item.isra.2+0x22f/0x290 [btrfs] [ 2581.543858] btrfs_log_inode+0x9ba/0xf60 [btrfs] [ 2581.543886] ? btrfs_submit_bio_hook+0x8e/0x180 [btrfs] [ 2581.543916] btrfs_log_inode_parent+0x27f/0xa40 [btrfs] [ 2581.543921] ? preempt_count_add+0x68/0xa0 [ 2581.543923] ? _raw_spin_lock+0x13/0x40 [ 2581.543925] ? preempt_count_add+0x68/0xa0 [ 2581.543927] ? _raw_spin_lock+0x13/0x40 [ 2581.543956] btrfs_log_dentry_safe+0x58/0x80 [btrfs] [ 2581.543984] btrfs_sync_file+0x2eb/0x440 [btrfs] [ 2581.543988] do_fsync+0x38/0x60 [ 2581.543991] SyS_fdatasync+0xf/0x20 [ 2581.543994] do_syscall_64+0x74/0x190 [ 2581.543997] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 2581.543999] RIP: 0033:0x7fa5ba08da7c [ 2581.544001] RSP: 002b:00007fa5b32dc710 EFLAGS: 00000293 ORIG_RAX: 000000000000004b [ 2581.544003] RAX: ffffffffffffffda RBX: 0000000000000010 RCX: 00007fa5ba08da7c [ 2581.544005] RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000000000000010 [ 2581.544006] RBP: 000000000000000a R08: 0000000000000020 R09: 0000000000000010 [ 2581.544008] R10: 6769546465726957 R11: 0000000000000293 R12: 0000000000000001 [ 2581.544009] R13: 000055e6352ab2f0 R14: 000055e635208480 R15: 00007fa5bcc5b6a7 [ 2581.544027] INFO: task netdata:1301 blocked for more than 120 seconds. [ 2581.544068] Tainted: P W O 4.15.7-1-ARCH #1 [ 2581.544104] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2581.544151] netdata D 0 1301 1 0x00000000 [ 2581.544154] Call Trace: [ 2581.544158] ? __schedule+0x24b/0x8c0 [ 2581.544162] schedule+0x32/0x90 [ 2581.544165] schedule_preempt_disabled+0x14/0x20 [ 2581.544168] __mutex_lock.isra.0+0x274/0x520 [ 2581.544190] ? btrfs_show_devname+0x28/0xf0 [btrfs] [ 2581.544211] btrfs_show_devname+0x28/0xf0 [btrfs] [ 2581.544216] show_mountinfo+0x1a2/0x290 [ 2581.544219] seq_read+0x371/0x480 [ 2581.544224] __vfs_read+0x36/0x170 [ 2581.544228] vfs_read+0x91/0x130 [ 2581.544232] SyS_read+0x52/0xc0 [ 2581.544235] do_syscall_64+0x74/0x190 [ 2581.544238] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 2581.544240] RIP: 0033:0x7fac0c978988 [ 2581.544242] RSP: 002b:00007fac0a564c90 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 [ 2581.544244] RAX: ffffffffffffffda RBX: 000055dff2ac3ec0 RCX: 00007fac0c978988 [ 2581.544246] RDX: 0000000000000200 RSI: 000055dff2ac3ec0 RDI: 0000000000000027 [ 2581.544247] RBP: 0000000000000200 R08: 0000000000000000 R09: 00000000000040b0 [ 2581.544249] R10: 000055dff2062840 R11: 0000000000000246 R12: 000000005a9ffc5b [ 2581.544250] R13: 00007fac0a565dd0 R14: 000055dff2aa6980 R15: 0000000000000001 [ 2665.927305] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 2704.426100] INFO: task btrfs-transacti:353 blocked for more than 120 seconds. [ 2704.426175] Tainted: P W O 4.15.7-1-ARCH #1 [ 2704.426228] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2704.426298] btrfs-transacti D 0 353 2 0x80000000 [ 2704.426304] Call Trace: [ 2704.426318] ? __schedule+0x24b/0x8c0 [ 2704.426323] ? percpu_counter_add_batch+0x7e/0xb0 [ 2704.426329] schedule+0x32/0x90 [ 2704.426335] io_schedule+0x12/0x40 [ 2704.426342] wait_on_page_bit+0xea/0x130 [ 2704.426348] ? add_to_page_cache_lru+0xe0/0xe0 [ 2704.426353] __filemap_fdatawait_range+0xbf/0x110 [ 2704.426360] filemap_fdatawait_range+0xe/0x20 [ 2704.426411] btrfs_wait_ordered_range+0x68/0x100 [btrfs] [ 2704.426455] __btrfs_wait_cache_io+0x42/0x1b0 [btrfs] [ 2704.426490] btrfs_start_dirty_block_groups+0x1a2/0x470 [btrfs] [ 2704.426530] btrfs_commit_transaction+0x117/0x930 [btrfs] [ 2704.426568] ? start_transaction+0x9e/0x420 [btrfs] [ 2704.426605] transaction_kthread+0x17b/0x1a0 [btrfs] [ 2704.426643] ? btrfs_cleanup_transaction+0x570/0x570 [btrfs] [ 2704.426646] kthread+0x113/0x130 [ 2704.426653] ? kthread_create_on_node+0x70/0x70 [ 2704.426657] ? do_syscall_64+0x74/0x190 [ 2704.426662] ? SyS_exit_group+0x10/0x10 [ 2704.426666] ret_from_fork+0x22/0x40 [ 2756.179973] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 2756.180023] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 2846.432363] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 2846.432373] systemd[1]: systemd-journald.service: Failed with result 'watchdog'. [ 2846.432886] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 2846.433027] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 2. [ 2846.433355] systemd[1]: Stopped Flush Journal to Persistent Storage. [ 2846.433373] systemd[1]: Stopping Flush Journal to Persistent Storage... [ 2846.433513] systemd[1]: Stopped Journal Service. [ 2846.433693] systemd[1]: systemd-journald.service: Found left-over process 410 (systemd-journal) in control group while starting unit. Ignoring. [ 2846.433698] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 2846.434983] systemd[1]: Starting Journal Service... [ 2936.684829] systemd[1]: systemd-journald.service: Start operation timed out. Terminating. [ 3026.937338] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 3026.937389] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 3026.937467] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 3117.189653] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 3207.442117] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 3207.442168] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 3207.442243] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 3297.694476] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 3297.694486] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [ 3297.694767] systemd[1]: Failed to start Journal Service. [ 3297.694867] systemd[1]: Dependency failed for Flush Journal to Persistent Storage. [ 3297.694910] systemd[1]: systemd-journal-flush.service: Job systemd-journal-flush.service/start failed with result 'dependency'. [ 3297.695487] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 3297.695550] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 3. [ 3297.695981] systemd[1]: Stopped Journal Service. [ 3297.696113] systemd[1]: systemd-journald.service: Found left-over process 410 (systemd-journal) in control group while starting unit. Ignoring. [ 3297.696117] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 3387.946813] systemd[1]: systemd-journald.service: Start operation timed out. Terminating. [ 3478.199155] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 3478.199208] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 3478.199289] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 3478.199315] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 3568.451368] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 3658.703757] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 3658.703808] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 3658.703884] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 3658.703912] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 3748.956054] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 3748.956064] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [ 3748.956341] systemd[1]: Failed to start Journal Service. [ 3748.957048] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 3748.957108] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 4. [ 3748.957516] systemd[1]: Stopped Journal Service. [ 3748.957660] systemd[1]: systemd-journald.service: Found left-over process 410 (systemd-journal) in control group while starting unit. Ignoring. [ 3748.957664] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 3748.957684] systemd[1]: systemd-journald.service: Found left-over process 7740 (systemd-journal) in control group while starting unit. Ignoring. [ 3748.957687] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 3839.208349] systemd[1]: systemd-journald.service: Start operation timed out. Terminating. [ 3929.460618] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 3929.460670] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 3929.460752] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 3929.460779] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 3929.460803] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 4019.712901] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 4109.965176] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 4109.965227] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 4109.965304] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 4109.965331] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 4109.965356] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 4200.217351] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 4200.217359] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [ 4200.217564] systemd[1]: Failed to start Journal Service. [ 4200.218152] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 4200.218211] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 5. [ 4200.218618] systemd[1]: Stopped Journal Service. [ 4200.218750] systemd[1]: systemd-journald.service: Found left-over process 410 (systemd-journal) in control group while starting unit. Ignoring. [ 4200.218754] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 4200.218774] systemd[1]: systemd-journald.service: Found left-over process 7740 (systemd-journal) in control group while starting unit. Ignoring. [ 4200.218777] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 4290.471350] systemd[1]: systemd-journald.service: Start operation timed out. Terminating. [ 4380.728501] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 4380.728553] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 4380.728636] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 4380.728662] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 4380.728687] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 4380.728711] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 4470.985109] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 4561.241050] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 4561.241103] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 4561.241183] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 4561.241209] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 4561.241234] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 4561.241258] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 4651.496495] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 4651.496506] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [ 4651.496786] systemd[1]: Failed to start Journal Service. [ 4651.497730] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 4651.497819] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 6. [ 4651.498567] systemd[1]: Stopped Journal Service. [ 4651.498797] systemd[1]: systemd-journald.service: Found left-over process 410 (systemd-journal) in control group while starting unit. Ignoring. [ 4651.498803] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 4651.498844] systemd[1]: systemd-journald.service: Found left-over process 7740 (systemd-journal) in control group while starting unit. Ignoring. [ 4651.498850] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 4741.751516] systemd[1]: systemd-journald.service: Start operation timed out. Terminating. [ 4832.006159] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 4832.006211] systemd[1]: systemd-journald.service: Killing process 7867 (systemd-journal) with signal SIGKILL. [ 4832.006295] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 4832.006321] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 4832.006347] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 4832.006371] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 4832.006399] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 4922.260517] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 5012.514693] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 5012.514745] systemd[1]: systemd-journald.service: Killing process 7867 (systemd-journal) with signal SIGKILL. [ 5012.514827] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 5012.514853] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 5012.514878] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 5012.514901] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 5012.514929] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 5102.768688] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 5102.768697] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [ 5102.768980] systemd[1]: Failed to start Journal Service. [ 5102.769783] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 5102.769865] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 7. [ 5102.770505] systemd[1]: Stopped Journal Service. [ 5102.770690] systemd[1]: systemd-journald.service: Found left-over process 410 (systemd-journal) in control group while starting unit. Ignoring. [ 5102.770696] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 5102.770724] systemd[1]: systemd-journald.service: Found left-over process 7740 (systemd-journal) in control group while starting unit. Ignoring. [ 5102.770729] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 5193.022451] systemd[1]: systemd-journald.service: Start operation timed out. Terminating. [ 5283.275997] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 5283.276050] systemd[1]: systemd-journald.service: Killing process 7894 (systemd-journal) with signal SIGKILL. [ 5283.276135] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 5283.276161] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 5283.276186] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 5283.276210] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 5283.276237] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 5283.276261] systemd[1]: systemd-journald.service: Killing process 7867 (systemd-journal) with signal SIGKILL. [ 5373.529521] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 5463.782969] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 5463.783021] systemd[1]: systemd-journald.service: Killing process 7894 (systemd-journal) with signal SIGKILL. [ 5463.783102] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 5463.783128] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 5463.783154] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 5463.783178] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 5463.783205] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 5463.783230] systemd[1]: systemd-journald.service: Killing process 7867 (systemd-journal) with signal SIGKILL. [ 5554.036287] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 5554.036298] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [ 5554.036584] systemd[1]: Failed to start Journal Service. [ 5554.037267] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 5554.037329] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 8. [ 5554.037739] systemd[1]: Stopped Journal Service. [ 5554.037898] systemd[1]: systemd-journald.service: Found left-over process 410 (systemd-journal) in control group while starting unit. Ignoring. [ 5554.037902] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 5554.037923] systemd[1]: systemd-journald.service: Found left-over process 7740 (systemd-journal) in control group while starting unit. Ignoring. [ 5554.037926] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 5644.289537] systemd[1]: systemd-journald.service: Start operation timed out. Terminating. [ 5734.542720] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ 5734.542771] systemd[1]: systemd-journald.service: Killing process 7915 (systemd-journal) with signal SIGKILL. [ 5734.542856] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 5734.542882] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 5734.542907] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 5734.542931] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 5734.542958] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 5734.542983] systemd[1]: systemd-journald.service: Killing process 7867 (systemd-journal) with signal SIGKILL. [ 5734.543007] systemd[1]: systemd-journald.service: Killing process 7894 (systemd-journal) with signal SIGKILL. [ 5824.795821] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring. [ 5915.048944] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing. [ 5915.048996] systemd[1]: systemd-journald.service: Killing process 7915 (systemd-journal) with signal SIGKILL. [ 5915.049079] systemd[1]: systemd-journald.service: Killing process 410 (systemd-journal) with signal SIGKILL. [ 5915.049105] systemd[1]: systemd-journald.service: Killing process 7740 (systemd-journal) with signal SIGKILL. [ 5915.049130] systemd[1]: systemd-journald.service: Killing process 7773 (systemd-journal) with signal SIGKILL. [ 5915.049155] systemd[1]: systemd-journald.service: Killing process 7793 (systemd-journal) with signal SIGKILL. [ 5915.049182] systemd[1]: systemd-journald.service: Killing process 7841 (systemd-journal) with signal SIGKILL. [ 5915.049206] systemd[1]: systemd-journald.service: Killing process 7867 (systemd-journal) with signal SIGKILL. [ 5915.049230] systemd[1]: systemd-journald.service: Killing process 7894 (systemd-journal) with signal SIGKILL. [ 6005.302033] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 6005.302044] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [ 6005.302329] systemd[1]: Failed to start Journal Service. [ 6005.303161] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [ 6005.303243] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 9. [ 6005.303854] systemd[1]: Stopped Journal Service.
The people you need to contact are on the linux-scsi@vger.kernel.org mailing list. They are extremely unlikely to be following this bugzilla issue. You'll need to ping the mailing list thread on the linux-scsi mailing list. Or contact the two SCSI maintainers: SCSI SUBSYSTEM M: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com> T: git git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git M: "Martin K. Petersen" <martin.petersen@oracle.com> T: git git://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git Or try contacting the patch author in question, Bart Van Assche <bart.vanassche@wdc.com>. There's not much we (the ext4 developers) can do here to help.
Please close this bugzilla entry as a duplicate of #198861.
Thanks for pointing out the dup bugzilla entry. *** This bug has been marked as a duplicate of bug 198861 ***
On Wed, Nov 08, 2023 at 09:37:23AM +0000, bugzilla-daemon@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=198923 > > Javier Crosby (murphyde835@gmail.com) changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |murphyde835@gmail.com > > --- Comment #11 from Javier Crosby (murphyde835@gmail.com) --- > I'm encountering comparative issues as of late when rhythmbox(a case catcher) > is attempting to compose a downloaded mp3 record to a ntfs volume. Framework > isn't completely hindered however, just all further access endeavors (source: > https://coreball.co) to that ntfs volume fall flat during that meeting and > upon > closure, the framework hangs tight for Circle Director for over 10 minutes > (didn't stand by significantly longer and did a hard reset). > I suspect you commented on the wrong bug...
(In reply to Dennis Busch from comment #6) > The bug report I linked to in comment 3 mentioned two patches ( > https://patchwork.kernel.org/patch/10181165/ and > https://patchwork.kernel.org/patch/10233617/ ) but neither of those appears > to have been applied. I would stick to the last working kernel version for > now (for me that is 4.14.19 as mentioned in that other bug report) and keep > an eye on > https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/ > https://flappydunkgame.com to > see if anything familiar looking pops up which suggests that this particular > problem was fixed ( maybe it already was but I am unable to determine for > sure as I do not fully understand the issue, just have a hunch the problem > is/was a locking issue in the RCU system ). I think so...