| 2023-06-20 16:05:12 |
Ioanna Alifieraki |
bug |
|
|
added bug |
| 2023-06-20 16:05:23 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Focal |
|
| 2023-06-20 16:05:23 |
Ioanna Alifieraki |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2023-06-20 16:05:23 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-06-20 16:05:23 |
Ioanna Alifieraki |
bug task added |
|
linux (Ubuntu Jammy) |
|
| 2023-06-20 16:06:04 |
Ioanna Alifieraki |
bug task added |
|
kexec-tools (Ubuntu) |
|
| 2023-06-20 16:30:05 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2023-06-20 16:30:06 |
Ubuntu Kernel Bot |
linux (Ubuntu Focal): status |
New |
Incomplete |
|
| 2023-06-20 16:30:07 |
Ubuntu Kernel Bot |
linux (Ubuntu Jammy): status |
New |
Incomplete |
|
| 2023-06-29 14:24:20 |
Ioanna Alifieraki |
description |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
[Other]
Commits to backport
JAMMY:
kernel:
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
FOCAL:
kernel (5.15 hwe kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
[Other]
Commits to backport
JAMMY:
kernel:
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
FOCAL:
kernel (5.15 hwe kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-08 14:03:21 |
Ioanna Alifieraki |
linux (Ubuntu Focal): status |
Incomplete |
Won't Fix |
|
| 2023-07-08 14:03:43 |
Ioanna Alifieraki |
kexec-tools (Ubuntu): importance |
Undecided |
Medium |
|
| 2023-07-08 14:03:45 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2023-07-08 14:03:48 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Jammy): importance |
Undecided |
Medium |
|
| 2023-07-08 14:03:50 |
Ioanna Alifieraki |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2023-07-08 14:03:54 |
Ioanna Alifieraki |
linux (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2023-07-08 14:03:56 |
Ioanna Alifieraki |
linux (Ubuntu Jammy): importance |
Undecided |
Medium |
|
| 2023-07-08 14:03:58 |
Ioanna Alifieraki |
linux (Ubuntu Jammy): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-08 14:03:59 |
Ioanna Alifieraki |
linux (Ubuntu Focal): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-08 14:04:05 |
Ioanna Alifieraki |
linux (Ubuntu Focal): assignee |
Ioanna Alifieraki (joalif) |
|
|
| 2023-07-08 14:04:08 |
Ioanna Alifieraki |
linux (Ubuntu): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-08 14:04:10 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Jammy): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-08 14:04:11 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Focal): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-08 14:04:14 |
Ioanna Alifieraki |
kexec-tools (Ubuntu): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-08 14:11:50 |
Ioanna Alifieraki |
description |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
[Other]
Commits to backport
JAMMY:
kernel:
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
FOCAL:
kernel (5.15 hwe kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
[Other]
Commits to backport
KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
kernel (5.19 kernel) :
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Kinetic |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
bug task added |
|
kexec-tools (Ubuntu Kinetic) |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
bug task added |
|
linux (Ubuntu Kinetic) |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Mantic |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
bug task added |
|
kexec-tools (Ubuntu Mantic) |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
bug task added |
|
linux (Ubuntu Mantic) |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
bug task added |
|
kexec-tools (Ubuntu Lunar) |
|
| 2023-07-08 14:14:23 |
Ioanna Alifieraki |
bug task added |
|
linux (Ubuntu Lunar) |
|
| 2023-07-08 14:15:28 |
Ioanna Alifieraki |
linux (Ubuntu Kinetic): status |
New |
Won't Fix |
|
| 2023-07-08 14:15:45 |
Ioanna Alifieraki |
bug task deleted |
linux (Ubuntu Mantic) |
|
|
| 2023-07-08 14:15:51 |
Ioanna Alifieraki |
bug task deleted |
linux (Ubuntu Lunar) |
|
|
| 2023-07-08 14:15:58 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Kinetic): status |
New |
Won't Fix |
|
| 2023-07-08 14:25:32 |
Ioanna Alifieraki |
description |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
[Other]
Commits to backport
KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
kernel (5.19 kernel) :
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
[Other]
Commits to backport
*** MANTIC:
kernel 6.3: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
***LUNAR:
kernel 6.2: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
*** JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Instead the 5.15-hwe kernel can be used.
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-08 15:13:09 |
Ioanna Alifieraki |
description |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
[Other]
Commits to backport
*** MANTIC:
kernel 6.3: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
***LUNAR:
kernel 6.2: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
*** JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Instead the 5.15-hwe kernel can be used.
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
KEXEX - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
KEXEC - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
*** MANTIC:
kernel 6.3: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
***LUNAR:
kernel 6.2: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
*** JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Instead the 5.15-hwe kernel can be used.
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-08 15:13:43 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Lunar): importance |
Undecided |
Medium |
|
| 2023-07-08 15:13:43 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Lunar): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-08 15:33:06 |
Ioanna Alifieraki |
attachment added |
|
lp2024479_focal.debdiff https://bugs.launchpad.net/ubuntu/lunar/+source/kexec-tools/+bug/2024479/+attachment/5684764/+files/lp2024479_focal.debdiff |
|
| 2023-07-08 15:33:46 |
Ioanna Alifieraki |
attachment added |
|
lp2024479_jammy.debdiff https://bugs.launchpad.net/ubuntu/lunar/+source/kexec-tools/+bug/2024479/+attachment/5684765/+files/lp2024479_jammy.debdiff |
|
| 2023-07-08 15:34:37 |
Ioanna Alifieraki |
attachment added |
|
lp2024479_lunar.debdiff https://bugs.launchpad.net/ubuntu/lunar/+source/kexec-tools/+bug/2024479/+attachment/5684766/+files/lp2024479_lunar.debdiff |
|
| 2023-07-08 15:35:21 |
Ioanna Alifieraki |
attachment added |
|
lp2024479_mantic.debdiff https://bugs.launchpad.net/ubuntu/lunar/+source/kexec-tools/+bug/2024479/+attachment/5684767/+files/lp2024479_mantic.debdiff |
|
| 2023-07-08 15:35:53 |
Ioanna Alifieraki |
bug |
|
|
added subscriber Support Engineering Sponsors |
| 2023-07-08 15:36:19 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Focal): status |
New |
In Progress |
|
| 2023-07-08 15:36:25 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Jammy): status |
New |
In Progress |
|
| 2023-07-08 15:36:33 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Lunar): status |
New |
In Progress |
|
| 2023-07-08 15:36:42 |
Ioanna Alifieraki |
kexec-tools (Ubuntu Mantic): status |
New |
In Progress |
|
| 2023-07-08 16:14:44 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2023-07-08 16:14:44 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Terry Rudd |
| 2023-07-08 16:14:50 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-07-10 12:53:09 |
Mauricio Faria de Oliveira |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-07-10 13:04:15 |
Mauricio Faria de Oliveira |
kexec-tools (Ubuntu Mantic): status |
In Progress |
Incomplete |
|
| 2023-07-10 13:04:27 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Mauricio Faria de Oliveira |
| 2023-07-10 13:05:20 |
Mauricio Faria de Oliveira |
tags |
patch |
patch se-sponsor-mfo |
|
| 2023-07-10 13:08:25 |
Mauricio Faria de Oliveira |
description |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
To address this issue the following upstrem commits are needed:
From the kernel side :
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
From kexec-tools
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
KEXEX - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
KEXEC - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
*** MANTIC:
kernel 6.3: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
***LUNAR:
kernel 6.2: not affected
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
*** JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
*** FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Instead the 5.15-hwe kernel can be used.
kexec:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
[Fix]
To address this issue the following upstrem commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
KEXEX - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
KEXEC - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
- MANTIC:
kernel 6.3: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- LUNAR:
kernel 6.2: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
- JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Instead the 5.15-hwe kernel can be used.
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-10 14:05:58 |
Christian Ehrhardt |
kexec-tools (Ubuntu Mantic): status |
Incomplete |
Fix Committed |
|
| 2023-07-10 15:23:29 |
Tim Gardner |
linux (Ubuntu Jammy): status |
Incomplete |
In Progress |
|
| 2023-07-10 17:10:43 |
Launchpad Janitor |
kexec-tools (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2023-07-11 18:16:16 |
Ioanna Alifieraki |
attachment added |
|
lp2024479_focal-v2.debdiff https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685457/+files/lp2024479_focal-v2.debdiff |
|
| 2023-07-11 18:17:13 |
Ioanna Alifieraki |
attachment added |
|
lp2024479_jammy-v2.debdiff https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685458/+files/lp2024479_jammy-v2.debdiff |
|
| 2023-07-11 18:17:49 |
Ioanna Alifieraki |
attachment added |
|
lp2024479_lunar-v2.debdiff https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685459/+files/lp2024479_lunar-v2.debdiff |
|
| 2023-07-12 13:22:21 |
Mauricio Faria de Oliveira |
description |
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
[Fix]
To address this issue the following upstrem commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15:
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
KEXEX - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
KEXEC - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
- MANTIC:
kernel 6.3: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- LUNAR:
kernel 6.2: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- KINETIC: WON'T FIX
Kinetic won't be fixed as it EOLs soon.
- JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Instead the 5.15-hwe kernel can be used.
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Impact]
kdump fails on arm64, on machines with a lot of memory when offset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel region.
[Fix]
To address this issue the following upstream commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.
[Test Plan]
You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15 - Jammy (and Focal via the HWE kernel):
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
kexec-tools - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
kexec-tools - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
- MANTIC:
kernel 6.3: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- LUNAR:
kernel 6.2: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- KINETIC: WON'T FIX
Kinetic won't be fixed as it is EOL soon.
- JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Kernel 5.15 (HWE): Fixed via Jammy.
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-12 13:24:06 |
Mauricio Faria de Oliveira |
bug task added |
|
linux-hwe-5.15 (Ubuntu) |
|
| 2023-07-12 13:24:22 |
Mauricio Faria de Oliveira |
linux-hwe-5.15 (Ubuntu Jammy): status |
New |
Invalid |
|
| 2023-07-12 13:24:32 |
Mauricio Faria de Oliveira |
linux-hwe-5.15 (Ubuntu Kinetic): status |
New |
Invalid |
|
| 2023-07-12 13:24:40 |
Mauricio Faria de Oliveira |
linux-hwe-5.15 (Ubuntu): status |
New |
Invalid |
|
| 2023-07-12 13:24:51 |
Mauricio Faria de Oliveira |
linux-hwe-5.15 (Ubuntu Focal): status |
New |
In Progress |
|
| 2023-07-12 13:25:14 |
Mauricio Faria de Oliveira |
linux-hwe-5.15 (Ubuntu Focal): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2023-07-12 13:25:39 |
Mauricio Faria de Oliveira |
linux (Ubuntu): status |
Incomplete |
Invalid |
|
| 2023-07-12 13:25:39 |
Mauricio Faria de Oliveira |
linux (Ubuntu): assignee |
Ioanna Alifieraki (joalif) |
|
|
| 2023-07-12 13:25:50 |
Mauricio Faria de Oliveira |
linux (Ubuntu): importance |
Medium |
Undecided |
|
| 2023-07-12 13:25:59 |
Mauricio Faria de Oliveira |
linux (Ubuntu Focal): importance |
Medium |
Undecided |
|
| 2023-07-12 13:26:09 |
Mauricio Faria de Oliveira |
linux-hwe-5.15 (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2023-07-12 15:22:31 |
Mauricio Faria de Oliveira |
description |
[Impact]
kdump fails on arm64, on machines with a lot of memory when offset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel region.
[Fix]
To address this issue the following upstream commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.
[Test Plan]
You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump and trigger a crash.
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
[Regression Potential]
KERNEL 5.15 - Jammy (and Focal via the HWE kernel):
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
kexec-tools - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
kexec-tools - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
- MANTIC:
kernel 6.3: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- LUNAR:
kernel 6.2: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- KINETIC: WON'T FIX
Kinetic won't be fixed as it is EOL soon.
- JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Kernel 5.15 (HWE): Fixed via Jammy.
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Impact]
kdump fails on arm64, on machines with a lot of memory when offset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel region.
[Fix]
To address this issue the following upstream commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.
[Test Plan]
You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump, configure the crash kernel size, and trigger a crash.
- Failing scenario (crashkernel >= 4G, without offset "@<address>"):
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
- Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')
This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal).
[Regression Potential]
KERNEL 5.15 - Jammy (and Focal via the HWE kernel):
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
kexec-tools - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
kexec-tools - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
- MANTIC:
kernel 6.3: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- LUNAR:
kernel 6.2: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- KINETIC: WON'T FIX
Kinetic won't be fixed as it is EOL soon.
- JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Kernel 5.15 (HWE): Fixed via Jammy.
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-12 19:50:05 |
Mauricio Faria de Oliveira |
summary |
kdump fails on arm64 when offset is not specified |
kdump fails on big arm64 systems when offset is not specified |
|
| 2023-07-14 19:33:47 |
Steve Langasek |
kexec-tools (Ubuntu Lunar): status |
In Progress |
Fix Committed |
|
| 2023-07-14 19:33:48 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-07-14 19:33:50 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2023-07-14 19:33:54 |
Steve Langasek |
tags |
patch se-sponsor-mfo |
patch se-sponsor-mfo verification-needed verification-needed-lunar |
|
| 2023-07-14 19:44:26 |
Steve Langasek |
kexec-tools (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-07-14 19:44:32 |
Steve Langasek |
tags |
patch se-sponsor-mfo verification-needed verification-needed-lunar |
patch se-sponsor-mfo verification-needed verification-needed-jammy verification-needed-lunar |
|
| 2023-07-14 19:55:25 |
Steve Langasek |
kexec-tools (Ubuntu Focal): status |
In Progress |
Incomplete |
|
| 2023-07-14 20:48:29 |
Mauricio Faria de Oliveira |
kexec-tools (Ubuntu Focal): status |
Incomplete |
In Progress |
|
| 2023-07-19 09:39:14 |
Ubuntu Kernel Bot |
tags |
patch se-sponsor-mfo verification-needed verification-needed-jammy verification-needed-lunar |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-needed verification-needed-jammy verification-needed-lunar |
|
| 2023-07-19 10:22:25 |
Robie Basak |
kexec-tools (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2023-07-19 10:22:28 |
Robie Basak |
tags |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-needed verification-needed-jammy verification-needed-lunar |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-needed verification-needed-focal verification-needed-jammy verification-needed-lunar |
|
| 2023-07-20 14:24:03 |
Ioanna Alifieraki |
tags |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-needed verification-needed-focal verification-needed-jammy verification-needed-lunar |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-done-lunar verification-needed verification-needed-focal verification-needed-jammy |
|
| 2023-07-20 14:55:36 |
Ioanna Alifieraki |
description |
[Impact]
kdump fails on arm64, on machines with a lot of memory when offset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel region.
[Fix]
To address this issue the following upstream commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.
[Test Plan]
You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump, configure the crash kernel size, and trigger a crash.
- Failing scenario (crashkernel >= 4G, without offset "@<address>"):
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
- Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')
This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal).
[Regression Potential]
KERNEL 5.15 - Jammy (and Focal via the HWE kernel):
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
kexec-tools - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
kexec-tools - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
- MANTIC:
kernel 6.3: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- LUNAR:
kernel 6.2: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- KINETIC: WON'T FIX
Kinetic won't be fixed as it is EOL soon.
- JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Kernel 5.15 (HWE): Fixed via Jammy.
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
[Impact]
kdump fails on arm64, on machines with a lot of memory when offset is not specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel region.
[Fix]
To address this issue the following upstream commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou <chenzhou10@huawei.com>
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.
[Test Plan]
You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
Install linux-crashdump, configure the crash kernel size, and trigger a crash.
1) Failing scenario (crashkernel >= 4G, without offset "@<address>"):
It won't work unless the offset is specified because the memory crashkernel cannot be allocated.
With the patches applied it works as expected without having to specify the offset.
2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')
This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal).
[Regression Potential]
KERNEL 5.15 - Jammy (and Focal via the HWE kernel):
To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details.
All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel.
This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality.
However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well.
kexec-tools - FOCAL:
To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick.
Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
Commit cf977b1af9ec67fab adds code without altering current functionality.
Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features.
kexec-tools - JAMMY, LUNAR, MANTIC:
Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump.
[Other]
Commits to backport
- MANTIC:
kernel 6.3: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- LUNAR:
kernel 6.2: not affected
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- KINETIC: WON'T FIX
Kinetic won't be fixed as it is EOL soon.
- JAMMY:
kernel (5.15 kernel):
a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones
a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified
4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed
5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64
944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
- FOCAL:
Kernel 5.4: Won't fix because of high regression potential.
Kernel 5.15 (HWE): Fixed via Jammy.
kexec-tools:
b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions
2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem
cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions
f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions
64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available)
f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes |
|
| 2023-07-21 08:06:03 |
Ioanna Alifieraki |
tags |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-done-lunar verification-needed verification-needed-focal verification-needed-jammy |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-done-jammy verification-done-lunar verification-needed verification-needed-focal |
|
| 2023-07-24 13:22:14 |
Ioanna Alifieraki |
tags |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-done-jammy verification-done-lunar verification-needed verification-needed-focal |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-done verification-done-focal verification-done-jammy verification-done-lunar |
|
| 2023-07-26 13:09:12 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-07-26 13:10:09 |
Launchpad Janitor |
kexec-tools (Ubuntu Lunar): status |
Fix Committed |
Fix Released |
|
| 2023-07-26 13:10:13 |
Launchpad Janitor |
kexec-tools (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-07-26 13:10:16 |
Launchpad Janitor |
kexec-tools (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2023-08-02 06:37:17 |
Roxana Nicolescu |
linux (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-08-16 16:16:27 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-azure patch se-sponsor-mfo verification-done verification-done-focal verification-done-jammy verification-done-lunar |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-lunar verification-needed-jammy-linux |
|
| 2023-08-18 11:57:49 |
Ioanna Alifieraki |
tags |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-lunar verification-needed-jammy-linux |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
linux-hwe-5.15 (Ubuntu Focal): status |
In Progress |
Fix Released |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2022-40982 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-20593 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-21400 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-2898 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-31084 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-3609 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-3610 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-3611 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-3776 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-3777 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-3995 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-4004 |
|
| 2023-09-04 12:31:49 |
Launchpad Janitor |
cve linked |
|
2023-4015 |
|
| 2023-09-04 12:50:34 |
Mauricio Faria de Oliveira |
removed subscriber Mauricio Faria de Oliveira |
|
|
|
| 2023-09-05 19:50:55 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-jammy-linux-nvidia-tegra |
|
| 2023-09-08 23:46:26 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-jammy-linux-nvidia-tegra |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra |
|
| 2023-09-10 20:51:30 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra |
kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra |
|
| 2023-09-11 10:24:09 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra |
kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-raspi |
|
| 2023-09-15 17:51:40 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-raspi |
kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi |
|
| 2023-09-15 23:15:15 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi |
kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi |
|
| 2023-10-03 20:42:08 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi |
kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 kernel-spammed-jammy-linux-xilinx-zynqmp-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi verification-needed-jammy-linux-xilinx-zynqmp |
|
| 2023-10-07 19:58:24 |
Mauricio Faria de Oliveira |
linux (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-03-01 06:19:37 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 kernel-spammed-jammy-linux-xilinx-zynqmp-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi verification-needed-jammy-linux-xilinx-zynqmp |
kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 kernel-spammed-focal-linux-riscv-5.15-v2 kernel-spammed-jammy-linux-azure kernel-spammed-jammy-linux-intel-iotg-v2 kernel-spammed-jammy-linux-mtk-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-raspi-v2 kernel-spammed-jammy-linux-v2 kernel-spammed-jammy-linux-xilinx-zynqmp-v2 patch se-sponsor-mfo verification-done-focal verification-done-jammy verification-done-jammy-linux verification-done-lunar verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-mtk verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi verification-needed-jammy-linux-xilinx-zynqmp |
|
