For the benefit of Canonical, this bug is likely related to LP bug
1546260 which is generally covering the issue with kexec issues causing
kdump to not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Alton,
Can you re-create with dmesg log level raised and logs moved to console
instead of k-buffer (I am hoping to get some kernel debug log on console
while reboot).
Step 1. Back_up the dmesg log
step 2. Raise dmesg console level
[root@dev-fedora ~]# dmesg --console-level=7
[root@dev-fedora ~]#
Hi team canonical,
Can you please take look on the issue and let us know, if you require
any additional info or test to debug/solve the issue.
Thanks,
Chandan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Externalizing comment for canonical to take a look and advise:
root@roselp1:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic
root=UUID=b0dee2d0-a2c9-43e2-a43b-70fec2cf6180 ro splash quiet smt-enabled=off
xmon=on crashkernel=384M-:128M
root@roselp1:~#
root@roselp1:~# ls /var/crash/
.
Canonical,
We are still debugging on the issue.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544438
Title:
ISST:LTE: LPAR roselp1 kexec_core from reboot command
To manage notifications
