** Tags added: cscc
--
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/1777242
Title:
4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)
Status in linux package in
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tested this v2 test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777242
No problems from my side.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It kind of works but takes forever to start due to crng initialization.
(Forever like I didn’t wait and ended up pressing some random keys to get
things moving after more than a minute.)
[6.163871] 8139cp :00:03.0 ens3: link up, 100Mbps, full-duplex, lpa
0x05E1
[ 97.338260] random:
I built a v2 test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777242
Can you test this kernel and see if it resolves this bug?
Also, can you post the output from dmesg?
--
You received this bug notification because you are a member of Kernel
I can confirm 4.15.0-23.26~lp1777242 is installing and booting fine.
Thanks for your quick feedbacks. :)
--
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/1777242
Title:
4.15.0-23-generic
Bionic commit 494f8f20811baf5 is a revert of Bionic commit dc0f16f9b50.
This was done for bug 1728238. We will investigate further to find a
solution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tested with 4.15.0-23 ~lp1777242
(http://kernel.ubuntu.com/~jsalisbury/lp1777242) kernel. It solves the
bug.
--
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/1777242
Title:
I built a test kernel with a revert of Bionic commit
494f8f20811baf580370f7d65bb7ea615ec37882. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1777242
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test
Tested 4.15.18 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/)
I boots normally with no kernel panic problem.
--
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/1777242
Title:
When tested with main line version 4.17.2 (http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.17.2/), kernel panic problem resurfaces.
--
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/1777242
Hmm, I had missed that :
$ sudo update-initramfs -u -k 4.15.0-23-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
modinfo: ERROR: could not get modinfo from 'qxl': Exec format error
depmod: ERROR: failed to load symbols from
Can you next test the upstream 4.15.18 stable kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
If 4.15.18 still has the bug, we can perform a reverse kernel bisect to
identify the fix in mainline.
--
You received this bug notification because you are a member of Kernel
Packages,
I have tried with this mainline kernel ver 4.18 rc1
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1) and has no
kernel panic problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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
Kernel log says:
Failed to execute /init (error -2)
Kernel panic - not syncing: No working init found. Try passing init= option to
kernel. [...]
** Attachment added: "Capture d’écran depuis 2018-06-16 15-54-05.png"
Apport info is obviously from the booting kernel, I’ll try to also get
some useful information from the panic in the VT.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1777242
18 matches
Mail list logo
