** 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.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-aws Boot failure downgradin
This bug is awaiting verification that the linux-kvm/4.15.0-1102.104
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,
This bug was fixed in the package linux - 4.15.0-161.169
---
linux (4.15.0-161.169) bionic; urgency=medium
* bionic/linux: 4.15.0-161.169 -proposed tracker (LP: #1947358)
* Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
r5.metal (LP: #1946149)
- SA
I confirm that bionic/linux 4.15.0-161.169 and bionic/linux-aws
4.15.0-1114.121 are not experiencing the reported boot issues on AWS
r5.metal or on any other platform/instance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
** 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/1946149
Title:
Bionic/linux-aws Boot failure downgrading f
** Also affects: linux-aws (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux-aws (Ubuntu Bionic)
Status: New => In Progress
** Package changed: linux-aws (Ubuntu) => linux (Ubuntu)
**
** Description changed:
- When creating an r5.metal instance on AWS, the default kernel is
- bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.
+
+ [ Impact ]
+ The bionic 4.15 kernels are failing to boot on r5.me
As I was bisecting the commits, I was attempting to take advantage of
parallelism. While my test kernel was building I would deploy a clean
AWS r5.metal instance. I started seeing test kernels boot that I
wouldn't expect to boot. So I decided as a sanity test, I would deploy
an r5.metal instance,
Hi Mauricio,
Thanks for getting this info. This is very helpful! I see a few
potential patches between 4.15.0-159.167 and 4.15.0-160.168 that could
be related to the hang. This will help greatly with the bisect.
Ian
--
You received this bug notification because you are a member of Kernel
Pac
Steps to reproduce:
---
Ubuntu 18.04 image in AWS r5.metal instance type.
$ lsb_release -cs
bionic
$ dmesg | grep DMI:
[0.00] DMI: Amazon EC2 r5.metal/Not Specified, BIOS 1.0 10/16/2017
$ uname -rv
5.4.0-1045-aws #47~18.04.1-Ubuntu SMP Tue Apr 13 15:58:14 UTC 2021
$ sudo add-apt-reposi
** Attachment added: "serial-console-output.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+attachment/5532619/+files/serial-console-output.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
We've got a serial console log from AWS Support through our Support team
(special thanks to Pedro Principeza and our former colleague Mark Thomas.)
The problem is definitely not the ext4/jbd2 patchset as suspected
(although it's unclear how reverting it caused the kernel to boot;
maybe build envir
Hey Kleber,
Thanks for confirming.
I guess there might be something wrong with the boot process on r5.metal,
specifically:
- there's no issue with kexec boot, just with normal boot (same code and
from/to versions)
- there's no issue with normal boot on similar instance types (r5d.metal,
r5.24x
Hi Mauricio,
We are seeing the issue only on r5.metal.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-
Hi Kleber,
Thanks for the info.
The impact on bionic/generic is also exclusively on aws r5.metal or
broader?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/li
This issue is also affecting the bionic/linux generic kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-aws Boot failure downgrading from Bionic/linu
Mauricio,
Interesting update, I agree that we need more info as to what the state
is when the instance won't boot switching to the new 4.15 kernel. I'll
check with my team in the morning and see if we can get additional info
from AWS
I was trying a few more scenarios this evening the first being
Ian,
Do you/team have contacts in here or AWS that could help with that?
I think that other lines of investigation now, after our findings
and apparent inconsistencies, would be based on speculation, and
we're better trying to get real information/logs from the system
with AWS Support.
cheers,
M
Today I wanted to try and instrument the boot process a bit,
since we have no serial console in the nitro metal instances.
I was looking for pstore_blk (hoping we could panic_on_warn
or panic_on_oops), but it's only available in 5.8+ it seems.)
So I decided to start with grub, and keep a progress
Just want to add an update. I haven't been able to replicate
successfully booting 4.15.0-1113-aws from 5.4.0-1058-aws, so I'm
questioning whether I made a mistake the time I thought it was
successful.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Thanks for the in-depth update Mauricio! Is there any investigation
you'd like me to specifically target?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-
For the record, 4.15.0-1113-aws works in r5.metal w/ kexec.
Booted it 10 times successfully from both 5.4.0-1058-aws
and 4.15.0-1113-aws (itself.)
(not that it was expected to make a difference as the issue
happens on normal boot, which doesn't have previous kernel.)
Right after that, in the sam
BTW, do you know of the differences between r5.metal and r5.24xlarge?
Per the specs they seem to be the same as in cpu/ram/nic/_nvme_ storage,
but differ in baremetal vs nitro hypervisor?
The reason I ask is because downgrading from 5.4.0-1056-aws to 4.15.0-1113-aws
worked/booted fine on r5.24xla
It looks like it's not a problem with the patchset in general,
maybe it's specific to aws 4.15?
The patchset is in 5.4.0-1058-aws and it booted fine here too.
I'll check the patchset in 4.15.0-1113-aws.
A difference from your comment is that I could _not_ boot it
after 5.4.0-1058-aws, which worke
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.
If I remove these patches the instance correctly boots the 4.15 k
Confirmed it does work to first upgrade bionic/linux-5.4 from
5.4.0-1056-aws to 5.4.0-1058-aws and then update to 4.15.0-1113-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Hey Ian, thanks for the bug report! I'm checking this on AWS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-aws Boot failure downgrading from Bionic/linu
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel.
+ aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.
If
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel.
If I remove these patches the instance correctly boots the 4.15 kerne
Have been unable to capture a stack trace using 'aws get-console-
output'. Enabled kdump and was unable to replicate the failed boot,
which makes this feel like a race condition with NVME.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel.
+
+ If I remove these patches the instance correctly boots the 4.15 kerne
31 matches
Mail list logo
