[Kernel-packages] [Bug 2045413] Re: package linux-generic 6.5.0.13.15 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Hello Victor, I suspect you may have a hardware problem. I suggest
running memtest86+ overnight or over the weekend as a first step.
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/2045413
Title:
package linux-generic 6.5.0.13.15 failed to install/upgrade: problemas
de dependência - deixando desconfigurado
Status in linux package in Ubuntu:
New
Bug description:
not is actualizing
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.13.15
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: victor 2592 F wireplumber
/dev/snd/controlC0: victor 2592 F wireplumber
/dev/snd/seq:victor 2585 F pipewire
CasperMD5CheckResult: pass
Date: Wed Nov 29 11:04:07 2023
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2023-11-03 (28 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=b171771b-95a6-4164-96a8-505fafc19176 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
SourcePackage: linux
Title: package linux-generic 6.5.0.13.15 failed to install/upgrade: problemas
de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2020
dmi.bios.release: 1.12
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Octavia_PKS
dmi.board.vendor: PK
dmi.board.version: V1.12
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.12:bd11/05/2020:br1.12:efr1.2:svnAcer:pnNitroAN515-43:pvrV1.12:rvnPK:rnOctavia_PKS:rvrV1.12:cvnAcer:ct10:cvrV1.12:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-43
dmi.product.sku:
dmi.product.version: V1.12
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045413/+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 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
*** This bug is a duplicate of bug 2044657 *** https://bugs.launchpad.net/bugs/2044657 ** This bug has been marked a duplicate of bug 2044657 zfs block cloning file system corruption -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+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 2045445] Re: HotFix update zfs related packages to 2.2.2
*** This bug is a duplicate of bug 2044657 *** https://bugs.launchpad.net/bugs/2044657 ** This bug has been marked a duplicate of bug 2044657 zfs block cloning file system corruption -- 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/2045445 Title: HotFix update zfs related packages to 2.2.2 Status in zfs-linux package in Ubuntu: Confirmed Bug description: ~2 weeks ago a bug was detected which can lead to data corruption on zfs pools. most important: https://github.com/openzfs/zfs/issues/15526 which has over 300 comments by now https://github.com/openzfs/zfs/issues/15533 This is bad enough, but a lot of work was done by the developers to get a HotFix out ASAP (2.2.1) and yesterday finally the real fixes with everything that washed up during research in 2.2.2. So while new releases of ZFS are available, nothing of this has lead to new packages for the current Mantic release. I understand that one should be careful with new releases, but these are HotFix releases for serious problems and not a new feature. Most distros included the 2.2.1 release very quickly in their repositories, there is still nothing from Ubuntu. For a distribution which is pushing ZFS (which I highly appreciate and that was the reason to switch to Ubuntu long time ago) this is really not good. So please produce 2.2.2 packages for Mantic ASAP and keep an eye on the openzfs issues on GitHub in the future. No one needs the last too weeks a second time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2045445/+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 2038084] Re: There was an error playing video.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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/2038084
Title:
There was an error playing video.
Status in linux package in Ubuntu:
Expired
Bug description:
cheese '..' but if i try to open a bug with 'ubuntu-bug cheese' cheese
takes control and creates a bug for linux package
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: cheese 44.1-1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.484
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 2 12:09:01 2023
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231002)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
cheese44.1-1
cheese-common 44.1-1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2022
dmi.bios.release: 14.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1402
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H610M-E D4
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd04/01/2022:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610M-ED4: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
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: corrado1873 F wireplumber
/dev/snd/controlC1: corrado1873 F wireplumber
/dev/snd/seq:corrado1867 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-02 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231002)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=7d776968-d1b6-407e-aec1-6854f571aa1d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: mantic wayland-session
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2022
dmi.bios.release: 14.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1402
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H610M-E D4
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.:bvr1402:bd04/01/2022:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610M-ED4: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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038084/+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 2045451] Re: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44
** Attachment added: "dmesg_boot" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+attachment/5725757/+files/dmesg_boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045451 Title: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: 'Synaptics TM2668-002 Touchpad' Touchpad stops working after a while on 'Lenovo Thinkpad 440 S' unknown why/when. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 04:01:51 2023 InstallationDate: Installed on 2023-07-26 (128 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+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 2045451] Re: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44
Follwed instructions found on: https://wiki.ubuntu.com/DebuggingTouchpadDetection -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045451 Title: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: 'Synaptics TM2668-002 Touchpad' Touchpad stops working after a while on 'Lenovo Thinkpad 440 S' unknown why/when. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 04:01:51 2023 InstallationDate: Installed on 2023-07-26 (128 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+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 2045451] Re: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44
** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+attachment/5725756/+files/Xorg.1.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045451 Title: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: 'Synaptics TM2668-002 Touchpad' Touchpad stops working after a while on 'Lenovo Thinkpad 440 S' unknown why/when. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 04:01:51 2023 InstallationDate: Installed on 2023-07-26 (128 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+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 2045451] Re: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44
** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+attachment/5725755/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045451 Title: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: 'Synaptics TM2668-002 Touchpad' Touchpad stops working after a while on 'Lenovo Thinkpad 440 S' unknown why/when. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 04:01:51 2023 InstallationDate: Installed on 2023-07-26 (128 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+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 2045451] Re: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44
** Attachment added: "Xorg.1.log_diff" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+attachment/5725754/+files/Xorg.1.log_diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045451 Title: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: 'Synaptics TM2668-002 Touchpad' Touchpad stops working after a while on 'Lenovo Thinkpad 440 S' unknown why/when. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 04:01:51 2023 InstallationDate: Installed on 2023-07-26 (128 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+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 2045451] [NEW] 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44
Public bug reported: 'Synaptics TM2668-002 Touchpad' Touchpad stops working after a while on 'Lenovo Thinkpad 440 S' unknown why/when. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 04:01:51 2023 InstallationDate: Installed on 2023-07-26 (128 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "dmesg_diff" https://bugs.launchpad.net/bugs/2045451/+attachment/5725750/+files/dmesg_diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045451 Title: 'Synaptics TM2668-002 Touchpad' Touchpad st0 S' unknown why/when.ops working after a while on 'Lenovo Thinkpad 44 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: 'Synaptics TM2668-002 Touchpad' Touchpad stops working after a while on 'Lenovo Thinkpad 440 S' unknown why/when. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 04:01:51 2023 InstallationDate: Installed on 2023-07-26 (128 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045451/+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 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
This patch is also needed for a clean build. 3d8fa78ebd61 scsi: scsi_transport_sas: Add 22.5 Gbps link rate definitions -- 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/2029905 Title: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Bug description: This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get target object based on rphy
[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
Here is the test kernel. https://people.canonical.com/~mreed/dell/lp_2029905_mpi3mr/ -- 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/2029905 Title: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Bug description: This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get target object based on rphy e22bae30667a scsi: mpi3mr: Add expander
[Kernel-packages] [Bug 2045445] Re: HotFix update zfs related packages to 2.2.2
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-49298 -- 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/2045445 Title: HotFix update zfs related packages to 2.2.2 Status in zfs-linux package in Ubuntu: Confirmed Bug description: ~2 weeks ago a bug was detected which can lead to data corruption on zfs pools. most important: https://github.com/openzfs/zfs/issues/15526 which has over 300 comments by now https://github.com/openzfs/zfs/issues/15533 This is bad enough, but a lot of work was done by the developers to get a HotFix out ASAP (2.2.1) and yesterday finally the real fixes with everything that washed up during research in 2.2.2. So while new releases of ZFS are available, nothing of this has lead to new packages for the current Mantic release. I understand that one should be careful with new releases, but these are HotFix releases for serious problems and not a new feature. Most distros included the 2.2.1 release very quickly in their repositories, there is still nothing from Ubuntu. For a distribution which is pushing ZFS (which I highly appreciate and that was the reason to switch to Ubuntu long time ago) this is really not good. So please produce 2.2.2 packages for Mantic ASAP and keep an eye on the openzfs issues on GitHub in the future. No one needs the last too weeks a second time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2045445/+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 2045445] Re: HotFix update zfs related packages to 2.2.2
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/2045445 Title: HotFix update zfs related packages to 2.2.2 Status in zfs-linux package in Ubuntu: Confirmed Bug description: ~2 weeks ago a bug was detected which can lead to data corruption on zfs pools. most important: https://github.com/openzfs/zfs/issues/15526 which has over 300 comments by now https://github.com/openzfs/zfs/issues/15533 This is bad enough, but a lot of work was done by the developers to get a HotFix out ASAP (2.2.1) and yesterday finally the real fixes with everything that washed up during research in 2.2.2. So while new releases of ZFS are available, nothing of this has lead to new packages for the current Mantic release. I understand that one should be careful with new releases, but these are HotFix releases for serious problems and not a new feature. Most distros included the 2.2.1 release very quickly in their repositories, there is still nothing from Ubuntu. For a distribution which is pushing ZFS (which I highly appreciate and that was the reason to switch to Ubuntu long time ago) this is really not good. So please produce 2.2.2 packages for Mantic ASAP and keep an eye on the openzfs issues on GitHub in the future. No one needs the last too weeks a second time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2045445/+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 2045445] [NEW] HotFix update zfs related packages to 2.2.2
Public bug reported: ~2 weeks ago a bug was detected which can lead to data corruption on zfs pools. most important: https://github.com/openzfs/zfs/issues/15526 which has over 300 comments by now https://github.com/openzfs/zfs/issues/15533 This is bad enough, but a lot of work was done by the developers to get a HotFix out ASAP (2.2.1) and yesterday finally the real fixes with everything that washed up during research in 2.2.2. So while new releases of ZFS are available, nothing of this has lead to new packages for the current Mantic release. I understand that one should be careful with new releases, but these are HotFix releases for serious problems and not a new feature. Most distros included the 2.2.1 release very quickly in their repositories, there is still nothing from Ubuntu. For a distribution which is pushing ZFS (which I highly appreciate and that was the reason to switch to Ubuntu long time ago) this is really not good. So please produce 2.2.2 packages for Mantic ASAP and keep an eye on the openzfs issues on GitHub in the future. No one needs the last too weeks a second time. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: bclone zfs ** Summary changed: - HotFix Update zfs related packages to 2.2.2 + HotFix update zfs related packages to 2.2.2 ** Description changed: ~2 weeks ago a bug was detected which can lead to data corruption on zfs pools. most important: https://github.com/openzfs/zfs/issues/15526 which has over 300 comments by now https://github.com/openzfs/zfs/issues/15533 This is bad enough, but a lot of work was done by the developers to get a HotFix out ASAP (2.2.1) and yesterday finally the real fixes with everything that washed up during research in 2.2.2. So while new releases of ZFS are available, nothing of this has lead to new packages for the current Mantic release. I understand that one should be careful with new releases, but these are HotFix releases for serious problems and not a new feature. Most distros included the 2.2.1 - release very quickly in there repositories, there is still nothing from + release very quickly in their repositories, there is still nothing from Ubuntu. For a distribution which is pushing ZFS (which I highly appreciate and that was the reason to switch to Ubuntu long time ago) this is really not good. So please produce 2.2.2 packages for Mantic ASAP and keep an eye on the openzfs issues on GitHub in the future. No one needs the last too weeks a second time. -- 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/2045445 Title: HotFix update zfs related packages to 2.2.2 Status in zfs-linux package in Ubuntu: New Bug description: ~2 weeks ago a bug was detected which can lead to data corruption on zfs pools. most important: https://github.com/openzfs/zfs/issues/15526 which has over 300 comments by now https://github.com/openzfs/zfs/issues/15533 This is bad enough, but a lot of work was done by the developers to get a HotFix out ASAP (2.2.1) and yesterday finally the real fixes with everything that washed up during research in 2.2.2. So while new releases of ZFS are available, nothing of this has lead to new packages for the current Mantic release. I understand that one should be careful with new releases, but these are HotFix releases for serious problems and not a new feature. Most distros included the 2.2.1 release very quickly in their repositories, there is still nothing from Ubuntu. For a distribution which is pushing ZFS (which I highly appreciate and that was the reason to switch to Ubuntu long time ago) this is really not good. So please produce 2.2.2 packages for Mantic ASAP and keep an eye on the openzfs issues on GitHub in the future. No one needs the last too weeks a second time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2045445/+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 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems
Reassigning to xorg-server initially. Ubuntu doesn't have gldriver-test to enable xorg desktops to work on a raspi5. So is there an equivalent package for Ubuntu or should gldriver-test be added to the ubuntu repo? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in linux-raspi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: New Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2044718/+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 2045443] [NEW] Ubuntu-5.15.0-89.99 breaks virtio-net spec and doesn't boot
Public bug reported:
I use a non-qemu VMM, cloud-hypervisor. It looks like a patch was
applied, that introduced a bug, a week later another patch got written
to fix that bug, and that second patch was not applied in Ubuntu's
release, but is seen in Greg KH's 5.15 branch.
The result of the bug is the kernel will not boot.
Cumulative diff:
```
> git diff Ubuntu-5.15.0-86.96 Ubuntu-5.15.0-89.99 drivers/net/virtio_net.c
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
index 0351f86494f1..af335f8266c2 100644
--- a/drivers/net/virtio_net.c
+++ b/drivers/net/virtio_net.c
@@ -3319,6 +3319,8 @@ static int virtnet_probe(struct virtio_device *vdev)
}
}
+ _virtnet_set_queues(vi, vi->curr_queue_pairs);
+
/* serialize netdev register + virtio_device_ready() with ndo_open() */
rtnl_lock();
@@ -3339,8 +3341,6 @@ static int virtnet_probe(struct virtio_device *vdev)
goto free_unregister_netdev;
}
- virtnet_set_queues(vi, vi->curr_queue_pairs);
-
/* Assume link up if device can't report link status,
otherwise get link status from config. */
netif_carrier_off(dev);
```
Blamed Commit:
```
commit 5e0545ef5682562ffef072138d9340ea36a2ebc9
Author: Jason Wang
Date: Tue Jul 25 03:20:49 2023 -0400
virtio-net: fix race between set queues and probe
BugLink: https://bugs.launchpad.net/bugs/2035400
commit 25266128fe16d5632d43ada34c847d7b8daba539 upstream.
A race were found where set_channels could be called after registering
but before virtnet_set_queues() in virtnet_probe(). Fixing this by
moving the virtnet_set_queues() before netdevice registering. While at
it, use _virtnet_set_queues() to avoid holding rtnl as the device is
not even registered at that time.
Cc: sta...@vger.kernel.org
Fixes: a220871be66f ("virtio-net: correctly enable multiqueue")
Signed-off-by: Jason Wang
Acked-by: Michael S. Tsirkin
Reviewed-by: Xuan Zhuo
Link: https://lore.kernel.org/r/20230725072049.617289-1-jasow...@redhat.com
Signed-off-by: Jakub Kicinski
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Stefan Bader
```
Investigation into Greg KH's 5.15 branch shows the (unapplied?) followup
as:
```
commit 431db3f48c286462ad7453ccdf284f590aafa949
Author: Jason Wang
Date: Wed Aug 9 23:12:56 2023 -0400
virtio-net: set queues after driver_ok
commit 51b813176f098ff61bd2833f627f5319ead098a5 upstream.
Commit 25266128fe16 ("virtio-net: fix race between set queues and
probe") tries to fix the race between set queues and probe by calling
_virtnet_set_queues() before DRIVER_OK is set. This violates virtio
spec. Fixing this by setting queues after virtio_device_ready().
Note that rtnl needs to be held for userspace requests to change the
number of queues. So we are serialized in this way.
Fixes: 25266128fe16 ("virtio-net: fix race between set queues and probe")
Reported-by: Dragos Tatulea
Acked-by: Michael S. Tsirkin
Signed-off-by: Jason Wang
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
```
Boot stack trace:
```
[ 28.129660] watchdog: BUG: soft lockup - CPU#1 stuck for 26s!
[systemd-udevd:165]
[ 28.130265] Modules linked in: crct10dif_pclmul crc32_pclmul
ghash_clmulni_intel aesni_intel crypto_simd cryptd virtio_net(+)
net_failover virtio_rng failover virtio_blk
[ 28.131396] CPU: 1 PID: 165 Comm: systemd-udevd Not tainted
5.15.0-89-generic https://github.com/ubicloud/ubicloud/pull/99-Ubuntu
[ 28.131997] Hardware name: Cloud Hypervisor cloud-hypervisor, BIOS 0
[ 28.132479] RIP: 0010:virtnet_send_command+0x10b/0x170 [virtio_net]
[ 28.132951] Code: 0b 83 c1 d8 85 c0 0f 88 d2 6e 00 00 48 8b 7b 08 e8
6a 72 c1 d8 84 c0 75 11 eb 56 48 8b 7b 08 e8 6b 5e c1 d8 84 c0 75 17 f3
90 <48> 8b 7b 08 48 8d b5 6c ff ff ff e8 f5 71 c1 d8 48 85 c0 74 dc 48
[ 28.134326] RSP: 0018:9b0c4064f9b8 EFLAGS: 0246
[ 28.134720] RAX: RBX: 89dfc0d13980 RCX:
0a20
[ 28.135252] RDX: RSI: 9b0c4064f9bc RDI:
89dfc7cc00c0
[ 28.135787] RBP: 9b0c4064fa50 R08: 0001 R09:
0003
[ 28.136316] R10: 0003 R11: 0002 R12:
9b0c4064f9e0
[ 28.136851] R13: 0002 R14: 0004 R15:
89dfc0c49400
[ 28.137381] FS: 7feeba10e8c0() GS:89e0f7d0()
knlGS:
[ 28.137981] CS: 0010 DS: ES: CR0: 80050033
[ 28.138408] CR2: 7feeba90a0f8 CR3: 000100258000 CR4:
00350ee0
[ 28.138940] Call Trace:
[ 28.139129]
[ 28.139291] ? show_trace_log_lvl+0x1d6/0x2ea
[ 28.139627] ? show_trace_log_lvl+0x1d6/0x2ea
[ 28.139957] ? _virtnet_set_queues+0xbb/0x100 [virtio_net]
[ 28.140369] ? show_regs.part.0+0x23/0x29
[ 28.140672] ? show_regs.cold+0x8/0xd
[ 28.140950] ?
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
I suppose the answer is to edit the postinst script albeit it looking for some kind of compile time function when trying to build the kernel module. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Just to confirm I have the same problem on 22.04 with kernel: Building initial module for 6.2.0-37-generic :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead :4: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :4: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead :3: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :3: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead :2: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :2: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-37-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1076.71)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1076.71) for focal have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/unknown (arm64) adv-17v35x/unknown (arm64) bbswitch/unknown (arm64) ddcci-driver-linux/unknown (arm64) dm-writeboost/unknown (arm64) dpdk/unknown (arm64) fwts/unknown (arm64) glibc/unknown (arm64) gost-crypto/unknown (arm64) iptables-netflow/unknown (arm64) jool/unknown (arm64) langford/unknown (arm64) lime-forensics/unknown (arm64) linux-bluefield/unknown (arm64) lttng-modules/unknown (arm64) lxc/unknown (arm64) mali-midgard/unknown (arm64) nat-rtsp/unknown (arm64) openafs/unknown (arm64) openrazer/unknown (arm64) r8168/unknown (arm64) snapd/unknown (arm64) west-chamber/unknown (arm64) wireguard-linux-compat/unknown (arm64) xtables-addons/unknown (arm64) zfs-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
https://lists.ubuntu.com/archives/kernel-team/2023-December/147391.html
** Description changed:
SRU Justification
[Impact]
- A stable update from LP: #1853180 was carried forward to the Lunar 6.2
- and Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
+ An update from LP: #1853180 was carried forward to the Lunar 6.2 and
+ Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
** Changed in: linux-aws (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Lunar:
In Progress
Status in linux-aws source package in Mantic:
In Progress
Status in linux-aws source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
An update from LP: #1853180 was carried forward to the Lunar 6.2 and
Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2045428] [NEW] AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Public bug reported:
SRU Justification
[Impact]
A stable update from LP: #1853180 was carried forward to the Lunar 6.2
and Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
** Affects: linux-aws (Ubuntu)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Lunar)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Mantic)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Noble)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Package changed: linux (Ubuntu) => linux-aws (Ubuntu)
** Description changed:
SRU Justification
[Impact]
A stable update from LP: #1853180 was carried forward to the Lunar 6.2
- kernel. As it did not cause a conflict it likely escaped notice when the
- Jammy AWS kernel was forward ported. Commit
+ and Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
+ notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
** Also affects: linux-aws (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Noble)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-aws source package in Lunar:
In Progress
Status in linux-aws source package in Mantic:
In Progress
Status in linux-aws source package in Noble:
In Progress
Bug description:
SRU Justification
[Impact]
A stable update from LP: #1853180 was carried forward to the Lunar 6.2
and Mantic 6.5 kernels. As it did not cause a conflict it likely
escaped notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
I ran a quick check. Everything up to these exists already in our 6.5 kernel. 9134211f7bed missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~5 6f81b1cfdf33 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~4 d9adb81e67e9 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~3 e7a8648e1ce2 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~2 d9a5ab0ea98f missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~1 9a9068b2afa0 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2 82b2fb52d6ec does not appear in Ubuntu. Best guess on first appearance upstream: v6.7-rc1 6fa21eab82be does not appear in either ubuntu or the upstream kernel. c9260ff28ee5 does not appear in either ubuntu or the upstream kernel. cb5b60894602 does not appear in either ubuntu or the upstream kernel. 1193a89d2b6d does not appear in either ubuntu or the upstream kernel. b4d94164ff32 does not appear in either ubuntu or the upstream kernel. Those last five are not in any tree I checked (mainline, linux-next). I'd rather not pull any of these until they've landed at least in linux- next. Otherwise, -- 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/2045233 Title: [Ubuntu 22.04.04]: mpi3mr driver update request Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. 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 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number
[Kernel-packages] [Bug 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed -- 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/2039208 Title: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. [Fix] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+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 2045425] [NEW] Windows VM slower performance with Passmark vs Ubuntu VM
Public bug reported: Summary : A Windows VM(KVM) on 22.04.3 is 10%(SMT off) to 16%(SMT on) slower running Passmark vs a Ubuntu 22.04.3 VM(KVM). The results should be within 1% of each other. System Information : Dell - AMD EPYC 7543 32-Core Processor, 2801 Mhz, 32 Core(s), 32 Logical Processor(s) Zen 3 (Milan) BIOS - 2.12.4 FW (iDRAC Firmware Version7.00.30.00) NUMA Nodes Per Socket 1(default) Memory - 512 GB of DRAM DDR4 OS : Ubuntu 22.04.3 Setup: Install Ubuntu 22.04.3 and then setup 2 VMs one with Win 22 std. and another one with Ubuntu 22.04.3. Install Passmark benchmark on both the VMs and then run the “Single CPU Threaded” benchmark on both the OS with SMT enable and disable mode. Passmark Download link : https://www.passmark.com/products/pt_linux/download.php Linux Setup version: PerformanceTest Linux x86 64-bit 5.4 MB, v11.0 Build 1002, October 19 2023 Microsoft setup version: Download PerformanceTest 11.0 x86 102 MB, Build 1007 For Intel and AMD x86 CPUs Results : *** Bare metal *** Windows 2022 SMT ON: Win22 VM 1% slower SMT OFF: Win22 VM 1% slower SMT Run1Run2Run3Average On 2766276827712768.33 OFF 2773276627652768 Ubuntu 22.04 SMT Run1Run2Run3Average On 2777277727752776.33 OFF 2798279227922794 KVM SMT ON : Win22 VM 16% slower SMT OFF: Win22 VM 10% slower Host: Ubuntu 22.04 VM: Win server 22 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On 2356228722892310.67 OFF 2424245925662483 Host Ubuntu 22.04 KVM with Ubuntu 22.04 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On 2730274127292733.33 OFF 2745274627462745.67 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Windows VM 10% lower performance with Passmark vs Ubuntu VM + Windows VM slower performance with Passmark vs Ubuntu VM -- 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/2045425 Title: Windows VM slower performance with Passmark vs Ubuntu VM Status in linux package in Ubuntu: New Bug description: Summary : A Windows VM(KVM) on 22.04.3 is 10%(SMT off) to 16%(SMT on) slower running Passmark vs a Ubuntu 22.04.3 VM(KVM). The results should be within 1% of each other. System Information : Dell - AMD EPYC 7543 32-Core Processor, 2801 Mhz, 32 Core(s), 32 Logical Processor(s) Zen 3 (Milan) BIOS - 2.12.4 FW (iDRAC Firmware Version7.00.30.00) NUMA Nodes Per Socket 1(default) Memory - 512 GB of DRAM DDR4 OS : Ubuntu 22.04.3 Setup: Install Ubuntu 22.04.3 and then setup 2 VMs one with Win 22 std. and another one with Ubuntu 22.04.3. Install Passmark benchmark on both the VMs and then run the “Single CPU Threaded” benchmark on both the OS with SMT enable and disable mode. Passmark Download link : https://www.passmark.com/products/pt_linux/download.php Linux Setup version: PerformanceTest Linux x86 64-bit 5.4 MB, v11.0 Build 1002, October 19 2023 Microsoft setup version: Download PerformanceTest 11.0 x86 102 MB, Build 1007 For Intel and AMD x86 CPUs Results : *** Bare metal *** Windows 2022 SMT ON: Win22 VM 1% slower SMT OFF: Win22 VM 1% slower SMT Run1Run2Run3Average On2766276827712768.33 OFF 2773276627652768 Ubuntu 22.04 SMT Run1Run2Run3Average On2777277727752776.33 OFF 2798279227922794 KVM SMT ON : Win22 VM 16% slower SMT OFF: Win22 VM 10% slower Host: Ubuntu 22.04 VM: Win server 22 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On2356228722892310.67 OFF 2424245925662483 Host Ubuntu 22.04 KVM with Ubuntu 22.04 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On2730274127292733.33 OFF 2745274627462745.67 To manage notifications about this bug go to:
[Kernel-packages] [Bug 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Opinion ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium -- 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/2045233 Title: [Ubuntu 22.04.04]: mpi3mr driver update request Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. 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 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer
[Kernel-packages] [Bug 2045412] Re: [mantic] Allow module compression to be turned off
** Tags added: patch -- 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/2045412 Title: [mantic] Allow module compression to be turned off Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: Fix Committed Bug description: [SRU Justification] == Impact 23.10/Mantic (and newer) kernels are packaged with modules compressed to save disk space and load time. This will remain unchanged. For simplifying backports into 22.04/Jammy LTS we need a way to turn this off when compiling those newer kernels as HWE kernels. == Fix Add an option to turn off module compression when packaging the kernel. This will be unset when compiling Mantic and newer. So there will be no change there. == Testcase Verify that in Mantic the size of the modules package(s) does not change. == Regression potential The compression could be accidentally disabled in newer kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045412/+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 1628204] Re: linux: 4.4.0-41.61 -proposed tracker
best information like the http://cryptopostage.info/ -- 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/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 2041996] Re: pwr-mlxbf: Several bug fixes for focal
This bug is awaiting verification that the linux-bluefield/5.4.0-1076.82 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-done- focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed- focal-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2041996 Title: pwr-mlxbf: Several bug fixes for focal Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] There is are several changes that needs to be made to pwr-mlxbf in focal: * There is a race condition between gpio-mlxbf2.c driver being loaded and pwr-mlxbf.c being loaded * When the module is removed, there is a panic due to NULL pointer access * soft reset needs to be replaced by graceful reboot [Fix] * Fix race condition between gpio-mlxbf2.c driver being loaded and pwr-mlxbf.c being loaded * Fix panic due to access to NULL pointer when driver is removed via rmmod * support graceful reboot instead of soft reset [Test Case] * all test cases are for BF2: * trigger the gpio toggling from the BMC: ipmitool raw 0x32 0xA1 0x02 This should trigger a graceful reboot of the DPU. * rmmod/modprobe * reboot test and make sure the driver is always loaded [Regression Potential] * Run the 100 reboot test and make sure that the driver is loaded with no issues. That the gpio graceful reboot works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2041996/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
** 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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
In Progress
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in firmware-sof source package in Mantic:
In Progress
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2044512] Re: Build failure if run in a console
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/2044512 Title: Build failure if run in a console Status in linux package in Ubuntu: New Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: New Bug description: [Impact] Build fails if run in a console: $ debian/rules binary ... # Compress kernel modules find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm stdout is a console, aborting make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123 [Test Case] See above. [Where Problems Could Occur] Build failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044512/+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 2044512] Re: Build failure if run in a console
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Importance: Medium => High ** Changed in: linux (Ubuntu Noble) Importance: Medium => High ** Changed in: linux (Ubuntu Mantic) Importance: High => Medium ** Changed in: linux (Ubuntu Noble) Importance: High => Medium -- 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/2044512 Title: Build failure if run in a console Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: [Impact] Build fails if run in a console: $ debian/rules binary ... # Compress kernel modules find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm stdout is a console, aborting make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123 [Test Case] See above. [Where Problems Could Occur] Build failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044512/+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 2045412] Re: [mantic] Allow module compression to be turned off
** Attachment added: "Submitted packaging change" https://bugs.launchpad.net/ubuntu/mantic/+source/linux/+bug/2045412/+attachment/5725687/+files/20231120-%5BMANTIC%5D%5BNOBLE%5D%5BUNSTABLE%5D%5BPATCH%5D%20UBUNTU_%20%5BPackaging%5D%20make%20ZSTD%20module%20compression%20conditional-8840.txt ** 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/2045412 Title: [mantic] Allow module compression to be turned off Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: Fix Committed Bug description: [SRU Justification] == Impact 23.10/Mantic (and newer) kernels are packaged with modules compressed to save disk space and load time. This will remain unchanged. For simplifying backports into 22.04/Jammy LTS we need a way to turn this off when compiling those newer kernels as HWE kernels. == Fix Add an option to turn off module compression when packaging the kernel. This will be unset when compiling Mantic and newer. So there will be no change there. == Testcase Verify that in Mantic the size of the modules package(s) does not change. == Regression potential The compression could be accidentally disabled in newer kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045412/+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 2045412] [NEW] [mantic] Allow module compression to be turned off
Public bug reported: [SRU Justification] == Impact 23.10/Mantic (and newer) kernels are packaged with modules compressed to save disk space and load time. This will remain unchanged. For simplifying backports into 22.04/Jammy LTS we need a way to turn this off when compiling those newer kernels as HWE kernels. == Fix Add an option to turn off module compression when packaging the kernel. This will be unset when compiling Mantic and newer. So there will be no change there. == Testcase Verify that in Mantic the size of the modules package(s) does not change. == Regression potential The compression could be accidentally disabled in newer kernels. ** Affects: linux (Ubuntu) Importance: Medium Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Fix Committed ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Summary changed: - [mantic] Make ZSTD module compression optional + [mantic] Allow module compression to be turned off -- 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/2045412 Title: [mantic] Allow module compression to be turned off Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: Fix Committed Bug description: [SRU Justification] == Impact 23.10/Mantic (and newer) kernels are packaged with modules compressed to save disk space and load time. This will remain unchanged. For simplifying backports into 22.04/Jammy LTS we need a way to turn this off when compiling those newer kernels as HWE kernels. == Fix Add an option to turn off module compression when packaging the kernel. This will be unset when compiling Mantic and newer. So there will be no change there. == Testcase Verify that in Mantic the size of the modules package(s) does not change. == Regression potential The compression could be accidentally disabled in newer kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045412/+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 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9
** 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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042060 Title: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume from suspend. The audio play and capture functions are not working after resume from S3. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/. [Test Case] 1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA . 2. Perform system suspend/resume at least 3 times. 3. Verify the audio functions, including playback and capture [Where problems could occur] Only affect specific laptops with the CS35L41 HDA. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042060/+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 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** 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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2039151 Title: Support speaker mute hotkey for Cirrus CS35L41 HDA codec Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Some systems use a special hotkey to mute speaker audio. On systems using CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI notifications to detect whether the hotkey is triggered to switch the mute state. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t. [Test Case] 1. Power on the machine with CS35L41 HDA and the speaker mute hotkey. 2. Verify the audio functions 3. Verify if the speaker can be mute/unmute by the hotkey. [Where problems could occur] Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey on keyboard. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039151/+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 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
** 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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Won't Fix Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+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 2043730] Re: Update io_uring to 6.6
Skipped "io_uring: annotate the struct io_kiocb slab for appropriate user copy" since this was already applied as part of upstream stable v6.5.5. Also skipped "io_uring/net: fix iter retargeting for selected buf" for the same reason. Skipped "io_uring/fs: remove sqe->rw_flags checking from LINKAT" because this is already applied as part of upstream stable v6.5.6. ** 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/2043730 Title: Update io_uring to 6.6 Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] io_uring is a fast-developed subsystem in the Linux kernel. In order to keep up with the latest changes such that applying further fixes are possible, it should be updated to a more recent version. [Test case] Given the general update, there are no specific test cases. [Potential regression] io_uring users only would be affected given most changes are restricted to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043730/+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 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** 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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid 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.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html which is included in v6.7-rc1 7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+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 2041613] Re: correct cephfs pull request for uidmap support
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/2041613 Title: correct cephfs pull request for uidmap support Status in linux package in Ubuntu: New Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: New Bug description: [ Impact ] * During mantic dev cycle, we pulled all of cephfs testing patches, rather than uidmapshift patches alone * We also pulled in debug patches that generate a lot of dmesg and delays in the cephfs module [ Test Plan ] * run ceph fs and experience less dmesg at info level [ Where problems could occur ] * Hopefully the reverts were done correctly, and none of the messages reference non-existing things, in all the code paths. [ Other Info ] * Story time how we got here: The following pull requests BugLink: https://bugs.launchpad.net/bugs/2038522 BugLink: https://bugs.launchpad.net/bugs/2032959 generated the following commit list 1: eddf9ed788 UBUNTU: [Config] disable shiftfs 72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default 80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts 9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op 1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr 8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir 5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter 19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in create_request_message() 6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request 8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put 55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32 54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct ceph_mds_request_args_ext an union f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug logs b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/ cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client() 42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers 9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support 8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client caps still outstanding a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put before unmounting 17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio with a non-NULL ->private 834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're waiting too long for them 498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128 3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new fscrypt helper 8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for fscrypt 288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish when unmounting 435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting 862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot naming limitations 904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked directories a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes 9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and writepages 0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for encrypted inodes efed7d1764 UBUNTU: SAUCE: ceph: add truncate size handling support for fscrypt 5d65284a6a UBUNTU: SAUCE: ceph: add object version support for sync read d76cff7c37 UBUNTU: SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read 53d1c3958e UBUNTU: SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support 7ecbaa5849 UBUNTU: SAUCE: ceph: add infrastructure for file encryption and decryption 4142d15305 UBUNTU: SAUCE: ceph: handle fscrypt fields in cap messages from MDS 53507ac6a8 UBUNTU: SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces b9936d13f4 UBUNTU:
[Kernel-packages] [Bug 2043724] Re: Focal update: v5.4.259 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/2043724 Title: Focal update: v5.4.259 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.259 upstream stable release from git://git.kernel.org/ RDMA/cxgb4: Check skb value for failure to allocate lib/test_meminit: fix off-by-one error in test_pages() pwm: hibvt: Explicitly set .polarity in .get_state() HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect quota: Fix slow quotaoff net: prevent address rewrite in kernel_bind() drm: etvnaviv: fix bad backport leading to warning drm/msm/dsi: skip the wait for video mode done if not applicable ravb: Fix up dma_free_coherent() call in ravb_remove() ieee802154: ca8210: Fix a potential UAF in ca8210_probe mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type xen-netback: use default TX queue size for vifs drm/vmwgfx: fix typo of sizeof argument ixgbe: fix crash with empty VF macvlan list net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() nfc: nci: assert requested protocol is valid workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask() dmaengine: stm32-mdma: abort resume if no ongoing transfer usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read usb: dwc3: Soft reset phy on probe for host usb: musb: Get the musb_qh poniter after musb_giveback usb: musb: Modify the "HWVers" register address iio: pressure: bmp280: Fix NULL pointer exception iio: pressure: dps310: Adjust Timeout Settings iio: pressure: ms5611: ms5611_prom_is_valid false negative bug mcb: remove is_added flag from mcb_device struct libceph: use kernel_connect() ceph: fix incorrect revoked caps assert in ceph_fill_file_size() Input: powermate - fix use-after-free in powermate_config_complete Input: psmouse - fix fast_reconnect function for PS/2 mode Input: xpad - add PXN V900 support cgroup: Remove duplicates in cgroup v1 tasks file pinctrl: avoid unsafe code pattern in find_pinctrl() usb: gadget: udc-xilinx: replace memcpy with memcpy_toio usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs dmaengine: mediatek: Fix deadlock caused by synchronize_irq() powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE powerpc/64e: Fix wrong test in __ptep_test_and_clear_young() ravb: Fix use-after-free issue in ravb_tx_timeout_work() Documentation: sysctl: align cells in second content column usb: hub: Guard against accesses to uninitialized BOS descriptors Bluetooth: hci_event: Ignore NULL link key Bluetooth: Reject connection with the device which has same BD_ADDR Bluetooth: Fix a refcnt underflow problem for hci_conn Bluetooth: vhci: Fix race when opening vhci device Bluetooth: hci_event: Fix coding style Bluetooth: avoid memcmp() out of bounds warning ice: fix over-shifted variable nfc: nci: fix possible NULL pointer dereference in send_acknowledge() regmap: fix NULL deref on lookup KVM: x86: Mask LVTPC when handling a PMI netfilter: nft_payload: fix wrong mac header matching qed: fix LL2 RX buffer allocation xfrm: fix a data-race in xfrm_gen_index() xfrm: interface: use DEV_STATS_INC() net: ipv4: fix return value check in esp_remove_trailer net: ipv6: fix return value check in esp_remove_trailer net: rfkill: gpio: prevent value glitch during probe tcp: fix excessive TLP and RACK timeouts from HZ rounding tcp: tsq: relax tcp_small_queue_check() when rtx queue contains a single skb tun: prevent negative ifindex ipv4: fib: annotate races around nh->nh_saddr_genid and nh->nh_saddr net: usb: smsc95xx: Fix an error code in smsc95xx_reset() i40e: prevent crash on probe if hw registers have invalid values net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve neighbor: tracing: Move pin6 inside CONFIG_IPV6=y section netfilter: nft_set_rbtree: .deactivate fails if element has expired net: pktgen: Fix interface flags printing resource: Add irqresource_disabled() ACPI: Drop acpi_dev_irqresource_disabled() ACPI: resource: Skip IRQ override on Asus Vivobook
[Kernel-packages] [Bug 2042107] Re: Focal update: v5.4.258 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/2042107
Title:
Focal update: v5.4.258 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.258 upstream stable release
from git://git.kernel.org/
NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
tracing: Increase trace array ref count on enable and filter files
ata: libahci: clear pending interrupt status
ext4: remove the 'group' parameter of ext4_trim_extent
ext4: add new helper interface ext4_try_to_trim_range()
ext4: scope ret locally in ext4_try_to_trim_range()
ext4: change s_last_trim_minblks type to unsigned long
ext4: mark group as trimmed only if it was fully scanned
ext4: replace the traditional ternary conditional operator with with
max()/min()
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
ASoC: meson: spdifin: start hw on dai probe
netfilter: nf_tables: disallow element removal on anonymous sets
bpf: Avoid deadlock when using queue and stack maps from NMI
selftests/tls: Add {} to avoid static checker warning
selftests: tls: swap the TX and RX sockets in some tests
ASoC: imx-audmix: Fix return error with devm_clk_get()
i40e: Fix for persistent lldp support
UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: i40e Fix GPF when deleting VMs"
i40e: Remove scheduling while atomic possibility
i40e: Fix warning message and call stack during rmmod i40e driver
i40e: Fix VF VLAN offloading when port VLAN is configured
powerpc/perf/hv-24x7: Update domain value check
dccp: fix dccp_v4_err()/dccp_v6_err() again
net: hns3: add 5ms delay before clear firmware reset irq source
net: bridge: use DEV_STATS_INC()
team: fix null-ptr-deref when team device type is changed
net: rds: Fix possible NULL-pointer dereference
gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
scsi: qla2xxx: Fix update_fcport for current_topology
scsi: qla2xxx: Fix deletion race condition
drm/amd/display: Reinstate LFC optimization
drm/amd/display: Fix LFC multiplier changing erratically
drm/amd/display: prevent potential division by zero errors
ata: libata: disallow dev-initiated LPM transitions to unsupported states
MIPS: Alchemy: only build mmc support helpers if au1xmmc is enabled
clk: tegra: fix error return case for recalc_rate
ARM: dts: ti: omap: motorola-mapphone: Fix abe_clkctrl warning on boot
bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart wake-up
xtensa: add default definition for XCHAL_HAVE_DIV32
xtensa: iss/network: make functions static
xtensa: boot: don't add include-dirs
xtensa: boot/lib: fix function prototypes
gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip
parisc: sba: Fix compile warning wrt list of SBA devices
parisc: iosapic.c: Fix sparse warnings
parisc: drivers: Fix sparse warning
parisc: irq: Make irq_stack_union static to avoid sparse warning
selftests/ftrace: Correctly enable event in instance-event.tc
ring-buffer: Avoid softlockup in ring_buffer_resize()
ata: libata-eh: do not clear ATA_PFLAG_EH_PENDING in ata_eh_reset()
spi: nxp-fspi: reset the FLSHxCR1 registers
bpf: Clarify error expectations from bpf_clone_redirect
powerpc/watchpoints: Annotate atomic context in more places
ncsi: Propagate carrier gain/loss events to the NCSI controller
fbdev/sh7760fb: Depend on FB=y
nvme-pci: do not set the NUMA node of device if it has none
watchdog: iTCO_wdt: No need to stop the timer in probe
watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running
i40e: improve locking of mac_filter_hash
i40e: always propagate error value in i40e_set_vsi_promisc()
i40e: fix return of uninitialized aq_ret in i40e_set_vsi_promisc
smack: Record transmuting in smk_transmuted
smack: Retrieve transmuting information in smack_inode_getsecurity()
Smack:- Use overlay inode label in smack_inode_copy_up()
serial: 8250_port: Check IRQ data before use
nilfs2: fix potential use after free in
[Kernel-packages] [Bug 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Lunar) Status: In Progress => 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/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid 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.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Lunar)
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/2043841
Title:
kernel BUG: io_uring openat triggers audit reference count underflow
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
occurs during io_uring openat audit processing. I have a kernel patch
that was accepted into the upstream kernel as well as the v6.6,
v6.5.9, and v6.1.60 releases. The bug was first introduced in the
upstream v5.16 kernel.
I do not see the change yet in:
* The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel
repository.
* The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.
Can this upstream commit be cherry picked?
The upstream commit is:
03adc61edad49e1bbecfb53f7ea5d78f398fe368
The upstream patch thread is:
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u
The maintainer pull request thread is:
https://lore.kernel.org/lkml/20231019-kampfsport-
metapher-e5211d7be247@brauner
The pre-patch discussion thread is:
https://lore.kernel.org/io-
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u
The commit log message is:
commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
Author: Dan Clash
Date: Thu Oct 12 14:55:18 2023 -0700
audit,io_uring: io_uring openat triggers audit reference count
underflow
An io_uring openat operation can update an audit reference count
from multiple threads resulting in the call trace below.
A call to io_uring_submit() with a single openat op with a flag of
IOSQE_ASYNC results in the following reference count updates.
These first part of the system call performs two increments that
do not race.
do_syscall_64()
__do_sys_io_uring_enter()
io_submit_sqes()
io_openat_prep()
__io_openat_prep()
getname()
getname_flags() /* update 1 (increment) */
__audit_getname() /* update 2 (increment) */
The openat op is queued to an io_uring worker thread which starts the
opportunity for a race. The system call exit performs one decrement.
do_syscall_64()
syscall_exit_to_user_mode()
syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
audit_reset_context()
putname() /* update 3 (decrement) */
The io_uring worker thread performs one increment and two decrements.
These updates can race with the system call decrement.
io_wqe_worker()
io_worker_handle_work()
io_wq_submit_work()
io_issue_sqe()
io_openat()
io_openat2()
do_filp_open()
path_openat()
__audit_inode() /* update 4 (increment) */
putname() /* update 5 (decrement) */
__audit_uring_exit()
audit_reset_context()
putname() /* update 6 (decrement) */
The fix is to change the refcnt member of struct audit_names
from int to atomic_t.
kernel BUG at fs/namei.c:262!
Call Trace:
...
? putname+0x68/0x70
audit_reset_context.part.0.constprop.0+0xe1/0x300
__audit_uring_exit+0xda/0x1c0
io_issue_sqe+0x1f3/0x450
? lock_timer_base+0x3b/0xd0
io_wq_submit_work+0x8d/0x2b0
? __try_to_del_timer_sync+0x67/0xa0
io_worker_handle_work+0x17c/0x2b0
io_wqe_worker+0x10a/0x350
Cc: sta...@vger.kernel.org
Link:
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support
to io_uring")
Signed-off-by: Dan Clash
Link:
https://lore.kernel.org/r/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
Reviewed-by: Jens Axboe
Signed-off-by: Christian Brauner
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043841/+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 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** 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/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+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 2043527] Re: STONEY not supported in kfd
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: mantic -- 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/2043527 Title: STONEY not supported in kfd Status in linux package in Ubuntu: New Bug description: I'm running lubuntu 23.10 (Mantic Minotaur) on an HP Chromebook 11A G8 EE, board name 'BARLA', using the current MrChromebox BIOS. The thing takes ages (+3 min.) to cold boot and play any video. (Plus there's no sound from the internal speakers, which I knew about, separate issue, just noting that here for posterity. I pair with a Bluetooth headset that works fine.) On boot, before the splash screen, I see in this order, a soft lockup error, the error in the title of this post, and errors about the audio. From journalctl: Nov 14 09:33:01 uname-barla kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [(udev-worker):115] Nov 14 09:33:01 uname-barla kernel: [drm] initializing kernel modesetting (STONEY 0x1002:0x98E4 0x1002:0x1EB0 0xEB). Nov 14 09:33:01 uname-barla kernel: kfd kfd: amdgpu: STONEY not supported in kfd From inxi: System: Kernel: 6.5.0-10-generic arch: x86_64 bits: 64 compiler: N/A Desktop: LXQt v: 1.3.0 Distro: Ubuntu 23.10 (Mantic Minotaur) Machine: Type: Laptop System: Google product: Barla v: rev7 serial: Mobo: Google model: Barla v: rev7 serial: UEFI: coreboot v: MrChromebox-4.21.1 date: 10/29/2023 Battery: ID-1: BAT0 charge: 19.4 Wh (41.9%) condition: 46.3/47.4 Wh (97.7%) volts: 7.5 min: 7.7 model: 333-1D- GH02047 status: discharging CPU: Info: dual core model: AMD A4-9120C RADEON R4 5 COMPUTE CORES 2C+3G bits: 64 type: MCP arch: Excavator rev: 0 cache: L1: 192 KiB L2: 2 MiB Speed (MHz): avg: 1200 min/max: 1200/1600 boost: enabled cores: 1: 1200 2: 1200 bogomips: 6387 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] driver: amdgpu v: kernel arch: GCN-3 bus-ID: 00:01.0 Device-2: Quanta HP TrueVision HD Camera driver: uvcvideo type: USB bus-ID: 1-1.1:3 Display: x11 server: X.Org v: 1.21.1.9 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1366x768~60Hz API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: active: gbm,x11,surfaceless,device inactive: wayland API: OpenGL v: 4.5 vendor: amd mesa v: 23.2.1-1ubuntu3 glx-v: 1.4 direct-render: yes renderer: AMD Radeon R3 Graphics (stoney LLVM 15.0.7 DRM 3.54 6.5.0-10-generic) Audio: Device-1: AMD driver: snd_hda_intel v: kernel bus-ID: 00:01.1 API: ALSA v: k6.5.0-10-generic status: kernel-api Server-1: PipeWire v: 0.3.84 status: active Network: Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard driver: rtw_8822ce v: N/A port: 1000 bus-ID: 01:00.0 IF: wlp1s0 state: up mac: Bluetooth: Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB bus-ID: 1-1.2:4 Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 5.1 lmp-v: 10 Drives: Local Storage: total: 29.12 GiB used: 9.01 GiB (30.9%) ID-1: /dev/mmcblk1 vendor: Hynix model: hB8aP size: 29.12 GiB Partition: ID-1: / size: 28.2 GiB used: 9 GiB (31.9%) fs: ext4 dev: /dev/mmcblk1p2 ID-2: /boot/efi size: 299.4 MiB used: 7.7 MiB (2.6%) fs: vfat dev: /dev/mmcblk1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 29.8 C mobo: N/A gpu: amdgpu temp: 29.0 C Fan Speeds (rpm): N/A Info: Processes: 175 Uptime: 6h 35m Memory: total: 4 GiB note: est. available: 3.54 GiB used: 881.3 MiB (24.3%) Init: systemd target: graphical (5) Compilers: N/A Packages: 1893 Shell: Bash v: 5.2.15 inxi: 3.3.31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043527/+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 2043527] [NEW] STONEY not supported in kfd
You have been subscribed to a public bug: I'm running lubuntu 23.10 (Mantic Minotaur) on an HP Chromebook 11A G8 EE, board name 'BARLA', using the current MrChromebox BIOS. The thing takes ages (+3 min.) to cold boot and play any video. (Plus there's no sound from the internal speakers, which I knew about, separate issue, just noting that here for posterity. I pair with a Bluetooth headset that works fine.) On boot, before the splash screen, I see in this order, a soft lockup error, the error in the title of this post, and errors about the audio. >From journalctl: Nov 14 09:33:01 uname-barla kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [(udev-worker):115] Nov 14 09:33:01 uname-barla kernel: [drm] initializing kernel modesetting (STONEY 0x1002:0x98E4 0x1002:0x1EB0 0xEB). Nov 14 09:33:01 uname-barla kernel: kfd kfd: amdgpu: STONEY not supported in kfd >From inxi: System: Kernel: 6.5.0-10-generic arch: x86_64 bits: 64 compiler: N/A Desktop: LXQt v: 1.3.0 Distro: Ubuntu 23.10 (Mantic Minotaur) Machine: Type: Laptop System: Google product: Barla v: rev7 serial: Mobo: Google model: Barla v: rev7 serial: UEFI: coreboot v: MrChromebox-4.21.1 date: 10/29/2023 Battery: ID-1: BAT0 charge: 19.4 Wh (41.9%) condition: 46.3/47.4 Wh (97.7%) volts: 7.5 min: 7.7 model: 333-1D- GH02047 status: discharging CPU: Info: dual core model: AMD A4-9120C RADEON R4 5 COMPUTE CORES 2C+3G bits: 64 type: MCP arch: Excavator rev: 0 cache: L1: 192 KiB L2: 2 MiB Speed (MHz): avg: 1200 min/max: 1200/1600 boost: enabled cores: 1: 1200 2: 1200 bogomips: 6387 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] driver: amdgpu v: kernel arch: GCN-3 bus-ID: 00:01.0 Device-2: Quanta HP TrueVision HD Camera driver: uvcvideo type: USB bus-ID: 1-1.1:3 Display: x11 server: X.Org v: 1.21.1.9 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1366x768~60Hz API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: active: gbm,x11,surfaceless,device inactive: wayland API: OpenGL v: 4.5 vendor: amd mesa v: 23.2.1-1ubuntu3 glx-v: 1.4 direct-render: yes renderer: AMD Radeon R3 Graphics (stoney LLVM 15.0.7 DRM 3.54 6.5.0-10-generic) Audio: Device-1: AMD driver: snd_hda_intel v: kernel bus-ID: 00:01.1 API: ALSA v: k6.5.0-10-generic status: kernel-api Server-1: PipeWire v: 0.3.84 status: active Network: Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard driver: rtw_8822ce v: N/A port: 1000 bus-ID: 01:00.0 IF: wlp1s0 state: up mac: Bluetooth: Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB bus-ID: 1-1.2:4 Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 5.1 lmp-v: 10 Drives: Local Storage: total: 29.12 GiB used: 9.01 GiB (30.9%) ID-1: /dev/mmcblk1 vendor: Hynix model: hB8aP size: 29.12 GiB Partition: ID-1: / size: 28.2 GiB used: 9 GiB (31.9%) fs: ext4 dev: /dev/mmcblk1p2 ID-2: /boot/efi size: 299.4 MiB used: 7.7 MiB (2.6%) fs: vfat dev: /dev/mmcblk1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 29.8 C mobo: N/A gpu: amdgpu temp: 29.0 C Fan Speeds (rpm): N/A Info: Processes: 175 Uptime: 6h 35m Memory: total: 4 GiB note: est. available: 3.54 GiB used: 881.3 MiB (24.3%) Init: systemd target: graphical (5) Compilers: N/A Packages: 1893 Shell: Bash v: 5.2.15 inxi: 3.3.31 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- STONEY not supported in kfd https://bugs.launchpad.net/bugs/2043527 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1559794] Re: does not work my wireless card. does not connect any network
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: broadcom-sta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/1559794 Title: does not work my wireless card. does not connect any network Status in broadcom-sta package in Ubuntu: Confirmed Bug description: Broadcom wireless card does not work. Does not connect any wifi network ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: broadcom-sta-source (not installed) ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 20 19:32:51 2016 InstallationDate: Installed on 2014-08-23 (575 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: broadcom-sta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1559794/+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 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
** Description changed: - Issue: mq-posix interface does not work. It results in permission denied - even all interfaces are connected. + [ Impact ] - which ubuntu: UbuntuCore22 (kernel for Jammy) + mq-posix snapd interface does not work on Ubuntu Core 22. It results in + permission denied even all interfaces are connected. - Detail; Our brandstore customer is using posix message queue for IPC - between snaps. They added mq-posix interface and connected them properly - but getting permission denied error. + Our brandstore customer is using posix message queue for IPC between + snaps. They added mq-posix interface and connected them properly but + getting permission denied error. - Our guess:The AppArmor patch for posix message queue created for other - customer did not land in jammy kernel. + The AppArmor patch for posix message queue created for other customer + did not land in the standard jammy kernel. - Request: please apply patch for mq-posix interface to jammy kernel + Userspace support for AppArmor message queue handling is already present + in Ubuntu Core 22, it is just missing from the kernel. + + [ Test Plan ] + + * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. + * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client + + [ Where problems could occur ] + + * The patches already exist for 5.15 and have been used on other + private customer kernels and all kernels released after 22.04, so there + is already a good track record for this patchset and it shouldn't create + any issues. + + [ Other Info ] + + * This is a time-sensitive issue for a paying customer -- 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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
I'm also getting these testing on 6.5.0-10-generic and here the issue is
triggered by enabling the docker service.
--
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/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
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.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2044718] Re: mantic on raspberry5: x and/or lightdm problems
** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in linux-raspi package in Ubuntu: Invalid Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2044718/+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 2044192] Re: Patches needed for AmpereOne (arm64)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
--
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/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-gcp source package in Jammy:
Fix Committed
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 GCP and Focal 5.4 GCP for now
* Also submitting to Jammy 5.15 generic
* Cherry-picks from upstream
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested on GCP AmpereOne instance
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044192/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
** Changed in: linux (Ubuntu Mantic)
Importance: High => Medium
** Changed in: linux (Ubuntu Noble)
Importance: High => Medium
--
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/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
In Progress
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in firmware-sof source package in Mantic:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
> Applied to kvm-x86 svm, with a comment as suggested by Maxim. > [1/2] Revert "nSVM: Check for reserved encodings of TLB_CONTROL in nested > VMCB" > https://github.com/kvm-x86/linux/commit/a484755ab252 -- 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/2008583 Title: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB. Status in linux package in Ubuntu: Confirmed Bug description: My setup: Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x Hypervisor: KVM Windows VM with VMware Workstation 16 Running nested VMs in VMware works ok. It fails if Linux host kernel is updated to 5.19 (22.04.2) with MONITOR PANIC: Invalid VMCB. VMware Workstation unrecoverable error: (vcpu-0) vcpu-0:Invalid VMCB. If I update to Workstation 17 it fails with 2023-02-24T15:21:35.112Z In(05) vmx The following features are required for SVM support in VMware Workstation; however, these features are not available on this host: 2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID. This host supports AMD-V, but the AMD-V implementation is incompatible with VMware Workstation. VMware Workstation does not support the user level monitor on this host. Module 'MonitorMode' power on failed. The same VM works ok on 5.19 kernel on my Intel PC. So it has to do with updated Linux kernel and AMD virtualization and VMware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+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 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
zfs-linux 2.2.2 released tonight... In the changelog: dnode_is_dirty: check dnode and its data for dirtiness #15571 #15526 Which is the above patch for CVE 2023-49298 -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+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 2045382] Re: AMD Lexa PRO graphic card can't work
** Description changed: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work normally by using the onboard graphic card. After checking, AMD graphic card is broken after upgrading to 5.15.0-89-generic, it still have same issue in "5.15.0-91-generic" kernel version, but everything is good in the "5.15.0-88-generic" kernel version. [Information] - ProblemType: Bug - Problematic DUT CID: 202101-28622 Platform name: Caribou Launchpad Tag: fossa-cubone-rkl Project name: Optiplex 5090 - Architecture: amd64 Used GM image: dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso DistroRelease: Ubuntu 20.04.6 LTS kernel version: 5.15.0-91-generic GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 1 14:39:55 2023 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work normally by using the onboard graphic card. After checking, AMD graphic card is broken after upgrading to 5.15.0-89-generic, it still have same issue in "5.15.0-91-generic" kernel version, but everything is good in the "5.15.0-88-generic" kernel version. [Information] Problematic DUT CID: 202101-28622 Platform name: Caribou Launchpad Tag: fossa-cubone-rkl Project name: Optiplex 5090 - Used GM image: dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso - DistroRelease: Ubuntu 20.04.6 LTS - kernel version: 5.15.0-91-generic GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 1 14:39:55 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2045382 Title: AMD Lexa PRO graphic card can't work Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work
[Kernel-packages] [Bug 2045384] [NEW] AppArmor patch for mq-posix interface is missing in jammy
Public bug reported: Issue: mq-posix interface does not work. It results in permission denied even all interfaces are connected. which ubuntu: UbuntuCore22 (kernel for Jammy) Detail; Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. Our guess:The AppArmor patch for posix message queue created for other customer did not land in jammy kernel. Request: please apply patch for mq-posix interface to jammy kernel ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/2045384/+attachment/5725568/+files/version.log -- 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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: New Bug description: Issue: mq-posix interface does not work. It results in permission denied even all interfaces are connected. which ubuntu: UbuntuCore22 (kernel for Jammy) Detail; Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. Our guess:The AppArmor patch for posix message queue created for other customer did not land in jammy kernel. Request: please apply patch for mq-posix interface to jammy kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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
