ISST-LTE:Ubuntu15.04:20150318:kdump: linux-crashdump packages install using apt-get will stuck

Bug #1434023 reported by bugproxy
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

== Comment: #0 - Hemant Kumar <email address hidden> - 2015-03-19 04:25:43 ==
Defect Description:
-----------------------

I have installed ubuntu15.04 daily build (20150318). After installation i tried installing kdump package "linux-crashdump" using apt-get.
"apt-get install linux-crashdump"

And after package installation it will stuck and will not give prompt. here is output:

root@highlp2:/home/hemant# apt-get install linux-crashdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  apport apport-symptoms binutils crash kdump-tools kexec-tools libdw1
  libpolkit-agent-1-0 libpolkit-backend-1-0 makedumpfile policykit-1
  python3-apport python3-problem-report
Suggested packages:
  apport-gtk apport-kde binutils-doc python3-launchpadlib
The following NEW packages will be installed:
  apport apport-symptoms binutils crash kdump-tools kexec-tools libdw1
  libpolkit-agent-1-0 libpolkit-backend-1-0 linux-crashdump makedumpfile
  policykit-1 python3-apport python3-problem-report
0 upgraded, 14 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,514 kB of archives.
After this operation, 30.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libdw1 ppc64el 0.160-0ubuntu3 [161 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-agent-1-0 ppc64el 0.105-8ubuntu2 [14.6 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-backend-1-0 ppc64el 0.105-8ubuntu2 [33.5 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-problem-report all 2.16.2-0ubuntu3 [10.2 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-apport all 2.16.2-0ubuntu3 [75.8 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport all 2.16.2-0ubuntu3 [113 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport-symptoms all 0.20 [14.2 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports/ vivid/main binutils ppc64el 2.25-5ubuntu1 [2,184 kB]
Get:9 http://ports.ubuntu.com/ubuntu-ports/ vivid/main crash ppc64el 7.0.8-1ubuntu1 [2,664 kB]
Get:10 http://ports.ubuntu.com/ubuntu-ports/ vivid/main makedumpfile ppc64el 1:1.5.7-5 [99.8 kB]
Get:11 http://ports.ubuntu.com/ubuntu-ports/ vivid/main kexec-tools ppc64el 1:2.0.7-5ubuntu2 [73.8 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports/ vivid/main kdump-tools all 1:1.5.7-5 [16.2 kB]
Get:13 http://ports.ubuntu.com/ubuntu-ports/ vivid/main linux-crashdump ppc64el 3.19.0.9.8 [2,550 B]
Get:14 http://ports.ubuntu.com/ubuntu-ports/ vivid/main policykit-1 ppc64el 0.105-8ubuntu2 [50.7 kB]
Fetched 5,514 kB in 0s (31.4 MB/s)
Preconfiguring packages ...

Package configuration

 ?????????????????????????? Configuring kexec-tools ??????????????????????????
 ? ?
 ? If you choose this option, a system reboot will trigger a restart into a ?
 ? kernel loaded by kexec instead of going through the full system boot ?
 ? loader process. ?
 ? ?
 ? Should kexec-tools handle reboots? ?
 ? ?
 ? <Yes> <No> ?
 ? ?
 ?????????????????????????????????????????????????????????????????????????????

Selecting previously unselected package libdw1:ppc64el.
(Reading database ... 48391 files and directories currently installed.)
Preparing to unpack .../libdw1_0.160-0ubuntu3_ppc64el.deb ...
Unpacking libdw1:ppc64el (0.160-0ubuntu3) ...
[ 81.163819] sda2: WRITE SAME failed. Manually zeroing.
Selecting previously unselected package libpolkit-agent-1-0:ppc64el.
Preparing to unpack .../libpolkit-agent-1-0_0.105-8ubuntu2_ppc64el.deb ...
Unpacking libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ...
Selecting previously unselected package libpolkit-backend-1-0:ppc64el.
Preparing to unpack .../libpolkit-backend-1-0_0.105-8ubuntu2_ppc64el.deb ...
Unpacking libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ...
Selecting previously unselected package python3-problem-report.
Preparing to unpack .../python3-problem-report_2.16.2-0ubuntu3_all.deb ...
Unpacking python3-problem-report (2.16.2-0ubuntu3) ...
Selecting previously unselected package python3-apport.
Preparing to unpack .../python3-apport_2.16.2-0ubuntu3_all.deb ...
Unpacking python3-apport (2.16.2-0ubuntu3) ...
Selecting previously unselected package apport.
Preparing to unpack .../apport_2.16.2-0ubuntu3_all.deb ...
Unpacking apport (2.16.2-0ubuntu3) ...
Selecting previously unselected package apport-symptoms.
Preparing to unpack .../apport-symptoms_0.20_all.deb ...
Unpacking apport-symptoms (0.20) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.25-5ubuntu1_ppc64el.deb ...
Unpacking binutils (2.25-5ubuntu1) ...
Selecting previously unselected package crash.
Preparing to unpack .../crash_7.0.8-1ubuntu1_ppc64el.deb ...
Unpacking crash (7.0.8-1ubuntu1) ...
Selecting previously unselected package makedumpfile.
Preparing to unpack .../makedumpfile_1%3a1.5.7-5_ppc64el.deb ...
Unpacking makedumpfile (1:1.5.7-5) ...
Selecting previously unselected package kexec-tools.
Preparing to unpack .../kexec-tools_1%3a2.0.7-5ubuntu2_ppc64el.deb ...
Unpacking kexec-tools (1:2.0.7-5ubuntu2) ...
Selecting previously unselected package kdump-tools.
Preparing to unpack .../kdump-tools_1%3a1.5.7-5_all.deb ...
Unpacking kdump-tools (1:1.5.7-5) ...
Selecting previously unselected package linux-crashdump.
Preparing to unpack .../linux-crashdump_3.19.0.9.8_ppc64el.deb ...
Unpacking linux-crashdump (3.19.0.9.8) ...
Selecting previously unselected package policykit-1.
Preparing to unpack .../policykit-1_0.105-8ubuntu2_ppc64el.deb ...
Unpacking policykit-1 (0.105-8ubuntu2) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for dbus (1.8.12-1ubuntu3) ...
Setting up libdw1:ppc64el (0.160-0ubuntu3) ...
Setting up libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ...
Setting up libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ...
Setting up python3-problem-report (2.16.2-0ubuntu3) ...
Setting up python3-apport (2.16.2-0ubuntu3) ...
Setting up apport (2.16.2-0ubuntu3) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out (g-dbus-error-quark, 20)
Failed to execute operation: Connection timed out
invoke-rc.d: apport.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present.
Setting up apport-symptoms (0.20) ...
Setting up binutils (2.25-5ubuntu1) ...
Setting up crash (7.0.8-1ubuntu1) ...
Setting up makedumpfile (1:1.5.7-5) ...
Setting up kexec-tools (1:2.0.7-5ubuntu2) ...
Generating /etc/default/kexec...
Generating grub configuration file ...
Found linux image: /boot/vmlinux-3.19.0-9-generic
Found initrd image: /boot/initrd.img-3.19.0-9-generic
[ 129.359839] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 129.361219] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 129.362597] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 129.363956] FAT-fs (sda1): bogus number of reserved sectors
[ 129.436838] FAT-fs (sda1): bogus number of reserved sectors
[ 129.452912] qnx4: no qnx4 filesystem (no root dir).
[ 129.454004] ufs: You didn't specify the type of your ufs filesystem
[ 129.454004]
[ 129.454004] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 129.454004]
[ 129.454004] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 129.454476] ufs: ufs_fill_super(): bad magic number
[ 129.560607] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 129.562540] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 129.564323] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 129.566828] FAT-fs (sdb1): bogus number of reserved sectors
[ 129.588732] FAT-fs (sdb1): bogus number of reserved sectors
[ 129.604172] qnx4: no qnx4 filesystem (no root dir).
[ 129.605263] ufs: You didn't specify the type of your ufs filesystem
[ 129.605263]
[ 129.605263] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 129.605263]
[ 129.605263] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 129.609651] ufs: ufs_fill_super(): bad magic number
[ 132.504360] EXT4-fs (sdg1): VFS: Can't find ext4 filesystem
[ 132.512102] EXT4-fs (sdg1): VFS: Can't find ext4 filesystem
[ 132.517429] EXT4-fs (sdg1): VFS: Can't find ext4 filesystem
[ 132.525346] FAT-fs (sdg1): bogus number of reserved sectors
[ 132.568984] FAT-fs (sdg1): bogus number of reserved sectors
[ 132.671699] qnx4: no qnx4 filesystem (no root dir).
[ 132.672869] ufs: You didn't specify the type of your ufs filesystem
[ 132.672869]
[ 132.672869] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 132.672869]
[ 132.672869] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 132.694344] ufs: ufs_fill_super(): bad magic number
[ 144.620556] EXT4-fs (sdl1): VFS: Can't find ext4 filesystem
[ 144.655644] EXT4-fs (sdl1): VFS: Can't find ext4 filesystem
[ 144.674704] EXT4-fs (sdl1): VFS: Can't find ext4 filesystem
[ 144.685403] FAT-fs (sdl1): bogus number of reserved sectors
[ 144.735992] FAT-fs (sdl1): bogus number of reserved sectors
[ 144.775409] qnx4: no qnx4 filesystem (no root dir).
[ 144.776813] ufs: You didn't specify the type of your ufs filesystem
[ 144.776813]
[ 144.776813] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 144.776813]
[ 144.776813] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 144.794942] ufs: ufs_fill_super(): bad magic number
[ 157.803938] EXT4-fs (sdq1): VFS: Can't find ext4 filesystem
[ 157.809537] EXT4-fs (sdq1): VFS: Can't find ext4 filesystem
[ 157.811758] EXT4-fs (sdq1): VFS: Can't find ext4 filesystem
[ 157.814393] FAT-fs (sdq1): bogus number of reserved sectors
[ 157.832624] FAT-fs (sdq1): bogus number of reserved sectors
[ 157.861850] qnx4: no qnx4 filesystem (no root dir).
[ 157.862890] ufs: You didn't specify the type of your ufs filesystem
[ 157.862890]
[ 157.862890] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 157.862890]
[ 157.862890] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 157.870722] ufs: ufs_fill_super(): bad magic number
Found Ubuntu Vivid Vervet (development branch) (15.04) on /dev/sdb2
Found Ubuntu Vivid Vervet (development branch) (15.04) on /dev/sdg2
Found Ubuntu Vivid Vervet (development branch) (15.04) on /dev/sdl2
Found Ubuntu Vivid Vervet (development branch) (15.04) on /dev/sdq2
done

