Boot hangs at "loading initial ramdisk..."
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| linux (Ubuntu) |
High
|
Unassigned | ||
| Bionic |
High
|
Unassigned |
Bug Description
I cannot load a kernel beyond 4.15.0-32-generic on my machine.
Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 12 10:52:00 2018
HibernationDevice: RESUME=
InstallationDate: Installed on 2018-01-05 (249 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. Precision Tower 7810
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
dmi.bios.date: 06/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A27
dmi.board.name: 0KJCC5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Precision Tower 7810
dmi.sys.vendor: Dell Inc.
Krister (thekswenson) wrote : | #1 |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Bionic): | |
status: | New → In Progress |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
status: | Confirmed → In Progress |
Joseph Salisbury (jsalisbury) wrote : | #3 |
I built a 4.15.0-35 test kernel.
The test kernel can be downloaded from:
http://
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-
Thanks in advance!
Krister (thekswenson) wrote : | #4 |
I get error messages when installing linux-headers:
-- kms@winters:
=> sudo dpkg -i linux-image-
(Reading database ... 599557 files and directories currently installed.)
.
. snip
.
Setting up linux-headers-
/etc/kernel/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.15.0-35-generic (x86_64)
Consult /var/lib/
Setting up linux-image-
Setting up linux-modules-
Processing triggers for linux-image-
/etc/kernel/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.15.0-35-generic (x86_64)
Consult /var/lib/
.
. snip
.
Joseph Salisbury (jsalisbury) wrote : | #5 |
The linux-headers package shouldn't be needed to test for this bug. You should only need to install the linux-modules, linux-modules-extra and linux-image-
Krister (thekswenson) wrote : | #6 |
The 4.15.0-35 test kernel also hangs at "loading initial ramdisk...".
Joseph Salisbury (jsalisbury) wrote : | #7 |
I started a kernel bisect between Ubuntu-4.15.--32 and Ubuntu-4.15.0-33. The kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
77a24c313d21e37
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #8 |
I'll test this tomorrow.
Krister (thekswenson) wrote : | #9 |
The kernel 4.15.0-32-generic #35~lp1792100Co
I installed an older kernel to use in case of problems. It turns out the some of the older kernels hang in the same way. Here's the rundown on the kernels from the repository:
4.15.0-30: hangs
4.15.0-29: hangs
4.15.0-24: works
4.15.0-20: works
Joseph Salisbury (jsalisbury) wrote : | #10 |
I built the next test kernel, up to the following commit:
7f36a83df6d4fab
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #11 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #12 |
I built the next test kernel, up to the following commit:
9627b5742a8e8d8
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #13 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #14 |
I built the next test kernel, up to the following commit:
00c3aa70c712c5f
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #15 |
The directory http://
Joseph Salisbury (jsalisbury) wrote : | #16 |
Sorry, my upload failed. The .debs are there now.
Krister (thekswenson) wrote : | #17 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #18 |
I built the next test kernel, up to the following commit:
84d28cc43f2d982
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #19 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #20 |
I built the next test kernel, up to the following commit:
d4be7ce8e632469
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #21 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #22 |
I built the next test kernel, up to the following commit:
d86a0bd64457a43
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #23 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #24 |
I built the next test kernel, up to the following commit:
f03220fb0122a5a
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #25 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #26 |
I built the next test kernel, up to the following commit:
3dfa1c904fcf138
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #27 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #28 |
I built the next test kernel, up to the following commit:
19e56be2af5ad53
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
Krister (thekswenson) wrote : | #29 |
The kernel is missing at http://
Joseph Salisbury (jsalisbury) wrote : | #30 |
Sorry about that. The .debs are there now.
Krister (thekswenson) wrote : | #31 |
The 4.15.0-33-generic #37~lp1792100Co
Joseph Salisbury (jsalisbury) wrote : | #32 |
I built a test kernel using the master-next repo.
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not?
Krister (thekswenson) wrote : | #33 |
The 4.15.0-
Joseph Salisbury (jsalisbury) wrote : | #34 |
Does it hang at the same point as prior kernels, or does it seem different?
Krister (thekswenson) wrote : | #35 |
It looks (superficially) the same...
the purple screen says "loading initial ramdisk..." indefinitely.
If you give me instructions, I could look into it further.
Joseph Salisbury (jsalisbury) wrote : | #36 |
What's interesting is the test kernel in comment #28 was tested as good. That was built with commit 19e56be2af5 as the tip of the tree. That commit is only one commit behind 22df1539aed9, which is the version tag. However, the bug exists when commit 22df1539aed9 is the tip.
I built a v2 version of 4.15.0-33.
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not?
Krister (thekswenson) wrote : | #37 |
The 4.15.0-33-generic #37~lp1792100v2 kernel works.
Joseph Salisbury (jsalisbury) wrote : | #38 |
That was using a stock 4.15.0-33.36 tree that I built. Can you test the official build from the ppa, which is available here:
https:/
Just be sure to install all three of the required packages:
linux-modules, linux-modules-extra and linux-image-
Krister (thekswenson) wrote : | #39 |
The 4.15.0-33-generic #36-Ubuntu kernel works.
Joseph Salisbury (jsalisbury) wrote : | #40 |
That is good news, that might indicate this bug is now fixed. Can you apply all the latest updates and the latest kernel to see if the bug still exists?
Krister (thekswenson) wrote : | #41 |
Neither the 4.18.0-10 nor the 4.15.0-39 kernel will boot.
Joseph Salisbury (jsalisbury) wrote : | #42 |
Hmm, OK, thanks for the feedback. Let me review the bisect results and see if we went astray at some point.
Joseph Salisbury (jsalisbury) wrote : | #43 |
Would it be possible for you to test the latest upstream kernel? Refer to https:/
Krister (thekswenson) wrote : | #44 |
The 4.20.0-
Joseph Salisbury (jsalisbury) wrote : | #45 |
If that is the case, we are better off performing a "Reverse" bisect to identify the fix in mainline versus investigating what went wrong in the first regular bisect.
The steps for a reverse bisect are similar, but we first need to find the last "Bad" kernel and the first "Good" kernel. Can you test the following kernels:
v4.19: http://
v4.20-rc1: http://
Krister (thekswenson) wrote : | #46 |
Those kernels are OK.
Joseph Salisbury (jsalisbury) wrote : | #47 |
Can you test 4.18 final:
http://
Krister (thekswenson) wrote : | #48 |
The 4.18.0-
Joseph Salisbury (jsalisbury) wrote : | #49 |
Can you test the following kernel? It appears this bug may have been introduced by a SAUCE patch:
-34:
https:/
Joseph Salisbury (jsalisbury) wrote : | #50 |
Also, just to confirm to test this kernel you need to install the linux-modules, linux-modules-extra and linux-image-
Joseph Salisbury (jsalisbury) wrote : | #51 |
Can you also test the following mainline kernels to confirm if this is due to a SAUCE patch or not:
4.15.18: http://
4.16 Final: http://
Krister (thekswenson) wrote : | #52 |
The 4.15.0-34-generic downloaded from https:/
Krister (thekswenson) wrote : | #54 |
The 4.15.18-
Krister (thekswenson) wrote : | #56 |
The 4.16.0-
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Confirmed |
Changed in linux (Ubuntu): | |
status: | In Progress → Confirmed |
Changed in linux (Ubuntu Bionic): | |
assignee: | Joseph Salisbury (jsalisbury) → nobody |
Changed in linux (Ubuntu): | |
assignee: | Joseph Salisbury (jsalisbury) → nobody |
Nick (nick-power) wrote : | #57 |
Upgrading to 18.10 works.
This change was made by a bot.