Assiging to the linux source package, and marking as confirmed per comment #5.
Thanks for the detailed report and test steps.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notifi
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e0caaf75d443e02e55e146fd75fe2efc8aed5540
commit e0caaf75d443e02e55e146fd75fe2efc8aed5540
Author: Trond Myklebust
Date: Tue Feb 8 13:38:23 2022 -0500
NFS: LOOKUP_DIRECTORY is also ok with symlinks
Commit ac79
Hi Jonathan. Done! That needs some Ubuntu groups/membership.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
The issue seems to be in subiquity (server installer) not the linux
kernel, per the 'error' screenshot (thanks!)
Marking the subiquity project as affected, and linux as invalid.
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: In
Hey You-Sheng Yang @vicamo,
Friendly poke :) Could you please verify linux-firmware in impish-
proposed?
This verification seems to block the linux-firmware SRU on impish, and
that blocks a larger SRU on focal.
Thanks!
--
You received this bug notification because you are a member of Kernel
Pa
> So far this has happened only once, hasn't been reproduced with same
nor later kernels.
Ok, thanks.
So, the issue might have happened due a transient hardware condition,
not being reproducible even with the same kernel version.
Let's close this bug, then, as it doesn't seem to be software/kern
Thanks for the bug report.
Can you please upload a picture of the screen during freeze?
We need more information from the 'kernel panic' message.
** Package changed: linux-signed-hwe-5.4 (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received
x27; on
bugs.lp.net).
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-firmware (Ubuntu Bionic)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: linux-firmware (Ubuntu Focal)
I
Bionic test package:
$ dpkg-deb -c linux-firmware_1.173.20+test20220214b1_all.deb | grep -w ice
drwxr-xr-x root/root 0 2022-02-13 23:10 ./lib/firmware/intel/ice/
drwxr-xr-x root/root 0 2022-02-13 23:10 ./lib/firmware/intel/ice/ddp/
-rw-r--r-- root/root577796 2022-02-13 23:10
https://lists.ubuntu.com/archives/kernel-team/2022-February/128061.html
** Description changed:
[Impact]
- * Missing firmware for Intel ICE driver on Bionic,
-which is supported by the HWE kernel from Focal.
-
+ * Missing firmware for Intel ICE driver on Bionic,
+ which is suppo
The package in bionic-proposed has been verified by an user
with access to the relevant device; 2 interfaces up/running.
# apt install linux-firmware
...
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64
linux-firmware all 1.173.21 [74.8 MB]
...
Setting up linux-firmware (1.173.21
Verification done for bionic-proposed.
There are no verification steps, but the description shows what to check for:
- It currently doesn't parse the downstream WHENCE.ubuntu file.
- Fix that and cleanup any errors flagged by the checker.
Note: these must be performed on the git repo per dep on
(Ubuntu)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: dmidecode (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Affects: dmidecode (Ubuntu Kinetic)
Importance: Undecided
Assignee: Mauricio Faria de
** Description changed:
Backport the support for SMBIOS 3.4 and 3.5 specifications
in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3)
to enable new hardware in the LTS release per SRU policy [1].
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
+
+ P.S.: SRU te
** Description changed:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
The patchset in comment #2
[Focal/FIPS][PATCH 0/4] Fix kernel BUG/Oops errors from modprobe while the
DRBG has not yet initialized (focal/fips-updates)
is now superseded by patch:
[Focal/FIPS][PATCH] UBUNTU: SAUCE: random: fallback to CRNG while DRBG is not
yet initialized
--
You received
[Focal/FIPS][PATCH v2] UBUNTU: SAUCE: random: fallback to CRNG while DRBG is
not yet initialized
(code-style change)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981487
Title:
kernel
Hi Jeremy,
It seems the PR in rhboot's grub2 hasn't been reviewed yet;
just mentions from other folks who also found it helpful.
Would you consider sending this to the grub-devel list? (i.e., upstream gnu's
grub2)
It looks like it wasn't yet (search results only cover rhboot).
By the way, this
Packages built successfully on supported architectures with
-updates/-proposed on ppa:mfo/build & ppa:mfo/build-proposed.
Uploaded to jammy. Debdiff attached for reference.
** Description changed:
+ [Impact]
+
+ * Support the SMBIOS 3.4 and 3.5 specifications in Jammy
+to enable new hardw
** Patch added: "lp1986852_dmidecode.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852/+attachment/569/+files/lp1986852_dmidecode.debdiff
** Tags added: se-sru-sponsor-mfo
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981487
Title:
kernel BUG/Oops errors from modprobe while t
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie" sta
Hi Ivan,
Yes, I just checked its changelog, which includes commits for this LP
bug number (below).
Thanks!
```
linux (5.4.0-135.152) focal; urgency=medium
* focal/linux: 5.4.0-135.152 -proposed tracker (LP: #1997412)
* containerd sporadic timeouts (LP: #1996678)
- epoll: call final ep
Hi Hans,
Thanks for the pointer to the synthetic reproducer!
It provided accurate and consistent results considering
the kernel versions reported (not) to exhibit the issue.
The Azure test kernel with the 3 patches [1] to address
that shows the same (good) results as the Azure kernel
prior to th
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: parted (Ubuntu)
Status: New =
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1837788
Title:
bcache kernel warning w
This is the warning trigger line:
int bch_cached_dev_writeback_start(struct cached_dev *dc)
...
WARN_ON(test_and_set_bit(BCACHE_DEV_WB_RUNNING, &dc->disk.flags));
...
This commit fixes this problem:
commit 1f0ffa67349c56ea54c03ccfd1e073c990e7411e
Author: Coly Li
For reference, this is the Warning in the CurrentDmesg.txt file.
[ 71.925684] WARNING: CPU: 8 PID: 2977 at
/build/linux-jmOa1Y/linux-4.15.0/drivers/md/bcache/writeback.c:603
bch_cached_dev_writeback_start+0x13f/0x1af [bcache]
[ 71.925686] Modules linked in: ebtable_filter ebtables ip6table_f
Tested with bionic-proposed (problem exists)
---
# uname -rv
4.15.0-56-generic #62-Ubuntu SMP Wed Jul 24 20:18:55 UTC 2019
# ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1
[ 39.096888] bcache: register_bdev() registered backing device loop0/null 2>&1
[ 39.109511] bcache: run_cache
Tested with eoan-proposed (problem does not exist)
root@bionic-bcache:~# uname -rv
5.2.0-9-generic #10-Ubuntu SMP Sat Jul 20 14:05:52 UTC 2019
# ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1
[ 54.032674] bcache: register_bdev() registered backing device loop0
[ 54.036972] bc
Tested with disco-proposed (problem exists)
-
# uname -rv
5.0.0-22-generic #23-Ubuntu SMP Tue Jul 23 17:23:54 UTC 2019
# ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1
[ 57.992319] bcache: register_bdev() registered backing device loop0/null 2>&1
[ 57.997331] bcache: run_cache
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status
Tested with bionic-proposed + patch (problem does not happen)
---
Test kernel available in:
https://people.canonical.com/~mfo/lp1837788/linux_4.15.0-56.62+test20190725b1_amd64/
# uname -rv
4.15.0-56-generic #62+test20190725b1 SMP Thu Jul 25 12:44:16 -03 2019
# ./setup-bcache-wb_percent-before
Hi Craig,
Thanks for testing and the details.
> The following command did not work : sudo apt install --allow-
downgrades dmidecode/jammy-updates
Alternatively, you can download/install this deb package, to revert your
instance back to the version in jammy-updates [1].
https://launchpad.net/ubu
$ git fetch -v
From https://git.savannah.nongnu.org/git/dmidecode
= [up to date]master -> origin/master
$ git log --oneline dmidecode-3-4..origin/master
6ca381c1247c dmidecode: Do not let --dump-bin overwrite an existing file
d8cfbc808f38 dmidecode: Write the whole dump file a
This is apparently a regression due to (ubuntu-only) kernel commit [1]
commit e9ec6b526c6a ("UBUNTU: SAUCE: (no-up) version: Implement
version_signature proc file.")
It modifies the contents of `/proc/version` by appending a version signature
(available individually in `/proc/version_signature`,
Some options/considerations to address this (need input from the kernel team),
given there might be impact to (other) userspace tools:
1) Make `linux_banner` like `linux_proc_banner`, i.e., append version
signature.
Fixes this issue; expands regression potential to other userspace
tools.)
Perhap
Note: this is not an issue in the more common, dumpfile form (w/ core dump),
since it does not check `/proc/version`.
1) live system form:
$ sudo crash -st ./usr/lib/debug/boot/vmlinux-6.1.0-16-generic
WARNING: ./usr/lib/debug/boot/vmlinux-6.1.0-16-generic
and /proc/version do not match!
GDB session with crash from git.
(gdb) p pc.namelist
$11 = 0x7fffed7f "../usr/lib/debug/boot/vmlinux-6.1.0-16-generic"
(gdb) p kt.proc_version
$12 = "Linux version 6.1.0-16-generic (buildd@lcy02-amd64-014)
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-14ubuntu2) 12.2.0, GNU ld (GNU Binutils
for U
Andy mentioned this is known and there's a fix in the works (LP bug
unknown at the moment).
--
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/2009595
Title:
DEP8 failure in lunar
Status in
Oops; I missed a refresh before posting my previous comment. Sorry.
The change should address the issue in crash, as /proc/version would be
a substring of a 'Linux version' string in vmlinux.
Marking as Fix Committed.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Ch
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
v5.12-rc1-dontuse~7^2~13
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
P
Updating the bug description with the crash versions/tags which
_contains_ the commit IDs.
Verified with the provided commit list:
$ cat
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.
http
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, could
(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 we
*** 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 K
** 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.
https://bugs.launchpad.net
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 subs
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 package in
** 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 notificatio
** 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
htt
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
** 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 gdb-
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, wh
** 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
https
** 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.
https://bugs.launchpad.net/bu
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 buildin
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 notific
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 packag
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 FUN
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
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
su
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 file=$DISK,if=none,id=
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 .
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 li
** 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:
+
+ https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+merge/45
** 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 8.0.3
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 are
Hi. Can you please test Kinetic?
It has dmidecode 3.4 which is the latest in Ubuntu, Debian, and upstream
git AFAICT.
Thanks!
** Changed in: dmidecode (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Hi Craig,
You can e.g., either download/install/remove the package from Kinetic in
Jammy (its deps work on Jammy) or copy the DMI tables into a Kinetic
container.
Option 1) Kinetic package on Jammy
$ wget
https://launchpad.net/ubuntu/+archive/primary/+files/dmidecode_3.4-1_amd64.deb
$ sudo apt
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.
F
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
** 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:
GRUB_C
** 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 o
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 o
** 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.
https://bugs.launchpad.net/bugs
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 correc
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 sup
** 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 wh
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.
https://bugs.l
created with mknod.
** 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 Oliveir
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
... root=...
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
[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.
https://bugs.launchpad.n
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 membe
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 mkno
Setting tag verification-done-focal.
Test results with stress-ng: 700 PASSED, 0 FAILED.
Test results w/ (x)fstests: no regressions in data=ordered and
data=journal (below).
---
Focal, data=ordered: no regression.
$ ./fstests-check-logs.sh prop-ordered/xfstests.log*
Kernel version: 5.4.0-89-gen
Setting tag verification-done-bionic.
Test results with stress-ng: 2420 PASSED, 0 FAILED.
Test results w/ (x)fstests: no regressions in data=ordered and
data=journal (below).
---
Bionic, data=ordered: no regression.
$ ./fstests-check-logs.sh prop-ordered/xfstests.log*
Kernel version: 4.15.0-16
Hey Ian, thanks for the bug report! I'm checking this on AWS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-aws Boot failure downgrading from Bionic/linu
It looks like it's not a problem with the patchset in general,
maybe it's specific to aws 4.15?
The patchset is in 5.4.0-1058-aws and it booted fine here too.
I'll check the patchset in 4.15.0-1113-aws.
A difference from your comment is that I could _not_ boot it
after 5.4.0-1058-aws, which worke
BTW, do you know of the differences between r5.metal and r5.24xlarge?
Per the specs they seem to be the same as in cpu/ram/nic/_nvme_ storage,
but differ in baremetal vs nitro hypervisor?
The reason I ask is because downgrading from 5.4.0-1056-aws to 4.15.0-1113-aws
worked/booted fine on r5.24xla
For the record, 4.15.0-1113-aws works in r5.metal w/ kexec.
Booted it 10 times successfully from both 5.4.0-1058-aws
and 4.15.0-1113-aws (itself.)
(not that it was expected to make a difference as the issue
happens on normal boot, which doesn't have previous kernel.)
Right after that, in the sam
Today I wanted to try and instrument the boot process a bit,
since we have no serial console in the nitro metal instances.
I was looking for pstore_blk (hoping we could panic_on_warn
or panic_on_oops), but it's only available in 5.8+ it seems.)
So I decided to start with grub, and keep a progress
Ian,
Do you/team have contacts in here or AWS that could help with that?
I think that other lines of investigation now, after our findings
and apparent inconsistencies, would be based on speculation, and
we're better trying to get real information/logs from the system
with AWS Support.
cheers,
M
Hi Kleber,
Thanks for the info.
The impact on bionic/generic is also exclusively on aws r5.metal or
broader?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/li
601 - 700 of 727 matches
Mail list logo