--------- IT WILL STUCK HERE-----------

I waited around 30 min but it will be stuck here only.
To get the prompt(console) back we need to reboot the lpar.

After reboot i tried installing kdump package again and i saw this:

root@highlp2:~# apt-get install linux-crashdump
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
root@highlp2:~#

I did "dpkg --configure -a" here and tried installing kdump package (linux-crashdump) and it says package is already installed.

I checked kdump service here and it says kdump is active:

root@highlp2:~# /etc/init.d/kdump-tools status
? kdump-tools.service - Kernel crash dump capture service
   Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2015-03-19 03:31:20 EDT; 47s ago
  Process: 9956 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS)
 Main PID: 9956 (code=exited, status=0/SUCCESS)

Mar 19 03:31:20 highlp2 systemd[1]: Starting Kernel crash dump capture serv.....
Mar 19 03:31:20 highlp2 systemd[1]: Started Kernel crash dump capture service.
Hint: Some lines were ellipsized, use -l to show in full.
root@highlp2:~#

root@highlp2:~# uname -a
Linux highlp2 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:43 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@highlp2:~#

I have tried installing another ubuntu15.04 lpar with cdrom as well but everytime kdump package installation will get stuck here and we need a reboot after this.

Steps to recreate:

1> Install ubuntu15.04 lpar
2> login to lpar as root
3> apt-get install linux-crashdump

