Public bug reported:
== Comment: #0 - Ping Tian Han <pt...@cn.ibm.com> - 2016-02-15 04:29:28 ==
---Problem Description---
When trying to reboot the system by kexec, it failed. On the console, we saw:
thymelp2 login: [ 507.646433] sysrq: SysRq : This sysrq operation is disabled.
[ 515.543145] sysrq: SysRq : Changing Loglevel
[ 515.543166] sysrq: Loglevel set to 9
[ 517.959794] sysrq: SysRq : Emergency Sync
[ 517.983391] Emergency Sync complete
[ 518.969945] sysrq: SysRq : Emergency Sync
[ 518.972149] Emergency Sync complete
[ 519.887521] sysrq: SysRq : Emergency Sync
[ 519.896428] Emergency Sync complete
[ 520.951239] sysrq: SysRq : Emergency Remount R/O
[ 520.961834] EXT4-fs (sda2): re-mounted. Opts: (null)
[ 520.964846] Emergency Remount complete
[ 521.965700] sysrq: SysRq : Emergency Remount R/O
[ 521.965760] Emergency Remount complete
[ 522.919144] sysrq: SysRq : Emergency Remount R/O
[ 522.919187] Emergency Remount complete
[ 544.618490] EXT4-fs (sda2): ext4_writepages: jbd2_start: 832 pages, ino
7737780; err -30
[ 544.618537] EXT4-fs (sda2): ext4_writepages: jbd2_start: 832 pages, ino
7737824; err -30
[ 544.618548] EXT4-fs (sda2): ext4_writepages: jbd2_start: 832 pages, ino
7737791; err -30
[ 544.618557] EXT4-fs (sda2): ext4_writepages: jbd2_start: 832 pages, ino
7737795; err -30
[ 548.710176] mlx4_core 0004:01:00.0: mlx4_shutdown was called
[ 549.032483] mlx4_en 0004:01:00.0: removed PHC
[ 553.568793] kexec_core: Starting new kernel
[ 553.589308] kexec: waiting for cpu 160 (physical 160) to enter 1 state
[ 553.594565] kexec: waiting for cpu 165 (physical 165) to enter 1 state
[ 553.594648] kexec: waiting for cpu 1 (physical 1) to enter 2 state
[ 553.595352] kexec: waiting for cpu 4 (physical 4) to enter 2 state
[ 553.655271] kexec: waiting for cpu 32 (physical 32) to enter 2 state
[ 553.674833] kexec: waiting for cpu 35 (physical 35) to enter 2 state
[ 553.674947] kexec: waiting for cpu 36 (physical 36) to enter 2 state
[ 553.685406] kexec: waiting for cpu 40 (physical 40) to enter 2 state
[ 553.694544] kexec: waiting for cpu 48 (physical 48) to enter 2 state
[ 553.694852] kexec: waiting for cpu 50 (physical 50) to enter 2 state
[ 553.694909] kexec: waiting for cpu 51 (physical 51) to enter 2 state
[ 553.694981] kexec: waiting for cpu 104 (physical 104) to enter 2 state
[ 553.704546] kexec: waiting for cpu 136 (physical 136) to enter 2 state
[ 553.714536] kexec: waiting for cpu 137 (physical 137) to enter 2 state
<-------------- hangs here
after 'kexec -e'
Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
Mitsuyoshi/carri...@us.ibm.com
---uname output---
Linux thymelp2 4.4.0-2-generic #16-Ubuntu SMP Thu Jan 28 15:42:17 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
Machine Type = LPAR IBM,8247-22L
---System Hang---
We have to power reset the system to reclaim it.
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. load new kernel by
sudo kexec -l /boot/vmlinux-4.4.0-2-generic
--append='BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic
root=UUID=c7fec198-8f74-44e3-a81e-a5a8f6f9d814 ro splash quiet
crashkernel=384M-:128M' --initrd=/boot/initrd.img-4.4.0-2-generic
2. load the new kernel by
sudo kexec -e
Stack trace output:
no
Oops output:
no
System Dump Info:
The system was configured to capture a dump, however a dump was not produced.
*Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie
Mitsuyoshi/carri...@us.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
-Attach sysctl -a output output to the bug.
** Affects: ubuntu
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New
** Tags: architecture-ppc64le bugnameltc-137124 severity-high
targetmilestone-inin---
** Tags added: architecture-ppc64le bugnameltc-137124 severity-high
targetmilestone-inin---
** Changed in: ubuntu
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546919
Title:
ISST-LTE: kexec failed to boot kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1546919/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
