Kernel crash on running mercurial clone on a btrfs file system on a SSD Ubuntu 14.04

Bug #1466364 reported by Anshuman Aggarwal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

On running mercurial commands which add/remove lots of files from the disk (typically hard linked) the following error shows up. Since btrfs doesn't really have a fsck utility not sure what I should be running

Jun 18 12:57:27 one kernel: [151416.037158] CPU: 0 PID: 8362 Comm: hg Not tainted 3.13.0-55-generic #92-Ubuntu
Jun 18 12:57:27 one kernel: [151416.038376] Hardware name: /DH61WW, BIOS BEH6110H.86A.0035.2012.0112.2206 01/12/2012
Jun 18 12:57:27 one kernel: [151416.039594] task: ffff880082fd6000 ti: ffff8801023d2000 task.ti: ffff8801023d2000
Jun 18 12:57:27 one kernel: [151416.040812] RIP: 0010:[<ffffffff8137287d>] [<ffffffff8137287d>] memcpy+0xd/0x110
Jun 18 12:57:27 one kernel: [151416.042036] RSP: 0018:ffff8801023d3910 EFLAGS: 00010202
Jun 18 12:57:27 one kernel: [151416.043258] RAX: ffff880168d67dfe RBX: 000000000000009f RCX: 0000000000000013
Jun 18 12:57:27 one kernel: [151416.044491] RDX: 0000000000000007 RSI: 0005080000000000 RDI: ffff880168d67dfe
Jun 18 12:57:27 one kernel: [151416.045727] RBP: ffff8801023d3948 R08: 0000000000001000 R09: ffff8801023d3918
Jun 18 12:57:27 one kernel: [151416.046970] R10: 0000000000000000 R11: 0000000000000003 R12: ffff88008f53bb28
Jun 18 12:57:27 one kernel: [151416.048225] R13: 0000160000000000 R14: ffff880168d67e9d R15: 000000000000009f
Jun 18 12:57:27 one kernel: [151416.049482] FS: 00007fa796d7c740(0000) GS:ffff88021fa00000(0000) knlGS:0000000000000000
Jun 18 12:57:27 one kernel: [151416.050737] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 18 12:57:27 one kernel: [151416.051994] CR2: 00007fa796d9d000 CR3: 000000017f6dd000 CR4: 00000000000407f0
Jun 18 12:57:27 one kernel: [151416.053268] Stack:
Jun 18 12:57:27 one kernel: [151416.054536] ffffffffa028049c 0000000000001000 ffff88020ebcf800 ffff88020d8273f0
Jun 18 12:57:27 one kernel: [151416.055820] 0000000000000000 ffff88017125f640 ffff880193263720 ffff8801023d3a08
Jun 18 12:57:27 one kernel: [151416.057103] ffffffffa02653dc 0000000000003188 0000000000000000 0000000000001000
Jun 18 12:57:27 one kernel: [151416.058391] Call Trace:
Jun 18 12:57:27 one kernel: [151416.059686] [<ffffffffa028049c>] ? read_extent_buffer+0xbc/0x110 [btrfs]
Jun 18 12:57:27 one kernel: [151416.061114] [<ffffffffa02653dc>] btrfs_get_extent+0x91c/0x970 [btrfs]
Jun 18 12:57:27 one kernel: [151416.062471] [<ffffffffa027c697>] __do_readpage+0x357/0x730 [btrfs]
Jun 18 12:57:27 one kernel: [151416.063792] [<ffffffffa0264ac0>] ? btrfs_real_readdir+0x5b0/0x5b0 [btrfs]
Jun 18 12:57:27 one kernel: [151416.065110] [<ffffffffa027cdf2>] __extent_readpages.constprop.41+0x2a2/0x2c0 [btrfs]
Jun 18 12:57:27 one kernel: [151416.066441] [<ffffffffa0264ac0>] ? btrfs_real_readdir+0x5b0/0x5b0 [btrfs]
Jun 18 12:57:27 one kernel: [151416.067756] [<ffffffffa027ec76>] extent_readpages+0x1b6/0x1c0 [btrfs]
Jun 18 12:57:27 one kernel: [151416.069084] [<ffffffffa0264ac0>] ? btrfs_real_readdir+0x5b0/0x5b0 [btrfs]
Jun 18 12:57:27 one kernel: [151416.070385] [<ffffffff81197dc3>] ? alloc_pages_current+0xa3/0x160
Jun 18 12:57:27 one kernel: [151416.071699] [<ffffffffa0262c1f>] btrfs_readpages+0x1f/0x30 [btrfs]
Jun 18 12:57:27 one kernel: [151416.072969] [<ffffffff8115bb99>] __do_page_cache_readahead+0x1b9/0x260
Jun 18 12:57:27 one kernel: [151416.074213] [<ffffffff8115c072>] ondemand_readahead+0x152/0x2a0
Jun 18 12:57:27 one kernel: [151416.075455] [<ffffffff8117ecc8>] ? __vma_link_rb+0xb8/0xe0
Jun 18 12:57:27 one kernel: [151416.076694] [<ffffffff8115c1f1>] page_cache_sync_readahead+0x31/0x50
Jun 18 12:57:27 one kernel: [151416.077930] [<ffffffff81151cb5>] generic_file_aio_read+0x4c5/0x700
Jun 18 12:57:27 one kernel: [151416.079243] [<ffffffff81180f93>] ? mmap_region+0x163/0x600
Jun 18 12:57:27 one kernel: [151416.080603] [<ffffffff811bda1a>] do_sync_read+0x5a/0x90
Jun 18 12:57:27 one kernel: [151416.081825] [<ffffffff811be0b5>] vfs_read+0x95/0x160
Jun 18 12:57:27 one kernel: [151416.083037] [<ffffffff811bebc9>] SyS_read+0x49/0xa0
Jun 18 12:57:27 one kernel: [151416.084231] [<ffffffff81733d5d>] system_call_fastpath+0x1a/0x1f
Jun 18 12:57:27 one kernel: [151416.085408] Code: 43 4e 5b 5d c3 66 0f 1f 84 00 00 00 00 00 e8 fb fb ff ff eb e2 90 90 90 90 90 90 90 90 90 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 <f3> 48 a5 89 d1 f3 a4 c3 20 4c 8b 06 4c 8b 4e 08 4c 8b 56 10 4c
Jun 18 12:57:27 one kernel: [151416.088027] RIP [<ffffffff8137287d>] memcpy+0xd/0x110
Jun 18 12:57:27 one kernel: [151416.089294] RSP <ffff8801023d3910>
Jun 18 12:57:27 one kernel: [151416.263462] ---[ end trace 20764feb3a900ca9 ]---

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-55-generic 3.13.0-55.92
ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bgadmin 25170 F.... pulseaudio
 /dev/snd/controlC1: bgadmin 25170 F.... pulseaudio
Date: Thu Jun 18 13:00:10 2015
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-55-generic root=UUID=736169b4-5ad3-482b-b86d-7c0c43a98fae ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-55-generic N/A
 linux-backports-modules-3.13.0-55-generic N/A
 linux-firmware 1.127.12
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/12/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BEH6110H.86A.0035.2012.0112.2206
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61WW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG23116-204
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0035.2012.0112.2206:bd01/12/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-204:cvn:ct3:cvr:

Revision history for this message
Anshuman Aggarwal (anshuman-aggarwal) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Anshuman Aggarwal (anshuman-aggarwal) wrote :

This issue has occurred on a new installation of Ubuntu 14.04 on a SSD with btrfs filesystem on the full drive.

I will try booting with the mainline kernel and update the results here

Revision history for this message
Anshuman Aggarwal (anshuman-aggarwal) wrote :

kernel-fixed-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Anshuman Aggarwal (anshuman-aggarwal) wrote :

Linux one 4.1.0-040100rc8-generic #201506150335 SMP Mon Jun 15 02:37:00 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

This is the version in which it is fixed for sure. Is the recommendation to stay on this kernel? I assume its unlikely to be back ported?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.