[Kernel-packages] [Bug 2051414] Re: package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
This looks a lot like you have the no longer maintained anbox-modules
(https://github.com/anbox/anbox-modules) installed, at least according
to the dpkg output:
dkms autoinstall on 6.5.0-15-generic/x86_64 succeeded for anbox-ashmem
dkms autoinstall on 6.5.0-15-generic/x86_64 failed for anbox-binder(10)
The anbox-modules project is no longer maintained and the best solution
here is if you uninstall them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2051414
Title:
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
with return code 11
Status in dkms package in Ubuntu:
Confirmed
Bug description:
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
with return code 11
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sujan 1797 F wireplumber
/dev/snd/controlC2: sujan 1797 F wireplumber
/dev/snd/controlC0: sujan 1797 F wireplumber
/dev/snd/seq:sujan 1792 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Jan 27 14:13:03 2024
ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
InstallationDate: Installed on 2023-12-30 (28 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
IwConfig:
lono wireless extensions.
eno1 no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=500a7aa9-de47-4eed-9a39-8658283b229b ro quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: dkms
Title: package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2014
dmi.bios.release: 2.57
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.57
dmi.board.asset.tag: SGH533R53W
dmi.board.name: 18E7
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: SGH533R53W
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL01v02.57:bd12/11/2014:br2.57:svnHewlett-Packard:pnHPProDesk600G1TWR:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct6:cvr:skuC8T90AV:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP ProDesk 600 G1 TWR
dmi.product.sku: C8T90AV
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051414/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052705] Re: package linux-headers-6.5.0-15-generic 6.5.0-15.15 failed to install/upgrade: linux-headers-6.5.0-15-generic paketi post-installation betiği kuruldu alt süreci 1 ha
*** This bug is a duplicate of bug 2051414 ***
https://bugs.launchpad.net/bugs/2051414
** Information type changed from Private Security to Public
** This bug has been marked a duplicate of bug 2051414
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
--
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/2052705
Title:
package linux-headers-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: linux-headers-6.5.0-15-generic paketi post-
installation betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona
erdi
Status in linux package in Ubuntu:
Confirmed
Bug description:
bilmiyorum
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-15-generic 6.5.0-15.15
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
linux-libc-dev:amd64: Install
NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: beyzanrsr 1597 F wireplumber
/dev/snd/controlC1: beyzanrsr 1597 F wireplumber
/dev/snd/seq:beyzanrsr 1591 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Feb 8 17:13:34 2024
DpkgHistoryLog:
Start-Date: 2024-02-08 17:11:15
Commandline: /usr/bin/unattended-upgrade
Upgrade: linux-libc-dev:amd64 (6.5.0-15.15, 6.5.0-17.17)
ErrorMessage: linux-headers-6.5.0-15-generic paketi post-installation betiği
kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi
InstallationDate: Installed on 2023-12-02 (69 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=50c847c3-ad3a-4f4a-847e-fc7c299a1a16 ro quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: linux-headers-6.5.0-15-generic paketi post-installation betiği
kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3306
dmi.board.name: JM50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenix:bvrV0.3306:bd08/24/2009:svnAcer:pnAspire5739G:pvrNotApplicable:rvnAcer:rnJM50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku:
dmi.product.name: Aspire 5739G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052705/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051414] Re: package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2051414
Title:
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
with return code 11
Status in dkms package in Ubuntu:
Confirmed
Bug description:
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
with return code 11
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sujan 1797 F wireplumber
/dev/snd/controlC2: sujan 1797 F wireplumber
/dev/snd/controlC0: sujan 1797 F wireplumber
/dev/snd/seq:sujan 1792 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Jan 27 14:13:03 2024
ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
InstallationDate: Installed on 2023-12-30 (28 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
IwConfig:
lono wireless extensions.
eno1 no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=500a7aa9-de47-4eed-9a39-8658283b229b ro quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: dkms
Title: package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2014
dmi.bios.release: 2.57
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.57
dmi.board.asset.tag: SGH533R53W
dmi.board.name: 18E7
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: SGH533R53W
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL01v02.57:bd12/11/2014:br2.57:svnHewlett-Packard:pnHPProDesk600G1TWR:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct6:cvr:skuC8T90AV:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP ProDesk 600 G1 TWR
dmi.product.sku: C8T90AV
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051414/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052704] Re: package linux-headers-6.5.0-15-generic 6.5.0-15.15 failed to install/upgrade: linux-headers-6.5.0-15-generic paketi post-installation betiği kuruldu alt süreci 1 ha
*** This bug is a duplicate of bug 2051414 ***
https://bugs.launchpad.net/bugs/2051414
** Information type changed from Private Security to Public
** This bug has been marked a duplicate of bug 2051414
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
--
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/2052704
Title:
package linux-headers-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: linux-headers-6.5.0-15-generic paketi post-
installation betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona
erdi
Status in linux package in Ubuntu:
New
Bug description:
bilmiyorum
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-15-generic 6.5.0-15.15
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
linux-libc-dev:amd64: Install
NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: beyzanrsr 1597 F wireplumber
/dev/snd/controlC1: beyzanrsr 1597 F wireplumber
/dev/snd/seq:beyzanrsr 1591 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Feb 8 17:13:34 2024
DpkgHistoryLog:
Start-Date: 2024-02-08 17:11:15
Commandline: /usr/bin/unattended-upgrade
Upgrade: linux-libc-dev:amd64 (6.5.0-15.15, 6.5.0-17.17)
ErrorMessage: linux-headers-6.5.0-15-generic paketi post-installation betiği
kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi
InstallationDate: Installed on 2023-12-02 (69 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=50c847c3-ad3a-4f4a-847e-fc7c299a1a16 ro quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: linux-headers-6.5.0-15-generic paketi post-installation betiği
kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3306
dmi.board.name: JM50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenix:bvrV0.3306:bd08/24/2009:svnAcer:pnAspire5739G:pvrNotApplicable:rvnAcer:rnJM50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku:
dmi.product.name: Aspire 5739G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052704/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051414] Re: package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Hello, thanks for the bug report. This looks like something to report to
the Anbox upstream developers for help.
Thanks
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2051414
Title:
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
with return code 11
Status in dkms package in Ubuntu:
New
Bug description:
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
with return code 11
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sujan 1797 F wireplumber
/dev/snd/controlC2: sujan 1797 F wireplumber
/dev/snd/controlC0: sujan 1797 F wireplumber
/dev/snd/seq:sujan 1792 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Jan 27 14:13:03 2024
ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
InstallationDate: Installed on 2023-12-30 (28 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
IwConfig:
lono wireless extensions.
eno1 no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=500a7aa9-de47-4eed-9a39-8658283b229b ro quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: dkms
Title: package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15 failed to
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with
return code 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2014
dmi.bios.release: 2.57
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.57
dmi.board.asset.tag: SGH533R53W
dmi.board.name: 18E7
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: SGH533R53W
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL01v02.57:bd12/11/2014:br2.57:svnHewlett-Packard:pnHPProDesk600G1TWR:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct6:cvr:skuC8T90AV:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP ProDesk 600 G1 TWR
dmi.product.sku: C8T90AV
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051414/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] Re: [amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
You should report the bug to where you got the drivers from. Was it not
from Ubuntu?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2045584
Title:
[amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
Status in linux package in Ubuntu:
Incomplete
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051360] Re: package linux-generic-hwe-22.04 6.5.0.15.17 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Hello, thanks for the report. This looks like it might be an issue with
the synosnap DKMS package. You might want to contact whoever supplied
this to help fix it.
Thanks
** Information type changed from Private Security to Public
--
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/2051360
Title:
package linux-generic-hwe-22.04 6.5.0.15.17 failed to install/upgrade:
problemi con le dipendenze - lasciato non configurato
Status in linux package in Ubuntu:
New
Bug description:
non mi permette di aggiornare il kernel
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic-hwe-22.04 6.5.0.15.17
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: salvox 2601 F wireplumber
/dev/snd/controlC0: salvox 2601 F wireplumber
/dev/snd/controlC2: salvox 2601 F wireplumber
/dev/snd/seq:salvox 2590 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Jan 26 06:23:19 2024
ErrorMessage: problemi con le dipendenze - lasciato non configurato
InstallationDate: Installed on 2023-05-08 (263 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
IwConfig:
lono wireless extensions.
enp2s0no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill:
SourcePackage: linux
Title: package linux-generic-hwe-22.04 6.5.0.15.17 failed to install/upgrade:
problemi con le dipendenze - lasciato non configurato
UpgradeStatus: Upgraded to mantic on 2023-11-04 (83 days ago)
dmi.bios.date: 07/04/2019
dmi.bios.release: 1.21
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V5.0.0.13 R1.21.0 for D3600-A1x
dmi.board.name: D3600-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3600-A1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.21.0forD3600-A1x:bd07/04/2019:br1.21:svnFUJITSU:pnESPRIMOP558:pvr:rvnFUJITSU:rnD3600-A1:rvrS26361-D3600-A1:cvnFUJITSU:ct3:cvr:sku:
dmi.product.family: ESPRIMO-FTS
dmi.product.name: ESPRIMO P558
dmi.sys.vendor: FUJITSU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051360/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
Building 6.8.0-7 was possible. Building 6.8.0-9 fails - but I changed a few things: added LLVM=1 and removed it later on (then debain/rules clean 'ed), installed lib*-dev based on "Auto-detecting system features" output, KBUILD_BUILD_TIMESTAMP='2024-02-13' CC='ccache cc' -- 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/2047683 Title: Kernel build fails on debian/build/tools- perarch/tools/bpf/bpftool/vmlinux Status in linux package in Ubuntu: Confirmed Bug description: I've been attempting to build both the hwe-edge and lowlatency-hwe- next kernels from source. Both fail on bpftool not being present, though `debian/build/tools-perarch/tools/bpf/bpftool/vmlinux.h` is there. ``` make[1]: Leaving directory '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/perf' mv /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/vmlinux mv: cannot stat '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:713: /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/stamps/stamp-build-perarch] Error 1 ``` I've installed the related version of libbpf1 and libbpf-devel, but still seeing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052980] [NEW] Azure: cifs modules missing from the linux-modules package
Public bug reported: SRU Justification [Impact] The source layout of cifs has changed from fs/cifs to fs/smb/client. Therefore the modules has gone missing from linux-modules, but can be found in linux-modules-extra. [Fix] Add fs/smb/* to the inclusion list (debian.azure/control.d/azure.inclusion-list). [Test Plan] List files in the linux-modules package and verify that cifs.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to its original package. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052980 Title: Azure: cifs modules missing from the linux-modules package Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] The source layout of cifs has changed from fs/cifs to fs/smb/client. Therefore the modules has gone missing from linux-modules, but can be found in linux-modules-extra. [Fix] Add fs/smb/* to the inclusion list (debian.azure/control.d/azure.inclusion-list). [Test Plan] List files in the linux-modules package and verify that cifs.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to its original package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034938] Re: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2034938 Title: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: nvidia-graphics-drivers-390 does not working ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 6.2.0-32-generic Date: Fri Sep 8 17:58:11 2023 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.157-0ubuntu5.23.04.1:/var/lib/dkms/nvidia/390.157/build/nvidia/nv-acpi.c:77:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2023-04-29 (131 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageVersion: 390.157-0ubuntu5.23.04.1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2034938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
If you're using zfs-auto-snapshot, you can tell it to ignore bpool by setting the com.sun:auto-snapshot property to false on the bpool dataset: # zfs set com.sun:auto-snapshot=false bpool -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052967] [NEW] Provide all available pkcs11 userspace binaries for container consumption
Public bug reported: [ Impact ] * NVIDIA ERD drivers provide userspace libraries for consumption. * One of them is pkcs11 plugin compiled against openssl v3 or openssl v1.1 abi * A host system only needs one of them, that matches the host os OpenSSL ABI * However, if a given host system launches containers of a different releases series, it may require the other abi pkcs11 plugin. * It is common to pass userspace libraries from host to container guest (i.e. docker, k8s, lxd all have tooling to do so). * Thus to better support running ancient and obsolete containers on modern hostos; or vice versa run modern containers on ancient hostos; ship both variants of the library always in the ERD drivers. * Most urgently this affects the longterm ERD driver production branch 535-server * Shipping this update as packaging revision only, allows releasing this update without rebuilding LRM packages. [ Test Plan ] * Observe that ERD driver packages ship all available libnvidia-pkcs11-openssl*.so* libraries * Check that launching a docker container with userspace libraries passthrough results in both available in the guest * Ensuring that matching libssl/libcrypto is available in the guest container, remains exercise for the container operator. [ Where problems could occur ] * Lintian warnings will be generated w.r.t. missing library dependencies * One must ensure shlib dependency is not generated for the other library, as those will not be satisfied. [ Other Info ] * All other projects that try to be universal against multiple openssl ABIs typically use dlopen and make appropriate function calls from a single library build. I encourage NVIDIA upstream to adapt this strategy. A C language example of achieving this, licensed under MIT license, is available here https://github.com/golang-fips/openssl ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Focal) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2052967 Title: Provide all available pkcs11 userspace binaries for container consumption Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Status in nvidia-graphics-drivers-535-server source package in Bionic: New Status in nvidia-graphics-drivers-535-server source package in Focal: New Status in nvidia-graphics-drivers-535-server source package in Jammy: New Status in nvidia-graphics-drivers-535-server source package in Mantic: New Status in nvidia-graphics-drivers-535-server source package in Noble: New Bug description: [ Impact ] * NVIDIA ERD drivers provide userspace libraries for consumption. * One of them is pkcs11 plugin compiled against openssl v3 or openssl v1.1 abi * A host system only needs one of them, that matches the host os OpenSSL ABI * However, if a given host system launches containers of a different releases series, it may require the other abi pkcs11 plugin. * It is common to pass userspace libraries from host to container guest (i.e. docker, k8s, lxd all have tooling to do so). * Thus to better support running ancient and obsolete containers on modern hostos; or vice versa run modern containers on ancient hostos; ship both variants of the library always in the ERD drivers. * Most urgently this affects the longterm ERD driver production branch 535-server * Shipping this update as packaging revision only, allows releasing this update without rebuilding LRM packages. [ Test Plan ] * Observe that ERD driver packages ship all available libnvidia-pkcs11-openssl*.so* libraries * Check that launching a docker container with userspace libraries passthrough results in both available in the guest * Ensuring that
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Oh but please don't use `[trusted=yes]`, just add the repository with add-apt-repository ppa:ubuntu-uefi-team/backports-build. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
Same problem on 6.5.0-17-generic #17~22.04.1-Ubuntu. System Information Manufacturer: LENOVO Product Name: 20SUS2LM0D Version: ThinkPad P15 Gen 1 Serial Number: PF2J52X3 Wake-up Type: Power Switch SKU Number: LENOVO_MT_20SU_BU_Think_FM_ThinkPad P15 Gen 1 Family: ThinkPad P15 Gen 1 Is there anyone working on this BUG, it provide very bad experience on a very good computer... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052323] Re: Azure Site Recovery Disk Filter Driver (ASRDFD) DKMS module
this will be a new package.. ** Package changed: linux-meta-azure (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052323 Title: Azure Site Recovery Disk Filter Driver (ASRDFD) DKMS module Status in Ubuntu: Triaged Bug description: The Azure Site Recovery Disk Filter Driver is used for Azure site disaster recovery to aid in data replication and recovery. Microsoft has requested that the driver be made available as a DKMS module in generic and Azure kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2052323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051672] Re: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)
I hope that's OK if I put the 24.04's feature freeze as milestone. ** Changed in: iproute2 (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) Status in iproute2 package in Ubuntu: New Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces * Update upstream source from tag 'upstream/6.3.0' -- Luca Boccassi <> Tue, 13 Jun 2023 23:49:37 +0100 iproute2 (6.1.0-3) unstable; urgency=medium * Ensure 'ip mo' resolves to 'ip monitor' (Closes: #1036534) -- Luca Boccassi <> Mon, 22 May 2023 14:19:52 +0100 iproute2 (6.1.0-2) unstable; urgency=medium * Add Romanian language translation for debconf (Closes: #1031917) * Bump Standards-Version to 4.6.2, no changes * Bump d/copyright year range -- Luca Boccassi <> Sat, 25 Feb 2023 19:46:35 + To manage notifications
[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5
@Roxanan, When is the backport coming? I've tested the latest kernel from proposed and the issue still persists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048945 Title: scsi_eh_* process using idle CPU after upgrade to kernel 6.5 Status in linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Possibly related to https://lkml.kernel.org/linux- scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/ Getting alerts from monitoring tools about high average CPU usage. Machine reporting the following: root@server:~# uptime 17:04:34 up 14 days, 6:33, 2 users, load average: 15.66, 15.88, 15.94 root@server:~# top -d 1 top - 17:04:49 up 14 days, 6:33, 2 users, load average: 15.59, 15.85, 15.93 Tasks: 223 total, 1 running, 222 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.7 us, 1.4 sy, 0.0 ni, 49.3 id, 48.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7896.6 total, 1772.6 free, 1163.9 used, 4960.0 buff/cache MiB Swap: 2048.0 total, 1784.6 free,263.4 used. 6431.6avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 88 root 20 0 0 0 0 D 55.4 0.0 11275:46 scsi_eh_1 root@server:~# lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge linux-image-virtual-hwe-22.04-edge: Installed: 6.5.0.14.14~22.04.6 Candidate: 6.5.0.14.14~22.04.7 Version table: 6.5.0.14.14~22.04.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 6.5.0.14.14~22.04.6 100 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 10 17:02:50 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Tags: jammy third-party-packages Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 27 10:31 seq crw-rw 1 root audio 116, 33 Dec 27 10:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-14-generic N/A linux-backports-modules-6.5.0-14-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: Upgraded to jammy on
Re: [Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Hi, do you mean audio works with that option as boot arg? On Mon, Feb 12, 2024, 11:13 bademux <1935...@bugs.launchpad.net> wrote: > I have the same problem with HP EliteBook 840 G6 > > fix: "options snd-intel-dspcfg dsp_driver=1" works but mic is broken > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1935850 > > Title: > Dell XPS 17 (9710) PCI/internal sound card not detected > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Hirsute: > Fix Released > Status in linux source package in Impish: > Fix Released > > Bug description: > This patch is for soundwire audio, and only ubuntu 5.11-generic > and later kernels support soundwire audio driver, so this patch is not > sent to groovy and focal kernels. > > For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM > project, it is not urgent to merge this patch to OEM kenrels, after > the patch is in the hirsute and impish kernels, the oem kernels will > have this patch when syncing with generic kernels. > > [Impact] > On the Dell XPS 17 (9710) machine, the audio card is not detected when > booting hirsute or impish kernels. So the audio doesn't work on this > machine with ubuntu linux 21.04 or 21.10. > > [Fix] > Backport a upstream patch, this will set the correct codec config > for this machine: rt711 for headset, dual rt1308 for spks and rt715 > for internal mic. > > [Test] > Booting up with the patched kernel, the audio card is detected, test > internal speaker and internal mic, all work well, plug a headset, > the headphone and external mic work well too. > > > [Where problems could occur] > This change only applis to the Dell machines with the > DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the > regression, it will make the audio (speaker, internal mic and headset) > can't work anymore on the Dell machine with that PRODUCT_SKU, but this > possibility is very low, and we tested the patch on the machine, so > far no regression is found. > > > No audio/mic from internal speakers/build in microphone running Ubuntu > 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. > Tried suggestions from Dell XPS 17 (9700) but this is the new model and > fixes do not work. Currently running 21.04 with proposed. > > Have tried hirsute-proposed (5.11.0-24-generic) with no luck. > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu7 > ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 > Uname: Linux 5.11.0-24-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu65.1 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: mblack 1698 F pulseaudio > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 12 11:21:27 2021 > InstallationDate: Installed on 2021-07-07 (4 days ago) > InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 > (20210420) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Title: PCI/internal sound card not detected > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/15/2021 > dmi.bios.release: 1.2 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.2.0 > dmi.board.name: 012MMP > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 17 9710 > dmi.product.sku: 0A5D > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions > > -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact]
[Kernel-packages] [Bug 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
This is for 24.04 and there is no test kernel yet. This one we can start working on this week now that the 24.04 kernel tree has been updated to 6.8. -- 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/2044589 Title: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: This request is to add support for SAS5116 controller and few critical bug-fixes in Ubuntu 24.04 LTS. Below is the list of upstream commits that adds support for SAS5116: b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982595] Re: package firmware-b43-installer 1:019-7build2 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: b43-fwcutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1982595 Title: package firmware-b43-installer 1:019-7build2 failed to install/upgrade: installed firmware-b43-installer package post- installation script subprocess returned error exit status 1 Status in b43-fwcutter package in Ubuntu: Confirmed Bug description: On the startup it show me error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firmware-b43-installer 1:019-7build2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jul 21 23:41:10 2022 ErrorMessage: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-19 (3 days ago) InstallationMedia: Lubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-7build2 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1982595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] Re: [amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
Small update. Issue is resolved by removing ROCm drivers on the latest
version of Ubuntu 23.10. It seems that ROCm was the issue. I do not know
how and where I should report this or does it need to be verified by
someone else.
--
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/2045584
Title:
[amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051720]
Bluetooth still does not work with 6.7.4, however the logs have changed from the error that was shown before: $ journalctl -b | grep -E -i bluetooth Feb 11 14:27:14 andromeda kernel: Bluetooth: Core ver 2.22 Feb 11 14:27:14 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family Feb 11 14:27:14 andromeda kernel: Bluetooth: HCI device and connection manager initialized Feb 11 14:27:14 andromeda kernel: Bluetooth: HCI socket layer initialized Feb 11 14:27:14 andromeda kernel: Bluetooth: L2CAP socket layer initialized Feb 11 14:27:14 andromeda kernel: Bluetooth: SCO socket layer initialized Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800 Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Firmware Version: 255-255.255 Feb 11 14:27:15 andromeda systemd[1]: Reached target Bluetooth Support. Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: FW download error recovery failed (-19) Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: sending frame failed (-19) Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Reading supported features failed (-19) Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Error reading debug features Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: sending frame failed (-19) Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19) Feb 11 14:27:15 andromeda systemd[1]: Stopped target Bluetooth Support. Feb 11 14:27:15 andromeda NetworkManager[781]: [1707683235.5366] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so) Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Device revision is 1 Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Secure boot is enabled Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: OTP lock is enabled Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: API lock is enabled Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Debug lock is disabled Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Feb 11 14:27:15 andromeda systemd[1]: Reached target Bluetooth Support. Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800 Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Firmware Version: 255-255.255 Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Waiting for firmware download to complete Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Firmware loaded in 1386206 usecs Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Waiting for device to boot Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Device booted in 14608 usecs Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02 Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Firmware revision 0.3 build 249 week 27 2023 Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. -- 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/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: ``` kernel: Bluetooth: hci0: command 0xfc05 tx timeout ``` This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel. ``` $ uname -a Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth ``` ``` $ journalctl -b | egrep -i bluetooth Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth. Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support. Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) ``` ``` linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
Sorry, I can't test it as I am using the 22.04 LTS Jammy and it is occuring on my work laptop, so I can't install 23.10 to check the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux package in Ubuntu: Invalid Status in linux-signed-hwe-6.5 package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Invalid Bug description: SRU Justification: [Impact] Multiple users have reported frozen displays when external HDMI device is connected on systems with intel graphics chipsets. [Fix] * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events" from 6.6.9 [Test Plan] * Tested on Intel TigerLake with iris Xe Graphics and no issues so far. It seems it affects mostly Alder Lake though, but at least it does not cause any issues on other models. * It has also been tested upstream https://gitlab.freedesktop.org/drm/intel/-/issues/8685 [Where problems could occur] * We could see issues on systems with Intel Graphics when HDMI devices are connected during power state changes. Old description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008522] Re: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle
Ok, so every commit was upstream by v6.3-rc1. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2008522 Title: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. [HW/SW Information] Meteor Lake [Software Information] Target Version: 23.10 Target Kernel: 6.3 Commit IDs: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 External Links: [Business Justification] Platform enabling [External ID] LFE-7117 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Assignee: You-Sheng Yang (vicamo) => (unassigned)
--
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/2035971
Title:
linux tools packages for derived kernels refuse to install
simultaneously due to libcpupower name collision
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[ Impact ]
* Multiple kernel flavours are conflicting with each on .deb / file
level via their tools packages
* Resolve the conflicting private libcpupower.so by statically
linking it into the only C binary that uses said library in the linux-
tools
[ Test Plan ]
* co-install tools packages from multiple kernel flavours of the same
major version and abi, it should be successful
[ Where problems could occur ]
* If one tries really hard to find the private location of
libcpupower.so and dlopen it by ever changing abi name, that will not
be possible, until the separate bug report is fixed to introduce the
public stable libcpupower.so.1 which so far ubuntu has never yet
provided.
[ Other Info ]
* original bug report
Taking linux-kvm and linux-gcp for example:
$ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103384 2023-07-25 20:00
./usr/lib/libcpupower.so.6.2.0-1011
$ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103392 2023-08-16 15:08
./usr/lib/libcpupower.so.6.2.0-1011
linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
utilities, and yet files of the same full path cannot be installed
from two distinct debian packages, which follows we won't be able to
install two linux-tools packages of two different derived kernels on
the same system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
Uname: Linux 6.5.0-9004-generic x86_64
NonfreeKernelModules: zfs wl
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vicamo 6331 F wireplumber
/dev/snd/controlC0: vicamo 6331 F wireplumber
/dev/snd/seq:vicamo 6315 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Sep 14 23:31:16 2023
InstallationDate: Installed on 2022-04-10 (522 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-generic N/A
linux-backports-modules-6.5.0-9004-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035971/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052932] Re: Very slow wireless Internet download speed
** Description changed: I have very slow wireless download speed (normally 10 to 200 kb/s) in Ubuntu 24.04, 6.6.0-14-generic — nothing specific to this version, just mentioning it for completeness. - Occasionally it will be faster for some minutes, but usually I'm stuck - with those values. + Occasionally it will be faster for some minutes, around 5 Mb/s, good but + for a matter of fact not as fast as what I get in Windows, but usually + I'm stuck with those slow values. The weird thing is that upload speed is always fine, between 2 and 8 Mb/s: % speedtest Retrieving speedtest.net configuration... Testing from Deutsche Telekom AG (217.240.168.229)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Netcom BW (Biberach an der Riß) [118.69 km]: 60.93 ms Testing download speed Download: 0.18 Mbit/s Testing upload speed.. Upload: 3.12 Mbit/s The same issue exists with Iwd or Debian. In Windows, however, I get consistently 20 Mb/s download speed, so this is not a hardware issue. Also to work around that I tether my mobile phone to the computer via USB, which also works well. 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) - Subsystem: Lite-On Communications Inc Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter - Flags: bus master, fast devsel, latency 0, IRQ 132 - Memory at a400 (64-bit, non-prefetchable) [size=2M] - Capabilities: - Kernel driver in use: ath10k_pci - Kernel modules: ath10k_pci + Subsystem: Lite-On Communications Inc Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter + Flags: bus master, fast devsel, latency 0, IRQ 132 + Memory at a400 (64-bit, non-prefetchable) [size=2M] + Capabilities: + Kernel driver in use: ath10k_pci + Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.6.0-14-generic 6.6.0-14.14 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/seq:nteodosio 2424 F pipewire - /dev/snd/controlC0: nteodosio 2428 F wireplumber + USERPID ACCESS COMMAND + /dev/snd/seq:nteodosio 2424 F pipewire + /dev/snd/controlC0: nteodosio 2428 F wireplumber CRDA: N/A Date: Mon Feb 12 12:04:44 2024 InstallationDate: Installed on 2022-05-16 (637 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver - Bus 001 Device 003: ID 0408:a061 Quanta Computer, Inc. HD User Facing - Bus 001 Device 004: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 001 Device 003: ID 0408:a061 Quanta Computer, Inc. HD User Facing + Bus 001 Device 004: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Acer Aspire A515-52G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/vgxubuntu-root ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-6.6.0-14-generic N/A - linux-backports-modules-6.6.0-14-generic N/A - linux-firmware20240202.git36777504-0ubuntu1 + linux-restricted-modules-6.6.0-14-generic N/A + linux-backports-modules-6.6.0-14-generic N/A + linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2023-01-17 (391 days ago) dmi.bios.date: 01/07/2019 dmi.bios.release: 1.9 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Raticate_WL dmi.board.vendor: WL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd01/07/2019:br1.9:efr1.7:svnAcer:pnAspireA515-52G:pvrV1.09:rvnWL:rnRaticate_WL:rvrV1.09:cvnAcer:ct10:cvrV1.09:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-52G
[Kernel-packages] [Bug 2052932] [NEW] Very slow wireless Internet download speed
Public bug reported: I have very slow wireless download speed (normally 10 to 200 kb/s) in Ubuntu 24.04, 6.6.0-14-generic — nothing specific to this version, just mentioning it for completeness. Occasionally it will be faster for some minutes, but usually I'm stuck with those values. The weird thing is that upload speed is always fine, between 2 and 8 Mb/s: % speedtest Retrieving speedtest.net configuration... Testing from Deutsche Telekom AG (217.240.168.229)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Netcom BW (Biberach an der Riß) [118.69 km]: 60.93 ms Testing download speed Download: 0.18 Mbit/s Testing upload speed.. Upload: 3.12 Mbit/s The same issue exists with Iwd or Debian. In Windows, however, I get consistently 20 Mb/s download speed, so this is not a hardware issue. Also to work around that I tether my mobile phone to the computer via USB, which also works well. 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) Subsystem: Lite-On Communications Inc Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter Flags: bus master, fast devsel, latency 0, IRQ 132 Memory at a400 (64-bit, non-prefetchable) [size=2M] Capabilities: Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.6.0-14-generic 6.6.0-14.14 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:nteodosio 2424 F pipewire /dev/snd/controlC0: nteodosio 2428 F wireplumber CRDA: N/A Date: Mon Feb 12 12:04:44 2024 InstallationDate: Installed on 2022-05-16 (637 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 0408:a061 Quanta Computer, Inc. HD User Facing Bus 001 Device 004: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Acer Aspire A515-52G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/vgxubuntu-root ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2023-01-17 (391 days ago) dmi.bios.date: 01/07/2019 dmi.bios.release: 1.9 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Raticate_WL dmi.board.vendor: WL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd01/07/2019:br1.9:efr1.7:svnAcer:pnAspireA515-52G:pvrV1.09:rvnWL:rnRaticate_WL:rvrV1.09:cvnAcer:ct10:cvrV1.09:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-52G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/2052932 Title: Very slow wireless Internet download speed Status in linux package in Ubuntu: New Bug description: I have very slow wireless download speed (normally 10 to 200 kb/s) in Ubuntu 24.04, 6.6.0-14-generic — nothing specific to this version, just mentioning it for completeness. Occasionally it will be faster for some minutes, but usually I'm stuck with those values. The weird thing is that upload speed is always fine, between 2 and 8 Mb/s: % speedtest Retrieving speedtest.net configuration... Testing from Deutsche Telekom AG (217.240.168.229)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Netcom BW (Biberach an der Riß) [118.69 km]: 60.93 ms Testing download speed Download: 0.18 Mbit/s Testing upload speed.. Upload: 3.12 Mbit/s The same
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu2.2 --- kdump-tools (1:1.6.10ubuntu2.2) jammy; urgency=medium * Disable the initramfs generation in our kernel-postinst hook when we detect we are running in a chroot. LP: #2043059. -- dann frazier Thu, 01 Feb 2024 07:34:55 -0700 ** Changed in: kdump-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in kdump-tools package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in kdump-tools source package in Jammy: Fix Released Status in linux-nvidia source package in Jammy: Invalid Status in kdump-tools source package in Mantic: Fix Released Status in linux-nvidia source package in Mantic: Invalid Status in kdump-tools source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Invalid Bug description: [Impact] When installing in a chroot environment, the kdump-tools kernel hook will fail. This breaks certain OS image creation tools, such as BCM (which I assume is NVIDIA Base Command Manager from context). While BCM's image generation tool requires some additional tweaks to consume this, the proposed fix is necessary, and should be sufficient for other tools that use chroots. [Test Plan] 1) debootstrap a chroot environment for the target Ubuntu release 2) Install kdump-tools within that environment 3) Install a kernel package and make sure it succeeds. 4) do the same steps in a virtual machine, but with `ischroot` symlinked to /dev/true at install time. This should simulate a system that was just installed with an image prepared as above. 5) Then restore ischroot, and reboot. 6) Confirm the systemd service does generate an initramfs at boot, and 7) that a crash dump can be triggered afterwords. [Where Problems Could Occur] The solution we implemented in noble was simply to detect a chroot environment with ischroot, and disable initramfs generation. The systemd service will detect that an initrd is missing, and generate one on first boot. A source of potential problems is if that does not happen for some reason, resulting in a kdump-tools service failure on first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
This bug was fixed in the package kdump-tools - 1:1.8.1ubuntu1.1 --- kdump-tools (1:1.8.1ubuntu1.1) mantic; urgency=medium * Disable the initramfs generation in our kernel-postinst hook when we detect we are running in a chroot. LP: #2043059. -- dann frazier Thu, 01 Feb 2024 07:33:05 -0700 ** Changed in: kdump-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in kdump-tools package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in kdump-tools source package in Jammy: Fix Committed Status in linux-nvidia source package in Jammy: Invalid Status in kdump-tools source package in Mantic: Fix Released Status in linux-nvidia source package in Mantic: Invalid Status in kdump-tools source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Invalid Bug description: [Impact] When installing in a chroot environment, the kdump-tools kernel hook will fail. This breaks certain OS image creation tools, such as BCM (which I assume is NVIDIA Base Command Manager from context). While BCM's image generation tool requires some additional tweaks to consume this, the proposed fix is necessary, and should be sufficient for other tools that use chroots. [Test Plan] 1) debootstrap a chroot environment for the target Ubuntu release 2) Install kdump-tools within that environment 3) Install a kernel package and make sure it succeeds. 4) do the same steps in a virtual machine, but with `ischroot` symlinked to /dev/true at install time. This should simulate a system that was just installed with an image prepared as above. 5) Then restore ischroot, and reboot. 6) Confirm the systemd service does generate an initramfs at boot, and 7) that a crash dump can be triggered afterwords. [Where Problems Could Occur] The solution we implemented in noble was simply to detect a chroot environment with ischroot, and disable initramfs generation. The systemd service will detect that an initrd is missing, and generate one on first boot. A source of potential problems is if that does not happen for some reason, resulting in a kdump-tools service failure on first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] Update Released
The verification of the Stable Release Update for kdump-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in kdump-tools package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in kdump-tools source package in Jammy: Fix Committed Status in linux-nvidia source package in Jammy: Invalid Status in kdump-tools source package in Mantic: Fix Released Status in linux-nvidia source package in Mantic: Invalid Status in kdump-tools source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Invalid Bug description: [Impact] When installing in a chroot environment, the kdump-tools kernel hook will fail. This breaks certain OS image creation tools, such as BCM (which I assume is NVIDIA Base Command Manager from context). While BCM's image generation tool requires some additional tweaks to consume this, the proposed fix is necessary, and should be sufficient for other tools that use chroots. [Test Plan] 1) debootstrap a chroot environment for the target Ubuntu release 2) Install kdump-tools within that environment 3) Install a kernel package and make sure it succeeds. 4) do the same steps in a virtual machine, but with `ischroot` symlinked to /dev/true at install time. This should simulate a system that was just installed with an image prepared as above. 5) Then restore ischroot, and reboot. 6) Confirm the systemd service does generate an initramfs at boot, and 7) that a crash dump can be triggered afterwords. [Where Problems Could Occur] The solution we implemented in noble was simply to detect a chroot environment with ischroot, and disable initramfs generation. The systemd service will detect that an initrd is missing, and generate one on first boot. A source of potential problems is if that does not happen for some reason, resulting in a kdump-tools service failure on first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Update Released
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
This bug was fixed in the package zfs-linux - 2.2.0-0ubuntu1~23.10.2
---
zfs-linux (2.2.0-0ubuntu1~23.10.2) mantic; urgency=medium
* d/p/9b9b09f452a469458451c221debfbab944e7f081.patch Cherry-pick
"dnode_is_dirty: check dnode and its data for dirtiness" fix from
zfs-2.2.2. LP: #2044657
-- Dimitri John Ledkov Tue, 30 Jan 2024
15:54:02 +
** Changed in: zfs-linux (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
I have the same problem with HP EliteBook 840 G6 fix: "options snd-intel-dspcfg dsp_driver=1" works but mic is broken -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Noble) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => 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/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5
** Changed in: linux (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051947 Title: Sound: Add rtl quirk of M70-Gen5 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When plugin the headset jack, only speaker is identified. [Fix] Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work. [Test] Vendor tested on hardware, headset mic works fine. [Where problems could occur] It may break audio. This commit is merged by stable updates in noble kernel, 5.15 doesn't support this platform, SRU for mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad
** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Noble) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051896 Title: Fix spurious wakeup caused by Cirque touchpad Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Spurious wakeup event caused by Cirque touchpad, prevent the system from sleep properly. [Fix] Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad. [Test] Suspend the system 100 times and make sure non of the wakeup event is caused by the touchpad and its IRQ line. [Where problems could occur] Logically the power consumption can increase slightly, but in reality there isn't any noticeable change. Since the quirk only applies to one device, there isn't much regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052499] Re: Mantic update: upstream stable patchset 2024-02-06
** Changed in: linux (Ubuntu Mantic) 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/2052499 Title: Mantic update: upstream stable patchset 2024-02-06 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-06 Ported from the following upstream stable releases: v6.1.70, v6.6.9 from git://git.kernel.org/ kasan: disable kasan_non_canonical_hook() for HW tags bpf: Fix prog_array_map_poke_run map poke update ARM: dts: dra7: Fix DRA7 L3 NoC node register size ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init reset: Fix crash when freeing non-existent optional resets s390/vx: fix save/restore of fpu kernel context wifi: iwlwifi: pcie: add another missing bh-disable for rxq->lock wifi: mac80211: check if the existing link config remains unchanged wifi: mac80211: mesh: check element parsing succeeded wifi: mac80211: mesh_plink: fix matches_local logic Revert "net/mlx5e: fix double free of encap_header in update funcs" Revert "net/mlx5e: fix double free of encap_header" net/mlx5e: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list() net/mlx5: Re-organize mlx5_cmd struct net/mlx5e: Fix a race in command alloc flow net/mlx5e: fix a potential double-free in fs_udp_create_groups net/mlx5: Fix fw tracer first block check net/mlx5e: Correct snprintf truncation handling for fw_version buffer net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by representors net: mscc: ocelot: fix eMAC TX RMON stats for bucket 256-511 and above octeontx2-pf: Fix graceful exit during PFC configuration failure net: Return error from sk_stream_wait_connect() if sk_wait_event() fails net: sched: ife: fix potential use-after-free ethernet: atheros: fix a memleak in atl1e_setup_ring_resources net/rose: fix races in rose_kill_by_device() Bluetooth: Fix deadlock in vhci_send_frame Bluetooth: hci_event: shut up a false-positive warning net: mana: select PAGE_POOL net: check vlan filter feature in vlan_vids_add_by_dev() and vlan_vids_del_by_dev() afs: Fix the dynamic root's d_delete to always delete unused dentries afs: Fix dynamic root lookup DNS check net: check dev->gso_max_size in gso_features_check() keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry afs: Fix overwriting of result of DNS query afs: Fix use-after-free due to get/remove race in volume tree ASoC: hdmi-codec: fix missing report for jack initial status ASoC: fsl_sai: Fix channel swap issue on i.MX8MP i2c: aspeed: Handle the coalesced stop conditions with the start conditions. x86/xen: add CPU dependencies for 32-bit build pinctrl: at91-pio4: use dedicated lock class for IRQ gpiolib: cdev: add gpio_device locking wrapper around gpio_ioctl() nvme-pci: fix sleeping function called from interrupt context interconnect: Treat xlate() returning NULL node as an error iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw Input: ipaq-micro-keys - add error handling for devm_kmemdup scsi: bnx2fc: Fix skb double free in bnx2fc_rcv() iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma() iio: triggered-buffer: prevent possible freeing of wrong buffer ALSA: usb-audio: Increase delay in MOTU M quirk usb-storage: Add quirk for incorrect WP on Kingston DT Ultimate 3.0 G3 wifi: cfg80211: Add my certificate wifi: cfg80211: fix certs build to not depend on file order USB: serial: ftdi_sio: update Actisense PIDs constant names USB: serial: option: add Quectel EG912Y module support USB: serial: option: add Foxconn T99W265 with new baseline USB: serial: option: add Quectel RM500Q R13 firmware support ALSA: hda/realtek: Add quirk for ASUS ROG GV302XA Bluetooth: hci_event: Fix not checking if HCI_OP_INQUIRY has been sent Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE Bluetooth: Add more enc key size check net: usb: ax88179_178a: avoid failed operations when device is disconnected Input: soc_button_array - add mapping for airplane mode button net: 9p: avoid freeing uninit memory in
[Kernel-packages] [Bug 2051922] Re: Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected at all
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module am dgpu W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for mod ule amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_ta.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sjt_mec2.bin for mod ule amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sjt_mec.bin for modu le amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_rlc.bin for module am dgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_mec.bin for module am dgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/sdma_4_4_2.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for mo dule amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for mod ule amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_3.bin for module amdgp u -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051922 Title: Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected at all Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Dear Members! No wifi adapter detected on ubuntu, on win11 it works fine lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 But wifi failed to manifest on previous versions and on the upcoming 24.04 as well --- tethering works bluetooth works fine no soft block / no hard block "Additional drivers" empty "ethernet interface" never tried but it is detected "lspci" doesnt show wifi "lshw -C network" doesnt show wifi did a woodoo with iwlwifi-7265-ucode-25.30.14.0 file, copied files to firmware folder, it must have failed since still no wifi. I have done a couple other things in vain, glad to repeat for the sake of practice and result. - inxi -Abd System: Kernel: 6.5.0-14-generic x86_64 bits: 64 Desktop: GNOME 42.9 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish) Machine: Type: Mini-pc Mobo: N/A model: N/A v: V00 serial: UEFI: American Megatrends v: 1.11_P4C4M43_EC_0_0_59_AMI date: 11/05/2022 Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Device-2: Intel Bluetooth wireless interface type: USB driver: btusb Is there a way to give life to that piece of wifi technology? Thank you all in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052792] Re: Mantic update: upstream stable patchset 2024-02-09
** Changed in: linux (Ubuntu Mantic) 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/2052792 Title: Mantic update: upstream stable patchset 2024-02-09 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-09 Ported from the following upstream stable releases: v6.1.71, v6.6.10 from git://git.kernel.org/ ksmbd: switch to use kmemdup_nul() helper ksmbd: add support for read compound ksmbd: fix wrong interim response on compound ksmbd: fix `force create mode' and `force directory mode' ksmbd: Fix one kernel-doc comment ksmbd: add missing calling smb2_set_err_rsp() on error ksmbd: remove experimental warning ksmbd: remove unneeded mark_inode_dirty in set_info_sec() ksmbd: fix passing freed memory 'aux_payload_buf' ksmbd: return invalid parameter error response if smb2 request is invalid ksmbd: check iov vector index in ksmbd_conn_write() ksmbd: fix race condition with fp ksmbd: fix race condition from parallel smb2 logoff requests ksmbd: fix race condition between tree conn lookup and disconnect ksmbd: fix wrong error response status by using set_smb2_rsp_status() ksmbd: fix Null pointer dereferences in ksmbd_update_fstate() ksmbd: fix potential double free on smb2_read_pipe() error path ksmbd: Remove unused field in ksmbd_user struct ksmbd: reorganize ksmbd_iov_pin_rsp() ksmbd: fix kernel-doc comment of ksmbd_vfs_setxattr() ksmbd: fix missing RDMA-capable flag for IPoIB device in ksmbd_rdma_capable_netdev() ksmbd: add support for surrogate pair conversion ksmbd: no need to wait for binded connection termination at logoff ksmbd: fix kernel-doc comment of ksmbd_vfs_kern_path_locked() ksmbd: prevent memory leak on error return ksmbd: separately allocate ci per dentry ksmbd: move oplock handling after unlock parent dir ksmbd: release interim response after sending status pending response ksmbd: move setting SMB2_FLAGS_ASYNC_COMMAND and AsyncId ksmbd: don't update ->op_state as OPLOCK_STATE_NONE on error ksmbd: set epoch in create context v2 lease ksmbd: set v2 lease capability ksmbd: downgrade RWH lease caching state to RH for directory ksmbd: send v2 lease break notification for directory ksmbd: lazy v2 lease break on smb2_write() ksmbd: avoid duplicate opinfo_put() call on error of smb21_lease_break_ack() ksmbd: fix wrong allocation size update in smb2_open() linux/export: Ensure natural alignment of kcrctab array block: renumber QUEUE_FLAG_HW_WC ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16() platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe mm/filemap: avoid buffered read/write race to read inconsistent data mm: migrate high-order folios in swap cache correctly mm/memory-failure: cast index to loff_t before shifting it mm/memory-failure: check the mapcount of the precise page ring-buffer: Fix wake ups when buffer_percent is set to 100 tracing: Fix blocked reader of snapshot buffer NFSD: fix possible oops when nfsd/pool_stats is closed. Revert "platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe" fs: cifs: Fix atime update check linux/export: Fix alignment for 64-bit ksymtab entries mptcp: refactor sndbuf auto-tuning mptcp: fix possible NULL pointer dereference on close mptcp: fix inconsistent state on fastopen race platform/x86/intel/pmc: Add suspend callback platform/x86/intel/pmc: Allow reenabling LTRs platform/x86/intel/pmc: Move GBE LTR ignore to suspend callback selftests: secretmem: floor the memory size to the multiple of page_size Revert "nvme-fc: fix race between error recovery and creating association" ftrace: Fix modification of direct_function hash while in use UBUNTU: Upstream stable to v6.1.71, v6.6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051924] Re: Mantic update: upstream stable patchset 2024-02-01
** Changed in: linux (Ubuntu Mantic) 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/2051924 Title: Mantic update: upstream stable patchset 2024-02-01 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-01 Ported from the following upstream stable releases: v6.1.69, v6.6.8 from git://git.kernel.org/ r8152: add vendor/device ID pair for D-Link DUB-E250 r8152: add vendor/device ID pair for ASUS USB-C2500 ext4: fix warning in ext4_dio_write_end_io() ksmbd: fix memory leak in smb2_lock() afs: Fix refcount underflow from error handling race HID: lenovo: Restrict detection of patched firmware only to USB cptkbd net/mlx5e: Fix possible deadlock on mlx5e_tx_timeout_work net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX qca_debug: Prevent crash on TX ring changes qca_debug: Fix ethtool -G iface tx behavior qca_spi: Fix reset behavior bnxt_en: Fix wrong return value check in bnxt_close_nic() bnxt_en: Fix HWTSTAMP_FILTER_ALL packet timestamp logic atm: solos-pci: Fix potential deadlock on _queue_lock atm: solos-pci: Fix potential deadlock on _queue_lock net: fec: correct queue selection octeontx2-af: fix a use-after-free in rvu_nix_register_reporters octeontx2-pf: Fix promisc mcam entry action octeontx2-af: Update RSS algorithm index atm: Fix Use-After-Free in do_vcc_ioctl iavf: Introduce new state machines for flow director iavf: Handle ntuple on/off based on new state machines for flow director qed: Fix a potential use-after-free in qed_cxt_tables_alloc net: Remove acked SYN flag from packet in the transmit queue correctly net: ena: Destroy correct number of xdp queues upon failure net: ena: Fix xdp drops handling due to multibuf packets net: ena: Fix XDP redirection error stmmac: dwmac-loongson: Make sure MDIO is initialized before use sign-file: Fix incorrect return values check vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() dpaa2-switch: fix size of the dma_unmap dpaa2-switch: do not ask for MDB, VLAN and FDB replay net: stmmac: Handle disabled MDIO busses from devicetree net: atlantic: fix double free in ring reinit logic cred: switch to using atomic_long_t fuse: dax: set fc->dax to NULL in fuse_dax_conn_free() ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants ALSA: hda/realtek: Apply mute LED quirk for HP15-db PCI: loongson: Limit MRRS to 256 ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE drm/mediatek: Add spinlock for setting vblank event in atomic_begin x86/hyperv: Fix the detection of E820_TYPE_PRAM in a Gen2 VM usb: aqc111: check packet for fixup for true limit stmmac: dwmac-loongson: Add architecture dependency UBUNTU: [Config] updateconfigs for DWMAC_LOONGSON blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" blk-cgroup: bypass blkcg_deactivate_policy after destroying bcache: avoid oversize memory allocation by small stripe_size bcache: remove redundant assignment to variable cur_idx bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() bcache: avoid NULL checking to c->root in run_cache_set() nbd: fold nbd config initialization into nbd_alloc_config() nvme-auth: set explanation code for failure2 msgs nvme: catch errors from nvme_configure_metadata() selftests/bpf: fix bpf_loop_bench for new callback verification scheme LoongArch: Add dependency between vmlinuz.efi and vmlinux.efi LoongArch: Implement constant timer shutdown interface platform/x86: intel_telemetry: Fix kernel doc descriptions HID: glorious: fix Glorious Model I HID report HID: add ALWAYS_POLL quirk for Apple kb nbd: pass nbd_sock to nbd_read_reply() instead of index HID: hid-asus: reset the backlight brightness level on resume HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation net: usb: qmi_wwan: claim interface 4 for ZTE MF290 arm64: add dependency between vmlinuz.efi and Image HID: hid-asus: add const to read-only outgoing usb buffer btrfs: do not allow non subvolume
[Kernel-packages] [Bug 2052406] Re: Jammy update: v5.15.145 upstream stable release
** Changed in: linux (Ubuntu Jammy) 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/2052406 Title: Jammy update: v5.15.145 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.145 upstream stable release from git://git.kernel.org/ ksmbd: use ksmbd_req_buf_next() in ksmbd_verify_smb_message() ksmdb: use cmd helper variable in smb2_get_ksmbd_tcon() ksmbd: Remove redundant 'flush_workqueue()' calls ksmbd: remove md4 leftovers ksmbd: remove smb2_buf_length in smb2_hdr ksmbd: remove smb2_buf_length in smb2_transform_hdr ksmbd: change LeaseKey data type to u8 array ksmbd: use oid registry functions to decode OIDs ksmbd: Remove unused parameter from smb2_get_name() ksmbd: Remove unused fields from ksmbd_file struct definition ksmbd: set both ipv4 and ipv6 in FSCTL_QUERY_NETWORK_INTERFACE_INFO ksmbd: Fix buffer_check_err() kernel-doc comment ksmbd: Fix smb2_set_info_file() kernel-doc comment ksmbd: Delete an invalid argument description in smb2_populate_readdir_entry() ksmbd: Fix smb2_get_name() kernel-doc comment ksmbd: register ksmbd ib client with ib_register_client() ksmbd: set 445 port to smbdirect port by default ksmbd: smbd: call rdma_accept() under CM handler ksmbd: smbd: create MR pool ksmbd: smbd: change the default maximum read/write, receive size ksmbd: smbd: fix missing client's memory region invalidation ksmbd: smbd: validate buffer descriptor structures ksmbd: add support for key exchange ksmbd: use netif_is_bridge_port ksmbd: store fids as opaque u64 integers ksmbd: shorten experimental warning on loading the module ksmbd: Remove a redundant zeroing of memory ksmbd: replace usage of found with dedicated list iterator variable smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common ksmbd: remove filename in ksmbd_file ksmbd: smbd: change prototypes of RDMA read/write related functions ksmbd: smbd: introduce read/write credits for RDMA read/write ksmbd: smbd: simplify tracking pending packets ksmbd: smbd: change the return value of get_sg_list ksmbd: smbd: handle multiple Buffer descriptors ksmbd: fix wrong smbd max read/write size check ksmbd: Fix some kernel-doc comments ksmbd: smbd: fix connection dropped issue ksmbd: smbd: relax the count of sges required ksmbd: smbd: Remove useless license text when SPDX-License-Identifier is already used ksmbd: remove duplicate flag set in smb2_write ksmbd: remove unused ksmbd_share_configs_cleanup function ksmbd: use wait_event instead of schedule_timeout() ksmbd: request update to stale share config ksmbd: remove unnecessary generic_fillattr in smb2_open ksmbd: don't open-code file_path() ksmbd: don't open-code %pD ksmbd: constify struct path ksmbd: remove generic_fillattr use in smb2_open() ksmbd: casefold utf-8 share names and fix ascii lowercase conversion ksmbd: change security id to the one samba used for posix extension ksmbd: set file permission mode to match Samba server posix extension behavior ksmbd: fill sids in SMB_FIND_FILE_POSIX_INFO response ksmbd: fix encryption failure issue for session logoff response ksmbd: set NTLMSSP_NEGOTIATE_SEAL flag to challenge blob ksmbd: decrease the number of SMB3 smbdirect server SGEs ksmbd: reduce server smbdirect max send/receive segment sizes ksmbd: hide socket error message when ipv6 config is disable ksmbd: make utf-8 file name comparison work in __caseless_lookup() ksmbd: call ib_drain_qp when disconnected ksmbd: validate share name from share config response ksmbd: replace one-element arrays with flexible-array members ksmbd: set SMB2_SESSION_FLAG_ENCRYPT_DATA when enforcing data encryption for this share ksmbd: use F_SETLK when unlocking a file ksmbd: Fix resource leak in smb2_lock() ksmbd: Convert to use sysfs_emit()/sysfs_emit_at() APIs ksmbd: send proper error response in smb2_tree_connect() ksmbd: Implements sess->rpc_handle_list as xarray ksmbd: fix typo, syncronous->synchronous ksmbd: Remove duplicated codes ksmbd: update Kconfig to note Kerberos support and fix indentation ksmbd: Fix spelling mistake "excceed" -> "exceeded" ksmbd: Fix parameter name and comment mismatch ksmbd: fix possible
[Kernel-packages] [Bug 2051655] Re: Focal update: v5.4.266 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051655 Title: Focal update: v5.4.266 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.266 upstream stable release from git://git.kernel.org/ ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5 ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init reset: Fix crash when freeing non-existent optional resets s390/vx: fix save/restore of fpu kernel context wifi: mac80211: mesh_plink: fix matches_local logic net/mlx5: improve some comments net/mlx5: Fix fw tracer first block check net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by representors net: sched: ife: fix potential use-after-free ethernet: atheros: fix a memleak in atl1e_setup_ring_resources net/rose: fix races in rose_kill_by_device() net: check vlan filter feature in vlan_vids_add_by_dev() and vlan_vids_del_by_dev() afs: Fix the dynamic root's d_delete to always delete unused dentries afs: Fix dynamic root lookup DNS check net: warn if gso_type isn't set for a GSO SKB net: check dev->gso_max_size in gso_features_check() afs: Fix overwriting of result of DNS query i2c: aspeed: Handle the coalesced stop conditions with the start conditions. pinctrl: at91-pio4: use dedicated lock class for IRQ ALSA: hda/hdmi: Add quirk to force pin connectivity on NUC10 ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB smb: client: fix NULL deref in asn1_ber_decoder() btrfs: do not allow non subvolume root targets for snapshot interconnect: Treat xlate() returning NULL node as an error iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw Input: ipaq-micro-keys - add error handling for devm_kmemdup scsi: bnx2fc: Fix skb double free in bnx2fc_rcv() iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma() wifi: cfg80211: Add my certificate wifi: cfg80211: fix certs build to not depend on file order USB: serial: ftdi_sio: update Actisense PIDs constant names USB: serial: option: add Quectel EG912Y module support USB: serial: option: add Foxconn T99W265 with new baseline USB: serial: option: add Quectel RM500Q R13 firmware support Bluetooth: hci_event: Fix not checking if HCI_OP_INQUIRY has been sent net: 9p: avoid freeing uninit memory in p9pdu_vreadf net: rfkill: gpio: set GPIO direction x86/alternatives: Sync core before enabling interrupts usb: fotg210-hcd: delete an incorrect bounds test ring-buffer: Fix wake ups when buffer_percent is set to 100 block: Don't invalidate pagecache for invalid falloc modes Linux 5.4.266 UBUNTU: Upstream stable to v5.4.266 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052404] Re: Jammy update: v5.15.144 upstream stable release
** Changed in: linux (Ubuntu Jammy) 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/2052404 Title: Jammy update: v5.15.144 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.144 upstream stable release from git://git.kernel.org/ r8152: add vendor/device ID pair for D-Link DUB-E250 r8152: add vendor/device ID pair for ASUS USB-C2500 netfilter: nf_tables: fix 'exist' matching on bigendian arches mm/memory_hotplug: handle memblock_add_node() failures in add_memory_resource() memblock: allow to specify flags with memblock_add_node() MIPS: Loongson64: Handle more memory types passed from firmware ksmbd: fix memory leak in smb2_lock() afs: Fix refcount underflow from error handling race HID: lenovo: Restrict detection of patched firmware only to USB cptkbd net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX qca_debug: Prevent crash on TX ring changes qca_debug: Fix ethtool -G iface tx behavior qca_spi: Fix reset behavior atm: solos-pci: Fix potential deadlock on _queue_lock atm: solos-pci: Fix potential deadlock on _queue_lock net: vlan: introduce skb_vlan_eth_hdr() net: fec: correct queue selection octeontx2-af: fix a use-after-free in rvu_nix_register_reporters octeontx2-pf: Fix promisc mcam entry action octeontx2-af: Update RSS algorithm index qed: Fix a potential use-after-free in qed_cxt_tables_alloc net: Remove acked SYN flag from packet in the transmit queue correctly net: ena: Destroy correct number of xdp queues upon failure net: ena: Fix xdp drops handling due to multibuf packets net: ena: Fix XDP redirection error stmmac: dwmac-loongson: Make sure MDIO is initialized before use sign-file: Fix incorrect return values check vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() dpaa2-switch: fix size of the dma_unmap net: stmmac: use dev_err_probe() for reporting mdio bus registration failure net: stmmac: Handle disabled MDIO busses from devicetree net: atlantic: fix double free in ring reinit logic cred: switch to using atomic_long_t fuse: dax: set fc->dax to NULL in fuse_dax_conn_free() ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants ALSA: hda/realtek: Apply mute LED quirk for HP15-db PCI: loongson: Limit MRRS to 256 drm/mediatek: Add spinlock for setting vblank event in atomic_begin usb: aqc111: check packet for fixup for true limit stmmac: dwmac-loongson: Add architecture dependency UBUNTU: [Config] updateconfigs for CONFIG_DWMAC_LOONGSON blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" blk-cgroup: bypass blkcg_deactivate_policy after destroying bcache: avoid oversize memory allocation by small stripe_size bcache: remove redundant assignment to variable cur_idx bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() bcache: avoid NULL checking to c->root in run_cache_set() platform/x86: intel_telemetry: Fix kernel doc descriptions HID: glorious: fix Glorious Model I HID report HID: add ALWAYS_POLL quirk for Apple kb HID: hid-asus: reset the backlight brightness level on resume HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation net: usb: qmi_wwan: claim interface 4 for ZTE MF290 HID: hid-asus: add const to read-only outgoing usb buffer btrfs: do not allow non subvolume root targets for snapshot soundwire: stream: fix NULL pointer dereference for multi_link ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify team: Fix use-after-free when an option instance allocation fails drm/amdgpu/sdma5.2: add begin/end_use ring callbacks ring-buffer: Fix memory leak of free page tracing: Update snapshot buffer on resize if it is allocated ring-buffer: Do not update before stamp when switching sub-buffers ring-buffer: Have saved event hold the entire event ring-buffer: Fix writing to the buffer with max_data_size ring-buffer: Fix a race in rb_time_cmpxchg() for 32 bit archs ring-buffer: Do not try to put back write_stamp USB:
