[Kernel-packages] [Bug 2063529] Re: Add support for Quectel RM520N-GL modem

[Bin Li]

** Description changed:

  [Impact]
  
- * Add support for Quectel RM520N-GL modem, so the device could be
- properly probed.
+ * Add support for Quectel RM520N-GL modem, so the device could be properly 
+ probed.
+ 
+ 08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:1007]
+ Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:100b]
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
  * These commits only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
  * Upstream commits:
    
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
    
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

** Summary changed:

- Add support for Quectel RM520N-GL modem
+ Add support for Quectel RM520N-GL modem [1eac:1007]

-- 
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/2063529

Title:
  Add support for Quectel RM520N-GL modem [1eac:1007]

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
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:
  In Progress

Bug description:
  [Impact]

  * Add support for Quectel RM520N-GL modem, so the device could be properly 
  probed.

  08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:1007]
  Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:100b]

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * These commits only introduces a PID, it won't impact devices which
  are supported originally.

  [Other Info]

  * Upstream commits:
    
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
    
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063529/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2063399] Re: Add support for Quectel EM160R-GL modem [1eac:100d]

[Bin Li]

** Summary changed:

- Add support for Quectel EM160R-GL modem
+ Add support for Quectel EM160R-GL modem [1eac:100d]

** Description changed:

  [Impact]
  
  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.
+ 
+ 08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:100d]
+ Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:5004]
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
  * The commit only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by 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/2063399

Title:
  Add support for Quectel EM160R-GL modem [1eac:100d]

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Won't Fix
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:
  In Progress

Bug description:
  [Impact]

  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.

  08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:100d]
  Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:5004]

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * The commit only introduces a PID, it won't impact devices which are
  supported originally.

  [Other Info]

  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063399/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2063288] [NEW] nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

[Bin Li]

Public bug reported:

$ ubuntu-drivers list
nvidia-driver-535-open, (kernel modules provided by 
linux-modules-nvidia-535-open-oem-22.04d)
nvidia-driver-550-server-open, (kernel modules provided by 
nvidia-dkms-550-server-open)
nvidia-driver-535, (kernel modules provided by 
linux-modules-nvidia-535-oem-22.04d)
nvidia-driver-550-server, (kernel modules provided by nvidia-dkms-550-server)

u@Libra2v1-6:~$ lspci -nn | grep NV
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:28b9] 
(rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22be] (rev a1)

$ cat /sys/devices/pci:00/:00:01.0/:01:00.0/modalias
pci:v10DEd28B9sv17AAsd2306bc03sc00i00

>From apt-cache show nvidia-driver-500, I could find the modalias below.

pci:v10DEd28B9sv*sd*bc03sc*i*

** Affects: nvidia-graphics-drivers-550 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu.
https://bugs.launchpad.net/bugs/2063288

Title:
  nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

Status in nvidia-graphics-drivers-550 package in Ubuntu:
  New

Bug description:
  $ ubuntu-drivers list
  nvidia-driver-535-open, (kernel modules provided by 
linux-modules-nvidia-535-open-oem-22.04d)
  nvidia-driver-550-server-open, (kernel modules provided by 
nvidia-dkms-550-server-open)
  nvidia-driver-535, (kernel modules provided by 
linux-modules-nvidia-535-oem-22.04d)
  nvidia-driver-550-server, (kernel modules provided by nvidia-dkms-550-server)

  u@Libra2v1-6:~$ lspci -nn | grep NV
  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:28b9] (rev a1)
  01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22be] (rev a1)

  $ cat /sys/devices/pci:00/:00:01.0/:01:00.0/modalias
  pci:v10DEd28B9sv17AAsd2306bc03sc00i00

  From apt-cache show nvidia-driver-500, I could find the modalias
  below.

  pci:v10DEd28B9sv*sd*bc03sc*i*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2063288/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049570] Re: 10de:28B9 was not supported in nvidia-driver-535

[Bin Li]

535.171.04 is supported the 28B9.

available: 535.171.04-0ubuntu0.22.04.1 [distro] non-free
modalias: pci:v10DEd28B9sv17AAsd2234bc03sc02i00
path: /sys/devices/pci:00/:00:01.0/:01:00.0
vendor: NVIDIA Corporation
support level: PB

** Changed in: oem-priority
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2049570

Title:
  10de:28B9 was not supported in nvidia-driver-535

Status in OEM Priority Project:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released

Bug description:
  On OEM project, we found the 28B9 is not supported in nvidia-
  driver-535, the version 535.154.05-0ubuntu0.22.04.1 in the proposed
  channel also doesn't include this id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2049570/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops

[Bin Li]

Installed the 2.0-1ubuntu4.7 version of firmware-sof-signed on the
previously failed ThinkPad platforms. Confirmed that now the LEDs can
toggle accordingly.

** Tags added: originate-from-2047202 sutton

-- 
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/2049569

Title:
  Enable the mic-mute led on Dell MTL laptops

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]
  On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is 
working but the LED(on F4) state is not changed accordingly.

  [Fix]
  There's no problem on the same series on RPL platform. It needs MTL specific 
SoF driver and controls to support the registered mixer switch. It requires the 
patches in 
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
 and 
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.
  2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.

  [Where problems could occur]
  It's only required for new sof-audio-pci-intel-mtl driver. The impact should 
be restricting.

  == firmware-sof ==

  [Impact]
  The mic-mute led not working on Intel MTL powered laptops.

  [Fix]
  For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add 
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the 
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control 
matches with the updated driver.

  [Test Case]
  1. enable -proposed pocket and install firmware-sof-signed
  2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.

  [Where problems could occur]
  The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all 
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

[Bin Li]

commit 3c9a7d086da4a403d72ab8df8d924f7247882653
Author: Dimitri John Ledkov 
Date:   Fri Oct 27 18:53:00 2023 +0200

Revert "UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting"

BugLink: https://bugs.launchpad.net/bugs/2041613

This reverts commit a53dba9297be9597eac7b17738723bd44bac97ea.

Signed-off-by: Dimitri John Ledkov 
Acked-by: Andrea Righi 
Acked-by: Roxana Nicolescu 
Signed-off-by: Stefan Bader 

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

[Bin Li]

On 22.04.4 with 6.5.0-oem kernel, we also met this issue during
shutdown.

Feb 23 15:20:36 P3-Tiny-Ref3-1 kernel: evict_inodes inode 20f5b07f, 
i_count = 1, was skipped!
Feb 23 15:20:36 P3-Tiny-Ref3-1 kernel: evict_inodes inode 3d74f469, 
i_count = 1, was skipped!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes

[Bin Li]

** Tags added: originate-from-2051090

** Tags added: originate-from-2051089

-- 
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/2046504

Title:
  Fix AMDGPU display on lower resolution modes

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
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

Bug description:
  [Impact]
  AMD GPU display is blank when set lower resolution than native mode on eDP.

  [Fix]
  On eDP the invalid modes are set, call mode set for valid modes instead.

  [Test]
  Tested on hardware, all the modes shown in gnome menu can be set OK.

  [Where problems could occur]
  It may break AMD display.

  This issue is not reproduced on v6.2- kernel versions, so SRU for
  oem-6.5 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes

[Bin Li]

** Tags added: originate-from-2047489

-- 
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/2046504

Title:
  Fix AMDGPU display on lower resolution modes

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
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

Bug description:
  [Impact]
  AMD GPU display is blank when set lower resolution than native mode on eDP.

  [Fix]
  On eDP the invalid modes are set, call mode set for valid modes instead.

  [Test]
  Tested on hardware, all the modes shown in gnome menu can be set OK.

  [Where problems could occur]
  It may break AMD display.

  This issue is not reproduced on v6.2- kernel versions, so SRU for
  oem-6.5 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes

[Bin Li]

** Tags added: originate-from-2047680

** No longer affects: oem-priority

-- 
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/2046504

Title:
  Fix AMDGPU display on lower resolution modes

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
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

Bug description:
  [Impact]
  AMD GPU display is blank when set lower resolution than native mode on eDP.

  [Fix]
  On eDP the invalid modes are set, call mode set for valid modes instead.

  [Test]
  Tested on hardware, all the modes shown in gnome menu can be set OK.

  [Where problems could occur]
  It may break AMD display.

  This issue is not reproduced on v6.2- kernel versions, so SRU for
  oem-6.5 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049570] [NEW] 10de:28B9 was not supported in nvidia-driver-535

[Bin Li]

Public bug reported:

On OEM project, we found the 28B9 is not supported in nvidia-driver-535,
the version 535.154.05-0ubuntu0.22.04.1 in the proposed channel also
doesn't include this id.

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-2049497 sutton

** Tags added: oem-priority originate-from-2049497 sutton

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2049570

Title:
  10de:28B9 was not supported in nvidia-driver-535

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  On OEM project, we found the 28B9 is not supported in nvidia-
  driver-535, the version 535.154.05-0ubuntu0.22.04.1 in the proposed
  channel also doesn't include this id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2049570/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-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

[Bin Li]

hi acelan,

 Got it, thanks a lot.

-- 
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 2028217] Re: MTL: Add support for Meteor Lake

[Bin Li]

Hi koba,

 The lastest thermald 2.4.9-1ubuntu0.4 failed to start on my Meteor Lake
platform, is it expected cause the dytc_lapmode? Thanks!

Dec 29 14:38:16 Mersey-1 thermald[842]: 35 CPUID levels; family:model:stepping 
0x6:aa:4 (6:170:4)
Dec 29 14:38:16 Mersey-1 thermald[842]: 
[/sys/devices/platform/thinkpad_acpi/dytc_lapmode] present: Thermald can't run 
on this platform 
Dec 29 14:38:16 Mersey-1 thermald[842]: Unsupported cpu model or platform   
Dec 29 14:38:16 Mersey-1 systemd[1]: thermald.service: Deactivated successfully.

-- 
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 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0

[Bin Li]

** Tags added: originate-from-2046325 sutton

-- 
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/2041495

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in OEM Priority Project:
  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 Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2041495

  [Impact]

  NVME module left unready, therefore not recognized by the installation 
process, and/or after installation with following error messages:
  ```
  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0
  ```

  [Fix]

  Proposed fix in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5=6cc834ba62998c65c42d0c63499bdd35067151ec
  "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well
  as stable kernels v6.1.55 and v6.5.5.

  [Test Case]

  Apply to kernel and boot with the nvme module installed. Now the device 
