Since we are still in development with bionic and things change quickly, please re-try with the very latest kernel which is right now:
$ sudo apt -y -qq update && rmadison --arch=ppc64el linux-generic | grep bionic linux-generic | 4.15.0.15.16 | bionic | ppc64el -- 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/1764377 Title: [Ubuntu 18.04] Guest fails to boot with "console=ttyS0,115200" included in kernel param Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Balamuruhan S <balamuruh...@in.ibm.com> - 2018-03-29 01:36:52 == ---Problem Description--- Guest fails to boot with Call Trace by using "console=ttyS0,115200" in kernel param Using latest kernel suggested by Bug 166023 in Host and Guest Contact Information = Balamuruhan S / balamuruh...@in.ibm.com ---uname output--- # uname -a Linux ltc-boston17 4.15.0-12-generic #13 SMP Tue Mar 27 08:20:19 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Boston ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Have a healthy guest booted with latest kernel 2. Boot the guest and enter grub menu to edit kernel param 2. append "console=ttyS0,115200" to kernel param and try to boot 3. Guest fails to boot and goes to shutoff state with Call Trace Call Trace: [ 9.184631] random: crng init done [ 9.330927] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 9.330927] [ 9.332928] CPU: 25 PID: 1 Comm: init Not tainted 4.15.0-12-generic #13 [ 9.334375] Call Trace: [ 9.335077] [c0000007fd10bc30] [c000000000ce991c] dump_stack+0xb0/0xf4 (unreliable) [ 9.336334] [c0000007fd10bc70] [c00000000010b4a0] panic+0x148/0x328 [ 9.337339] [c0000007fd10bd10] [c000000000112888] do_exit+0xc78/0xc80 [ 9.338359] [c0000007fd10bdd0] [c000000000112960] do_group_exit+0x60/0x100 [ 9.339216] [c0000007fd10be10] [c000000000112a24] SyS_exit_group+0x24/0x30 [ 9.340113] [c0000007fd10be30] [c00000000000b184] system_call+0x58/0x6c Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Balamuruhan S / balamuruh...@in.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. == Comment: #7 - Balamuruhan S <balamuruh...@in.ibm.com> - 2018-04-13 04:28:22 == I have hit it while booting already installed guest from qcow2 and edited its commandline from grub menu, so I have attached the full boot log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