contact info: <email address hidden>

== Comment: #1 - Hemant Kumar <email address hidden> - 2015-03-19 04:31:10 ==
After reboot i got /var/log/syslogs from lpar.

Revision history for this message
bugproxy (bugproxy) wrote : /var/log/syslogs

Default Comment by Bridge

tags: added: architecture-ppc64 bugnameltc-122925 severity-critical targetmilestone-inin---
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1434023/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Luciano Chavez (lnx1138)
affects: ubuntu → linux-meta (Ubuntu)
Brad Figg (brad-figg)
affects: linux-meta (Ubuntu) → linux (Ubuntu)
tags: added: kernel-da-key
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-04-10 09:14 EDT-------
Hello Ubuntu,

Any updates on this?

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-04-14 13:29 EDT-------
From the logs, update-grub seems finished.
Question is: is anything done later, to create that apparently hang scenario?

...
Setting up kexec-tools (1:2.0.7-5ubuntu2) ...
...
Generating grub configuration file ...
...
done

<STUCK>

Checking in binary package..
Ah, yes - there are more things done after update-grub ('Automatically added' snippets).

# apt-get download kexec-tools
# dpkg-deb -e kexec-tools_1%3a2.0.7-5ubuntu2_ppc64el.deb bin-pkg

# cat bin-pkg/postinst
...