should be probed with success.
  ```
  kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0
  kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI 
INT A
  kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff
  kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds
  kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer.
  kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues
  kernel: [2.136735]  nvme0n1: p1 p2 p3
  ```

  [Where problems could occur]

  This patch tries to set an appropriate CRTO (Controller Ready
  Timeouts) that may be reported incorrectly by some devices. There
  should be little (a bit longer CRTO) to no effect on devices
  performing normally before hands.

  [Other Info]

  While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1
  will be nominated.

  == original bug report ==

  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2041495/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2043580] Re: New Intel MIPI IPU6 firmware available for MTL-P platform

[Bin Li]

** Tags added: oem-priority originate-from-2044254 sutton

-- 
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/2043580

Title:
  New Intel MIPI IPU6 firmware available for MTL-P platform

Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Intel IPU6 camera drivers may not load with MTL QS stepping CPUs.

  [Fix]

  New upstream firmware release in
  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87.

  [Test Case]

  1. Install firmware into /lib/firmware/intel/ipu6epmtl_fw.bin and reboot
  2. Try access camera via webcamtest.com
  3. The camera should be working as verified with ES CPUs.

  [Where problems could occur]

  Opaque firmware, and there is no IPU6/MTL platform shipped yet.

  [Other Info]

  Intel MIPI IPU6 on Intel Meteor Lake platform is only supported on 6.5 kernels
  or newer. Nominate Jammy for oem-6.5, Noble as the next LTS, and best effort
  support for Mantic.

  == original bug report ==

  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87
  Intel released a new firmware blob for MIPI IPU6 on Intel Meteor Lake 
platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2043580/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

[Bin Li]

@vicamo,

 I met this issue on Lenovo platforms, do you have any updates about
this SRU, thanks!

-- 
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/2037390

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Incomplete
Status in linux-firmware source package in Mantic:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform.

iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  3 upstream commits needed.

  For the first commit for iwlwifi, it supports both AX211 and BE200 (for bug
  2028065).

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort. While there is no
  Noble branch yet, Noble is not nominated.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-06 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-jiayi-jammy-amd64-20230706-44
  MachineType: Intel Corporation Meteor Lake Client Platform
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem 
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-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-9004-oem N/A
   linux-backports-modules-6.5.0-9004-oem  N/A
   linux-firmware  
20220329.git681281e4-0ubuntu3.19+exp.83
  Tags: third-party-packages jammy
  Uname: Linux 6.5.0-9004-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/21/2023
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: MTL-P DDR5 SODIMM SBS RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.71
  dmi.modalias: 

[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

[Bin Li]

** Tags added: originate-from-2045721 sutton

-- 
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/2037390

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Incomplete
Status in linux-firmware source package in Mantic:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform.

iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  3 upstream commits needed.

  For the first commit for iwlwifi, it supports both AX211 and BE200 (for bug
  2028065).

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort. While there is no
  Noble branch yet, Noble is not nominated.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-06 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-jiayi-jammy-amd64-20230706-44
  MachineType: Intel Corporation Meteor Lake Client Platform
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem 
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-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-9004-oem N/A
   linux-backports-modules-6.5.0-9004-oem  N/A
   linux-firmware  
20220329.git681281e4-0ubuntu3.19+exp.83
  Tags: third-party-packages jammy
  Uname: Linux 6.5.0-9004-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/21/2023
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: MTL-P DDR5 SODIMM SBS RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.71
  dmi.modalias: 

[Kernel-packages] [Bug 2035559] Re: upgrade to latest proposed kernel 6.5.0-5 failed

[Bin Li]

** Changed in: tp-smapi (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035559

Title:
  upgrade to latest proposed kernel 6.5.0-5 failed

Status in linux package in Ubuntu:
  Invalid
Status in tp-smapi package in Ubuntu:
  Fix Released

Bug description:
  Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.5.0-5-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build 
M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/tp-smapi-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64)
  Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information.
  dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia
  dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10)
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
   * dkms: autoinstall for kernel 6.5.0-5-generic
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.5.0-5-generic (--configure):
   installed linux-headers-6.5.0-5-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of 
linux-headers-generic-hwe-22.04:
   linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; 
however:
Package linux-headers-6.5.0-5-generic is not configured yet.

  dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: dependency problems prevent configuration of 
  linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
6.5.0.5.7); however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-oem-22.04:
   linux-oem-22.04 depends on linux-generic-hwe-22.04; however:
Package linux-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-oem-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.5.0-5-generic; however:
Package linux-headers-6.5.0-5-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfNo apport report written because the 
error message indicates its a followup error from a previous failure.

 No apport repo
  rt written because MaxReports is reached already
  No apport report written 
because MaxReports is reached already

No apport report written because MaxReports is 
  reached already
 igured
  dpkg: dependency problems prevent configuration of linux-headers-oem-22.04:
   linux-headers-oem-22.04 depends on linux-headers-generic-hwe-22.04; however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-headers-oem-22.04 (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for linux-image-6.5.0-5-generic (6.5.0-5.5) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.5.0-5-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build 
M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/tp-smapi-dkms.0.crash'
  Error! Bad return status for module 

[Kernel-packages] [Bug 2035559] Re: upgrade to latest proposed kernel 6.5.0-5 failed

[Bin Li]

Hi fenris,

This issue should be fixed in mantic now, could you help check if you
could reproduce this issue again? Thanks!

tp-smapi (0.44-1ubuntu1) mantic; urgency=medium 



  *  Restrict module to amd64   



 -- Paolo Pisati   Fri, 22 Sep 2023 06:55:18 +  



tp-smapi (0.44-1) unstable; urgency=medium  



  * New upstream version 0.44   

+ Support 6.4 kernel

  Closes: #1038207

-- 
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/2035559

Title:
  upgrade to latest proposed kernel 6.5.0-5 failed

Status in linux package in Ubuntu:
  Invalid
Status in tp-smapi package in Ubuntu:
  New

Bug description:
  Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.5.0-5-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build 
M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/tp-smapi-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64)
  Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information.
  dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia
  dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10)
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
   * dkms: autoinstall for kernel 6.5.0-5-generic
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.5.0-5-generic (--configure):
   installed linux-headers-6.5.0-5-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of 
linux-headers-generic-hwe-22.04:
   linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; 
however:
Package linux-headers-6.5.0-5-generic is not configured yet.

  dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: dependency problems prevent configuration of 
  linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
6.5.0.5.7); however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-oem-22.04:
   linux-oem-22.04 depends on linux-generic-hwe-22.04; however:
Package linux-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-oem-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.5.0-5-generic; however:
Package linux-headers-6.5.0-5-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfNo apport report written because the 
error message indicates its a followup error from a previous failure.

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

ON ThinkPad X1 Carbon Gen 11(8086:a75d), the mipi works fine now on
22.04 with generic kernel or 6.1.0-oem kernel, tested in gst-launch-1.0,
it works fine.

I found it the gst-plugin-scanner crashed after install libcamhal0 , and
I met this issue on X1 Carbon Gen 10(8086:465d) too.

** Attachment added: 
"_usr_lib_x86_64-linux-gnu_gstreamer1.0_gstreamer-1.0_gst-plugin-scanner.1002.crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5699882/+files/_usr_lib_x86_64-linux-gnu_gstreamer1.0_gstreamer-1.0_gst-plugin-scanner.1002.crash

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please 

[Kernel-packages] [Bug 2035051] [NEW] hevc encoding on intel igpu produces garbled output ubuntu 22.04

[Yensong Ted Li]

Public bug reported:

Please refer to this for more details:

https://github.com/intel/media-driver/issues/1503

Apparently the issue has been fixed since ffmpeg 5.1+; but unfortunately
since ubuntu 22.04 is still based off of the ffmpeg 4.4.2 software
stack, applications like OBS installed via the official PPA is unable to
use the system ffmpeg libraries like libavcodec58 to record using the
VAAPI hevc encoder without producing absolutely garbled videos.

I am more than happy to provide any additional information in order to
resolve this issue :)

** Affects: ffmpeg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jammy

** Package changed: linux-signed-hwe-5.13 (Ubuntu) => ffmpeg (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/2035051

Title:
  hevc encoding on intel igpu produces garbled output ubuntu 22.04

Status in ffmpeg package in Ubuntu:
  New

Bug description:
  Please refer to this for more details:

  https://github.com/intel/media-driver/issues/1503

  Apparently the issue has been fixed since ffmpeg 5.1+; but
  unfortunately since ubuntu 22.04 is still based off of the ffmpeg
  4.4.2 software stack, applications like OBS installed via the official
  PPA is unable to use the system ffmpeg libraries like libavcodec58 to
  record using the VAAPI hevc encoder without producing absolutely
  garbled videos.

  I am more than happy to provide any additional information in order to
  resolve this issue :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/2035051/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

linux-oem-22.04d in updates now, but it could not support mipi yet.

6.5.0-1003-oem

Sep 08 06:03:58 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
isys port open ready failed -16
Sep 08 06:03:58 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
Device close failure: -16
Sep 08 06:04:00 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
Device release time out -16
Sep 08 06:04:00 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
Clearing old context


** Attachment added: "6.5.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5699219/+files/6.5.log

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

ON ThinkPad X1 Carbon Gen 10, the mipi works fine now on 22.04 with
genericc kernel or 6.1.0-oem kernel,  tested in gst-launch-1.0 or
https://webcamtests.com/ .

$ sudo apt install inux-modules-ipu6-generic-hwe-22.04 
linux-modules-ivsc-generic-hwe-22.04
$ sudo apt install linux-modules-ipu6-oem-22.04c linux-modules-ivsc-oem-22.04c
$ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 
$ sudo apt install libcamhal0
$ sudo reboot

$ gst-launch-1.0 v4l2src ! glimagesink

I just found some 'Payload checksum (CRC) error', not sure if it has any
risks.

Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
stream on ov2740 5-0036
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Payload checksum (CRC) error
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Single packet header error corrected
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Multiple packet header errors detected
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Payload checksum (CRC) error
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Incomplete long packet detected
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Frame sync error
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Inter-frame short packet discarded
Sep 08 05:15:18 binli-X1-Carbon-G10 kernel: intel-ipu6-isys intel-ipu6-isys0: 
csi2-1 error: Inter-frame long packet discarded

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

@kc,

 For #109, Gabriel tried the windows last year, but he remember he never
made the mipi work before. Thanks!

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

Tried vicamo's ppa, it didn't work too.

https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412

sudo apt install gstreamer1.0-icamera libgsticamerainterface-1.0-1

And reboot, then try the command (if you are in wayland session):

$ sudo -E gst-launch-1.0 icamerasrc buffer-count=7 ! 
video/x-raw,format=NV12,width=1280,height=720 ! videoconvert ! glimagesink
[08-30 02:46:41.958] CamHAL[INF] load_camera_hal_library, the library name: 
lib/x86_64-linux-gnu/libcamhal/pluginsipu6ep.so   
[08-30 02:46:41.958] CamHAL[ERR] load_camera_hal_library, failed to open 
library: lib/x86_64-linux-gnu/libcamhal/pluginsipu6ep.so, error: lib/x86_
64-linux-gnu/libcamhal/pluginsipu6ep.so: cannot open shared object file: No 
such file or directory
[08-30 02:46:41.958] CamHAL[ERR] get_number_of_cameras, function call is 
nullptr  
[08-30 02:46:41.958] CamHAL[ERR] get_number_of_cameras, function call is 
nullptr  
[08-30 02:46:41.958] CamHAL[ERR] get_number_of_cameras, function call is 
nullptr  

  
(gst-launch-1.0:3805): GLib-GObject-CRITICAL **: 02:46:41.958: 
g_param_spec_enum: assertion 'g_enum_get_value (enum_class, default_value) != 
NULL'
 failed 
  

  
(gst-launch-1.0:3805): GLib-GObject-CRITICAL **: 02:46:41.958: 
validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed   
   

  
(gst-launch-1.0:3805): GLib-GObject-CRITICAL **: 02:46:41.958: 
g_param_spec_ref_sink: assertion 'G_IS_PARAM_SPEC (pspec)' failed   
   

  
(gst-launch-1.0:3805): GLib-GObject-CRITICAL **: 02:46:41.958: 
g_param_spec_unref: assertion 'G_IS_PARAM_SPEC (pspec)' failed  
   
[08-30 02:46:41.958] CamHAL[ERR] get_number_of_cameras, function call is 
nullptr  
[08-30 02:46:41.958] CamHAL[ERR] get_number_of_cameras, function call is 
nullptr  
WARNING: erroneous pipeline: could not link camerasrc0 to videoconvert0, 
camerasrc0 can't handle caps video/x-raw, format=(string)NV12, width=(int
)1280, height=(int)720 

