kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

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.2 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'.

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.2-unstable/


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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1486875

Title:
  Udisk related kernel panic upon boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am seeing these lines in the journalctl and my system is behaving
  very weird, slow boot process:

  Aug 20 19:30:58 M1 kernel: INFO: task udisksd:16724 blocked for more than 120 seconds.
  Aug 20 19:30:58 M1 kernel:       Tainted: P           OE  3.19.0-26-generic #28-Ubuntu
  Aug 20 19:30:58 M1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Aug 20 19:30:58 M1 kernel: udisksd         D ffff880199a6bac8     0 16724      1 0x00000004
  Aug 20 19:30:58 M1 kernel:  ffff880199a6bac8 ffff8801ab4444b0 0000000000014240 ffff880199a6bfd8
  Aug 20 19:30:58 M1 kernel:  0000000000014240 ffffffff81c1a580 ffff8801ab4444b0 0000000000800000
  Aug 20 19:30:58 M1 kernel:  ffff8801b76b1398 ffff8801b76b139c ffff8801ab4444b0 00000000ffffffff
  Aug 20 19:30:58 M1 kernel: Call Trace:
  Aug 20 19:30:58 M1 kernel:  [<ffffffff817c72d9>] schedule_preempt_disabled+0x29/0x70
  Aug 20 19:30:58 M1 kernel:  [<ffffffff817c9195>] __mutex_lock_slowpath+0x95/0x100
  Aug 20 19:30:58 M1 kernel:  [<ffffffff817c9216>] ? mutex_lock+0x16/0x40
  Aug 20 19:30:58 M1 kernel:  [<ffffffff817c9223>] mutex_lock+0x23/0x40
  Aug 20 19:30:58 M1 kernel:  [<ffffffff8122ef03>] __blkdev_get+0x63/0x490
  Aug 20 19:30:58 M1 kernel:  [<ffffffff8122f371>] blkdev_get+0x41/0x390
  Aug 20 19:30:58 M1 kernel:  [<ffffffff8122f720>] ? blkdev_get_by_dev+0x60/0x60
  Aug 20 19:30:58 M1 kernel:  [<ffffffff8122f77f>] blkdev_open+0x5f/0x90
  Aug 20 19:30:58 M1 kernel:  [<ffffffff811f2392>] do_dentry_open+0x1d2/0x330
  Aug 20 19:30:58 M1 kernel:  [<ffffffff811f2659>] vfs_open+0x49/0x50
  Aug 20 19:30:58 M1 kernel:  [<ffffffff812027c7>] do_last+0x247/0x12c0
  Aug 20 19:30:58 M1 kernel:  [<ffffffff81205830>] path_openat+0x80/0x5f0
  Aug 20 19:30:58 M1 kernel:  [<ffffffff811a822c>] ? tlb_finish_mmu+0x1c/0x50
  Aug 20 19:30:58 M1 kernel:  [<ffffffff81206fba>] do_filp_open+0x3a/0xb0
  Aug 20 19:30:58 M1 kernel:  [<ffffffff81213d47>] ? __alloc_fd+0xa7/0x130
  Aug 20 19:30:58 M1 kernel:  [<ffffffff811f3faa>] do_sys_open+0x12a/0x280
  Aug 20 19:30:58 M1 kernel:  [<ffffffff811f411e>] SyS_open+0x1e/0x20
  Aug 20 19:30:58 M1 kernel:  [<ffffffff817cb70d>] system_call_fastpath+0x16/0x1b
  Aug 20 19:31:18 M1 org.gnome.zeitgeist.SimpleIndexer[16462]: ** (zeitgeist-fts:17025): WARNING **: Unable to get info on application://gnome-terminal-server.desktop
  Aug 20 19:31:20 M1 systemd[1]: udisks2.service still around after final SIGKILL. Entering failed mode.
  Aug 20 19:31:20 M1 systemd[1]: Failed to start Disk Manager.
  Aug 20 19:31:20 M1 systemd[1]: Unit udisks2.service entered failed state.
  Aug 20 19:31:20 M1 systemd[1]: udisks2.service failed.

  
  Any ideas how to fix the above?

  Thanks

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