This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1029.33 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1011.11 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1024.24~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-azure/5.15.0-1063.72
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-
linux-azure'. If
Nelle,
Seems no one else is experiencing the issue I described above, so it's
probably a me problem. I will do more troubleshooting on my end. Thanks
for sharing your results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1061.67~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
Today, on my setup (TrueNAS-SCALE-22.12.4.2) I didn't notice any
problems with new kernel 5.15.0-105-generic #115-Ubuntu when I copied 5
files with a total size of over 430GB from local disk to the mounted
network CIFS drive.
--
You received this bug notification because you are a member of
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1056.60~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
riscv-5.15' to
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
Hi, I believe that kernel 5.15.0-105-generic may not have have solved
the issue entirely.
I upgraded to 104 from -proposed, and then when 105 was available, I
updated to 105, and then removed 104 and the -proposed repo entirely.
While, the issue does not present itself as frequently, I still
Running an apt upgrade rather than apt-get upgrade installed the new kernel now.
Just installed on testserver and tried CIFS mounts with a short test.
It seems working now, thanks !
I'll install as soon as possible this kernel on 2 more productive servers and
try what's happen
Bye
Axel
--
You
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1011.11
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gcp-tcpx' to 'verification-done-
Seems apt-upgrade will not download new kernel:
Die folgenden Pakete sind zurückgehalten worden:
linux-generic linux-headers-generic linux-image-generic
ubuntu-advantage-tools ubuntu-pro-client-l10n
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm totally confused now. Last note her says you're wating for confirmation,
but I got 2 emails telling me, that the fixed kernel has been released now. But
when I do a apt-get update and apt-get upgrade still 104 will be installed? Did
I misunderstood something?
Axel
--
You received this bug
This bug is awaiting verification that the linux-
fips/5.15.0-105.115+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-fips' to
'verification-done-jammy-linux-fips'.
Thanks a lot !
Axel
>>> engaging374 <2060...@bugs.launchpad.net> 19.04.2024 10:16 >>>
@Alex
Well it's officially released now. It's up to you to install the patch.
:-)
I think someone needs to verify the patch as soon as it's in -proposed
state. Without verification it will be dropped from the
@Alex
Well it's officially released now. It's up to you to install the patch.
:-)
I think someone needs to verify the patch as soon as it's in -proposed
state. Without verification it will be dropped from the source code. (
-> no official fix will be provided in -updates.)
Normally it's not the
Hi Matthew,
tested Jammy & Focal (hwe). Looks good for me. :-)
Thank you & the Kernel Team!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
CIFS stopped working/is unstable with
This bug was the first time I came into this forum, so sorry if this a dumb
question:
today I got 3 emails that that a fix might be available and I have to test it.
If I do nbot the fix will be removed from kernel?
Really? Is it really needed that I do some tests after so many already did?
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 Ubuntu
Bugs,
This bug is awaiting verification that the linux-nvidia/5.15.0-1051.52
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-nvidia' to 'verification-done-
jammy-linux-nvidia'.
This bug is awaiting verification that the linux-
lowlatency/5.15.0-105.115 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1042.44 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
This bug was fixed in the package linux - 5.15.0-105.115
---
linux (5.15.0-105.115) jammy; urgency=medium
* jammy/linux: 5.15.0-105.115 -proposed tracker (LP: #2061372)
* Jammy update: v5.15.149 upstream stable release (LP: #2059014) // CIFS
stopped working/is unstable with
BUILD_EXCLUSIVE errors were there in 104 also. Wireguard still works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
CIFS stopped working/is unstable with kernel update to
I had no problem installing and testing 5.15.0-104, but when I try to
install 105 I get:
Setting up linux-headers-5.15.0-105-generic (5.15.0-105.115) ...
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.15.0-105-generic
Error! The
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
Spent so long troubleshooting a container and Veeam Agent issue just to
find out it was a kernel issueAnd here I was worried that power
outage borked something...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I can confirm that linux-generic 5.15.0.105 is not available yet in
proposed repository. Latest version is 104.
# apt policy linux-generic
linux-generic:
Installed: 5.15.0.102.99
Candidate: 5.15.0.104.101
Version table:
5.15.0.104.101 500
500
I feel compelled to agree with Axel and Andreas:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/comments/9
This bug is particularly surprising for a stable release, breaking CIFS
is not a pleasant thing to deal with.I tend to stick to the stable
builds to avoid things just like
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
Yep, Focal is also affected. Will this fix also be available for Focal?
Edit:
I have tried to add it here, but looked wrong. Not sure if it's the right way
to add Focal to this bug.
** Also affects: focal (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: focal
I had a hard time diagnosing this issue due to the difficulty of finding
this bug report. As I use Focal, I didn't think to check the Jammy
board. The general Ubuntu board has a report for this issue, but since
it's marked as a duplicate of this one it is hidden by default.
--
You received this
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1024.24 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
This bug is awaiting verification that the linux/5.15.0-105.115 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
> In the meantime, the meta package will be deleted so that other people
do not upgrade to 5.15.0-102.
Just checking, has that happened? I'm still seeing that offered in
response to "apt upgrade" on an older system here:
The following NEW packages will be installed:
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
Good to know a new kernel is coming out soon to fix the issue. Thank
you.
Where is the best place to look to see when the patch is released?
Many thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi! Thanks for reporting this.
We will do our best to release new kernels in 1-2 days. In the meantime, the
meta package will be deleted so that other people do not upgrade to 5.15.0-102.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I downloaded the files linked at the top labeled 20240315 and extracted
them and installed it on my UZG-01 and I show "20230507" but it is
stable as of right now. I have not gotten any more disconnect notices
from my automation to monitor it since the update and connections do
seem to be faster
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
To manage notifications about this bug go to:
Hi,
I also did some testing with 5.15.0-104-generic from proposed repository
and can confirm this version works again.
I urgently request you to reconsider the decision to postpone the
release until the end of the month. Automatic patching/updating
currently breaks several servers every day but
Hello,
I just tested your suggestion wit 104
It's working here with this kernel
Dont understand why you will still provide a faulty kernel until end of month?
We have a lot of servers here using CIFS mounts and we have to prevent all of
them now from getting a faulty kernel.
bye
Axel
--
You
> Just a note that 5.15.0-104-generic is a part of the 2024.04.01 SRU
cycle, and will likely be released at the end of month, as per
https://kernel.ubuntu.com/, and won't be coming out any sooner.
Do I understand this correctly, do you keep kernel update 5.15.0-102.112
in place and let people
Hello Matthew,
I tested it with 22.04.4 LTS.
Linux srv1 5.15.0-104-generic #114-Ubuntu SMP Thu Mar 28 15:39:51 UTC
2024 x86_64 x86_64 x86_64 GNU/Linux
'df -hT /opt/test'
Filesystem Type Size Used Avail Use% Mounted on
//cifssrv/clone1 cifs 9.5G 4.4G 5.2G 46%
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
I collected a bunch of info on it. Seems to be reported all over the
place:
-
https://www.reddit.com/r/linux/comments/1bzvy5l/ubuntu_22044_latest_updates_492024_break_cifssmb/
-
https://www.reddit.com/r/Ubuntu/comments/1bzshdt/ubuntu_2204_smb_shares_stopped_working_lastnight/
-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
Same problems here. Get error messages like "Too many symlinks" and exactly the
same as in this description.
Found also, that CIFS mounts to Netapp mostly works, but df -h doesnt show them
and mounts to other CIFS shares doesnt work.
Verified it on 5 Linux Boxes, all started failing after patch
See related question
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
To manage notifications about this bug go
53 matches
Mail list logo
