Hide Forgot
Description of problem: trying to copy some files on a WD 4Tb HDD. seems related to my motherboard a asrock mini-itx J3710-ITX with 4 HDDs Additional info: reporter: libreport-2.7.2 kernel BUG at fs/buffer.c:3061! invalid opcode: 0000 [#1] SMP Modules linked in: bnep fuse ebtable_filter ebtables ip6table_filter ip6_tables intel_rapl intel_powerclamp coretemp kvm iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi irqbypass crct10dif_pclmul snd_hda_codec_realtek crc32_pclmul snd_hda_codec_generic ghash_clmulni_intel intel_cstate snd_hda_intel snd_intel_sst_acpi snd_hda_codec snd_soc_rt5670 snd_intel_sst_core snd_soc_sst_mfld_platform snd_soc_rl6231 snd_soc_sst_match mei_txe snd_soc_core snd_hda_core mei i2c_i801 snd_hwdep i2c_smbus lpc_ich shpchp snd_compress snd_pcm_dmaengine ac97_bus hci_uart snd_seq btbcm btqca snd_seq_device btintel snd_pcm nxp_nci_i2c bluetooth nxp_nci nci nfc dw_dmac snd_timer dw_dmac_core snd i2c_designware_platform rfkill_gpio soc_button_array i2c_designware_core soundcore spi_pxa2xx_platform rfkill tpm_tis pwm_lpss_platform tpm_tis_core pwm_lpss tpm acpi_pad nfsd auth_rpcgss nfs_acl lockd grace sunrpc i915 crc32c_intel serio_raw i2c_algo_bit drm_kms_helper r8169 mii drm fjes video sdhci_acpi sdhci mmc_core i2c_hid CPU: 2 PID: 1694 Comm: scp Not tainted 4.8.4-200.fc24.x86_64 #1 Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3710-ITX, BIOS P1.30 03/30/2016 task: ffff90f51b0b0000 task.stack: ffff90f51e224000 RIP: 0010:[<ffffffffbb2899fb>] [<ffffffffbb2899fb>] submit_bh_wbc+0x19b/0x1b0 RSP: 0018:ffff90f51e2279b8 EFLAGS: 00010246 RAX: 0000000000220005 RBX: ffff90f50cd747b8 RCX: 0000000000000000 RDX: ffff90f50cd747b8 RSI: 0000000000000148 RDI: 0000000000000001 RBP: ffff90f51e2279e8 R08: 0000000000000000 R09: ffff90f50bf08d90 R10: 0000000000000000 R11: 0000000000000228 R12: 0000000000000148 R13: ffff90f52c2a5000 R14: ffff90f516752400 R15: 0000000078828071 FS: 00007f51e7d6b700(0000) GS:ffff90f53fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000056455c8782c8 CR3: 000000024c5a9000 CR4: 00000000001006e0 Stack: ffff90f50cd747b8 ffff90f50cd747b8 0000000000000148 ffff90f52c2a5000 ffff90f516752400 0000000078828071 ffff90f51e227a08 ffffffffbb28c205 ffff90f50cd747b8 ffffffffbbf56740 ffff90f51e227a50 ffffffffbb305f28 Call Trace: [<ffffffffbb28c205>] __sync_dirty_buffer+0x55/0x100 [<ffffffffbb305f28>] ext4_commit_super+0x1e8/0x2a0 [<ffffffffbb30637b>] __ext4_error_inode+0x9b/0x170 [<ffffffffbb2f2540>] ext4_find_entry+0x3f0/0x6d0 [<ffffffffbb26b194>] ? d_alloc_parallel+0xc4/0x4f0 [<ffffffffbb2f2dd7>] ext4_lookup+0x77/0x210 [<ffffffffbb25c845>] lookup_slow+0xa5/0x170 [<ffffffffbb25d53c>] walk_component+0x1ec/0x310 [<ffffffffbb25e837>] path_lookupat+0x67/0x120 [<ffffffffbb260e11>] filename_lookup+0xb1/0x180 [<ffffffffbb26e813>] ? touch_atime+0x33/0xd0 [<ffffffffbb226606>] ? kmem_cache_alloc+0x156/0x1b0 [<ffffffffbb260a0f>] ? getname_flags+0x4f/0x1f0 [<ffffffffbb260fb6>] user_path_at_empty+0x36/0x40 [<ffffffffbb255a26>] vfs_fstatat+0x66/0xc0 [<ffffffffbb255f7e>] SYSC_newstat+0x2e/0x60 [<ffffffffbb25086b>] ? vfs_read+0x11b/0x130 [<ffffffffbb251cc5>] ? SyS_read+0x55/0xc0 [<ffffffffbb25614e>] SyS_newstat+0xe/0x10 [<ffffffffbb802572>] entry_SYSCALL_64_fastpath+0x1a/0xa4 Code: c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 f0 80 62 01 f7 e9 ea fe ff ff be 1c 0c 00 00 48 c7 c7 9e dc c5 bb e8 69 75 e1 ff eb b0 0f 0b <0f> 0b 0f 0b 0f 0b 0f 0b 0f 0b 90 66 2e 0f 1f 84 00 00 00 00 00 RIP [<ffffffffbb2899fb>] submit_bh_wbc+0x19b/0x1b0 RSP <ffff90f51e2279b8>
Created attachment 1217770 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.