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 -
** 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.
https://bugs.launchp
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/
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 (
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 | grep
** Tags added: sts-sponsor-mfo
--
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/1942784
Title:
makedumpfile not properly working on focal with 5.11 kernel
Status in makedumpfile pa
** Also affects: makedumpfile (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Focal)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Focal)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
** Tags added: sts-sponsor-mf
** Also affects: makedumpfile (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Hirsute
** Changed in: makedumpfile (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu Hirsute)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://
Hey Jo,
Thanks for the debdiff!
...
So, it looks like the 2 commits for dmesg/printk are actually LP#1921403
that you handled previously?
For better tracking/documentation purposes, the right thing to do would be to
keep these 2 patches
associated with that bug (well, it requires an SRU templa
signee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (m
** Description changed:
+ [Impact]
+
+ With mmap()ed files on ext4's data journaling it's possible to change
+ a mapped page's buffers contents during their jbd2 transaction commit
+ (as currently nothing prevents/blocks the write access at that time.)
+
+ This might happen between the buffers c
Regression test results with (x)fstests.
Bionic, data=ordered: no regression.
Original:
---
$ ./fstests-check-logs.sh orig-ordered/xfstests.log*
Kernel version: 4.15.0-156-generic #163-Ubuntu
- Number of Runs: 10
- Always fail (failed every time)
10 ext4/045
10 generic/044
10 ge
Regression test results with (x)fstests.
Bionic, data=journal: no regression.
Original:
---
$ ./fstests-check-logs.sh orig-journal/xfstests.log*
Kernel version: 4.15.0-156-generic #163-Ubuntu
- Number of Runs: 10
- Always fail (failed every time)
10 ext4/045
10 generic/082
10 ge
Regression test results with (x)fstests.
Bionic, data=journal: no regression.
Original:
---
$ ./fstests-check-logs.sh orig-journal/xfstests.log*
Kernel version: 5.4.0-84-generic #94-Ubuntu
- Number of Runs: 10
- Always fail (failed every time)
10 ext4/024
10 ext4/034
10 ext4/045
Regression test results with (x)fstests.
Focal, data=ordered: no regression.
Original:
---
$ ./fstests-check-logs.sh orig-ordered/xfstests.log*
Kernel version: 5.4.0-84-generic #94-Ubuntu
- Number of Runs: 10
- Always fail (failed every time)
10 ext4/024
10 ext4/034
10 ext4/045
Test results with stress-ng.
The original kernels hit the issue (very often on Bionic, less often on Focal.)
The modified kernels don't (in 2x the number of runs on both Bionic and Focal.)
Number of tests (stress-ng + crash + mount) that mount PASSED or FAILED (ie,
problem was hit.)
---
Bionic
** Attachment added: "fstests-run.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+attachment/5524206/+files/fstests-run.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
Attaching the scripts used for testing
(run/check xfstests, and run stress-ng)
--
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/1847340
Title:
ext4 journal recovery fails w/ data=journal +
** Attachment added: "fstests-check-logs.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+attachment/5524207/+files/fstests-check-logs.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Attachment added: "test-loop.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+attachment/5524208/+files/test-loop.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/bugs/1
** Summary changed:
- ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
+ ext4 journal recovery fails w/ data=journal + mmap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Patches posted for SRU.
[B/F][PATCH 0/5] ext4/jbd2: data=journal: write-protect pages on transaction
commit
https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Just updating the numbers for Focal / Original in comment #9
(the issue did happen more times overnight.)
[ 10.018315] rc.local[744]: 61 FAILED
[ 10.018882] rc.local[744]:1186 PASSED
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
? do_sys_open+0x1ba/0x2e0
__x64_sys_openat+0x20/0x30
do_syscall_64+0x5e/0x200
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4a06fa
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Bionic)
Importance: Low
Assignee: Mauricio Fari
Steps to Reproduce:
1) test app
# cat openat.c
#include
#include
int main() {
int rc;
rc = openat(AT_FDCWD, "test", O_RDWR | O_CREAT | S_IRWXU);
if (rc < 0) {
perror("openat");
** Description changed:
[Impact]
* AppArmor-enabled applications on the aufs filesystem
might hit a kernel bug when getting file attributes.
* The aufs filesystem explicitly assigns a NULL pointer
to `struct path.mnt` for `vfs_getattr()`, which calls
into AppArmor that
Test with focal-proposed (5.4.0-90.101)
---
Original:
# ../openat
Killed
[ 286.989830] BUG: kernel NULL pointer dereference, address: 0010
...
[ 286.996507] CPU: 2 PID: 5529 Comm: openat Not tainted 5.4.0-90-generic
#101-Ubuntu
[ 286.997358] Hardware name: QEMU Standard PC (i440F
Hirsute doesn't ship aufs anymore; no testing needed, just patching.
commit 4fb9ce7538c89f81e3fa5bfae881c9b49e7137e0
Author: Seth Forshee
Date: Fri Feb 19 14:46:24 2021 -0600
UBUNTU: [Config] CONFIG_AUFS_FS=n
We're keeping aufs in the source tree for backports but disabling
it sta
Test with bionic-proposed (4.15.0-162.170)
---
Original:
# ../openat
Killed
[ 442.526300] BUG: unable to handle kernel NULL pointer dereference at
0010
...
[ 442.539854] CPU: 1 PID: 5644 Comm: openat Not tainted 4.15.0-162-generic
#170-Ubuntu
[ 442.540733] Hardware name: QEMU St
[H/F/B][PATCH 0/1] aufs: fix kernel bug with apparmor and fuseblk
https://lists.ubuntu.com/archives/kernel-team/2021-October/125163.html
--
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/19484
Hey Jo,
Thanks for finding out the real patch/fix,
and testing on the supported architectures!
The debdiff looks good; I'll review/sponsor later!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launch
** Description changed:
[IMPACT]
When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the h
** Description changed:
+ [IMPACT]
- [DESCRIPTION]
makedumpfile does not create the dmesg. in /var/crash.
This happens only on 5.10+ kernel because 5.10 kernel introduces a new
lockless ringbuffer.
+
+ [FIX]
This issue has been addressed upstream with commits :
[1] c617ec633392([P
** Summary changed:
- makedumpfile not properly working on focal with 5.11 kernel
+ makedumpfile falls back to cp on focal with 5.11 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net
Hi Eric,
Answering this as I'm working on it now. :)
Yes, this has been considered and tested by Jo
in the other bug 1942784 comment 7.
Thanks for your attention to the bug/compatibility matrix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Reviewed and uploaded to Focal. Thanks @joalif!
--
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/1942784
Title:
makedumpfile falls back to cp on focal with 5.11 kernel
Status in ma
Reviewed and uploaded to Focal. Thanks @joalif!
(debdiff in bug 1942784)
--
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/1921403
Title:
makedumpfile does not create dmesg file in /
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 syst
** 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 when
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 atta
** 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 subscrib
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.)
$ git
(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 ma
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 -
** 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
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 archit
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) =>
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 i
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)
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 util
** 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
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 8.0.3
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; i<=24;
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
St
** 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 (
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.
https://bugs.launc
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 c
typo 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)
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 origin/zf
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
zf
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
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 ZED_POWER_OFF_ENCLO
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 /etc/zfs/zed.d/zed.
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 combine
tus: In Progress => Incomplete
** Changed in: crash (Ubuntu Lunar)
Status: In Progress => Incomplete
** Changed in: crash (Ubuntu Jammy)
Status: In Progress => Incomplete
** Changed in: crash (Ubuntu)
Assignee: Chengen Du (chengendu) => Mauricio Faria de Oliveira (m
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 rece
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:
$ rm
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 Kerne
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
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 ZED
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
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: /var/crash/202401081708/dump.2024
** 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 8.0.
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 ${SERIES}-server-cloudi
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 ${SERIES}-serve
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 t
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 ${SERIES}-server-cloudi
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
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
Verified bionic, focal, and hirsute (hwe kernel in focal) with steps in
comment #1.
The kernel packages in -updates hit the issue.
The kernel packages in -proposed don't hit it.
ubuntu@mfo-aufs-bionic:~/aufs$ uname -rv
4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021
ubuntu@mfo-auf
Thanks!
The picture in comment #4 contains the full stack trace.
Some technical analysis for reference. Don't worry about it.
Please see the next comment for suggestions, for now.
...
When returning to userspace from the exit_group() syscall
(as per: orig rax == 0xe7 == 231 -> sys_exit_group; s
This seems to be a nouveau/nvidia drivers topic.
I'm not a graphics expert, but if I recall correctly,
the opensource `nouveau` driver is usually disabled in
favor of the proprietary `nvidia` drivers, which seem
to work better on the Nvidia cards/gpus.
I can't provide the detailed steps right now
For documentation purposes,
(after working on items related to bug 1802021 / 1872021 / this bug)
The stack traces in this issue would suggest a duplicate of bug 1802021,
fixed in kernel 4.15.0-47.50, but this happens in 4.15.0-96, which has
that fix.
So, looking at comments #5 and #6, the issue s
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which
x (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Xenial)
Importance: High
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Also affects: linux (Ubuntu Xenial)
Analysis:
---
Kernel BUG:
Apr 21 11:39:31 web-12667 kernel: BUG: unable to handle kernel NULL
pointer dereference at 02c0
Apr 21 11:39:31 web-12667 kernel: IP: []
fuse_readdir+0x376/0x700
...
Apr 21 11:39:31 web-12667 kernel: Oops: [#5] SMP
[SRU][Xenial][PATCH] UBUNTU: SAUCE: fuse: fix bad !inode in
fuse_direntplus_link()
--
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/1970482
Title:
Xenial: kernel BUG/Oops/crash in fuse_rea
Hi Tuomas,
Thanks for the bug report.
What is the kernel version n the previous/successful boot log? (comment
#2)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
APPLIED: [SRU][Xenial][PATCH] UBUNTU: SAUCE: fuse: fix bad !inode in
fuse_direntplus_link()
** Changed in: linux (Ubuntu Xenial)
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.
Note for other readers / observation:
The kernel/OS in bug description are RHEL 8, not Ubuntu.
[4.18.0-240.el8.x86_64]
But per the comment/link at the end [1] it seems this bug
will be used for a lpfc driver update (fixing that error).
"""
Patches pushed upstream 4/12/22:
https://lore.kernel.or
Hi Nemir,
Thanks for reporting a bug and the detailed zip file.
Could you please test 5.4.0-100 [1] from focal-proposed? [2]
...
One of the stack traces in your `kernel_trace.txt` file [3]
similarly matches a stack trace from bug 1966803 comment 2 [4]
(from iput() to xfs_buf_lock()) that is fix
No hurry, and thanks.
Yes, the fix is already applied since/in v5.5 and later.
~/git/linux$ git describe --contains 93597ae8dac0149b5c00b787cba6bf7ba213e666
v5.5-rc1~8^2~31
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If you could test 5.4.0-110 that would be nice to confirm whether or not
it's the same issue, and if so, and mark it as duplicate.
Theoretically this might be a different issue also fixed in 5.13.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
*** This bug is a duplicate of bug 1966803 ***
https://bugs.launchpad.net/bugs/1966803
Hey Nemir,
That's great news; thanks for testing!
I'll set this bug as a dup of 1966803.
** This bug has been marked a duplicate of bug 1966803
xfs: Fix deadlock between AGI and AGF when target_ip exis
Hi Byron,
Thanks for reporting this bug.
Looking at the attached files, they don't seem to have a kernel stack
trace to provide insight about the crash; let's try to get it.
Do you see kernel messages in your monitor when the issue happens, that
you could take a picture and upload?
That might b
Hi Michael,
Thanks for reporting this bug.
We'd need some kernel messages to understand where it's coming from.
It looks like the Gen8 Microserver has iLO / serial console support.
Can you please check whether you can setup a serial console on it?
Then you might need linux kernel option 'consol
Your attachments came through after I sent last comment.
You could get to a shell in order to run the commands?
CurrentDmesg.txt does show an interesting error (but
it starts in the middle of the flood) going to ext4/
scsi/ata/intel DMA, which is the DMAR handler/thing.
Having messages from befo
Hi Vincent,
Thanks for the bug report.
> when attaching new volume to host. systemd-udevd trigger
> unshare process to run snap import command on new volumes and it fail.
> volume finally map to host. it doesn't affect volume usage.
> but some udev rule need to check for this strange behavior.
Reassigning to package snapd per ownership of rules file.
$ grep -r 'snap auto-import' /lib/udev/rules.d/
/lib/udev/rules.d/66-snapd-autoimport.rules:3:RUN+="/usr/bin/unshare -m
/usr/bin/snap auto-import --mount=/dev/%k"
$ dpkg -S /lib/udev/rules.d/66-snapd-autoimport.rules
snapd: /lib/udev/
501 - 600 of 727 matches
Mail list logo
