[Kernel-packages] [Bug 2080454] Re: NIC(r8169) didn't link up after resuming from suspend
This commit from upstream stable update leads to the issue.
commit 5e864d90b20803edf6bd44a99fb9afa7171785f2
Author: Atlas Yu
Date: Thu Mar 28 13:51:52 2024 +0800
r8169: skip DASH fw status checks when DASH is disabled
On devices that support DASH, the current code in the "rtl_loop_wait"
function
raises false alarms when DASH is disabled. This occurs because the function
attempts to wait for the DASH firmware to be ready, even though it's not
relevant in this case.
r8169 :0c:00.0 eth0: RTL8168ep/8111ep, 38:7c:76:49:08:d9, XID 502, IRQ
86
r8169 :0c:00.0 eth0: jumbo features [frames: 9194 bytes, tx
checksumming: ko]
r8169 :0c:00.0 eth0: DASH disabled
...
r8169 :0c:00.0 eth0: rtl_ep_ocp_read_cond == 0 (loop: 30, delay: 1).
This patch modifies the driver start/stop functions to skip checking the
DASH
firmware status when DASH is explicitly disabled. This prevents unnecessary
delays and false alarms.
The patch has been tested on several ThinkStation P8/PX workstations.
Fixes: 0ab0c45d8aae ("r8169: add handling DASH when DASH is disabled")
Signed-off-by: Atlas Yu
Reviewed-by: Heiner Kallweit
Link:
https://lore.kernel.org/r/20240328055152.18443-1-atlas...@canonical.com
Signed-off-by: Jakub Kicinski
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2080454
Title:
NIC(r8169) didn't link up after resuming from suspend
Status in linux-signed-hwe-6.8 package in Ubuntu:
New
Bug description:
[Summary]
During the SRU testing, I found a hp laptop always timeout after
suspend test, after checking I found that the NIC didn't link up.
Part of journal log as follows:
Sep 12 11:13:01 ubuntu kernel: PM: suspend entry (s2idle)
...
...
Sep 12 11:13:10 ubuntu kernel: PM: suspend exit
...
Sep 12 11:13:14 ubuntu kernel: r8169 :02:00.1 enp2s0f1: PCI error (cmd =
0x0407, status_errs = 0x)
[Expected result]
SRU test can continue after suspend test.
[Actual result]
SRU test times out and NIC is down.
[Additional information]
Following are the DUTs that are impacted.
https://certification.canonical.com/hardware/202304-31463/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.8.0-44-generic 6.8.0-44.44~22.04.1
ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckMismatches: ./preseed/project.cfg
CasperMD5CheckResult: fail
Date: Thu Sep 12 11:16:43 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-stella-jammy-amd64-20230920-537
InstallationDate: Installed on 2024-09-11 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
pc-stella-jammy-amd64-20230920-537
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.8
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2080454/+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 2078783] Re: revert the commit which breaks the soundwire audio in v6.11-rc6
** Description changed:
[Impact]
+ The commit included in v6.11-rc6 has been reported that breaks the audio.
+ ab8d66d132bc soundwire: stream: fix programming slave ports for non-continous
port maps
+
+ https://lore.kernel.org/alsa-
+
devel/b6c75eee-761d-44c8-8413-2a5b34ee2...@linux.intel.com/T/#m08e3dd833c64a99d5707de3440b3857c521ed242
[Fix]
+ The patch author submitted patch to revert it.
+
https://lore.kernel.org/alsa-devel/20240904145228.289891-1-krzysztof.kozlow...@linaro.org/T/#u
[Test]
+ The issue could be reproduce on Dell Bolan, so just check if the audio works
on the machine.
[Where problems could occur]
+ It won't change anything and the issue addressed by the ab8d66d132bc
("soundwire: stream: fix programming slave ports for non-continous port maps")
didn't fix actually.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2078783
Title:
revert the commit which breaks the soundwire audio in v6.11-rc6
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux-oem-6.11 source package in Noble:
In Progress
Bug description:
[Impact]
The commit included in v6.11-rc6 has been reported that breaks the audio.
ab8d66d132bc soundwire: stream: fix programming slave ports for non-continous
port maps
https://lore.kernel.org/alsa-
devel/b6c75eee-761d-44c8-8413-2a5b34ee2...@linux.intel.com/T/#m08e3dd833c64a99d5707de3440b3857c521ed242
[Fix]
The patch author submitted patch to revert it.
https://lore.kernel.org/alsa-devel/20240904145228.289891-1-krzysztof.kozlow...@linaro.org/T/#u
[Test]
The issue could be reproduce on Dell Bolan, so just check if the audio works
on the machine.
[Where problems could occur]
It won't change anything and the issue addressed by the ab8d66d132bc
("soundwire: stream: fix programming slave ports for non-continous port maps")
didn't fix actually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2078783/+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 2078783] [NEW] revert the commit which breaks the soundwire audio in v6.11-rc6
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.11 (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-6.11 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oem-6.11 (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2078783 Title: revert the commit which breaks the soundwire audio in v6.11-rc6 Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oem-6.11 source package in Noble: In Progress Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2078783/+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 2078652] Re: Clean up Compal DW5933e/T700 WWAN driver
** Changed in: linux (Ubuntu Noble) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Oracular) Status: In Progress => Invalid ** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Won't Fix ** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: Won't Fix => 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/2078652 Title: Clean up Compal DW5933e/T700 WWAN driver Status in linux package in Ubuntu: Invalid Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078652/+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 2078656] Re: NIC speed down to 10 Mbps after resuming from suspend
The issue should be fixed in 6.8.0-44.44 by below commit
commit 27e70aa72937bcfd08ffc10727ad315f9763e6ac
Author: Hui Wang
Date: Thu Jul 18 16:57:16 2024 +0800
e1000e: move force SMBUS near the end of enable_ulp function
BugLink: https://bugs.launchpad.net/bugs/2073358
The commit 861e8086029e ("e1000e: move force SMBUS from enable ulp
function to avoid PHY loss issue") introduces a regression on
PCH_MTP_I219_LM18 (PCIID: 0x8086550A). Without the referred commit, the
ethernet works well after suspend and resume, but after applying the
commit, the ethernet couldn't work anymore after the resume and the
dmesg shows that the NIC link changes to 10Mbps (1000Mbps originally):
[ 43.305084] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps
Full Duplex, Flow Control: Rx/Tx
Without the commit, the force SMBUS code will not be executed if
"return 0" or "goto out" is executed in the enable_ulp(), and in my
case, the "goto out" is executed since FWSM_FW_VALID is set. But after
applying the commit, the force SMBUS code will be ran unconditionally.
Here move the force SMBUS code back to enable_ulp() and put it
immediately ahead of hw->phy.ops.release(hw), this could allow the
longest settling time as possible for interface in this function and
doesn't change the original code logic.
The issue was found on a Lenovo laptop with the ethernet hw as below:
00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:550a]
(rev 20).
And this patch is verified (cable plug and unplug, system suspend
and resume) on Lenovo laptops with ethernet hw: [8086:550a],
[8086:550b], [8086:15bb], [8086:15be], [8086:1a1f], [8086:1a1c] and
[8086:0dc7].
Fixes: 861e8086029e ("e1000e: move force SMBUS from enable ulp function to
avoid PHY loss issue")
Signed-off-by: Hui Wang
Acked-by: Vitaly Lifshits
Tested-by: Naama Meir
Reviewed-by: Simon Horman
Reviewed-by: Paul Menzel
Signed-off-by: Tony Nguyen
Tested-by: Zhang Rui
Signed-off-by: Jacob Keller
Link:
https://lore.kernel.org/r/20240528-net-2024-05-28-intel-net-fixes-v1-1-dc8593d2b...@intel.com
Signed-off-by: Jakub Kicinski
(cherry picked from commit bfd546a552e140b0a4c8a21527c39d6d21addb28)
Signed-off-by: Aaron Ma
Acked-by: Thibault Ferrante
Acked-by: Noah Wager
Acked-by: Andrei Gherzan
Signed-off-by: Roxana Nicolescu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2078656
Title:
NIC speed down to 10 Mbps after resuming from suspend
Status in linux-signed-hwe-6.8 package in Ubuntu:
New
Bug description:
[Summary]
During the SRU testing, I found at least 2 DUTs always timeout after
suspend test, after checking I found that both of them only detect 10
Mbps speed on their NIC and can't get IP from DHCP.
Part of journal log as follows:
Sep 02 10:55:00 ubuntu kernel: PM: suspend entry (s2idle)
...
...
Sep 02 10:55:11 ubuntu kernel: PM: suspend exit
Sep 02 10:55:15 ubuntu kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up
10 Mbps Full Duplex, Flow Control: None
[Expected result]
SRU test can continue after suspend test and network speed should be
1000 Mbps.
[Actual result]
SRU test times out and network speed down to 10 Mbps.
[Additional information]
Following are the DUTs that are impacted.
https://certification.canonical.com/hardware/202312-33185/
https://certification.canonical.com/hardware/202312-32380/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
Uname: Linux 6.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 2 11:58:59 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-aron-14+X120
InstallationDate: Installed on 2024-08-20 (12 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.8
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2078656/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.ne
[Kernel-packages] [Bug 2078652] [NEW] Clean up Compal DW5933e/T700 WWAN driver
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.11 (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Oracular) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.11 (Ubuntu Oracular) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.11 (Ubuntu Oracular) Status: New => Invalid ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Oracular) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.11 (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Status: New => In Progress ** Changed in: linux-oem-6.11 (Ubuntu Noble) 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/2078652 Title: Clean up Compal DW5933e/T700 WWAN driver Status in linux package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.11 source package in Noble: In Progress Status in linux source package in Oracular: In Progress Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078652/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
Hi Bozsoki, >From the schedule, 2024.08.05 cycle will release 6.8.0-44 kernel. So, the optimise schedule will be at the end of Oct, which is 8 weeks later. https://kernel.ubuntu.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: In Progress Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-6.8 source package in Jammy: Confirmed Status in linux source package in Noble: Fix Committed Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: In Progress Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: SRU Justification [Impact] The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area. Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. The problem persists in the latest drm tip. [Fix] As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue. This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs. [Test] 1. Boot up to desktop with 6.8.0-x kernels 2. Moving cursor around the desktop 3. There should be no flicker while cursor is moving [Where problems could occur] For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency. Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal. === After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
I've submitted SRU for all Skylake GPU, and looks like we need to add KBL GPU to the list, too. Jeffery in #65 and Abdullah in #72 use KBL. We don't have SRU cycle in Sep., so will wait for another month to collect more info and submit another SRU later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: In Progress Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-6.8 source package in Jammy: Confirmed Status in linux source package in Noble: Fix Committed Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: In Progress Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: SRU Justification [Impact] The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area. Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. The problem persists in the latest drm tip. [Fix] As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue. This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs. [Test] 1. Boot up to desktop with 6.8.0-x kernels 2. Moving cursor around the desktop 3. There should be no flicker while cursor is moving [Where problems could occur] For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency. Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal. === After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
Hi Leonardo, Yes, we know the MTL flickering issue, you can try using "i915.enable_psr2_sel_fetch=0". The fix is planning to be landed on 6.8.0-45.45 or later. Or you can try switching to use 6.8-oem kernel which already includes the fix. sudo apt install linux-oem-22.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: In Progress Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-6.8 source package in Jammy: Confirmed Status in linux source package in Noble: Fix Committed Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: In Progress Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: SRU Justification [Impact] The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area. Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. The problem persists in the latest drm tip. [Fix] As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue. This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs. [Test] 1. Boot up to desktop with 6.8.0-x kernels 2. Moving cursor around the desktop 3. There should be no flicker while cursor is moving [Where problems could occur] For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency. Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal. === After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+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 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
SRU has been submitted, thanks Hui. https://lists.ubuntu.com/archives/kernel-team/2024-August/152912.html -- 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/2072679 Title: Regression: unable to reach low idle states on Tiger Lake Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: In the v2: Thanks for Timo to point out, there is the same problem for lunar-generic and mantic-generic kernels, and we applied to similar UBUNTU SAUCE patches to those kernels, but somehow we forgot to apply the patches to unstable at that time, hence we have regression for this issue in N/O/..., the tracking bug for L/M is: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034504 short-term plan: SRU the SAUCE patches to N/O/unstable, fix the regression on those Dell machines ASAP. long-term plan: Kai-heng will ping and discuss with linux-pci maintainers, modify the patch as maintainers request, once the formal patches are merged to upstream kernel, I will revert the SAUCE patches from N/O/unstable and SRU the formal patches to these kernels. [Impact] The NVME controller works in RAID on mode by default on some Dell machines, and in this case, the PCIE ASPM couldn't be enabled, and as a result the system idle can't enter deep idle states. This issue not only impacts ubuntu users but also impacts our Dell OEM projects. [Fix] pick 2 commits from linux-pci mailist [Test] After running the patched kernel, we could run 'sudo lspci -nnvv' and check "Non-Volatile memory controller": LnkCtl: ASPM L1 Enabled; And check idle states, we could see the system could enter deep idle: $ sudo cat /sys/kernel/debug/pmc_core/package_cstate_show Package C2 : 55740989 Package C3 : 4656373 Package C6 : 43325041 Package C7 : 6687655 Package C8 : 44948950 Package C9 : 1693 Package C10 : 92865596 [Where problems could occur] Because the patchset is not accepted by upstream yet, it is a bit risky to merge the patchset to ubuntu kernel. And the patch only impacts vmd driver, hence if there is regression, it could only be in the nvme driver with RAID on mode. The regression possibility is very low because we already tested the patch on many Dell, lenovo machines, there is no regression so far. After upgrading to Ubuntu 24.04 the CPU is unable to hit lower idle states. The device is a HP Spectre x360 14 (14-ea1000) with a Tiger Lake CPU. This is a regression introduced somewhere 6.5.0-42 and 6.8.0-36. The issue is not observed when booting the same OS with 6.5.0-42. Some debug output: root@hp-spectre-x360:/sys/kernel/debug/pmc_core# cat package_cstate_show Package C2 : 36087003 Package C3 : 69314350 Package C6 : 0 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 0 $ sudo cat /sys/kernel/debug/pmc_core/substate_requirements Element |S0i2.0 |Status | pmc0:USB2PLL_OFF_STS | Required | Yes | pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | | pmc0: PCIe_Gen3PLL_OFF_STS | Required | Yes | pmc0:OPIOPLL_OFF_STS | Required | Yes | pmc0: OCPLL_OFF_STS | Required | Yes | pmc0:MIPIPLL_OFF_STS | Required | Yes | pmc0:AC_Ring_Osc_OFF_STS | Required | Yes | pmc0:SATAPLL_OFF_STS | Required | Yes | pmc0:CSME_PG_STS | Required | Yes | pmc0:SATA_PG_STS | Required | Yes | pmc0:xHCI_PG_STS | Required | Yes | pmc0: UFSX2_PG_STS | Required | Yes | pmc0: OTG_PG_STS | Required | Yes | pmc0: SPA_PG_STS | Required | Yes | pmc0: SPB_PG_STS | Required | Yes | pmc0: SPC_PG_STS | Required | | pmc0:THC0_PG_STS | Required | Yes | pmc0:THC1_PG_STS | Required | Yes | pmc0: GBETSN_PG_STS | Required | Yes | pmc0: GBE_PG_STS | Required | Yes | pmc0:LPSS_PG_STS | Required | Yes | pmc0: xHCI0_D3_STS | Required | Yes | pmc0: xDCI1_D3_STS | Required | Yes | pmc0: IS_D3_STS | Required | Yes | pmc0: GBE_TSN_D3_STS | Required | Yes | pmc0: CPU_C10_REQ_STS_0 | Required | Yes | pmc0:MPHY_Core_DL_REQ_STS_16 | Required | | pmc0: Break-even_En_REQ_STS_17 | Required | Yes | pmc0:Auto-demo_En_REQ_STS_18 | Required | Yes | pmc0: Int_Timer_SS_Wake0_Pol_STS | Required |
[Kernel-packages] [Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
I believe there are 2 types of flicker issues. If disable PSR works for you, you can attach your panel edid on bug 2069993 sudo get-edid > edid.bin Our colleague will help you adding your panel to the driver. And in this bug, we are trying to fix the flicker issue that can be worked around by intel_iommu=igfx_off I'll need your VGA PCI ID if intel_iommu=igfx_off works for you. lspci -nnk | grep -A3 VGA -- 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/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: SRU Justification [Impact] The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area. Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. The problem persists in the latest drm tip. [Fix] As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue. This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs. [Test] 1. Boot up to desktop with 6.8.0-x kernels 2. Moving cursor around the desktop 3. There should be no flicker while cursor is moving [Where problems could occur] For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency. Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal. === After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+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 2073538] Re: kacpi_notify high cpu on interrupt gpe17
You can see there are so many ucsi_acpi_notify events which should be from GPE17. The root cause is never from the ucsi driver, it's been DOS to timeout. 2024-08-08T17:16:11.837231-04:00 victus kernel: message repeated 6360 times: [ ucsi_acpi_notify: CCI: 0] 2024-08-08T17:16:11.837236-04:00 victus kernel: ucsi_acpi USBC000:00: failed to reset PPM! 2024-08-08T17:16:11.837246-04:00 victus kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed It's good that you can build the kernel by yourself, in this case you can try to check if the quirk is activate on your machine by adding some debug message in the second patch. And also check what ucsi command you got, maybe you got some different commands oether than the hardocded commands in the first patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2073538 Title: kacpi_notify high cpu on interrupt gpe17 Status in linux package in Ubuntu: Incomplete Bug description: Picked up a HP laptop during July sales, and found the CPU soars to 80+ with kacpi_notify hitting GPE17. I would like some help finding the cause. Google searches were vague about masking the interrupt which did NOT help. If we can find what is calling the interrupts maybe we can better document a solution. top - 20:00:05 up 10 min, 1 user, load average: 86.24, 76.27, 42.44 Tasks: 453 total, 2 running, 451 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.1 us, 8.5 sy, 0.0 ni, 91.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 62040.5 total, 51595.7 free, 3166.0 used, 8146.3 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 58874.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 127 root 20 0 0 0 0 D 1.3 0.0 0:03.71 [kworker/11:1+kacpi_notify] 280 root 20 0 0 0 0 D 1.3 0.0 0:06.63 [kworker/5:5+kacpi_notify] 314 root 20 0 0 0 0 D 1.3 0.0 0:06.68 [kworker/5:12+kacpi_notify] ubuntu@ubuntu:~$ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0' /sys/firmware/acpi/interrupts/sci:1907 /sys/firmware/acpi/interrupts/gpe_all:1907 /sys/firmware/acpi/interrupts/gpe17:1907 EN enabled unmasked ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 2813 F pipewire /dev/snd/controlC1: ubuntu 2815 F wireplumber /dev/snd/controlC0: ubuntu 2815 F wireplumber /dev/snd/controlC2: ubuntu 2815 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu Jul 18 19:52:46 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: HP Victus by HP Gaming Laptop 15-fb2xxx ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2024 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8C2F dmi.board.vendor: HP dmi.board.version: 04.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 4.14 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/20/2024:br15.3:efr4.14:svnHP:pnVictusbyHPGamingLaptop15-fb2xxx:pvr:rvnHP:rn8C2F:rvr04.14:cvnHP:ct10:cvrChassisVersion:skuA14MNUA#ABA: dmi.product.family: 103C_5335M7 HP Victus dmi.product.name: Victus by HP Gaming Laptop 15-fb2xxx dmi.product.sku: A14MNUA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+subscriptions -- Mailing list: https://launchpad.net/~kerne
[Kernel-packages] [Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
Thanks for reporting the issue, here is the SRU https://lists.ubuntu.com/archives/kernel-team/2024-August/152750.html -- 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/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: SRU Justification [Impact] The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area. Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. The problem persists in the latest drm tip. [Fix] As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue. This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs. [Test] 1. Boot up to desktop with 6.8.0-x kernels 2. Moving cursor around the desktop 3. There should be no flicker while cursor is moving [Where problems could occur] For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency. Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal. === After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
** Description changed: + SRU Justification + + [Impact] + The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area. + Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. + The problem persists in the latest drm tip. + + [Fix] + As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue. + This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs. + + [Test] + 1. Boot up to desktop with 6.8.0-x kernels + 2. Moving cursor around the desktop + 3. There should be no flicker while cursor is moving + + [Where problems could occur] + For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency. + Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal. + + === + After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 -- 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/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: SRU Justification [Impact] The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area. Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. The problem persists in the latest drm tip. [Fix] As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue. This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs. [Test] 1. Boot up to desktop with 6.8.0-x kernels 2. Moving cursor around the desktop 3. There should be no flicker while cursor is moving [Where problems could occur] For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency. Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal. === After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is:
[Kernel-packages] [Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Confirmed ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
This kernel added the SKL ID to the quirk which did the same thing as intel_iommu=igfx_off We may have to carry these quirks before Intel provides a real fix. Please give it a try and I'll submit SRU later. https://people.canonical.com/~acelan/bugs/lp2062951/ -- 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/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+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 2073538] Re: kacpi_notify high cpu on interrupt gpe17
Okay, let's if this works for you. https://people.canonical.com/~acelan/bugs/lp2073538/ I added 2 patches, one is from the upstream bug you mentioned, another one is just adding you machine info 0001-usb-typec-ucsi_acpi-Add-LG-Gram-quirk.patch 0002-usb-typec-ucsi_acpi-Add-Victus-by-HP-Gaming-Laptop-1.patch Usually, you just need to install below 3 packages linux-image-unsigned-6.8.0-43-generic_6.8.0-43.43_amd64.deb linux-modules-6.8.0-43-generic_6.8.0-43.43_amd64.deb linux-modules-extra-6.8.0-43-generic_6.8.0-43.43_amd64.deb -- 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/2073538 Title: kacpi_notify high cpu on interrupt gpe17 Status in linux package in Ubuntu: Incomplete Bug description: Picked up a HP laptop during July sales, and found the CPU soars to 80+ with kacpi_notify hitting GPE17. I would like some help finding the cause. Google searches were vague about masking the interrupt which did NOT help. If we can find what is calling the interrupts maybe we can better document a solution. top - 20:00:05 up 10 min, 1 user, load average: 86.24, 76.27, 42.44 Tasks: 453 total, 2 running, 451 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.1 us, 8.5 sy, 0.0 ni, 91.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 62040.5 total, 51595.7 free, 3166.0 used, 8146.3 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 58874.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 127 root 20 0 0 0 0 D 1.3 0.0 0:03.71 [kworker/11:1+kacpi_notify] 280 root 20 0 0 0 0 D 1.3 0.0 0:06.63 [kworker/5:5+kacpi_notify] 314 root 20 0 0 0 0 D 1.3 0.0 0:06.68 [kworker/5:12+kacpi_notify] ubuntu@ubuntu:~$ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0' /sys/firmware/acpi/interrupts/sci:1907 /sys/firmware/acpi/interrupts/gpe_all:1907 /sys/firmware/acpi/interrupts/gpe17:1907 EN enabled unmasked ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 2813 F pipewire /dev/snd/controlC1: ubuntu 2815 F wireplumber /dev/snd/controlC0: ubuntu 2815 F wireplumber /dev/snd/controlC2: ubuntu 2815 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu Jul 18 19:52:46 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: HP Victus by HP Gaming Laptop 15-fb2xxx ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2024 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8C2F dmi.board.vendor: HP dmi.board.version: 04.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 4.14 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/20/2024:br15.3:efr4.14:svnHP:pnVictusbyHPGamingLaptop15-fb2xxx:pvr:rvnHP:rn8C2F:rvr04.14:cvnHP:ct10:cvrChassisVersion:skuA14MNUA#ABA: dmi.product.family: 103C_5335M7 HP Victus dmi.product.name: Victus by HP Gaming Laptop 15-fb2xxx dmi.product.sku: A14MNUA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+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 2073538] Re: kacpi_notify high cpu on interrupt gpe17
I don't have a better idea about this, it looks like it's a h/w issue to me. The GPE17 is triggerred by EC, so I can't figure out a proper fix for this issue. The feasible workaround would be ignore it by adding below line to the kernel cmdline acpi_mask_gpe=0x17 There is no updated BIOS to address this issue, so I believe there should be a way to negotiate with the BIOS to stop the GPE17 flooding. If you want to better fix the issue, could you contact HP's customer support to see if they can shed some light on this? Thanks. ** Changed in: linux (Ubuntu) Status: In Progress => 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/2073538 Title: kacpi_notify high cpu on interrupt gpe17 Status in linux package in Ubuntu: Incomplete Bug description: Picked up a HP laptop during July sales, and found the CPU soars to 80+ with kacpi_notify hitting GPE17. I would like some help finding the cause. Google searches were vague about masking the interrupt which did NOT help. If we can find what is calling the interrupts maybe we can better document a solution. top - 20:00:05 up 10 min, 1 user, load average: 86.24, 76.27, 42.44 Tasks: 453 total, 2 running, 451 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.1 us, 8.5 sy, 0.0 ni, 91.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 62040.5 total, 51595.7 free, 3166.0 used, 8146.3 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 58874.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 127 root 20 0 0 0 0 D 1.3 0.0 0:03.71 [kworker/11:1+kacpi_notify] 280 root 20 0 0 0 0 D 1.3 0.0 0:06.63 [kworker/5:5+kacpi_notify] 314 root 20 0 0 0 0 D 1.3 0.0 0:06.68 [kworker/5:12+kacpi_notify] ubuntu@ubuntu:~$ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0' /sys/firmware/acpi/interrupts/sci:1907 /sys/firmware/acpi/interrupts/gpe_all:1907 /sys/firmware/acpi/interrupts/gpe17:1907 EN enabled unmasked ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 2813 F pipewire /dev/snd/controlC1: ubuntu 2815 F wireplumber /dev/snd/controlC0: ubuntu 2815 F wireplumber /dev/snd/controlC2: ubuntu 2815 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu Jul 18 19:52:46 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: HP Victus by HP Gaming Laptop 15-fb2xxx ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2024 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8C2F dmi.board.vendor: HP dmi.board.version: 04.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 4.14 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/20/2024:br15.3:efr4.14:svnHP:pnVictusbyHPGamingLaptop15-fb2xxx:pvr:rvnHP:rn8C2F:rvr04.14:cvnHP:ct10:cvrChassisVersion:skuA14MNUA#ABA: dmi.product.family: 103C_5335M7 HP Victus dmi.product.name: Victus by HP Gaming Laptop 15-fb2xxx dmi.product.sku: A14MNUA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+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/ListHe
[Kernel-packages] [Bug 2073538] Re: kacpi_notify high cpu on interrupt gpe17
There are some kernels need you to try 6.8.0-40 has been landed in -proposed, compares with 6.8.0-31 it includes many stable updates from 6.8.2 to 6.8.12. The issue may has been fixed by one of the updates. It the -proposed kernel doesn't help, I'm wondering if the issue has been fix by the upstream kernel, please give it a try, thanks. https://kernel.ubuntu.com/mainline/v6.11-rc1/ -- 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/2073538 Title: kacpi_notify high cpu on interrupt gpe17 Status in linux package in Ubuntu: In Progress Bug description: Picked up a HP laptop during July sales, and found the CPU soars to 80+ with kacpi_notify hitting GPE17. I would like some help finding the cause. Google searches were vague about masking the interrupt which did NOT help. If we can find what is calling the interrupts maybe we can better document a solution. top - 20:00:05 up 10 min, 1 user, load average: 86.24, 76.27, 42.44 Tasks: 453 total, 2 running, 451 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.1 us, 8.5 sy, 0.0 ni, 91.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 62040.5 total, 51595.7 free, 3166.0 used, 8146.3 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 58874.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 127 root 20 0 0 0 0 D 1.3 0.0 0:03.71 [kworker/11:1+kacpi_notify] 280 root 20 0 0 0 0 D 1.3 0.0 0:06.63 [kworker/5:5+kacpi_notify] 314 root 20 0 0 0 0 D 1.3 0.0 0:06.68 [kworker/5:12+kacpi_notify] ubuntu@ubuntu:~$ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0' /sys/firmware/acpi/interrupts/sci:1907 /sys/firmware/acpi/interrupts/gpe_all:1907 /sys/firmware/acpi/interrupts/gpe17:1907 EN enabled unmasked ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 2813 F pipewire /dev/snd/controlC1: ubuntu 2815 F wireplumber /dev/snd/controlC0: ubuntu 2815 F wireplumber /dev/snd/controlC2: ubuntu 2815 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu Jul 18 19:52:46 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: HP Victus by HP Gaming Laptop 15-fb2xxx ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2024 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8C2F dmi.board.vendor: HP dmi.board.version: 04.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 4.14 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/20/2024:br15.3:efr4.14:svnHP:pnVictusbyHPGamingLaptop15-fb2xxx:pvr:rvnHP:rn8C2F:rvr04.14:cvnHP:ct10:cvrChassisVersion:skuA14MNUA#ABA: dmi.product.family: 103C_5335M7 HP Victus dmi.product.name: Victus by HP Gaming Laptop 15-fb2xxx dmi.product.sku: A14MNUA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+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 2065128] Re: rtw89_8852ce - Lost WIFI connection after suspend
** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2065128 Title: rtw89_8852ce - Lost WIFI connection after suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Status in linux source package in Oracular: Fix Released Status in linux-oem-6.5 source package in Oracular: Invalid Bug description: [Impact] Lost WIFI connection after suspend. While this happen, the WIFI module couldn't detect any AP, re-enable module and reboot OS without any help. There only way to get it back is cold boot. [Fix] Realtek provides a fix which has been included in rtw maintainer's tree https://lore.kernel.org/linux-wireless/20240426061200.44262-1-pks...@realtek.com/T/#mbfcb37c2fdc85ba280743f2b07fbf1fa8719eb79 The commits has been included in v6.10-rc1 4e5957101d42 wifi: rtw89: 8852c: refine power sequence to imporve power consumption 535c045da60f wifi: rtw89: reset AFEDIG register in power off sequence [Test case] 1. Boot into OS 2. open terminal to keep checking dmesg or check the wifi connection from GUI 3. suspend/resume multiple times 4. check the wifi connection [Where problems could occur] What the 2 commits should be safe and won't introduce any regression. 1. Reset AFEDIG register before BB reset in power off sequence 2. Adjust power and clock parameters To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2065128/+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 2073538] Re: kacpi_notify high cpu on interrupt gpe17
Found there is one BIOS update on HP website(the relase date is 2 days later than yours) https://support.hp.com/us-en/drivers/victus-by-hp-15.6-inch-gaming-laptop-15-fb2000/2101821639 I think you could try below commands to update the BIOS 1. sudo fwupdmgr get-devices # to get updates from fwupd 2. sudo fwupdmgr update # to update to the latest firmware -- 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/2073538 Title: kacpi_notify high cpu on interrupt gpe17 Status in linux package in Ubuntu: In Progress Bug description: Picked up a HP laptop during July sales, and found the CPU soars to 80+ with kacpi_notify hitting GPE17. I would like some help finding the cause. Google searches were vague about masking the interrupt which did NOT help. If we can find what is calling the interrupts maybe we can better document a solution. top - 20:00:05 up 10 min, 1 user, load average: 86.24, 76.27, 42.44 Tasks: 453 total, 2 running, 451 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.1 us, 8.5 sy, 0.0 ni, 91.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 62040.5 total, 51595.7 free, 3166.0 used, 8146.3 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 58874.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 127 root 20 0 0 0 0 D 1.3 0.0 0:03.71 [kworker/11:1+kacpi_notify] 280 root 20 0 0 0 0 D 1.3 0.0 0:06.63 [kworker/5:5+kacpi_notify] 314 root 20 0 0 0 0 D 1.3 0.0 0:06.68 [kworker/5:12+kacpi_notify] ubuntu@ubuntu:~$ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0' /sys/firmware/acpi/interrupts/sci:1907 /sys/firmware/acpi/interrupts/gpe_all:1907 /sys/firmware/acpi/interrupts/gpe17:1907 EN enabled unmasked ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 2813 F pipewire /dev/snd/controlC1: ubuntu 2815 F wireplumber /dev/snd/controlC0: ubuntu 2815 F wireplumber /dev/snd/controlC2: ubuntu 2815 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu Jul 18 19:52:46 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: HP Victus by HP Gaming Laptop 15-fb2xxx ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2024 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8C2F dmi.board.vendor: HP dmi.board.version: 04.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 4.14 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/20/2024:br15.3:efr4.14:svnHP:pnVictusbyHPGamingLaptop15-fb2xxx:pvr:rvnHP:rn8C2F:rvr04.14:cvnHP:ct10:cvrChassisVersion:skuA14MNUA#ABA: dmi.product.family: 103C_5335M7 HP Victus dmi.product.name: Victus by HP Gaming Laptop 15-fb2xxx dmi.product.sku: A14MNUA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
Hi James, Could you provide the following result of commands 1. `sudo dmidecode --type 0` 2. `usb-devices` 3. `sudo libinput list-devices` (you probable need to install libinput-tools manually) 4. `sudo libinput debug-events` and then press the mute key Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 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.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Triaged ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: After upgrading to Ubuntu 24.04 the CPU is unable to hit lower idle states. The device is a HP Spectre x360 14 (14-ea1000) with a Tiger Lake CPU. This is a regression introduced somewhere 6.5.0-42 and 6.8.0-36. The issue is not observed when booting the same OS with 6.5.0-42. Some debug output: root@hp-spectre-x360:/sys/kernel/debug/pmc_core# cat package_cstate_show Package C2 : 36087003 Package C3 : 69314350 Package C6 : 0 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 0 $ sudo cat /sys/kernel/debug/pmc_core/substate_requirements Element |S0i2.0 |Status | pmc0:USB2PLL_OFF_STS | Required | Yes | pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | | pmc0: PCIe_Gen3PLL_OFF_STS | Required | Yes | pmc0:OPIOPLL_OFF_STS | Required | Yes | pmc0: OCPLL_OFF_STS | Required | Yes | pmc0:MIPIPLL_OFF_STS | Required | Yes | pmc0:AC_Ring_Osc_OFF_STS | Required | Yes | pmc0:SATAPLL_OFF_STS | Required | Yes | pmc0:CSME_PG_STS | Required | Yes | pmc0:SATA_PG_STS | Required | Yes | pmc0:xHCI_PG_STS | Required | Yes | pmc0: UFSX2_PG_STS | Required | Yes | pmc0: OTG_PG_STS | Required | Yes | pmc0: SPA_PG_STS | Required | Yes | pmc0: SPB_PG_STS | Required | Yes | pmc0: SPC_PG_STS | Required | | pmc0:THC0_PG_STS | Required | Yes | pmc0:THC1_PG_STS | Required | Yes | pmc0: GBETSN_PG_STS | Required | Yes | pmc0: GBE_PG_STS | Required | Yes | pmc0:LPSS_PG_STS | Required | Yes | pmc0: xHCI0_D3_STS | Required | Yes | pmc0: xDCI1_D3_STS | Required | Yes | pmc0: IS_D3_STS | Required | Yes | pmc0: GBE_TSN_D3_STS | Required | Yes | pmc0: CPU_C10_REQ_STS_0 | Required | Yes | pmc0:MPHY_Core_DL_REQ_STS_16 | Required | | pmc0: Break-even_En_REQ_STS_17 | Required | Yes | pmc0:Auto-demo_En_REQ_STS_18 | Required | Yes | pmc0: Int_Timer_SS_Wake0_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake1_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake2_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake3_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake4_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake5_Pol_STS | Required | | On 6.5: pmc0:MPHY_Core_DL_REQ_STS_16 | Required | | pmc0: SPC_PG_STS | Required | | pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | | have status set to 'Yes' ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-38-generic 6.8.0-38.38 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:kstoilov 2634 F pipewire /dev/snd/controlC0: kstoilov 2634 F pipewire kstoilov 2641 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 10 21:26:37 2024 InstallationDate: Installed on 2023-05-04 (433 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP Spectre x360 Convertible 14-ea1xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-38-generic N/A linux-backports-modules-6.8.0-38-generic N/A linux-firmware20
[Kernel-packages] [Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
Here is the test kernel with the mentioned 2 patches, please remember to disable the secure boot from the BIOS. https://people.canonical.com/~acelan/bugs/lp2072679/ -- 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/2072679 Title: Regression: unable to reach low idle states on Tiger Lake Status in linux package in Ubuntu: Triaged Bug description: After upgrading to Ubuntu 24.04 the CPU is unable to hit lower idle states. The device is a HP Spectre x360 14 (14-ea1000) with a Tiger Lake CPU. This is a regression introduced somewhere 6.5.0-42 and 6.8.0-36. The issue is not observed when booting the same OS with 6.5.0-42. Some debug output: root@hp-spectre-x360:/sys/kernel/debug/pmc_core# cat package_cstate_show Package C2 : 36087003 Package C3 : 69314350 Package C6 : 0 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 0 $ sudo cat /sys/kernel/debug/pmc_core/substate_requirements Element |S0i2.0 |Status | pmc0:USB2PLL_OFF_STS | Required | Yes | pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | | pmc0: PCIe_Gen3PLL_OFF_STS | Required | Yes | pmc0:OPIOPLL_OFF_STS | Required | Yes | pmc0: OCPLL_OFF_STS | Required | Yes | pmc0:MIPIPLL_OFF_STS | Required | Yes | pmc0:AC_Ring_Osc_OFF_STS | Required | Yes | pmc0:SATAPLL_OFF_STS | Required | Yes | pmc0:CSME_PG_STS | Required | Yes | pmc0:SATA_PG_STS | Required | Yes | pmc0:xHCI_PG_STS | Required | Yes | pmc0: UFSX2_PG_STS | Required | Yes | pmc0: OTG_PG_STS | Required | Yes | pmc0: SPA_PG_STS | Required | Yes | pmc0: SPB_PG_STS | Required | Yes | pmc0: SPC_PG_STS | Required | | pmc0:THC0_PG_STS | Required | Yes | pmc0:THC1_PG_STS | Required | Yes | pmc0: GBETSN_PG_STS | Required | Yes | pmc0: GBE_PG_STS | Required | Yes | pmc0:LPSS_PG_STS | Required | Yes | pmc0: xHCI0_D3_STS | Required | Yes | pmc0: xDCI1_D3_STS | Required | Yes | pmc0: IS_D3_STS | Required | Yes | pmc0: GBE_TSN_D3_STS | Required | Yes | pmc0: CPU_C10_REQ_STS_0 | Required | Yes | pmc0:MPHY_Core_DL_REQ_STS_16 | Required | | pmc0: Break-even_En_REQ_STS_17 | Required | Yes | pmc0:Auto-demo_En_REQ_STS_18 | Required | Yes | pmc0: Int_Timer_SS_Wake0_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake1_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake2_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake3_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake4_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake5_Pol_STS | Required | | On 6.5: pmc0:MPHY_Core_DL_REQ_STS_16 | Required | | pmc0: SPC_PG_STS | Required | | pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | | have status set to 'Yes' ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-38-generic 6.8.0-38.38 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:kstoilov 2634 F pipewire /dev/snd/controlC0: kstoilov 2634 F pipewire kstoilov 2641 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 10 21:26:37 2024 InstallationDate: Installed on 2023-05-04 (433 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP Spectre x360 Convertible 14-ea1xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-38-generic N/A linux-backports-modules-6.8.0-38-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-07-07 (3 days ago) dmi.bios.date: 04/03/2024 dmi.bios.release: 15.33 dmi.bios.vendor: AMI dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 89DB dmi.board.vendor: HP dmi.board.version: 40.65 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.fir
[Kernel-packages] [Bug 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card
@Jess, Does the "iwlwifi :e4:00.0: WRT: Invalid buffer destination" error affect the wifi stability? Could you provde a dmesg log after you upgraded to 24.04? BTW, could you also check your wifi AP(router), try rebooting it or check if there is a new firmware for it, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060748 Title: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card Status in linux package in Ubuntu: New Bug description: I just installed Kubuntu 23.10 (using latest default kernel) on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth card. Here is output from lspci -v: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi Wifi error popping up every few minutes in Kubuntu I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi card: Code: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi The internet seems to be somewhat working, but at least once a minute I have two "Network Management" error notifications that pop up in KDE that say "Connection Wired Connection 3 deactivated" and "Wired Interface e2x52e8ae7d39d1: IP configuration was unavailable". I checked the logs in /var/log/dmesg and saw that there were a ton of iwlwifi error messages in there that look like this: [ 44.926474] kernel: Intel(R) Wireless WiFi driver for Linux [ 44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002) [ 44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x8000 [ 44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than supported by driver [ 44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 [ 44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm [ 44.955070] kernel: Bluetooth: Core ver 2.22 [ 44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family [ 44.955090] kernel: Bluetooth: HCI device and connection manager initialized [ 44.955095] kernel: Bluetooth: HCI socket layer initialized [ 44.955097] kernel: Bluetooth: L2CAP socket layer initialized [ 44.955101] kernel: Bluetooth: SCO socket layer initialized [ 45.275827] kernel: Bluetooth: hci0: Device revision is 0 [ 45.275833] kernel: Bluetooth: hci0: Secure boot is enabled [ 45.275836] kernel: Bluetooth: hci0: OTP lock is enabled [ 45.275838] kernel: Bluetooth: hci0: API lock is enabled [ 45.275840] kernel: Bluetooth: hci0: Debug lock is disabled [ 45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 45.278400] kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi [ 45.278415] kernel: Bluetooth: hci0: Boot Address: 0x100800 [ 45.278416] kernel: Bluetooth: hci0: Firmware Version: 254-28.23 [ 47.405919] kernel: iwlwifi :e4:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20 [ 47.405936] kernel: iwlwifi :e4:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 47.405945] kernel: iwlwifi :e4:00.0: WFPM_AUTH_KEY_0: 0x90 [ 47.405955] kernel: iw
[Kernel-packages] [Bug 2060193] Re: iwlwifi microcode crash when using wrong password to join a WPA3 access point
This is not a driver failure, it's the microcode in the iwlwifi firmware. As the issue no longer be reproducible by the bug reporter, Pauli, I'm going to close this bug. @QkiZ, It's interesting that the issue could be fixed by the newer kernel, I'd treat that as another issue. If you want to help us to find the root cause, plase file a new bug and we may need your help to see between which kernels the issue is gone. Thanks. ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid -- 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/2060193 Title: iwlwifi microcode crash when using wrong password to join a WPA3 access point Status in linux-firmware package in Ubuntu: Invalid Bug description: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B
[Kernel-packages] [Bug 2060193] Re: iwlwifi microcode crash when using wrong password to join a WPA3 access point
This kind of iwlwifi microcode crashes usually results from the router(Access Point). Have you tried to cold reboot your AP? >From other discussion I found on the net, the issue might be related to 40MHz >channel, you probably could try the below setting. options cfg80211 cfg80211_disable_40mhz_24ghz=Y -- 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/2060193 Title: iwlwifi microcode crash when using wrong password to join a WPA3 access point Status in linux-firmware package in Ubuntu: Confirmed Bug description: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel Apr 3 22:13:57 waplinuc kernel: [1158487.457015] iwlwifi :00:14.3: 0x | timestamp Apr 3 22:13:57 waplinuc kernel: [1158487.457016] iwlwifi :00:14.3: 0x88
[Kernel-packages] [Bug 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card
@Jess, Yes, that would be helpful if you can help to collect the dynamic debug log by the trace-cmd. There is no update for the iwlwifi firmware(-83) you are using now, but it might worth of trying to upgrade the firmware version to -84. You can download the latest firmware from the linux-firmware git tree[1], but please remember that only copy the files you need. That help us to narrow down the required firmware. In this case you probably only need iwlwifi-ty-a0-gf-a0-84.ucode, you can check your boot dmesg to see which firmware is loaded. You can upload the boot dmesg here if you are not sure which firmware you are using. 1. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/ -- 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/2060748 Title: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card Status in linux package in Ubuntu: New Bug description: I just installed Kubuntu 23.10 (using latest default kernel) on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth card. Here is output from lspci -v: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi Wifi error popping up every few minutes in Kubuntu I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi card: Code: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi The internet seems to be somewhat working, but at least once a minute I have two "Network Management" error notifications that pop up in KDE that say "Connection Wired Connection 3 deactivated" and "Wired Interface e2x52e8ae7d39d1: IP configuration was unavailable". I checked the logs in /var/log/dmesg and saw that there were a ton of iwlwifi error messages in there that look like this: [ 44.926474] kernel: Intel(R) Wireless WiFi driver for Linux [ 44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002) [ 44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x8000 [ 44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than supported by driver [ 44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 [ 44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm [ 44.955070] kernel: Bluetooth: Core ver 2.22 [ 44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family [ 44.955090] kernel: Bluetooth: HCI device and connection manager initialized [ 44.955095] kernel: Bluetooth: HCI socket layer initialized [ 44.955097] kernel: Bluetooth: L2CAP socket layer initialized [ 44.955101] kernel: Bluetooth: SCO socket layer initialized [ 45.275827] kernel: Bluetooth: hci0: Device revision is 0 [ 45.275833] kernel: Bluetooth: hci0: Secure boot is enabled [ 45.275836] kernel: Bluetooth: hci0: OTP lock is enabled [ 45.275838] kernel: Bluetooth: hci0: API lock is enabled [ 45.275840] kernel: Bluetooth: hci0: Debug lock is disabled [ 45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 45.278400] kernel: Bluetooth: hci0:
[Kernel-packages] [Bug 2046225] Re: The eDP OLED panel has no output on MTL platform
Mantic(6.5.0-27.28) got the fix through upstream stable update. ** Description changed: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 Which is in drm-intel-next currently 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing + which is included in v6.7-rc6 + e6861d8264cd drm/i915/edp: don't write to DP_LINK_BW_SET when using rate select + [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 Which is in drm-intel-next currently 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing which is included in v6.7-rc6 e6861d8264cd drm/i915/edp: don't write to DP_LINK_BW_SET when using rate select [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+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 2045205] Re: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen
The 2 commits are included in v6.8-rc1, and it won't impact any functionalities, so won't fix for old releases. 7a030abc0185 mtd: spi-nor: Stop reporting warning message when soft reset is not suported cff49d58f57e spi: Unify error codes by replacing -ENOTSUPP with -EOPNOTSUPP ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045205 Title: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] There is a spi error message on the screen when shutting down the machine. It won't hurt anything and all device work well in the next boot up. Intel SPI controller doesn't support reset command, but our customer feel bad about this message. [Fix] Distinguish the error code -EOPNOTSUPP from -ENOTSUPP, and not showing the warnning when it's op not supported. https://lkml.org/lkml/2023/11/29/62 [Test case] 1. boot up the system with intel SPI controller on it 2. power off the system and check if there are spi software reset failed errors on the screen. [Where problems could occur] There is a minor risk of breaking user-space applications that rely on specific return codes for unsupported operations. However, this risk is considered low, as such use-cases are unlikely to be common or critical. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045205/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Description changed:
SRU Justification for Noble
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
The new series of the fix has been merged into v6.9
6d4266675279 PCI/ASPM: Update save_state when configuration changes
64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates
c198fafa0125 PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state()
17423360a27a PCI/ASPM: Save L1 PM Substates Capability for suspend/resume
1e11b5494c3d PCI/ASPM: Move pci_save_ltr_state() to aspm.c
f3994bba8200 PCI/ASPM: Always build aspm.c
fa84f4435a62 PCI/ASPM: Move pci_configure_ltr() to aspm.c
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[Where the problems could occur]
+ Hard to evaluate, these patches change the PCI/ASPM behavior and may lead to
PCI devices work abnormal.
=
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux-oem-6.8 source package in Jammy:
Invalid
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux-oem-6.8 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Status in linux-oem-6.8 source package in Noble:
In Progress
Bug description:
SRU Justification for Noble
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
The new series of the fix has been merged into v6.9
6d4266675279 PCI/ASPM: Update save_state when configuration changes
64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates
c198fafa0125
[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
** Description changed: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.8-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform + + To avoid conflict pull in one more quirk from v6.8-rc3 + fcfc9f711d1e ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. + The other commit add one more ID to the table and disable speaker passthrough. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.8-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform To avoid conflict pull in one more quirk from v6.8-rc3 fcfc9f711d1e ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. The other commit add one more ID to the table and disable speaker passthrough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
** Description changed: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] - The commit from v6.5-rc5 fixes the issue + The commit from v6.8-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.8-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
The formal firmware names are ibt-0291-0291.{ddc,sfi} which are incuded
in Jammy and Mantic release.
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Incomplete => Fix Released
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Incomplete => Fix Released
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2033455
Title:
Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.5 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.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2033455
[Impact]
Missing BT IDs for support for Intel Discrete Misty Peak2/BE202.
[Fix]
Bluetooth:
a. kernel driver:
-
https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t
- Also depends on patches for Gale Peak(BE200) from bug 2028065.
b. firmware (shared with Gale Peak, to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
[Test Case]
To boot with patched kernel and prereleased firmware blob and check
basic Bluetooth functions.
[Where problems could occur]
New device. Expect incomplete functions and bugs.
[Other Info]
Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2033455/+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 2049184] Re: iwlwifi leads to system randomly hangs after suspend
The fix is included in 5.15.0-104.114 * Jammy update: v5.15.149 upstream stable release (LP: #2059014) 6.5.0-32.32 * Mantic update: upstream stable patchset 2024-03-26 (LP: #2059068) ** Description changed: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ + Which has been included in v6.8-rc2 + cf4a0d840ecc wifi: iwlwifi: fix a memory corruption + [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ Which has been included in v6.8-rc2 cf4a0d840ecc wifi: iwlwifi: fix a memory corruption [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Description changed:
+ SRU Justification for Noble
+
+ [Impact]
+ checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
+
+ [Fix]
+ The new series of the fix has been merged into v6.9
+
+ 6d4266675279 PCI/ASPM: Update save_state when configuration changes
+ 64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates
+ c198fafa0125 PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state()
+ 17423360a27a PCI/ASPM: Save L1 PM Substates Capability for suspend/resume
+ 1e11b5494c3d PCI/ASPM: Move pci_save_ltr_state() to aspm.c
+ f3994bba8200 PCI/ASPM: Always build aspm.c
+ fa84f4435a62 PCI/ASPM: Move pci_configure_ltr() to aspm.c
+
+ [Test Case]
+ 1. suspend and resume.
+ 2. check if the error appears in dmesg
+ ~~~
+ pcieport :00:1c.0: pciehp: Slot(5): Card not present
+ rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
+ rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
+ ~~~
+
+ [Where the problems could occur]
+
+ =
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
-
+
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
-
+
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
-
+
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
-do that after PCIe capability is restored in pci_restore_aspm_state()
-following PCIe r6.0, sec 5.5.4.
-
+ do that after PCIe capability is restored in pci_restore_aspm_state()
+ following PCIe r6.0, sec 5.5.4.
+
2) ASPM is first enabled on the upstream component and then downstream
-(this is already forced by the parent-child ordering of Linux
-Device Power Management framework).
-
+ (this is already forced by the parent-child ordering of Linux
+ Device Power Management framework).
+
3) Program ASPM L1 PM substate configuration before L1 enables.
-
+
4) Program ASPM L1 PM substate enables last after rest of the fields
-in the capability are programmed.
-
+ in the capability are programmed.
+
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
-where these regressions happened, just in case. For the TUXEDO case
-we only skip restore if the BIOS is involved in system suspend
-(that's forcing "mem_sleep=deep" in the command line). This is to
-avoid possible power regression when the default suspend to idle is
-used, and at the same time make sure the devices continue working
-after resume when the BIOS is involved.
+ where these regressions happened, just in case. For the TUXEDO case
+ we only skip restore if the BIOS is involved in system suspend
+ (that's forcing "mem_sleep=deep" in the command line). This is to
+ avoid possible power regression when the default suspend to idle is
+ used, and at the same time make sure the devices continue working
+ after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
- pcieport :00:1c.0: pciehp: Slot(5): Card not present
- rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
- rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
+ pcieport :00:1c.0: pciehp: Slot(5): Card not present
+ rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
+ rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux-oem-6.
[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux-oem-6.8 source package in Jammy:
Invalid
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux-oem-6.8 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Status in linux-oem-6.8 source package in Noble:
In Progress
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2057484] Re: kernel worker event freezes during traffic on iwlwifi
*** This bug is a duplicate of bug 2058808 *** https://bugs.launchpad.net/bugs/2058808 A fix has been submitted, please check bug 2058808 ** This bug has been marked a duplicate of bug 2058808 iwlwifi disconnect and crash - intel wifi7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057484 Title: kernel worker event freezes during traffic on iwlwifi Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: With traffic on Intel Wifi 7 BE200 card, For a while kernel enter 100% cpu usage on a worker event thread and kworker/0:0-events_freezable is in D state. System highly unresponsive during this time. Happens in 6.5.0-25, does not happen in 6.5.0-17 Description:Ubuntu 22.04.4 LTS Release:22.04 Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status linux-modules-6.5.0-25-generic: Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status filename: /lib/modules/6.5.0-25-generic/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko license:GPL description:Intel(R) Wireless WiFi driver for Linux firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode firmware: iwlwifi-2030-6.ucode firmware: iwlwifi-2000-6.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-5.ucode firmware: iwlwifi-6000g2b-6.ucode firmware: iwlwifi-6000g2a-6.ucode firmware: iwlwifi-6050-5.ucode firmware: iwlwifi-6000-6.ucode firmware: iwlwifi-7265D-29.ucode firmware: iwlwifi-7265-17.ucode firmware: iwlwifi-3168-29.ucode firmware: iwlwifi-3160-17.ucode firmware: iwlwifi-7260-17.ucode firmware: iwlwifi-8265-36.ucode firmware: iwlwifi-8000C-36.ucode firmware: iwlwifi-9260-th-b0-jf-b0-46.ucode firmware: iwlwifi-9000-pu-b0-jf-b0-46.ucode firmware: iwlwifi-cc-a0-77.ucode firmware: iwlwifi-QuZ-a0-jf-b0-77.ucode firmware: iwlwifi-QuZ-a0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-jf-b0-77.ucode firmware: iwlwifi-Qu-c0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-hr-b0-77.ucode firmware: iwlwifi-ma-b0-mr-a0-83.ucode firmware: iwlwifi-ma-b0-gf4-a0-83.ucode firmware: iwlwifi-ma-b0-gf-a0-83.ucode firmware: iwlwifi-ma-b0-hr-b0-83.ucode firmware: iwlwifi-ma-a0-mr-a0-83.ucode firmware: iwlwifi-ma-a0-gf4-a0-83.ucode firmware: iwlwifi-ma-a0-gf-a0-83.ucode firmware: iwlwifi-ma-a0-hr-b0-83.ucode firmware: iwlwifi-ty-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-hr-b0-83.ucode firmware: iwlwifi-so-a0-jf-b0-83.ucode firmware: iwlwifi-gl-c0-fm-c0-83.ucode firmware: iwlwifi-gl-b0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-fm4-b0-83.ucode firmware: iwlwifi-bz-a0-fm-c0-83.ucode firmware: iwlwifi-bz-a0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-gf4-a0-83.ucode firmware: iwlwifi-bz-a0-gf-a0-83.ucode firmware: iwlwifi-bz-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-wh-a0-83.ucode firmware: iwlwifi-sc-a0-gf4-a0-83.ucode firmware: iwlwifi-sc-a0-gf-a0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-fm-c0-83.ucode firmware: iwlwifi-sc-a0-fm-b0-83.ucode srcversion: CE34BB7E0E287E10FEC1E13 alias: pci:v8086dE440sv*sd*bc*sc*i* alias: pci:v8086d7740sv*sd*bc*sc*i* alias: pci:v8086dA840sv*sd*bc*sc*i* alias: pci:v8086d272Bsv*sd*bc*sc*i* alias: pci:v8086d2727sv*sd*bc*sc*i* alias: pci:v8086d7E40sv*sd*bc*sc*i* alias: pci:v8086d2729sv*sd*bc*sc*i* alias: pci:v8086d7F70sv*sd*bc*sc*i* alias: pci:v8086d54F0sv*sd*bc*sc*i* alias: pci:v8086d51F1sv*sd*bc*sc*i* alias: pci:v8086d51F1sv*sd*bc*sc*i* alias: pci:v8086d51F0sv*sd*bc*sc*i* alias: pci:v8086d7AF0sv*sd*bc*sc*i* alias: pci:v8086d7A70sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7
I feel like this commit may fix the issue which is included in 6.5.0-27.28. commit edb960c5f95228109dd8fd8056d0d28579daad7d Author: Avraham Stern Date: Thu Dec 7 04:50:17 2023 +0200 wifi: iwlwifi: pcie: avoid a NULL pointer dereference BugLink: https://bugs.launchpad.net/bugs/2055199 [ Upstream commit ce038edfce43fb345f8dfdca0f7b17f535896701 ] It possible that while the rx rb is being handled, the transport has been stopped and re-started. In this case the tx queue pointer is not yet initialized, which will lead to a NULL pointer dereference. Fix it. Signed-off-by: Avraham Stern Signed-off-by: Miri Korenblit Link: https://msgid.link/20231207044813.cd0898cafd89.I0b84daae753ba9612092bf383f5c6f761446e964@changeid Signed-off-by: Johannes Berg Signed-off-by: Sasha Levin Signed-off-by: Manuel Diewald Signed-off-by: Stefan Bader -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058808 Title: iwlwifi disconnect and crash - intel wifi7 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: iwlwifi disconnecting and crashing when I using Wifi 2.4GHz. [ cut here ] Invalid rxb from HW 0 WARNING: CPU: 14 PID: 896 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc rapl nvidia_uvm(PO) nfnetlink binfmt_misc n xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW OE 6.5.0-26-generic #26~22.04.1-Ubuntu Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023 RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9 RSP: 0018:b91d803e0e18 EFLAGS: 00010246 RAX: RBX: 956747353c30 RCX: RDX: RSI: RDI: RBP: b91d803e0e78 R08: R09: R10: R11: R12: 1007 R13: 0015 R14: R15: 956746a30028 FS: () GS:95768f38() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? free_unref_page+0x30/0x180 iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi] ? skb_free_head+0xa8/0xd0 __napi_poll+0x30/0x1f0 net_rx_action+0x181/0x2e0 ? __irq_wake_thread+0x42/0x50 __do_softirq+0xd9/0x349 ? __pfx_irq_thread_fn+0x10/0x10 do_softirq.part.0+0x41/0x80 __local_bh_enable_ip+0x72/0x80 iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi] irq_thread_fn+0x21/0x70 irq_thread+0xf8/0x1c0 ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 ---[ end trace ]--- iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0. iwlwifi :05:00.0: Start IWL Error Log Dump: iwlwifi :05:00.0: Transport status: 0x004A, valid: 6 iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN iwlwifi :05:00.0: 0x0003 | trm_hw_status0 iwlwifi :05:00.0: 0x | trm_hw_status1 iwlwifi :05:00.0: 0x002C280A | branchlink2 iwlwifi :05:00.0: 0x9328 | interruptlink1 iwlwifi :05:00.0: 0x9328 | interruptlink2 iwlwifi :05:00.0: 0xF46C | data1 iwlwifi :05:00.0: 0x0100 | data2 iwlwifi :05:00.0: 0x | data3 iwlwifi :05:00.0: 0xA0005E44
[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] No modems were found sometimtes after reboot/poweroff Got below messages when it fails [ 1.294786] mtk_t7xx :05:00.0: enabling device ( -> 0002) [ 1.298085] mtk_t7xx :05:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 1.298108] mtk_t7xx :05:00.0: device [14c3:4d75] error status/mask=0010/0040 [ 1.298123] mtk_t7xx :05:00.0: [20] UnsupReq (First) [ 1.298136] mtk_t7xx :05:00.0: AER: TLP Header: 4001 000f 88824030 3e800100 [ 1.298460] mtk_t7xx :05:00.0: AER: can't recover (no error_detected callback) [ 3.302402] mtk_t7xx :05:00.0: Invalid device status 0x1 [Fix] Fibocom provides a fix for this issue which is included in linux-next now https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ 2dac6381c3da net: wwan: t7xx: Add fastboot WWAN port d27553c14f06 net: wwan: t7xx: Infrastructure for early port configuration 409c38d4f156 net: wwan: t7xx: Add sysfs attribute for device state machine e3caf184107a wwan: core: Add WWAN fastboot port type [Test Case] 1. Boot to OS. 2. Insert sim card to the system. 3. Check the gnome-settings with WWAN settings or check with command mmcli -L 4. Repeat 1, 2, 3 multiple times and make sure WWAN always exists and works well [Where problems could occur] Hard to tell, but ODM and us did some tests and confirmed the WWAN doesn't keep working during 1900 reboot stress test. = At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013in
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] The first commit introduces no functional changes, it merely relocates the delay flag to dc_debug_options and makes some consequent modifications. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+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 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
** Tags added: oem-priority originate-from-2049877 somerville -- 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Mantic: New Bug description: Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Description changed: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] - It's just add 2 panel IDs to the quirk, should be pretty safe to include them. + The first commit should not introduce any function changes, just move the delay flag to dc_debug_options and do some consenquence modification. + The second commit introduce a new flag, but we don't use it. + The third and forth commits add 4 panel IDs which should be pretty safe to include them. ** Description changed: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] - The first commit should not introduce any function changes, just move the delay flag to dc_debug_options and do some consenquence modification. + The first commit doesn't introduce any functional changes, just move the delay flag to dc_debug_options and do some consenquence modification. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. ** Description changed: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] - The first commit doesn't introduce any functional changes, just move the delay flag to dc_debug_options and do some consenquence modification. + The first commit introduces no functional changes, it merely relocates the delay flag to dc_debug_options and makes some consequent modifications. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] The first commit introduc
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Description changed: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP - To avoid conflicts, pull in another panel quirk + To avoid conflicts, pull in 3 other small patches + c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs + 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+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 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Description changed: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP + + To avoid conflicts, pull in another panel quirk + 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Tags added: oem-priority originate-from-2054427 somerville -- 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/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in another panel quirk 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+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 2057430] [NEW] The screen brightness is unable to adjust on BOE panel DPN#R6FD8
Public bug reported: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in another panel quirk 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) 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/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in another panel quirk 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057430/+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 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
** Description changed: [Impact] No modems were found sometimtes after reboot/poweroff Got below messages when it fails [ 1.294786] mtk_t7xx :05:00.0: enabling device ( -> 0002) [ 1.298085] mtk_t7xx :05:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 1.298108] mtk_t7xx :05:00.0: device [14c3:4d75] error status/mask=0010/0040 [ 1.298123] mtk_t7xx :05:00.0: [20] UnsupReq (First) [ 1.298136] mtk_t7xx :05:00.0: AER: TLP Header: 4001 000f 88824030 3e800100 [ 1.298460] mtk_t7xx :05:00.0: AER: can't recover (no error_detected callback) [ 3.302402] mtk_t7xx :05:00.0: Invalid device status 0x1 [Fix] Fibocom provides a fix for this issue which is included in linux-next now https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ + 2dac6381c3da net: wwan: t7xx: Add fastboot WWAN port + d27553c14f06 net: wwan: t7xx: Infrastructure for early port configuration + 409c38d4f156 net: wwan: t7xx: Add sysfs attribute for device state machine + e3caf184107a wwan: core: Add WWAN fastboot port type + [Test Case] 1. Boot to OS. 2. Insert sim card to the system. 3. Check the gnome-settings with WWAN settings or check with command mmcli -L 4. Repeat 1, 2, 3 multiple times and make sure WWAN always exists and works well [Where problems could occur] + Hard to tell, but ODM and us did some tests and confirmed the WWAN doesn't keep working during 1900 reboot stress test. = At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source
[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
** Description changed: + [Impact] + No modems were found sometimtes after reboot/poweroff + Got below messages when it fails + + [ 1.294786] mtk_t7xx :05:00.0: enabling device ( -> 0002) + [ 1.298085] mtk_t7xx :05:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) + [ 1.298108] mtk_t7xx :05:00.0: device [14c3:4d75] error status/mask=0010/0040 + [ 1.298123] mtk_t7xx :05:00.0: [20] UnsupReq (First) + [ 1.298136] mtk_t7xx :05:00.0: AER: TLP Header: 4001 000f 88824030 3e800100 + [ 1.298460] mtk_t7xx :05:00.0: AER: can't recover (no error_detected callback) + [ 3.302402] mtk_t7xx :05:00.0: Invalid device status 0x1 + + [Fix] + Fibocom provides a fix for this issue which is included in linux-next now + https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ + + [Test Case] + 1. Boot to OS. + 2. Insert sim card to the system. + 3. Check the gnome-settings with WWAN settings or check with command mmcli -L + 4. Repeat 1, 2, 3 multiple times and make sure WWAN always exists and works well + + [Where problems could occur] + + = At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1157 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-stella-jammy-amd64-20231228-670 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-6.5.0-3011-oem N/A - linux-backports-modules-6.5.0-3011-oem N/A - linux-firmware 20220329.git681281e4-0ubuntu3.24 + linux-restricted-modules-6.5.0-3011-oem N/A + linux-backports-modules-6.5.0-3011-oem N/A + linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status i
[Kernel-packages] [Bug 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ v9 has been accepted. ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x
[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Noble will include this commit soon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Noble will include this commit soon ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Tags added: oem-priority originate-from-2054365 somerville -- 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/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Noble will include this commit soon ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2054487] [NEW] There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Public bug reported: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Fix Released ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Fix Released ** Affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2054365 somerville ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) 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-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) 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/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2051334] Re: There is sound from the speakers and headphones at the same time on one dell platform
** Tags removed: verification-needed-jammy-linux-oem-6.1 verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051334 Title: There is sound from the speakers and headphones at the same time on one dell platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] After headphone is plugged, the sound plays from both headphone and speaker. [Fix] Cirrus provides a fix for this issue and currently, the patch is in sound subsystem tree https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=fcfc9f711d1e2fc7876ac12b1b16c509404b9625 [Verify] Plugin headphone and play sounds, the sound should be from headphone only. [Where problems could occur] The fix is only for 2 specific models, and has been verfied. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051334/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-oem-6.5 verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
The patch seems be accepted and will be merged to v6.9.
We'll skip this fix on Mantic as the patchset grouth and affects all PCI
devices, and will try backporting it to Noble kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
New series of the patches https://patchwork.kernel.org/project/linux-
pci/cover/20240128233212.1139663-1-david.e@linux.intel.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
Jammy included this fix from stable update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
** Description changed: [Impact] + The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] + Mario points out the commit in 6.7 may help + 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] + 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. + 2. Boot OS, put SUT to suspend. + 3. Wake up the System from suspend. + 4. Right away reboot the system from Ubuntu OS. + 5. Put SUT to suspend and wake up the system. + 6. After wake up Suspend, SUT should not be black screen. + 7. Repetition Step 2~6 30 cycles [Where problems could occur] + Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051341] [NEW] black screen when wake up from s3 with AMD W7600 gfx
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2051251 somerville ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-2051251 somerville -- 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/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051334] [NEW] There is sound from the speakers and headphones at the same time on one dell platform
Public bug reported: [Impact] After headphone is plugged, the sound plays from both headphone and speaker. [Fix] Cirrus provides a fix for this issue and currently, the patch is in sound subsystem tree https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=fcfc9f711d1e2fc7876ac12b1b16c509404b9625 [Verify] Plugin headphone and play sounds, the sound should be from headphone only. [Where problems could occur] The fix is only for 2 specific models, and has been verfied. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2049724 somerville ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) 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-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Tags added: oem-priority originate-from-2049724 somerville ** Description changed: [Impact] + After headphone is plugged, the sound plays from both headphone and speaker. [Fix] + Cirrus provides a fix for this issue and currently, the patch is in sound subsystem tree + https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=fcfc9f711d1e2fc7876ac12b1b16c509404b9625 [Verify] + Plugin headphone and play sounds, the sound should be from headphone only. [Where problems could occur] + The fix only for 2 specific models, and has been verfied. ** Description changed: [Impact] After headphone is plugged, the sound plays from both headphone and speaker. [Fix] Cirrus provides a fix for this issue and currently, the patch is in sound subsystem tree https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=fcfc9f711d1e2fc7876ac12b1b16c509404b9625 [Verify] Plugin headphone and play sounds, the sound should be from headphone only. [Whe
[Kernel-packages] [Bug 2051333] [NEW] There is sound from the speakers and headphones at the same time on one dell platform
Public bug reported: [Impact] [Fix] [Verify] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051333 Title: There is sound from the speakers and headphones at the same time on one dell platform Status in linux package in Ubuntu: New Bug description: [Impact] [Fix] [Verify] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051333/+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 2047184] Re: Audio device is not available, instead it shows dummy output in the settings
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047184 Title: Audio device is not available, instead it shows dummy output in the settings Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Audio device is not available, instead it shows dummy output in the settings [Fix] SOF driver looks for a config which both sample width and valid bits are both 32 bits. However, the config in NHLT table is 32-bit sample width and 24-bit valid bits. Should ignore the valid bits in NHLT when the sample width is 32 bits. Confirmed the below commit in v6.7-rc4 fix the issue 7b4c93a50a2e ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format [Test case] 1. check audio input/output on the system 2. System can play and record audio normally [Where problems could occur] When the samples assumed to be vbps=32 then the 'noise' introduced by the lower two bits (channel number) have no real life implication on audio quality. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047184/+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 2047398] Re: Add missing RPL P/U CPU IDs
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-oem-6.5 verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+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 2047461] Re: drm: Update file owner during use
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-oem-6.5 verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+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 2049184] Re: iwlwifi leads to system randomly hangs after suspend
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: ... * 6835 MHz [177] (disabled) * 6855 MHz [181] (disabled) * 6875 MHz [185] (disabled) * 6895 MHz [189] (disabled) * 6915 MHz [193] (disabled) * 6935 MHz [197] (disabled) * 6955 MHz [201] (disabled) * 6975 MHz [205] (disabled) * 6995 MHz [209] (disabled) * 7015 MHz [213] (disabled) * 7035 MHz [217] (disabled) * 7055 MHz [221] (disabled) * 7075 MHz [225] (disabled) * 7095 MHz [229] (disabled) * 7115 MHz [233] (disabled) [Where problems could occur] Should have some impact to current RTL devices, but didn't see any fix patches for the 3 commits now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+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 2049184] Re: iwlwifi leads to system randomly hangs after suspend
** Description changed: [Impact] + The system randomly hangs while doing s2idle test. [Fix] + Intel found the issue and provided a fix. + https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ [Test case] + Boot up the system and run the s2idle test around 1000 times + sudo fwts s3 --s3-multiple=1000 [Where problems could occur] + The fix is trivial and should no introduce any issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The system randomly hangs while doing s2idle test. [Fix] Intel found the issue and provided a fix. https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/ [Test case] Boot up the system and run the s2idle test around 1000 times sudo fwts s3 --s3-multiple=1000 [Where problems could occur] The fix is trivial and should no introduce any issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+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 2049184] [NEW] iwlwifi leads to system randomly hangs after suspend
Public bug reported: [Impact] [Fix] [Test case] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2033497 somerville ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Tags added: oem-priority originate-from-2033497 somerville -- 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/2049184 Title: iwlwifi leads to system randomly hangs after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049184/+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 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
The final discuss and version are here
https://bugzilla.kernel.org/show_bug.cgi?id=216877
https://patchwork.kernel.org/project/linux-pci/patch/20231221011250.191599-1-david.e@linux.intel.com/
And koba has backported the old version of that commit to oem kernel
commit 16e5386dabd18bd9c507867b0df6c414783af4a8
Author: Mika Westerberg
Date: Mon Oct 2 10:00:44 2023 +0300
UBUNTU: SAUCE: PCI/ASPM: Add back L1 PM Substate save and restore
BugLink: https://bugs.launchpad.net/bugs/2042500
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before
pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
Reported-by: Koba Ko
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217321
Link: https://bugzilla.kernel.org/show_bug.cgi?id=216782
Link: https://bugzilla.kernel.org/show_bug.cgi?id=216877
Cc: Tasev Nikola
Cc: Mark Enriquez
Cc: Thomas Witt
Cc: Werner Sembach
Tested-by: Kai-Heng Feng
Signed-off-by: Mika Westerberg
Reviewed-by: Ilpo Järvinen
(backported from
https://lore.kernel.org/all/20231002070044.2299644-1-mika.westerb...@linux.intel.com/)
Signed-off-by: Koba Ko
Signed-off-by: Timo Aaltonen
** Bug watch added: Linux Kernel Bug Tracker #216877
https://bugzilla.kernel.org/show_bug.cgi?id=216877
** Bug watch added: Linux Kernel Bug Tracker #217321
https://bugzilla.kernel.org/show_bug.cgi?id=217321
** Bug watch added: Linux Kernel Bug Tracker #216782
https://bugzilla.kernel.org/show_bug.cgi?id=216782
--
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/1980829
Title:
System freeze after resuming from suspend due to PCI ASPM settings
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-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux-oem-6.0 source package in Focal:
Invalid
Status in linux-oem-6.1 source package in Focal:
Invalid
Status in linux-oem-6.5 source package in Focal:
Invalid
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-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
In Progress
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
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux-oem-6.5 source package in Kinetic:
Invalid
Bug description:
For OEM-6.1
[Impact]
While
[Kernel-packages] [Bug 2047398] Re: Add missing RPL P/U CPU IDs
** Tags added: originate-from-2047480 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+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 2047398] Re: Add missing RPL P/U CPU IDs
** Tags added: originate-from-2046946 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+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 2028217] Re: MTL: Add support for Meteor Lake
https://github.com/intel/thermal_daemon/issues/268 It's a known issue on lenovo laptops which lacks of firmware support. Suggested by upstream to add --ingore-cpuid-check to make thermald keeps working. ** Bug watch added: github.com/intel/thermal_daemon/issues #268 https://github.com/intel/thermal_daemon/issues/268 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Released Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2047461] Re: drm: Update file owner during use
SRU for oem-6.5 - https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/122 SRU for Mantic/Noble - https://lists.ubuntu.com/archives/kernel-team/2023-December/147674.html -- 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/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+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 2047461] [NEW] drm: Update file owner during use
Public bug reported: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => Incomplete ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients&#
[Kernel-packages] [Bug 2047398] Re: Add missing RPL P/U CPU IDs
SRU M/L - https://lists.ubuntu.com/archives/kernel- team/2023-December/147670.html ** Tags added: oem-priority originate-from-2046947 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+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 2047398] [NEW] Add missing RPL P/U CPU IDs
Public bug reported: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2047398 Title: Add missing RPL P/U CPU IDs Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047398/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Changed in: linux (Ubuntu Jammy)
Assignee: koba (kobako) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Mantic)
Assignee: koba (kobako) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Noble)
Assignee: koba (kobako) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2047184] [NEW] Audio device is not available, instead it shows dummy output in the settings
Public bug reported: [Impact] Audio device is not available, instead it shows dummy output in the settings [Fix] SOF driver looks for a config which both sample width and valid bits are both 32 bits. However, the config in NHLT table is 32-bit sample width and 24-bit valid bits. Should ignore the valid bits in NHLT when the sample width is 32 bits. Confirmed the below commit in v6.7-rc4 fix the issue 7b4c93a50a2e ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format [Test case] 1. check audio input/output on the system 2. System can play and record audio normally [Where problems could occur] When the samples assumed to be vbps=32 then the 'noise' introduced by the lower two bits (channel number) have no real life implication on audio quality. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2043541 somerville ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-2043541 somerville ** Changed in: linux-oem-6.5 (Ubuntu Noble) 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/2047184 Title: Audio device is not available, instead it shows dummy output in the settings Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Audio device is not available, instead it shows dummy output in the settings [Fix] SOF driver looks for a config which both sample width and valid bits are both 32 bits. However, the config in NHLT table is 32-bit sample width and 24-bit valid bits. Should ignore the valid bits in NHLT when the sample width is 32 bits. Confirmed the below commit in v6.7-rc4 fix the issue 7b4c93a50a2e ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format [Test case] 1. check audio input/output on the system 2. System can play and record audio normally [Where problems could occur] When the samples assumed to be vbps=32 then the 'noise' introduced by the lower two bits (channel number) have no real life implication on audio quality. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047184/+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 2045386] Re: Add ODM driver gpio-m058ssan
** Information type changed from Private to Public ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Tags added: erlin oem-priority originate-from-2039779 -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2045385] Re: Add ODM driver rtc-pcf85263
** Tags added: erlin oem-priority originate-from-2039779 -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2045387] Re: Add ODM driver f81604 usb-can
** Information type changed from Private to Public ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Tags added: erlin oem-priority originate-from-2039779 -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 2045385] Re: Add ODM driver rtc-pcf85263
** Information type changed from Private to Public ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385/+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 2046985] Re: Add ODM driver rtc-pcf85263
*** This bug is a duplicate of bug 2045385 *** https://bugs.launchpad.net/bugs/2045385 ** This bug has been marked a duplicate of private bug 2045385 -- 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/2046985 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046985/+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 2046985] Re: Add ODM driver rtc-pcf85263
** Tags added: originate-from-2039779 -- 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/2046985 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046985/+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 2046985] [NEW] Add ODM driver rtc-pcf85263
Public bug reported:
[ Impact ]
rtc-pcf85263 driver needed for ODM partner
[ Test Plan ]
Load the driver setting the timestamp level to 0 (default to 1) :
modprobe rtc-pcf85263 tsl=0
export the rtc device:
echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device
RTC device should act as a standard RTC,
hwclock -r -f /dev/rtc1 #for reading
hwclock -w -f /dev/rtc1 #for writing
This driver has anti-tampering function.
Get the current tamper timestamp:
cat /sys/class/rtc/rtc1/device/timestamp1
unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the
anti-tampering goes in open state.
The timestamp should be updated to the current time.
[ Where problems could occur ]
Events could occur on the I2C bus communication.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
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/2046985
Title:
Add ODM driver rtc-pcf85263
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
In Progress
Bug description:
[ Impact ]
rtc-pcf85263 driver needed for ODM partner
[ Test Plan ]
Load the driver setting the timestamp level to 0 (default to 1) :
modprobe rtc-pcf85263 tsl=0
export the rtc device:
echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device
RTC device should act as a standard RTC,
hwclock -r -f /dev/rtc1 #for reading
hwclock -w -f /dev/rtc1 #for writing
This driver has anti-tampering function.
Get the current tamper timestamp:
cat /sys/class/rtc/rtc1/device/timestamp1
unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the
anti-tampering goes in open state.
The timestamp should be updated to the current time.
[ Where problems could occur ]
Events could occur on the I2C bus communication.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046985/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
This series conflict with below SRU for Noble, so will no submit Noble SRU until below SRU has been included https://lists.ubuntu.com/archives/kernel-team/2023-December/147538.html ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: ... * 6835 MHz [177] (disabled) * 6855 MHz [181] (disabled) * 6875 MHz [185] (disabled) * 6895 MHz [189] (disabled) * 6915 MHz [193] (disabled) * 6935 MHz [197] (disabled) * 6955 MHz [201] (disabled) * 6975 MHz [205] (disabled) * 6995 MHz [209] (disabled) * 7015 MHz [213] (disabled) * 7035 MHz [217] (disabled) * 7055 MHz [221] (disabled) * 7075 MHz [225] (disabled) * 7095 MHz [229] (disabled) * 7115 MHz [233] (disabled) [Where problems could occur] Should have some impact to current RTL devices, but didn't see any fix patches for the 3 commits now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Description changed: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] - Run `iw list` should see something like below + Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: - * 5955 MHz [1] (22.0 dBm) (no IR) - * 5975 MHz [5] (22.0 dBm) (no IR) - * 5995 MHz [9] (22.0 dBm) (no IR) - * 6015 MHz [13] (22.0 dBm) (no IR) - * 6035 MHz [17] (22.0 dBm) (no IR) - * 6055 MHz [21] (22.0 dBm) (no IR) - * 6075 MHz [25] (22.0 dBm) (no IR) - * 6095 MHz [29] (22.0 dBm) (no IR) - * 6115 MHz [33] (22.0 dBm) (no IR) - * 6135 MHz [37] (22.0 dBm) (no IR) - * 6155 MHz [41] (22.0 dBm) (no IR) - * 6175 MHz [45] (22.0 dBm) (no IR) - * 6195 MHz [49] (22.0 dBm) (no IR) - * 6215 MHz [53] (22.0 dBm) (no IR) - - And `iw reg get` shows the contry code read from BIOS and supported - freq, too - - phy#0 (self-managed) - country TW: DFS-UNSET - (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ - (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ - (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ - + ... + * 6835 MHz [177] (disabled) + * 6855 MHz [181] (disabled) + * 6875 MHz [185] (disabled) + * 6895 MHz [189] (disabled) + * 6915 MHz [193] (disabled) + * 6935 MHz [197] (disabled) + * 6955 MHz [201] (disabled) + * 6975 MHz [205] (disabled) + * 6995 MHz [209] (disabled) + * 7015 MHz [213] (disabled) + * 7035 MHz [217] (disabled) + * 7055 MHz [221] (disabled) + * 7075 MHz [225] (disabled) + * 7095 MHz [229] (disabled) + * 7115 MHz [233] (disabled) [Where problems could occur] + Should have some impact to current RTL devices, but didn't see any fix patches for the 3 commits now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: ... * 6835 MHz [177] (disabled) * 6855 MHz [181] (disabled) * 6875 MHz [185] (disabled) * 6895 MHz [189] (disabled) * 6915 MHz [193] (disabled) * 6935 MHz [197] (disabled) * 6955 MHz [201] (disabled) * 6975 MHz [205] (disabled) * 6995 MHz [209] (disabled) * 7015 MHz [213] (disabled) * 7035 MHz [217] (disabled) * 7055 MHz [221] (disabled) * 7075 MHz [225] (disabled)
[Kernel-packages] [Bug 2045205] Re: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045205 Title: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] There is a spi error message on the screen when shutting down the machine. It won't hurt anything and all device work well in the next boot up. Intel SPI controller doesn't support reset command, but our customer feel bad about this message. [Fix] Distinguish the error code -EOPNOTSUPP from -ENOTSUPP, and not showing the warnning when it's op not supported. https://lkml.org/lkml/2023/11/29/62 [Test case] 1. boot up the system with intel SPI controller on it 2. power off the system and check if there are spi software reset failed errors on the screen. [Where problems could occur] There is a minor risk of breaking user-space applications that rely on specific return codes for unsupported operations. However, this risk is considered low, as such use-cases are unlikely to be common or critical. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045205/+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 2046225] Re: The eDP OLED panel has no output on MTL platform
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 Which is in drm-intel-next currently 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+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 2046225] Re: The eDP OLED panel has no output on MTL platform
** Description changed: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] + The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. ** Description changed: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 + Which is in drm-intel-next currently + 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing + [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. -- 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/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 Which is in drm-intel-next currently 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+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 2046225] Re: The eDP OLED panel has no output on MTL platform
** Description changed: [Impact] + We got a blank screen when boot into the system with OLED panel. [Fix] + Intel provides a patch to fix this + https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 [Test case] + 1. Install Ubuntu 22.04 on the system with 6.5+ kernel + 2. Check the screen display normally [Where problems could occur] -- 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/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194&rev=2 [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+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 2046225] [NEW] The eDP OLED panel has no output on MTL platform
Public bug reported: [Impact] [Fix] [Test case] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+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 2018236] Re: Fix ADL: System shutdown automatically when run Prime95&stress-ng with i9-12900K
** Changed in: thermald (Ubuntu Focal) Assignee: koba (kobako) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018236 Title: Fix ADL: System shutdown automatically when run Prime95&stress-ng with i9-12900K Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.15 package in Ubuntu: New Status in thermald package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux-meta-hwe-5.15 source package in Focal: New Status in thermald source package in Focal: In Progress Status in linux source package in Jammy: New Status in linux-meta-hwe-5.15 source package in Jammy: Invalid Status in thermald source package in Jammy: Fix Released Bug description: [Description] System shutdown automatically when stressing the machine. [Fix] Need these two to fix the issue. cbdd92b) Parse idsp and trips d385f20) Use PL1 max/min from PPCC when policies match https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be [Test Case] 1. Find a unit with i9-12900k CPU and air cooling 2. Install tools #sudo apt install stress-ng s-tui #sudo systemctl stop thermald #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) #./mprime #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. #sudo s-tui -c [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018236/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Description changed: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] + Run `iw list` should see something like below + + Frequencies: + * 5955 MHz [1] (22.0 dBm) (no IR) + * 5975 MHz [5] (22.0 dBm) (no IR) + * 5995 MHz [9] (22.0 dBm) (no IR) + * 6015 MHz [13] (22.0 dBm) (no IR) + * 6035 MHz [17] (22.0 dBm) (no IR) + * 6055 MHz [21] (22.0 dBm) (no IR) + * 6075 MHz [25] (22.0 dBm) (no IR) + * 6095 MHz [29] (22.0 dBm) (no IR) + * 6115 MHz [33] (22.0 dBm) (no IR) + * 6135 MHz [37] (22.0 dBm) (no IR) + * 6155 MHz [41] (22.0 dBm) (no IR) + * 6175 MHz [45] (22.0 dBm) (no IR) + * 6195 MHz [49] (22.0 dBm) (no IR) + * 6215 MHz [53] (22.0 dBm) (no IR) + + And `iw reg get` shows the contry code read from BIOS [Where problems could occur] ** Description changed: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see something like below Frequencies: - * 5955 MHz [1] (22.0 dBm) (no IR) - * 5975 MHz [5] (22.0 dBm) (no IR) - * 5995 MHz [9] (22.0 dBm) (no IR) - * 6015 MHz [13] (22.0 dBm) (no IR) - * 6035 MHz [17] (22.0 dBm) (no IR) - * 6055 MHz [21] (22.0 dBm) (no IR) - * 6075 MHz [25] (22.0 dBm) (no IR) - * 6095 MHz [29] (22.0 dBm) (no IR) - * 6115 MHz [33] (22.0 dBm) (no IR) - * 6135 MHz [37] (22.0 dBm) (no IR) - * 6155 MHz [41] (22.0 dBm) (no IR) - * 6175 MHz [45] (22.0 dBm) (no IR) - * 6195 MHz [49] (22.0 dBm) (no IR) - * 6215 MHz [53] (22.0 dBm) (no IR) + * 5955 MHz [1] (22.0 dBm) (no IR) + * 5975 MHz [5] (22.0 dBm) (no IR) + * 5995 MHz [9] (22.0 dBm) (no IR) + * 6015 MHz [13] (22.0 dBm) (no IR) + * 6035 MHz [17] (22.0 dBm) (no IR) + * 6055 MHz [21] (22.0 dBm) (no IR) + * 6075 MHz [25] (22.0 dBm) (no IR) + * 6095 MHz [29] (22.0 dBm) (no IR) + * 6115 MHz [33] (22.0 dBm) (no IR) + * 6135 MHz [37] (22.0 dBm) (no IR) + * 6155 MHz [41] (22.0 dBm) (no IR) + * 6175 MHz [45] (22.0 dBm) (no IR) + * 6195 MHz [49] (22.0 dBm) (no IR) + * 6215 MHz [53] (22.0 dBm) (no IR) - And `iw reg get` shows the contry code read from BIOS + And `iw reg get` shows the contry code read from BIOS and supported + freq, too + + phy#0 (self-managed) + country TW: DFS-UNSET + (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ + (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ + (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ + [Where problems could occur] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: I