** Attachment added: "vicamo.ipu6.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5696341/+files/vicamo.ipu6.log

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't 

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

6.1.0-oem kernel has the same issue.


Aug 30 00:01:20 binli-ThinkPad-X1-Carbon-Gen-10 kernel: intel-ipu6-isys 
intel-ipu6-isys0: isys port open ready failed -16
Aug 30 00:01:20 binli-ThinkPad-X1-Carbon-Gen-10 kernel: intel-ipu6-isys 
intel-ipu6-isys0: Device close failure: -16
Aug 30 00:01:22 binli-ThinkPad-X1-Carbon-Gen-10 kernel: intel-ipu6-isys 
intel-ipu6-isys0: Device release time out -16


** Attachment added: "6.1.0-oem-ipu.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5696287/+files/6.1.0-oem-ipu.log

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third 

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

Currently it couldn't work on 22.04.3 on X1 Carbon G10 too, kernel is
6.2.0-31 and linux-firmware is ubuntu3.18.

$ sudo apt install linux-generic-hwe-22.04 linux-modules-ipu6-generic-hwe-22.04 
linux-modules-ivsc-generic-hwe-22.04
$ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
$ sudo apt install libcamhal-ipu6ep0

** Attachment added: "ipu6.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5696285/+files/ipu6.log

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh 

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Bin Li]

Currently it couldn't work on 20.04.6 on X1 Carbon G10.

$ sudo apt install linux-generic-hwe-20.04

$ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6

$ sudo apt install libcamhal-ipu6ep0

$ sudo reboot

Aug 29 06:00:14 u-ThinkPad-X1-Carbon-Gen-10 gst-plugin-scan[1134]:
Failed to load plugin '/usr/lib/x86_64-linux-
gnu/gstreamer-1.0/libgsticamerasrc.so': /lib/x86_64-linux-
gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by
/lib/x86_64-linux-gnu/libgcss-ipu6ep.so.0)

Aug 29 06:00:18 u-ThinkPad-X1-Carbon-Gen-10 gst-plugin-scan[1589]:
Failed to load plugin '/usr/lib/x86_64-linux-
gnu/gstreamer-1.0/libgsticamerasrc.so': /lib/x86_64-linux-
gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by
/lib/x86_64-linux-gnu/libgcss-ipu6ep.so.0)

** Attachment added: "ipu.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5696051/+files/ipu.log

-- 
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/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as 

[Kernel-packages] [Bug 2021449] Re: ALSA: hda/realtek: Enable headset onLenovo M70/M90

[Bin Li]

After enabled the proposed channel, I could install the 1015-oem kernel
successfully, and the headset could be used.

$ apt-cache policy linux-oem-22.04c 
linux-oem-22.04c:
  Installed: 6.1.0.1015.15
  Candidate: 6.1.0.1015.15
  Version table:
 *** 6.1.0.1015.15 500
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 6.1.0.1014.14 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages

** Attachment added: "headset.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021449/+attachment/5681083/+files/headset.png

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

** Changed in: oem-priority
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2021449

Title:
  ALSA: hda/realtek: Enable headset onLenovo M70/M90

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.

  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f

  [Test]
  After applying the patch, the os works fine with the headset mic on 6.1.0-oem.

  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2021449/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2021449] Re: ALSA: hda/realtek: Enable headset onLenovo M70/M90

[Bin Li]

** Description changed:

  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.
  
  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f
  
  [Test]
- After applying the patch, the os works fine with the headset mic.
+ After applying the patch, the os works fine with the headset mic on 6.1.0-oem.
  
  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2021449

Title:
  ALSA: hda/realtek: Enable headset onLenovo M70/M90

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.

  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f

  [Test]
  After applying the patch, the os works fine with the headset mic on 6.1.0-oem.

  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2021449/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

[Bin Li]

I did a test on focal platforms, I found this issue was not fixed yet.

By default user used oem kernel which is set by oem-meta packages, it
will be ok, but if the user select the generic kernel, then it will meet
black screen issue cause of missing nvidia driver.

Start-Date: 2023-05-31  06:04:11
Commandline: /usr/bin/unattended-upgrade -v
Requested-By: u (1001)
Install: linux-hwe-5.15-headers-5.15.0-73:amd64 (5.15.0-73.80~20.04.1, 
automatic), linux-headers-generic-hwe-20.04:amd64 (5.15.0.73.80~20.04.34, 
automatic), linux-modules-extra-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1, 
automatic), linux-image-generic-hwe-20.04:amd64 (5.15.0.73.80~20.04.34, 
automatic), linux-generic-hwe-20.04:amd64 (5.15.0.73.80~20.04.34, automatic), 
linux-modules-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1, automatic), 
linux-headers-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1, automatic), 
linux-image-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1, automatic)
Upgrade: linux-image-oem-20.04d:amd64 (5.14.0.1032.29, 5.15.0.73.80~20.04.34), 
linux-oem-20.04d:amd64 (5.14.0.1032.29, 5.15.0.73.80~20.04.34)
End-Date: 2023-05-31  06:04:45

Start-Date: 2023-05-31  06:18:38
Commandline: /usr/bin/unattended-upgrade -v
Requested-By: u (1001)
Remove: linux-image-oem-20.04d:amd64 (5.15.0.73.80~20.04.34)
End-Date: 2023-05-31  06:18:38

Start-Date: 2023-05-31  06:18:42
Commandline: /usr/bin/unattended-upgrade -v
Requested-By: u (1001)
Remove: linux-headers-oem-20.04d:amd64 (5.15.0.73.80~20.04.34)
End-Date: 2023-05-31  06:18:42

Removing linux-headers-oem-20.04d (5.15.0.73.80~20.04.34) ...
Packages that were successfully auto-removed: linux-headers-oem-20.04d 
linux-image-oem-20.04d
Packages that are kept back: 
Package libnvidia-cfg1-510 is kept back because a related package is kept back 
or due to local apt_preferences(5).
Package libnvidia-compute-510 is kept back because a related package is kept 
back or due to local apt_preferences(5).
Package libnvidia-decode-510 is kept back because a related package is kept 
back or due to local apt_preferences(5).
Package libnvidia-encode-510 is kept back because a related package is kept 
back or due to local apt_preferences(5).
Package libnvidia-extra-510 is kept back because a related package is kept back 
or due to local apt_preferences(5).
Package libnvidia-fbc1-510 is kept back because a related package is kept back 
or due to local apt_preferences(5).
Package libnvidia-gl-510 is kept back because a related package is kept back or 
due to local apt_preferences(5).
Package linux-modules-nvidia-510-oem-20.04d is kept back because a related 
package is kept back or due to local apt_preferences(5).
Package nvidia-compute-utils-510 is kept back because a related package is kept 
back or due to local apt_preferences(5).
Package nvidia-driver-510 is kept back because a related package is kept back 
or due to local apt_preferences(5).
Package nvidia-kernel-common-510 is kept back because a related package is kept 
back or due to local apt_preferences(5).
Package nvidia-kernel-source-510 is kept back because a related package is kept 
back or due to local apt_preferences(5).
Package nvidia-utils-510 is kept back because a related package is kept back or 
due to local apt_preferences(5).
Package xserver-xorg-video-nvidia-510 is kept back because a related package is 
kept back or due to local apt_preferences(5).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505

Title:
  Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

Status in OEM Priority Project:
  Confirmed
Status in linux-meta-oem-5.14 package in Ubuntu:
  New
Status in linux-meta-oem-5.17 package in Ubuntu:
  Fix Released

Bug description:
  If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
  would like meet this issue.

  1020-oem is in security channel. In jammy the unattende-upgrade will
  install security fixes by default.

  For the I+N platforms, the nvidia driver couldn't be installed for
  1020-oem kernel, then user will meet a black screen cause of nvidia
  modules couldn't be loaded.

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESMApps:${distro_codename}-apps-security";
  "${distro_id}ESM:${distro_codename}-infra-security";

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe 

[Kernel-packages] [Bug 2021449] Re: ALSA: hda/realtek: Enable headset onLenovo M70/M90

[Bin Li]

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2021449

Title:
  ALSA: hda/realtek: Enable headset onLenovo M70/M90

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.

  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f

  [Test]
  After applying the patch, the os works fine with the headset mic.

  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2021449/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2021449] [NEW] ALSA: hda/realtek: Enable headset onLenovo M70/M90

[Bin Li]

Public bug reported:

[Impact]
The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 generic 
kernel.
Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
The previous quirk for M70/M90 is for Gen3.

[Fix]
cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f

[Test]
After applying the patch, the os works fine with the headset mic.

[Where problems could occur]
It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Description changed:

  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.
+ 
+ On Jammy, 6.1.0-oem kernel and 5.19.0-42-generic

