Hi everyone,
Thank you for testing, and its great to hear that it fixes the issue.
The Jammy HWE kernel is still queued up to be built, it should be built
over the next few days. You can keep an eye on it at
https://kernel.ubuntu.com/reports/kernel-stable-board/
Regardless, we should be on
Hi Bernard,
Can you have a look at your /var/log/kern.log and /var/log/syslog files,
and look for what is known as a kernel oops? It looks like some of the
examples in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919
Would you be able to copy and paste any you find into a
Hi everyone,
The kernel team has built the patch into the s2024.04.1 SRU cycle, as
6.5.0-35-generic.
An ETA for this is the week of 13th of May, as per
https://kernel.ubuntu.com/
Would anyone be able to help test the kernel by installing
6.5.0-35-generic from -proposed and doing a cifs mount
Hi everyone,
Thanks for helping to test the test kernel, and I am glad that it fixes
the issue.
I have written a SRU template and have set it as the description of the
bug.
I have submitted the revert to the Kernel team mailing list for SRU:
Cover Letter:
** Summary changed:
- Remote filesystems mounted as CIFS not working after update to Kernel
"6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu"
(aarch64).
+ cifs: Copying file to same directory results in page fault
** Description changed:
- Remote filesystems
Hi Axel,
Sorry about you getting spammed about all these verifications. The robot
that posts these messages looks for the Launchpad bug number in the
package changelogs, and just makes a post for every package it sees it
in.
You might not know, but Ubuntu has slightly over 100 kernels these
) => (unassigned)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
smb: wsize blocks of bytes followed with
h:
commit 9dc02a5b7540d18a69bcbaf8f4fa428e32075b4b (HEAD -> lp2060919-test)
Author: Matthew Ruffell
Date: Fri Apr 19 17:25:48 2024 +1200
Revert "cifs: fix flushing folio regression for 6.1 backport"
This reverts commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1.
dif
Hello,
I can't actually reproduce the issue, I seem to be missing something.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
server min protocol = NT1
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
Hi everyone,
5.15.0-105-generic has been released to -updates now. It fixes the cifs
issue.
https://launchpad.net/ubuntu/+source/linux/5.15.0-105.115
Please let us know if you find any more issues.
Thanks,
Matthew
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received this bug notification because you are a member of Kernel
Performing verification for Jammy.
I started two Jammy VMs. One is a server and the other a client.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
read
Hi everyone, the fix will also be available for Focal, as part of it
getting the Jammy HWE kernel. It will be released at the same time as
Jammy's kernel is released.
We got the notification above that the kernel should be in -proposed,
but I have been refreshing -proposed all day and the kernel
The new kernel is tagged as 5.15.0-105-generic, and it is a respin of
5.15.0-103-generic with the fix.
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/log/?h=Ubuntu-5.15.0-105.115
It should be available in -proposed soon, the Kernel Team are still
rebuilding all the
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Come over to bug 2060780 and talk about it with us there.
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received
Hi everyone,
5.15.0-104-generic just hit jammy-proposed a couple minutes ago. It
isn't available for focal users yet.
Can someone please test 5.15.0-104-generic on jammy and let me know if
it fixes the issue? Thanks.
Instructions to Install (On a mantic system):
1) cat << EOF | sudo tee
Hi everyone,
Reading:
https://lore.kernel.org/lkml/2024020616.454699-1-kova...@altlinux.org/T/
It seems the issue was introduced in
commit 33eae65c6f49770fec7a662935d4eb4a6406d24b
Author: Paulo Alcantara
Date: Wed Dec 13 12:25:57 2023 -0300
Subject: smb: client: fix OOB in
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Tags added: seg
--
You received this bug notification because you
Hi R. Diez,
The 6.5.0-27-generic kernel just got released, so it should make its way
to an archive mirror near you in the next couple of hours, and should
solve your SMB 1 issue. The 6.8 kernel should be good to go when you get
it in the next couple of months.
Let us know if you encounter any
Performing verification for mantic.
I deployed mantic onto a bare metal server, with kernel 6.5.0-26-generic from
-updates.
I installed a KVM stack, synced a cloud image, and tested VM creation.
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh
Performing verification for Jammy.
I started a fresh VM, with 5.15.0-101-generic from updates. I ran the
following reproducer:
$ fallocate -l 1G /tmp/blob
$ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
$ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt
mkpart primary
Performing verification for mantic.
I started two VMs. A jammy VM for the cifs server, and a mantic VM, for
the client.
I set the jammy VM up as per the testcase.
I set the mantic VM up as per the testcase.
The mantic VM uses kernel 6.5.0-25-generic from -updates.
$ uname -rv
6.5.0-25-generic
The fix for noble should be present in 6.8.0-16-generic and later.
Marking as Fix committed for Noble.
--
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/2049634
Title:
smb: wsize blocks of
** Changed in: linux (Ubuntu Noble)
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/2049634
Title:
smb: wsize blocks of bytes followed with
I think the fix was included in 5.15.149 upstream;
https://lwn.net/Articles/963359/
Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
The kernel team have just pulled in 5.15.148, and haven't started on
149. They will likely get to it in the next week or so.
Thanks,
Matthew
Yes, 6.5.0-25-generic is available for both jammy and mantic systems. It
was released earlier this week.
Is anyone able to try it out and let me know if it fixes the issue?
Thanks.
** Changed in: linux (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
Hi cipricus,
This is a security feature working as intended. Ubuntu recently decided
to disable unprivileged access to user namespaces. You can find more
information it about it here:
Hi Sly,
We do actually test as many dkms builds as we can. Well, mainly all the
kernel modules present in the Ubuntu archive, like evdi-dkms.
The trouble starts when you get dkms sources from other places that we
don't know about, like the DisplayLink installer that I linked above.
You, me, and
Hi Sly,
Your evdi kernel module for DisplayLink docks failed to compile. It
likely couldn't generate your initramfs, leaving your 6.5.0-21-generic
not able to boot.
Your logs say its trying to build version 1.11.0:
ERROR (dkms apport): binary package for evdi: 1.11.0 not found
Error! Bad return
Hi everyone,
@angros47, yes, this issue looks to be what you are experiencing here.
https://bugs.archlinux.org/task/80064 mentions that the issue was
introduced in:
commit aa3998dbeb3abce63653b7f6d4542e7dcd022590
Author: Damien Le Moal
Date: Sat Aug 26 09:43:39 2023 +0900
Subject: ata:
Reviews from Senior Kernel Team Members:
ACK 1
https://lists.ubuntu.com/archives/kernel-team/2024-February/149051.html
ACK 2
https://lists.ubuntu.com/archives/kernel-team/2024-February/149061.html
Applied
https://lists.ubuntu.com/archives/kernel-team/2024-February/149119.html
Will let you know
Submitted the patch as SRU to mantic. Noble will pick it up when the
kernel team pulls in 6.8-rc5.
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149042.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149043.html
--
You received this bug
** Description changed:
+ BugLink: https://bugs.launchpad.net/bugs/2049634
+
[Impact]
Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
set will see data destruction when copying files from their systems onto
- a cifs smb 1.0 mount.
+ a cifs smb mount.
wsize
Hi R. Diez,
The patch was merged upstream in 6.8-rc5:
commit 4860abb91f3d7fbaf8147d54782149bb1fc45892
Author: Steve French
Date: Tue Feb 6 16:34:22 2024 -0600
Subject: smb: Fix regression in writes when non-standard maximum write size
negotiated
Link:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/148896.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/148897.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
could cause it
to page fault and subsequently crash, resulting in downtime.
The only workaround will be to disable all profiling tools until a fix
is available.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Mantic)
Importance: Medium
I tried on a random lab machine with 2x HP MM0500GBKAK disks.
With 6.5.0-18-generic:
Before:
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
Hi R. Diez,
Steve posted a new patch [1] that also rounds the wsize down when specified on
the mount command line, just as we wanted:
[1] https://lore.kernel.org/linux-
cifs/CAH2r5mvPz2CUyKDZv_9fYGu=9L=3uime7xajgbbu+if8ch8...@mail.gmail.com/
I tested it, and it works great.
$ sudo mount -t
Hi everyone,
Would it be possible if you could try 6.8-rc4 mainline to see if the
issue is fixed there?
https://kernel.ubuntu.com/mainline/v6.8-rc4/
$ wget
https://kernel.ubuntu.com/mainline/v6.8-rc4/amd64/linux-headers-6.8.0-060800rc4-generic_6.8.0-060800rc4.202402112032_amd64.deb
$ wget
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed-hwe-6.5 (Ubuntu)
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
--
You
*** This bug is a duplicate of bug 2053041 ***
https://bugs.launchpad.net/bugs/2053041
Hi Alex, please come over to bug 2053041 and we can try figure this out.
Thanks!
** This bug has been marked a duplicate of bug 2053041
Issue when shutting down computer: internal hard drive is not shut
Hi R. Diez,
You have probably been following the chatter on the upstream mailing list
discussion. I initially thought the patch didn't fix the issue, as when I mount
with wsize=16850, the issue still occurs [1], but it seems that the intent of
the patch is to only correct when the server
Hi Andrea,
I'm having some trouble with this bug, particularly on jammy-hwe.
You see, is_rust_module.sh seems to have returned again.
I see you removed it in 4f2dbd4037a697c6d96eb3d8867253e2c8d6f8d0 (ubuntu-mantic)
but if you look at 0eec6d2a63d86ac94dc8fa7c56820a0972ccbe1f (ubuntu-mantic),
** Summary changed:
- smb1: wsize blocks of bytes followed with binary zeros on copy, destroying
data
+ smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
The cifs-netfs refactor in development seems to fix the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-
fs.git/log/?h=cifs-netfs
Specifically:
commit 34efb2a814f1882ddb4a518c2e8a54db119fd0d8
Author: David Howells
Date: Fri Oct 6 18:29:59 2023 +0100
Subject: cifs: Cut
I have bisected the issue, and found the commit that introduces the
problem:
commit d08089f649a0cfb2099c8551ac47eef0cc23fdf2
Author: David Howells
Date: Mon Jan 24 21:13:24 2022 +
Subject: cifs: Change the I/O paths to use an iterator rather than a page list
Link:
linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) =&g
Hi Eugene,
Can you try the latest 6.8-rc1 and let us know if it works there? Then
we can see if we just need to backport a patch to 6.5, or talk to the
upstream maintainers instead.
https://kernel.ubuntu.com/mainline/v6.8-rc1/
Thanks,
Matthew
--
You received this bug notification because you
Exactly 3900 bytes long? That sure is strange. Do you think I would be
able to reproduce if I set up a smb1.0 mount, make a bunch of text files
with random content, take their sha256 checksums, copy to the smb1.0
share, then re-compute the sha256 checksums to see if they match?
I would probably
Hi Craig.
Excellent work tracking down the mailing list discussion. From what I can see is
that actual memory allocation and free still works as intended, it is just
accounting that becomes incorrect, making your system work correctly, just with
wrong numbers displayed in your metrics.
** No longer affects: linux-meta (Ubuntu)
** No longer affects: linux-meta-hwe-6.5 (Ubuntu)
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Hi rdiez,
Yes, this was fixed in 6.2.0-32-generic, as it included the commit you
mentioned in your description.
commit e5e1411ee7e612335d8e9d6fd7379401dee54f28
Author: Paulo Alcantara
Date: Tue May 23 17:38:38 2023 -0300
cifs: fix smb1 mount regression
BugLink:
*** This bug is a duplicate of bug 2033732 ***
https://bugs.launchpad.net/bugs/2033732
** This bug has been marked a duplicate of bug 2033732
SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
--
You received this bug notification because you are a member of Kernel
You can file a bug just like you did. If you happen to do a bit more
debugging, then making sure it gets assigned to the correct package
helps.
For the kernel, always just file a new bug, unless someone has the same
issue as you and you can find the bug via google or the all bugs
category on the
Great, so the fix works as intended. 5.15.0-91-generic should be
released to -updates this week hopefully.
I don't think the CPC team builds any cloud images with -proposed
enabled. I asked around, and I'll let you know if there does happen to
be some images built.
For the meantime you could
Hi Daniel,
Thanks for reporting. I had a look into the followup commit you
mentioned:
~/Work/kernel/ubuntu-jammy$ git log --grep "virtio-net: set queues after
driver_ok" origin/master-next
commit c6c83b9055f44bcb2bc2fae32323c0a1510c7656
Author: Jason Wang
Date: Wed Aug 9 23:12:56 2023 -0400
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Hi icaria36,
Your configuration boots to nouveau instead of the nvidia driver when
you boot into -lowlatency. As seen in the below Xserver logs:
...
Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (==) Matched nouveau as
autoconfigured driver 0
...
Nov 17 11:59:24 quiet
Hi Heiko,
I had a look at the changes between 5.15.0-86-generic and
5.15.0-88-generic, and there are the following cifs commits:
ubuntu-jammy $ git log --grep "cifs" --oneline Ub
untu-5.15.0-86.96..Ubuntu-5.15.0-88.98
c92787866aa8 cifs: if deferred close is disabled then close files immediately
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed (Ubuntu)
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: seg
--
You received this bug notification because you are a member of Kernel
Performing verification for Jammy. I checked out the
Ubuntu-5.15.0-90.100 git tag from the source repository on an arm64
system, and made sure that pahole was removed. I completed a build and
looked at the build log, and there were no more pahole warnings.
Marking verified for jammy.
** Tags
Performing verification for Jammy. David Thompson has tested the Ubuntu-
bluefield-5.15.0-1029.31 git tag on a arm64 system, and built a kernel
successfully, with no more pahole warnings occurring.
Marking verified for linux-bluefield.
** Tags removed: verification-needed-jammy-linux-bluefield
Hi Ray,
I can see the difference:
diff --git a/dmesg_working.log b/dmesg_broken.log
index 79e34be..de76884 100644
--- a/dmesg_working.log
+++ b/dmesg_broken.log
@@ -59,7 +59,7 @@ reserve setup_data: [mem
0xfee0-0xfee00fff] reserved
-efi: ACPI=0xba282000 ACPI 2.0=0xba282000
Hi Zoltan,
The bisect route would be standard debian packages. You would just wget
the packages, dpkg -i them, reboot into it, suspend, resume, remove
kernel, and report back with the result. Then I would build you the next
one.
I'll have a closer look through the commits in 5.15.0-78 to
Hi Zoltan,
There is about 1400 commits between 5.15.0-78 (good) and 5.15.0-82
(bad):
$ git log --oneline Ubuntu-5.15.0-78.85..Ubuntu-5.15.0-82.91 | wc -l
1379
Are you interested in helping us with a kernel bisect? I would build you
kernels halfway between each good and bad kernel until we land
Hi Ray,
Your dmesg log shows 16gb of usable memory.
[0.159452] Memory: 16117124K/16648596K available (20480K kernel
code, 4152K rwdata, 12720K rodata, 4764K init, 17540K bss, 531212K
reserved, 0K cma-reserved)
Could you please wait until you happen to get a boot where you get less
memory
Patches have been submitted to the kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2023-September/144570.html
https://lists.ubuntu.com/archives/kernel-team/2023-September/144571.html
--
You received this bug notification because you are a member of Kernel
Packages, which
luefield (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffel
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2023955
[Impact]
Due to fips for jammy not being available yet, users with requirements
to be fips certified or fips compliant have to use focal, and many are
finding certain hardware devices do not work on their
: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Focal)
Status:
Hi Paul,
Yes, if we look at https://kernel.ubuntu.com/sru/dashboards/web/kernel-
stable-board.html under 2023.05.15 SRU cycle, under Jammy it has linux-
hwe-5.19 5.19.0-44.45~22.04.1 sitting in -proposed, so yes, this fix
will be made available to kinetic and jammy-hwe.
Saying that, the
Hi Paul,
Thanks for verifying that linux-nvidia kernel, but for the future, you
don't need to worry about verifying each and every kernel series. These
days, the kernel team maintains over 100 kernel variants, and it is
simply impossible to check them all.
We just check the primary ones, e.g.
Its not necessary Loic, linux-hwe is a derivative of the kinetic kernel,
and it will be automatically built and pushed to -proposed in due
course, likely over the next few days.
It will be a part of the 5.19.0-44 HWE kernel. I'll keep an eye on it, I
don't think the HWE kernel is moving to the
** No longer affects: linux-hwe-5.19 (Ubuntu)
** No longer affects: linux-hwe-5.19 (Ubuntu Jammy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2007001
Title:
vmwgfx fails to
Wonderful! Thank you very much Paul for testing!
This will slowly work its way through the Kernel SRU process. We should
see a release to -updates the week of 5th June, as per
https://kernel.ubuntu.com/, give or take a few days if any CVEs turn up.
--
You received this bug notification because
Hi everyone,
I have submitted the revert to the Kernel Team for SRU:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2023-April/138908.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2023-April/138909.html
The next step is for the kernel team to review the patch, and for
** Summary changed:
- Blank console display with aarch64 kernel 5.19.0-31
+ vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
** Description changed:
- Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion
- 13.0.1 on Apple Silicon_ from 5.19.0-29 to
Hi everyone,
I have built a test kernel based on the current 5.19.0-38-generic kernel for
both Kinetic and Jammy HWE. It has the below patch reverted:
commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
Author: Thomas Zimmermann
Date: Mon Jul 18 09:23:18 2022 +0200
Subject: video/aperture:
hanged in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.
*** This bug is a duplicate of bug 2007001 ***
https://bugs.launchpad.net/bugs/2007001
Hi Zack,
Thanks for the report and the link. I'll get a test kernel building with
a revert and we can get some community users to try it out.
I'll post it in bug 2007001 instead, the existing bug, and
Hi Christian, Alfredo,
5.4.0-146-generic was released yesterday with a fix for the NFS
regression, and it should have less bandwidth consumption than
5.4.0-144-generic.
There is still some reports that it still has higher NFS requests than
before the regression was introduced, so please chime in
Performing verification for Jammy.
I started a fresh Jammy VM, and installed 5.15.0-67-generic from
-updates.
I appended apparmor=0 to GRUB_CMDLINE_LINUX_DEFAULT, updated grub, and
rebooted.
>From there, I installed auditd, and stress-ng. I edited
/etc/audit/rules.d/audit.rules to include:
-a
Performing verification for Focal.
The customer in question installed 5.4.0-145-generic to their busy
production Kubernetes cluster, and have had no issues in the week and a
half the kernel has been running for. Before, they would suffer
deadlocks three or four times a day, so the kernel in
Performing verification for Bionic
I started a fresh VM with 4.15.0-206-generic from -updates. I attached 2x virtio
disks of 3gb each, for scratch disks.
I ran btrfs/154 with the following results:
# ./check btrfs/154
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 bionic-xfs
Performing verification for Focal
I started a fresh VM with 5.4.0-144-generic from -updates. I attached 2x virtio
disks of 3gb each, for scratch disks.
I ran btrfs/154 with the following results:
# ./check btrfs/154
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 focal-xfs
Hi Alfredo,
Do you happen to use NFSv3 in your environment? There was a regression
in 5.4.0-144-generic that cased a massive spike in ACCESS requests being
made, which could explain low performance.
bug 2009325
Thanks,
Matthew
--
You received this bug notification because you are a member of
** Tags added: seg
--
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/2009325
Title:
NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Status in linux package in Ubuntu:
Hi JianlinLV,
I tried the latest 5.15.0-60-generic kernel from -updates, and I
couldn't reproduce the issue anymore.
Can you try 5.15.0-60-generic and let me know?
I bisected it down to 5.15.0-52-generic being broken, and it being fixed
in 5.15.0-53-generic.
Still trying to find the commit
ovs-vsctl[51186]: ovs|1|vsctl|INFO|Called as ovs-vsctl --timeout=120
--oneline --format=json --db=tcp:127.0.0.1:6640 -- --if-exists del-port br-int
tap8c883ee5-5f
kernel: device tap8c883ee5-5f left promiscuous mode
lldpd[2309]: removal request for address of fe80::fc16:3eff:fe07:2be2%27, but
Hi David,
Thanks for the link, I think that is the most plausible explanation I have
seen so far.
The only problem is, if we look at the patch:
diff --git a/drivers/net/tun.c b/drivers/net/tun.c
index 7a3ab3427369..24001112c323 100644
--- a/drivers/net/tun.c
+++ b/drivers/net/tun.c
@@ -686,7
ntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: focal sts
** Description changed:
- BugLink: https://bugs.launchpad.net/bugs/
+ BugLink: https://bugs.launchpad.net/bugs/2007219
[Impact]
A deadlock exists in the XFS filesys
ecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
**
M Stacking Patchset fix - Change Landlock from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
The discussion uses largely information found in this SRU template,
plus some additional information from mailing list threads
highlighting why it is safe to move to LSMBLOB_NOT_NEEDED.
From Matthew Ruffell
https:
Gardner:
Subject:
Please Re-review LSM Stacking Patchset fix - Change Landlock from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
The discussion uses largely information found in this SRU template,
plus some additional information from mailing list threads
highlighting why it is safe to
** Tags added: sts
--
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/1962485
Title:
Kernel Crash [general protection fault: [#1] SMP NOPTI]
Status in linux package in Ubuntu:
** Tags added: focal jammy kinetic
--
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/1983656
Title:
iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
Status in linux
ogress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) =&g
gh and Tim Gardner:
Subject:
Please Re-review LSM Stacking Patchset fix - Change Landlock from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
The discussion uses largely information found in this SRU template,
plus some additional information from mailing list threads
highlighting why it is safe t
k from
LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED
+
+ The discussion uses largely information found in this SRU template, plus
+ some additional information from mailing list threads highlighting why
+ it is safe to move to LSMBLOB_NOT_NEEDED.
+
+ From Matthew Ruffell
+ https://pastebin.canonical.com/
1 - 100 of 402 matches
Mail list logo
