[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
** Changed in: hwe-next Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
The fix is landed in Ubuntu-6.2.0-34.34 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+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 2034479] Re: Fix suspend hang on Lenovo workstation
The fix is landed in Ubuntu-5.15.0-88.98 and Ubuntu-6.2.0-36.36. ** Tags removed: verification-needed-jammy-linux verification-needed-lunar-linux ** Tags added: verification-done-jammy-linux verification-done-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1 and merged by stable update in oem-6.1, SRU for Jammy and Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+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 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
The fix is landed in Ubuntu-oem-6.1-6.1.0-1024.24, Ubuntu-6.2.0-36.36 and Ubuntu-5.15.0-88.98 ** Tags removed: verification-needed-jammy-linux verification-needed-jammy-linux-oem-6.1 verification-needed-lunar-linux ** Tags added: verification-done-jammy-linux verification-done-jammy-linux-oem-6.1 verification-done-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
Tested on hardware and run s2idle stress test 30 times OK. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: New Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+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 1970923] Re: [SRU][F/J] Update firmware of MT7922
** Tags added: verification-done-focal ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1975798] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1975798 Title: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] Lenovo(Z13/Z16) advertises an orientation sensor connected to SFH. But actually it's not there. [Fix] Read reg of sensor discovery. [Test] Verified on hardware, it show failure and driver returned. [Where problems could occur] Low risk, it may break AMD SFH driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1975798/+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 1975804] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: linux-oem-5.14 (Ubuntu Jammy)
** No longer affects: linux-oem-5.17 (Ubuntu Focal)
** No longer affects: linux (Ubuntu Focal)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: hwe-next
Assignee: (unassigned) => AaronMa (mapengyu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1975804
Title:
[SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on
AMD A+A GPU
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
New
Status in linux-oem-5.14 source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux-oem-5.17 source package in Jammy:
New
Bug description:
[Impact]
Sytesm may hang after s2idle on AMD A+A GPU config due to the following
commits:
8b328c64c7082278c888927f00e526786eec2880 ("drm/amdgpu: don't use BACO
for reset in S3") https://bugs.launchpad.net/bugs/1968475
a26d80ba0d9e67ea11cbfc25618320163497d3fe ("drm/amd/pm: keep the BACO
feature enabled for suspend") https://bugs.launchpad.net/bugs/1958371
[Fix]
Revert one commit and don't reset dGPU when s2idle
[Test]
Verified on AMD RMB, stress s2idle passed.
[Where problems could occur]
Low risk, it may break s2idle on AMD platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1975804/+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 1975798] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1975798 Title: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] Lenovo(Z13/Z16) advertises an orientation sensor connected to SFH. But actually it's not there. [Fix] Read reg of sensor discovery. [Test] Verified on hardware, it show failure and driver returned. [Where problems could occur] Low risk, it may break AMD SFH driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1975798/+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 1975804] [NEW] [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU
Public bug reported:
[Impact]
Sytesm may hang after s2idle on AMD A+A GPU config due to the following
commits:
8b328c64c7082278c888927f00e526786eec2880 ("drm/amdgpu: don't use BACO
for reset in S3") https://bugs.launchpad.net/bugs/1968475
a26d80ba0d9e67ea11cbfc25618320163497d3fe ("drm/amd/pm: keep the BACO
feature enabled for suspend") https://bugs.launchpad.net/bugs/1958371
[Fix]
Revert one commit and don't reset dGPU when s2idle
[Test]
Verified on AMD RMB, stress s2idle passed.
[Where problems could occur]
Low risk, it may break s2idle on AMD platform.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags: amd oem-priority originate-from-1972903
** Tags added: amd oem-priority originate-from-1972903
--
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/1975804
Title:
[SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on
AMD A+A GPU
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
New
Status in linux-oem-5.14 source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux-oem-5.17 source package in Jammy:
New
Bug description:
[Impact]
Sytesm may hang after s2idle on AMD A+A GPU config due to the following
commits:
8b328c64c7082278c888927f00e526786eec2880 ("drm/amdgpu: don't use BACO
for reset in S3") https://bugs.launchpad.net/bugs/1968475
a26d80ba0d9e67ea11cbfc25618320163497d3fe ("drm/amd/pm: keep the BACO
feature enabled for suspend") https://bugs.launchpad.net/bugs/1958371
[Fix]
Revert one commit and don't reset dGPU when s2idle
[Test]
Verified on AMD RMB, stress s2idle passed.
[Where problems could occur]
Low risk, it may break s2idle on AMD platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1975804/+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 1975804] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1975804
Title:
[SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on
AMD A+A GPU
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
New
Status in linux-oem-5.14 source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux-oem-5.17 source package in Jammy:
New
Bug description:
[Impact]
Sytesm may hang after s2idle on AMD A+A GPU config due to the following
commits:
8b328c64c7082278c888927f00e526786eec2880 ("drm/amdgpu: don't use BACO
for reset in S3") https://bugs.launchpad.net/bugs/1968475
a26d80ba0d9e67ea11cbfc25618320163497d3fe ("drm/amd/pm: keep the BACO
feature enabled for suspend") https://bugs.launchpad.net/bugs/1958371
[Fix]
Revert one commit and don't reset dGPU when s2idle
[Test]
Verified on AMD RMB, stress s2idle passed.
[Where problems could occur]
Low risk, it may break s2idle on AMD platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1975804/+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 1975798] [NEW] [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH
Public bug reported: [Impact] Lenovo(Z13/Z16) advertises an orientation sensor connected to SFH. But actually it's not there. [Fix] Read reg of sensor discovery. [Test] Verified on hardware, it show failure and driver returned. [Where problems could occur] Low risk, it may break AMD SFH driver. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1973144 ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.14 (Ubuntu Jammy) ** No longer affects: linux-oem-5.17 (Ubuntu Focal) ** Tags added: amd oem-priority originate-from-1973144 ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) -- 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/1975798 Title: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] Lenovo(Z13/Z16) advertises an orientation sensor connected to SFH. But actually it's not there. [Fix] Read reg of sensor discovery. [Test] Verified on hardware, it show failure and driver returned. [Where problems could occur] Low risk, it may break AMD SFH driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1975798/+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 1970923] Re: [SRU][F/J] Update firmware of MT7922
@h4wkmoon, Thanks for your test. send the patch to upstream: https://lore.kernel.org/linux-bluetooth/20220602092822.953521-1-aaron...@canonical.com/T/#u -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. - - Because of the schedule, SRU as SAUCE for focal only. - After this version is landed to linux-firmware, focal and jammy can be aligned with upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: New Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+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 1976214] [NEW] [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
Public bug reported: [Impact] Call trace on new ADL BIOS: kernel: [ cut here ] kernel: Missing case (devdata->child.hdmi_max_data_rate == 3) kernel: WARNING: CPU: 8 PID: 491 at drivers/gpu/drm/i915/display/intel_bios.c:1954 parse_ddi_port+0x724/0xab0 [i915] kernel: Modules linked in: fjes(+) snd_intel_sdw_acpi iwlmvm(+) snd_hda_codec intel_powerclamp snd_hda_core coretemp i915(+) mac80211 snd_hwdep libarc4 thinkpad_acpi(+) nvram snd_pcm drm_buddy platform_profile ledtrig_audio ttm kv> kernel: think_lmi(+) syscopyarea serio_raw efi_pstore firmware_attributes_class wmi_bmof mtd hid_multitouch ecc intel_cstate joydev nci cfg80211 industrialio mei_me snd clk_tps68470 sysfillrect videodev typec_ucsi intel_rapl_comm> kernel: CPU: 8 PID: 491 Comm: systemd-udevd Not tainted 5.18.0-051800rc6-generic #202205082130 kernel: Hardware name: LENOVO 21CDSIT245/21CDSIT245, BIOS N3AET58W (1.23 ) 04/15/2022 kernel: RIP: 0010:parse_ddi_port+0x724/0xab0 [i915] kernel: calling iwl_mvm_init+0x0/0x1000 [iwlmvm] @ 645 kernel: Code: 45 31 ed 45 0f b6 c9 e9 89 fa ff ff 0f b6 d0 48 c7 c6 90 c7 b8 c1 48 c7 c7 ea 2e b7 c1 4c 89 5d c8 4c 89 55 d0 e8 92 5c ee e0 <0f> 0b 4c 8b 55 d0 4c 8b 5d c8 e9 f8 fb ff ff 31 db e9 7d fa ff ff kernel: RSP: 0018:ac58c136b910 EFLAGS: 00010282 kernel: RAX: RBX: 0009 RCX: 0027 kernel: RDX: 8e63376205a8 RSI: 0001 RDI: 8e63376205a0 kernel: RBP: ac58c136b968 R08: 0003 R09: 0019 kernel: R10: 000a R11: 20676e697373694d R12: 8e5c4e7c kernel: R13: 0001 R14: R15: 0042 kernel: FS: 7f17f9ba2880() GS:8e633760() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 55695ac9c7c8 CR3: 000118806002 CR4: 00770ee0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: intel_bios_init+0x4f5/0x6a0 [i915] kernel: intel_modeset_init_noirq+0x3a/0x260 [i915] kernel: i915_driver_probe+0x201/0x590 [i915] kernel: ? acpi_dev_found+0x66/0x70 kernel: i915_pci_probe+0x58/0x140 [i915] kernel: local_pci_probe+0x48/0x90 kernel: pci_call_probe+0x55/0x180 kernel: pci_device_probe+0x84/0x110 kernel: really_probe+0x1b3/0x390 kernel: __driver_probe_device+0x96/0x190 kernel: driver_probe_device+0x23/0xc0 kernel: __driver_attach+0xbd/0x1d0 kernel: ? __device_attach_driver+0x110/0x110 kernel: bus_for_each_dev+0x7c/0xc0 kernel: driver_attach+0x1e/0x30 kernel: bus_add_driver+0x162/0x200 kernel: driver_register+0x95/0xf0 kernel: __pci_register_driver+0x68/0x70 kernel: i915_pci_register_driver+0x23/0x30 [i915] kernel: i915_init+0x3b/0xeb [i915] kernel: ? 0xc1c7 kernel: do_one_initcall+0x46/0x210 kernel: ? kmem_cache_alloc_trace+0x1a6/0x320 kernel: do_init_module+0x52/0x260 kernel: load_module+0xb81/0xc90 kernel: __do_sys_finit_module+0xc5/0x130 kernel: __x64_sys_finit_module+0x18/0x20 kernel: do_syscall_64+0x59/0x80 kernel: ? do_syscall_64+0x69/0x80 kernel: ? irqentry_exit+0x35/0x40 kernel: ? sysvec_reschedule_ipi+0x7b/0x120 kernel: ? asm_sysvec_reschedule_ipi+0xa/0x20 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae kernel: RIP: 0033:0x7f17f9e4b73d kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 23 37 0d 00 f7 d8 64 89 01 48 kernel: RSP: 002b:7ffc5d349e18 EFLAGS: 0246 ORIG_RAX: 0139 kernel: RAX: ffda RBX: 5644ea7d3960 RCX: 7f17f9e4b73d kernel: RDX: RSI: 5644ea7db9a0 RDI: 0019 kernel: RBP: 0002 R08: R09: kernel: R10: 0019 R11: 0246 R12: 5644ea7db9a0 kernel: R13: R14: 5644ea5aaf60 R15: 5644ea7d3960 kernel: kernel: ---[ end trace ]--- [Fix] Update new TMDS clock setting defined by VBT to configure max TMDS clock rate. [Test] Verified on hardware, no errors or calltrace. [Where problems could occur] Low risk, add new definition on new hardware. It may break i915 driver. Backported in minor change because this part of code is made to a function. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1968589 sutto
[Kernel-packages] [Bug 1976214] Re: [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => In Progress ** Changed in: hwe-next Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1976214 Title: [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] Call trace on new ADL BIOS: kernel: [ cut here ] kernel: Missing case (devdata->child.hdmi_max_data_rate == 3) kernel: WARNING: CPU: 8 PID: 491 at drivers/gpu/drm/i915/display/intel_bios.c:1954 parse_ddi_port+0x724/0xab0 [i915] kernel: Modules linked in: fjes(+) snd_intel_sdw_acpi iwlmvm(+) snd_hda_codec intel_powerclamp snd_hda_core coretemp i915(+) mac80211 snd_hwdep libarc4 thinkpad_acpi(+) nvram snd_pcm drm_buddy platform_profile ledtrig_audio ttm kv> kernel: think_lmi(+) syscopyarea serio_raw efi_pstore firmware_attributes_class wmi_bmof mtd hid_multitouch ecc intel_cstate joydev nci cfg80211 industrialio mei_me snd clk_tps68470 sysfillrect videodev typec_ucsi intel_rapl_comm> kernel: CPU: 8 PID: 491 Comm: systemd-udevd Not tainted 5.18.0-051800rc6-generic #202205082130 kernel: Hardware name: LENOVO 21CDSIT245/21CDSIT245, BIOS N3AET58W (1.23 ) 04/15/2022 kernel: RIP: 0010:parse_ddi_port+0x724/0xab0 [i915] kernel: calling iwl_mvm_init+0x0/0x1000 [iwlmvm] @ 645 kernel: Code: 45 31 ed 45 0f b6 c9 e9 89 fa ff ff 0f b6 d0 48 c7 c6 90 c7 b8 c1 48 c7 c7 ea 2e b7 c1 4c 89 5d c8 4c 89 55 d0 e8 92 5c ee e0 <0f> 0b 4c 8b 55 d0 4c 8b 5d c8 e9 f8 fb ff ff 31 db e9 7d fa ff ff kernel: RSP: 0018:ac58c136b910 EFLAGS: 00010282 kernel: RAX: RBX: 0009 RCX: 0027 kernel: RDX: 8e63376205a8 RSI: 0001 RDI: 8e63376205a0 kernel: RBP: ac58c136b968 R08: 0003 R09: 0019 kernel: R10: 000a R11: 20676e697373694d R12: 8e5c4e7c kernel: R13: 0001 R14: R15: 0042 kernel: FS: 7f17f9ba2880() GS:8e633760() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 55695ac9c7c8 CR3: 000118806002 CR4: 00770ee0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: intel_bios_init+0x4f5/0x6a0 [i915] kernel: intel_modeset_init_noirq+0x3a/0x260 [i915] kernel: i915_driver_probe+0x201/0x590 [i915] kernel: ? acpi_dev_found+0x66/0x70 kernel: i915_pci_probe+0x58/0x140 [i915] kernel: local_pci_probe+0x48/0x90 kernel: pci_call_probe+0x55/0x180 kernel: pci_device_probe+0x84/0x110 kernel: really_probe+0x1b3/0x390 kernel: __driver_probe_device+0x96/0x190 kernel: driver_probe_device+0x23/0xc0 kernel: __driver_attach+0xbd/0x1d0 kernel: ? __device_attach_driver+0x110/0x110 kernel: bus_for_each_dev+0x7c/0xc0 kernel: driver_attach+0x1e/0x30 kernel: bus_add_driver+0x162/0x200 kernel: driver_register+0x95/0xf0 kernel: __pci_register_driver+0x68/0x70 kernel: i915_pci_register_driver+0x23/0x30 [i915] kernel: i915_init+0x3b/0xeb [i915] kernel: ? 0xc1c7 kernel: do_one_initcall+0x46/0x210 kernel: ? kmem_cache_alloc_trace+0x1a6/0x320 kernel: do_init_module+0x52/0x260 kernel: load_module+0xb81/0xc90 kernel: __do_sys_finit_module+0xc5/0x130 kernel: __x64_sys_finit_module+0x18/0x20 kernel: do_syscall_64+0x59/0x80 kernel: ? do_syscall_64+0x69/0x80 kernel: ? irqentry_exit+0x35/0x40 kernel: ? sysvec_reschedule_ipi+0x7b/0x120 kernel: ? asm_sysvec_reschedule_ipi+0xa/0x20 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae kernel: RIP: 0033:0x7f17f9e4b73d kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 23 37 0d 00 f7 d8 64 89 01 48 kernel: RSP: 002b:7ffc5d349e18 EFLAGS: 0246 ORIG_RAX: 0139 kernel: RAX: ffda RBX: 5644ea7d3960 RCX: 7f17f9e4b73d kernel: RDX: RSI:
[Kernel-packages] [Bug 1970923] Re: [SRU][F/J] Update firmware of MT7922
@h4wkmoon Could you try to apply the attached patch and build kernel or btusb module to verify? ** Patch added: "0001-Bluetooth-btusb-Add-support-of-IMC-Networks-PID-0x35.patch" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1970923/+attachment/5593660/+files/0001-Bluetooth-btusb-Add-support-of-IMC-Networks-PID-0x35.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1978244] Re: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
** Tags removed: verification-needed-jammy ** Tags added: verification-done-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/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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 1978244] Re: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
Tested on 5.15.0-41 kernel, suspend and resume OK. -- 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/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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 1978244] [NEW] [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
Public bug reported: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) 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/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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 1978244] Re: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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 1978297] [NEW] [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211
Public bug reported: [Impact] When bootup Jammy kernel, it shows callrace: kernel: kernel: UBSAN: invalid-load in /home/u/aaron/bionic/net/mac80211/status.c:1164:21 kernel: load of value 216 is not a valid value for type '_Bool' kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.15.36+ #12 kernel: Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET30W (1.11 ) 05/27/2022 kernel: Call Trace: kernel: kernel: dump_stack_lvl+0x4a/0x5f kernel: dump_stack+0x10/0x12 kernel: ubsan_epilogue+0x9/0x45 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 kernel: ieee80211_tx_status_ext.cold+0x1e/0xb0 [mac80211] kernel: ? percpu_ref_kill_and_confirm+0xd0/0xd0 kernel: ? rht_key_get_hash.isra.0+0x19/0x20 [mac80211] kernel: ? sta_info_hash_lookup+0xac/0x100 [mac80211] kernel: ieee80211_tx_status+0x72/0xa0 [mac80211] kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] kernel: tasklet_action_common.constprop.0+0xc0/0xf0 kernel: tasklet_action+0x22/0x30 kernel: __do_softirq+0xd9/0x2e3 kernel: irq_exit_rcu+0x8c/0xb0 kernel: common_interrupt+0x8a/0xa0 kernel: kernel: kernel: asm_common_interrupt+0x1e/0x40 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620 kernel: Code: 3d b4 85 3d 5c e8 57 a7 6b ff 49 89 c7 0f 1f 44 00 00 31 ff e8 a8 b3 6b ff 80 7d d0> kernel: RSP: 0018:9e2dc01f7e38 EFLAGS: 0246 kernel: RAX: 8dfdb6870b00 RBX: 8df6c3ab6c00 RCX: 00023cd33784 kernel: RDX: 00023d103fa8 RSI: 00023cd33784 RDI: kernel: RBP: 9e2dc01f7e88 R08: 00023cd33d63 R09: 000aae60 kernel: R10: 0004 R11: 071c71c71c71c71c R12: a4ce65a0 kernel: R13: 0003 R14: 0003 R15: 00023cd33d63 kernel: ? cpuidle_enter_state+0xc8/0x620 kernel: ? sched_clock_local+0x13/0x90 kernel: cpuidle_enter+0x2e/0x40 kernel: do_idle+0x203/0x2a0 kernel: cpu_startup_entry+0x20/0x30 kernel: start_secondary+0x12a/0x180 kernel: secondary_startup_64_no_verify+0xc2/0xcb kernel: kernel: [Fix] The size of the status_driver_data field was not adjusted when the is_valid_ack_signal field was added. Adjust the struct size accordingly. [Test] Verified on hardware, no error. [Where problems could occur] Low risk, It may break wifi driver. Minor changes in title of "Copyright" when backport. ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Description changed: [Impact] When bootup Jammy kernel, it shows callrace: kernel: kernel: UBSAN: invalid-load in /home/u/aaron/bionic/net/mac80211/status.c:1164:21 kernel: load of value 216 is not a valid value for type '_Bool' kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.15.36+ #12 kernel: Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET30W (1.11 ) 05/27/2022 kernel: Call Trace: kernel: kernel: dump_stack_lvl+0x4a/0x5f kernel: dump_stack+0x10/0x12 kernel: ubsan_epilogue+0x9/0x45 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 kernel: ieee80211_tx_status_ext.cold+0x1e/0xb0 [mac80211] kernel: ? percpu_ref_kill_and_confirm+0xd0/0xd0 kernel: ? rht_key_get_hash.isra.0+0x19/0x20 [mac80211] kernel: ? sta_info_hash_lookup+0xac/0x100 [mac80211] kernel: ieee80211_tx_status+0x72/0xa0 [mac80211] kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] kernel: tasklet_action_common.constprop.0+0xc0/0xf0 kernel: tasklet_action+0x22/0x30 kernel: __do_softirq+0xd9/0x2e3 kernel: irq_exit_rcu+0x8c/0xb0 kernel: common_interrupt+0x8a/0xa0 kernel: kernel: kernel: asm_common_interrupt+0x1e/0x40 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620 kernel: Code: 3d b4 85 3d 5c e8 57 a7 6b ff 49 89 c7 0f 1f 44 00 00 31 ff e8 a8 b3 6b ff 80 7d d0> kernel: RSP: 0018:9e2dc01f7e38 EFLAGS: 0246 kernel: RAX: 8dfdb6870b00 RBX: 8df6c3ab6c00 RCX: 00023cd33784 kernel: RDX: 00023d103fa8 RSI: 00023cd33784 RDI: kernel: RBP: 9e2dc01f7e88 R08: 00023cd33d63 R09:
[Kernel-packages] [Bug 1975804] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1975804
Title:
[SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on
AMD A+A GPU
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
New
Status in linux-oem-5.14 source package in Focal:
New
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.17 source package in Jammy:
New
Bug description:
[Impact]
System may hang after s2idle on AMD A+A GPU config due to the following
commits:
8b328c64c7082278c888927f00e526786eec2880 ("drm/amdgpu: don't use BACO
for reset in S3") https://bugs.launchpad.net/bugs/1968475
a26d80ba0d9e67ea11cbfc25618320163497d3fe ("drm/amd/pm: keep the BACO
feature enabled for suspend") https://bugs.launchpad.net/bugs/1958371
[Fix]
Revert one commit and don't reset dGPU when s2idle
[Test]
Verified on AMD RMB, stress s2idle passed.
[Where problems could occur]
Low risk, it may break s2idle on AMD platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1975804/+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 1975798] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1975798 Title: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] Lenovo(Z13/Z16) advertises an orientation sensor connected to SFH. But actually it's not there. [Fix] Read reg of sensor discovery. [Test] Verified on hardware, it show failure and driver returned. [Where problems could occur] Low risk, it may break AMD SFH driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1975798/+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 1978986] [NEW] [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance on AMD
Public bug reported: [Impact] The brightness is not changed obviously during 200 to 255. [Fix] max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo and Rembrandt, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. Due to the schedule of OEM project, SRU this patch as SAUCE in OEM kernels only. ** Affects: hwe-next Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Tags: oem-priority originate-from-1962647 sutton ** Tags added: oem-priority originate-from-1962647 sutton ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux-oem-5.14 (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux-oem-5.17 (Ubuntu Focal) ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Incomplete ** Changed in: linux-oem-5.17 (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux-oem-5.17 (Ubuntu) Status: Opinion => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => In Progress ** Changed in: hwe-next Status: New => Fix Committed ** Changed in: hwe-next Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance on AMD Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The brightness is not changed obviously during 200 to 255. [Fix] max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo and Rembrandt, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. Due to the schedule of OEM project, SRU this patch as SAUCE in OEM kernels only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1978986] Re: [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance on AMD
** Description changed: [Impact] The brightness is not changed obviously during 200 to 255. [Fix] max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo and Rembrandt, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. + + Due to the schedule of OEM project, SRU this patch as SAUCE in OEM + kernels only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance on AMD Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The brightness is not changed obviously during 200 to 255. [Fix] max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo and Rembrandt, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. Due to the schedule of OEM project, SRU this patch as SAUCE in OEM kernels only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1981922] Re: Upgrade yellow carp DMCUB firmware to fix suspend failure
** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1981922 Title: Upgrade yellow carp DMCUB firmware to fix suspend failure Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Certain Rembrandt designs use LPDDR memory and current firmware in linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on DC power with it. Some sample designs affected by the failure are Thinkpad X13, Z13, Z16. This failure doesn't affect resume with AC power or designs without LPDDR memory. [Fix] Upgrade yellow carp DMCUB firmware binary. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24 [Test] Verify suspend/resume works. Verify that externally plugged displays haven't regressed. [Where problems could occur] Firmware is only loaded to Rembrandt designs. Regressions would be tied to those platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981922/+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 1982524] Re: QCNFA765 in Lenovo Z16 fails after waking from s2idle
ath11k issue will be fixed by next release of linux-firmware which is already in proposed channel. 20220329.git681281e4-0ubuntu3.3 WCN6855 firmware version: ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 -- 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/1982524 Title: QCNFA765 in Lenovo Z16 fails after waking from s2idle Status in linux package in Ubuntu: Confirmed Bug description: Hi, I use a pretty new model laptop lenovo z16 running kubuntu. Biggest issue right now is it has an issue where when it wakes up from sleep the wifi adapter fails to work. I have tried restarting network related services with no success. Visually it seems the wifi adapter may not be recognized as it only shows the lan icon after waking. The I have found some relevant output in /var/log/syslog that seems to confirm the issue (wlp4s0) but not much else and I'm not sure where best to look for more detailed information on this type of issue. I attached that output as it is a couple hundred lines even though I tried to just get some informative bits. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3GET35W(1.16):bd06/29/2022:br1.16:efr1.17:svnLENOVO:pn21D421D400:pvrThinkPadZ16Gen1:rvnLENOVO:rn21D421D400:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D4_BU_Think_FM_ThinkPadZ16Gen1: dmi.product.family: ThinkPad Z16 Gen 1 dmi.product.name: 21D421D400 dmi.product.sku: LENOVO_MT_21D4_BU_Think_FM_ThinkPad Z16 Gen 1 dmi.product.version: ThinkPad Z16 Gen 1 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias:
[Kernel-packages] [Bug 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking
This is a known issue of new vbios, please wait for a new BIOS to fix it. -- 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/1982679 Title: Lenovo T16 unable to wake up from sleep, screen blinking Status in linux package in Ubuntu: Confirmed Bug description: Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics. Running Ubuntu 22.04 LTS. Unable to wake up from sleep - the screen backlight is on, but the screen is solid black. After a while it starts randomly flashing with a login screen for about ~300ms and also each time I type a character. Also the "reboot" command hangs. Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in BIOS - same issue. Not sure if relevant, but journal log contains these lines: jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-sigterm' timed out. Killing. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes still around after SIGKILL. Ignoring. jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable link training jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-post' timed out. Terminating. jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'final-sigterm' timed out. Killing. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1761 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 09:22:18 2022 InstallationDate: Installed on 2022-07-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21BVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21BVCTO1WW dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982679/+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 1981922] Re: Upgrade yellow carp DMCUB firmware to fix suspend failure
** Tags added: amd oem-priority ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Kinetic) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1981922 Title: Upgrade yellow carp DMCUB firmware to fix suspend failure Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: In Progress Bug description: [Impact] Certain Rembrandt designs use LPDDR memory and current firmware in linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on DC power with it. Some sample designs affected by the failure are Thinkpad X13, Z13, Z16. This failure doesn't affect resume with AC power or designs without LPDDR memory. [Fix] Upgrade yellow carp DMCUB firmware binary. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24 [Test] Verify suspend/resume works. Verify that externally plugged displays haven't regressed. [Where problems could occur] Firmware is only loaded to Rembrandt designs. Regressions would be tied to those platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981922/+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 1970923] [NEW] [SRU][F/J] Update firmware of MT7922
Public bug reported: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1964309 originate-from-1965894 originate-from-1968687 originate-from-1968953 sutton ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1968687 sutton ** Tags added: originate-from-1964309 ** Tags added: originate-from-1968953 ** Tags added: originate-from-1965894 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Jammy: New Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1970923] Re: [SRU][F/J] Update firmware of MT7922
Already in progress. https://lists.ubuntu.com/archives/kernel-team/2022-April/129833.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Jammy: New Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1972806] [NEW] [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
Public bug reported: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. Because of the schedule, SRU as SAUCE for focal only. After this version is landed to linux-firmware, focal and jammy can be aligned with upstream. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1965726 sutton ** Tags added: oem-priority originate-from-1965726 sutton ** Summary changed: - [SRU][F] Update firmware of WCN6855 + [SRU][F][linux-firmware] Update firmware of WCN6855 ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Summary changed: - [SRU][F][linux-firmware] Update firmware of WCN6855 + [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. Because of the schedule, SRU as SAUCE for focal only. After this version is landed to linux-firmware, focal and jammy can be aligned with upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Could you try upstream kernel? 5.18-rc kernel got a lot of patches for rtw89. upstream bug: https://github.com/lwfinger/rtw89/issues/144 ** Bug watch added: github.com/lwfinger/rtw89/issues #144 https://github.com/lwfinger/rtw89/issues/144 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: New Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1969181] Re: [SRU][OEM-5.14] Fix iwlwifi iwl-nvm-parse.c warning
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969181 Title: [SRU][OEM-5.14] Fix iwlwifi iwl-nvm-parse.c warning Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] With Intel wifi card [8086:51f0], boot with oem-5.14.0-1027+, the warning will be shown: Mar 14 23:30:36 Phoenix-1 kernel: Call Trace: Mar 14 23:30:36 Phoenix-1 kernel: Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_get_regdomain+0xe2/0x1d0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_get_current_regdomain+0x4c/0x50 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_init_mcc+0x81/0x1d0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: ? iwl_acpi_get_dsm_u32+0x2f/0x60 [iwlwifi] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_up+0x87a/0xd70 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: __iwl_mvm_mac_start+0x2b/0x190 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_mac_start+0x50/0xb0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: drv_start+0x40/0xd0 [mac80211] Mar 14 23:30:36 Phoenix-1 kernel: ieee80211_do_open+0x394/0x810 [mac80211] Mar 14 23:30:36 Phoenix-1 kernel: ieee80211_open+0x6c/0x90 [mac80211] [Fix] This warning is introduced by commit: commit 827b84824ef2d910930c9974765de592e77b5072 Author: Chia-Lin Kao (AceLan) Date: Wed Feb 23 18:40:13 2022 +0800 UBUNTU: SAUCE: iwlwifi: disable 6-7 GHz channels BugLink: https://bugs.launchpad.net/bugs/1961971 Disable UHB (ultra high band) channels on all AX210/AX211 cards Signed-off-by: Chia-Lin Kao (AceLan) Signed-off-by: Timo Aaltonen Replace the warning to debug info to avoid the error message. [Test] Verified on HW with Intel wifi card, no errors after boot. [Where problems could occur] It may break Intel wifi driver. Change the debug info only, it's unlikely. The issue is on oem-5.14 only, no need for other kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969181/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18-rc5/ Please try AMD64 build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: New Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1978986] Re: [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
** Summary changed: - [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance on AMD + [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance ** Summary changed: - [SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance + [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: Invalid => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Released => In Progress ** Description changed: [Impact] - The brightness is not changed obviously during 200 to 255. + The brightness is not changed obviously during 200 to 255 on AMD + or 400 to 512 on Intel.. [Fix] + Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] - Verified on AMD Cezanne, Barcelo and Rembrandt, also on LCD panel and - OLED panel. The brightness is changed more obivously on OLED panel, and + Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. - Due to the schedule of OEM project, SRU this patch as SAUCE in OEM - kernels only. + All 3 patches are in drm-misc tree. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1990847] Re: Mobile broadband does not work after suspend on t460s with EM7455
>From log cdc_mbim is already registered after suspend: [ 521.493053] cdc_mbim 1-2:1.12: cdc-wdm0: USB WDM device [ 521.494980] cdc_mbim 1-2:1.12 wwan0: register 'cdc_mbim' at usb-:00:14.0-2, CDC MBIM, 3a:21:84:1e:5e:ae Can it be reconnected by restart NetworkManager or use cli? -- 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/1990847 Title: Mobile broadband does not work after suspend on t460s with EM7455 Status in linux package in Ubuntu: Confirmed Bug description: Mobile broadband does not work after suspend on Thinkpad t460s with built-in Sierra Wireless EM7455. It switches constantly on and off then. The only solution to repair the situation is to go to Windows and switching on there. After check in Settings > Mobile Broadband > Modem Details it looks like that after sleep the modem is not recognised any more. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: x 1799 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 007: ID 1199:9079 Sierra Wireless, Inc. EM7455 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FAS0B000 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c5109461-1cbf-452e-b76d-a13b0e90ca86 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy wayland-session Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/06/2022 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET88W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS0B000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET88W(1.56):bd07/06/2022:br1.56:efr1.14:svnLENOVO:pn20FAS0B000:pvrThinkPadT460s:rvnLENOVO:rn20FAS0B000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS0B000 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990847/+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 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
Fix blank screen on Thinkpad ADL 4K+ panel
Status in HWE Next:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
V2:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
Reload link rate as WA to fix the issue.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
It may break DP output on Intel platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
https://lists.ubuntu.com/archives/kernel-team/2022-August/132789.html This SRU is not in Ubuntu-oem-5.17-5.17.0-1020.21 or Ubuntu- oem-5.17-5.17.0-1019.20 @Timo Could you help double check? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1995041] [NEW] Fix ath11k deadlock on WCN6855
Public bug reported: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: In Progress ** Tags: oem-priority originate-from-1981178 sutton ** Tags added: oem-priority originate-from-1981178 sutton ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => In Progress ** Changed in: hwe-next Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress 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 linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: In Progress Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug
[Kernel-packages] [Bug 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
** Tags added: verification-done-jammy -- 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/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1980621] Re: [SRU][OEM-5.14/Jammy/OEM-5.17][PATCH 0/1] Fix blank screen on Thinkpad ADL 4K+ panel
** Description changed:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
+
+
+ V2:
+ [Impact]
+ Set screen off on ThinkPad P1G5 with 4k+ panel.
+ The screen will never be back.
+
+ [Fix]
+ Reload link rate as WA to fix the issue.
+
+ [Test]
+ Verified on hardware, screen on/off 20 times OK.
+
+ [Where problems could occur]
+ It may break DP output on Intel platform.
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: In Progress
** Also affects: linux-oem-5.14 (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** No longer affects: linux-oem-5.14 (Ubuntu Kinetic)
** No longer affects: linux-oem-5.17 (Ubuntu Kinetic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
[SRU][OEM-5.14/Jammy/OEM-5.17][PATCH 0/1] Fix blank screen on Thinkpad
ADL 4K+ panel
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Won't Fix
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
V2:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
Reload link rate as WA to fix the issue.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
It may break DP output on Intel platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel
Looks like the SRU [1] is missed in 2022.09.19 cycle of Jammy 5.15.
[1] https://lists.ubuntu.com/archives/kernel-
team/2022-September/133093.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
Fix blank screen on Thinkpad ADL 4K+ panel
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Won't Fix
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Bug description:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
V2:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
Reload link rate as WA to fix the issue.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
It may break DP output on Intel platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
https://lists.ubuntu.com/archives/kernel-team/2022-August/132789.html missed in oem-5.17. ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
I didn't reproduce this issue on 5.15. Did anyone reproduce it and can verify it? If so I can do SRU for it. -- 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/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
I will resend it to K/OEM-6.0/U once it lands in Linus's tree. ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Fix Released ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Kinetic) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AaronMa (mapengyu) ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) -- 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/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1988721] [NEW] [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
Public bug reported: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1981177 sutton ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Tags added: oem-priority originate-from-1981177 sutton -- 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/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking
It should be fixed in 48W, but looks like it's delayed. In the meanwhile, the potential fix: https://patchwork.freedesktop.org/patch/msgid/20220602141850.21301-6-animesh.ma...@intel.com You may want to try it. -- 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/1982679 Title: Lenovo T16 unable to wake up from sleep, screen blinking Status in linux package in Ubuntu: Confirmed Bug description: Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics. Running Ubuntu 22.04 LTS. Unable to wake up from sleep - the screen backlight is on, but the screen is solid black. After a while it starts randomly flashing with a login screen for about ~300ms and also each time I type a character. Also the "reboot" command hangs. Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in BIOS - same issue. Not sure if relevant, but journal log contains these lines: jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-sigterm' timed out. Killing. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes still around after SIGKILL. Ignoring. jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable link training jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-post' timed out. Terminating. jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'final-sigterm' timed out. Killing. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1761 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 09:22:18 2022 InstallationDate: Installed on 2022-07-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21BVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21BVCTO1WW dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1963615] Re: Add proper runtime PM support to Realtek PCIe cardreader
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem-5.17 (Ubuntu Focal) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1963615 Title: Add proper runtime PM support to Realtek PCIe cardreader Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] New generations of Realtek PCIe card reader cannot detect card insertion when the device is in PCI D3. [Fix] Rework the runtime PM flow and add chip specific support. [Test] With the series applied, the device can detect card insertion when it's in PCI D3. [Where problems could occur] System wide power management with less usage like hibernation, kexec reboot, etc. are not tested extensively. So these cases may be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963615/+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 1981922] Re: Upgrade yellow carp DMCUB firmware to fix suspend failure
@Mario, VCN is updated to commit: 9ed4d42c51aca "amdgpu: update Yellow Carp VCN firmware" The revert VCN and 22.20 is not merged. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1981922 Title: Upgrade yellow carp DMCUB firmware to fix suspend failure Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Certain Rembrandt designs use LPDDR memory and current firmware in linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on DC power with it. Some sample designs affected by the failure are Thinkpad X13, Z13, Z16. This failure doesn't affect resume with AC power or designs without LPDDR memory. [Fix] Upgrade yellow carp DMCUB firmware binary. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24 [Test] Verify suspend/resume works. Verify that externally plugged displays haven't regressed. [Where problems could occur] Firmware is only loaded to Rembrandt designs. Regressions would be tied to those platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981922/+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 1981922] Re: Upgrade yellow carp DMCUB firmware to fix suspend failure
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1981922 Title: Upgrade yellow carp DMCUB firmware to fix suspend failure Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Certain Rembrandt designs use LPDDR memory and current firmware in linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on DC power with it. Some sample designs affected by the failure are Thinkpad X13, Z13, Z16. This failure doesn't affect resume with AC power or designs without LPDDR memory. [Fix] Upgrade yellow carp DMCUB firmware binary. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24 [Test] Verify suspend/resume works. Verify that externally plugged displays haven't regressed. [Where problems could occur] Firmware is only loaded to Rembrandt designs. Regressions would be tied to those platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981922/+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 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking
New BIOS should be released in several days. Please wait for a while. -- 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/1982679 Title: Lenovo T16 unable to wake up from sleep, screen blinking Status in linux package in Ubuntu: Confirmed Bug description: Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics. Running Ubuntu 22.04 LTS. Unable to wake up from sleep - the screen backlight is on, but the screen is solid black. After a while it starts randomly flashing with a login screen for about ~300ms and also each time I type a character. Also the "reboot" command hangs. Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in BIOS - same issue. Not sure if relevant, but journal log contains these lines: jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-sigterm' timed out. Killing. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes still around after SIGKILL. Ignoring. jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable link training jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-post' timed out. Terminating. jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'final-sigterm' timed out. Killing. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1761 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 09:22:18 2022 InstallationDate: Installed on 2022-07-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21BVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21BVCTO1WW dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982679/+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 1942999] Re: [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock
** Summary changed: - [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock + [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Confirmed ** Description changed: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. + + Intel still doesn't provide any solution about their approach. + In the meantime, this patch is still the only fix. + Re-submit it to Jammy, oem-5.17 and Unstable kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. Intel still doesn't provide any solution about their approach. In the meantime, this patch is still the only fix. Re-submit it to Jammy, oem-5.17 and Unstable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
tested on 5.19.0-30-generic and 5.15.0-59-generic: Tx power table (channel 155) CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160
[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
The fix is landed in linux-firmware version: Ubuntu-20220923.gitf09bebf3-0ubuntu1.2 Ubuntu-20220923.gitf09bebf3-0ubuntu1.3 ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1995041] Re: Fix ath11k deadlock on WCN6855
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
Verified on 5.17.0-1025, the max brightness is changed along with the edid. ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel
Verified on 5.17.0-1025.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
Fix blank screen on Thinkpad ADL 4K+ panel
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
V2:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
Reload link rate as WA to fix the issue.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
It may break DP output on Intel platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1995041] Re: Fix ath11k deadlock on WCN6855
Verified on 5.17.0-1025 5.19.0-27 ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- 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/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
Verified on 5.17.0-1025 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1995041] Re: Fix ath11k deadlock on WCN6855
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
Fix blank screen on Thinkpad ADL 4K+ panel
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
V2:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
Reload link rate as WA to fix the issue.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
It may break DP output on Intel platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
Ha, built the branch locally. And mark in the comments that the patches are in the tree. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 2000299] [NEW] Fix W6400 hang after resume of S3 stress
Public bug reported: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Tags: oem-priority originate-from-1993996 sutton ** Tags added: oem-priority originate-from-1993996 sutton ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: hwe-next Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Description changed: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] - Low risk, It may cause AMD GPU hang. + Low risk, upstream fix. + It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. -- 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/2000299 Title: Fix W6400 hang after resume of S3 stress Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000299/+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 1997200] [NEW] Mediatek WLAN RZ616(MT7922) SAR table control
Public bug reported: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: oem-priority originate-from-1975584 sutton ** Tags added: oem-priority originate-from-1975584 sutton ** Summary changed: - Mediatek WLAN RZ616(aka MT7922) SAR table control + Mediatek WLAN RZ616(MT7922) SAR table control ** Description changed: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
** Description changed: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. + + These commits are already in oem-6.0 and unstable. ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: hwe-next Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
Verification-done-jammy-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1995041] Re: Fix ath11k deadlock on WCN6855
Verification-done-jammy-5.15 Verification-done-jammy-5.17-oem Verification-done-oem-6.0 Verification-done-kinetic Verification-done- unstable-6.1 -- 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/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel
verification-done-jammy verification-done-oem-5.17 verification-done-
oem-6.0 verification-done-kinetic verification-done-unstable
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
Fix blank screen on Thinkpad ADL 4K+ panel
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
It's a upstream kernel regression.
And reverted by upstream.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
Low risk, it reverts a regression and may break i915 driver.
On 5.14-oem and Jammy kernel, This commit was claimed to backport
commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for
max dp source rate")
But it's not kind of it.
So revert it instead.
On 5.17 kernel, revert it by upstream commit.
Unstable kernel already got it.
V2:
[Impact]
Set screen off on ThinkPad P1G5 with 4k+ panel.
The screen will never be back.
[Fix]
Reload link rate as WA to fix the issue.
[Test]
Verified on hardware, screen on/off 20 times OK.
[Where problems could occur]
It may break DP output on Intel platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
verification-done-jammy verification-done-oem-5.17 verification-done- oem-6.0 verification-done-kinetic verification-done-unstable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
Hi Acelan,
The first bad commit:
commit 224dffc89a957e2f006de3202d12c09bf348f992 (refs/bisect/bad)
Author: Alex Deucher
Date: Wed Dec 21 15:26:47 2022 +0800
drm/amdgpu: make sure to init common IP before gmc
BugLink: https://launchpad.net/bugs/2000110
Move common IP init before GMC init so that HDP gets
remapped before GMC init which uses it.
This fixes the Unsupported Request error reported through
AER during driver load. The error happens as a write happens
to the remap offset before real remapping is done.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=216373
The error was unnoticed before and got visible because of the commit
referenced below. This doesn't fix anything in the commit below, rather
fixes the issue in amdgpu exposed by the commit. The reference is only
to associate this commit with below one so that both go together.
Fixes: 8795e182b02d ("PCI/portdrv: Don't disable AER reporting in
get_port_device_capability()")
Acked-by: Christian König
Reviewed-by: Lijo Lazar
Signed-off-by: Alex Deucher
Cc: sta...@vger.kernel.org
(cherry picked from commit a8671493d2074950553da3cf07d1be43185ef6c6)
Signed-off-by: Chia-Lin Kao (AceLan)
Is this commit necessary for LP:2000110, if not it should be reverted.
Otherwise, the following series are needed:
https://lore.kernel.org/linux-pci/20220909164758.5632-1-alexander.deuc...@amd.com/
** Bug watch added: Linux Kernel Bug Tracker #216373
https://bugzilla.kernel.org/show_bug.cgi?id=216373
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Incomplete => Triaged
--
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/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Triaged
Bug description:
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not
100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
so this appears to be a regression in whatever changes there were in
the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
5.17.0.1026.27.
I think this should be high priority, because it gives the impression
that the system is completely borked, when in actuality it's probably
just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting
the system (the microphone mute LED comes on as expected), but even X
starting does not turn the screen back on. Switching to the frame
buffer console with Ctrl-Alt-Fx does nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
** Also affects: alsa-ucm-conf (Ubuntu Lunar) Importance: Critical Status: In Progress ** Also affects: alsa-ucm-conf (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Bug description: [Impact] Mic-mute LED is broken on some AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2009642] Re: mt7921: add support of MTFG table
Verified on linux-firmware Ubuntu-20220329.git681281e4-0ubuntu3.11. ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2009642 Title: mt7921: add support of MTFG table Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. Lunar already got the firmware, so SRU for Jammy only. Kernel commit is a new feature and it requests more than 10 unrelated commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009642/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu1.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2012590/+attachment/5656740/+files/alsa-ucm-conf_1.2.6.3-1ubuntu1.5.debdiff ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => Critical ** Tags added: oem-priority originate-from-2001611 sutton ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: hwe-next Importance: Undecided => Critical ** Changed in: hwe-next Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Bug description: [Impact] Mic-mute LED is broken on some AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2012590] [NEW] Fix broken micmute LED on AMD ACP DMIC
Public bug reported: [Impact] Mic-mute LED is broken on some AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. ** Affects: hwe-next Importance: Critical Assignee: AaronMa (mapengyu) Status: In Progress ** Affects: alsa-ucm-conf (Ubuntu) Importance: Critical Status: In Progress ** Affects: alsa-ucm-conf (Ubuntu Jammy) Importance: Critical Status: In Progress ** Affects: alsa-ucm-conf (Ubuntu Lunar) Importance: Critical Status: In Progress ** Tags: oem-priority originate-from-2001611 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Bug description: [Impact] Mic-mute LED is broken on some AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2009642] Re: mt7921: add support of MTFG table
** Changed in: linux-firmware (Ubuntu Lunar) Status: In Progress => Invalid -- 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/2009642 Title: mt7921: add support of MTFG table Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009642/+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 2009642] [NEW] mt7921: add support of MTFG table
Public bug reported: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) 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/2009642 Title: mt7921: add support of MTFG table Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009642/+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 2009642] Re: mt7921: add support of MTFG table
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- 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/2009642 Title: mt7921: add support of MTFG table Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009642/+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 2009642] Re: mt7921: add support of MTFG table
** Description changed: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. + Lunar already got the firmware, so SRU for Jammy only. + Kernel commit is a new feature and it requests more than 10 unrelated + commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Invalid ** Tags added: oem-priority originate-from-2008052 sutton ** Tags added: originate-from-2007990 -- 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/2009642 Title: mt7921: add support of MTFG table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. Lunar already got the firmware, so SRU for Jammy only. Kernel commit is a new feature and it requests more than 10 unrelated commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009642/+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 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: In Progress => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Tags added: oem-priority originate-from-2002264 sutton -- 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/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+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 2009118] [NEW] Fix mediatek wifi driver crash when loading wrong SAR table
Public bug reported: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009118/+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 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
It's fixed now in proposed kernel linux-oem-6.1/6.1.0-1008.8 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+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 2009642] Re: mt7921: add support of MTFG table
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2009642 Title: mt7921: add support of MTFG table Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. Lunar already got the firmware, so SRU for Jammy only. Kernel commit is a new feature and it requests more than 10 unrelated commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009642/+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 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
Updated to Jammy 1.2.6.3-1ubuntu1.5, Mic-mute LED works as expected. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Mic-mute LED is broken on some AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
Thanks to @seb128 for your kindly help. ** Changed in: alsa-ucm-conf (Ubuntu Kinetic) Importance: Undecided => Critical ** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Sometimes Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
Also kinetic 1.2.6.3-1ubuntu4.2 ** Description changed: [Impact] - Mic-mute LED is broken on some AMD ACP DMIC. + Sometimes Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD ACP DMIC. [Fix] - Update Mic LED settings for ACP DMIC, + Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Sometimes Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2000299] Re: Fix W6400 hang after resume of S3 stress
** Tags removed: verification-needed-jammy ** Tags added: verification-done-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/2000299 Title: Fix W6400 hang after resume of S3 stress Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000299/+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 2023539] Re: Add audio support for ThinkPad P1 Gen 6
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: hwe-next Status: New => Invalid -- 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/2023539 Title: Add audio support for ThinkPad P1 Gen 6 Status in HWE Next: Invalid Status in linux package in Ubuntu: Invalid Bug description: [Impact] No sound output or sound output is too low on ThinkPad P1 Gen 6 [Fix] Add quirk for ThinkPad P1 Gen 6 [Test] Tested with alsa audio, audio works fine. [Where problems could occur] Risk low due to specific hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023539/+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 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2
** Summary changed: - Add audio support for ThinkPad P1 Gen 6 + Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 ** Description changed: [Impact] - No sound output or sound output is too low on ThinkPad P1 Gen 6 + No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2 [Fix] - Add quirk for ThinkPad P1 Gen 6 + Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2. [Test] Tested with alsa audio, audio works fine. [Where problems could occur] Risk low due to specific hardware. + + These 2 patches in already in Unstable and OEM-6.1 already got them via + stable updates. -- 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/2023539 Title: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 Status in HWE Next: Invalid Status in linux package in Ubuntu: Invalid Bug description: [Impact] No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2 [Fix] Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2. [Test] Tested with alsa audio, audio works fine. [Where problems could occur] Risk low due to specific hardware. These 2 patches in already in Unstable and OEM-6.1 already got them via stable updates. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023539/+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 2023650] Re: Add microphone support of the front headphone port on P3 Tower
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023650 Title: Add microphone support of the front headphone port on P3 Tower Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The 3.5mm headphone port in front panel cannot detect the microphone. [Fix] Add quirk for headset mic pin on P3 Tower. [Test] Tested with alsa audio, mic works fine. [Where problems could occur] Low risk to add specific hardware ID. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023650/+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 2023650] [NEW] Add microphone support of the front headphone port on P3 Tower.
Public bug reported: [Impact] The 3.5mm headphone port in front panel cannot detect the microphone. [Fix] Add quirk for headset mic pin on P3 Tower. [Test] Tested with alsa audio, mic works fine. [Where problems could occur] Low risk to add specific hardware ID. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2015957 sutton ** Tags added: oem-priority originate-from-2015957 sutton -- 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/2023650 Title: Add microphone support of the front headphone port on P3 Tower. Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] The 3.5mm headphone port in front panel cannot detect the microphone. [Fix] Add quirk for headset mic pin on P3 Tower. [Test] Tested with alsa audio, mic works fine. [Where problems could occur] Low risk to add specific hardware ID. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023650/+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