** Description changed:

+ [Impact]
+ The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.
  
- On Jammy, 6.1.0-oem kernel and 5.19.0-42-generic
+ [Fix]
+ cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f
+ 
+ [Test]
+ After applying the patch, the os works fine with the headset mic.
+ 
+ [Where problems could occur]
+ It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2021449

Title:
  ALSA: hda/realtek: Enable headset onLenovo M70/M90

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.

  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f

  [Test]
  After applying the patch, the os works fine with the headset mic.

  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021449/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2008188] Re: blacklist: Problem blacklisting hash

[Bin Li]

We can close this issue as wontfix.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008188

Title:
  blacklist: Problem blacklisting hash

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Confirmed

Bug description:
  When boot up the system from oem-6.1 kernel, some errors will printed
  in the console.

  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008188/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2008188] Re: blacklist: Problem blacklisting hash

[Bin Li]

@vanvugt,

 Yes, with 5.19 or later kernel, this issue could be reproduced on most
Lenovo's machines.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008188

Title:
  blacklist: Problem blacklisting hash

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Confirmed

Bug description:
  When boot up the system from oem-6.1 kernel, some errors will printed
  in the console.

  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008188/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2008188] Re: blacklist: Problem blacklisting hash

[Bin Li]

@Andreas,

 Thanks, and yes, I got the feedback from Lenovo, currently it should be
an issue and couldn't be fixed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008188

Title:
  blacklist: Problem blacklisting hash

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Confirmed

Bug description:
  When boot up the system from oem-6.1 kernel, some errors will printed
  in the console.

  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008188/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

[Bin Li]

Hi Alberto & Andy,

 Currently our customer met this issue on focal too.
 We released image with 5.14.0-1032.35 oem kernel and nvidia 
510.51-0ubuntu0.20.04.1, and the unattended-upgrade upgraded to 5.14.0-1051.58, 
and the nvidia modules could not be installed.

 Could you help apply the jammy's fix into focal? Thanks!

$ sudo apt install linux-modules-nvidia-510-5.14.0-1051-oem
The following packages have unmet dependencies:
 linux-modules-nvidia-510-5.14.0-1051-oem : Depends: nvidia-kernel-common-510 
(<= 510.85.02-1) but 510.108.03-0ubuntu0.20.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505

Title:
  Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

Status in OEM Priority Project:
  Fix Released
Status in linux-meta-oem-5.14 package in Ubuntu:
  New
Status in linux-meta-oem-5.17 package in Ubuntu:
  Fix Released

Bug description:
  If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
  would like meet this issue.

  1020-oem is in security channel. In jammy the unattende-upgrade will
  install security fixes by default.

  For the I+N platforms, the nvidia driver couldn't be installed for
  1020-oem kernel, then user will meet a black screen cause of nvidia
  modules couldn't be loaded.

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESMApps:${distro_codename}-apps-security";
  "${distro_id}ESM:${distro_codename}-infra-security";

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

[Bin Li]

** Also affects: linux-meta-oem-5.14 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505

Title:
  Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

Status in OEM Priority Project:
  Fix Released
Status in linux-meta-oem-5.14 package in Ubuntu:
  New
Status in linux-meta-oem-5.17 package in Ubuntu:
  Fix Released

Bug description:
  If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
  would like meet this issue.

  1020-oem is in security channel. In jammy the unattende-upgrade will
  install security fixes by default.

  For the I+N platforms, the nvidia driver couldn't be installed for
  1020-oem kernel, then user will meet a black screen cause of nvidia
  modules couldn't be loaded.

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESMApps:${distro_codename}-apps-security";
  "${distro_id}ESM:${distro_codename}-infra-security";

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs

[Bin Li]

** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/2009676

Title:
  Add support for Raptor Lake S CPUs

Status in OEM Priority Project:
  Fix Released
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Support thermald on Raptor Lake S CPU.

  [Test Plan]

   * Use a machine with a Raptor Lake S cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Raptor Lake S in thermald, which
  won't impact other hardware.

  [Other Info]

  
https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs

[Bin Li]

Hi koba,

 I heard you will bump new version of thermald for jammy, may I know
your schedule about it? Thanks!

-- 
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/2009676

Title:
  Add support for Raptor Lake S CPUs

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [Impact]

   * Support thermald on Raptor Lake S CPU.

  [Test Plan]

   * Use a machine with a Raptor Lake S cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Raptor Lake S in thermald, which
  won't impact other hardware.

  [Other Info]

  
https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2009676] [NEW] Add support for Raptor Lake S CPUs

[Bin Li]

Public bug reported:

[Impact]

 * Support thermald on Raptor Lake S CPU.

[Test Plan]

 * Use a machine with a Raptor Lake S cpu.

 * systemctl status thermald

 * Status of thermald should be `running`

[Where problems could occur]

 * This change is to add support for Raptor Lake S in thermald, which
won't impact other hardware.

[Other Info]

https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: thermald (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-2008667 sutton

** Information type changed from Proprietary to Public

** Also affects: thermald (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: oem-priority originate-from-2008667 sutton

-- 
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/2009676

Title:
  Add support for Raptor Lake S CPUs

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [Impact]

   * Support thermald on Raptor Lake S CPU.

  [Test Plan]

   * Use a machine with a Raptor Lake S cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Raptor Lake S in thermald, which
  won't impact other hardware.

  [Other Info]

  
https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2008188] [NEW] blacklist: Problem blacklisting hash

[Bin Li]

Public bug reported:

When boot up the system from oem-6.1 kernel, some errors will printed in
the console.

Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13)
Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13)
Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13)
Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13)
Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13)
Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13)

