← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1665576] Re: btrfs lockup with linux-image-4.4.0-59-generic

 

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable 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.4.49

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags added: kernel-da-key

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1665576

Title:
  btrfs lockup with linux-image-4.4.0-59-generic

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  After upgrading server (xen pvm) to linux-image-4.4.0-59-generic from 4.4.0-57 it locked up soon after using the btrfs filesystem. (Startup looked OK.) No problem with 4.4.0-57. Standard 16.04 stable install.
  Reverting to 4.4.0-57 fixed the problem, just sharing to help others with similar issue and have a chance to hear if it's a known problem. (I did not find one.)

  Feb  2 10:06:36 server1 kernel: [10484.092006] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [apache2:1704]
  ...
  Feb  2 10:06:36 server1 kernel: [10484.092043] Call Trace:
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff818381d3>] _raw_read_lock+0x23/0x30
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc017f80a>] btrfs_tree_read_lock_atomic+0x2a/0x60 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc011daff>] btrfs_search_slot+0x59f/0xa00 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc011890a>] ? btrfs_alloc_path+0x1a/0x20 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff810caf11>] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc0136a8e>] btrfs_lookup_csum+0x4e/0x150 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc0136d3c>] __btrfs_lookup_bio_sums.isra.7+0x1ac/0x500 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc01486c0>] ? btrfs_real_readdir+0x5e0/0x5e0 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff811ed017>] ? kmem_cache_alloc+0x187/0x1f0
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc013ca98>] ? btrfs_bio_wq_end_io+0x28/0x70 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc0137316>] btrfs_lookup_bio_sums+0x36/0x40 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc0145f13>] btrfs_submit_bio_hook+0x133/0x1b0 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc016059d>] submit_one_bio+0x6d/0xa0 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc01673c3>] extent_readpages+0x143/0x200 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc01486c0>] ? btrfs_real_readdir+0x5e0/0x5e0 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff811e271c>] ? alloc_pages_current+0x8c/0x110
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffffc014632f>] btrfs_readpages+0x1f/0x30 [btrfs]
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8119db06>] __do_page_cache_readahead+0x196/0x230
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff81218ef4>] ? terminate_walk+0x64/0xd0
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8119dc70>] ondemand_readahead+0xd0/0x250
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8119df8e>] page_cache_sync_readahead+0x2e/0x50
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8119089d>] generic_file_read_iter+0x4ad/0x5c0
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8120e394>] new_sync_read+0x94/0xd0
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8120e3f6>] __vfs_read+0x26/0x40
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8120e9b6>] vfs_read+0x86/0x130
  Feb  2 10:06:36 server1 kernel: [10484.092043]  [<ffffffff8120f705>] SyS_read+0x55/0xc0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665576/+subscriptions