[Kernel-packages] [Bug 1988806] [NEW] Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Public bug reported:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this kABI
to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel, it
will not include this kABI and as a result will break SRIOV based Nvidia
vGPU. So, filing this bug to request to have a custom patch in HWE
kernel which doesn't remove the support for mdev_set_iommu_device()
kABI.
** Affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in linux-meta package in Ubuntu:
New
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1988806/+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 1988809] [NEW] ip/nexthop: fix default address selection for connected nexthop
Public bug reported:
[Impact]
Packets sent by userland apps are rejected/dropped if the source address
is not specified and the corresponding route is using a connected
nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test is
added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1988809
Title:
ip/nexthop: fix default address selection for connected nexthop
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
Packets sent by userland apps are rejected/dropped if the source
address is not specified and the corresponding route is using a
connected nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test
is added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+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 1988809] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1988809
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988809
Title:
ip/nexthop: fix default address selection for connected nexthop
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
Packets sent by userland apps are rejected/dropped if the source
address is not specified and the corresponding route is using a
connected nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test
is added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Since kernel 5.19 is now released to Ubuntu 22.10, this bug is Fix Released. But as mentioned in comment #87, we cannot fix Ubuntu 22.04 without further investigation done by those experiencing the bug. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1987312] Re: IWLMEI may cause device down at resuming from s2idle
** Description changed: + [SRU Justification] + + [Impact] + + WiFi interfaces unsolicitedly down at resuming from s2idle. + + [Fix] + Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. + + [Test Case] + + Make sure iwlmei.ko is not built. + + [Where problems could occur] + + iwlmei was not enabled before 5.17 and was turned on automatically since + then. This restores the state and shall not have impact on existing + devices. + + == original bug report == + + Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN + POR is only for Windows project design. Please remove or disable + CONFIG_IWLMEI from Linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1926564] Re: An recursive locking in igb and igc drivers
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: hwe-next Status: Incomplete => Fix Released -- 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/1926564 Title: An recursive locking in igb and igc drivers Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: [Impact] The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in __dev_open() it calls pm_runtime_resume() to resume devices, and in some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() again. That leads to a recursive lock. This issue is introduced by below commit since v5.9-rc1 bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] This commit currently is still under discussion fixes the issue. https://lkml.org/lkml/2021/4/20/123 [Test] Verified on Dell Precision workstations. [Where problems could occur] The patch is pretty straightforward, no problems could occur by this change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926564/+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 1987312] Re: IWLMEI may cause device down at resuming from s2idle
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-September/133010.html (oem-5.17/oem-6.0/kinetic/unstable) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1861634] Re: Dell XPS 9575 after resume from sleep/suspend, the backlight does not turn back on
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861634 Title: Dell XPS 9575 after resume from sleep/suspend, the backlight does not turn back on Status in linux package in Ubuntu: Fix Released Bug description: Release=Focal 20.04 (development) Pretty sure this is an xserver-xorg-video issue, please advise. After closing laptop lid on Dell XPS 9575 and resuming from sleep/suspend the backlight does not turn back on as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861634/+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 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
Thank you for your support. I will take a look at drm-tip kernels. I wish they were available through the Mainline application, it would make it much easier to install. I guess I'll need to wait for the fix in the kernel anyway. Cheers! -- 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/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: New Status in linux package in Ubuntu: New Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+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 1988825] [NEW] Cannot turn Bluetooth on in Ubuntu 22.04.01
Public bug reported: The steps: * Going to settings -> Bluetooth * Turn Bluetooth on. Seems to stay on, but can't connect anything to it * Go to another place in Settings, go back to Bluetooth * Result: Bluetooth is turned off Thank you! Alex ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 11:52:13 2022 InstallationDate: Installed on 2022-06-16 (81 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GV301RE.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GV301RE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: ROG Flow X13 dmi.product.name: ROG Flow X13 GV301RE_GV301RE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1988825 Title: Cannot turn Bluetooth on in Ubuntu 22.04.01 Status in bluez package in Ubuntu: New Bug description: The steps: * Going to settings -> Bluetooth * Turn Bluetooth on. Seems to stay on, but can't connect anything to it * Go to another place in Settings, go back to Bluetooth * Result: Bluetooth is turned off Thank you! Alex ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 11:52:13 2022 InstallationDate: Installed on 2022-06-16 (81 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GV301RE.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GV301RE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: ROG Flow X13 dmi.product.name: ROG Flow X13 GV301RE_GV301RE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988825/+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 1988825] Re: [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01
Being machine-specific means this is almost certainly a kernel bug. ** Summary changed: - Cannot turn Bluetooth on in Ubuntu 22.04.01 + [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01 ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Summary changed: - [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01 + [mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01 -- 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/1988825 Title: [mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01 Status in linux package in Ubuntu: New Bug description: The steps: * Going to settings -> Bluetooth * Turn Bluetooth on. Seems to stay on, but can't connect anything to it * Go to another place in Settings, go back to Bluetooth * Result: Bluetooth is turned off Thank you! Alex ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 11:52:13 2022 InstallationDate: Installed on 2022-06-16 (81 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GV301RE.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GV301RE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: ROG Flow X13 dmi.product.name: ROG Flow X13 GV301RE_GV301RE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988825/+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
Re: [Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device down at resuming from s2idle
debdiff for Jammy (version 9858-0ubuntu6+22.04.1) and Kinetic (9904-0ubuntu2). Need sponsoring. ** Attachment added: "backport-iwlwifi-dkms_9904-0ubuntu2.debdiff" https://bugs.launchpad.net/bugs/1987312/+attachment/5613999/+files/backport-iwlwifi-dkms_9904-0ubuntu2.debdiff ** Attachment added: "backport-iwlwifi-dkms_9858-0ubuntu6+22.04.1.debdiff" https://bugs.launchpad.net/bugs/1987312/+attachment/5614000/+files/backport-iwlwifi-dkms_9858-0ubuntu6+22.04.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1988825] 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/1988825 Title: [mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01 Status in linux package in Ubuntu: Confirmed Bug description: The steps: * Going to settings -> Bluetooth * Turn Bluetooth on. Seems to stay on, but can't connect anything to it * Go to another place in Settings, go back to Bluetooth * Result: Bluetooth is turned off Thank you! Alex ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 11:52:13 2022 InstallationDate: Installed on 2022-06-16 (81 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GV301RE.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GV301RE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: ROG Flow X13 dmi.product.name: ROG Flow X13 GV301RE_GV301RE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988825/+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 1987312] Re: IWLMEI may cause device down at resuming from s2idle
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-September/133014.html (kernel-versions) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1988831] [NEW] Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on
Public bug reported: [Impact] * it is desired to have intel_iommu=on by default * However this is causing many gpu bugs which are resolvable with igfx_off parameter * there is no Kconfig that can have intel_iommu=igfx_off behaviour * introduce intel_iommu=igfx_on kernel command line * introduce Kconfig that allows to have iommu default igfx_off * turn both of them on [Test Plan] * Test that iommu is on by default * Test that igfx_off is off by default * Test that one can turn on GPU iommu with igfx_on [Where problems could occur] * Lots of GPU bugs are discovered each time we try to turn IOMMU by default, hopefully with igfx_off we might have more success in turning iommu on and keeping it on. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699 https://twitter.com/hughsient/status/1564335142243602432 [Other Info] * Rock & a hard place => our users expect working displays in default kernel config which IOMMU seems to break a lot. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: iommu -- 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/1988831 Title: Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on Status in linux package in Ubuntu: Incomplete Bug description: [Impact] * it is desired to have intel_iommu=on by default * However this is causing many gpu bugs which are resolvable with igfx_off parameter * there is no Kconfig that can have intel_iommu=igfx_off behaviour * introduce intel_iommu=igfx_on kernel command line * introduce Kconfig that allows to have iommu default igfx_off * turn both of them on [Test Plan] * Test that iommu is on by default * Test that igfx_off is off by default * Test that one can turn on GPU iommu with igfx_on [Where problems could occur] * Lots of GPU bugs are discovered each time we try to turn IOMMU by default, hopefully with igfx_off we might have more success in turning iommu on and keeping it on. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699 https://twitter.com/hughsient/status/1564335142243602432 [Other Info] * Rock & a hard place => our users expect working displays in default kernel config which IOMMU seems to break a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988831/+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 1988831] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988831 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988831 Title: Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on Status in linux package in Ubuntu: Incomplete Bug description: [Impact] * it is desired to have intel_iommu=on by default * However this is causing many gpu bugs which are resolvable with igfx_off parameter * there is no Kconfig that can have intel_iommu=igfx_off behaviour * introduce intel_iommu=igfx_on kernel command line * introduce Kconfig that allows to have iommu default igfx_off * turn both of them on [Test Plan] * Test that iommu is on by default * Test that igfx_off is off by default * Test that one can turn on GPU iommu with igfx_on [Where problems could occur] * Lots of GPU bugs are discovered each time we try to turn IOMMU by default, hopefully with igfx_off we might have more success in turning iommu on and keeping it on. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699 https://twitter.com/hughsient/status/1564335142243602432 [Other Info] * Rock & a hard place => our users expect working displays in default kernel config which IOMMU seems to break a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988831/+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 1988831] Re: Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on
** Summary changed: - Allow configuring kernel with igfx_off by default, with userspace override igfx_on + Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on -- 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/1988831 Title: Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on Status in linux package in Ubuntu: Incomplete Bug description: [Impact] * it is desired to have intel_iommu=on by default * However this is causing many gpu bugs which are resolvable with igfx_off parameter * there is no Kconfig that can have intel_iommu=igfx_off behaviour * introduce intel_iommu=igfx_on kernel command line * introduce Kconfig that allows to have iommu default igfx_off * turn both of them on [Test Plan] * Test that iommu is on by default * Test that igfx_off is off by default * Test that one can turn on GPU iommu with igfx_on [Where problems could occur] * Lots of GPU bugs are discovered each time we try to turn IOMMU by default, hopefully with igfx_off we might have more success in turning iommu on and keeping it on. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699 https://twitter.com/hughsient/status/1564335142243602432 [Other Info] * Rock & a hard place => our users expect working displays in default kernel config which IOMMU seems to break a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988831/+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 1988831] Re: Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1988831 Title: Allow configuring kernel with iommu=igfx_off by default, with cmdline optional override to igfx_on Status in linux package in Ubuntu: Triaged Bug description: [Impact] * it is desired to have intel_iommu=on by default * However this is causing many gpu bugs which are resolvable with igfx_off parameter * there is no Kconfig that can have intel_iommu=igfx_off behaviour * introduce intel_iommu=igfx_on kernel command line * introduce Kconfig that allows to have iommu default igfx_off * turn both of them on [Test Plan] * Test that iommu is on by default * Test that igfx_off is off by default * Test that one can turn on GPU iommu with igfx_on [Where problems could occur] * Lots of GPU bugs are discovered each time we try to turn IOMMU by default, hopefully with igfx_off we might have more success in turning iommu on and keeping it on. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699 https://twitter.com/hughsient/status/1564335142243602432 [Other Info] * Rock & a hard place => our users expect working displays in default kernel config which IOMMU seems to break a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988831/+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 1988836] [NEW] Enable the open NVIDIA kernel modules
Public bug reported: The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu- kernel-modules/ ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Bug description: The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu- kernel-modules/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1988836/+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 1988838] [NEW] No console output on kinetic pi server images
Public bug reported: On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g. from http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/) there is no console output over HDMI. The "rainbow" boot screen appears as usual, but then remains while the system continues to boot and never switches to display the console. The system does still boot successfully, I can SSH into it, and console over serial still works but not over HDMI (testing on a Pi 3, and two revisions of the Pi 4). Adding either kms overlay (vc4-fkms-v3d or vc4-kms-v3d) to the boot configuration resolves this. Is it simply the case that future kernels are going to require a KMS overlay of some flavour or other to operate the console? If so, that's probably a good thing to some degree (it'll remove another difference between the pi server and desktop images), but ubuntu- release-upgrader will need to work to enforce that in the boot configuration for upgraders (and I'll need to tweak the gadget to ensure it's always included from now on). ** 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/1988838 Title: No console output on kinetic pi server images Status in linux-raspi package in Ubuntu: New Bug description: On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g. from http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/) there is no console output over HDMI. The "rainbow" boot screen appears as usual, but then remains while the system continues to boot and never switches to display the console. The system does still boot successfully, I can SSH into it, and console over serial still works but not over HDMI (testing on a Pi 3, and two revisions of the Pi 4). Adding either kms overlay (vc4-fkms-v3d or vc4-kms-v3d) to the boot configuration resolves this. Is it simply the case that future kernels are going to require a KMS overlay of some flavour or other to operate the console? If so, that's probably a good thing to some degree (it'll remove another difference between the pi server and desktop images), but ubuntu-release-upgrader will need to work to enforce that in the boot configuration for upgraders (and I'll need to tweak the gadget to ensure it's always included from now on). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988838/+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 1982759] Re: [22.10 FEAT] [SEC2117] zcryptctl support for control domains - kernel part
linux-generic 5.19.0.15.15 landed in kinetic hence updating to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982759 Title: [22.10 FEAT] [SEC2117] zcryptctl support for control domains - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Allow to assign control domains to a device node created by zcryptctl. Let the zcrypt DD block all cex admin requests submitted to a device node unless it is targeted to a control domain that is configured for the device node. (for compatibility reasons by default all control domains are assigned to the device node) Motivation: improve access control to crypto resources via device nodes - e.g. for Docker containers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982759/+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 1982386] Re: [22.10 FEAT] Support IBM z16 Processor-Activity-Instrumentation Facility (kernel part)
linux-generic 5.19.0.15.15 landed in kinetic hence updating to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982386 Title: [22.10 FEAT] Support IBM z16 Processor-Activity-Instrumentation Facility (kernel part) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This is the kernel part of the feature: Support IBM z16 PAI Facility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982386/+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 1987312] Re: IWLMEI may cause device down at resuming from s2idle
This bug was fixed in the package backport-iwlwifi-dkms - 9904-0ubuntu2 --- backport-iwlwifi-dkms (9904-0ubuntu2) kinetic; urgency=low [ You-Sheng Yang ] * Disable IWLMEI (LP: #1987312) -- You-Sheng Yang Wed, 24 Aug 2022 21:39:38 +0800 ** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
The fix is here: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/pm I'll do the backport once it's included in linux-next. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in linux package in Ubuntu: Confirmed Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Thanks, please give this kernel a try: https://people.canonical.com/~khfeng/lp1988346/ -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep' finished. ``` I think the problem is: > Aug 31 1
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
After putting nvidia.NVreg_PreserveVideoMemoryAllocations=0 in the kernel command line I don't remember any black screens after wake from suspend. They certainly haven't happened in Ubuntu 22.04. The computer is always usable immediately after waking. However, I have gotten lockups some time later after waking. These seem to never happen if I only use my main monitor, connected to the DVI port of the GeForce GT 710. That is the way X is configured to start. However, if I switch to the second monitor at some point after booting (also DVI but connected to the HDMI port), then lockups can happen, even after I switch back to the primary monitor. I use xrandr to switch. This is with the 470 driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1980861] Re: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
Applied to: - kinetic/linux: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=04f71532747e18d2f7cb57f0d3cb66f6c00f3b24 - linux-unstable: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable/commit/?id=b7efb6d15dea641b6944b245864e1e618c275aaa ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980861 Title: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU Status in Snappy: New Status in linux package in Ubuntu: Fix Committed Bug description: The snapd/desktop/advocacy team are investigating the startup performance of running snaps. While doing this and comparing various distros (fedora, opensuse, ubuntu) on Igors reference hardware we noticed that fedora is substantially faster at starting snaps. After some research it turns out that they use the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use CONFIG_SQUASHFS_DECOMP_SINGLE. I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that the first run firefox startup went from 15s to 6s (!) on Igors reference hardware. Given the dramatic performance improvements we would like to get this option switched. However we need to be careful and double check that the results from https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue - back in 2016 the kernel team swtich to _DECOMP_SINGLE because just mounting a snap would use up 131Mb or memory(!). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1980861/+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 1988605] [NEW] linux-tools and linux-cloud-tools for ppa mainline kernels
You have been subscribed to a public bug: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy linux-headers-5.19.5-051905_5.19.5-051905.202208291036_all.deb linux-headers-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb linux-image-unsigned-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb linux-modules-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb^C root@xbmc:~/Downloads/Linux/5.19.5# apt-cache policy linux-headers-5.19.5-051905 linux-headers-5.19.5-051905-generic linux-image-unsigned-5.19.5-051905-generic linux-modules-5.19.5-051905-generic linux-headers-5.19.5-051905: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-headers-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-image-unsigned-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-modules-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status 3) What you expected to happen I expect cpupower and perf to be present also for ppa mainline kernels. It has been bothering me for a while now that it is not part of what is built. 4) What happened instead $ sudo perf stat -a -e power/energy-pkg/,power/energy-cores/,cycles -I 1000 sleep 1000 WARNING: perf not found for kernel 5.19.5-051905 You may need to install the following packages for this specific kernel: linux-tools-5.19.5-051905-generic linux-cloud-tools-5.19.5-051905-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic $ sudo cpupower WARNING: cpupower not found for kernel 5.19.5-051905 You may need to install the following packages for this specific kernel: linux-tools-5.19.5-051905-generic linux-cloud-tools-5.19.5-051905-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic Would be very useful if these tools was present also for mainline ppa kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment cpupower kernel-bug linux-tools perf -- linux-tools and linux-cloud-tools for ppa mainline kernels https://bugs.launchpad.net/bugs/1988605 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
I upgraded from 20.04.2 to 22.04.1 over the weekend using the normal do- release-upgrade process I've always used. Since then I notice Firefox takes 30ish seconds to load. Telegram same. Libreoffice literally 3 minutes to open. I've tried some of the suggestions in this ticket and the issue remains. Thinkpad X1 Carbon 6th gen, 16gb ram. Very frustrating bug. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : h
[Kernel-packages] [Bug 1988605] Re: linux-tools and linux-cloud-tools for ppa mainline kernels
** Package changed: ubuntu => linux (Ubuntu) -- 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/1988605 Title: linux-tools and linux-cloud-tools for ppa mainline kernels Status in linux package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy linux-headers-5.19.5-051905_5.19.5-051905.202208291036_all.deb linux-headers-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb linux-image-unsigned-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb linux-modules-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb^C root@xbmc:~/Downloads/Linux/5.19.5# apt-cache policy linux-headers-5.19.5-051905 linux-headers-5.19.5-051905-generic linux-image-unsigned-5.19.5-051905-generic linux-modules-5.19.5-051905-generic linux-headers-5.19.5-051905: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-headers-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-image-unsigned-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-modules-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status 3) What you expected to happen I expect cpupower and perf to be present also for ppa mainline kernels. It has been bothering me for a while now that it is not part of what is built. 4) What happened instead $ sudo perf stat -a -e power/energy-pkg/,power/energy-cores/,cycles -I 1000 sleep 1000 WARNING: perf not found for kernel 5.19.5-051905 You may need to install the following packages for this specific kernel: linux-tools-5.19.5-051905-generic linux-cloud-tools-5.19.5-051905-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic $ sudo cpupower WARNING: cpupower not found for kernel 5.19.5-051905 You may need to install the following packages for this specific kernel: linux-tools-5.19.5-051905-generic linux-cloud-tools-5.19.5-051905-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic Would be very useful if these tools was present also for mainline ppa kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988605/+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 1988605] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988605 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988605 Title: linux-tools and linux-cloud-tools for ppa mainline kernels Status in linux package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy linux-headers-5.19.5-051905_5.19.5-051905.202208291036_all.deb linux-headers-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb linux-image-unsigned-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb linux-modules-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb^C root@xbmc:~/Downloads/Linux/5.19.5# apt-cache policy linux-headers-5.19.5-051905 linux-headers-5.19.5-051905-generic linux-image-unsigned-5.19.5-051905-generic linux-modules-5.19.5-051905-generic linux-headers-5.19.5-051905: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-headers-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-image-unsigned-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status linux-modules-5.19.5-051905-generic: Installert: 5.19.5-051905.202208291036 Kandidat: 5.19.5-051905.202208291036 Versjonstabell: *** 5.19.5-051905.202208291036 100 100 /var/lib/dpkg/status 3) What you expected to happen I expect cpupower and perf to be present also for ppa mainline kernels. It has been bothering me for a while now that it is not part of what is built. 4) What happened instead $ sudo perf stat -a -e power/energy-pkg/,power/energy-cores/,cycles -I 1000 sleep 1000 WARNING: perf not found for kernel 5.19.5-051905 You may need to install the following packages for this specific kernel: linux-tools-5.19.5-051905-generic linux-cloud-tools-5.19.5-051905-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic $ sudo cpupower WARNING: cpupower not found for kernel 5.19.5-051905 You may need to install the following packages for this specific kernel: linux-tools-5.19.5-051905-generic linux-cloud-tools-5.19.5-051905-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic Would be very useful if these tools was present also for mainline ppa kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988605/+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 1713997] Re: kexec-tools should not ask to handle reboots
Hm, don't you still need kexec-tools installed to reboot with kexec via systemd? I think this bug should be more about asking to reboot using kexec with systemd. The only problem is that for that to work, Ubuntu would need to implement https://systemd.io/BOOT_LOADER_SPECIFICATION/ (or move to boot using systemd-boot instead of grub2 - then the former is gained for free). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1713997 Title: kexec-tools should not ask to handle reboots Status in kexec-tools package in Ubuntu: Confirmed Bug description: Reboots via kexec-tools are only supported on SysV init systems. With systemd the only supported init system by now, kexec-tools should no longer ask (during installation) if reboots should be handled by kexec-tools. There should be no user interaction required when installing the package. $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 $ apt-cache policy kexec-tools kexec-tools: Installed: 1:2.0.15-0ubuntu1 Candidate: 1:2.0.15-0ubuntu1 Version table: *** 1:2.0.15-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713997/+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 1988877] [NEW] package linux-image-5.15.0-47-generic 5.15.0-47.51 failed to install/upgrade: zapętlenie wyzwalaczy, przerywanie
Public bug reported: problem with installation of this package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195 Uname: Linux 5.4.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarek 1701 F pulseaudio /dev/snd/controlC1: jarek 1701 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Sep 6 22:00:08 2022 ErrorMessage: zapętlenie wyzwalaczy, przerywanie InstallationDate: Installed on 2018-11-17 (1389 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 5737 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-125-generic root=UUID=6904edfd-6e4c-4a84-8736-982c6474372e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-5.15.0-47-generic 5.15.0-47.51 failed to install/upgrade: zapętlenie wyzwalaczy, przerywanie UpgradeStatus: Upgraded to jammy on 2022-09-06 (0 days ago) dmi.bios.date: 09/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 045YHR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/27/2013:svnDellInc.:pnInspiron5737:pvrA06:rvnDellInc.:rn045YHR:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.family: 00 dmi.product.name: Inspiron 5737 dmi.product.sku: Inspiron 5737 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1988877 Title: package linux-image-5.15.0-47-generic 5.15.0-47.51 failed to install/upgrade: zapętlenie wyzwalaczy, przerywanie Status in linux package in Ubuntu: New Bug description: problem with installation of this package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195 Uname: Linux 5.4.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarek 1701 F pulseaudio /dev/snd/controlC1: jarek 1701 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Sep 6 22:00:08 2022 ErrorMessage: zapętlenie wyzwalaczy, przerywanie InstallationDate: Installed on 2018-11-17 (1389 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 5737 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-125-generic root=UUID=6904edfd-6e4c-4a84-8736-982c6474372e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-5.15.0-47-generic 5.15.0-47.51 failed to install/upgrade: zapętlenie wyzwalaczy, przerywanie UpgradeStatus: Upgraded to jammy on 2022-09-06 (0 days ago) dmi.bios.date: 09/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 045YHR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/27/2013:svnDellInc.:pnInspiron5737:pvrA06:rvnDellInc.:rn045YHR:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.family: 00 dmi.product.name: Inspiron 5737 dmi.product.sku: Inspiron 5737 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988877/+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 1988877] 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/1988877 Title: package linux-image-5.15.0-47-generic 5.15.0-47.51 failed to install/upgrade: zapętlenie wyzwalaczy, przerywanie Status in linux package in Ubuntu: Confirmed Bug description: problem with installation of this package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195 Uname: Linux 5.4.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarek 1701 F pulseaudio /dev/snd/controlC1: jarek 1701 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Sep 6 22:00:08 2022 ErrorMessage: zapętlenie wyzwalaczy, przerywanie InstallationDate: Installed on 2018-11-17 (1389 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 5737 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-125-generic root=UUID=6904edfd-6e4c-4a84-8736-982c6474372e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-5.15.0-47-generic 5.15.0-47.51 failed to install/upgrade: zapętlenie wyzwalaczy, przerywanie UpgradeStatus: Upgraded to jammy on 2022-09-06 (0 days ago) dmi.bios.date: 09/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 045YHR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/27/2013:svnDellInc.:pnInspiron5737:pvrA06:rvnDellInc.:rn045YHR:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.family: 00 dmi.product.name: Inspiron 5737 dmi.product.sku: Inspiron 5737 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988877/+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 1988346] Re: cm32181 module error blocking suspend
Update on the kernel 5.15.0-46 status. The light sensor does work after resuming from suspend, however the numbers reported are an order of magnitude greater than before. During day light it maxes out at 16941, but at night it will report 0, then if we shine light on it, return numbers > 1000 (before suspend it will return numbers < 100). -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
Please integrate the latest set of bug fix patches accepted in
mkp/scsi 5.20/scsi-staging
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post
RSCN completion
6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in
Fabric topology
6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
c364c453d30a scsi: lpfc: Revise FDMI reporting of supported port speed for
trunk groups
d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
39a1a86b9da2 scsi: lpfc: Move MI module parameter check to handle dynamic
disable
d531d9874da8 scsi: lpfc: Remove unnecessary NULL pointer assignment for
ELS_RDF path
76395c88d0af scsi: lpfc: Transition to NPR state upon LOGO cmpl if link down
or aborted
31e887864eb2 scsi: lpfc:
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
I have removed the repository 5.15.0-48 kernel and installed the kernels you linked to. (using dpkg -i *.deb). The system suspends successfully, but it does not wake from suspend. Here is the log showing the end of the suspend. At 23:10 I started suspend. At 23:13 I attempted to wake the machine from suspend but it did not respond. At 23:15 I held the power button to force restart the machine. The log below shows no activity between suspend at 23:10 and reboot at 23:15. Sep 06 23:10:01 nmurphy-laptop systemd-resolved[968]: wlan1: Bus client reset search domain list. Sep 06 23:10:01 nmurphy-laptop systemd-resolved[968]: wlan1: Bus client set default route setting: no Sep 06 23:10:01 nmurphy-laptop systemd-resolved[968]: wlan1: Bus client reset DNS server list. Sep 06 23:10:01 nmurphy-laptop gnome-shell[2605]: An active wireless connection, in infrastructure mode, involves no access point? Sep 06 23:10:02 nmurphy-laptop NetworkManager[1158]: [1662502202.0029] device (wlan1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Sep 06 23:10:02 nmurphy-laptop charon[1506]: 11[KNL] interface wlan1 deactivated Sep 06 23:10:02 nmurphy-laptop wpa_supplicant[1189]: p2p-dev-wlan1: CTRL-EVENT-DSCP-POLICY clear_all Sep 06 23:10:02 nmurphy-laptop wpa_supplicant[1189]: p2p-dev-wlan1: CTRL-EVENT-DSCP-POLICY clear_all Sep 06 23:10:02 nmurphy-laptop wpa_supplicant[1189]: nl80211: deinit ifname=p2p-dev-wlan1 disabled_11b_rates=0 Sep 06 23:10:02 nmurphy-laptop wpa_supplicant[1189]: wlan1: CTRL-EVENT-DSCP-POLICY clear_all Sep 06 23:10:02 nmurphy-laptop dropbox[2870]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Sep 06 23:10:02 nmurphy-laptop wpa_supplicant[1189]: wlan1: CTRL-EVENT-DSCP-POLICY clear_all Sep 06 23:10:02 nmurphy-laptop wpa_supplicant[1189]: nl80211: deinit ifname=wlan1 disabled_11b_rates=0 Sep 06 23:10:02 nmurphy-laptop gnome-shell[2605]: Timelines with detached actors are not supported. [:0x55d177cdad10] in animation of duration 500ms but not on stage. Sep 06 23:10:03 nmurphy-laptop systemd[1]: Reached target Sleep. Sep 06 23:10:03 nmurphy-laptop systemd[1]: Starting Record successful boot for GRUB... Sep 06 23:10:03 nmurphy-laptop systemd[1]: Starting System Suspend... Sep 06 23:10:03 nmurphy-laptop systemd[1]: grub-common.service: Deactivated successfully. Sep 06 23:10:03 nmurphy-laptop systemd[1]: Finished Record successful boot for GRUB. Sep 06 23:10:03 nmurphy-laptop systemd-sleep[3490]: Entering sleep state 'suspend'... Sep 06 23:10:03 nmurphy-laptop kernel: PM: suspend entry (deep) Sep 06 23:10:03 nmurphy-laptop kernel: Filesystems sync: 0.040 seconds Sep 06 23:10:03 nmurphy-laptop bluetoothd[1156]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) Sep 06 23:10:03 nmurphy-laptop acpid[1153]: input device has been disconnected, fd 21 Sep 06 23:10:03 nmurphy-laptop gsd-media-keys[2734]: Unable to get default sink Sep 06 23:10:03 nmurphy-laptop dbus-daemon[1157]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.77" (uid=1000 pid=2472 comm="/usr/bin/wireplumber " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destina> -- Boot b4a40c46e1b74b6485627edd07694b2e -- Sep 06 23:15:25 nmurphy-laptop kernel: microcode: microcode updated early to revision 0x26, date = 2019-11-12 Sep 06 23:15:25 nmurphy-laptop kernel: Linux version 5.15.0-48-generic (ubuntu@ip-10-0-129-176) (gcc (Ubuntu 12.2.0-1ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.39) #54 SMP Tue Sep 6 01:28:34 UTC 2022 (Ubuntu 5.15.0-48.54-generic 5.15.53) Sep 06 23:15:25 nmurphy-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Sep 06 23:15:25 nmurphy-laptop kernel: KERNEL supported cpus: Sep 06 23:15:25 nmurphy-laptop kernel: Intel GenuineIntel Sep 06 23:15:25 nmurphy-laptop kernel: AMD AuthenticAMD Sep 06 23:15:25 nmurphy-laptop kernel: Hygon HygonGenuine Sep 06 23:15:25 nmurphy-laptop kernel: Centaur CentaurHauls Sep 06 23:15:25 nmurphy-laptop kernel: zhaoxin Shanghai Sep 06 23:15:25 nmurphy-laptop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Sep 06 23:15:25 nmurphy-laptop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Sep 06 23:15:25 nmurphy-laptop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Sep 06 23:15:25 nmurphy-laptop kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Sep 06 23:15:25 nmurphy-laptop kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. -- 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/1988346 Title: cm32181 module error bl
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
** Description changed:
+ [IMPACT/Justification]
+
+
+ [FIX]
+
Please integrate the latest set of bug fix patches accepted in mkp/scsi
5.20/scsi-staging
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post
RSCN completion
6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in
Fabric topology
6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
c364c453d30a scsi: lpfc: Revise FDMI reporting of supported port speed for
trunk groups
d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
39a1a86b9da2 scsi: lpfc: Move MI module parameter check to handle dynamic
disable
d531d9874da8 scsi: lpfc: Remove unnecessary NULL pointer assignment for
ELS_RDF path
76395c88d0af scsi: lpfc: Transition to NPR state upon LOGO cmpl if link down
or aborted
31e887864eb2 scsi: lpfc: Update fc_prli_sent outstanding only after
guaranteed IOCB submit
672d1cb40551 scsi: lpfc: Protect memory leak for NPIV ports sending PLOGI_RJT
577a942df3de scsi: lpfc: Fix null pointer dereference after failing to issue
FLOGI and PLOGI
3483a44bdfb4 scsi: lpfc: Clear fabric topology flag before initiati
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Thanks for the testing. First, let's make sure the resume fail was caused by cm32181. So can you please run `sudo modprobe -r cm32181`, and see if your system can resume successfully? -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop
[Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device down at resuming from s2idle
** Tags added: originate-from-1983454 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in OEM Priority Project: New Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hi KC, Sure, Please share more details once you have more updates. In case there is a ticket for No Signal issue, please do share. Thanks and Best Regards, Murali -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 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.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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
