Re: [Kernel-packages] [Bug 1969231] Re: Touch pad not working
Hi, Thanks, It is working now. Not new problem started. Left speaker stopped working! Thanks. Bhaskara On Wed, 20 Apr, 2022, 06:01 Seth Arnold, <1969...@bugs.launchpad.net> wrote: > Thanks for taking the time to report this bug and helping to make Ubuntu > better. We appreciate the difficulties you are facing, but this appears > to be a "regular" (non-security) bug. I have unmarked it as a security > issue since this bug does not show evidence of allowing attackers to > cross privilege boundaries nor directly cause loss of data/privacy. > Please feel free to report any other bugs you may find. > > ** Information type changed from Private Security to Public > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1969231 > > Title: > Touch pad not working > > Status in linux-signed-hwe-5.13 package in Ubuntu: > New > > Bug description: > Touch pad not working after installing Ubuntu 20.04 > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 > ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 > Uname: Linux 5.13.0-39-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.23 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 15 19:52:29 2022 > InstallationDate: Installed on 2022-03-18 (27 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > SourcePackage: linux-signed-hwe-5.13 > 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-5.13/+bug/1969231/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1969231 Title: Touch pad not working Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Touch pad not working after installing Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 19:52:29 2022 InstallationDate: Installed on 2022-03-18 (27 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 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-5.13/+bug/1969231/+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 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
@~reshmi-susheela-aravind - will you be able to look into this? -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1969633] Re: Continuous Bluetooth timeouts [Broadcom BCM20702A]
So how do I get Canonical to fix the kernel bug? How do I notify them of the bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Continuous Bluetooth timeouts [Broadcom BCM20702A] Status in linux-hwe-5.13 package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1969633/+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 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: In Progress Bug description: See https://lists.ubuntu.com/archives/kernel- team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
verify #21, the result is good. The kernel log for reference.
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274/+attachment/5581937/+files/kernel.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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Yeah a kernel fix is more useful because you won't get Night Light or
colour profile support without a kernel fix.
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Thanks Timo, this series of patches seems fix this issue
https://www.spinics.net/lists/intel-gfx/msg284609.html
Here is the test kernel, I can't reproduce the issue with this kernel.
https://people.canonical.com/~acelan/bugs/lp1967274/
I'll submit SRU soon.
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
There may be no need if 42.1 is tagged in the next week or so. It's
scheduled for 23 April (roughly):
https://wiki.gnome.org/FortyTwo
I imagine we will SRU 42.1 quickly. Also I don't have any sponsorship
powers myself.
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
@vanvugt
Hello,
Will you help to SRU it for jammy?
Thanks,
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1968892] Re: Micmute LED support for Zbook Fury 16 G9
Enable -proposed channel on Zbook Fury 16 G9 and install linux- oem-5.14/5.14.0-1034.37, micmute/audio mute leds work fine. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968892 Title: Micmute LED support for Zbook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The audio mute key(F5) LED does not work. [Fix] Need this commit from v5.18-rc1 ce18f905a500 ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 [Test] Verified on the target machine. [Where problems could occur] The modified hda_fixups, ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED, has the same contain as ALC245_FIXUP_CS35L41_SPI_2, but with new mic mute led gpio settings. So, if might affect the machines with the same chip ID that mic mute led is already working. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968892/+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 1969633] Re: Bluetooth not connecting
Thanks for the bug report. Your kernel log seems to show Bluetooth commands repeatedly failing to transmit: [337184.522407] Bluetooth: hci0: command 0x0406 tx timeout [337887.553831] Bluetooth: hci0: command 0x0c1a tx timeout [337889.565670] Bluetooth: hci0: command 0x0c3a tx timeout [337891.581728] Bluetooth: hci0: command 0x0c1a tx timeout [337913.213192] Bluetooth: hci0: command 0x1405 tx timeout [337915.229228] Bluetooth: hci0: command 0x1403 tx timeout So that's either a kernel bug or a hardware fault. BlueZ is not really relevant here. ** Summary changed: - Bluetooth not connecting + Continuous Bluetooth timeouts [Broadcom BCM20702A] ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Continuous Bluetooth timeouts [Broadcom BCM20702A] Status in linux-hwe-5.13 package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1969633/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
Enable -proposed channel and install linux-firmware (1.187.30). The DUT load the correct tplg file and audio works fine. [kernel] [5.375961] sof-audio-pci-intel-tgl :00:1f.3: SoundWire machine driver sof_sdw topology sof-adl-rt711-l2-rt1316-l01.tplg [5.375962] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4 [5.375970] sof-audio-pci-intel-tgl :00:1f.3: loading firmware [5.384434] sof-audio-pci-intel-tgl :00:1f.3: request_firmware intel/sof/sof-adl.ri successful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic 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-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in firmware-sof source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
** Tags added: rls-jj-incoming -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+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 1948626] Re: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
I have provided a test kernel https://people.canonical.com/~mreed/lp_1948626_nvme_tcp/ ** Summary changed: - Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 + [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 ** Description changed: + [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas + + [Fix] + 1. Update kernel with TP8010 kernel patches: + + a. + https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 + + b. + https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 + + [Test Case] + + + [Other Info] + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches ** Description changed: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 + c. + nvme: add CNTRLTYPE definitions for 'identify controller + https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] - [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify
[Kernel-packages] [Bug 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Sujith, Can you provide a test case that will test these patches? ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1948626] Re: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
An additional patch was needed to fix the build of the two patches. commit e15a8a9755659ff5972f30de4dd64867c97f242d Author: Hannes Reinecke Date: Wed Sep 22 08:35:20 2021 +0200 nvme: add CNTRLTYPE definitions for 'identify controller' Update the 'identify controller' structure to define the newly added CNTRLTYPE field. Signed-off-by: Hannes Reinecke Reviewed-by: Chaitanya Kulkarni Reviewed-by: Himanshu Madhani Signed-off-by: Christoph Hellwig -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1969614] Re: package linux-image-5.13.0-40-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.13.0-40-generic.dpkg-new': Operation not permitted
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1969614 Title: package linux-image-5.13.0-40-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.13.0-40-generic.dpkg- new': Operation not permitted Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: fixing bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-40-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 20 16:40:50 2022 DuplicateSignature: package:linux-image-5.13.0-40-generic:(not installed) Unpacking linux-image-5.13.0-40-generic (5.13.0-40.45~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-JLEEPz/3-linux-image-5.13.0-40-generic_5.13.0-40.45~20.04.1_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.13.0-40-generic.dpkg-new': Operation not permitted ErrorMessage: unable to open '/boot/vmlinuz-5.13.0-40-generic.dpkg-new': Operation not permitted InstallationDate: Installed on 2022-02-03 (75 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.13 Title: package linux-image-5.13.0-40-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.13.0-40-generic.dpkg-new': Operation not permitted 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-5.13/+bug/1969614/+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 1969689] [NEW] USB devices not detected on CM4
Public bug reported: USB devices are not working on the CM4. When running `lsusb` the hub is detected, but devices are not. ``` ubuntu@ubuntu:~$ sudo dmesg | egrep -i "dwc2|usb" [0.151915] usbcore: registered new interface driver usbfs [0.151976] usbcore: registered new interface driver hub [0.152047] usbcore: registered new device driver usb [1.125855] usbcore: registered new interface driver lan78xx [1.125926] usbcore: registered new interface driver smsc95xx [1.125965] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.126070] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.126318] uhci_hcd: USB Universal Host Controller Interface driver [1.765785] usb_phy_generic phy: supply vcc not found, using dummy regulator [1.864470] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.864674] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.916752] dwc2 fe98.usb: DWC OTG Controller [1.916788] dwc2 fe98.usb: new USB bus registered, assigned bus number 1 [1.916822] dwc2 fe98.usb: irq 36, io mem 0xfe98 [1.917028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [1.917040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.917048] usb usb1: Product: DWC OTG Controller [1.917055] usb usb1: Manufacturer: Linux 5.15.0-1005-raspi dwc2_hsotg [1.917062] usb usb1: SerialNumber: fe98.usb [1.917627] hub 1-0:1.0: USB hub found [7.831293] usbcore: registered new interface driver brcmfmac ``` @waveform was able to confirm the issue. The line `dtoverlay=dwc2,dr_mode=host` is present in config.txt. We suspect this to be a dtb/kernel issue. This is happening on both armhf and arm64. ** Affects: linux-raspi (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/1969689 Title: USB devices not detected on CM4 Status in linux-raspi package in Ubuntu: New Bug description: USB devices are not working on the CM4. When running `lsusb` the hub is detected, but devices are not. ``` ubuntu@ubuntu:~$ sudo dmesg | egrep -i "dwc2|usb" [0.151915] usbcore: registered new interface driver usbfs [0.151976] usbcore: registered new interface driver hub [0.152047] usbcore: registered new device driver usb [1.125855] usbcore: registered new interface driver lan78xx [1.125926] usbcore: registered new interface driver smsc95xx [1.125965] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.126070] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.126318] uhci_hcd: USB Universal Host Controller Interface driver [1.765785] usb_phy_generic phy: supply vcc not found, using dummy regulator [1.864470] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.864674] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.916752] dwc2 fe98.usb: DWC OTG Controller [1.916788] dwc2 fe98.usb: new USB bus registered, assigned bus number 1 [1.916822] dwc2 fe98.usb: irq 36, io mem 0xfe98 [1.917028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [1.917040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.917048] usb usb1: Product: DWC OTG Controller [1.917055] usb usb1: Manufacturer: Linux 5.15.0-1005-raspi dwc2_hsotg [1.917062] usb usb1: SerialNumber: fe98.usb [1.917627] hub 1-0:1.0: USB hub found [7.831293] usbcore: registered new interface driver brcmfmac ``` @waveform was able to confirm the issue. The line `dtoverlay=dwc2,dr_mode=host` is present in config.txt. We suspect this to be a dtb/kernel issue. This is happening on both armhf and arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1969689/+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 1969678] [NEW] Focal update: v5.4.186 upstream stable release
Public bug reported: 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.186 upstream stable release from git://git.kernel.org/ Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" sctp: fix the processing for INIT chunk xfrm: Check if_id in xfrm_migrate xfrm: Fix xfrm migrate issues when address family changes arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity arm64: dts: rockchip: reorder rk3399 hdmi clocks arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" ARM: dts: rockchip: reorder rk322x hmdi clocks ARM: dts: rockchip: fix a typo on rk3288 crypto-controller mac80211: refuse aggregations sessions before authorized MIPS: smp: fill in sibling and core maps earlier ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready atm: firestream: check the return value of ioremap() in fs_init() iwlwifi: don't advertise TWT support drm/vrr: Set VRR capable prop only if it is attached to connector nl80211: Update bss channel on channel switch for P2P_CLIENT tcp: make tcp_read_sock() more robust sfc: extend the locking on mcdi->seqno kselftest/vm: fix tests build with old libc fixup for "arm64 entry: Add macro for reading symbol address from the trampoline" Linux 5.4.186 UBUNTU: upstream stable to v5.4.186 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - 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.186 upstream stable release + from git://git.kernel.org/ -v5.4.186 upstream stable release -from git://git.kernel.org/ + Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" + sctp: fix the processing for INIT chunk + xfrm: Check if_id in xfrm_migrate + xfrm: Fix xfrm migrate issues when address family changes + arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity + arm64: dts: rockchip: reorder rk3399 hdmi clocks + arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" + ARM: dts: rockchip: reorder rk322x hmdi clocks + ARM: dts: rockchip: fix a typo on rk3288 crypto-controller + mac80211: refuse aggregations sessions before authorized + MIPS: smp: fill in sibling and core maps earlier + ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE + can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready + atm: firestream: check the return value of ioremap() in fs_init() + iwlwifi: don't advertise TWT support + drm/vrr: Set VRR capable prop only if it is attached to connector + nl80211: Update bss channel on channel switch for P2P_CLIENT + tcp: make tcp_read_sock() more robust + sfc: extend the locking on mcdi->seqno + kselftest/vm: fix tests build with old libc + fixup for "arm64 entry: Add macro for reading symbol address from the trampoline" + Linux 5.4.186 + UBUNTU: upstream stable to v5.4.186 -- You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 1969672] [NEW] Focal update: v5.4.185 upstream stable release
Public bug reported: 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.185 upstream stable release from git://git.kernel.org/ clk: qcom: gdsc: Add support to update GDSC transition delay arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero net: qlogic: check the return value of dma_alloc_coherent() in qed_vf_hw_prepare() qed: return status of qed_iov_get_link drm/sun4i: mixer: Fix P010 and P210 format numbers ARM: dts: aspeed: Fix AST2600 quad spi group ethernet: Fix error handling in xemaclite_of_probe net: ethernet: ti: cpts: Handle error for clk_enable net: ethernet: lpc_eth: Handle error for clk_enable ax25: Fix NULL pointer dereference in ax25_kill_by_device net/mlx5: Fix size field in bufferx_reg struct net/mlx5: Fix a race on command flush flow NFC: port100: fix use-after-free in port100_send_complete selftests: pmtu.sh: Kill tcpdump processes launched by subshell. gpio: ts4900: Do not set DAT and OE together gianfar: ethtool: Fix refcount leak in gfar_get_ts_info net: phy: DP83822: clear MISR2 register to disable interrupts sctp: fix kernel-infoleak for SCTP sockets net: bcmgenet: Don't claim WOL when its not available net-sysfs: add check for netdevice being present to speed_show Revert "xen-netback: remove 'hotplug-status' once it has served its purpose" Revert "xen-netback: Check for hotplug-status existence before watching" ipv6: prevent a possible race condition with lifetimes tracing: Ensure trace buffer is at least 4096 bytes large selftest/vm: fix map_fixed_noreplace test failure selftests/memfd: clean up mapping in mfd_fail_write ARM: Spectre-BHB: provide empty stub for non-config fuse: fix pipe buffer lifetime for direct_io staging: gdm724x: fix use after free in gdm_lte_rx() net: macb: Fix lost RX packet wakeup race in NAPI receive mmc: meson: Fix usage of meson_mmc_post_req() riscv: Fix auipc+jalr relocation range checks arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0 virtio: unexport virtio_finalize_features virtio: acknowledge all features before access ARM: fix Thumb2 regression with Spectre BHB ext4: add check to prevent attempting to resize an fs with sparse_super2 x86/cpufeatures: Mark two free bits in word 3 x86/cpu: Add hardware-enforced cache coherency as a CPUID feature x86/mm/pat: Don't flush cache if hardware enforces cache coherency across encryption domnains KVM: SVM: Don't flush cache if hardware enforces cache coherency across encryption domains Linux 5.4.185 UBUNTU: upstream stable to v5.4.185 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - 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.185 upstream stable release + from git://git.kernel.org/ -v5.4.185 upstream stable release -from git://git.kernel.org/ + clk: qcom: gdsc: Add support to update GDSC transition delay + arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias +
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
Looks like the missing bits were re-added in Bionic HWE kernel version
5.4.0-108.122~18.04.1. This allowed confirming with the recently
released -109 version:
root@bionic-vm:~# lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
root@bionic-vm:~# uname -a
Linux bionic-vm 5.4.0-109-generic #123~18.04.1-Ubuntu SMP Fri Apr 8 09:48:52
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@bionic-vm:~# modprobe virtio_gpu
root@bionic-vm:~# grep -E '(virtio-gpu|vmwgfx)\.ko'
/var/lib/dpkg/info/linux-modules-5.4.0-109-generic.list
/lib/modules/5.4.0-109-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
/lib/modules/5.4.0-109-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
As such, marking it as verified for Bionic too now.
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
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/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port
[Kernel-packages] [Bug 1969666] [NEW] Impish update: upstream stable patchset 2022-04-20
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-04-20 Ported from the following upstream stable releases: v5.10.104, v5.15.27 from git://git.kernel.org/ mac80211_hwsim: report NOACK frames in tx_status mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work i2c: bcm2835: Avoid clock stretching timeouts ASoC: rt5668: do not block workqueue if card is unbound ASoC: rt5682: do not block workqueue if card is unbound regulator: core: fix false positive in regulator_late_cleanup() KVM: arm64: vgic: Read HW interrupt pending state from the HW tipc: fix a bit overflow in tipc_crypto_key_rcv() cifs: fix double free race when mount fails in cifs_get_root() selftests/seccomp: Fix seccomp failure by adding missing headers i2c: cadence: allow COMPILE_TEST i2c: qup: allow COMPILE_TEST net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 usb: gadget: don't release an existing dev->buf usb: gadget: clear related members when goto fail exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() exfat: fix i_blocks for files truncated over 4 GiB tracing: Add test for user space strings when filtering on string pointers serial: stm32: prevent TDR register overwrite when sending x_char ata: pata_hpt37x: fix PCI clock detection drm/amdgpu: check vm ready by amdgpu_vm->evicting flag tracing: Add ustring operation to filtering string pointers ALSA: intel_hdmi: Fix reference to PCM buffer address riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP riscv: Fix config KASAN && DEBUG_VIRTUAL ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min iommu/amd: Recover from event log overflow drm/i915: s/JSP2/ICP2/ PCH xen/netfront: destroy queues before real_num_tx_queues is zeroed thermal: core: Fix TZ_GET_TRIP NULL pointer dereference ntb: intel: fix port config status offset for SPR mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls xfrm: fix MTU regression netfilter: fix use-after-free in __nf_register_net_hook() bpf, sockmap: Do not ignore orig_len parameter xfrm: enforce validity of offload input flags e1000e: Correct NVM checksum verification flow net: fix up skbs delta_truesize in UDP GRO frag_list netfilter: nf_queue: don't assume sk is full socket netfilter: nf_queue: fix possible use-after-free netfilter: nf_queue: handle socket prefetch batman-adv: Request iflink once in batadv-on-batadv check batman-adv: Request iflink once in batadv_get_real_netdevice batman-adv: Don't expect inter-netns unique iflink indices net: ipv6: ensure we call ipv6_mc_down() at most once net: dcb: flush lingering app table entries for unregistered devices net/smc: fix connection leak net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server mac80211: fix forwarded mesh frames AC & queue selection net: stmmac: fix return value of __setup handler mac80211: treat some SAE auth steps as final iavf: Fix missing check for running netdev net: sxgbe: fix return value of __setup handler ibmvnic: register netdev after init of adapter net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc() efivars: Respect "block" flag in efivar_entry_set_safe() firmware: arm_scmi: Remove space in MODULE_ALIAS name ASoC: cs4265: Fix the duplicated control name can: gs_usb: change active_channels's type from atomic_t to u8 arm64: dts: rockchip: Switch RK3399-Gru DP to SPDIF output igc: igc_read_phy_reg_gpy: drop premature return ARM: Fix kgdb breakpoint for Thumb2 ARM: 9182/1: mmu: fix returns from early_param() and __setup() functions selftests: mlxsw: tc_police_scale: Make test more robust pinctrl: sunxi: Use unique lockdep classes for IRQs igc: igc_write_phy_reg_gpy: drop premature return ibmvnic: free reset-work-item when flushing memfd: fix F_SEAL_WRITE after shmem huge page allocated s390/extable: fix exception table sorting ARM: dts: switch timer config to common devkit8000 devicetree ARM: dts: Use 32KiHz oscillator on devkit8000 soc: fsl: guts: Revert commit 3c0d64e867ed soc: fsl: guts: Add a missing memory allocation failure check soc: fsl: qe: Check of ioremap return value ARM: tegra: Move panels to AUX bus ibmvnic: complete init_done on transport events net: chelsio: cxgb3: check the return value of pci_find_capability() iavf: Refactor iavf state machine tracking nl80211: Handle nla_memdup failures in
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
any plans to address this in jammy? haven't had any movement on the upstream bug so I assume reverting that one commit is probably the best option? -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+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 1966066] Re: audio from external sound card is distorted
I can report that 5.13.0-41-generic #46-Ubuntu SMP Thu Apr 14 20:06:04 UTC 2022
- fixes regular popping with a "KORG, Inc. ToneLabST" (lsusb, product name is
Vox ToneLab ST) at a tempo of around 80-90 bpm
- Focusrite-Novation Scarlett 2i4 still working (never was an issue)
- 2nd display connected through HDMI still working.
Great! Thanks a lot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
This bug was fixed in the package backport-iwlwifi-dkms - 9858-0ubuntu3 --- backport-iwlwifi-dkms (9858-0ubuntu3) jammy; urgency=medium * Fix FTBFS dkms module during kernel builds with a non-default kernelsourcedir location by respecting kernelsourcedir in dkms.conf (LP: #1969434) -- You-Sheng Yang Tue, 19 Apr 2022 17:20:09 +0800 ** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. == backport-iwlwifi-dkms SRU == In order to be compiled with dkms-build in kernel source package, the kernel header dir will not be /lib/modules//build but a temporary directory. This change specifies KLIB_BUILD
[Kernel-packages] [Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
I've picked up the PR into a bileto ppa https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4831 it seems to work for me correctly. If one has MOK dkms key enrolled or secureboot disabled, one can use zfs-dkms package from the above ppa as a solution. Please test it and let me know. I will try to SRU that, but it may take a kernel sru cycle to fully land. -- 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/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1968591] Re: xfrm interface cannot be changed anymore
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+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 1968591] Re: xfrm interface cannot be changed anymore
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+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 1968591] Re: xfrm interface cannot be changed anymore
** Description changed: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo - root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 + root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. -- 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/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+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 1969633] [NEW] Bluetooth not connecting
Public bug reported: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Bluetooth not connecting Status in bluez package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1035.36)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1035.36) for focal have finished running. The following regressions have been reported in tests triggered by the package: gost-crypto/unknown (arm64) dm-writeboost/unknown (arm64) jool/unknown (arm64) ddcci-driver-linux/unknown (arm64) zfs-linux/unknown (arm64) lxc/unknown (arm64) openafs/unknown (arm64) lime-forensics/unknown (arm64) iptables-netflow/unknown (arm64) glibc/unknown (arm64) bbswitch/unknown (arm64) openrazer/unknown (arm64) xtables-addons/unknown (arm64) lttng-modules/unknown (arm64) snapd/unknown (arm64) acpi-call/unknown (arm64) wireguard-linux-compat/unknown (arm64) west-chamber/unknown (arm64) fwts/unknown (arm64) adv-17v35x/unknown (arm64) linux-bluefield/unknown (arm64) r8168/unknown (arm64) langford/unknown (arm64) nat-rtsp/unknown (arm64) mali-midgard/unknown (arm64) dpdk/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 packing 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 1969624] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969624 Title: kernel NULL pointer dereference while removing floppy module Status in linux package in Ubuntu: Confirmed Bug description: Kernel/Package is linux-image-5.15.0-25-generic running: $ modprobe -r floppy Killed ends in BUG: kernel NULL pointer dereference (see dmesg). 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 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 20 13:33 seq crw-rw 1 root audio 116, 33 Apr 20 13:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Apr 20 13:50:56 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=/dev/mapper/system-root ro console=ttyS0,38400n8 elevator=noop net.ifnames=0 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: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969624/+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 1969624] [NEW] kernel NULL pointer dereference while removing floppy module
Public bug reported: Kernel/Package is linux-image-5.15.0-25-generic running: $ modprobe -r floppy Killed ends in BUG: kernel NULL pointer dereference (see dmesg). 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 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 20 13:33 seq crw-rw 1 root audio 116, 33 Apr 20 13:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Apr 20 13:50:56 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=/dev/mapper/system-root ro console=ttyS0,38400n8 elevator=noop net.ifnames=0 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: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- 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/1969624 Title: kernel NULL pointer dereference while removing floppy module Status in linux package in Ubuntu: Confirmed Bug description: Kernel/Package is linux-image-5.15.0-25-generic running: $ modprobe -r floppy Killed ends in BUG: kernel NULL pointer dereference (see dmesg). 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 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 20 13:33 seq crw-rw 1 root audio 116, 33 Apr 20 13:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Apr 20 13:50:56 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=/dev/mapper/system-root ro console=ttyS0,38400n8 elevator=noop net.ifnames=0 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: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1917471
Title:
[SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
causes Bus Fatal Error when rebooting system with BCM5720 NIC
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their
logs and thus it is generating an unusualy high volume of support
calls from the field.
In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
Upstream, these errors were discovered and that patch was reverted
(see Fix Below). We carry the revert commit in all subsequent Focal
HWE kernels starting at 5.12, but the fix was never pulled back into
Focal 5.4.
according to the hardware partner:
the following error messages are observed when rebooting a machine
that uses the BCM5720 chipset, which is a widely used 1GbE controller
found on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
[FIX]
The fix is to apply this patch from upstream:
commit 9d3fcb28f9b9750b474811a2964ce022df56336e
Author: Josef Bacik
Date: Tue Mar 16 22:17:48 2021 -0400
Revert "PM: ACPI: reboot: Use S5 for reboot"
This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
This patch causes a panic when rebooting my Dell Poweredge r440. I do
not have the full panic log as it's lost at that stage of the reboot and
I do not have a serial console. Reverting this patch makes my system
able to reboot again.
Example:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471
The hardware partner has preemptively pulled our 5.4 tree, applied the
fix and tested it in their labs and determined that this does resolve
the issue.
[TEST CASE]
Install the patched kernel on a machine that uses a BCM5720 LOM and reboot
the machine and see that the errors no longer appear.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1969457] Re: /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links
It looks as if someone has filed a similar bug for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997980 ** Bug watch added: Debian Bug tracker #997980 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997980 -- 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/1969457 Title: /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links Status in zfs-linux package in Ubuntu: New Bug description: Fresh installation of 20.04.4 with installer created zfs native encrypted root zfsutils-linux: 0.8.3-1ubuntu12.13 On reboot, zvol /dev/zvol entries are not being created. This seems to effect different zvols each reboot. Example logs: ``` -- A start job for unit zsys-gc.service has finished successfully. -- -- The job identifier is 3139. Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:51 monolith zvol_wait[74805]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:52 monolith zvol_wait[74823]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:53 monolith zvol_wait[74932]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:54 monolith zvol_wait[74950]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:55 monolith zvol_wait[74969]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:56 monolith zvol_wait[74987]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:57 monolith zvol_wait[75006]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:58 monolith zvol_wait[4440]: Still waiting on 1 zvol links ... Apr 19 06:43:58 monolith zvol_wait[4440]: No progress since last loop. Apr 19 06:43:58 monolith zvol_wait[4440]: Checking if any zvols were deleted. Apr 19 06:43:58 monolith zvol_wait[4440]: Remaining zvols: Apr 19 06:43:58 monolith zvol_wait[4440]: rpool/libvirt_zvols/kube-04-disk0 Apr 19 06:43:58 monolith zvol_wait[4440]: Timed out waiting on zvol links Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit zfs-volume-wait.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit zfs-volume-wait.service has entered the 'failed' state with result 'exit-code'. Apr 19 06:43:58 monolith systemd[1]: Failed to start Wait for ZFS Volume (zvol) links in /dev. -- Subject: A start job for unit zfs-volume-wait.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-volume-wait.service has finished with a failure. -- -- The job identifier is 226 and the job result is failed. Apr 19 06:43:58 monolith systemd[1]: Dependency failed for ZFS volumes are ready. -- Subject: A start job for unit zfs-volumes.target has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-volumes.target has finished with a failure. ``` I believe this is related to changes made here: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457/+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 1967988] Re: Support different Cirrus audio codec configurations on Dell laptops
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967988 Title: Support different Cirrus audio codec configurations on Dell laptops Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On Dell's platform, Warlock/Bullseye Laptops have a mono DMIC, Cyborg and some Warlock variants uses a stereo DMIC. They are not correctly mapped to the corresponding configurations so the microphone function are not working as expected. [Fix] Cirrus upstream new FIXUPs to support different microphone configurations on different Dell laptop variants. [Test Case] 1. Go to Audio Settings 2. Make sure the microphone is correctly detected and responds to audio input. 3. Issue command "arecord record_file" and check the record_file is consistent with audio input. [Where problems could occur] Risk should be Low. The patches come from Cirrus and the configurations are mapped based on the audio codec's SSIDs for different Dell variants. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967988/+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 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
In reply to comment 19
I have tried reproducing the fatal-error issue by using focal proposed kernel
(linux-image-unsigned-5.4.0-110-generic_5.4.0-110.124_amd64.deb) - Issue is no
longer seen.
Attaching serial console logs of the efforts.
** Attachment added: "fatal_error_fix_proposed_kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+attachment/5581813/+files/fatal_error_fix_proposed_kernel.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/1917471
Title:
[SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
causes Bus Fatal Error when rebooting system with BCM5720 NIC
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their
logs and thus it is generating an unusualy high volume of support
calls from the field.
In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
Upstream, these errors were discovered and that patch was reverted
(see Fix Below). We carry the revert commit in all subsequent Focal
HWE kernels starting at 5.12, but the fix was never pulled back into
Focal 5.4.
according to the hardware partner:
the following error messages are observed when rebooting a machine
that uses the BCM5720 chipset, which is a widely used 1GbE controller
found on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
[FIX]
The fix is to apply this patch from upstream:
commit 9d3fcb28f9b9750b474811a2964ce022df56336e
Author: Josef Bacik
Date: Tue Mar 16 22:17:48 2021 -0400
Revert "PM: ACPI: reboot: Use S5 for reboot"
This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
This patch causes a panic when rebooting my Dell Poweredge r440. I do
not have the full panic log as it's lost at that stage of the reboot and
I do not have a serial console. Reverting this patch makes my system
able to reboot again.
Example:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471
The hardware partner
[Kernel-packages] [Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
Bionic 4.15.0-177.186 with node exotic-skunk.amd64 Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.3qPxgV32ap -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.cCbvsNzbhI enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP filter = vmx_ldtr_test, test = int3 filter = vmx_ldtr_test, test = into filter = vmx_ldtr_test, test = exit_monitor_from_l2_test filter = vmx_ldtr_test, test = invalid_msr filter = vmx_ldtr_test, test = v2_null_test filter = vmx_ldtr_test, test = v2_multiple_entries_test filter = vmx_ldtr_test, test = fixture_test_case1 filter = vmx_ldtr_test, test = fixture_test_case2 filter = vmx_ldtr_test, test = invvpid_test filter = vmx_ldtr_test, test = vmx_controls_test filter = vmx_ldtr_test, test = vmx_host_state_area_test filter = vmx_ldtr_test, test = vmx_guest_state_area_test filter = vmx_ldtr_test, test = vmentry_movss_shadow_test filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test filter = vmx_ldtr_test, test = apic_reg_virt_test filter = vmx_ldtr_test, test = virt_x2apic_mode_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test filter = vmx_ldtr_test, test = vmx_init_signal_test filter = vmx_ldtr_test, test = vmx_sipi_signal_test filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test filter = vmx_ldtr_test, test = vmx_ldtr_test Test suite: vmx_ldtr_test PASS: Expected 18 for L2 LDTR selector (got 18) PASS: Expected 0 for L1 LDTR selector (got 0) filter = vmx_ldtr_test, test = vmx_cr_load_test filter = vmx_ldtr_test, test = vmx_cr4_osxsave_test filter = vmx_ldtr_test, test = vmx_nm_test filter = vmx_ldtr_test, test = vmx_db_test filter = vmx_ldtr_test, test = vmx_nmi_window_test filter = vmx_ldtr_test, test = vmx_intr_window_test filter = vmx_ldtr_test, test = vmx_pending_event_test filter = vmx_ldtr_test, test = vmx_pending_event_hlt_test filter = vmx_ldtr_test, test = vmx_store_tsc_test filter = vmx_ldtr_test, test = vmx_preemption_timer_zero_test filter = vmx_ldtr_test, test = vmx_preemption_timer_tf_test filter = vmx_ldtr_test, test = vmx_preemption_timer_expiry_test filter = vmx_ldtr_test, test = ept_access_test_not_present filter = vmx_ldtr_test, test = ept_access_test_read_only filter = vmx_ldtr_test, test = ept_access_test_write_only filter = vmx_ldtr_test, test = ept_access_test_read_write filter = vmx_ldtr_test, test = ept_access_test_execute_only filter = vmx_ldtr_test, test = ept_access_test_read_execute filter = vmx_ldtr_test, test = ept_access_test_write_execute filter = vmx_ldtr_test, test = ept_access_test_read_write_execute filter = vmx_ldtr_test, test = ept_access_test_reserved_bits filter = vmx_ldtr_test, test = ept_access_test_ignored_bits filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_disabled filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_enabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_disabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_enabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_write filter = vmx_ldtr_test, test =
[Kernel-packages] [Bug 1968751] Re: Devlink wasn't enabled from common config
This bug is awaiting verification that the linux-bluefield/5.4.0-1035.38 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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- 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/1968751 Title: Devlink wasn't enabled from common config Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature A pull request was submitted for March SRU at: https://code.launchpad.net/~bodong-wang/ubuntu/+source/linux- bluefield/+git/version-seeds/+merge/416211 However, CONFIG_NET_DEVLINK was mistakenly removed when merging. This breaks all switchdev configurations. * How to test Any devlink command, e.g: # devlink dev eswitch show pci/:03:00.0 * What it could break N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1968751/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Description changed: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. - == original bug report == + == backport-iwlwifi-dkms SRU == + + Fix FTBFS with non-standard build directory layout, as executed by dkms + build with a sourcedir setting, as will be done by the above kernel + built-in dkms packages. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" ** Description changed: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed.
[Kernel-packages] [Bug 1969612] [NEW] 5.13.0-40 extremely slow with Alder Lake CPU
Public bug reported: System running i5-12400F CPU, this is Alder Lake with 6x performance cores (no efficiency cores). Booting with linux-image-5.13.0-40-generic is extremely slow. The system takes over a minute to even log in, usual time is a few seconds. Running anything even remotely taxing (eg: GRUB rebuild, sudo) effectively grinds the system to a halt. I notice CPU scaling never reaches above ~1 Ghz, whereas normal operation on 5.13.0-39 and earlier reaches up to ~4.7 GHz on demand. When 5.13.0-40 is booted, the CPU Frequency Scaling applet in MATE Desktop does not display the powersave/performance governors. sysfs shows the intel_pstate driver in use, running in powersave governor. Booting back into 5.13.0-39 resolves this, the system is fast and responsive again. Nothing jumps out as obvious to me in the changelog: https://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_5.13.0-40.45/changelog (searched "cpu" and "freq" and "alder"). As per https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies I would gladly test the latest upstream mainline build, however it's not possible to install v5.15.7 or later due to unmet libssl3 dependency. $ lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 $ apt-cache policy linux-image-5.13.0-40-generic linux-image-5.13.0-40-generic: Installed: 5.13.0-40.45~20.04.1 Candidate: 5.13.0-40.45~20.04.1 Version table: *** 5.13.0-40.45~20.04.1 500 500 http://au.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 20:41:52 2022 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu-MATE 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1969612 Title: 5.13.0-40 extremely slow with Alder Lake CPU Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: System running i5-12400F CPU, this is Alder Lake with 6x performance cores (no efficiency cores). Booting with linux-image-5.13.0-40-generic is extremely slow. The system takes over a minute to even log in, usual time is a few seconds. Running anything even remotely taxing (eg: GRUB rebuild, sudo) effectively grinds the system to a halt. I notice CPU scaling never reaches above ~1 Ghz, whereas normal operation on 5.13.0-39 and earlier reaches up to ~4.7 GHz on demand. When 5.13.0-40 is booted, the CPU Frequency Scaling applet in MATE Desktop does not display the powersave/performance governors. sysfs shows the intel_pstate driver in use, running in powersave governor. Booting back into 5.13.0-39 resolves this, the system is fast and responsive again. Nothing jumps out as obvious to me in the changelog: https://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_5.13.0-40.45/changelog (searched "cpu" and "freq" and "alder"). As per https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies I would gladly test the latest upstream mainline build, however it's not possible to install v5.15.7 or later due to unmet libssl3 dependency. $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ apt-cache policy linux-image-5.13.0-40-generic linux-image-5.13.0-40-generic: Installed: 5.13.0-40.45~20.04.1 Candidate: 5.13.0-40.45~20.04.1 Version table: *** 5.13.0-40.45~20.04.1 500 500 http://au.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 20:41:52 2022 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu-MATE 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about
[Kernel-packages] [Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
This bug is awaiting verification that the linux/4.15.0-177.186 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956315 Title: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50)) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] vmx_ldtr_test in ubuntu_kvm_unit_tests will fail with: FAIL: Expected 0 for L1 LDTR selector (got 50) It's a test for commit afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" According to Intel 64 and IA-32 Architectures Software Developer’s Manual, L1's LDTR should be 0 after an emulated VM-exit from L2. [Fix] * afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" We already have this patch in Jammy. This patch can be cherry-picked into F/F-OEM-5.14/I. But some straightforward backport work is required for Bionic, as the code snippet for nested KVM haven't been split out to vmx/nested.c (55d2375e KVM: nVMX: Move nested code to dedicated files). [Test] Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1956315-vmx-ldtr/ Tested with: * B (bare-metal / KVM instance) * F (KVM instance) * I (bare-metal / KVM instance) With this patched kernel, this test will pass: PASS: Expected 0 for L1 LDTR selector (got 0) Also tested with ubuntu_kvm_unit_tests and ubuntu_kvm_smoke_test to make sure this is not causing any other regressions. [Where problem could occur] If the patch is incorrect it might affect the nested KVM functionality while existing from L2 to L1. [Original bug description] Issue found on Bionic 4.15.0-166.174 with node rizzo Running 'kvm-ok' INFO: /dev/kvm exists KVM acceleration can be used '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=8a30588c timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Lnfifekq7r -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.i9y5hdMh49 enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP
[Kernel-packages] [Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
This bug is awaiting verification that the linux/4.15.0-177.186 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968016 Title: Use kernel-testing repo from launchpad for ADT tests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux-oem-5.17 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux-oem-5.17 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: In ADT tests, we are still using the kernel-testing repo from kernel.ubuntu.com, it should be migrated to launchpad instead to align with our other testing repos. For autotest-client-tests repo change, it will needs to be handled in the kernel-testing repo directly, see bug 1968257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968016/+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 1968340] Re: ip6gre driver does not hold device reference
This bug is awaiting verification that the linux/4.15.0-177.186 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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: verification-needed-bionic -- 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/1968340 Title: ip6gre driver does not hold device reference Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] When creating ip6gre interfaces in network namespaces, device references are not held, preventing further network namespaces from being created. [Test case] sudo modprobe ip6_gre unshare -Urn true unshare -Urn true The second unshare won't work and there will be "unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1" messages on kernel log. [Potential regression] ip6gre users can observe regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968340/+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 1786013] Autopkgtest regression report (linux-restricted-modules/4.15.0-177.186)
All autopkgtests for the newly accepted linux-restricted-modules (4.15.0-177.186) for bionic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1 (i386) 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/bionic/update_excuses.html#linux-restricted-modules [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 packing 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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
The SRU for oem-5.17 was sent out. ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1942624] Re: NVMe devices fail to probe due to ACPI power state change
It works ! ^_^ :D nice, thanks ! :D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942624 Title: NVMe devices fail to probe due to ACPI power state change Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] * Specific NVMe devices fail to probe and become unusable after boot * Caused by an ACPI regression that doesn't correctly handle power states * Upstream regression commit: 7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally * Regression window for Ubuntu kernels includes 5.13 and 5.14 [Test Plan] * Boot affected kernel and validate whether NVMe device is usable * Check kernel logs for failed probe message: "can't change power state from D3Cold to D0 (config space inaccessible)" [Fix] * Fixed by not turning off power resources in unknown state * Fix was introduced by commit: bc2836859643 ACPI: PM: Do not turn off power resources in unknown state * Kernels starting with 5.15 (e.g. Jammy) not affected, as they already contain the fix above [Regression Potential] * NVMe devices continue failing to probe * Other devices become unusable after power state changes * Further regressions would affect power state of devices, possibly after boot -- [Original Description] NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: Fix Released Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1934878] Re: Mute/mic LEDs no function on some HP platfroms
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934878 Title: Mute/mic LEDs no function on some HP platfroms Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ProBook 630 G8 Notebook PC 2) HP ProBook 445 G8 Notebook PC 3) HP ProBook 450 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934878/+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 1940629] Re: Support Jasper Lake
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940629 Title: Support Jasper Lake Status in OEM Priority Project: Fix Released Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: Fix Released Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+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 1966841] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic 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-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in firmware-sof source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1968902] Re: ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
According to the v2 submission this change has already been made for
Impish.
** Changed in: linux-oracle (Ubuntu Impish)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1968902
Title:
ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
Status in ubuntu-kernel-tests:
New
Status in linux-oracle package in Ubuntu:
In Progress
Status in linux-oracle source package in Focal:
In Progress
Status in linux-oracle source package in Impish:
Invalid
Bug description:
The ARM64_SW_TTBR0_PAN was disabled by commit:
c25f2bf469b3 ("UBUNTU: [config] oracle: Bring-up for arm64 support")
This config option is enabled on all other Ubuntu kernels and should
be enabled for the Oracle kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968902/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. == original bug report == [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1967988] Re: Support different Cirrus audio codec configurations on Dell laptops
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1034.37 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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967988 Title: Support different Cirrus audio codec configurations on Dell laptops Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On Dell's platform, Warlock/Bullseye Laptops have a mono DMIC, Cyborg and some Warlock variants uses a stereo DMIC. They are not correctly mapped to the corresponding configurations so the microphone function are not working as expected. [Fix] Cirrus upstream new FIXUPs to support different microphone configurations on different Dell laptop variants. [Test Case] 1. Go to Audio Settings 2. Make sure the microphone is correctly detected and responds to audio input. 3. Issue command "arecord record_file" and check the record_file is consistent with audio input. [Where problems could occur] Risk should be Low. The patches come from Cirrus and the configurations are mapped based on the audio codec's SSIDs for different Dell variants. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967988/+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 1968892] Re: Micmute LED support for Zbook Fury 16 G9
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1034.37 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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968892 Title: Micmute LED support for Zbook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The audio mute key(F5) LED does not work. [Fix] Need this commit from v5.18-rc1 ce18f905a500 ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 [Test] Verified on the target machine. [Where problems could occur] The modified hda_fixups, ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED, has the same contain as ALC245_FIXUP_CS35L41_SPI_2, but with new mic mute led gpio settings. So, if might affect the machines with the same chip ID that mic mute led is already working. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968892/+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 1960485] Re: intel graphics driver don't work
5.14 OEM kernel also not work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1960485 Title: intel graphics driver don't work Status in linux-oem-5.10 package in Ubuntu: Won't Fix Bug description: I use Huawei Mate Book e 2022，the Intel graphics devices is Intel Iris Xe （Intel Corporation Device [8086:9a40]）. But the kernel didn't support, I have to use the params with nomodeset, i can't change brightness. Also /sys/class/backlight/ is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1960485/+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