** Affects: linux-oem-6.1 (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: linux (Ubuntu) => linux-oem-6.1 (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008188

Title:
  blacklist: Problem blacklisting hash

Status in linux-oem-6.1 package in Ubuntu:
  New

Bug description:
  When boot up the system from oem-6.1 kernel, some errors will printed
  in the console.

  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)
  Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash 
(-13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2008188/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver

[Bin Li]

** Tags added: originate-from-2006879

** Tags added: sutton

-- 
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/2002601

Title:
  Wireless: Enable RTL8852BE wifi driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-firmware source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Justification]
  Enable Realtek RLT8852BE WIFI.

  [Test]
  1. put rtw8852b_fw.bin in /lib/firmware/rtw89/
  2. boot-up with kernel enabled RTL8852be.
  3. Connect to WIFI-AP and test with ping.

  * ping -I wlp2s0 8.8.8.8
  ~~~
  PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data.
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms
  64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms
  64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms
  64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms
  64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms
  ~~~
  * Connected to AP
  ~~~
  u@ubuntu:~$ nmcli dev
  DEVICE TYPE STATE CONNECTION
  enp3s0 ethernet connected Wired connection 1
  wlp2s0 wifi connected Canonical
  p2p-dev-wlp2s0 wifi-p2p disconnected --
  lo loopback unmanaged --
  ~~~
  * lsmod | grep 8852
  ~~~
  lsmod | grep 8852
  rtw89_8852be 16384 0
  rtw89_8852b 368640 1 rtw89_8852be
  rtw89_pci 61440 1 rtw89_8852be
  rtw89_core 442368 2 rtw89_8852b,rtw89_pci
  cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211
  ~~~

  4. cbd's built result,
  Lunar,
  ~~~
  remote: Resolving deltas: 100% (391/391), completed with 118 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-0e58018b43c1-ioeM
  remote: * 96/480 cores busy (1/5 hosts), 0 builds queued
  remote: 2023-01-12 03:16:35  kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK
  remote: 2023-01-12 03:17:47  kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK
  remote: 2023-01-12 03:11:36  kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK
  remote: 2023-01-12 03:16:30  kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK
  remote: 2023-01-12 03:10:24  kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK
  remote: 

  To cbd:lunar.git
  ~~~
  OEM-6.1,
  remote: Resolving deltas: 100% (399/399), completed with 121 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-c1002f30ccc3-m65z
  remote: * 0/192 cores busy (0/2 hosts), 0 builds queued
  remote: 2023-01-12 05:25:23  kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK
  remote: 

  To cbd:jammy.git

  [Where problems could occur]
  Medium, a new driver so the current driver may have some edge cases didn't 
consider.

  [Misc]
  * For generic Jammy, need more patches to enable RTL8852be so only SRU for 
OEM-6.1.
  * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on 
Lunar, so only SRU for Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive

[Bin Li]

** Changed in: oem-priority
 Assignee: (unassigned) => Atlas Yu (pseudoc)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1998154

Title:
  dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under
  universe archive

Status in OEM Priority Project:
  Fix Released
Status in dkms package in Ubuntu:
  Invalid

Bug description:
  [Description]

  The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in
  universe archive.

  https://packages.ubuntu.com/search?keywords=gcc-12
  gcc-12 is under main for kinect, and the patches are cherry-picked from 
kinect/stable, I suppose it is a mistake for jammy in universe.

  [debian/changelog]

  dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium

  Cherry-pick patches from kinetic/stable to address building dkms
  modules correctly for HWE kernels (LP: #1991664):

  Fix dkms-autopkgtest when a given dkms package is built into the
  kernel already of the same version. (i.e. zfs-linux on Ubuntu).

  Use exact compiler for dkms as used to build the kernel, when
  possible.

  Depend on gcc-12 to build modules for HWE kernels correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998154/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

[Bin Li]

Thanks all, the workaround works fine.

** No longer affects: nvidia-graphics-drivers-515 (Ubuntu)

** Changed in: oem-priority
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505

Title:
  Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

Status in OEM Priority Project:
  Fix Released
Status in linux-meta-oem-5.17 package in Ubuntu:
  Fix Released

Bug description:
  If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
  would like meet this issue.

  1020-oem is in security channel. In jammy the unattende-upgrade will
  install security fixes by default.

  For the I+N platforms, the nvidia driver couldn't be installed for
  1020-oem kernel, then user will meet a black screen cause of nvidia
  modules couldn't be loaded.

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESMApps:${distro_codename}-apps-security";
  "${distro_id}ESM:${distro_codename}-infra-security";

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991036] Re: ath11k: Freezing kernel when doing s2idle [17cb:1103]

[Bin Li]

*** This bug is a duplicate of bug 1995041 ***
https://bugs.launchpad.net/bugs/1995041

In ubuntu oem kernel, this patch will be available in next release.

https://patchwork.ozlabs.org/project/ubuntu-
kernel/patch/20221028050706.48086-2-aaron...@canonical.com/

** This bug has been marked a duplicate of bug 1995041
   Fix ath11k deadlock on WCN6855

-- 
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/1991036

Title:
  ath11k: Freezing kernel when doing s2idle [17cb:1103]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On ubuntu 22.04, I installed v6.0-rc3 mainline kernel.
  linux-firmware 20220329.git681281e4-0ubuntu3.4

  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: PM: suspend entry (s2idle)
  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: Filesystems sync: 0.004 seconds
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing user space processes ...
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing of tasks failed after 
20.007 seconds (9 tasks refusing to freeze, wq_busy=0):
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: task:NetworkManager  state:D 
stack:0 pid:  988 ppid: 1 flags:0x4006
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Call Trace:
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __schedule+0x221/0x5c0
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule+0x5f/0x100
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule_timeout+0x111/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  wait_for_completion+0x88/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __flush_work.isra.0+0x1b9/0x340
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
flush_workqueue_prep_pwqs+0x140/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __cancel_work_timer+0x10d/0x190
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
ath11k_mac_config_mon_status_default+0x9c/0x170 [ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  cancel_work_sync+0x10/0x20
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ath11k_mac_op_stop+0x9f/0x1e0 
[ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  drv_stop+0x45/0x120 [mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop_device+0x43/0x50 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_do_stop+0x6b1/0x980 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
cond_synchronize_rcu_expedited+0x40/0x40
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? qdisc_reset+0x27/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop+0x43/0x170 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __dev_close_many+0x9f/0x120

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1991036/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive

[Bin Li]

Hi Matthias,

 gcc-12 looks in a wrong archive, could you help fix it? Or do you know
who could fix it? Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1998154

Title:
  dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under
  universe archive

Status in dkms package in Ubuntu:
  New

Bug description:
  [Description]

  The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in
  universe archive.

  https://packages.ubuntu.com/search?keywords=gcc-12
  gcc-12 is under main for kinect, and the patches are cherry-picked from 
kinect/stable, I suppose it is a mistake for jammy in universe.

  [debian/changelog]

  dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium

  Cherry-pick patches from kinetic/stable to address building dkms
  modules correctly for HWE kernels (LP: #1991664):

  Fix dkms-autopkgtest when a given dkms package is built into the
  kernel already of the same version. (i.e. zfs-linux on Ubuntu).

  Use exact compiler for dkms as used to build the kernel, when
  possible.

  Depend on gcc-12 to build modules for HWE kernels correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1996890] Re: linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed

[Bin Li]

** Changed in: oem-priority
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu.
https://bugs.launchpad.net/bugs/1996890

Title:
  linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed

Status in OEM Priority Project:
  Invalid
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Invalid

Bug description:
  The linux-modules-nvidia-515-5.17.0-1015-oem is in a wrong dependency.
  After upgraded to latest kernel 1021-oem, the 1015-oem kernel failed to load 
the nvidia driver when boot up.

  rc  linux-modules-nvidia-515-5.17.0-1015-oem   5.17.0-1015.16 
  amd64Linux kernel nvidia modules for version 5.17.0-1015
  ii  linux-modules-nvidia-515-5.17.0-1021-oem   5.17.0-1021.22 
  amd64Linux kernel nvidia modules for version 5.17.0-1021
  ii  linux-modules-nvidia-515-oem-22.04a5.17.0-1021.22 
  amd64Extra drivers for nvidia-515 for the oem-22.04a flavour
  ii  linux-objects-nvidia-515-5.17.0-1015-oem   5.17.0-1015.16 
  amd64Linux kernel nvidia modules for version 5.17.0-1015 
(objects)
  ii  linux-objects-nvidia-515-5.17.0-1021-oem   5.17.0-1021.22 
  amd64Linux kernel nvidia modules for version 5.17.0-1021 
(objects)
  ii  linux-signatures-nvidia-5.17.0-1015-oem5.17.0-1015.16 
  amd64Linux kernel signatures for nvidia modules for version 
5.17.0-1015-oem
  ii  linux-signatures-nvidia-5.17.0-1021-oem5.17.0-1021.22 
  amd64Linux kernel signatures for nvidia modules for version 
5.17.0-1021-oem
  ii  nvidia-compute-utils-515   
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA compute utilities
  ii  nvidia-driver-515  
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA driver metapackage
  ii  nvidia-kernel-common-515   
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64Shared files used with 
the kernel module
  ii  nvidia-kernel-source-515   
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA kernel source 
package

  
  u@P360-tiny-1:~$ sudo apt install linux-modules-nvidia-515-5.17.0-1015-oem
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-modules-nvidia-515-5.17.0-1015-oem : Depends: nvidia-kernel-common-515 
(<= 515.65.01-1) but 515.76+really.515.65.01-0ubuntu0.22.04.2 is to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1996890/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1997505] [NEW] Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

[Bin Li]

Public bug reported:

If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
would like meet this issue.

1020-oem is in security channel. In jammy the unattende-upgrade will
install security fixes by default.

For the I+N platforms, the nvidia driver couldn't be installed for
1020-oem kernel, then user will meet a black screen cause of nvidia
modules couldn't be loaded.

Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESMApps:${distro_codename}-apps-security";
"${distro_id}ESM:${distro_codename}-infra-security";

** Affects: oem-priority
 Importance: Critical
 Assignee: Bin Li (binli)
 Status: In Progress

** Affects: nvidia-graphics-drivers-515 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1995563 sutton

** Description changed:

- If the GMed image used earlier kernel than 1020-oem, then you would like
- meet this issue.
+ If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
+ would like meet this issue.
  
  1020-oem is in security channel. In jammy the unattende-upgrade will
  install security fixes by default.
  
  For the I+N platforms, the nvidia driver couldn't be installed for
  1020-oem kernel, then user will meet a black screen cause of nvidia
  modules couldn't be loaded.
  
  Unattended-Upgrade::Allowed-Origins {
- "${distro_id}:${distro_codename}";
- "${distro_id}:${distro_codename}-security";
- // Extended Security Maintenance; doesn't necessarily exist for
- // every release and this system may not have it installed, but if
- // available, the policy for updates is such that unattended-upgrades
- // should also install from here by default.
- "${distro_id}ESMApps:${distro_codename}-apps-security";
- "${distro_id}ESM:${distro_codename}-infra-security";
+ "${distro_id}:${distro_codename}";
+ "${distro_id}:${distro_codename}-security";
+ // Extended Security Maintenance; doesn't necessarily exist for
+ // every release and this system may not have it installed, but if
+ // available, the policy for updates is such that unattended-upgrades
+ // should also install from here by default.
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";

** Tags added: oem-priority originate-from-1995563 sutton

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505

Title:
  Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
  would like meet this issue.

  1020-oem is in security channel. In jammy the unattende-upgrade will
  install security fixes by default.

  For the I+N platforms, the nvidia driver couldn't be installed for
  1020-oem kernel, then user will meet a black screen cause of nvidia
  modules couldn't be loaded.

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESMApps:${distro_codename}-apps-security";
  "${distro_id}ESM:${distro_codename}-infra-security";

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1996890] [NEW] linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed

[Bin Li]

Public bug reported:

The linux-modules-nvidia-515-5.17.0-1015-oem is in a wrong dependency.
After upgraded to latest kernel 1021-oem, the 1015-oem kernel failed to load 
the nvidia driver when boot up.

rc  linux-modules-nvidia-515-5.17.0-1015-oem   5.17.0-1015.16   
amd64Linux kernel nvidia modules for version 5.17.0-1015
ii  linux-modules-nvidia-515-5.17.0-1021-oem   5.17.0-1021.22   
amd64Linux kernel nvidia modules for version 5.17.0-1021
ii  linux-modules-nvidia-515-oem-22.04a5.17.0-1021.22   
amd64Extra drivers for nvidia-515 for the oem-22.04a flavour
ii  linux-objects-nvidia-515-5.17.0-1015-oem   5.17.0-1015.16   
amd64Linux kernel nvidia modules for version 5.17.0-1015 
(objects)
ii  linux-objects-nvidia-515-5.17.0-1021-oem   5.17.0-1021.22   
amd64Linux kernel nvidia modules for version 5.17.0-1021 
(objects)
ii  linux-signatures-nvidia-5.17.0-1015-oem5.17.0-1015.16   
amd64Linux kernel signatures for nvidia modules for version 
5.17.0-1015-oem
ii  linux-signatures-nvidia-5.17.0-1021-oem5.17.0-1021.22   
amd64Linux kernel signatures for nvidia modules for version 
5.17.0-1021-oem
ii  nvidia-compute-utils-515   
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA compute utilities
ii  nvidia-driver-515  
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA driver metapackage
ii  nvidia-kernel-common-515   
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64Shared files used with 
the kernel module
ii  nvidia-kernel-source-515   
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA kernel source 
package


u@P360-tiny-1:~$ sudo apt install linux-modules-nvidia-515-5.17.0-1015-oem
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-modules-nvidia-515-5.17.0-1015-oem : Depends: nvidia-kernel-common-515 
(<= 515.65.01-1) but 515.76+really.515.65.01-0ubuntu0.22.04.2 is to be installed
E: Unable to correct problems, you have held broken packages.

** Affects: oem-priority
 Importance: Critical
 Status: New

** Affects: nvidia-graphics-drivers-515 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1995563 sutton

** Package changed: nvidia-graphics-drivers-470 (Ubuntu) => nvidia-
graphics-drivers-515 (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1996890

Title:
  linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  The linux-modules-nvidia-515-5.17.0-1015-oem is in a wrong dependency.
  After upgraded to latest kernel 1021-oem, the 1015-oem kernel failed to load 
the nvidia driver when boot up.

  rc  linux-modules-nvidia-515-5.17.0-1015-oem   5.17.0-1015.16 
  amd64Linux kernel nvidia modules for version 5.17.0-1015
  ii  linux-modules-nvidia-515-5.17.0-1021-oem   5.17.0-1021.22 
  amd64Linux kernel nvidia modules for version 5.17.0-1021
  ii  linux-modules-nvidia-515-oem-22.04a5.17.0-1021.22 
  amd64Extra drivers for nvidia-515 for the oem-22.04a flavour
  ii  linux-objects-nvidia-515-5.17.0-1015-oem   5.17.0-1015.16 
  amd64Linux kernel nvidia modules for version 5.17.0-1015 
(objects)
  ii  linux-objects-nvidia-515-5.17.0-1021-oem   5.17.0-1021.22 
  amd64Linux kernel nvidia modules for version 5.17.0-1021 
(objects)
  ii  linux-signatures-nvidia-5.17.0-1015-oem5.17.0-1015.16 
  amd64Linux kernel signatures for nvidia modules for version 
5.17.0-1015-oem
  ii  linux-signatures-nvidia-5.17.0-1021-oem5.17.0-1021.22 
  amd64Linux kernel signatures for nvidia modules for version 
5.17.0-1021-oem
  ii  nvidia-compute-utils-515   
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA compute utilities
  ii  nvidia-driver-515  
515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA driver metapackage
  ii  nvidia-kernel-common-515   

[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)

[Bin Li]

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1989647

Title:
  Fix AMDGPU: No video output and system hangs with two monitor (dGPU:
  W6400)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  There's possibility that system will hang and no video output of two external 
monitor with dGPU W6400

  Monitor 1: ASUS ProArt PA238Q (FHD)
  Monitor 2: Dell P2415Q (4K)

  [Fix]
  Introduce the dmi quirk in amdgpu,
  and add dmi quirks to bypass the affected machine.

  [Test Case]
  Two ways to verify

  Method 1:
  1. Cold boot with ASUS
  2. Attach Dell monitor. ASUS is primary.
  3. Switch display mode to single ASUS
  4. Switch disaply mode back to Joing Displays. ASUS is primary

  Method 2:
  1. Cold boot with two monitors. ASUS is primary
  2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds
  3. Plug it back to DUT

  [Where problems could occur]
  Low, add a dmi quirk to bypass the target machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989647/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms

[Bin Li]

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800

-- 
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/1989046

Title:
  support independent clock and LED GPIOs for Intel IPU6 platforms

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When migrated from power_ctrl_logic driver to int3472, two additional
  independent CLK/LED GPIOs other than powerdown/reset must be probed
  exceptionally.

  [Fix]

  Vendor provided patch in
  
https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch.

  [Test Case]

  Tested on both TGL/ADL platforms against nominated kernels.

  [Where problems could occur]

  This adds exceptional cases with fallbacks to the original function. No
  one else is affected.

  [Other Info]

  This is an essential part for switching from power_ctrl_logic based GPIO
  control mechanism to the generic, upstreamed int3472 driver. Affects all
  IPU6 platforms that are to run new IPU6 driver dump in 202208.

  == original bug report ==

  Per
  
https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026
  and
  
https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2,
  additional fix for INT3472 is necessary to probe camera sensor GPIOs
  on Intel IPU6 platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989046/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

[Bin Li]

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800

-- 
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/1988797

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.14 source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  

[Kernel-packages] [Bug 1990330] Re: System hang during S3 test

[Bin Li]

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990330

Title:
  System hang during S3 test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R) 
Silver N6005 @ 2.00GHz

  [Fix]
  Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and 
found this below commit
  567511462387 mm/memcg: protect memcg_stock with a local_lock_t
  For safty, I backported the series of the patch
  https://www.spinics.net/lists/cgroups/msg31595.html
  But I still can reproduce the issue after applied those patches on top of 
5.17 oem kernel.
  So, I did a second round of bisecting and found below commit is required, too
  a74c6c00b1cb mm/memremap: avoid calling kasan_remove_zero_shadow() for device 
private memory

  [Test]
  Done the S3 test 400 times on the target and it's still working well.

  [Where problems could occur]
  Hard to evaluate the impact, but from the overnight test, the memory usage is 
still low, so there should be no memory leakage, and can't find any fix patch 
for those applied commits from upstream and linux-next trees.
  The patches are all from v5.18-rc1, so we only need them to be applied on 
oem-5.17 kernel, and will let QA to do thoroughly tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990330/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1990242] Re: Intel graphic driver is not probing[8086:468b]

[Bin Li]

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990242

Title:
  Intel graphic driver is not probing[8086:468b]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Got blank screen after entered desktop

  [Fix]
  Below commit in linux-next fixes the issue.
  6215a7c8f552 drm/i915: Add new ADL-S pci id

  [Test]
  Verified on the target machine.

  [Where problems could occur]
  It only adds an ID to the list, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990242/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1990240] Re: To support Intel Maple Ridge Thunderbolt [8086:1134]

[Bin Li]

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990240

Title:
  To support Intel Maple Ridge Thunderbolt [8086:1134]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  The TBT ID[8086:1134] the new project uses is not listed in the driver.

  [Fix]
  Intel submits this as we requested which is still in linux-next
  https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/

  [Where problems could occur]
  Adding only one ID, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990240/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged

[Bin Li]

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802

** Merge proposal unlinked:
   
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800

-- 
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/1990920

Title:
  Fix resume on AMD platforms when TBT monitor is plugged

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux 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 source package in Jammy:
  Fix Committed
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 source package in Kinetic:
  Confirmed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  When TBT monitor is connected to AMD platform, system resume will hit
  stack corruption or BUG_ON() macro.

  [Fix]
  Revert the offending commit and handle MST properly.

  [Test]
  The system can resume normally and no more kernel splat.
   
  [Where problems could occur]
  The new logic is restriced to MST hub, so normal DP/HDMI usage should be
  unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990920/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

[Bin Li]

@xaviermd,

 Thanks your feedback, the oem-sutton.newell-meta is expected, it's used
to help generate the OEM repository.

-- 
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/1990870

Title:
  Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

Status in OEM Priority Project:
  Fix Committed
Status in OEM Processes:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've 
upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and 
any “apt update” will trigger this message : 
  «««
  W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy 
trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
apt-key(8) for details.
  W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera 
pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris 
en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » 
ne dispose pas de la source « sutton.newell » (erreur de saisie dans 
sources.list ?)
  »»»

  
  (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » 
won't be used because the depot  « http://lenovo.archive.canonical.com jammy 
InRelease » doesn't have the source « sutton.newell » (mistake in sources.list 
?) »)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xavier 1608 F pulseaudio
   /dev/snd/controlC1:  xavier 1608 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-12-20 (280 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: LENOVO 20WMCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1049-oem 
root=UUID=f92a4fe4-5538-4055-9493-57eb678e2898 ro intel_iommu=on 
vfio-pci.ids=8086:4905
  ProcVersionSignature: Ubuntu 5.14.0-1049.56-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1049-oem N/A
   linux-backports-modules-5.14.0-1049-oem  N/A
   linux-firmware   20220329.git681281e4-0ubuntu3.5
  Tags:  jammy
  Uname: Linux 5.14.0-1049-oem x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (33 days ago)
 

[Kernel-packages] [Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

[Bin Li]

@xaviermd,

 Which oem package was updated? From your logs, I found you use kubuntu
while not the OEM image. 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/1990870

Title:
  Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

Status in OEM Priority Project:
  Fix Committed
Status in OEM Processes:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've 
upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and 
any “apt update” will trigger this message : 
  «««
  W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy 
trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
apt-key(8) for details.
  W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera 
pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris 
en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » 
ne dispose pas de la source « sutton.newell » (erreur de saisie dans 
sources.list ?)
  »»»

  
  (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » 
won't be used because the depot  « http://lenovo.archive.canonical.com jammy 
InRelease » doesn't have the source « sutton.newell » (mistake in sources.list 
?) »)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xavier 1608 F pulseaudio
   /dev/snd/controlC1:  xavier 1608 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-12-20 (280 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: LENOVO 20WMCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1049-oem 
root=UUID=f92a4fe4-5538-4055-9493-57eb678e2898 ro intel_iommu=on 
vfio-pci.ids=8086:4905
  ProcVersionSignature: Ubuntu 5.14.0-1049.56-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1049-oem N/A
   linux-backports-modules-5.14.0-1049-oem  N/A
   linux-firmware   20220329.git681281e4-0ubuntu3.5
  Tags:  jammy
  Uname: Linux 5.14.0-1049-oem x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (33 days ago)
  

[Kernel-packages] [Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

[Bin Li]

@xaviermd,

 This issue should be fixed now, could you help verify it again? Thanks!

 $ sudo apt update

** Changed in: oem-priority
   Status: In Progress => Fix Committed

** Tags added: originate-from-1991098 sutton

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990870

Title:
  Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

Status in OEM Priority Project:
  Fix Committed
Status in OEM Processes:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've 
upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and 
any “apt update” will trigger this message : 
  «««
  W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy 
trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
apt-key(8) for details.
  W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera 
pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris 
en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » 
ne dispose pas de la source « sutton.newell » (erreur de saisie dans 
sources.list ?)
  »»»

  
  (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » 
won't be used because the depot  « http://lenovo.archive.canonical.com jammy 
InRelease » doesn't have the source « sutton.newell » (mistake in sources.list 
?) »)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xavier 1608 F pulseaudio
   /dev/snd/controlC1:  xavier 1608 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-12-20 (280 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: LENOVO 20WMCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1049-oem 
root=UUID=f92a4fe4-5538-4055-9493-57eb678e2898 ro intel_iommu=on 
vfio-pci.ids=8086:4905
  ProcVersionSignature: Ubuntu 5.14.0-1049.56-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1049-oem N/A
   linux-backports-modules-5.14.0-1049-oem  N/A
   linux-firmware   20220329.git681281e4-0ubuntu3.5
  Tags:  jammy

[Kernel-packages] [Bug 1991036] Re: ath11k: Freezing kernel when doing s2idle [17cb:1103]

[Bin Li]

I also reported a bug in upstream.
https://bugzilla.kernel.org/show_bug.cgi?id=216434


** Tags added: originate-from-1982536

** Tags added: originate-from-1981178

** Tags added: originate-from-1981174

-- 
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/1991036

Title:
  ath11k: Freezing kernel when doing s2idle [17cb:1103]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On ubuntu 22.04, I installed v6.0-rc3 mainline kernel.
  linux-firmware 20220329.git681281e4-0ubuntu3.4

  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: PM: suspend entry (s2idle)
  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: Filesystems sync: 0.004 seconds
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing user space processes ...
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing of tasks failed after 
20.007 seconds (9 tasks refusing to freeze, wq_busy=0):
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: task:NetworkManager  state:D 
stack:0 pid:  988 ppid: 1 flags:0x4006
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Call Trace:
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __schedule+0x221/0x5c0
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule+0x5f/0x100
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule_timeout+0x111/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  wait_for_completion+0x88/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __flush_work.isra.0+0x1b9/0x340
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
flush_workqueue_prep_pwqs+0x140/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __cancel_work_timer+0x10d/0x190
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
ath11k_mac_config_mon_status_default+0x9c/0x170 [ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  cancel_work_sync+0x10/0x20
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ath11k_mac_op_stop+0x9f/0x1e0 
[ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  drv_stop+0x45/0x120 [mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop_device+0x43/0x50 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_do_stop+0x6b1/0x980 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
cond_synchronize_rcu_expedited+0x40/0x40
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? qdisc_reset+0x27/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop+0x43/0x170 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __dev_close_many+0x9f/0x120

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1991036/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991036] Re: ath11k: Freezing kernel when doing s2idle [17cb:1103]

[Bin Li]

I built a 5.17-oem kernel[1] with patch[2] and the hang issue is gone
when doing suspend, the rtnl acquire failed, no deadlock issue any more.

Sep 02 13:43:06 u-ThinkPad-P16-Gen-1 kernel: ath11k_pci :09:00.0: rtnl 
acquire failed
Sep 02 13:43:06 u-ThinkPad-P16-Gen-1 kernel: ath11k_pci :09:00.0: failed to 
perform regd update : -16


But the patch was rejected by reviewer as below comment. The reviewer previous 
patch is not a security fix. So Qualcomm Engineer submitted another patch to 
internal review.

[1] https://people.canonical.com/~binli/5.17.0-oem/
[2] 
https://patchwork.kernel.org/project/linux-wireless/patch/20220701072855.13655-1-quic_wg...@quicinc.com/

** Tags added: oem-priority originate-from-1983094 sutton

** Bug watch added: Linux Kernel Bug Tracker #216434
   https://bugzilla.kernel.org/show_bug.cgi?id=216434

-- 
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/1991036

Title:
  ath11k: Freezing kernel when doing s2idle [17cb:1103]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On ubuntu 22.04, I installed v6.0-rc3 mainline kernel.
  linux-firmware 20220329.git681281e4-0ubuntu3.4

  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: PM: suspend entry (s2idle)
  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: Filesystems sync: 0.004 seconds
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing user space processes ...
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing of tasks failed after 
20.007 seconds (9 tasks refusing to freeze, wq_busy=0):
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: task:NetworkManager  state:D 
stack:0 pid:  988 ppid: 1 flags:0x4006
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Call Trace:
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __schedule+0x221/0x5c0
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule+0x5f/0x100
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule_timeout+0x111/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  wait_for_completion+0x88/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __flush_work.isra.0+0x1b9/0x340
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
flush_workqueue_prep_pwqs+0x140/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __cancel_work_timer+0x10d/0x190
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
ath11k_mac_config_mon_status_default+0x9c/0x170 [ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  cancel_work_sync+0x10/0x20
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ath11k_mac_op_stop+0x9f/0x1e0 
[ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  drv_stop+0x45/0x120 [mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop_device+0x43/0x50 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_do_stop+0x6b1/0x980 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
cond_synchronize_rcu_expedited+0x40/0x40
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? qdisc_reset+0x27/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop+0x43/0x170 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __dev_close_many+0x9f/0x120

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1991036/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991036] [NEW] ath11k: Freezing kernel when doing s2idle [17cb:1103]

[Bin Li]

Public bug reported:

On ubuntu 22.04, I installed v6.0-rc3 mainline kernel.
linux-firmware 20220329.git681281e4-0ubuntu3.4

Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: PM: suspend entry (s2idle)
Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: Filesystems sync: 0.004 seconds
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing user space processes ...
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing of tasks failed after 
20.007 seconds (9 tasks refusing to freeze, wq_busy=0):
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: task:NetworkManager  state:D 
stack:0 pid:  988 ppid: 1 flags:0x4006
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Call Trace:
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __schedule+0x221/0x5c0
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule+0x5f/0x100
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule_timeout+0x111/0x150
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  wait_for_completion+0x88/0x140
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __flush_work.isra.0+0x1b9/0x340
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
flush_workqueue_prep_pwqs+0x140/0x140
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __cancel_work_timer+0x10d/0x190
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
ath11k_mac_config_mon_status_default+0x9c/0x170 [ath11k]
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  cancel_work_sync+0x10/0x20
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ath11k_mac_op_stop+0x9f/0x1e0 
[ath11k]
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  drv_stop+0x45/0x120 [mac80211]
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop_device+0x43/0x50 
[mac80211]
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_do_stop+0x6b1/0x980 
[mac80211]
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
cond_synchronize_rcu_expedited+0x40/0x40
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? qdisc_reset+0x27/0x150
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop+0x43/0x170 
[mac80211]
Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __dev_close_many+0x9f/0x120

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1981174 originate-from-1981178 
originate-from-1982536 originate-from-1983094 sutton

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991036

Title:
  ath11k: Freezing kernel when doing s2idle [17cb:1103]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On ubuntu 22.04, I installed v6.0-rc3 mainline kernel.
  linux-firmware 20220329.git681281e4-0ubuntu3.4

  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: PM: suspend entry (s2idle)
  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: Filesystems sync: 0.004 seconds
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing user space processes ...
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing of tasks failed after 
20.007 seconds (9 tasks refusing to freeze, wq_busy=0):
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: task:NetworkManager  state:D 
stack:0 pid:  988 ppid: 1 flags:0x4006
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Call Trace:
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __schedule+0x221/0x5c0
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule+0x5f/0x100
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule_timeout+0x111/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  wait_for_completion+0x88/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __flush_work.isra.0+0x1b9/0x340
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
flush_workqueue_prep_pwqs+0x140/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __cancel_work_timer+0x10d/0x190
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
ath11k_mac_config_mon_status_default+0x9c/0x170 [ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  cancel_work_sync+0x10/0x20
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ath11k_mac_op_stop+0x9f/0x1e0 
[ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  drv_stop+0x45/0x120 [mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop_device+0x43/0x50 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_do_stop+0x6b1/0x980 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
cond_synchronize_rcu_expedited+0x40/0x40
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? qdisc_reset+0x27/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop+0x43/0x170 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __dev_close_many+0x9f/0x120

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1991036/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

[Bin Li]

@xaviermd,

 Yes, cause we only enabled and certified this platform on 20.04, so the 
missing packages were not in 22.04.
 I will do more test and find a good way to fix it or a wiki page to explain 
this issue. 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/1990870

Title:
  Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

Status in OEM Priority Project:
  In Progress
Status in OEM Processes:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've 
upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and 
any “apt update” will trigger this message : 
  «««
  W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy 
trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
apt-key(8) for details.
  W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera 
pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris 
en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » 
ne dispose pas de la source « sutton.newell » (erreur de saisie dans 
sources.list ?)
  »»»

  
  (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » 
won't be used because the depot  « http://lenovo.archive.canonical.com jammy 
InRelease » doesn't have the source « sutton.newell » (mistake in sources.list 
?) »)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xavier 1608 F pulseaudio
   /dev/snd/controlC1:  xavier 1608 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-12-20 (280 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: LENOVO 20WMCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1049-oem 
root=UUID=f92a4fe4-5538-4055-9493-57eb678e2898 ro intel_iommu=on 
vfio-pci.ids=8086:4905
  ProcVersionSignature: Ubuntu 5.14.0-1049.56-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1049-oem N/A
   linux-backports-modules-5.14.0-1049-oem  N/A
   linux-firmware   20220329.git681281e4-0ubuntu3.5
  Tags:  jammy
  

[Kernel-packages] [Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

[Bin Li]

Here is a quick solution to fix these warnings, just remove the
oem-*-meta package from 'ubuntu-drivers list-oem'.

$ sudo ubuntu-drivers list-oem
oem-sutton.newell-aelfwine-meta
$ sudo apt purge oem-sutton.newell-aelfwine-meta
$ sudo apt update

-- 
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/1990870

Title:
  Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

Status in OEM Priority Project:
  In Progress
Status in OEM Processes:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've 
upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and 
any “apt update” will trigger this message : 
  «««
  W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy 
trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
apt-key(8) for details.
  W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera 
pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris 
en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » 
ne dispose pas de la source « sutton.newell » (erreur de saisie dans 
sources.list ?)
  »»»

  
  (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » 
won't be used because the depot  « http://lenovo.archive.canonical.com jammy 
InRelease » doesn't have the source « sutton.newell » (mistake in sources.list 
?) »)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990870/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

[Bin Li]

This issue is not related linux kernel, it's an issue of meta packages
in OEM project.

** Also affects: oemprocesses
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
   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/1990870

Title:
  Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

Status in OEM Priority Project:
  In Progress
Status in OEM Processes:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've 
upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and 
any “apt update” will trigger this message : 
  «««
  W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy 
trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in 
apt-key(8) for details.
  W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera 
pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas 
pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy 
InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie 
dans sources.list ?)
  W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris 
en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » 
ne dispose pas de la source « sutton.newell » (erreur de saisie dans 
sources.list ?)
  »»»

  
  (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » 
won't be used because the depot  « http://lenovo.archive.canonical.com jammy 
InRelease » doesn't have the source « sutton.newell » (mistake in sources.list 
?) »)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990870/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

[Bin Li]

** Tags added: originate-from-1990332

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1988797

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: 

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

[Bin Li]

** Tags added: originate-from-1976477 sutton

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1988797

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: 

[Kernel-packages] [Bug 1985901] WifiSyslog.txt

[Bin Li]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608140/+files/WifiSyslog.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] RfKill.txt

[Bin Li]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1985901/+attachment/5608138/+files/RfKill.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] UdevDb.txt

[Bin Li]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1985901/+attachment/5608139/+files/UdevDb.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] ProcEnviron.txt

[Bin Li]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608134/+files/ProcEnviron.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] ProcModules.txt

[Bin Li]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608136/+files/ProcModules.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] ProcInterrupts.txt

[Bin Li]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608135/+files/ProcInterrupts.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] acpidump.txt

[Bin Li]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608141/+files/acpidump.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] Lspci-vt.txt

[Bin Li]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608128/+files/Lspci-vt.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] PulseList.txt