# ------------------------- Debconf questions end ---------------------

# no triggers in grub2,
# see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481542
if [ -x /usr/sbin/update-grub ] && [ -e /boot/grub/grub.cfg ]; then
update-grub
fi

# Automatically added by dh_installinit
if [ -x "/etc/init.d/kexec" ]; then
update-rc.d kexec defaults >/dev/null
fi
if [ -x "/etc/init.d/kexec" ] || [ -e "/etc/init/kexec.conf" ]; then
invoke-rc.d kexec start || exit $?
fi
# End automatically added section
# Automatically added by dh_installinit
if [ -x "/etc/init.d/kexec-load" ]; then
update-rc.d kexec-load defaults >/dev/null
fi
if [ -x "/etc/init.d/kexec-load" ] || [ -e "/etc/init/kexec-load.conf" ]; then
invoke-rc.d kexec-load start || exit $?
fi
# End automatically added section

exit 0

You can try reproducing them by hand, and see if any does hang.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-04-14 15:12 EDT-------
*** Bug 123832 has been marked as a duplicate of this bug. ***

Revision history for this message
Chris J Arges (arges) wrote :

I've tested this on PowerNV, and linux-crashdump installs without error. update-grub works as well. This must be specific to grub2 and PowerVM.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
bugproxy (bugproxy) wrote : /var/log/syslogs

Default Comment by Bridge

Revision history for this message
bugproxy (bugproxy) wrote :

Default Comment by Bridge

Revision history for this message
bugproxy (bugproxy) wrote :

Default Comment by Bridge

Revision history for this message
bugproxy (bugproxy) wrote :

Default Comment by Bridge

Revision history for this message
bugproxy (bugproxy) wrote :

Default Comment by Bridge

Revision history for this message
bugproxy (bugproxy) wrote :

Default Comment by Bridge

Revision history for this message
bugproxy (bugproxy) wrote :

Default Comment by Bridge

Revision history for this message
bugproxy (bugproxy) wrote :

Default Comment by Bridge

bugproxy (bugproxy)
tags: added: architecture-ppc64le
removed: architecture-ppc64
Revision history for this message
Chris J Arges (arges) wrote :

I couldn't reproduce this on a PowerNV system, can somebody re-test this and confirm the issue still exists?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-07-02 12:24 EDT-------
Workaround, from a fresh install:
apt-get install policykit-1
apt-get install linux-crashdump

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-07-02 12:45 EDT-------
*** This bug has been marked as a duplicate of bug 122991 ***

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.