** Changed in: linux (Ubuntu)
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.
https://bugs.launchpad.net/bugs/1777338
Title:
Linux 4.15.0-23 crashes during the boot process
** 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/1777338
Title:
Linux 4.15.0-23 crashes during the boot process with a "Unable to
handle kernel NULL pointer
This bug was fixed in the package linux - 4.15.0-34.37
---
linux (4.15.0-34.37) bionic; urgency=medium
* linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
* Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I don't seem to have access to change the tag, but I can confirm that
4.15.0-34-generic from -proposed solves the problem. So the tag should
be verification-done-bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Bionic)
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.
https://bugs.launchpad.net/bugs/1777338
Title:
Linux 4.15.0-23 crashes during the boot
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-August/094683.html
** Description changed:
+ == SRU Justification ==
+ Mainline commit 1f50ddb4f418 introduced a regression. That commit added
+ speculative_store_bypass_ht_init() to the per-CPU initialization sequence.
+
OK, I have tested the provided kernel and it works for me under Xen.
Thank you for fixing the bug! I look forward to seeing this in the
real releases.
[anovak@octagon ~]$ uname -a
Linux octagon 4.15.0-31-generic #34~lp1777338 SMP Tue Aug 7 14:57:12
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
On Mon,
The hashes are:
63d7e9ca7710792e1603953b0ec14337 linux-image-
unsigned-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb
8cca692f07f9edbb56dec15375bc9979 linux-
modules-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb
df24a98ec4769f33a9831a5aaeb9f437 linux-modules-
Thanks for preparing this kernel; I am downloading it now. What are
the expected hashes of the files, so that I can verify the insecure
downloads?
On Tue, Aug 7, 2018 at 8:49 AM, Joseph Salisbury
wrote:
> I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b.
> The test
I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777338
Can you test this kernel and see if it resolves this bug?
If this kernel also fixes the bug, I'll submit an SRU request.
Note
OK, I grabbed commit 74899d92e3dc7671a8017b3146dcd4735f3b "x86/xen:
Add call of speculative_store_bypass_ht_init() to PV paths" from
g...@github.com:torvalds/linux.git and cherry-picked it on top of the tag
Ubuntu-4.15.0-29.31, and built the kernel, and now it boots fine as
dom0! I think that
I've been advised by Juergen Gross that not having "x86/xen: Add call of
speculative_store_bypass_ht_init() to PV paths" from the mainline kernel
might contribute to this problem. I am trying to pull that in now.
--
You received this bug notification because you are a member of Kernel
Packages,
I'm not finding any kernel packages in bionic-proposed; maybe they were
released already?
I've installed and tested 4.15.0-29 from the normal repos; it has the same
null pointer dereference at address 8 issue.
On Tue, Jul 24, 2018, 09:17 Joseph Salisbury
wrote:
> Thanks for finishing up the
Thanks for finishing up the bisect!
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
--
You received this bug
OK, I have finished the bisect.
3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c is the first bad commit. I
tested it and it displays the problem, and I tested
abd39ac1da07b433fc570332ee9ad938b5071760 right before it and that one
boots fine.
On Sat, Jul 21, 2018 at 9:42 AM, Adam Novak wrote:
> That one
That one works. On to 5856293c78e552c012835e667d66775bba20b4f7.
I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since
the CPU I am using is an AMD Ryzen chip, and those are tinkering
specifically with how the kernel handles those.
On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak
OK, I tried that one and it still exhibited the issue. I'm going to
try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next.
On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote:
> Thanks!
>
> I have tested this kernel; it doesn't work, so the problem is between
> fc8704280f2ada9f61f08a2d5adc0dab169cc207
Thanks!
I have tested this kernel; it doesn't work, so the problem is between
fc8704280f2ada9f61f08a2d5adc0dab169cc207 and
8eca6add0defde203282476d7969a7c13bbd7d91.
I've gotten set up with a kernel build environment; I think I can
finish the git bisect myself, but looking at the commits in that
I built the next test kernel, up to the following commit:
fc8704280f2ada9f61f08a2d5adc0dab169cc207
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777338
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
OK, I've tested this kernel, and it works just fine under Xen, from
what I can tell. The system comes up just fine:
Linux octagon 4.15.0-23-generic #26~lp1777338Commit8eca6add0 SMP Wed
Jun 27 15:50:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
The offending commit must be later.
On Thu, Jul 5,
Here are the md5sum hashes of the files needed to install the test
kernel:
d5f16dcf0080db1268d3b3477c911cd7 linux-image-
unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb
1d7504d8e691ba64d552a2d507179882 linux-
Hello,
Thanks for putting this together. I tried to get the kernels you
built, but I'm having trouble establishing a secure (https) connection
to kernel.ubuntu.com. It looks like the server might not offer https.
Can you give me the expected hashes of the files so I can verify the
downloads?
I started a kernel bisect between v4.15.0-22 and v4.15.0-23. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
8eca6add0defde203282476d7969a7c13bbd7d91
The test kernel can be downloaded from:
I updated my BIOS and tested the -24 kernel, as was recommended. It
definitely doesn't work any better. It still has the null dereference
problem, and then it prints a bunch of smp_call_function_too_many errors,
apparently forever.
On Tue, Jun 19, 2018, 08:11 Joseph Salisbury
wrote:
> Can you
Also a good idea to update the BIOS.
--
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/1777338
Title:
Linux 4.15.0-23 crashes during the boot process with a "Unable to
handle kernel NULL
Can you see if this issue exists in the 4.15.0-24 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15010188
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.
•
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux
This also affects the mainline kernel build 4.17.0-041700.201806041953
that I was testing for another bug.
I've attached a photo of the screen with the issue occurring, in that
version.
Booting not under Xen seems to work around the issue, and the system
comes up, but that's not useful for me
30 matches
Mail list logo
