Description of problem: yum clean all Additional info: reporter: libreport-2.1.10 kernel BUG at fs/buffer.c:3348! invalid opcode: 0000 [#1] SMP Modules linked in: rfcomm fuse bnep bluetooth nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw joydev arc4 rt2800pci rt2800lib coretemp snd_hda_codec_hdmi iTCO_wdt rt2x00pci iTCO_vendor_support lpc_ich snd_hda_codec_realtek snd_hda_intel snd_hda_codec rt2x00mmio rt2x00lib eeprom_93cx6 i2c_i801 snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd kvm crc32c_intel mac80211 mei_me cfg80211 mfd_core serio_raw r8169 mei mii soundcore crc_ccitt rfkill microcode acpi_cpufreq shpchp nfsd auth_rpcgss nfs_acl lockd sunrpc uinput nouveau mxm_wmi video firewire_ohci i2c_algo_bit usb_storage drm_kms_helper ttm drm firewire_core crc_itu_t i2c_core wmi CPU: 1 PID: 2443 Comm: yum Not tainted 3.12.6-200.fc19.x86_64 #1 Hardware name: Hewlett-Packard p6670t/2A9C, BIOS 6.14 11/05/2010 task: ffff8801a1f99080 ti: ffff8800b3b78000 task.ti: ffff8800b3b78000 RIP: 0010:[<ffffffff811de331>] [<ffffffff811de331>] free_buffer_head+0x51/0x60 RSP: 0018:ffff8800b3b79b88 EFLAGS: 00010287 RAX: ffff880189c66590 RBX: ffff880189c66548 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000001000 RDI: ffff880189c66548 RBP: ffff8800b3b79bb0 R08: 9010000000000000 R09: 0189c66548080000 R10: fe5839fd29915202 R11: ffffea0006271980 R12: ffff8800b9aa42d0 R13: 0000000000000001 R14: ffffea0006252980 R15: ffff8801a249bb98 FS: 00007f5964c41740(0000) GS:ffff8801afc40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000028cc008 CR3: 00000000ae7a0000 CR4: 00000000000007e0 Stack: ffffffff811de3bc ffff880189c66548 ffff880189c66548 0000000000000000 ffff880189c66548 ffff8800b3b79bf0 ffffffff81277e10 ffff8800b3b79c40 ffff880189c66548 ffffea0006252980 ffff8801a249b800 0000000000000000 Call Trace: [<ffffffff811de3bc>] ? try_to_free_buffers+0x7c/0xb0 [<ffffffff81277e10>] jbd2_journal_try_to_free_buffers+0xa0/0x110 [<ffffffff812307d2>] ext4_releasepage+0x52/0xb0 [<ffffffff81142362>] try_to_release_page+0x32/0x50 [<ffffffff811df93b>] block_invalidatepage+0xfb/0x120 [<ffffffff81230cae>] ext4_invalidatepage+0x5e/0xa0 [<ffffffff81231260>] ext4_da_invalidatepage+0x40/0x2e0 [<ffffffff811a7390>] ? mem_cgroup_uncharge_cache_page+0x20/0x30 [<ffffffff81150deb>] truncate_inode_page+0x8b/0x90 [<ffffffff81150fa5>] truncate_inode_pages_range+0x175/0x5c0 [<ffffffff81151405>] truncate_inode_pages+0x15/0x20 [<ffffffff812374da>] ext4_evict_inode+0x10a/0x4f0 [<ffffffff811c839f>] evict+0x9f/0x190 [<ffffffff811c8b85>] iput+0xf5/0x180 [<ffffffff811bc23b>] do_unlinkat+0x1ab/0x240 [<ffffffff811bf2d6>] SyS_unlink+0x16/0x20 [<ffffffff816716a9>] system_call_fastpath+0x16/0x1b Code: 40 0a 01 00 b8 01 00 00 00 65 0f c1 04 25 44 0a 01 00 3d ff 0f 00 00 7f 09 5d c3 0f 1f 80 00 00 00 00 e8 b3 fc ff ff 5d 66 90 c3 <0f> 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 RIP [<ffffffff811de331>] free_buffer_head+0x51/0x60 RSP <ffff8800b3b79b88>
Created attachment 846860 [details] File: dmesg
I guess this is the same bug I've been working upstream. Can you provide more information about the problem itself and filesystem you hit it? Is it reproducible? How? please run `tune2fs -l <device>` Also, a filesystem image might be useful too. e2image -Q <device> bz1049639.img bzip2 -z bz1049639.img --Carlos
One more thing. Can you reproduce it on newest kernels and/or latest Fedora version (20)?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 19 kernel bugs. Fedora 19 has now been rebased to 3.13.5-100.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. 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 4 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.