[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
[Expired for nvidia-graphics-drivers-535 (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
[Expired for linux-hwe-6.5 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
Hello, input/output errors like this are usually an indicator of failing
hardware. Make sure your backups are in good working order, and make
sure you don't overwrite backups with bad data.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Commit b44a34f581b0 applies to type 21J2 but Lenovo Thinkpad P14s (AMD)
Gen 4 is type 21K5.
Mario - you commented on a commit regarding type 21K5 here
https://lore.kernel.org/lkml/cbf8ac6f-5e8d-4430-aba7-853cded5a...@michaelkloos.com/T/
Should 21K5 be included in the Quirks List?
--
You
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?id=95dc0f6212b9eb8769fb40b2359a0a61cfac8494
--
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/2049793
Title:
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;
The fix hasn't been released yet.
"Fix Committed" status means the source has been updated but hasn't been
released in a package.
"Fix Released" status means the new package has the fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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
This bug was fixed in the package linux-restricted-modules - 6.8.0-28.28
---
linux-restricted-modules (6.8.0-28.28) noble; urgency=medium
* Main version: 6.8.0-28.28
* Packaging resync (LP: #1786013)
- [Packaging] debian/tracking-bug -- resync from main package
-- Paolo
This bug was fixed in the package linux-oem-6.8 - 6.8.0-1004.4
---
linux-oem-6.8 (6.8.0-1004.4) noble; urgency=medium
* noble/linux-oem-6.8: 6.8.0-1004.4 -proposed tracker (LP: #2062020)
* panel flickering after the i915.psr2 is enabled (LP: #2046315)
- drm/i915/alpm: Add
This bug was fixed in the package linux - 6.8.0-28.28
---
linux (6.8.0-28.28) noble; urgency=medium
* noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
* linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
This bug was fixed in the package nvidia-graphics-drivers-535 -
535.171.04-0ubuntu2
---
nvidia-graphics-drivers-535 (535.171.04-0ubuntu2) noble; urgency=medium
* remove
debian/dkms_nvidia/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch
*
This bug was fixed in the package linux-aws - 6.8.0-1006.6
---
linux-aws (6.8.0-1006.6) noble; urgency=medium
* noble/linux-aws: 6.8.0-1006.6 -proposed tracker (LP: #2061868)
* Rebase on 6.8.0-28.28
-- Andrea Righi Tue, 16 Apr 2024 19:26:16
+0200
** Changed in: linux-aws
This bug was fixed in the package linux-oracle - 6.8.0-1004.4
---
linux-oracle (6.8.0-1004.4) noble; urgency=medium
* noble/linux-oracle: 6.8.0-1004.4 -proposed tracker (LP: #2061873)
* Rebase on Ubuntu-6.8.0-28.28
-- Paolo Pisati Tue, 16 Apr 2024 19:36:13
+0200
** Changed
This bug was fixed in the package linux - 6.8.0-28.28
---
linux (6.8.0-28.28) noble; urgency=medium
* noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
* linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
This bug was fixed in the package linux - 6.8.0-28.28
---
linux (6.8.0-28.28) noble; urgency=medium
* noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
* linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
This bug was fixed in the package linux-oem-6.8 - 6.8.0-1004.4
---
linux-oem-6.8 (6.8.0-1004.4) noble; urgency=medium
* noble/linux-oem-6.8: 6.8.0-1004.4 -proposed tracker (LP: #2062020)
* panel flickering after the i915.psr2 is enabled (LP: #2046315)
- drm/i915/alpm: Add
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062545
> Is this new kernel working for you, Ganton?
No, it does not.
I've updated the kernel:
$ uname -a
Linux hostname 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28
23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
although in the end, after rebooting, I have experimented the
This bug was fixed in the package linux-riscv - 6.8.0-28.28.1
---
linux-riscv (6.8.0-28.28.1) noble; urgency=medium
* noble/linux-riscv: 6.8.0-28.28.1 -proposed tracker (LP: #2061974)
* Packaging resync (LP: #1786013)
- [Packaging] drop getabis data
- [Packaging]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-gcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
This is the upstream solution:
https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf
Here is the commit from 6.8.3:
b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")
--
You received this bug notification because you are a member of
This bug was fixed in the package zfs-linux - 2.2.2-0ubuntu9
---
zfs-linux (2.2.2-0ubuntu9) noble; urgency=medium
*
debian/patches/0007-Linux-6.8-compat-use-splice_copy_file_range-for-fallback.patch
- Linux 6.8 support(LP: #2058179)
* debian/control:
- add libtirpc-dev
Yep, I agree that it would be important to push some number of backports
like this one to kernel module before release. Ideally, 2.2.3 would be
better for 6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Description changed:
[Impact]
Linux kernel 6.2 includes patches with structural changes that may render the
crash utility unable to parse the dump file.
==
d122019bf061 mm: Split slab into its own type
401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
** Changed in: systemd (Ubuntu Noble)
Status: In Progress => Fix Committed
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2:
Thank Utkarsh. Yeah, we just dropped the ball on not getting this done
sooner. I'd like to see if we can make the case for SRU'ing 6.8 in, so
let's convert the bug to that.
I don't think we can justify dropping FAN support in an SRU, so let's
add that port back in.
We'll need to make a
crash 8.0.4 is available in noble (bug 2047861); checking the stable
releases' debdiffs.
** Changed in: crash (Ubuntu Noble)
Status: Fix Committed => Fix Released
** Description changed:
[Impact]
Linux kernel 6.2 includes patches with structural changes that may render the
crash
Marking Lunar as Won't Fix (EOL).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
kernel 6.2
Status
Updated the SRU template as requested in comment #11 with the detailed
test plans provided in comments #16-#20.
** Changed in: crash (Ubuntu Lunar)
Status: In Progress => Won't Fix
** Changed in: crash (Ubuntu Lunar)
Importance: Medium => Undecided
** Changed in: crash (Ubuntu Lunar)
The previously attached file dmesg20240419_2020.txt contains the dmesg
data booting the 1020 kernel.
Attached you find the dmesg file booting the 1018 kernel.
** Attachment added: "dmesg20240419_1018.txt"
Today the system has upgraded the kernel to Linux version 6.5.0-1020-oem
this should solves the keyboard problem introduced in kernel
6.5.0-1019-oem and already reported in:
- https://bugs.launchpad.net/bugs/2060727
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866
This bug fix does
Public bug reported:
The protection-domain-mapper package (and qrtr-tools) are both installed
by default on the Ubuntu Desktop for Raspberry Pi images, thanks to
their inclusion in the desktop-minimal seed for arm64. However, there's
no hardware that they target on these platforms, and the result
Hello,
After looking at it and discussing this with Dann Frazier yesterday (via
IRC on #ubuntu-release), we discussed that iproute2 is an important
package, it's in main, and has a huge bunch of reverse dependencies.
Bumping from 6.1.x to 6.8.x is a bit too much atm, especially given how
much is
** Changed in: systemd (Ubuntu Noble)
Milestone: None => ubuntu-24.04
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range
Please describe how to reproduce the issue. The bug report was based on
a self-built bluez, and did not explain what was the profile were
tested, which the built in UI or via an application talk to bluetoothd
When you are able to reproduce the issue, please run the following command, and
upload
** Summary changed:
- Still, No keybord after kernel update Linux t-l15 6.5.0-1020-oem
+ Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I also noticed this crash just before the Xwayland error:
[ 108.391556] [ cut here ]
[ 108.391560] WARNING: CPU: 7 PID: 6474 at kernel/workqueue.c:1790
__queue_work.part.0+0x30c/0x3e0
[ 108.391570] Modules linked in: uhid vboxnetadp(O) vboxnetflt(O) vboxdrv(O)
ccm
Public bug reported:
Installed new kernel as test to diagnose 5.15.0-102 kernel.
With 6.5 I am getting the errors in attached screen shot.
Also the keyboard stops working when I do a sleep/suspend and wake.
This line in grub fixes the keyboard inop issue and sleep issues both.
However with the
Public bug reported:
Kernel updates on Apr 8 '24 started the issue of keyboard not working after
sleep/suspend.
Kernel 5.15.0-97 works, other kernels after 97 need grub modified to make them
work.
Changed:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1
i8042.noaux=1"
Could someone please advise how these issues can float a little higher
before kernel freeze things happen? I tried to get this on the books
quite early by doing a Ubuntu Root on ZFS setup and giving it a test. I
know it's not directly related to the issue, but I tried to raise
awareness of this
I think I have the same issue which translates to the fact that I can't
boot the x13s image from https://cdimage.ubuntu.com/daily-live/current/
(2024-04-17 06:17).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Since kernel rebuilds are required for the ZFS fix to be readily
available, I am uploading the systemd workaround to help mitigate the
problem.
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Noble)
Importance: Medium => Critical
**
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
** Also affects: linux-aws (Ubuntu Noble)
Importance: Undecided
Assignee: Philip Cox (philcox)
Status: New
** Also affects: linux-aws (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Mantic)
Assignee: (unassigned) => Philip Cox
** Also affects: linux-aws (Ubuntu Noble)
Importance: Undecided
Assignee: Philip Cox (philcox)
Status: New
** Also affects: linux-aws (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Mantic)
Assignee: (unassigned) => Philip Cox
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-
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-
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2062556
Title:
[Ubuntu-24.04] Hugepage memory is not getting released even
Maybe this is related with this: https://lore.kernel.org/linux-
input/20240126160724.13278-1-hdego...@redhat.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2062562
Title:
Public bug reported:
After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes
back to life after suspend.
When booted with 6.5.0-26-generic everything is fine.
** Affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
---Problem Description---
Hugepages memory is not getting released even after destroying the guest
Machine Type = P10 Denali LPAR
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr 4 22:47:57 UTC
2024 ppc64le ppc64le ppc64le GNU/Linux
You have been subscribed to a public bug:
---Problem Description---
Hugepages memory is not getting released even after destroying the guest
Machine Type = P10 Denali LPAR
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr 4 22:47:57 UTC
2024 ppc64le ppc64le
--
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/1936678
Title:
Samsung Laptop support module doesn't load
Status in linux package in Ubuntu:
Won't Fix
Bug description:
This is
Public bug reported:
On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:
[ +0.000917] [drm] Display Core failed to initialize with v3.2.266!
[ +0.24] Unable to handle kernel access to user memory without uaccess
routines at virtual address 0008
A Radeon R230
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+attachment/5768195/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
** Changed in: zfs-linux (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Noble)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
This is what today is removed/added to the system:
Start-Date: 2024-04-19 13:33:54
Commandline: apt-get purge linux-image-6.1.0-1028-oem
Requested-By: pi (1000)
Purge: linux-image-6.1.0-1028-oem:amd64 ()
End-Date: 2024-04-19 13:33:54
Start-Date: 2024-04-19 13:34:24
Commandline: apt-get purge
Public bug reported:
Hello,
I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
This combination gives still a not working keyboard after booting.
Today the system has upgraded the kernel to Linux version
Public bug reported:
Ubuntu 22.04 Lock Screen is changing the brightness level automatically
- Asus Vivobook OLED 15. Also, fingerprint scanner seems not to work.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1
ProcVersionSignature: Ubuntu
I de-installed the nvidia driver completly and can confirm: This solves
the flickering issue.
Installing it again also adds flickering again.
(Using the 535 "tested" driver from the ubuntu distribution.)
--
You received this bug notification because you are a member of Kernel
Packages, which
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 Kernel
Packages, which is
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2062534
Title:
GDM3 autologin might be racy on GCP
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
Current kernel is: Linux gecko-t-t-linux-2204-wayland-exp-a2-mld-
sg4dt5wcf-acfajsmq 6.5.0-1017-gcp #17~22.04.1-Ubuntu SMP Thu Mar 14
20:30:38 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
This might not be a bug really about linux-gcp, but this is following
the work on bug 2039732 and so far I could not reproduce that locally.
Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
attached thus relying on vkms. I have reproduced locally a similar
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'.
Many thanks for the successful investigation!
Running the ppa test kernel I can't reproduce the problem anymore. :-)
I use two cifs servers running Debian 11, with a couple of shares. With both
standard kernels (6.5.0-27, 6.5.0-28) copying inside a share fails immediately
on any server.
My
Hi,
The system is about 3 years ago, I can't find one to reproduce. Your
help will be great.
I found many nv uvm error in dmesg,
Please uninstall nvidia-driver to check if it's caused by it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Thanks for your reply. I tested now both PSR settings, and the results
are
There is no screen flickering in 6.5.0-13, regardless of enable_psr=0 or
enable_psr=1
There is always screen flickering (every 1-2 minutes) in 6.5.0-27,
regardless of enable_psr=0 or enable_psr=1
So PSR seems to have no
if fixed zfs packages are pushed to the release, then user will have an
option to use DKMS at least (as I do now)
--
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/2058179
Title:
oh, it needs the kernel module to be rebuilt for the fix.. don't think
we have time for that anymore before the release.
--
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/2058179
Title:
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
I've been digging into this and this appears to be a regression
introduced by the following patch
https://github.com/torvalds/linux/commit/3cd3399dd7a84 which was first
released in Linux 6.0.0.
The bug is not a memory leak but rather a bug in how memory usage is
counted. Excess memory is not
In my reproduction environment i am testing against synology smb server
too.
now when i boot the test kernel:
$ uname -rv
6.5.0-27-generic #28~22.04.1+TEST2060919v20240419b1-Ubuntu SMP PREEMPT_DYNAMIC
Fr
sudo mount -t cifs -o username=jan,uid=1001,gid=1001 //192.168.8.3/home
testhome/
nautilus
@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
The attachment
"ipu6-drivers_0~git202404110253.97c94720-0ubuntu1~ppa.1.debdiff" seems
to be a debdiff. The ubuntu-sponsors team has been subscribed to the
bug report so that they can review and hopefully sponsor the debdiff.
If the attachment isn't a patch, please remove the "patch" flag from the
Public bug reported:
Softweare updater continually failing on this.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules:
and a build is available at
https://launchpad.net/~john-cabaj/+archive/ubuntu/zfs-splice-
fix/+packages
feel free to test before it is available in noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060780
Title:
CIFS stopped working/is
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?
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2061747
Proposed DKMS update for ipu6-drivers/noble based on new upstream
release Release_20240409.
Need sponsor.
** Patch added: "ipu6-drivers_0~git202404110253.97c94720-0ubuntu1~ppa.1.debdiff"
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Tested:
# uname -rv
6.5.0-27-generic #28+TEST2060919v20240419b1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr
19
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.10
Release:23.10
Codename: mantic
# cd /mnt/fpgnas/tmp
/mnt/fpgnas/tmp# touch
** Attachment added: "dmesg from the test"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+attachment/5768024/+files/dmesg_6.5.0-27-generic_%2328+TEST2060919v20240419b1.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in iwlwifi
driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to
...2.9 of the
>As promised, I uploaded test kernels to the below ppa:
>
>https://launchpad.net/~mruffell/+archive/ubuntu/lp2060919-test
OK. I'll test once it's built ends. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in
** 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
I've tested an initial version with the upstream patch and attached the
debdiff here. Will work to get this uploaded.
** Patch added: "zfs-linux_2.2.2-0ubuntu9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2058179/+attachment/5767995/+files/zfs-linux_2.2.2-0ubuntu9.debdiff
> I think this patch is probably not needed in 6.5, and causes the issue. How
> about I build
> you a test kernel with "cifs: fix flushing folio regression for 6.1 backport"
> reverted,
> and then we see if it fixes things?
Yep, fantastic. I can reproduce this problem anytime so I can test
Hi everyone,
As promised, I uploaded test kernels to the below ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2060919-test
They are based on 6.5.0-27-generic to keep it simple.
It just has "cifs: fix flushing folio regression for 6.1 backport". Thats it.
Pretty small patch:
commit
93 matches
Mail list logo