[Bin Li]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608137/+files/PulseList.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] Lsusb-v.txt

[Bin Li]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608131/+files/Lsusb-v.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] Lsusb-t.txt

[Bin Li]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608130/+files/Lsusb-t.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] Lsusb.txt

[Bin Li]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1985901/+attachment/5608129/+files/Lsusb.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 

[Kernel-packages] [Bug 1985901] IwConfig.txt

[Bin Li]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608126/+files/IwConfig.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] ProcCpuinfo.txt

[Bin Li]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608132/+files/ProcCpuinfo.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] ProcCpuinfoMinimal.txt

[Bin Li]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608133/+files/ProcCpuinfoMinimal.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 

[Kernel-packages] [Bug 1985901] CurrentDmesg.txt

[Bin Li]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1985901/+attachment/5608125/+files/CurrentDmesg.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 

[Kernel-packages] [Bug 1985901] CRDA.txt

[Bin Li]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1985901/+attachment/5608124/+files/CRDA.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 

[Kernel-packages] [Bug 1985901] Lspci.txt

[Bin Li]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1985901/+attachment/5608127/+files/Lspci.txt

-- 
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/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 

[Kernel-packages] [Bug 1985901] Re: kernel hang when connecting monitor

[Bin Li]

apport information

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: linux-oem (Ubuntu) => linux-oem-5.14 (Ubuntu)

