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
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
** 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.
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
The fix has been released on Xenial ESM (kernel version 4.4.0-224.257).
$ git log --oneline -1 341e4f5e9e07
341e4f5e9e07 UBUNTU: SAUCE: fuse: fix bad !inode in fuse_direntplus_link()
$ git describe --contains 341e4f5e9e07
Ubuntu-4.4.0-224.257~6
** Changed in: linux (Ubuntu Xenial)
Status
ack VM
cheers,
Mauricio
** Changed in: dmidecode (Ubuntu Kinetic)
Status: In Progress => Fix Released
** Changed in: dmidecode (Ubuntu Kinetic)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: dmidecode (Ubuntu Jammy)
Assignee: (unassigned) => Ma
Verification done on jammy-proposed.
1) a system/hardware vendor tested and confirmed that:
- systems with SMBIOS 3.5 report the new fields as expected;
- systems with SMBIOS < 3.4 keep the old fields as expected.
2) I tested on several physical and virtual machines, and:
- systems with
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
--
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/1
** 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/1883962
Title:
apparmor reference leak causes refcount_t overflo
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1884766
Title:
use-after-free in af_alg_accept() due to bh_lock_so
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1873074
Title:
kernel panic hit by kube-proxy iptables-save/restor
** Changed in: linux (Ubuntu)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
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/1863044
Title:
qla2xxx no longer dete
Public bug reported:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
* The modprob
(unassigned) => Mauricio Faria de Oliveira (mfo)
** Description changed:
[Impact]
- * The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
-errors during boot with the FIPS OpenSSL library installed
-(but those don't cause issues), when it runs modprobe with
-request_modu
[Focal/FIPS][PATCH 0/4] Fix kernel BUG/Oops errors from modprobe while
the DRBG has not yet initialized (focal/fips-updates)
--
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/1981487
Title:
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1981487
Title:
kernel BUG/Oops errors from modprobe while the DRBG has n
** Description changed:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
For reference purposes, I'm attaching a dmesg log with debugging boot
options to:
- print initcalls entry/return
- print calls to __request_module() while the FIPS DRBG is uninitialized
Method / boot options:
fips=1
random.fips_urandom_drbg_crypto_noload=0
random.fips_ur
Hi Joao,
Thanks for your work on this bug and the SRU.
I reviewed the LP bug and packaging changes in your PPA.
Things are almost good to go; congrats!
Please ack/adjust these points and let me know, so I can review/upload.
cheers,
Mauricio
...
LP bug review: LP#2081611
---
- Link [1] should
Hello Joao, or anyone else affected,
Accepted dmidecode into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/dmidecode/3.3-3ubuntu0.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Noble should be good for release, except for an i386 autopkgtest that
apparently never finished [1]:
autopkgtest for crmsh/4.6.0-1ubuntu2: amd64: Pass, arm64: Pass, armhf:
Pass, i386: Test in progress, ppc64el: Pass, s390x: Pass
I triggered a rerun for it; hopefully it may finish during my SRU
va
The verification of the Stable Release Update for dmidecode has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
It passed.
crmsh [noble/i386]
Version TriggersEnv DateDurationRequester
Result UUID
4.6.0-1ubuntu2 dmidecode/3.5-3ubuntu0.12024-11-25 22:04:36 UTC
0h 13m 34s mfo pass855eb873-69a4-412d-89de-dd49edac061f
log ar
The update_excuses page for jammy is currently outdated (Dec. 4th)
and I'm asking for it to be looked at by the responsible team.
Considering what is already there and in the pending-sru page,
plus other checks, only autopkgtests still need to be verified.
I did that manually with the autopkgtest
Hello Danilo, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Nick, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Changed in: linux (Ubuntu Focal)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
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/1981487
Title:
kernel BUG/Oops err
701 - 727 of 727 matches
Mail list logo
