Bug 1018632 - [abrt] kernel BUG at fs/btrfs/relocation.c:1055!
Summary: [abrt] kernel BUG at fs/btrfs/relocation.c:1055!
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:62de50412d7fc4a2062e0bab005...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 01:40 UTC by Peter Hjalmarsson
Modified: 2017-07-10 13:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-27 16:16:05 UTC
Type: ---
kanelxake: needinfo-


Attachments (Terms of Use)
File: dmesg (88.91 KB, text/plain)
2013-10-14 01:40 UTC, Peter Hjalmarsson
no flags Details

Description Peter Hjalmarsson 2013-10-14 01:40:36 UTC
Additional info:
reporter:       libreport-2.1.7
kernel BUG at fs/btrfs/relocation.c:1055!
invalid opcode: 0000 [#1] SMP 
Modules linked in: fuse ebtable_nat nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables rfcomm bnep be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi smsc47m192 hwmon_vid dm_service_time dm_multipath snd_hda_codec_analog raid0 snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm vhost_net tun macvtap macvlan snd_page_alloc snd_timer snd soundcore iTCO_wdt iTCO_vendor_support acpi_cpufreq mperf coretemp kvm_intel kvm serio_raw microcode btusb bluetooth lpc_ich i2c_i801 mfd_core rfkill sky2 i7core_edac edac_core asus_atk0110 uinput dm_crypt ata_generic pata_acpi btrfs zlib_deflate raid6_pq libcrc32c xor nouveau crc32c_intel mxm_wmi video firewire_ohci i2c_algo_bit firewire_core drm_kms_helper ttm crc_itu_t pata_jmicron drm usb_storage i2c_core wmi
CPU: 3 PID: 16415 Comm: btrfs-balance Not tainted 3.10.14-100.fc18.x86_64 #1
Hardware name: System manufacturer System Product Name/Rampage II Extreme, BIOS 2101    09/19/2011
task: ffff8803c72487a0 ti: ffff8804789ec000 task.ti: ffff8804789ec000
RIP: 0010:[<ffffffffa0299d7f>]  [<ffffffffa0299d7f>] build_backref_tree+0x10af/0x1160 [btrfs]
RSP: 0018:ffff8804789eda18  EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8804a411a450 RCX: dead000000200200
RDX: ffff8804789edab0 RSI: ffff8804789edab0 RDI: ffff8804a411a450
RBP: ffff8804789edb28 R08: ffff8804a411a450 R09: ffff8804ad003900
R10: ffffffffa0298c97 R11: 0000000000000001 R12: ffff88047f2cc180
R13: ffff8804a411a440 R14: ffff88046c017f30 R15: ffff8804755f1800
FS:  0000000000000000(0000) GS:ffff8804bfc60000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007fa31242619e CR3: 0000000001c0c000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Stack:
 ffffffffa0229fba ffff88047f2cc100 ffff8804789eda78 ffff8804a411a220
 ffff88046c017b40 ffff88046c017f30 ffff88047f2cc000 ffff8804755f6800
 ffff8804755f1920 ffff88047f2cc040 ffff880400000004 ffff8804755f1924
Call Trace:
 [<ffffffffa0229fba>] ? btrfs_free_path+0x2a/0x40 [btrfs]
 [<ffffffffa029a030>] relocate_tree_blocks+0x200/0x6d0 [btrfs]
 [<ffffffffa029b588>] ? add_data_references+0x248/0x280 [btrfs]
 [<ffffffffa029c1a4>] relocate_block_group+0x274/0x6c0 [btrfs]
 [<ffffffffa029c79b>] btrfs_relocate_block_group+0x1ab/0x2e0 [btrfs]
 [<ffffffffa02737f9>] btrfs_relocate_chunk.isra.62+0x59/0x4a0 [btrfs]
 [<ffffffffa026fa21>] ? free_extent_buffer+0x61/0xc0 [btrfs]
 [<ffffffffa02786e7>] btrfs_balance+0x917/0xf60 [btrfs]
 [<ffffffffa0278db2>] balance_kthread+0x82/0x90 [btrfs]
 [<ffffffffa0278d30>] ? btrfs_balance+0xf60/0xf60 [btrfs]
 [<ffffffff81082b30>] kthread+0xc0/0xd0
 [<ffffffff81010000>] ? perf_trace_xen_mmu_flush_tlb_others+0x50/0x110
 [<ffffffff81082a70>] ? kthread_create_on_node+0x120/0x120
 [<ffffffff8166526c>] ret_from_fork+0x7c/0xb0
 [<ffffffff81082a70>] ? kthread_create_on_node+0x120/0x120
Code: ff ff 4c 89 f7 e8 32 02 f9 ff 48 8b bd 10 ff ff ff e8 26 02 f9 ff 48 83 bd 58 ff ff ff 00 0f 84 3a f0 ff ff e9 ca fd ff ff 0f 0b <0f> 0b 49 8b 74 24 18 48 89 c7 e8 81 00 02 00 48 8b 85 20 ff ff 
RIP  [<ffffffffa0299d7f>] build_backref_tree+0x10af/0x1160 [btrfs]
 RSP <ffff8804789eda18>

Comment 1 Peter Hjalmarsson 2013-10-14 01:40:43 UTC
Created attachment 811835 [details]
File: dmesg

Comment 2 Justin M. Forbes 2013-10-18 21:20:48 UTC
*********** 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 18 kernel bugs.

Fedora 18 has now been rebased to 3.11.4-101.fc18.  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 19, and are still experiencing this issue, please change the version to Fedora 19.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2013-11-27 16:16:05 UTC
*********** 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.  

It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo.  Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue.  As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution

If you experience different issues, please open a new bug report for those.


Note You need to log in before you can comment on or make changes to this bug.