** Description changed:

- When I connected the ThinkVision 24i monitor, I found below issue.
+ When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
+ below issue.
  
  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
-  kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
+  kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
bios_parser_transmitter_control+0x1a/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dcn10_link_encoder_enable_dp_output+0x9e/0xd0 

[Kernel-packages] [Bug 1985901] Re: kernel hang when connecting monitor

[Bin Li]

5.15.0-46 has the same issue.

** Attachment added: "5.15.kernel.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985901/+attachment/5608063/+files/5.15.kernel.log

** Tags added: oem-priority originate-from-1978760 sutton

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor, I found below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  

[Kernel-packages] [Bug 1985901] Re: kernel hang when connecting monitor

[Bin Li]

** Attachment added: "kernel.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985901/+attachment/5608061/+files/kernel.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1985901

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  When I connected the ThinkVision 24i monitor, I found below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  

[Kernel-packages] [Bug 1985901] [NEW] kernel hang when connecting monitor

[Bin Li]

Public bug reported:

When I connected the ThinkVision 24i monitor, I found below issue.

Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
 kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - CPU#0 
stuck for 50s! [Xorg:1829]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm cmac 
algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 3b 
af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 08 
00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 c5 
66 90
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 EFLAGS: 
0282
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_cgs_read_register+0x14/0x20 
[amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_dm_dmub_reg_read+0x23/0x30 
[amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dc_dmub_srv_wait_idle+0x1b/0x40 
[amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
transmitter_control_v1_6+0x1af/0x1c0 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
bios_parser_transmitter_control+0x1a/0x30 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dcn10_link_encoder_enable_dp_output+0x9e/0xd0 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dcn21_link_encoder_enable_dp_output+0x19d/0x450 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dp_enable_link_phy+0x2d7/0x300 
[amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
perform_link_training_with_retries+0x114/0x290 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  enable_link_dp+0x142/0x1f0 [amdgpu]
8月 12 17:12:20 u-ThinkPad-L14-Gen-3 

[Kernel-packages] [Bug 1981922] Re: Upgrade yellow carp DMCUB firmware to fix suspend failure

[Bin Li]

Verified the issue on ThinkPad Z13/Z16/P16s Gen 1, I could suspend and
resume successfully.

** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1981922

Title:
  Upgrade yellow carp DMCUB firmware to fix suspend failure

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Certain Rembrandt designs use LPDDR memory and current firmware in 
linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on 
DC power with it.

  Some sample designs affected by the failure are Thinkpad X13, Z13,
  Z16.

  This failure doesn't affect resume with AC power or designs without
  LPDDR memory.

  [Fix]
  Upgrade yellow carp DMCUB firmware binary.

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24

  [Test]
  Verify suspend/resume works.
  Verify that externally plugged displays haven't regressed.

  [Where problems could occur]
  Firmware is only loaded to Rembrandt designs.  Regressions would be tied to 
those platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981922/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines

[Bin Li]

** Tags added: originate-from-1981169

-- 
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/1980700

Title:
  alsa: asoc: amd: the internal mic can't be dedected on yellow carp
  machines

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed

Bug description:
  The fix is already in the upstream kernel v5.19-rc1, no need to
  send the patches to unstable kernel. And for Jammy kernel, this SRU
  depends on #1949245, after merging the patchset for #1949245, then
  could apply this SRU to jammy.

  [Impact]
  On the AMD YC platforms, the internal mic can't be detected
  and there is no internal mic for users to use.

  [Fix]
  Backport 2 patches from mainline kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine which has updated BIOS, after
  loging into the desktop, open the gnome-sound-setting, there is
  internal mic, and could record sound via internal mic.

  [Where problems could occur]
  This only impacts intenal mic detection on AMD yc machines, it will
  check the acpi variable first, if not detected, it will check the acpi
  dmi table as before, so the regression possibility is very low, and we
  already tested these patches on a couple of Lenovo YC machines, all
  worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980700/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1978466] [NEW] The Ubuntu 22.04LTS Emulex driver is abnormal

[li yang]

Public bug reported:

  
When I use the Emulex card as a link to the storage and install NVMe, the OS 
Driver is abnormal and the port status of the card is abnormal

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
AlsaDevices:
 total 0
 crw-rw+ 1 root audio 116,  1 Jun 11 03:26 seq
 crw-rw+ 1 root audio 116, 33 Jun 11 03:26 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Jun 13 06:41:32 2022
InstallationDate: Installed on 2022-06-11 (2 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1604:10c0 Tascam Dell Integrated Hub
 Bus 001 Device 003: ID 1604:10c0 Tascam Dell Integrated Hub
 Bus 001 Device 002: ID 1604:10c0 Tascam Dell Integrated Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 14: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
MachineType: Dell Inc. PowerEdge MX740c
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2021
dmi.bios.release: 2.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.2
dmi.board.name: 00Y7XY
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 25
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: PowerEdge MX7000
dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.2:bd02/25/2021:br2.10:svnDellInc.:pnPowerEdgeMX740c:pvr:rvnDellInc.:rn00Y7XY:rvrA02:cvnDellInc.:ct25:cvrPowerEdgeMX7000:skuSKU=0765;ModelName=PowerEdgeMX740c:
dmi.product.family: PowerEdge
dmi.product.name: PowerEdge MX740c
dmi.product.sku: SKU=0765;ModelName=PowerEdge MX740c
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy uec-images

-- 
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/1978466

Title:
  The Ubuntu 22.04LTS Emulex driver is abnormal

Status in linux package in Ubuntu:
  New

Bug description:

  When I use the Emulex card as a link to the storage and install NVMe, the OS 
Driver is abnormal and the port status of the card is abnormal

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Jun 11 03:26 seq
   crw-rw+ 1 root audio 116, 33 Jun 11 03:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Jun 13 06:41:32 2022
  InstallationDate: Installed on 2022-06-11 (2 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam Dell Integrated Hub
   Bus 001 Device 003: ID 1604:10c0 Tascam Dell Integrated Hub
   Bus 001 Device 002: ID 1604:10c0 Tascam Dell Integrated Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 14: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ 

[Kernel-packages] [Bug 1970923] Re: [SRU][F/J] Update firmware of MT7922

[Bin Li]

Eugene had done two reboot 30 and one sleep 30 test with Fenrir-AMD-2, both
wifi and bt works well after the stress test. The kernel was 1036-oem and the 
firmware was 1.187.31.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1970923

Title:
  [SRU][F/J] Update firmware of MT7922

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  MT7922 is not stable to connect.

  [Fix]
  Update firmware of MT7922 wifi and bluetooth.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  Wifi b/g can be connected.
  iperf test result looks fine.
  Bluetooth is stable.

  [Where problems could occur]
  These firmware is specific for MT7922, it should be low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1970923/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1970451] Re: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy

[Bin Li]

** Tags added: originate-from-1969328 sutton

** Tags added: originate-from-1966833

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1970451

Title:
  Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal,
  Impish,  and Jammy

Status in OEM Priority Project:
  New
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 jammy/impish/focal/bionic ===

* New upstream release (LP: #1970451):
  - Fixed an issue where NvFBC was requesting Vulkan 1.0 while using
Vulkan 1.1 core features. This caused NvFBC to fail to initialize
with Vulkan loader versions 1.3.204 or newer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1970451/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1970923] Re: [SRU][F/J] Update firmware of MT7922

[Bin Li]

https://bugs.launchpad.net/sutton/+bug/1965460/comments/19

It should be from below commits.

commit ee439794cada7b1c26598d3e827ddb6b5b2512d6
Author: Sean Wang 
Date: Sat Apr 16 05:47:37 2022 +0800

linux-firmware: update firmware for mediatek bluetooth chip (MT7922)

Update binary firmware for MT7922 Bluetooth devices

File: mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin
Version: 20220322164155

Signed-off-by: Sean Wang 
Signed-off-by: Josh Boyer 

commit b0e1b45ea8ad8d0b8ab6342b0a30055780056af5
Author: Deren Wu 
Date: Fri Apr 15 21:30:42 2022 +0800

linux-firmware: update firmware for MT7922 WiFi device

Update binary firmware for MT7922 WiFi devices

File: mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
Version: 20220322163923a
File: mediatek/WIFI_RAM_CODE_MT7922_1.bin
Version: 20220322164011

Signed-off-by: Deren Wu 
Signed-off-by: Josh Boyer 

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1970923

Title:
   [SRU][F/J] Update firmware of MT7922

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware source package in Jammy:
  New

Bug description:
  [Impact]
  MT7922 is not stable to connect.

  [Fix]
  Update firmware of MT7922 wifi and bluetooth.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  Wifi b/g can be connected.
  iperf test result looks fine.
  Bluetooth is stable.

  [Where problems could occur]
  These firmware is specific for MT7922, it should be low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1970923/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1966061] Re: thinkpad_acpi: Support privacy-screen

[Bin Li]

** Patch removed: "5.17.0-1003.3-oem-privacy-support.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581234/+files/5.17.0-1003.3-oem-privacy-support.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/1966061

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966061/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1966061] Re: thinkpad_acpi: Support privacy-screen

[Bin Li]

In oem kernel, I found part of the 0004-drm-privacy-screen-add-
notifier.patch and 0006-thinkpad_acpi-add-hotkey-notify.patch are
missed.

commit 8a12b170558aabb31cc98fda0da6a56b518cadaa
Author: Hans de Goede 
Date:   Tue Oct 5 22:23:16 2021 +0200

drm/privacy-screen: Add notifier support (v2)

ommit 1b8101d51873d4644f0ff15f6eac46614542a76b
Author: Hans de Goede 
Date:   Tue Oct 5 22:23:18 2021 +0200

platform/x86: thinkpad_acpi: Add hotkey_notify_extended_hotkey()
helper


** Patch added: "5.17.0-1003.3-oem-privacy-support.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581234/+files/5.17.0-1003.3-oem-privacy-support.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/1966061

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966061/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1966061] Re: thinkpad_acpi: Support privacy-screen

[Bin Li]

** Patch added: "0007-thinkpad_acpi-privacy-screen.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581227/+files/0007-thinkpad_acpi-privacy-screen.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/1966061

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966061/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1966061] Re: thinkpad_acpi: Support privacy-screen

[Bin Li]

All the other patches could be applied on 5.15.0-27-generic.

-- 
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/1966061

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966061/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp