Udisk related kernel panic upon boot

Bug #1486875 reported by Michael Heuberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

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
---
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: michael-heuberger 6343 F.... pulseaudio
 /dev/snd/controlC2: michael-heuberger 6343 F.... pulseaudio
 /dev/snd/controlC0: michael-heuberger 6343 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028
InstallationDate: Installed on 2014-10-31 (313 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-28-generic N/A
 linux-backports-modules-3.19.0-28-generic N/A
 linux-firmware 1.143.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
Tags: vivid
Uname: Linux 3.19.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data
_MarkForUpload: True
dmi.bios.date: 08/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0803
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6X58D-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
---
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: michael-heuberger 6343 F.... pulseaudio
 /dev/snd/controlC2: michael-heuberger 6343 F.... pulseaudio
 /dev/snd/controlC0: michael-heuberger 6343 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028
InstallationDate: Installed on 2014-10-31 (313 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-28-generic N/A
 linux-backports-modules-3.19.0-28-generic N/A
 linux-firmware 1.143.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
Tags: vivid
Uname: Linux 3.19.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data
_MarkForUpload: True
dmi.bios.date: 08/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0803
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6X58D-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Phillip Susi (psusi)
affects: udisks (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1486875

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
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.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
Revision history for this message
Michael Heuberger (michael.heuberger) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected vivid
description: updated
Revision history for this message
Michael Heuberger (michael.heuberger) wrote : CRDA.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : IwConfig.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : JournalErrors.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : Lspci.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : Lsusb.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcEnviron.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcModules.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : PulseList.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : UdevDb.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : UdevLog.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
Michael Heuberger (michael.heuberger) wrote : AlsaInfo.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : CRDA.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : IwConfig.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : JournalErrors.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : Lspci.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : Lsusb.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcEnviron.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : ProcModules.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : PulseList.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : UdevDb.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : UdevLog.txt

apport information

Revision history for this message
Michael Heuberger (michael.heuberger) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Michael Heuberger (michael.heuberger) wrote :

Information is collected.

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

No idea.

> 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].

Sorry, I am not going to do this. Last time I upgraded the kernel manually it destroyed the boot process and I couldn't boot my machine anymore. Too risky.

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.