Hide Forgot
Description of problem: Not sure how this exact warning happened, but more recent ones with similar call traces appear to happen after the usb drive disconnects unexpectedly Additional info: reporter: libreport-2.6.4 WARNING: CPU: 2 PID: 20054 at fs/btrfs/extent-tree.c:3804 btrfs_write_dirty_block_groups+0x371/0x3a0 [btrfs] BTRFS: Transaction aborted (error -5) Modules linked in: nf_log_ipv4 nf_log_common xt_LOG tun rfcomm ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge ebtable_nat ip6table_raw ip6table_mangle ip6table_security bnep ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_raw iptable_mangle iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack btusb btrtl btbcm ebtable_filter btintel ebtables ip6table_filter ip6_tables ath3k bluetooth btrfs xor vfat fat raid6_pq intel_rapl x86_pkg_temp_thermal coretemp kvm_intel kvm eeepc_wmi asus_wmi sparse_keymap rfkill iTCO_wdt video iTCO_vendor_support snd_hda_codec_realtek irqbypass snd_hda_codec_generic snd_hda_codec_hdmi intel_cstate intel_uncore intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq i2c_i801 lpc_ich i2c_smbus snd_seq_device snd_pcm wmi mei_me snd_timer snd mei tpm_infineon soundcore shpchp tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt amdkfd amd_iommu_v2 radeon uas usb_storage crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel i2c_algo_bit drm_kms_helper serio_raw firewire_ohci ttm firewire_core 8021q garp stp crc_itu_t drm llc mrp r8169 mii fjes CPU: 2 PID: 20054 Comm: QThread Not tainted 4.8.8-100.fc23.x86_64 #1 Hardware name: System manufacturer System Product Name/P8P67 REV 3.1, BIOS 0105 03/28/2011 0000000000000286 000000009982f5ad ffffa005b5e2b8c8 ffffffffad3e493e ffffa005b5e2b918 0000000000000000 ffffa005b5e2b908 ffffffffad0a0ecb 00000edc00000000 ffffa006a1cf5440 ffffa00728361400 0000000000000000 Call Trace: [<ffffffffad3e493e>] dump_stack+0x63/0x85 [<ffffffffad0a0ecb>] __warn+0xcb/0xf0 [<ffffffffad0a0f4f>] warn_slowpath_fmt+0x5f/0x80 [<ffffffffc0a5df55>] ? write_one_cache_group.isra.49+0x45/0xa0 [btrfs] [<ffffffffc0a6b431>] btrfs_write_dirty_block_groups+0x371/0x3a0 [btrfs] [<ffffffffc0a7e7cf>] commit_cowonly_roots+0x24f/0x2e0 [btrfs] [<ffffffffc0a81187>] btrfs_commit_transaction+0x547/0xa40 [btrfs] [<ffffffffc0a79a9f>] btrfs_commit_super+0x8f/0xa0 [btrfs] [<ffffffffc0a7bbcb>] close_ctree+0x2db/0x380 [btrfs] [<ffffffffad26d3da>] ? evict_inodes+0x15a/0x180 [<ffffffffc0a4bf29>] btrfs_put_super+0x19/0x20 [btrfs] [<ffffffffad2520bf>] generic_shutdown_super+0x6f/0xf0 [<ffffffffad2523b2>] kill_anon_super+0x12/0x20 [<ffffffffc0a4cd98>] btrfs_kill_super+0x18/0x110 [btrfs] [<ffffffffad252763>] deactivate_locked_super+0x43/0x70 [<ffffffffad2527ec>] deactivate_super+0x5c/0x60 [<ffffffffad2711bf>] cleanup_mnt+0x3f/0x90 [<ffffffffad271252>] __cleanup_mnt+0x12/0x20 [<ffffffffad0bf0ce>] task_work_run+0x7e/0xa0 [<ffffffffad0a4cbb>] do_exit+0x2cb/0xb20 [<ffffffffad264e30>] ? poll_select_copy_remaining+0x150/0x150 [<ffffffffad0a5597>] do_group_exit+0x47/0xb0 [<ffffffffad0b0a55>] get_signal+0x295/0x630 [<ffffffffad0260a7>] do_signal+0x37/0x6c0 [<ffffffffad264e30>] ? poll_select_copy_remaining+0x150/0x150 [<ffffffffad264e30>] ? poll_select_copy_remaining+0x150/0x150 [<ffffffffad264e30>] ? poll_select_copy_remaining+0x150/0x150 [<ffffffffad00329c>] exit_to_usermode_loop+0x8c/0xd0 [<ffffffffad003bf1>] syscall_return_slowpath+0xa1/0xb0 [<ffffffffad7ffb3a>] entry_SYSCALL_64_fastpath+0xa2/0xa4
Created attachment 1225454 [details] File: dmesg
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.