Mantic and Jammy built successfully in all supported architectures.
(riscv64 fails, but it also fails on mantic/jammy-release; it's OK.)
Uploaded!
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
** Description changed:
[Impact]
- Linux kernel 6.2 includes patches with structural changes that may render the
crash utility unable to parse the dump file.
+ Linux kernel 6.2 includes patches with structural changes that may render the
crash utility in Mantic (release kernel 6.5) and Jammy
Jammy: patches 0001-0012 look good too!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
kernel 6.2
Partial review of the Jammy debdiff.
(Still in progress.)
Started with Jammy's patches 0012-0036, which are Mantic's patches 0001-0024
(already reviewed).
Most patches are identical, and some have context-line changes, as expected
(8.0.2/8.0.0 delta).
Just had a few changes.
$ for ((i=1;
Today, I tackled the Mantic debdiff (made only a few changes; below).
It's now currently building in a PPA for all supported architectures,
(ppa:mfo/lp2038249) and if all goes well I will upload it to Mantic.
Thanks!
Mauricio
---
All 24 commits are included in Noble (12 in 8.0.4 and 12 in
** Description changed:
[Impact]
Linux kernel 6.2 includes patches with structural changes that may render the
crash utility unable to parse the dump file.
==
d122019bf061 mm: Split slab into its own type
401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
crash 8.0.4 is available in noble (bug 2047861); checking the stable
releases' debdiffs.
** Changed in: crash (Ubuntu Noble)
Status: Fix Committed => Fix Released
** Description changed:
[Impact]
Linux kernel 6.2 includes patches with structural changes that may render the
crash
Marking Lunar as Won't Fix (EOL).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
kernel 6.2
Status
Updated the SRU template as requested in comment #11 with the detailed
test plans provided in comments #16-#20.
** Changed in: crash (Ubuntu Lunar)
Status: In Progress => Won't Fix
** Changed in: crash (Ubuntu Lunar)
Importance: Medium => Undecided
** Changed in: crash (Ubuntu Lunar)
Reviewed zfs-linux on mantic/jammy/focal-unapproved for acceptance.
They all look good to me (notes below, in addition to usual checks),
but I'll ask for another reviewer to provide input too, as it's ZFS.
(But I did want to provide some assistance in this long-running SRU.)
Thanks,
Mauricio
** Description changed:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport
Hey Chris,
> ... the primary way that users get zfs in Ubuntu is via the module built with
> the *kernel* image.
> ... fixing that requires a zfs-linux upload and then a further kernel upload
> to pull in the new zfs.
Yes, fixing the zfs modules shipped with the kernel packages require
** Changed in: zfs-linux (Ubuntu Lunar)
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
crash 8.0.4 accepted to noble-proposed, marking as Fix Committed
https://launchpad.net/ubuntu/+source/crash/8.0.4-1ubuntu1
** Also affects: crash (Ubuntu Noble)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Changed in: crash (Ubuntu Noble
The crash 8.0.4 merge in bug 2047861 looks good, it passed
autopkgtests/manual tests, and is now waiting on review/sponsoring for
Noble.
Once accepted/released to Noble, this should unblock the SRUs (which have
patches from 8.0.4).
I'll continue the SRU debdiff reviews for now.
--
You received
Tested in dump file form in s390x; working.
s390x
-
vm
SERIES=noble
ARCH=s390x
DISK=${SERIES}_${ARCH}.qcow2
wget
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b
Autopkgtests (live system form) PASS in amd64, arm64, ppc64el, s390x (armhf
skipped) [comment #3]
Manual tests (dump file form) PASS in amd64, arm64, ppc64el, s390x [comments
#4, #5, #6, #7]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Tested in dump file form in ppc64el; working.
ppc64el
---
vm
SERIES=noble
ARCH=ppc64el
DISK=${SERIES}_${ARCH}.qcow2
wget
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b
Tested in dump file form in arm64; working.
arm64
-
vm
SERIES=noble
ARCH=arm64
DISK=${SERIES}_${ARCH}.qcow2
wget
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b
** Merge proposal linked:
https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+merge/458192
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2047861
Title:
Merge crash
Autopkgtests above are in live system form.
Tested in dump file form in amd64; working.
# crash ./usr/lib/debug/boot/vmlinux-*-generic /var/crash/*/dump.*
...
KERNEL: ./usr/lib/debug/boot/vmlinux-6.6.0-14-generic
DUMPFILE:
Autopkgtests PASS from PPA:
$ DIR='https://autopkgtest.ubuntu.com/results/autopkgtest-noble-mfo-
lp2047861-noble-crash'
$ curl -sf "$DIR/?format=plain" | grep result.tar | while read TAR; do echo
"ARCH: $(echo $TAR | cut -d/ -f2)"; curl -sf "$DIR/$TAR" | tar xO summary; done
ARCH: amd64
live
Verification done for mantic-proposed.
All matches of the string are correct.
$ lxc launch ubuntu:mantic mantic-zed
$ lxc shell mantic-zed
# add-apt-repository -y -p proposed
# apt install -t mantic-proposed -y zfs-zed
# dpkg -s zfs-zed | grep Version:
Version: 2.2.0-0ubuntu1~23.10.1
# grep
Started the work to merge crash 8.0.4 in bug 2047861.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
Merge is in git branch
https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+ref/merge-lp2047861-noble
Building/testing from PPA
https://launchpad.net/~mfo/+archive/ubuntu/lp2047861-noble-crash
Still in progress.
--
You received this bug notification because you are a member of
Work in progress.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2047861
Title:
Merge crash 8.0.4-1 into Noble
Status in crash package in Ubuntu:
In Progress
Bug description:
$
Faria de Oliveira (mfo)
Status: In Progress
** Changed in: crash (Ubuntu)
Status: New => In Progress
** Changed in: crash (Ubuntu)
Importance: Undecided => Medium
** Changed in: crash (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You
ogress => Incomplete
** Changed in: crash (Ubuntu)
Assignee: Chengen Du (chengendu) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title
I will stage this to mantic with an upload + block-proposed-mantic tag.
The mantic unapproved queue already has zfs-linux 2.2.2-0ubuntu1~23.10,
but it seems it is not going to be accepted per bug 2044657 comment 46.
If that bug gets cherry-pick fixes as requested, that should be simple
to
Testing for Mantic:
mantic-updates:
$ rmadison -a source zfs-linux -s mantic-updates
zfs-linux | 2.2.0-0ubuntu1~23.10 | mantic-updates | source
$ dpkg -s zfs-zed | grep Version:
Version: 2.2.0-0ubuntu1~23.10
$ grep ZED_POWER_OFF_ENCLO
noble:
$ dpkg -s zfs-zed | grep Version:
Version: 2.2.2-0ubuntu1
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
test package:
$ dpkg-deb -x zfs-zed_2.2.2-0ubuntu2_amd64.deb deb
$ grep
Subscribing ~ubuntu-sponsors for review/sponsoring to Noble.
(I can handle the upload to mantic later.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2046082
Title:
zed.rc: typo in
Ubuntu:
$ rmadison -a source zfs-linux
...
zfs-linux | 0.8.3-1ubuntu12| focal | source
zfs-linux | 0.8.3-1ubuntu12.16 | focal-security | source
zfs-linux | 0.8.3-1ubuntu12.16 | focal-updates | source
zfs-linux | 2.1.2-1ubuntu3 | jammy | source
Upstream:
$ git log --oneline origin/zfs-2.2-release -- cmd/zed/zed.d/zed.rc | grep 'zed:
Add zedlet to power off slot when drive is faulted'
d19304ffeec5 zed: Add zedlet to power off slot when drive is faulted
$ git describe --contains d19304ffeec5
zfs-2.2.0-rc4~14
$ git log --oneline
in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
** Affects: zfs-linux (Ubuntu)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Affects: zfs-linux (Ubuntu Mantic)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Hi Dimitri,
Thanks for the details of the test plan execution!
That covers the kernel module/filesystem code quite well, thanks,
and there's the userspace tooling changes left, as you mentioned.
> In practice this SRU is already released to most users via LXD and via kernel
> upgrades.
> The
Hi Dimitri,
Could you please provide more evidence/details of the test plan
execution, considering this SRU is related to a filesystem?
```
[ Test Plan ]
* autopkgtest pass
* kernel regression zfs testsuite pass
* zsys integration test pass
* LXD support retested
```
The autopkgtests
** Merge proposal linked:
https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+merge/455464
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2042357
Title:
Merge crash
** Merge proposal linked:
https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+merge/455353
** Description changed:
- Work in progress; rebasing on 8.0.3+ds1-3, and testing.
+ Merge Request / git-ubuntu:
+
+
amd64
-
vm
lxc launch --vm -c limits.cpu=2 -c limits.memory=2GiB
ubuntu-daily:noble noble-vm
lxc shell noble-vm
# uname -rv
6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 7 01:35:40 UTC
2023
kdump-tools
sudo apt update && apt install -y
armhf
(fails to kexec to the crash kernel, anyway, for doc purposes)
-
vm
sudo modprobe nbd
sudo qemu-nbd -c /dev/nbd0 noble-server-cloudimg-armhf.img
mkdir mnt
sudo mount /dev/nbd0p16 mnt
sudo cp mnt/vmlinuz-*-generic mnt/initrd.img-*-generic .
common for arm64, ppc64el, s390x, armhf:
---
cloud-init data iso:
echo 'local-hostname: test' >meta-data
PUBKEY=$(cat $HOME/.ssh/id_rsa.pub)
cat
ppc64el
---
vm
SERIES=noble
ARCH=ppc64el
DISK=${SERIES}_${ARCH}.qcow2
wget
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b ${SERIES}-server-cloudimg-${ARCH}.img -f
qcow2 $DISK 8G
arm64
-
vm
SERIES=noble
ARCH=arm64
DISK=${SERIES}_${ARCH}.qcow2
wget
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b ${SERIES}-server-cloudimg-${ARCH}.img -f
qcow2 $DISK 8G
s390x
-
vm
sudo apt install -y qemu-system-s390x
qemu-system-s390x \
-machine s390-ccw-virtio -cpu qemu \
\
-smp cpus=2 -m 2048 \
-nodefaults -no-user-config \
-nographic -serial stdio \
\
-drive
The test packages in `ppa:mfo/noble-crash-v2` have worked well
(ie, crash can actually start, and is able to get a backtrace)
in amd64, arm64, ppc64el, and s390x (armhf couldn't even kexec).
This is a lot better than the current state (crash quits early)
in all these architectures, so I will move
Upstream patch 'Support-module-memory-layout-change-on-Linux-6.4'
is required to crash to open a 6.5 kernel crashdump on Noble too.
# crash ./usr/lib/debug/boot/vmlinux-*-generic /var/crash/*/dump.*
...
crash: invalid structure member offset: module_core_size
FILE: kernel.c LINE: 3781
Testing on amd64, arm64, armhf, ppc64el, and s390x with QEMU VMs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2042357
Title:
Merge crash 8.0.3+ds1-3 into Noble
Status in crash
The package built successfully in all architectures (amd64, arm64,
armhf, ppc64el, s390x).
The PPA does not have riscv64 enabled, but it crash/riscv64 FTBFS in
mantic-release,
which is in noble now, so even if it fails, it is not a regression from latest
state.
--
You received this bug
Merged with Debian (8.0.3+ds1-3), now building (ppa:mfo/crash-noble).
** Summary changed:
- Merge crash 8.0.3 into Noble
+ Merge crash 8.0.3+ds1-3 into Noble
** Description changed:
- Work in progress; rebasing on 8.0.3+ds1-3, and testing.
+ Work in progress; rebased on 8.0.3+ds1-3, now
** Attachment added: "dm_fake_dev.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5716855/+files/dm_fake_dev.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
- 2023/10/31: please do not merge 8.0.3-1 yet (issue with .orig tarball)
-
- Work in progress; testing changes on PPA.
+ Work in progress; rebasing on 8.0.3+ds1-3, and testing.
Debian bugs:
https://bugs.debian.org/1054805
Please update crash to 8.0.3
Debian crash 8.0.3+ds1-3 [1] addressed the gdb tarball issue.
I'll update the merge, and proceed with build and tests.
[1] https://tracker.debian.org/news/1475695/accepted-
crash-803ds1-3-source-into-unstable/
--
You received this bug notification because you are a member of Kernel
Packages,
** Description changed:
+ 2023/10/31: DO NOT MERGE 8.0.3-1 yet (issue with .orig tarball)
+
Work in progress; testing changes on PPA.
Debian bugs:
https://bugs.debian.org/1054805
Please update crash to 8.0.3
https://bugs.debian.org/1055117
FTBFS: crash 8.0.3-1 is missing
2]
* Added changes:
- d/p/0002-Fix-compilation-error-due-to-new-strlcpy-function.patch:
Fix FTBFS due to strlcpy() introduced in glibc 2.38.
crash (8.0.3-1) unstable; urgency=medium
* New upstream (Closes: #1054805)
* https://github.com/crash-utility/crash/compare/8.0.2...8.0.3
** Bug watch added: Debian Bug tracker #1054805
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054805
** Also affects: crash via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054805
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1055117
** Description changed:
- Work in progress
+ Work in progress; testing changes on PPA.
+
+ Debian bugs:
+
+ https://bugs.debian.org/1054805
+ Please update crash to 8.0.3
+
+ https://bugs.debian.org/1055117
+ FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz
--
You received this bug
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2042357
Title:
Merge crash 8.0.3 into Noble
Status in crash packa
Debian's crash 8.0.3-1 FTBFS, waiting on 8.0.3-2 [1].
[1] https://bugs.debian.org/1055117
** Bug watch added: Debian Bug tracker #1055117
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055117
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: crash (Ubuntu Groovy)
Status: Confirmed => Won't Fix
** Changed in: crash (Ubuntu Groovy)
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
*** This bug is a duplicate of bug 2038249 ***
https://bugs.launchpad.net/bugs/2038249
** This bug has been marked a duplicate of bug 2038249
The dump file parsing issue arises from structural changes in Linux kernel
6.2
--
You received this bug notification because you are a member of
(Comment #8)
> Submitted bug [1] (wishlist) to Debian maintainer to update crash from 8.0.2
> to 8.0.3 (released April/2023) in sid/unstable.
> With this we could merge a smaller set of changes later on.
> [1] https://bugs.debian.org/1054805
Crash 8.0.3 should soon be available in Debian, and
Hi Chengen,
Thanks for the great work for these SRUs.
I'd like to suggest an update/improvement to the Test Plan section.
Even though crash is so broken that it can't even open a file,
once it starts working at all, it would be important to check
that it is working _correctly_.
So, please,
The version in Noble is still the same as in Mantic, and Debian does not
have a newer version either to sync/merge [1], so it apparently will not
change soon.
Let's proceed with the Mantic debdiff plus changes for Noble.
Changes:
- Modified d/changelog style to '* Description (LP: #)' entry with
** Patch added: "lp2038249-crash-noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5713875/+files/lp2038249-crash-noble.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
Updating the bug description with the crash versions/tags which
_contains_ the commit IDs.
Verified with the provided commit list:
$ cat
Submitted bug [1] (wishlist) to Debian maintainer to update crash from
8.0.2 to 8.0.3 (released April/2023) in sid/unstable.
With this we could merge a smaller set of changes later on.
[1] https://bugs.debian.org/1054805
--
You received this bug notification because you are a member of Kernel
Marking Jammy as affected due to the 6.2+ HWE kernel from Lunar (and
later).
** Also affects: crash (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: crash (Ubuntu Jammy)
Status: New => In Progress
** Changed in: crash (Ubuntu Jammy)
Assignee: (unassigned) =>
Uploaded to Jammy too.
The SRU template is now updated to reflect that.
Packages verified with LXD VM and upstream crash for the 6.2 kernel for now
(before bug 2038248) and Ubuntu crash for the 5.15 GA kernel. All good!
(Details in comment #7.)
The package built correctly in a PPA on all
** Description changed:
[Impact]
+
+ The kernel crashdumps generated by makedumpfile on kernel 6.2
+ (affects Lunar, and Jammy with the HWE kernel) might not open
+ on crash, due to kernel changes not reflected in makedumpfile.
+
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct
Jammy is also affected for the 6.2 HWE kernel.
The patch for makedumpfile is the same, and applies cleanly.
It fixes the issue with the 6.2 HWE kernel, and causes no regression with the
5.15 GA kernel (ie, the dump file can still be opened in crash).
Details:
---
Setup:
$ lxc launch
(The package built correctly in a PPA on all architectures.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/2038248
Title:
Slab page exclusion issue on Linux 6.2-rc1
Status in
Hi Chengen,
The fix is included in 1.7.3 in mantic, so only lunar needs the fix.
We probably would like jammy as well, for compatibility with the 6.2+
HWE kernel (without regression to the 5.15 GA kernel).
Could you please check jammy for that too? (I'll add a task as
Incomplete.)
$
** Patch added: "lp2038248-makedumpfile-lunar-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248/+attachment/5707762/+files/lp2038248-makedumpfile-lunar-v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi Chengen,
Thanks for the detailed SRU template and debdiff!
I have only 2 minor fixes, which I already performed:
- Version: s/ubuntu1/ubuntu0.1/ (see doc [1])
- Maintainer: this is the first 'ubuntu' version, so run `update-maintainer`
(see `debian/control` hunk).
The updated debdiff is
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2024479
Title:
kdump fails on big arm64 systems
This bug has been fixed in Jammy, but not yet marked Fix Released
apparently due to an issue with the Launchpad bot (reported to the
Launchpad team); leaving as Fix Committed so to trigger when the bot
runs again for it.
linux (5.15.0-83.92) jammy; urgency=medium
* kdump fails on big arm64
This bug has been fixed in Lunar and Jammy, but not yet marked Fix
Released apparently due to an issue with the Launchpad bot (reported to
the Launchpad team); leaving as Fix Committed so to trigger when the bot
runs again for it.
linux (6.2.0-32.32) lunar; urgency=medium
...
* losetup with
The kernel changes are Fix Committed in the Azure kernel packages,
and should land slightly earlier than the Generic kernel packages.
linux-azure (5.15.0-1043.50) jammy-proposed
linux-azure-5.15 (5.15.0-1043.50~20.04.1) focal-proposed
--
You received this bug notification because you are a
[J/L][PATCH 0/2] loop: fix regression from max_loop default value change
https://lists.ubuntu.com/archives/kernel-team/2023-July/141350.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
Testing on Lunar:
---
The default behavior before the regression is restored/fixed.
The modified behaviors are unchanged.
$ lsb_release -cs
No LSB modules are available.
lunar
Original:
$ uname -rv
6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC
2023
Testing on Jammy:
---
The default behavior before the regression is restored/fixed.
The modified behaviors are unchanged.
$ lsb_release -cs
jammy
Original:
$ uname -rv
5.15.0-79-generic #86-Ubuntu SMP Mon Jul 10 16:07:21 UTC 2023
$ cat /proc/cmdline
...
knod.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.15 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
For documentation purposes: the riscv64 build fails on jammy/lunar-proposed,
which is not a regression; that is since/on the jammy/lunar-release pockets.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
** Changed in: kexec-tools (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2024479
Title:
kdump fails on big arm64 systems
Hi Steve,
Thanks for reviewing!
> Is this driven by user demand on focal?
Yes, this is driven by a support case from Azure
(kdump error on Arm64 VM w/ 48 vCPUs 192 GiB RAM).
> Was this a problem in practice when focal was released,
> or has it become a problem more recently
It seems that
Hi Jo,
Thanks for the debdiffs.
Lunar and Jammy (both: 1 patch) look good, just removed '0001' from
.patch.
Focal has 6 patches and required more attention/changes (which I adjusted),
and patches look good (some notes below for documentation/other reviewers).
The (updated) debdiffs built
** Summary changed:
- kdump fails on arm64 when offset is not specified
+ kdump fails on big arm64 systems when offset is not specified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
Ioanna and I just discussed about the working scenario (eg, crashkernel=1G on
5.4 kernel),
for it to be verified/no regressions with the patches (patched kexec-tools on
5.4 kernel).
This apparently isn't an issue, as the patch in J/L mentions it is backward
compatible
(still going through the
** Description changed:
[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
** Description changed:
- [Description]
+ [Impact]
- kdump fails on arm64, on machines with a lot of memory when offeset is not
specified,
+ 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:
Hey Christian, thanks for the quick review and sponsorship.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2024479
Title:
kdump fails on arm64 when offset is not specified
Status
Hi Jo,
Thanks for the bug report, sru template, and debdiffs!
For Mantic, we currently do not have sponsors that could upload, but I
certainly can review the debdiff and give you some feedback/request
changes before reaching out to another sponsor/uploader, to hopefully
make their life easier.
Apparently, the check for (non-ignored) modules might be inexact? as both
'mstflint_access' and 'nvidia-fs' are in the linux-modules-*-nvidia deb package.
(Note: this is just a su-guess-tion :) I haven't looked at it.)
$ dpkg-deb -c linux-modules-5.15.0-1017-nvidia_5.15.0-1017.17_amd64.deb |
Public bug reported:
II: Checking modules for nvidia...
read 12 modules.
reading new modules...read 6315 modules.
reading old modules...
MISS: icp (ignored)
MISS: mstflint_access
MISS: nvidia-fs
MISS: spl (ignored)
MISS: v4l2loopback (ignored)
MISS: zavl
Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux-hwe-5.15 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "loop-ctl-add.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+attachment/5661724/+files/loop-ctl-add.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
Simpler workarounds:
For non-existing /dev/loopN devices, `losetup /dev/loopN image` should
work (i.e., don't do `mknod /dev/loopN`).
For /dev/non-loopN devices, it doesn't (different code path), so the
utility attached should help for now.
Details below.
...
# lsb_release -cs
jammy
# uname
Possible workaround w/ losetup.
# uname -rv
5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023
# cat /sys/module/loop/parameters/max_loop
8
# losetup -nl | sort
/dev/loop0 0 0 1 1 /var/lib/snapd/snaps/lxd_24322.snap
0 512
/dev/loop1 0 0
The fix/commit is applied in v5.12, thus available on Jammy
(v5.15-based).
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
~/git/linux$ git describe --contains 4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
1 - 100 of 717 matches
Mail list logo
