[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec

[Andy Chi]

** 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 alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1997946

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 1998882] Re: Mute/mic LEDs no function on a HP platfrom

[Andy Chi]

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

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

Title:
  Mute/mic LEDs no function on a HP platfrom

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Triaged
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Triaged
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  Apply this patch on OEM-6.0, and after applying the quirk, the audio/mic mute 
LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID

[Andy Chi]

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

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

Title:
  Add additional Mediatek MT7922 BT device ID

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

Bug description:
  [Impact]

  A Mediatek MT7922 Bluetooth doesn't work out of box.

  [Fix]

  One ID for Foxconn / Hon Hai was included in upstream, add the ID to
  support this BT device.

  [Test Case]

  Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth.
  Check BD address from output of `hciconfig`.

  [Where problems could occur]

  This brings up new devices that wasn't working. After being up and
  running, we may face some other runtime issue, e.g. power consumption.

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


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

[Kernel-packages] [Bug 1970957] Re: suspend problem

[Marco Ciampa]

I have a TUXEDO Pulse 15 Gen2 with AMD® Ryzen 7 5700u with Ubuntu 22.04.

Now it seems working with linux-image-6.1.0-1004-oem.

Previously it sometimes did not wake up or it did wake up with NVME
disks in read-only (Samsung) or did not suspend at all.

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2003164] Re: package linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101 failed to install/upgrade: installed linux-modules-nvidia-470-5.4.0-1092-oracle package post-insta

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101
  failed to install/upgrade: installed linux-modules-
  nvidia-470-5.4.0-1092-oracle package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules-oracle package in Ubuntu:
  New

Bug description:
  This error come while i update my system

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 18 12:42:03 2023
  ErrorMessage: installed linux-modules-nvidia-470-5.4.0-1092-oracle package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-08-16 (154 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: linux-restricted-modules-oracle
  Title: package linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101 
failed to install/upgrade: installed linux-modules-nvidia-470-5.4.0-1092-oracle 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oracle/+bug/2003164/+subscriptions


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

[Kernel-packages] [Bug 2003164] [NEW] package linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101 failed to install/upgrade: installed linux-modules-nvidia-470-5.4.0-1092-oracle package post-ins

[Pranav Barot]

Public bug reported:

This error come while i update my system

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jan 18 12:42:03 2023
ErrorMessage: installed linux-modules-nvidia-470-5.4.0-1092-oracle package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-08-16 (154 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: linux-restricted-modules-oracle
Title: package linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101 failed 
to install/upgrade: installed linux-modules-nvidia-470-5.4.0-1092-oracle 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-restricted-modules-oracle (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy third-party-packages

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

Title:
  package linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101
  failed to install/upgrade: installed linux-modules-
  nvidia-470-5.4.0-1092-oracle package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules-oracle package in Ubuntu:
  New

Bug description:
  This error come while i update my system

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 18 12:42:03 2023
  ErrorMessage: installed linux-modules-nvidia-470-5.4.0-1092-oracle package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-08-16 (154 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: linux-restricted-modules-oracle
  Title: package linux-modules-nvidia-470-5.4.0-1092-oracle 5.4.0-1092.101 
failed to install/upgrade: installed linux-modules-nvidia-470-5.4.0-1092-oracle 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oracle/+bug/2003164/+subscriptions


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

[Kernel-packages] [Bug 2003161] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2003161

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Jammy)
   Status: New => Incomplete

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

Title:
  Fix speaker mute hotkey doesn't work on Dell G16 series

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  Speaker mute and Mic mute hotkey no function on the G16.

  [Fix]
  speaker mute event is sent by EC then dell-wmi can't recognize it.

  Add a new keymap for KEY_MUTE.

  Send for OEM kernels first then will SRU for generic kernel once the
  patch is merged.

  [Test Case]
  1. boot-up with the kernel applied the fix.
  2. Play video/audio.
  3. Press the speak-mute hotkey
  4. can't hear any sounds.

  [Where problems could occur]
  Low, only add a keymap the affect would be very limited.

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


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

[Kernel-packages] [Bug 2003161] [NEW] Fix speaker mute hotkey doesn't work on Dell G16 series

[koba]

Public bug reported:

[Impact]
Speaker mute and Mic mute hotkey no function on the G16.

[Fix]
speaker mute event is sent by EC then dell-wmi can't recognize it.

Add a new keymap for KEY_MUTE.

Send for OEM kernels first then will SRU for generic kernel once the
patch is merged.

[Test Case]
1. boot-up with the kernel applied the fix.
2. Play video/audio.
3. Press the speak-mute hotkey
4. can't hear any sounds.

[Where problems could occur]
Low, only add a keymap the affect would be very limited.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

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

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

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

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-6.1 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress


** Tags: oem-priority originate-from-2002127 somerville

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

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

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.0 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.1 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

** Description changed:

  [Impact]
  Speaker mute and Mic mute hotkey no function on the G16.
  
  [Fix]
  speaker mute event is sent by EC then dell-wmi can't recognize it.
  
  Add a new keymap for KEY_MUTE.
+ 
+ Send for OEM kernels first then will SRU for generic kernel once the
+ patch is merged.
  
  [Test Case]
  1. boot-up with the kernel applied the fix.
  2. Play video/audio.
  3. Press the speak-mute hotkey
  4. can't hear any sounds.
  
  [Where problems could occur]
  Low, only add a keymap the affect would be very limited.

** Summary changed:

- Fix speaker mute hotkey doesn't work
+ Fix speaker mute hotkey doesn't work on Dell G16 series

** Tags added: oem-priority originate-from-2002127 somerville

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

Title:
  Fix speaker mute hotkey doesn't work on Dell G16 series

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  Speaker mute and Mic mute hotkey no function on the G16.

  [Fix]
  speaker mute event is sent by EC then dell-wmi can't recognize it.

  Add a new keymap for KEY_MUTE.

  Send for OEM kernels first then will SRU for generic kernel once the
  patch is merged.

  [Test Case]
  1. boot-up with the kernel applied the fix.
  2. Play video/audio.
  3. Press the speak-mute hotkey
  4. can't hear any sounds.

  [Where problems could occur]
  Low, only add a keymap the affect would be very limited.

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


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

[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

[Frank Heimes]

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

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * In a secure execution guest, the external interrupt for the SIGP
 external call order is delivered twice to a VCPU even though it was 
 only sent once.

   * Under PV (protected virtualization), external call interrupts are
     delivered by the SIGP interpretation facility, without KVM's
     involvement.
     But, if the receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered.
     Hence, in this case, the SIGP external call order causes
     an interception.

   * In response, KVM only needs to wake the receiving VCPU.
     Interrupt delivery is then handled by the SIGP interpretation facility.

   * KVM wrongly assumed it also needs to request injection for the
     external call interrupt after the respective intercept, causing the
     interrupt to be delivered twice:
     * once through the SIGP interpretation facility
     * and once through the interrupt injection control by KVM.

   * Solution is to add appropriate special handling for 108 external
     call intercepts.

  [Fix]

   * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
     "KVM: s390: pv: don't present the ecall interrupt twice"

  [Test Case]

   * Have an Secure Execution (PV) environment setup on an
     IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).

   * Apply kvm-unit-test submitted upstream:
     "[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
  orders in enabled wait"

   * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV

   * Check logs/smp_PV.log.
     If system is affected, the following line can be found:
     "ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
  (code 0x1202): on cpu 1 at 0x11958"

   * If the system is not affected, the line should look like this:
     "PASS: smp: psw wait: ecall: received"

  [Regression Potential / What can go wrong]

   * The handle_pv_notification can be wrong and misleading
     in case 'ret' is not handled correctly.

   * trace_kvm_s390_handle_sigp_pei might not be called correctly,
     now after the if condition.

   * In worst case the external interrupt could not be delivered
     at all or still too often.

  [Other]

   * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
     so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
     and 22.10/5.19.

   * But the patch got properly tagged for upstream stable:
     Cc:  # 5.7
     Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

   * And with that it got already picked up and is included in:
     22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
     22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.

   * So the only Ubuntu release that is affected is 20.04/focal.
  __

  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the
     SIGP external call order is delivered twice to a VCPU even
     though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
     interpretation facility, without KVM's involvement. But, if the
     receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered. Hence,
     in this case, the SIGP external call order causes an
     interception. In response, KVM only needs to wake the receiving
     VCPU. Interrupt delivery is then handled by the SIGP
     interpretation facility.

     KVM wrongfuly assumed it also needs to request injection for 
the
     external call interrupt after the respective intercept, causing
     the interrupt to be delivered twice: once through the SIGP
     interpretation facility and once through the interrupt 
injection
     control by KVM.
  Solution:  Add appropriate special handling for 108 external call
     intercepts.
  Reproduction:  0. Apply kvm-unit-test submitted upstream
    ("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
    call orders in enabled wait").
     1. Run the smp_PV kvm-unit-test:
  ./run_tests.sh smp_PV
     2. 

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions


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

[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup

[AceLan Kao]

** Description changed:

  [Impact]
  The commit in 5.17.0.1026.27 introduce an regression that leads to the panel 
of ThinkPad L14 Gen 3 becomes blank after bootup
  224dffc89a957 drm/amdgpu: make sure to init common IP before gmc
  
  [Fix]
  Revert this commit as it looks like it requires some other commits to work 
together, and from the discussion of the 5.10 stable, this commit has been 
reverted, too.
  https://gitlab.freedesktop.org/drm/amd/-/issues/2216
+ 
+ BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with
+ this commit, so no need to revert it.
  
  [Test]
  Verified by Aaron Ma.
  
  [Where problems could occur]
  Revert this commit will lead to the keep rebooting issue be re-opened(bug 
2000110), I'll check the issue again and submit another solution for it.
  
  
  
  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank
  shortly after bootup.
  
  As far as I can tell (the screen blanks pretty quickly, so I'm not 100%
  sure), the last message before the screen disappears is this one:
  
  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA
  
  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in the
  framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
  
  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.
  
  If I type the encryption password, it seems to progress to starting the
  system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

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

Title:
  ThinkPad L14 Gen 3 blank laptop screen on bootup

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Triaged

Bug description:
  [Impact]
  The commit in 5.17.0.1026.27 introduce an regression that leads to the panel 
of ThinkPad L14 Gen 3 becomes blank after bootup
  224dffc89a957 drm/amdgpu: make sure to init common IP before gmc

  [Fix]
  Revert this commit as it looks like it requires some other commits to work 
together, and from the discussion of the 5.10 stable, this commit has been 
reverted, too.
  https://gitlab.freedesktop.org/drm/amd/-/issues/2216

  BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with
  this commit, so no need to revert it.

  [Test]
  Verified by Aaron Ma.

  [Where problems could occur]
  Revert this commit will lead to the keep rebooting issue be re-opened(bug 
2000110), I'll check the issue again and submit another solution for it.

  

  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
  blank shortly after bootup.

  As far as I can tell (the screen blanks pretty quickly, so I'm not
  100% sure), the last message before the screen disappears is this one:

  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA

  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in
  the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
  5.17.0.1026.27.

  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.

  If I type the encryption password, it seems to progress to starting
  the system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

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


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

[Kernel-packages] [Bug 2003140] Re: Ubuntu laptop can't use external monitors

[Daniel van Vugt]

Finally, if you were to install Ubuntu again then we recommend version
22.04.1 more than 20.04.3 which you have here.

https://ubuntu.com/download/desktop

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

Title:
  Ubuntu laptop can't use external monitors

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid

Bug description:
  # What happens (Steps to reproduce):
  1. Install a clean version of Ubuntu onto a laptop:
  
Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us;
  VERSION="20.04.5 LTS (Focal Fossa)"
  nick@Precision-3541:~$ sudo lshw -C display
  [sudo] password for nick:
    *-display
     description: 3D controller
     product: GP107GLM [Quadro P620]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:01:00.0
     version: a1
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list rom
     configuration: driver=nvidia latency=0
     resources: irq:168 memory:ec00-ecff memory:c000-cfff 
memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07
    *-display
     description: VGA compatible controller
     product: UHD Graphics 630 (Mobile)
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:166 memory:eb00-ebff memory:8000-8fff 
ioport:4000(size=64) memory:c-d

  2. Connect a monitor and laptop with an HDMI cable
  3. Result
  - The monitor should display "No Signal"
  - Ubuntu should recognize the monitor, but not display anything on it.

  # What should happen
  Ubuntu should send signal to external monitors connected to the HDMI port. It 
should automatically configure discrete graphics cards. The same hardware works 
when booted from the Windows partition.

  # What I've tried
  ## Things that worked
  None

  ## Things that worked temporarily
  
https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579

  Installing NVidia-Prime, Setting "Performance Mode" to always use the
  discrete GPU

  ## Things that did not work (from various forums)
  1. Using multiple different drivers via "Software/Additional Drivers"
  2. Using the driver from NVidia's website
  3. Enabling NVidia via a modprob parameter at startup
  4. Varius xorg configuration files

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.161.03  Wed Oct 19 
00:10:36 UTC 2022
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 17 16:58:33 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
     Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a]
     Subsystem: Dell GP107GLM [Quadro P620] [1028:091a]
  InstallationDate: Installed on 2023-01-06 (11 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Precision 3541
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:

  dmi.bios.date: 09/13/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 0Y8H01
  

[Kernel-packages] [Bug 2003140] Re: Ubuntu laptop can't use external monitors

[Daniel van Vugt]

nvidia-installer.log.txt suggests the broken driver here was manually
installed and did not come from Ubuntu. So that makes this bug "Invalid"
for Ubuntu, but please continue to report new bugs about any additional
issues you encounter.


** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Ubuntu laptop can't use external monitors

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid

Bug description:
  # What happens (Steps to reproduce):
  1. Install a clean version of Ubuntu onto a laptop:
  
Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us;
  VERSION="20.04.5 LTS (Focal Fossa)"
  nick@Precision-3541:~$ sudo lshw -C display
  [sudo] password for nick:
    *-display
     description: 3D controller
     product: GP107GLM [Quadro P620]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:01:00.0
     version: a1
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list rom
     configuration: driver=nvidia latency=0
     resources: irq:168 memory:ec00-ecff memory:c000-cfff 
memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07
    *-display
     description: VGA compatible controller
     product: UHD Graphics 630 (Mobile)
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:166 memory:eb00-ebff memory:8000-8fff 
ioport:4000(size=64) memory:c-d

  2. Connect a monitor and laptop with an HDMI cable
  3. Result
  - The monitor should display "No Signal"
  - Ubuntu should recognize the monitor, but not display anything on it.

  # What should happen
  Ubuntu should send signal to external monitors connected to the HDMI port. It 
should automatically configure discrete graphics cards. The same hardware works 
when booted from the Windows partition.

  # What I've tried
  ## Things that worked
  None

  ## Things that worked temporarily
  
https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579

  Installing NVidia-Prime, Setting "Performance Mode" to always use the
  discrete GPU

  ## Things that did not work (from various forums)
  1. Using multiple different drivers via "Software/Additional Drivers"
  2. Using the driver from NVidia's website
  3. Enabling NVidia via a modprob parameter at startup
  4. Varius xorg configuration files

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.161.03  Wed Oct 19 
00:10:36 UTC 2022
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 17 16:58:33 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
     Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a]
     Subsystem: Dell GP107GLM [Quadro P620] [1028:091a]
  InstallationDate: Installed on 2023-01-06 (11 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Precision 3541
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh 

[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup

[AceLan Kao]

** Description changed:

+ [Impact]
+ The commit in 5.17.0.1026.27 introduce an regression that leads to the panel 
of ThinkPad L14 Gen 3 becomes blank after bootup
+ 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc
+ 
+ [Fix]
+ Revert this commit as it looks like it requires some other commits to work 
together, and from the discussion of the 5.10 stable, this commit has been 
reverted, too.
+ https://gitlab.freedesktop.org/drm/amd/-/issues/2216
+ 
+ [Test]
+ Verified by Aaron Ma.
+ 
+ [Where problems could occur]
+ Revert this commit will lead to the keep rebooting issue be re-opened(bug 
2000110), I'll check the issue again and submit another solution for it.
+ 
+ 
+ 
  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank
  shortly after bootup.
  
  As far as I can tell (the screen blanks pretty quickly, so I'm not 100%
  sure), the last message before the screen disappears is this one:
  
  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA
  
  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in the
  framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
  
  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.
  
  If I type the encryption password, it seems to progress to starting the
  system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

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

Title:
  ThinkPad L14 Gen 3 blank laptop screen on bootup

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Triaged

Bug description:
  [Impact]
  The commit in 5.17.0.1026.27 introduce an regression that leads to the panel 
of ThinkPad L14 Gen 3 becomes blank after bootup
  224dffc89a957 drm/amdgpu: make sure to init common IP before gmc

  [Fix]
  Revert this commit as it looks like it requires some other commits to work 
together, and from the discussion of the 5.10 stable, this commit has been 
reverted, too.
  https://gitlab.freedesktop.org/drm/amd/-/issues/2216

  [Test]
  Verified by Aaron Ma.

  [Where problems could occur]
  Revert this commit will lead to the keep rebooting issue be re-opened(bug 
2000110), I'll check the issue again and submit another solution for it.

  

  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
  blank shortly after bootup.

  As far as I can tell (the screen blanks pretty quickly, so I'm not
  100% sure), the last message before the screen disappears is this one:

  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA

  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in
  the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
  5.17.0.1026.27.

  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.

  If I type the encryption password, it seems to progress to starting
  the system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

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


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

[Kernel-packages] [Bug 2003140] Re: Ubuntu laptop can't use external monitors

[Daniel van Vugt]

Thanks for the bug report.

The Nvidia Xorg driver doesn't appear to be loading for some reason,
which is the main problem. Although the Nvidia kernel driver is loaded.

You are using Nvidia driver version 470.161.03 but their website
suggests the current supported version for your Quadro P620 is
525.78.01. But regardless of version, it looks like the issue here is a
failed installation of the Xorg driver. And the bug reporting system is
suggesting you might have tried a manual driver installation in the past
too.

To fix this, please open the 'Additional Drivers' app and use it to
install a newer Nvidia driver. Please do not attempt to install drivers
manually without using the Additional Drivers app because doing so can
lead to bugs like this one.

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: New => Incomplete

** Tags added: multimonitor nvidia

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

Title:
  Ubuntu laptop can't use external monitors

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  # What happens (Steps to reproduce):
  1. Install a clean version of Ubuntu onto a laptop:
  
Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us;
  VERSION="20.04.5 LTS (Focal Fossa)"
  nick@Precision-3541:~$ sudo lshw -C display
  [sudo] password for nick:
    *-display
     description: 3D controller
     product: GP107GLM [Quadro P620]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:01:00.0
     version: a1
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list rom
     configuration: driver=nvidia latency=0
     resources: irq:168 memory:ec00-ecff memory:c000-cfff 
memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07
    *-display
     description: VGA compatible controller
     product: UHD Graphics 630 (Mobile)
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:166 memory:eb00-ebff memory:8000-8fff 
ioport:4000(size=64) memory:c-d

  2. Connect a monitor and laptop with an HDMI cable
  3. Result
  - The monitor should display "No Signal"
  - Ubuntu should recognize the monitor, but not display anything on it.

  # What should happen
  Ubuntu should send signal to external monitors connected to the HDMI port. It 
should automatically configure discrete graphics cards. The same hardware works 
when booted from the Windows partition.

  # What I've tried
  ## Things that worked
  None

  ## Things that worked temporarily
  
https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579

  Installing NVidia-Prime, Setting "Performance Mode" to always use the
  discrete GPU

  ## Things that did not work (from various forums)
  1. Using multiple different drivers via "Software/Additional Drivers"
  2. Using the driver from NVidia's website
  3. Enabling NVidia via a modprob parameter at startup
  4. Varius xorg configuration files

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.161.03  Wed Oct 19 
00:10:36 UTC 2022
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 17 16:58:33 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] 

[Kernel-packages] [Bug 2003140] [NEW] Ubuntu laptop can't use external monitors

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

# What happens (Steps to reproduce):
1. Install a clean version of Ubuntu onto a laptop:
Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us;
VERSION="20.04.5 LTS (Focal Fossa)"
nick@Precision-3541:~$ sudo lshw -C display
[sudo] password for nick:
  *-display
   description: 3D controller
   product: GP107GLM [Quadro P620]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list rom
   configuration: driver=nvidia latency=0
   resources: irq:168 memory:ec00-ecff memory:c000-cfff 
memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07
  *-display
   description: VGA compatible controller
   product: UHD Graphics 630 (Mobile)
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:166 memory:eb00-ebff memory:8000-8fff 
ioport:4000(size=64) memory:c-d

2. Connect a monitor and laptop with an HDMI cable
3. Result
- The monitor should display "No Signal"
- Ubuntu should recognize the monitor, but not display anything on it.

# What should happen
Ubuntu should send signal to external monitors connected to the HDMI port. It 
should automatically configure discrete graphics cards. The same hardware works 
when booted from the Windows partition.

# What I've tried
## Things that worked
None

## Things that worked temporarily
https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579

Installing NVidia-Prime, Setting "Performance Mode" to always use the
discrete GPU

## Things that did not work (from various forums)
1. Using multiple different drivers via "Software/Additional Drivers"
2. Using the driver from NVidia's website
3. Enabling NVidia via a modprob parameter at startup
4. Varius xorg configuration files

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.161.03  Wed Oct 19 
00:10:36 UTC 2022
 GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 17 16:58:33 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a]
   Subsystem: Dell GP107GLM [Quadro P620] [1028:091a]
InstallationDate: Installed on 2023-01-06 (11 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Dell Inc. Precision 3541
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:

dmi.bios.date: 09/13/2022
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0Y8H01
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd09/13/2022:br1.23:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A:
dmi.product.family: Precision
dmi.product.name: Precision 3541
dmi.product.sku: 091A
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: 

[Kernel-packages] [Bug 2002689] Re: mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3 SoC

[Liming Sun]

Tim,  Thanks for the code review. I got the Acked-by email but haven't seen it 
in the jammy repo yet.
Do you know when this change might be pushed?

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

Title:
  mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3
  SoC

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  In Progress

Bug description:
  
  SRU Justification:

  [Impact]

  
  This is a porting commit from 
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253.

  
  [Fix]
  * N/A

  [Test Case]
  * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' 
from external rshim driver.
The rshim MAC address will show up.

  # cat /dev/rshim0/misc
  DISPLAY_LEVEL 1 (0:basic, 1:advanced, 2:log)
  BOOT_MODE 1 (0:rshim, 1:emmc, 2:emmc-boot-swap)
  BOOT_TIMEOUT 100 (seconds)
  DROP_MODE 0 (0:normal, 1:drop)
  SW_RESET 0 (1: reset)
  DEV_NAME usb-1-1.1
  DEV_INFO BlueField-2(Rev 0)
  OPN_STR MBF2M516A-EEEO
  BOOT_RESET_SKIP 0 (1: skip)
  PEER_MAC 00:1a:ca:ff:ff:01 (rw)
  PXE_ID 0x (rw)
  VLAN_ID 0 0 (rw)
  * echo "PEER_MAC xx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the MAC 
address, which will take effect in next boot.

  [Regression Potential]
  * This is a new enhancement and is backward-compatible with previous behavior.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-ibm/5.15.0.1024.20)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-ibm (5.15.0.1024.20) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.35-0ubuntu3.1 (amd64)
linux-ibm/5.15.0-1024.27 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-ibm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 2002385] Re: Memory error while booting

[Russ W]

Might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320

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

Title:
  Memory error while booting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just installed  ¨LinuxMint Vera Xfce" again after getting probably
  the same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
  amd64.iso) I tried out to get an external HDMI/VDI monitor working on
  my laptop.

  All worked fine with the default "Nouveau" video driver installed. I
  tried some xandr settings to check my external HDMI monitor, which
  basically worked. Then I noticed only the Nouveau driver was
  installed. I upgraded to the official (recommended by LinuxMint)
  NVidia-driver-525, did the compulsary reboot and got stuck with an
  "out of memory error" during that reboot (I don´t recall the literal
  message but something like that it was). The only option I had
  (because the install-USB oviously came with it) was choosing to boot
  with the previous 5.15.0-56 kernel which to my relief worked. After
  this boot I reverted to the Nouveau video driver and installed Kernel
  5.15.0-57 again. So far this works, but I dare not install the
  official NVidia-driver-525 again.

  I don´t know if this is important, but so far I have no
  /etc/X11/xorg.conf file in place. I'm still trying to find out what a
  working configuration for my laptop with a secondary external IIyama
  screen is.

  I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD
  boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is
  also far from fully developed it seems) with secure boot disabled.

  b.t.w. It seems I cannot add more than one attachment to this report.

  Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74

  1) lsb_release -rd:  Description: Linux Mint 21.1
    Release:21.1
  2) n.a.
  3) I expected to happen: flawless reboot
  4) What happened instead: boot got stuck on a out of memory error.

  Extra info: default-display-manager (file in /etc/X11/): /usr/sbin/lightdm
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scutec 3996 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 21.1
  InstallationDate: Installed on 2023-01-09 (0 days ago)
  InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217
  MachineType: Acer Aspire VN7-792G
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=fc2964e7-baed-4419-a709-e3fb79bc9e17 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  vera
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2016
  dmi.bios.release: 1.9
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd05/17/2016:br1.9:efr1.5:svnAcer:pnAspireVN7-792G:pvrV1.09:rvnAcer:rnAspireVN7-792G:rvrV1.09:cvnAcer:ct10:cvrV1.09:skuAspireVN7-792G_103B_1.09:
  dmi.product.family: SKL
  dmi.product.name: Aspire VN7-792G
  dmi.product.sku: Aspire VN7-792G_103B_1.09
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 2002968] Re: Fix flicker display problem on some panels which support PSR2

[Chris Chiu]

** Tags added: originate-from-2001736

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

Title:
  Fix flicker display problem on some panels which support PSR2

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Incomplete
Status in linux-oem-6.0 source package in Lunar:
  New
Status in linux-oem-6.1 source package in Lunar:
  New

Bug description:
  [Impact]
  On some PSR2 supported panels, which connects to Intel Graphics has flicker 
symptom. It gets normal after booting the kernel with parameter `i915. 
enable_psr=0`

  [Fix]
  Backport one patch from upstream. 
https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_psr.c?id=084aab04cc60e5eab32287d0483c33e12c92da87

  [Test]
  Booting the patched kernel with problematic panel (LGD LCD_VD78M), check if 
the display has abnormal flickering problem on graphics interfaces.

  [Where problems could occur]
  The risk of regression is low. It only fixes problem on panels which support 
PSR2.

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


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

[Kernel-packages] [Bug 2001605] Re: Add support for SEV-SNP

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-gcp/5.15.0-1028.35
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gcp verification-needed-jammy

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

Title:
  Add support for SEV-SNP

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  Fix Committed

Bug description:
  Version 3 of AMD's Secure Encrypted Virtualization is called SNP
  (Secure Nested Pages). Support for this has been added to the kernel,
  mostly in v5.19 with some prerequisites from v5.16. This feature is
  requested to be backported to Jammy (5.15).

  More information at
  https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view

  
  [Impact]
  No support for SEV-SNP on AMD EPYC2 CPUs currently

  [Fix]
  Add SEV-SNP support patches.

  [Test]
  Extensive testing by the cloud team over several months, testing general 
functionality under SEV-SNP.

  [Regression Potential]
  This was never working so there should be no risk of regression for 
SEV-SNP.As it does change those files it can have an effect on existing SEV 
functionality in case of a bug. The code is limited so no regression outside of 
SEV is expected.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1032.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1032.28) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

digimend-dkms/10-4 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9

[Po-Hsu Lin]

Hint removed, marking this as Fix-released in U-K-T

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

Title:
  BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from
  ubuntu_kernel_selftests failed on K-5.19 P9

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related 
tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are 
not supported.

   test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 
0x02
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to 
select_runtime err=-524
   ...
   test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to 
select_runtime err=-524
   ...
   test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed]

  Please find attachment for the complete test log.

  [Fix]
  * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations
  * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations
  * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg
  These patches can be cherry-picked into Kinetic kernel.

  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/

  Steps:
  1. Reboot with the patched kernel
  2. Run:
    sudo dmesg -C
    sudo modprobe test_bpf
    sudo dmesg

  Tested with Power9 node baltar, with the patched kernel there will be no 
failure reported by the test_bpf:
    test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed]

  [Where problems could occur]
  This patchset just broaden the BPF operations support on ppc64, we might see 
some new failures when using these instruction somewhere in the future.

  Cascardo: The existing atomic operations may regress as well, since
  they now produce different code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+subscriptions


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

[Kernel-packages] [Bug 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9

[Po-Hsu Lin]

Test passed with Kinetic linux/5.19.0-30.31 on P9 node "baltar":
test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed]
test_bpf: test_tail_calls: Summary: 10 PASSED, 0 FAILED, [10/10 JIT'ed]
test_bpf: test_skb_segment: Summary: 2 PASSED, 0 FAILED

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

** Changed in: ubuntu-kernel-tests
   Status: In Progress => 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/2001618

Title:
  BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from
  ubuntu_kernel_selftests failed on K-5.19 P9

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related 
tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are 
not supported.

   test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 
0x02
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to 
select_runtime err=-524
   ...
   test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to 
select_runtime err=-524
   ...
   test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed]

  Please find attachment for the complete test log.

  [Fix]
  * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations
  * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations
  * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg
  These patches can be cherry-picked into Kinetic kernel.

  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/

  Steps:
  1. Reboot with the patched kernel
  2. Run:
    sudo dmesg -C
    sudo modprobe test_bpf
    sudo dmesg

  Tested with Power9 node baltar, with the patched kernel there will be no 
failure reported by the test_bpf:
    test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed]

  [Where problems could occur]
  This patchset just broaden the BPF operations support on ppc64, we might see 
some new failures when using these instruction somewhere in the future.

  Cascardo: The existing atomic operations may regress as well, since
  they now produce different code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+subscriptions


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

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

[Daniel van Vugt]

Comment #8 is a crash in the 'nouveau' kernel driver unrelated to this
bug. Although you should technically report a new bug for that,
'nouveau' is not very well maintained and we would always just recommend
using the 'Additional Drivers' app to install one of the official Nvidia
drivers instead.

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

[Daniel van Vugt]

Please report all issues not relating to "adding CRTC not allowed
without modesets" as new bugs.

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup

[AceLan Kao]

Hi Paul,

Aaron has found the bad commit which is 
224dffc89a957 drm/amdgpu: make sure to init common IP before gmc

I've updated the test kernel at the same location which reverted the commit.
https://people.canonical.com/~acelan/bugs/lp2002467/

I'm going to submit SRU to revert this one, please help to verify it,
thanks.

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

Title:
  ThinkPad L14 Gen 3 blank laptop screen on bootup

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Triaged

Bug description:
  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
  blank shortly after bootup.

  As far as I can tell (the screen blanks pretty quickly, so I'm not
  100% sure), the last message before the screen disappears is this one:

  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA

  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in
  the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
  5.17.0.1026.27.

  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.

  If I type the encryption password, it seems to progress to starting
  the system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

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


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

[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops

[Andy Chi]

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

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

Title:
  Mic Mute LED doesn't work on DMIC laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Mic mute LED doesn't work on Intel-based HP laptops.

  [Fix]
  Due to recent change on how kernel creates sound LEDs, there are two captures 
are registered, one from SoF and one from HDA. The SoF one is the "real" 
capture system uses.

  Since physical LED only gets light up when _all_ captures are muted,
  detach the HDA one so micmute LED only need to consider SoF capture's
  mute status.

  [Test]
  The mic mute LED works again on DMIC laptops.

  The legacy HDA systems are unaffected.

  [Where problems could occur]
  Theoretically the system may have more than two internal captures registered, 
then disabling one will not be enough.

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


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

[Kernel-packages] [Bug 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28

[Po-Hsu Lin]

Test passed with Kinetic linux-azure/5.19.0-1017.18

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

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

Title:
  mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on
  kinetic/linux 5.19.0-27.28

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all
  instances.

  Running tests...
  vma05 1 TINFO: timeout per run is 0h 5m 0s
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none
  
  Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents 
look like this:

  vma05 1 TPASS: [vsyscall] reported correctly
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 418325]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  __pthread_kill_implementation (no_tid=0, signo=11,
  threadid=) at ./nptl/pthread_kill.c:44

  Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
  #0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
  #3  0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
  #4  0x55f54287a072 in main () at vma05_vdso.c:5
  vma05 1 TPASS: [vdso] backtrace complete
  --
  while on 5.19.0-27.28 it looks like this:
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 1501]
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9b3c09226b in ?? ()

  Thread 1 (LWP 1501):
  #0  0x7f9b3c09226b in ?? ()
  Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none

  Suggesting that this bug has somehow been reintroduced. Will look into
  this further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+subscriptions


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

[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup

[AceLan Kao]

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

Title:
  ThinkPad L14 Gen 3 blank laptop screen on bootup

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Triaged

Bug description:
  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
  blank shortly after bootup.

  As far as I can tell (the screen blanks pretty quickly, so I'm not
  100% sure), the last message before the screen disappears is this one:

  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA

  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in
  the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
  5.17.0.1026.27.

  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.

  If I type the encryption password, it seems to progress to starting
  the system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

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


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

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

[beadon]

Should I open this as a different issue with the Core X Chroma
Thunderbolt 3 enclosure ?  It's very similar.

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

[beadon]

Ok, I am getting a slightly different, but perhaps related problem with
another USB-C / eGPU encapsulation (PCIE tunneles over USB-C basically)
device.

I've done some testing with the Razer Core X Chroma, a USB-C connected
Thunderbolt 3 eGPU enclosure.  Reference to hardware is here :
https://www.razer.com/gaming-egpus/Razer-Core-X/RC21-01430100-R3U1

I have 2x displays now connected to the internal PCIE nVidia TU117
[GeForce GTX 1650] loaded in the unit.  The BIOS seems to work fine, ,
but when I get to the gnome login screen things hang.  I am narrowing it
down, but just like the display blanking on the Intel based on cursor
location, I am seeing the same behavior with this enclosure - if at boot
time the enclosure is connected, then the displays will lock up.  If, I
move the mouse to the right edge of the screen , the desktop will also
lock up.

Attached are the logs of the attachment, then detachment of this
enclosure.  Note that on re-attaching the enclosure the USB devices
which previously worked fine attached to the enclosure no longer
function (perhaps not deregistered properly?).


Details for HW info

beadon@semiauto:~$ hwinfo --gfxcard --short
graphics card:  
   nVidia TU117 [GeForce GTX 1650]
   Intel TigerLake-LP GT2 [Iris Xe Graphics]

Primary display adapter: #26





** Attachment added: "log-for-chroma.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003031/+attachment/5642118/+files/log-for-chroma.txt

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1102.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-azure

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

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

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


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

[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1102.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  md: Replace snprintf with scnprintf

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1102.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * In a secure execution guest, the external interrupt for the SIGP
 external call order is delivered twice to a VCPU even though it was 
 only sent once.

   * Under PV (protected virtualization), external call interrupts are
     delivered by the SIGP interpretation facility, without KVM's
     involvement.
     But, if the receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered.
     Hence, in this case, the SIGP external call order causes
     an interception.

   * In response, KVM only needs to wake the receiving VCPU.
     Interrupt delivery is then handled by the SIGP interpretation facility.

   * KVM wrongly assumed it also needs to request injection for the
     external call interrupt after the respective intercept, causing the
     interrupt to be delivered twice:
     * once through the SIGP interpretation facility
     * and once through the interrupt injection control by KVM.

   * Solution is to add appropriate special handling for 108 external
     call intercepts.

  [Fix]

   * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
     "KVM: s390: pv: don't present the ecall interrupt twice"

  [Test Case]

   * Have an Secure Execution (PV) environment setup on an
     IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).

   * Apply kvm-unit-test submitted upstream:
     "[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
  orders in enabled wait"

   * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV

   * Check logs/smp_PV.log.
     If system is affected, the following line can be found:
     "ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
  (code 0x1202): on cpu 1 at 0x11958"

   * If the system is not affected, the line should look like this:
     "PASS: smp: psw wait: ecall: received"

  [Regression Potential / What can go wrong]

   * The handle_pv_notification can be wrong and misleading
     in case 'ret' is not handled correctly.

   * trace_kvm_s390_handle_sigp_pei might not be called correctly,
     now after the if condition.

   * In worst case the external interrupt could not be delivered
     at all or still too often.

  [Other]

   * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
     so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
     and 22.10/5.19.

   * But the patch got properly tagged for upstream stable:
     Cc:  # 5.7
     Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

   * And with that it got already picked up and is included in:
     22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
     22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.

   * So the only Ubuntu release that is affected is 20.04/focal.
  __

  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the
     SIGP external call order is delivered twice to a VCPU even
     though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
     interpretation facility, without KVM's involvement. But, if the
     receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered. Hence,
     in this case, the SIGP external call order causes an
     interception. In response, KVM only needs to wake the receiving
     VCPU. Interrupt delivery is then handled by the SIGP
     interpretation facility.

     KVM wrongfuly assumed it also needs to request injection for 
the
     

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1102.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions


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

[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1102.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-azure

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

Title:
  Fix rfkill causing soft blocked wifi

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Need this patch in so a BIOS upgrade won't cause issues on HP laptops.

  commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a
  Author: Jorge Lopez 
  Date:   Fri Oct 28 10:55:27 2022 -0500

   platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded
  strange char "^@" which printed out every second and makes login
  nearly impossible. Also the below messages were shown both in console
  and journal/dmesg every second:

  usb 1-3: Device not responding to setup address.
  usb 1-3: device not accepting address 4, error -71
  usb 1-3: device descriptor read/all, error -71
  usb usb1-port3: unable to enumerate USB device

  Wifi is soft blocked by checking rfkill. When unblocked manually,
  after few seconds it would be soft blocked again. So I was suspecting
  something triggered rfkill to soft block wifi.  At the end it was
  fixed by removing hp_wmi module.

  The root cause is the way hp-wmi driver handles command 1B on
  post-2009 BIOS.  In pre-2009 BIOS, command 1Bh return 0x4 to indicate
  that BIOS no longer controls the power for the wireless devices.

  Signed-off-by: Jorge Lopez 
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468
  Reviewed-by: Mario Limonciello 
  Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com
  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede 
  Signed-off-by: Hans de Goede 

  [Test case]

  test on a HP laptop with the new BIOS

  [Where problems could occur]

  from the commit:
    * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that
    * BIOS no longer controls the power for the wireless
    * devices. All features supported by this command will no
    * longer be supported.

  anyone running a laptop with obsolete pre-2009 BIOS probably won't
  notice the missing feature at this point.

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


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

[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1102.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-azure

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

Title:
  Expose built-in trusted and revoked certificates

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [ Impact ]

   * Kernels have a set of builtin trusted and revoked certificates as a bundle
   * It is not very easy to access them, one needs to either download linux 
kernel package source code; or boot the kernel look up builtin hashes; and then 
find certificates externally
   * It would be more convenient for inspection to expose these in the 
buildinfo package, which already exposes auxiliary kernel information

  [ Test Plan ]

   * sudo apt install linux-buildinfo-$(uname -r)
   * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and 
contains livepatch cert
   * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists 
and contains 2012 cert

  Example output:
  $ grep Subject: -r usr/lib/linux
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = 
Canonical Ltd. Live Patch Signing
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, 
ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel 
Module Signing
  usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: 
C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical 
Ltd. Secure Boot Signing

  
  [ Where problems could occur ]

   * buildinfo is an auxiliary package not installed by default, but
  used by developer tooling and packaging.

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


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

[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup

[Paul Gear]

Unfortunately, the 5.17.0-2026.27 kernel removing commit
d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a did not resolve the problem -
it exhibits the same display blanking characteristics on the ThinkPad
L14 Gen3 AMD as the signed release 5.17.0-1026-oem does.  Boot log for
this kernel attached.

** Attachment added: "kern.log-5.17.0-2026-oem"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5642117/+files/kern.log-5.17.0-2026-oem

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

Title:
  ThinkPad L14 Gen 3 blank laptop screen on bootup

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Triaged

Bug description:
  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
  blank shortly after bootup.

  As far as I can tell (the screen blanks pretty quickly, so I'm not
  100% sure), the last message before the screen disappears is this one:

  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA

  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in
  the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
  5.17.0.1026.27.

  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.

  If I type the encryption password, it seems to progress to starting
  the system (the microphone mute LED comes on as expected), but even X
  starting does not turn the screen back on.  Switching to the frame
  buffer console with Ctrl-Alt-Fx does nothing.

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


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

[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"

[beadon]

I am seeing this issue in Ubuntu 22.10 , specifically for a Razer
Deathadder mouse :

Jan 17 17:59:28 semiauto /usr/libexec/gdm-x-session[2147]: (EE) event20
- Razer Razer DeathAdder: client bug: event processing lagging behind by
24ms, your system is too slow


Which information do you need to troubleshoot further ?

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

Title:
  libinput says "your system is too slow"

Status in GNOME Shell:
  Fix Released
Status in libinput:
  Fix Released
Status in Linux:
  Confirmed
Status in libinput package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:

  During the freeze, the output of the install had a message from "gdm-
  x-session" saying "your system is too slow".

  To reproduce:
  1. Launch the Ubuntu installer
  2. Begin the installation process
  3. When the installation process begins, move the cursor around
  4. Notice how the PC freezes and drops mouse events

  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04

  gnome-shell:
Installed: 3.36.0-2ubuntu2
Candidate: 3.36.0-2ubuntu2
Version table:
   *** 3.36.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr 3 14:24:21 2020
  DisplayManager: gdm3
  GsettingsChanges:

  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions


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

[Kernel-packages] [Bug 2003139] [NEW] Jammy update: v5.15.85 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.85 upstream stable release
   from git://git.kernel.org/

udf: Discard preallocation before extending file with a hole
udf: Fix preallocation discarding at indirect extent boundary
udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size
udf: Fix extending file within last block
usb: gadget: uvc: Prevent buffer overflow in setup handler
USB: serial: option: add Quectel EM05-G modem
USB: serial: cp210x: add Kamstrup RF sniffer PIDs
USB: serial: f81232: fix division by zero on line-speed change
USB: serial: f81534: fix division by zero on line-speed change
xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N
igb: Initialize mailbox message for VF reset
usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for 
Raptor Lake
HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk
selftests: net: Use "grep -E" instead of "egrep"
net: loopback: use NET_NAME_PREDICTABLE for name_assign_type
Linux 5.15.85
UBUNTU: Upstream stable to v5.15.85

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.85 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.85 upstream stable release
-from git://git.kernel.org/
+ udf: Discard preallocation before extending file with a hole
+ udf: Fix preallocation discarding at indirect extent boundary
+ udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size
+ udf: Fix extending file within last block
+ usb: gadget: uvc: Prevent buffer overflow in setup handler
+ USB: serial: option: add Quectel EM05-G modem
+ USB: serial: cp210x: add Kamstrup RF sniffer PIDs
+ USB: serial: f81232: fix division by zero on line-speed change
+ USB: serial: f81534: fix division by zero on line-speed change
+ xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N
+ igb: Initialize mailbox message for VF reset
+ usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system 
for Raptor Lake
+ HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk
+ selftests: net: Use "grep -E" instead of "egrep"
+ net: loopback: use NET_NAME_PREDICTABLE for name_assign_type
+ Linux 5.15.85
+ UBUNTU: Upstream stable to v5.15.85

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

Title:
  Jammy update: v5.15.85 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. 

[Kernel-packages] [Bug 2003134] Re: Jammy update: v5.15.83 upstream stable release

[Kamal Mostafa]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.83 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.83 upstream stable release
-from git://git.kernel.org/
+ clk: generalize devm_clk_get() a bit
+ clk: Provide new devm_clk helpers for prepared and enabled clocks
+ mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
+ arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series
+ arm: dts: rockchip: fix node name for hym8563 rtc
+ arm: dts: rockchip: remove clock-frequency from rtc
+ ARM: dts: rockchip: fix ir-receiver node names
+ arm64: dts: rockchip: fix ir-receiver node names
+ ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
+ fs: use acquire ordering in __fget_light()
+ ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
+ ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
+ ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
+ spi: mediatek: Fix DEVAPC Violation at KO Remove
+ ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
+ ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine 
transitions
+ 9p/fd: Use P9_HDRSZ for header size
+ regulator: slg51000: Wait after asserting CS pin
+ ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
+ selftests/net: Find nettest in current directory
+ btrfs: send: avoid unaligned encoded writes when attempting to clone range
+ ASoC: soc-pcm: Add NULL check in BE reparenting
+ regulator: twl6030: fix get status of twl6032 regulators
+ fbcon: Use kzalloc() in fbcon_prepare_logo()
+ usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer
+ 9p/xen: check logical size for buffer size
+ net: usb: qmi_wwan: add u-blox 0x1342 composition
+ mm/khugepaged: take the right locks for page table retraction
+ mm/khugepaged: fix GUP-fast interaction by sending IPI
+ mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths
+ rtc: mc146818-lib: extract mc146818_avoid_UIP
+ rtc: cmos: avoid UIP when writing alarm time
+ rtc: cmos: avoid UIP when reading alarm time
+ cifs: fix use-after-free caused by invalid pointer `hostname`
+ drm/bridge: anx7625: Fix edid_read break case in sp_tx_edid_read()
+ xen/netback: do some code cleanup
+ xen/netback: don't call kfree_skb() with interrupts disabled
+ media: videobuf2-core: take mmap_lock in vb2_get_unmapped_area()
+ soundwire: intel: Initialize clock stop timeout
+ media: v4l2-dv-timings.c: fix too strict blanking sanity checks
+ memcg: fix possible use-after-free in memcg_write_event_control()
+ mm/gup: fix gup_pud_range() for dax
+ Bluetooth: btusb: Add debug message for CSR controllers
+ Bluetooth: Fix crash when replugging CSR fake controllers
+ net: mana: Fix race on per-CQ variable napi work_done
+ KVM: s390: vsie: Fix the initialization of the epoch extension (epdx) field
+ drm/vmwgfx: Don't use screen objects when SEV is active
+ drm/amdgpu/sdma_v4_0: turn off SDMA ring buffer in the s2idle suspend
+ drm/shmem-helper: Remove errant put in error path
+ drm/shmem-helper: Avoid vm_open error paths
+ net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing()
+ HID: usbhid: Add ALWAYS_POLL quirk for some mice
+ HID: hid-lg4ff: Add check for empty lbuf
+ HID: core: fix shift-out-of-bounds in hid_report_raw_event
+ HID: ite: Enable QUIRK_TOUCHPAD_ON_OFF_REPORT on Acer Aspire Switch V 10
+ can: af_can: fix NULL pointer dereference in can_rcv_filter
+ clk: Fix pointer casting to prevent oops in devm_clk_release()
+ gpiolib: improve coding style for local variables
+ gpiolib: check the 'ngpios' property in core gpiolib code
+ gpiolib: fix memory leak in gpiochip_setup_dev()
+ netfilter: nft_set_pipapo: Actually validate intervals 

[Kernel-packages] [Bug 2003137] [NEW] Jammy update: v5.15.84 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.84 upstream stable release
   from git://git.kernel.org/

x86/vdso: Conditionally export __vdso_sgx_enter_enclave()
vfs: fix copy_file_range() averts filesystem freeze protection
ASoC: fsl_micfil: explicitly clear software reset bit
ASoC: fsl_micfil: explicitly clear CHnF flags
ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()
libbpf: Use page size as max_entries when probing ring buffer map
pinctrl: meditatek: Startup with the IRQs disabled
can: sja1000: fix size of OCR_MODE_MASK define
can: mcba_usb: Fix termination command argument
net: fec: don't reset irq coalesce settings to defaults on "ip link up"
ASoC: cs42l51: Correct PGA Volume minimum value
perf: Fix perf_pending_task() UaF
nvme-pci: clear the prp2 field when not used
ASoC: ops: Correct bounds check for second channel on SX controls
net: fec: properly guard irq coalesce setup
Linux 5.15.84
UBUNTU: Upstream stable to v5.15.84

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.84 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.84 upstream stable release
-from git://git.kernel.org/
+ x86/vdso: Conditionally export __vdso_sgx_enter_enclave()
+ vfs: fix copy_file_range() averts filesystem freeze protection
+ ASoC: fsl_micfil: explicitly clear software reset bit
+ ASoC: fsl_micfil: explicitly clear CHnF flags
+ ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()
+ libbpf: Use page size as max_entries when probing ring buffer map
+ pinctrl: meditatek: Startup with the IRQs disabled
+ can: sja1000: fix size of OCR_MODE_MASK define
+ can: mcba_usb: Fix termination command argument
+ net: fec: don't reset irq coalesce settings to defaults on "ip link up"
+ ASoC: cs42l51: Correct PGA Volume minimum value
+ perf: Fix perf_pending_task() UaF
+ nvme-pci: clear the prp2 field when not used
+ ASoC: ops: Correct bounds check for second channel on SX controls
+ net: fec: properly guard irq coalesce setup
+ Linux 5.15.84
+ UBUNTU: Upstream stable to v5.15.84

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

Title:
  Jammy update: v5.15.84 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.15.84 upstream 

[Kernel-packages] [Bug 2003134] [NEW] Jammy update: v5.15.83 upstream stable release

[Kamal Mostafa]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.83 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  Jammy update: v5.15.83 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.83 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation

[Brian Murray]

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7
  Mobile Workstation

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7 
Mobile Workstation when muting corresponding audio devices.
  * The right channel of internal speaker has not sound.

  [Fix]
  Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling 
LEDs and initialing AMP.

  [Test]
  Built a test kernel with applying this patch, the mute/micmute LEDs are work 
as expected.
  The internal speaker could play the sounds from left and right channels.

  [Where problems could occur]
  This quirk is specific for these two platforms. It should not cause the 
regression to other systems.

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


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

[Kernel-packages] [Bug 2003130] [NEW] Jammy update: v5.15.81 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.81 upstream stable release
   from git://git.kernel.org/

ASoC: fsl_sai: use local device pointer
ASoC: fsl_asrc fsl_esai fsl_sai: allow CONFIG_PM=N
serial: Add rs485_supported to uart_port
serial: fsl_lpuart: Fill in rs485_supported
tty: serial: fsl_lpuart: don't break the on-going transfer when global reset
sctp: remove the unnecessary sinfo_stream check in sctp_prsctp_prune_unsent
sctp: clear out_curr if all frag chunks of current msg are pruned
cifs: introduce new helper for cifs_reconnect()
cifs: split out dfs code from cifs_reconnect()
cifs: support nested dfs links over reconnect
cifs: Fix connections leak when tlink setup failed
ata: libata-scsi: simplify __ata_scsi_queuecmd()
ata: libata-core: do not issue non-internal commands once EH is pending
drm/display: Don't assume dual mode adaptors support i2c sub-addressing
nvme-pci: add NVME_QUIRK_BOGUS_NID for Micron Nitro
nvme-pci: disable namespace identifiers for the MAXIO MAP1001
nvme-pci: disable write zeroes on various Kingston SSD
nvme-pci: add NVME_QUIRK_BOGUS_NID for Netac NV7000
iio: ms5611: Simplify IO callback parameters
iio: pressure: ms5611: fixed value compensation bug
ceph: do not update snapshot context when there is no new snapshot
ceph: avoid putting the realm twice when decoding snaps fails
x86/sgx: Create utility to validate user provided offset and length
x86/sgx: Add overflow check in sgx_validate_offset_length()
binder: validate alloc->mm in ->mmap() handler
ceph: Use kcalloc for allocating multiple elements
ceph: fix NULL pointer dereference for req->r_session
wifi: mac80211: fix memory free error when registering wiphy fail
wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
riscv: dts: sifive unleashed: Add PWM controlled LEDs
audit: fix undefined behavior in bit shift for AUDIT_BIT
wifi: airo: do not assign -1 to unsigned char
wifi: mac80211: Fix ack frame idr leak when mesh has no route
wifi: ath11k: Fix QCN9074 firmware boot on x86
spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
selftests/bpf: Add verifier test for release_reference()
Revert "net: macsec: report real_dev features when HW offloading is enabled"
platform/x86: ideapad-laptop: Disable touchpad_switch
platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
platform/x86/intel/hid: Add some ACPI device IDs
scsi: ibmvfc: Avoid path failures during live migration
scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
block, bfq: fix null pointer dereference in bfq_bio_bfqg()
arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10 
properly""
ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
RISC-V: vdso: Do not add missing symbols to version section in linker script
MIPS: pic32: treat port as signed integer
xfrm: fix "disable_policy" on ipv4 early demux
xfrm: replay: Fix ESN wrap around for GSO
af_key: Fix send_acquire race with pfkey_register
ARM: dts: am335x-pcm-953: Define fixed regulators in root node
ASoC: hdac_hda: fix hda pcm buffer overflow issue
ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
x86/hyperv: Restore VP assist page after cpu offlining/onlining
scsi: storvsc: Fix handling of srb_status and capacity change events
ASoC: max98373: Add checks for devm_kcalloc
regulator: core: fix kobject release warning and memory leak in 
regulator_register()
spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
regulator: core: fix UAF in destroy_regulator()
bus: sunxi-rsb: Remove the shutdown callback
bus: sunxi-rsb: Support atomic transfers
tee: optee: fix possible memory leak in optee_register_device()
ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
selftests: mptcp: more stable simult_flows tests
selftests: mptcp: fix mibit vs mbit mix up
net: liquidio: simplify if expression
rxrpc: Allow list of in-use local UDP endpoints to be viewed in /proc
rxrpc: Use refcount_t rather than atomic_t
rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-CAN-15975]
net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
nfc/nci: fix race with opening and closing
net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
9p/fd: fix issue of 

[Kernel-packages] [Bug 2003132] [NEW] Jammy update: v5.15.82 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.82 upstream stable release
   from git://git.kernel.org/

arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored
drm/i915: Create a dummy object for gen6 ppgtt
drm/i915/gt: Use i915_vm_put on ppgtt_create error paths
erofs: fix order >= MAX_ORDER warning due to crafted negative i_size
btrfs: sink iterator parameter to btrfs_ioctl_logical_to_ino
btrfs: free btrfs_path before copying inodes to userspace
spi: spi-imx: Fix spi_bus_clk if requested clock is higher than input clock
btrfs: move QUOTA_ENABLED check to rescan_should_stop from 
btrfs_qgroup_rescan_worker
btrfs: qgroup: fix sleep from invalid context bug in btrfs_qgroup_inherit()
drm/display/dp_mst: Fix drm_dp_mst_add_affected_dsc_crtcs() return code
drm/amdgpu: update drm_display_info correctly when the edid is read
drm/amdgpu: Partially revert "drm/amdgpu: update drm_display_info correctly 
when the edid is read"
iio: health: afe4403: Fix oob read in afe4403_read_raw
iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw
iio: light: rpr0521: add missing Kconfig dependencies
bpf, perf: Use subprog name when reporting subprog ksymbol
scripts/faddr2line: Fix regression in name resolution on ppc64le
ARM: at91: rm9200: fix usb device clock id
libbpf: Handle size overflow for ringbuf mmap
hwmon: (ltc2947) fix temperature scaling
hwmon: (ina3221) Fix shunt sum critical calculation
hwmon: (i5500_temp) fix missing pci_disable_device()
hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails
bpf: Do not copy spin lock field from user in bpf_selem_alloc
nvmem: rmem: Fix return value check in rmem_read()
of: property: decrement node refcount in of_fwnode_get_reference_args()
ixgbevf: Fix resource leak in ixgbevf_init_module()
i40e: Fix error handling in i40e_init_module()
fm10k: Fix error handling in fm10k_init_module()
iavf: remove redundant ret variable
iavf: Fix error handling in iavf_init_module()
e100: Fix possible use after free in e100_xmit_prepare
net/mlx5: DR, Fix uninitialized var warning
net/mlx5: Fix uninitialized variable bug in outlen_write()
net/mlx5e: Fix use-after-free when reverting termination table
can: sja1000_isa: sja1000_isa_probe(): add missing free_sja1000dev()
can: cc770: cc770_isa_probe(): add missing free_cc770dev()
can: etas_es58x: es58x_init_netdev(): free netdev when register_candev()
can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods
can: m_can: Add check for devm_clk_get
qlcnic: fix sleep-in-atomic-context bugs caused by msleep
aquantia: Do not purge addresses when setting the number of rings
wifi: cfg80211: fix buffer overflow in elem comparison
wifi: cfg80211: don't allow multi-BSSID in S1G
wifi: mac8021: fix possible oob access in ieee80211_get_rate_duration
net: phy: fix null-ptr-deref while probe() failed
net: ethernet: ti: am65-cpsw: fix error handling in am65_cpsw_nuss_probe()
net: net_netdev: Fix error handling in ntb_netdev_init_module()
net/9p: Fix a potential socket leak in p9_socket_open
net: ethernet: nixge: fix NULL dereference
net: wwan: iosm: fix kernel test robot reported error
net: wwan: iosm: fix dma_alloc_coherent incompatible pointer type
dsa: lan9303: Correct stat name
tipc: re-fetch skb cb after tipc_msg_validate
net: hsr: Fix potential use-after-free
net: mdiobus: fix unbalanced node reference count
afs: Fix fileserver probe RTT handling
net: tun: Fix use-after-free in tun_detach()
packet: do not set TP_STATUS_CSUM_VALID on CHECKSUM_COMPLETE
sctp: fix memory leak in sctp_stream_outq_migrate()
net: ethernet: renesas: ravb: Fix promiscuous mode after system resumed
hwmon: (coretemp) Check for null before removing sysfs attrs
hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new()
riscv: vdso: fix section overlapping under some conditions
riscv: mm: Proper page permissions after initmem free
ALSA: dice: fix regression for Lexicon I-ONIX FW810S
error-injection: Add prompt for function error injection
tools/vm/slabinfo-gnuplot: use "grep -E" instead of "egrep"
nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()
x86/bugs: Make sure MSR_SPEC_CTRL is updated properly upon resume from S3
pinctrl: intel: Save and restore pins in "direct IRQ" mode
v4l2: don't fall back to follow_pfn() if pin_user_pages_fast() fails
net: stmmac: Set MAC's flow control register to reflect current settings
mmc: mmc_test: Fix removal of debugfs file
mmc: core: Fix ambiguous TRIM and DISCARD arg
mmc: sdhci-esdhc-imx: correct CQHCI exit halt state check
mmc: sdhci-sprd: Fix 

[Kernel-packages] [Bug 2001726] Re: Kinetic update: upstream stable patchset 2023-01-04

[Luke Nowakowski-Krijger]

** Changed in: linux (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

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

Title:
  Kinetic update: upstream stable patchset 2023-01-04

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2023-01-04

  Ported from the following upstream stable releases:
  v5.15.79, v6.0.9

     from git://git.kernel.org/

  thunderbolt: Add DP OUT resource when DP tunnel is discovered
  drm/amdkfd: handle CPU fault on COW mapping
  drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
  hwspinlock: qcom: correct MMIO max register for newer SoCs
  phy: stm32: fix an error code in probe
  wifi: cfg80211: silence a sparse RCU warning
  wifi: cfg80211: fix memory leak in query_regdb_file()
  soundwire: qcom: reinit broadcast completion
  soundwire: qcom: check for outanding writes before doing a read
  bpf, verifier: Fix memory leak in array reallocation for stack state
  bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues
  wifi: mac80211: Set TWT Information Frame Disabled bit as 1
  bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without FILE
  HID: hyperv: fix possible memory leak in mousevsc_probe()
  bpf, sockmap: Fix sk->sk_forward_alloc warn_on in sk_stream_kill_queues
  bpf: Fix sockmap calling sleepable function in teardown path
  bpf, sock_map: Move cancel_work_sync() out of sock lock
  bpf: Add helper macro bpf_for_each_reg_in_vstate
  bpf: Fix wrong reg type conversion in release_reference()
  net: gso: fix panic on frag_list with mixed head alloc types
  macsec: delete new rxsc when offload fails
  macsec: fix secy->n_rx_sc accounting
  macsec: fix detection of RXSCs when toggling offloading
  macsec: clear encryption keys from the stack after setting up offload
  octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
  net: tun: Fix memory leaks of napi_get_frags
  bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
  bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
  net: fman: Unregister ethernet device on removal
  capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
  phy: ralink: mt7621-pci: add sentinel to quirks table
  KVM: s390: pv: don't allow userspace to set the clock under PV
  net: lapbether: fix issue of dev reference count leakage in 
lapbeth_device_event()
  hamradio: fix issue of dev reference count leakage in bpq_device_event()
  net: wwan: iosm: fix memory leak in ipc_wwan_dellink
  net: wwan: mhi: fix memory leak in mhi_mbim_dellink
  drm/vc4: Fix missing platform_unregister_drivers() call in vc4_drm_register()
  tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
  ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
  can: af_can: fix NULL pointer dereference in can_rx_register()
  net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
  net: broadcom: Fix BCMGENET Kconfig
  tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header
  dmaengine: pxa_dma: use platform_get_irq_optional
  dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove()
  dmaengine: ti: k3-udma-glue: fix memory leak when register device fail
  net: lapbether: fix issue of invalid opcode in lapbeth_open()
  drivers: net: xgene: disable napi when register irq failed in 
xgene_enet_open()
  perf stat: Fix printing os->prefix in CSV metrics output
  perf tools: Add the include/perf/ directory to .gitignore
  netfilter: nfnetlink: fix potential dead lock in nfnetlink_rcv_msg()
  netfilter: Cleanup nft_net->module_list from nf_tables_exit_net()
  net: marvell: prestera: fix memory leak in prestera_rxtx_switch_init()
  net: nixge: disable napi when enable interrupts failed in nixge_open()
  net: wwan: iosm: fix memory leak in ipc_pcie_read_bios_cfg
  net/mlx5: Bridge, verify LAG state when adding bond to bridge
  net/mlx5: Allow async trigger completion execution on single CPU systems
  net/mlx5e: E-Switch, Fix comparing termination table instance
  net: cpsw: disable napi in cpsw_ndo_open()
  net: cxgb3_main: disable napi when bind qsets failed in cxgb_up()
  stmmac: intel: Update PCH PTP clock rate from 200MHz to 204.8MHz
  mctp: Fix an error handling path in mctp_init()
  cxgb4vf: shut down the adapter when 

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

[beadon]

I have applied the workaround for mutter :
  MUTTER_DEBUG_FORCE_KMS_MODE=simple

I am seeing no further logs at the moment.  I will continue to monitor
for issues.

To address any low-level issues I also have applied the system firmware
update, available via ISO from the Lenovo support site "n32ur20w.iso".
the release date on this was Jan 02 , 2023, so only about 2 weeks ago.

I expect the issue to re-occur.

Reference for anyone following along at home :
https://pcsupport.lenovo.com/us/en/products/laptops-and-
netbooks/thinkpad-x-series-laptops/thinkpad-x1-yoga-6th-gen-
type-20xy-20y0/20xy/20xy0027us/downloads/driver-
list/component?name=BIOS%2FUEFI


Release notes for this firmware update included here too :


** Attachment added: "n32ur20w.txt"
   
https://bugs.launchpad.net/linux/+bug/2003031/+attachment/5642055/+files/n32ur20w.txt

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

[beadon]

Yes, there is a USB-C "port extender" (dock) attached to this Lenovo
laptop.  The model is the MUC-0501B.  It is this exact device :
https://amzn.to/3XA5u5N  -- "USB C Adapters for MacBook Pro/Air,Mac
Dongle with 3 USB Port,USB C to HDMI, USB C to RJ45 Ethernet,MOKiN 9 in
1 USB C to HDMI Adapter,100W Pd Charging, USB C to SD/TF Card Reader USB
C Hub".

I also have noticed occassional flickering.  What's interesting is that
either the display controlled via this, or via the direct HDMI port will
"drop out" for a second or 2 when the mouse moves between the screens.
If I move the mouse back to the alternate screen, the display comes
back.


** Attachment added: "video of a related(?) problem."
   
https://bugs.launchpad.net/linux/+bug/2003031/+attachment/5642054/+files/PXL_20230117_204102229.mp4

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 2003122] Re: Jammy update: v5.15.80 upstream stable release

[Kamal Mostafa]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.80 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.80 upstream stable release
-from git://git.kernel.org/
+ mm: hwpoison: refactor refcount check handling
+ mm: hwpoison: handle non-anonymous THP correctly
+ mm: shmem: don't truncate page if memory failure happens
+ ASoC: wm5102: Revert "ASoC: wm5102: Fix PM disable depth imbalance in 
wm5102_probe"
+ ASoC: wm5110: Revert "ASoC: wm5110: Fix PM disable depth imbalance in 
wm5110_probe"
+ ASoC: wm8997: Revert "ASoC: wm8997: Fix PM disable depth imbalance in 
wm8997_probe"
+ ASoC: mt6660: Keep the pm_runtime enables before component stuff in 
mt6660_i2c_probe
+ ASoC: rt1019: Fix the TDM settings
+ ASoC: wm8962: Add an event handler for TEMP_HP and TEMP_SPK
+ spi: intel: Fix the offset to get the 64K erase opcode
+ ASoC: codecs: jz4725b: add missed Line In power control bit
+ ASoC: codecs: jz4725b: fix reported volume for Master ctl
+ ASoC: codecs: jz4725b: use right control for Capture Volume
+ ASoC: codecs: jz4725b: fix capture selector naming
+ ASoC: Intel: sof_sdw: add quirk variant for LAPBC710 NUC15
+ selftests/futex: fix build for clang
+ selftests/intel_pstate: fix build for ARCH=x86_64
+ ASoC: rt1308-sdw: add the default value of some registers
+ drm/amd/display: Remove wrong pipe control lock
+ ACPI: scan: Add LATT2021 to acpi_ignore_dep_ids[]
+ RDMA/efa: Add EFA 0xefa2 PCI ID
+ btrfs: raid56: properly handle the error when unable to find the missing 
stripe
+ NFSv4: Retry LOCK on OLD_STATEID during delegation return
+ ACPI: x86: Add another system to quirk list for forcing StorageD3Enable
+ firmware: arm_scmi: Cleanup the core driver removal callback
+ i2c: tegra: Allocate DMA memory for DMA engine
+ i2c: i801: add lis3lv02d's I2C address for Vostro 5568
+ drm/imx: imx-tve: Fix return type of imx_tve_connector_mode_valid
+ btrfs: remove pointless and double ulist frees in error paths of qgroup tests
+ x86/cpu: Add several Intel server CPU model numbers
+ ASoC: codecs: jz4725b: Fix spelling mistake "Sourc" -> "Source", "Routee" -> 
"Route"
+ mtd: spi-nor: intel-spi: Disable write protection only if asked
+ spi: intel: Use correct mask for flash and protected regions
+ KVM: x86/pmu: Do not speculatively query Intel GP PMCs that don't exist yet
+ hugetlbfs: don't delete error page from pagecache
+ arm64: dts: qcom: sa8155p-adp: Specify which LDO modes are allowed
+ arm64: dts: qcom: sm8150-xperia-kumano: Specify which LDO modes are allowed
+ arm64: dts: qcom: sm8250-xperia-edo: Specify which LDO modes are allowed
+ arm64: dts: qcom: sm8350-hdk: Specify which LDO modes are allowed
+ spi: stm32: Print summary 'callbacks suppressed' message
+ ARM: dts: at91: sama7g5: fix signal name of pin PB2
+ ASoC: core: Fix use-after-free in snd_soc_exit()
+ ASoC: tas2770: Fix set_tdm_slot in case of single slot
+ ASoC: tas2764: Fix set_tdm_slot in case of single slot
+ ARM: at91: pm: avoid soft resetting AC DLL
+ serial: 8250: omap: Fix missing PM runtime calls for omap8250_set_mctrl()
+ serial: 8250_omap: remove wait loop from Errata i202 workaround
+ serial: 8250: omap: Fix unpaired pm_runtime_put_sync() in omap8250_remove()
+ serial: 8250: omap: Flush PM QOS work on remove
+ serial: imx: Add missing .thaw_noirq hook
+ tty: n_gsm: fix sleep-in-atomic-context bug in gsm_control_send
+ bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb()
+ ASoC: soc-utils: Remove __exit for snd_soc_util_exit()
+ pinctrl: rockchip: list all pins in a possible mux route for PX30
+ scsi: scsi_transport_sas: Fix error handling in sas_phy_add()
+ block: sed-opal: kmalloc the cmd/resp buffers
+ bpf: Fix memory leaks in __check_func_call
+ arm64: Fix bit-shifting UB in the MIDR_CPU_MODEL() macro
+ siox: fix possible memory leak in siox_device_add()
+ parport_pc: Avoid FIFO port location truncation
+ pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map
+ drm/vc4: kms: Fix IS_ERR() vs NULL check for vc4_kms
+ drm/panel: simple: set bpc field for logic technologies 

[Kernel-packages] [Bug 2003122] [NEW] Jammy update: v5.15.80 upstream stable release

[Kamal Mostafa]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.80 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Jammy update: v5.15.80 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.80 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1927253] Re: mlxbf-tmfifo: Add ctrl message and MAC configuration

[Liming Sun]

I couldn't see the change in 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-bluefield/+git/jammy.

Is this the correct repo I should see this commit, or probably takes
some time?

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

Title:
  mlxbf-tmfifo: Add ctrl message and MAC configuration

Status in linux-bluefield package in Ubuntu:
  Fix Released

Bug description:
  THis one is created to track the commit merge of the mlxbf-tmfifo
  driver to support ctrl message and MAC configuration.

  SRU Justification:

  [Impact]
  * N/A.

  [Fix]
  * N/A.

  [Test Case]
  * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' 
from external rshim driver. 
The rshim MAC address will show up.
  # cat /dev/rshim0/misc
  DISPLAY_LEVEL   1 (0:basic, 1:advanced, 2:log)
  BOOT_MODE   1 (0:rshim, 1:emmc, 2:emmc-boot-swap)
  BOOT_TIMEOUT100 (seconds)
  DROP_MODE   0 (0:normal, 1:drop)
  SW_RESET0 (1: reset)
  DEV_NAMEusb-1-1.1
  DEV_INFOBlueField-2(Rev 0)
  OPN_STR MBF2M516A-EEEO
  BOOT_RESET_SKIP 0 (1: skip)
  PEER_MAC00:1a:ca:ff:ff:01 (rw)
  PXE_ID  0x (rw)
  VLAN_ID 0 0 (rw)
  * echo "PEER_MACxx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the 
MAC address, which will take effect in next boot.

  [Regression Potential]
  * This is a new enhancement and is backward-compatible with previous behavior.

  [Other]
  * N/A

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


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

[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

[Tim Gardner]

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

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

Title:
  md: Replace snprintf with scnprintf

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set

[Jim Tim]

** Information type changed from Public to Public Security

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

Title:
  DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 22.04 with kernel 5.15.0.27.30 on an HPE ProLiant
  DL20 Gen9 server. The server has an HPE Smart HBA H240 SATA
  controller.

  Since Ubuntu 22.04, the kernel runs into trouble after a few hours of
  uptime. The problem starts with a few instances of a message such as
  this:

  Apr 26 12:03:37  kernel: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 
already set (to 7bf32003 not 24c563801)
  Apr 26 12:03:37  kernel: [ cut here ]
  Apr 26 12:03:37  kernel: WARNING: CPU: 1 PID: 10171 at 
drivers/iommu/intel/iommu.c:2391 __domain_mapping.cold+0x94/0xcb
  Apr 26 12:03:37  kernel: Modules linked in: tls rpcsec_gss_krb5 
binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT 
nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limi>
  Apr 26 12:03:37  kernel:  drm_kms_helper aesni_intel syscopyarea 
sysfillrect sysimgblt fb_sys_fops xhci_pci cec crypto_simd i2c_i801 rc_core 
cryptd drm xhci_pci_renesas ahci i2c_smbus tg3 hpsa>
  Apr 26 12:03:37  kernel: CPU: 1 PID: 10171 Comm: kworker/u4:0 Not 
tainted 5.15.0-27-generic #28-Ubuntu
  Apr 26 12:03:37  kernel: Hardware name: HP ProLiant DL20 
Gen9/ProLiant DL20 Gen9, BIOS U22 04/01/2021
  Apr 26 12:03:37  kernel: Workqueue: writeback wb_workfn 
(flush-253:2)
  Apr 26 12:03:37  kernel: RIP: 0010:__domain_mapping.cold+0x94/0xcb
  Apr 26 12:03:37  kernel: Code: 27 9d 4c 89 4d b8 4c 89 45 c0 e8 03 
c5 fa ff 8b 05 e7 e6 40 01 4c 8b 45 c0 4c 8b 4d b8 85 c0 74 09 83 e8 01 89 05 
d2 e6 40 01 <0f> 0b e9 7e b2 b1 ff 89 ca 48 83 >
  Apr 26 12:03:37  kernel: RSP: 0018:c077826b2fa0 EFLAGS: 00010202
  Apr 26 12:03:37  kernel: RAX: 0004 RBX: 
9f0042062990 RCX: 
  Apr 26 12:03:37  kernel: RDX:  RSI: 
9f02b3d20980 RDI: 9f02b3d20980
  Apr 26 12:03:37  kernel: RBP: c077826b2ff0 R08: 
00024c563801 R09: 0024c563
  Apr 26 12:03:37  kernel: R10:  R11: 
c01550e0 R12: 000f
  Apr 26 12:03:37  kernel: R13: 0007bf32 R14: 
9f00412f5800 R15: 9f0042062938
  Apr 26 12:03:37  kernel: FS:  () 
GS:9f02b3d0() knlGS:
  Apr 26 12:03:37  kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 26 12:03:37  kernel: CR2: 1530f676a01c CR3: 
00029c210001 CR4: 002706e0
  Apr 26 12:03:37  kernel: Call Trace:
  Apr 26 12:03:37  kernel:  
  Apr 26 12:03:37  kernel:  intel_iommu_map_pages+0xdc/0x120
  Apr 26 12:03:37  kernel:  ? 
__alloc_and_insert_iova_range+0x203/0x240
  Apr 26 12:03:37  kernel:  __iommu_map+0xda/0x270
  Apr 26 12:03:37  kernel:  __iommu_map_sg+0x8e/0x120
  Apr 26 12:03:37  kernel:  iommu_map_sg_atomic+0x14/0x20
  Apr 26 12:03:37  kernel:  iommu_dma_map_sg+0x345/0x4d0
  Apr 26 12:03:37  kernel:  __dma_map_sg_attrs+0x68/0x70
  Apr 26 12:03:37  kernel:  dma_map_sg_attrs+0xe/0x20
  Apr 26 12:03:37  kernel:  scsi_dma_map+0x39/0x50
  Apr 26 12:03:37  kernel:  
hpsa_scsi_ioaccel2_queue_command.constprop.0+0x11e/0x570 [hpsa]
  Apr 26 12:03:37  kernel:  ? __blk_rq_map_sg+0x36/0x160
  Apr 26 12:03:37  kernel:  hpsa_scsi_ioaccel_queue_command+0x82/0xd0 
[hpsa]
  Apr 26 12:03:37  kernel:  hpsa_ioaccel_submit+0x174/0x190 [hpsa]
  Apr 26 12:03:37  kernel:  hpsa_scsi_queue_command+0x19c/0x240 [hpsa]
  Apr 26 12:03:37  kernel:  ? recalibrate_cpu_khz+0x10/0x10
  Apr 26 12:03:37  kernel:  scsi_dispatch_cmd+0x93/0x1f0
  Apr 26 12:03:37  kernel:  scsi_queue_rq+0x2d1/0x690
  Apr 26 12:03:37  kernel:  blk_mq_dispatch_rq_list+0x126/0x600
  Apr 26 12:03:37  kernel:  ? __sbitmap_queue_get+0x1/0x10
  Apr 26 12:03:37  kernel:  __blk_mq_do_dispatch_sched+0xba/0x2d0
  Apr 26 12:03:37  kernel:  
__blk_mq_sched_dispatch_requests+0x104/0x150
  Apr 26 12:03:37  kernel:  blk_mq_sched_dispatch_requests+0x35/0x60
  Apr 26 12:03:37  kernel:  __blk_mq_run_hw_queue+0x34/0xb0
  Apr 26 12:03:37  kernel:  __blk_mq_delay_run_hw_queue+0x162/0x170
  Apr 26 12:03:37  kernel:  blk_mq_run_hw_queue+0x83/0x120
  Apr 26 12:03:37  kernel:  blk_mq_sched_insert_requests+0x69/0xf0
  Apr 26 12:03:37  kernel:  blk_mq_flush_plug_list+0x103/0x1c0
  Apr 26 12:03:37  kernel:  blk_flush_plug_list+0xdd/0x100
  Apr 26 12:03:37  kernel:  blk_mq_submit_bio+0x2bd/0x600
  Apr 26 12:03:37  kernel:  __submit_bio+0x1ea/0x220
  Apr 26 12:03:37  kernel:  ? mempool_alloc_slab+0x17/0x20
  Apr 26 12:03:37  kernel:  __submit_bio_noacct+0x85/0x1f0
  Apr 26 12:03:37  kernel:  submit_bio_noacct+0x4e/0x120
  Apr 26 12:03:37  kernel:  ? radix_tree_lookup+0xd/0x10
  Apr 26 12:03:37  kernel:  ? bio_associate_blkg_from_css+0x1b2/0x310
  Apr 26 12:03:37  kernel:  

[Kernel-packages] [Bug 1997946] Update Released

[Timo Aaltonen]

The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.2

---
alsa-ucm-conf (1.2.6.3-1ubuntu1.2) jammy; urgency=medium

  * Backport patch for speaker AMP-ALC1318 support. (LP: #1997946)

  [ Andy Chi ]
  * d/p/sof-soundwire-set-PGA-capture-switch-for-rt715-mic-in-Boo.patch:
- fix microphone recording on rt715 (LP: #2000465)

 -- Kai-Chuan Hsieh   Mon, 26 Dec 2022
14:53:41 +0800

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 2000465] Re: [SRU]rt715-sdca codec cannot record audio with internal microphone

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.2

---
alsa-ucm-conf (1.2.6.3-1ubuntu1.2) jammy; urgency=medium

  * Backport patch for speaker AMP-ALC1318 support. (LP: #1997946)

  [ Andy Chi ]
  * d/p/sof-soundwire-set-PGA-capture-switch-for-rt715-mic-in-Boo.patch:
- fix microphone recording on rt715 (LP: #2000465)

 -- Kai-Chuan Hsieh   Mon, 26 Dec 2022
14:53:41 +0800

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU]rt715-sdca codec cannot record audio with internal microphone

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  rt715-sdca codec cannot record audio with internal microphone

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal microphone should work propoerly.

  [Where problems could occur]
  Only fix for DUT with rt715-sdca device

  [Other Info]
  Upstream bug:
  https://github.com/alsa-project/alsa-ucm-conf/issues/255
  Fix:
  
https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa

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


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

[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu3

---
alsa-ucm-conf (1.2.6.3-1ubuntu3) kinetic; urgency=medium

  * Backport patch for speaker AMP-ALC1318 support. (LP: #1997946)

  [ Andy Chi ]
  * d/p/sof-soundwire-set-PGA-capture-switch-for-rt715-mic-in-Boo.patch:
- fix microphone recording on rt715 (LP: #2000465)

 -- Kai-Chuan Hsieh   Mon, 26 Dec 2022
15:12:24 +0800

** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 2000465] Update Released

[Timo Aaltonen]

The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU]rt715-sdca codec cannot record audio with internal microphone

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  rt715-sdca codec cannot record audio with internal microphone

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal microphone should work propoerly.

  [Where problems could occur]
  Only fix for DUT with rt715-sdca device

  [Other Info]
  Upstream bug:
  https://github.com/alsa-project/alsa-ucm-conf/issues/255
  Fix:
  
https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa

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


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

[Kernel-packages] [Bug 2000465] Re: [SRU]rt715-sdca codec cannot record audio with internal microphone

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu3

---
alsa-ucm-conf (1.2.6.3-1ubuntu3) kinetic; urgency=medium

  * Backport patch for speaker AMP-ALC1318 support. (LP: #1997946)

  [ Andy Chi ]
  * d/p/sof-soundwire-set-PGA-capture-switch-for-rt715-mic-in-Boo.patch:
- fix microphone recording on rt715 (LP: #2000465)

 -- Kai-Chuan Hsieh   Mon, 26 Dec 2022
15:12:24 +0800

** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU]rt715-sdca codec cannot record audio with internal microphone

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  rt715-sdca codec cannot record audio with internal microphone

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal microphone should work propoerly.

  [Where problems could occur]
  Only fix for DUT with rt715-sdca device

  [Other Info]
  Upstream bug:
  https://github.com/alsa-project/alsa-ucm-conf/issues/255
  Fix:
  
https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa

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


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

[Kernel-packages] [Bug 2003111] Re: ASAN catches bug in v4l kernel module.

[Bram Stolk]

lunar running on VM, kernel version 5.19.0-21-generic is not affected.

kinetic running on HW, kernel version 5.19.0-29-generic is affected.

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

Title:
  ASAN catches bug in v4l kernel module.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The package linux-modules-extra-5.19.0-29-generic has a kernel module
  named vivid.ko for artificial v4l streams.

  When I modprobe the vivid.ko module, an invalid operation is detected
  by ASAN, and the created of /dev/video0 device file fails.

  The offending call is v4l_querymenu

  The offending operation is shift-out-of-bounds

  I tried this in a virtual machine of lunar (23.04) where the modprobe
  succeeded. But it fails on the real machine, running kinetic (22.10)

  This is a kernel bug.

  
  ```
  [ 6028.277644] vivid-000: using single planar format API
  [ 6028.278261] Registered IR keymap rc-cec
  [ 6028.278304] rc rc0: vivid-000-vid-cap0 as /devices/platform/vivid.0/rc/rc0
  [ 6028.278329] input: vivid-000-vid-cap0 as 
/devices/platform/vivid.0/rc/rc0/input34
  [ 6028.278395] vivid-000: CEC adapter cec0 registered for HDMI input 0
  [ 6028.278420] vivid-000: V4L2 capture device registered as video3
  [ 6028.278422] Registered IR keymap rc-cec
  [ 6028.278433] rc rc1: vivid-000-vid-out0 as /devices/platform/vivid.0/rc/rc1
  [ 6028.278451] input: vivid-000-vid-out0 as 
/devices/platform/vivid.0/rc/rc1/input35
  [ 6028.278491] vivid-000: CEC adapter cec1 registered for HDMI output 0
  [ 6028.278512] vivid-000: V4L2 output device registered as video4
  [ 6028.278531] vivid-000: V4L2 capture device registered as vbi0, supports 
raw and sliced VBI
  [ 6028.278550] vivid-000: V4L2 output device registered as vbi1, supports raw 
and sliced VBI
  [ 6028.278571] vivid-000: V4L2 capture device registered as swradio0
  [ 6028.278590] vivid-000: V4L2 receiver device registered as radio0
  [ 6028.278609] vivid-000: V4L2 transmitter device registered as radio1
  [ 6028.278628] vivid-000: V4L2 metadata capture device registered as video5
  [ 6028.278649] vivid-000: V4L2 metadata output device registered as video6
  [ 6028.278669] vivid-000: V4L2 touch capture device registered as v4l-touch0
  [ 6028.302648] 

  [ 6028.302651] UBSAN: shift-out-of-bounds in 
/build/linux-qLbdtO/linux-5.19.0/drivers/media/v4l2-core/v4l2-ctrls-api.c:1102:35
  [ 6028.302652] shift exponent 64 is too large for 64-bit type 'long long 
unsigned int'
  [ 6028.302654] CPU: 4 PID: 2138 Comm: pipewire Not tainted 5.19.0-29-generic 
#30-Ubuntu
  [ 6028.302656] Hardware name: ASUS System Product Name/PRIME Z690M-PLUS D4, 
BIOS 1008 01/13/2022
  [ 6028.302656] Call Trace:
  [ 6028.302657]  
  [ 6028.302659]  show_stack+0x4e/0x61
  [ 6028.302663]  dump_stack_lvl+0x4a/0x6f
  [ 6028.302665]  dump_stack+0x10/0x18
  [ 6028.302666]  ubsan_epilogue+0x9/0x43
  [ 6028.302668]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 6028.302669]  ? mutex_lock+0x12/0x50
  [ 6028.302673]  v4l2_querymenu.cold+0x24/0x39 [videodev]
  [ 6028.302681]  v4l_querymenu+0x81/0xa0 [videodev]
  [ 6028.302686]  __video_do_ioctl+0x1e7/0x590 [videodev]
  [ 6028.302691]  video_usercopy+0x14b/0x730 [videodev]
  [ 6028.302696]  ? video_get_user.constprop.0+0x1d0/0x1d0 [videodev]
  [ 6028.302700]  video_ioctl2+0x15/0x30 [videodev]
  [ 6028.302705]  v4l2_ioctl+0x69/0xb0 [videodev]
  [ 6028.302709]  __x64_sys_ioctl+0x9d/0xe0
  [ 6028.302711]  do_syscall_64+0x58/0x90
  [ 6028.302712]  ? do_syscall_64+0x67/0x90
  [ 6028.302712]  ? do_syscall_64+0x67/0x90
  [ 6028.302713]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [ 6028.302715] RIP: 0033:0x7f8631712d8f
  [ 6028.302717] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 
00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  [ 6028.302717] RSP: 002b:7ffd35484ed0 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 6028.302719] RAX: ffda RBX: 0400 RCX: 
7f8631712d8f
  [ 6028.302720] RDX: 7ffd35485050 RSI: c02c5625 RDI: 
0032
  [ 6028.302720] RBP: 000b R08: 0a58 R09: 
000b
  [ 6028.302721] R10: 0008000c R11: 0246 R12: 
7ffd35485058
  [ 6028.302721] R13: 7ffd35485050 R14: 55959cc26a48 R15: 
0032
  [ 6028.302723]  
  [ 6028.302724] 

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-modules-extra-5.19.0-29-generic 5.19.0-29.30
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   

[Kernel-packages] [Bug 2003111] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  ASAN catches bug in v4l kernel module.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The package linux-modules-extra-5.19.0-29-generic has a kernel module
  named vivid.ko for artificial v4l streams.

  When I modprobe the vivid.ko module, an invalid operation is detected
  by ASAN, and the created of /dev/video0 device file fails.

  The offending call is v4l_querymenu

  The offending operation is shift-out-of-bounds

  I tried this in a virtual machine of lunar (23.04) where the modprobe
  succeeded. But it fails on the real machine, running kinetic (22.10)

  This is a kernel bug.

  
  ```
  [ 6028.277644] vivid-000: using single planar format API
  [ 6028.278261] Registered IR keymap rc-cec
  [ 6028.278304] rc rc0: vivid-000-vid-cap0 as /devices/platform/vivid.0/rc/rc0
  [ 6028.278329] input: vivid-000-vid-cap0 as 
/devices/platform/vivid.0/rc/rc0/input34
  [ 6028.278395] vivid-000: CEC adapter cec0 registered for HDMI input 0
  [ 6028.278420] vivid-000: V4L2 capture device registered as video3
  [ 6028.278422] Registered IR keymap rc-cec
  [ 6028.278433] rc rc1: vivid-000-vid-out0 as /devices/platform/vivid.0/rc/rc1
  [ 6028.278451] input: vivid-000-vid-out0 as 
/devices/platform/vivid.0/rc/rc1/input35
  [ 6028.278491] vivid-000: CEC adapter cec1 registered for HDMI output 0
  [ 6028.278512] vivid-000: V4L2 output device registered as video4
  [ 6028.278531] vivid-000: V4L2 capture device registered as vbi0, supports 
raw and sliced VBI
  [ 6028.278550] vivid-000: V4L2 output device registered as vbi1, supports raw 
and sliced VBI
  [ 6028.278571] vivid-000: V4L2 capture device registered as swradio0
  [ 6028.278590] vivid-000: V4L2 receiver device registered as radio0
  [ 6028.278609] vivid-000: V4L2 transmitter device registered as radio1
  [ 6028.278628] vivid-000: V4L2 metadata capture device registered as video5
  [ 6028.278649] vivid-000: V4L2 metadata output device registered as video6
  [ 6028.278669] vivid-000: V4L2 touch capture device registered as v4l-touch0
  [ 6028.302648] 

  [ 6028.302651] UBSAN: shift-out-of-bounds in 
/build/linux-qLbdtO/linux-5.19.0/drivers/media/v4l2-core/v4l2-ctrls-api.c:1102:35
  [ 6028.302652] shift exponent 64 is too large for 64-bit type 'long long 
unsigned int'
  [ 6028.302654] CPU: 4 PID: 2138 Comm: pipewire Not tainted 5.19.0-29-generic 
#30-Ubuntu
  [ 6028.302656] Hardware name: ASUS System Product Name/PRIME Z690M-PLUS D4, 
BIOS 1008 01/13/2022
  [ 6028.302656] Call Trace:
  [ 6028.302657]  
  [ 6028.302659]  show_stack+0x4e/0x61
  [ 6028.302663]  dump_stack_lvl+0x4a/0x6f
  [ 6028.302665]  dump_stack+0x10/0x18
  [ 6028.302666]  ubsan_epilogue+0x9/0x43
  [ 6028.302668]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 6028.302669]  ? mutex_lock+0x12/0x50
  [ 6028.302673]  v4l2_querymenu.cold+0x24/0x39 [videodev]
  [ 6028.302681]  v4l_querymenu+0x81/0xa0 [videodev]
  [ 6028.302686]  __video_do_ioctl+0x1e7/0x590 [videodev]
  [ 6028.302691]  video_usercopy+0x14b/0x730 [videodev]
  [ 6028.302696]  ? video_get_user.constprop.0+0x1d0/0x1d0 [videodev]
  [ 6028.302700]  video_ioctl2+0x15/0x30 [videodev]
  [ 6028.302705]  v4l2_ioctl+0x69/0xb0 [videodev]
  [ 6028.302709]  __x64_sys_ioctl+0x9d/0xe0
  [ 6028.302711]  do_syscall_64+0x58/0x90
  [ 6028.302712]  ? do_syscall_64+0x67/0x90
  [ 6028.302712]  ? do_syscall_64+0x67/0x90
  [ 6028.302713]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [ 6028.302715] RIP: 0033:0x7f8631712d8f
  [ 6028.302717] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 
00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  [ 6028.302717] RSP: 002b:7ffd35484ed0 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 6028.302719] RAX: ffda RBX: 0400 RCX: 
7f8631712d8f
  [ 6028.302720] RDX: 7ffd35485050 RSI: c02c5625 RDI: 
0032
  [ 6028.302720] RBP: 000b R08: 0a58 R09: 
000b
  [ 6028.302721] R10: 0008000c R11: 0246 R12: 
7ffd35485058
  [ 6028.302721] R13: 7ffd35485050 R14: 55959cc26a48 R15: 
0032
  [ 6028.302723]  
  [ 6028.302724] 

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-modules-extra-5.19.0-29-generic 5.19.0-29.30
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   

[Kernel-packages] [Bug 2003111] [NEW] ASAN catches bug in v4l kernel module.

[Bram Stolk]

Public bug reported:

The package linux-modules-extra-5.19.0-29-generic has a kernel module
named vivid.ko for artificial v4l streams.

When I modprobe the vivid.ko module, an invalid operation is detected by
ASAN, and the created of /dev/video0 device file fails.

The offending call is v4l_querymenu

The offending operation is shift-out-of-bounds

I tried this in a virtual machine of lunar (23.04) where the modprobe
succeeded. But it fails on the real machine, running kinetic (22.10)

This is a kernel bug.


```
[ 6028.277644] vivid-000: using single planar format API
[ 6028.278261] Registered IR keymap rc-cec
[ 6028.278304] rc rc0: vivid-000-vid-cap0 as /devices/platform/vivid.0/rc/rc0
[ 6028.278329] input: vivid-000-vid-cap0 as 
/devices/platform/vivid.0/rc/rc0/input34
[ 6028.278395] vivid-000: CEC adapter cec0 registered for HDMI input 0
[ 6028.278420] vivid-000: V4L2 capture device registered as video3
[ 6028.278422] Registered IR keymap rc-cec
[ 6028.278433] rc rc1: vivid-000-vid-out0 as /devices/platform/vivid.0/rc/rc1
[ 6028.278451] input: vivid-000-vid-out0 as 
/devices/platform/vivid.0/rc/rc1/input35
[ 6028.278491] vivid-000: CEC adapter cec1 registered for HDMI output 0
[ 6028.278512] vivid-000: V4L2 output device registered as video4
[ 6028.278531] vivid-000: V4L2 capture device registered as vbi0, supports raw 
and sliced VBI
[ 6028.278550] vivid-000: V4L2 output device registered as vbi1, supports raw 
and sliced VBI
[ 6028.278571] vivid-000: V4L2 capture device registered as swradio0
[ 6028.278590] vivid-000: V4L2 receiver device registered as radio0
[ 6028.278609] vivid-000: V4L2 transmitter device registered as radio1
[ 6028.278628] vivid-000: V4L2 metadata capture device registered as video5
[ 6028.278649] vivid-000: V4L2 metadata output device registered as video6
[ 6028.278669] vivid-000: V4L2 touch capture device registered as v4l-touch0
[ 6028.302648] 

[ 6028.302651] UBSAN: shift-out-of-bounds in 
/build/linux-qLbdtO/linux-5.19.0/drivers/media/v4l2-core/v4l2-ctrls-api.c:1102:35
[ 6028.302652] shift exponent 64 is too large for 64-bit type 'long long 
unsigned int'
[ 6028.302654] CPU: 4 PID: 2138 Comm: pipewire Not tainted 5.19.0-29-generic 
#30-Ubuntu
[ 6028.302656] Hardware name: ASUS System Product Name/PRIME Z690M-PLUS D4, 
BIOS 1008 01/13/2022
[ 6028.302656] Call Trace:
[ 6028.302657]  
[ 6028.302659]  show_stack+0x4e/0x61
[ 6028.302663]  dump_stack_lvl+0x4a/0x6f
[ 6028.302665]  dump_stack+0x10/0x18
[ 6028.302666]  ubsan_epilogue+0x9/0x43
[ 6028.302668]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[ 6028.302669]  ? mutex_lock+0x12/0x50
[ 6028.302673]  v4l2_querymenu.cold+0x24/0x39 [videodev]
[ 6028.302681]  v4l_querymenu+0x81/0xa0 [videodev]
[ 6028.302686]  __video_do_ioctl+0x1e7/0x590 [videodev]
[ 6028.302691]  video_usercopy+0x14b/0x730 [videodev]
[ 6028.302696]  ? video_get_user.constprop.0+0x1d0/0x1d0 [videodev]
[ 6028.302700]  video_ioctl2+0x15/0x30 [videodev]
[ 6028.302705]  v4l2_ioctl+0x69/0xb0 [videodev]
[ 6028.302709]  __x64_sys_ioctl+0x9d/0xe0
[ 6028.302711]  do_syscall_64+0x58/0x90
[ 6028.302712]  ? do_syscall_64+0x67/0x90
[ 6028.302712]  ? do_syscall_64+0x67/0x90
[ 6028.302713]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 6028.302715] RIP: 0033:0x7f8631712d8f
[ 6028.302717] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 
00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[ 6028.302717] RSP: 002b:7ffd35484ed0 EFLAGS: 0246 ORIG_RAX: 
0010
[ 6028.302719] RAX: ffda RBX: 0400 RCX: 7f8631712d8f
[ 6028.302720] RDX: 7ffd35485050 RSI: c02c5625 RDI: 0032
[ 6028.302720] RBP: 000b R08: 0a58 R09: 000b
[ 6028.302721] R10: 0008000c R11: 0246 R12: 7ffd35485058
[ 6028.302721] R13: 7ffd35485050 R14: 55959cc26a48 R15: 0032
[ 6028.302723]  
[ 6028.302724] 

```

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-modules-extra-5.19.0-29-generic 5.19.0-29.30
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  stolk  2160 F wireplumber
 /dev/snd/controlC0:  stolk  2160 F wireplumber
 /dev/snd/seq:stolk  2138 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 17 10:12:44 2023
Dependencies:
 linux-modules-5.19.0-29-generic 5.19.0-29.30
 wireless-regdb 2022.06.06-0ubuntu1
InstallationDate: Installed on 2022-08-26 (144 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825)
MachineType: ASUS System Product Name

[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu6

---
alsa-ucm-conf (1.2.6.3-1ubuntu6) lunar; urgency=medium

  * d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
 - Backport patch to fix micmute LED. (LP: #2002373)

  * d/p/sof-hda-dsp-Set-Dmic0-Capture-Switch-on.patch
 - Backport patch to fix capture switch default value. (LP: #2001896)

 -- Andy Chi   Tue, 17 Jan 2023 17:52:51 +0800

** Changed in: alsa-ucm-conf (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

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

Title:
  sof-hda-dsp internal mic default off after fresh install

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Device with sof-hda-dsp sound card has internal mic off after fresh install

  [Test Plan]
  On the platform with sofhdadsp sound card
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal mic should be on by default

  [Where problems could occur]
  The change takes place on platform with sof-hda-dsp sound card, and it only 
be executed during boot sequence, it won't impact the stored state.
  However, it will change user default expectation after fresh installation.

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/259

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


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

[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu6

---
alsa-ucm-conf (1.2.6.3-1ubuntu6) lunar; urgency=medium

  * d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
 - Backport patch to fix micmute LED. (LP: #2002373)

  * d/p/sof-hda-dsp-Set-Dmic0-Capture-Switch-on.patch
 - Backport patch to fix capture switch default value. (LP: #2001896)

 -- Andy Chi   Tue, 17 Jan 2023 17:52:51 +0800

** Changed in: alsa-ucm-conf (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

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

Title:
  Mic Mute LED doesn't work on DMIC laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Mic mute LED doesn't work on Intel-based HP laptops.

  [Fix]
  Due to recent change on how kernel creates sound LEDs, there are two captures 
are registered, one from SoF and one from HDA. The SoF one is the "real" 
capture system uses.

  Since physical LED only gets light up when _all_ captures are muted,
  detach the HDA one so micmute LED only need to consider SoF capture's
  mute status.

  [Test]
  The mic mute LED works again on DMIC laptops.

  The legacy HDA systems are unaffected.

  [Where problems could occur]
  Theoretically the system may have more than two internal captures registered, 
then disabling one will not be enough.

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


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

[Kernel-packages] [Bug 2001605] Re: Add support for SEV-SNP

[Thadeu Lima de Souza Cascardo]

** Changed in: linux-gcp (Ubuntu Jammy)
 Assignee: (unassigned) => Khaled El Mously (kmously)

** Changed in: linux-gcp (Ubuntu Jammy)
   Importance: Undecided => Critical

** Changed in: linux-gcp (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Add support for SEV-SNP

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  Fix Committed

Bug description:
  Version 3 of AMD's Secure Encrypted Virtualization is called SNP
  (Secure Nested Pages). Support for this has been added to the kernel,
  mostly in v5.19 with some prerequisites from v5.16. This feature is
  requested to be backported to Jammy (5.15).

  More information at
  https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view

  
  [Impact]
  No support for SEV-SNP on AMD EPYC2 CPUs currently

  [Fix]
  Add SEV-SNP support patches.

  [Test]
  Extensive testing by the cloud team over several months, testing general 
functionality under SEV-SNP.

  [Regression Potential]
  This was never working so there should be no risk of regression for 
SEV-SNP.As it does change those files it can have an effect on existing SEV 
functionality in case of a bug. The code is limited so no regression outside of 
SEV is expected.

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


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

[Kernel-packages] [Bug 2003103] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-headers-5.15.0-57 5.15.0-57.63 failed to
  install/upgrade: le paquet est dans un état vraiment incohérent; vous
  devriez  le réinstaller avant de tenter de le configurer.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Des erreurs ont été rencontrées pendant l'exécution :
   linux-headers-5.15.0-57
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-5.15.0-57 5.15.0-57.63
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anne   2252 F pulseaudio
   /dev/snd/controlC1:  anne   2252 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Jan 17 17:19:31 2023
  DpkgHistoryLog:
   Start-Date: 2023-01-17  16:47:49
   Commandline: apt --fix-broken install
   Requested-By: anne (1000)
   Install: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-modules-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-modules-extra-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-headers-5.15.0-58:amd64 (5.15.0-58.64, automatic), 
linux-image-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic)
   Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.57.55, 5.15.0.58.56), 
linux-headers-generic-hwe-22.04:amd64 (5.15.0.56.54, 5.15.0.58.56), 
linux-generic-hwe-22.04:amd64 (5.15.0.57.55, 5.15.0.58.56)
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2022-06-20 (211 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20BUS05W00
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=72acf307-3550-4cf4-add0-2153e772fae0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  SourcePackage: linux
  Title: package linux-headers-5.15.0-57 5.15.0-57.63 failed to 
install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BUS05W00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: N11424
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:br1.19:efr1.2:svnLENOVO:pn20BUS05W00:pvrThinkPadT450:rvnLENOVO:rn20BUS05W00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BU_BU_Think_FM_ThinkPadT450:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BUS05W00
  dmi.product.sku: LENOVO_MT_20BU_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2003103] [NEW] package linux-headers-5.15.0-57 5.15.0-57.63 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tent

[An Ne]

Public bug reported:

Des erreurs ont été rencontrées pendant l'exécution :
 linux-headers-5.15.0-57
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-headers-5.15.0-57 5.15.0-57.63
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  anne   2252 F pulseaudio
 /dev/snd/controlC1:  anne   2252 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Jan 17 17:19:31 2023
DpkgHistoryLog:
 Start-Date: 2023-01-17  16:47:49
 Commandline: apt --fix-broken install
 Requested-By: anne (1000)
 Install: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-modules-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-modules-extra-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-headers-5.15.0-58:amd64 (5.15.0-58.64, automatic), 
linux-image-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic)
 Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.57.55, 5.15.0.58.56), 
linux-headers-generic-hwe-22.04:amd64 (5.15.0.56.54, 5.15.0.58.56), 
linux-generic-hwe-22.04:amd64 (5.15.0.57.55, 5.15.0.58.56)
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
InstallationDate: Installed on 2022-06-20 (211 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: LENOVO 20BUS05W00
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=72acf307-3550-4cf4-add0-2153e772fae0 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu7
SourcePackage: linux
Title: package linux-headers-5.15.0-57 5.15.0-57.63 failed to install/upgrade: 
le paquet est dans un état vraiment incohérent; vous devriez  le réinstaller 
avant de tenter de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/06/2015
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET54WW (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BUS05W00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: N11424
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:br1.19:efr1.2:svnLENOVO:pn20BUS05W00:pvrThinkPadT450:rvnLENOVO:rn20BUS05W00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BU_BU_Think_FM_ThinkPadT450:
dmi.product.family: ThinkPad T450
dmi.product.name: 20BUS05W00
dmi.product.sku: LENOVO_MT_20BU_BU_Think_FM_ThinkPad T450
dmi.product.version: ThinkPad T450
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-headers-5.15.0-57 5.15.0-57.63 failed to
  install/upgrade: le paquet est dans un état vraiment incohérent; vous
  devriez  le réinstaller avant de tenter de le configurer.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Des erreurs ont été rencontrées pendant l'exécution :
   linux-headers-5.15.0-57
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-5.15.0-57 5.15.0-57.63
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anne   2252 F pulseaudio
   /dev/snd/controlC1:  anne   2252 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Jan 17 17:19:31 2023
  DpkgHistoryLog:
   Start-Date: 2023-01-17  16:47:49
   Commandline: apt --fix-broken install
   Requested-By: anne (1000)
   Install: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-modules-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-modules-extra-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic), 
linux-headers-5.15.0-58:amd64 (5.15.0-58.64, automatic), 
linux-image-5.15.0-58-generic:amd64 (5.15.0-58.64, automatic)
   Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.57.55, 5.15.0.58.56), 
linux-headers-generic-hwe-22.04:amd64 (5.15.0.56.54, 5.15.0.58.56), 
linux-generic-hwe-22.04:amd64 (5.15.0.57.55, 

[Kernel-packages] [Bug 2002658] Re: Kinetic linux-azure - Enable TDX guest driver w/MSFT Hyper-v

[Tim Gardner]

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

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

Title:
  Kinetic linux-azure - Enable TDX guest driver w/MSFT Hyper-v

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Support for Intel TDX guest driver is just now appearing upstream.
  This patch set is a backport of the patches essential to enabling TDX
  guest support on the Microsoft hypervisor.

  Most of these patches are not yet upstream, but are considered benign
  with respect to MSFT hypervisors that do not yet have support for TDX.
  I have boot tested on an existing Hyper-v hypervisor to ensure
  backwards compatibility.

  This patch set will eventually be replaced by upstream patches.

  [Test Plan]

  Boot on a TDX enabled Hyper-v instance.

  [Where things could go wrong]

  Existing Azure instances could have boot issues.

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


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

[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

[Frank Heimes]

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

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * In a secure execution guest, the external interrupt for the SIGP
 external call order is delivered twice to a VCPU even though it was 
 only sent once.

   * Under PV (protected virtualization), external call interrupts are
     delivered by the SIGP interpretation facility, without KVM's
     involvement.
     But, if the receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered.
     Hence, in this case, the SIGP external call order causes
     an interception.

   * In response, KVM only needs to wake the receiving VCPU.
     Interrupt delivery is then handled by the SIGP interpretation facility.

   * KVM wrongly assumed it also needs to request injection for the
     external call interrupt after the respective intercept, causing the
     interrupt to be delivered twice:
     * once through the SIGP interpretation facility
     * and once through the interrupt injection control by KVM.

   * Solution is to add appropriate special handling for 108 external
     call intercepts.

  [Fix]

   * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
     "KVM: s390: pv: don't present the ecall interrupt twice"

  [Test Case]

   * Have an Secure Execution (PV) environment setup on an
     IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).

   * Apply kvm-unit-test submitted upstream:
     "[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
  orders in enabled wait"

   * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV

   * Check logs/smp_PV.log.
     If system is affected, the following line can be found:
     "ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
  (code 0x1202): on cpu 1 at 0x11958"

   * If the system is not affected, the line should look like this:
     "PASS: smp: psw wait: ecall: received"

  [Regression Potential / What can go wrong]

   * The handle_pv_notification can be wrong and misleading
     in case 'ret' is not handled correctly.

   * trace_kvm_s390_handle_sigp_pei might not be called correctly,
     now after the if condition.

   * In worst case the external interrupt could not be delivered
     at all or still too often.

  [Other]

   * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
     so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
     and 22.10/5.19.

   * But the patch got properly tagged for upstream stable:
     Cc:  # 5.7
     Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

   * And with that it got already picked up and is included in:
     22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
     22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.

   * So the only Ubuntu release that is affected is 20.04/focal.
  __

  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the
     SIGP external call order is delivered twice to a VCPU even
     though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
     interpretation facility, without KVM's involvement. But, if the
     receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered. Hence,
     in this case, the SIGP external call order causes an
     interception. In response, KVM only needs to wake the receiving
     VCPU. Interrupt delivery is then handled by the SIGP
     interpretation facility.

     KVM wrongfuly assumed it also needs to request injection for 
the
     external call interrupt after the respective intercept, causing
     the interrupt to be delivered twice: once through the SIGP
     interpretation facility and once through the interrupt 
injection
     control by KVM.
  Solution:  Add appropriate special handling for 108 external call
     intercepts.
  Reproduction:  0. Apply kvm-unit-test submitted upstream
    ("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
    call orders in enabled wait").
     1. Run the smp_PV kvm-unit-test:
  ./run_tests.sh smp_PV
     2. 

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions


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

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

[beadon]

Spelling error :  "When I woke the machine..."

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.4.0-1095.103
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-aws

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

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

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


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

[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.4.0-1095.103
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-aws verification-needed-focal

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

Title:
  md: Replace snprintf with scnprintf

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.4.0-1095.103
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-aws verification-needed-focal

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * In a secure execution guest, the external interrupt for the SIGP
 external call order is delivered twice to a VCPU even though it was 
 only sent once.

   * Under PV (protected virtualization), external call interrupts are
     delivered by the SIGP interpretation facility, without KVM's
     involvement.
     But, if the receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered.
     Hence, in this case, the SIGP external call order causes
     an interception.

   * In response, KVM only needs to wake the receiving VCPU.
     Interrupt delivery is then handled by the SIGP interpretation facility.

   * KVM wrongly assumed it also needs to request injection for the
     external call interrupt after the respective intercept, causing the
     interrupt to be delivered twice:
     * once through the SIGP interpretation facility
     * and once through the interrupt injection control by KVM.

   * Solution is to add appropriate special handling for 108 external
     call intercepts.

  [Fix]

   * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
     "KVM: s390: pv: don't present the ecall interrupt twice"

  [Test Case]

   * Have an Secure Execution (PV) environment setup on an
     IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).

   * Apply kvm-unit-test submitted upstream:
     "[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
  orders in enabled wait"

   * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV

   * Check logs/smp_PV.log.
     If system is affected, the following line can be found:
     "ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
  (code 0x1202): on cpu 1 at 0x11958"

   * If the system is not affected, the line should look like this:
     "PASS: smp: psw wait: ecall: received"

  [Regression Potential / What can go wrong]

   * The handle_pv_notification can be wrong and misleading
     in case 'ret' is not handled correctly.

   * trace_kvm_s390_handle_sigp_pei might not be called correctly,
     now after the if condition.

   * In worst case the external interrupt could not be delivered
     at all or still too often.

  [Other]

   * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
     so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
     and 22.10/5.19.

   * But the patch got properly tagged for upstream stable:
     Cc:  # 5.7
     Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

   * And with that it got already picked up and is included in:
     22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
     22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.

   * So the only Ubuntu release that is affected is 20.04/focal.
  __

  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the
     SIGP external call order is delivered twice to a VCPU even
     though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
     interpretation facility, without KVM's involvement. But, if the
     receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered. Hence,
     in this case, the SIGP external call order causes an
     interception. In response, KVM only needs to wake the receiving
     VCPU. Interrupt delivery is then handled by the SIGP
     interpretation facility.

     KVM wrongfuly assumed it also needs to request injection for 
the
     

[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.4.0-1095.103
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-aws

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

Title:
  Fix rfkill causing soft blocked wifi

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Need this patch in so a BIOS upgrade won't cause issues on HP laptops.

  commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a
  Author: Jorge Lopez 
  Date:   Fri Oct 28 10:55:27 2022 -0500

   platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded
  strange char "^@" which printed out every second and makes login
  nearly impossible. Also the below messages were shown both in console
  and journal/dmesg every second:

  usb 1-3: Device not responding to setup address.
  usb 1-3: device not accepting address 4, error -71
  usb 1-3: device descriptor read/all, error -71
  usb usb1-port3: unable to enumerate USB device

  Wifi is soft blocked by checking rfkill. When unblocked manually,
  after few seconds it would be soft blocked again. So I was suspecting
  something triggered rfkill to soft block wifi.  At the end it was
  fixed by removing hp_wmi module.

  The root cause is the way hp-wmi driver handles command 1B on
  post-2009 BIOS.  In pre-2009 BIOS, command 1Bh return 0x4 to indicate
  that BIOS no longer controls the power for the wireless devices.

  Signed-off-by: Jorge Lopez 
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468
  Reviewed-by: Mario Limonciello 
  Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com
  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede 
  Signed-off-by: Hans de Goede 

  [Test case]

  test on a HP laptop with the new BIOS

  [Where problems could occur]

  from the commit:
    * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that
    * BIOS no longer controls the power for the wireless
    * devices. All features supported by this command will no
    * longer be supported.

  anyone running a laptop with obsolete pre-2009 BIOS probably won't
  notice the missing feature at this point.

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.4.0-1095.103
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-aws verification-needed-focal

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions


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

[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.4.0-1095.103
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-aws

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

Title:
  Expose built-in trusted and revoked certificates

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [ Impact ]

   * Kernels have a set of builtin trusted and revoked certificates as a bundle
   * It is not very easy to access them, one needs to either download linux 
kernel package source code; or boot the kernel look up builtin hashes; and then 
find certificates externally
   * It would be more convenient for inspection to expose these in the 
buildinfo package, which already exposes auxiliary kernel information

  [ Test Plan ]

   * sudo apt install linux-buildinfo-$(uname -r)
   * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and 
contains livepatch cert
   * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists 
and contains 2012 cert

  Example output:
  $ grep Subject: -r usr/lib/linux
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = 
Canonical Ltd. Live Patch Signing
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, 
ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel 
Module Signing
  usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: 
C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical 
Ltd. Secure Boot Signing

  
  [ Where problems could occur ]

   * buildinfo is an auxiliary package not installed by default, but
  used by developer tooling and packaging.

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


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

[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install

[Andy Chi]

** Tags added: originate-from-2003089 stella

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

Title:
  sof-hda-dsp internal mic default off after fresh install

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  Device with sof-hda-dsp sound card has internal mic off after fresh install

  [Test Plan]
  On the platform with sofhdadsp sound card
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal mic should be on by default

  [Where problems could occur]
  The change takes place on platform with sof-hda-dsp sound card, and it only 
be executed during boot sequence, it won't impact the stored state.
  However, it will change user default expectation after fresh installation.

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/259

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


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

[Kernel-packages] [Bug 1995004] Re: Increase stability with connection tracking offload

[Launchpad Bug Tracker]

This bug was fixed in the package linux-bluefield - 5.4.0-1054.60

---
linux-bluefield (5.4.0-1054.60) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1054.60 -proposed tracker (LP:
#1997808)

  * Increase stability with connection tracking offload (LP: #1995004)
- net: Fix return value of qdisc ingress handling on success
- netfilter: conntrack: annotate data-races around ct->timeout
- netfilter: conntrack: remove unneeded nf_ct_put
- netfilter: conntrack: convert to refcount_t api
- netfilter: flowtable: Make sure GC works periodically in idle system
- netfilter: flowtable: avoid possible false sharing
- netfilter: flowtable: fix excessive hw offload attempts after failure
- netfilter: nf_flowtable: expose nf_flow_table_gc_cleanup()
- netfilter: flowtable: add function to invoke garbage collection 
immediately
- netfilter: flowtable: fix stuck flows on cleanup due to pending work

  * bluefield-edac: Potentially overflowing expression (LP: #1995109)
- SAUCE: bluefield-edac: Fix potential integer overflow

  [ Ubuntu: 5.4.0-136.153 ]

  * focal/linux: 5.4.0-136.153 -proposed tracker (LP: #1997835)
  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates
  * [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait
(LP: #1995941)
- KVM: s390: pv: don't present the ecall interrupt twice
  * [UBUNTU 20.04] boot: Add s390x secure boot trailer (LP: #1996071)
- s390/boot: add secure boot trailer
  * Fix rfkill causing soft blocked wifi (LP: #1996198)
- platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi
  * md: Replace snprintf with scnprintf (LP: #1993315)
- md: Replace snprintf with scnprintf
  * input/keyboard: the keyboard on some Asus laptops can't work (LP: #1992266)
- ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA
- ACPI: resource: Add ASUS model S5402ZA to quirks
  * Focal update: v5.4.218 upstream stable release (LP: #1995530)
- mm: pagewalk: Fix race between unmap and page walker
- perf tools: Fixup get_current_dir_name() compilation
- firmware: arm_scmi: Add SCMI PM driver remove routine
- dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
- dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent 
API
  failure
- ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
- scsi: qedf: Fix a UAF bug in __qedf_probe()
- net/ieee802154: fix uninit value bug in dgram_sendmsg
- um: Cleanup syscall_handler_t cast in syscalls_32.h
- um: Cleanup compiler warning in arch/x86/um/tls_32.c
- arch: um: Mark the stack non-executable to fix a binutils warning
- usb: mon: make mmapped memory read only
- USB: serial: ftdi_sio: fix 300 bps rate for SIO
- mmc: core: Replace with already defined values for readability
- mmc: core: Terminate infinite loop in SD-UHS voltage switch
- rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
- nilfs2: fix leak of nilfs_root in case of writer thread creation failure
- nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
- ceph: don't truncate file in atomic_open
- random: clamp credited irq bits to maximum mixed
- ALSA: hda: Fix position reporting on Poulsbo
- efi: Correct Macmini DMI match in uefi cert quirk
- USB: serial: qcserial: add new usb-id for Dell branded EM7455
- random: restore O_NONBLOCK support
- random: avoid reading two cache lines on irq randomness
- random: use expired timer rather than wq for mixing fast pool
- Input: xpad - add supported devices as contributed on github
- Input: xpad - fix wireless 360 controller breaking after suspend
- Linux 5.4.218
  * Focal update: v5.4.217 upstream stable release (LP: #1995528)
- xfs: fix misuse of the XFS_ATTR_INCOMPLETE flag
- xfs: introduce XFS_MAX_FILEOFF
- xfs: truncate should remove all blocks, not just to the end of the page
  cache
- xfs: fix s_maxbytes computation on 32-bit kernels
- xfs: fix IOCB_NOWAIT handling in xfs_file_dio_aio_read
- xfs: refactor remote attr value buffer invalidation
- xfs: fix memory corruption during remote attr value buffer invalidation
- xfs: move incore structures out of xfs_da_format.h
- xfs: streamline xfs_attr3_leaf_inactive
- xfs: fix uninitialized variable in xfs_attr3_leaf_inactive
- xfs: remove unused variable 'done'
- Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
- docs: update mediator information in CoC docs
- Linux 5.4.217
  * Focal update: v5.4.216 upstream stable release (LP: #1995526)
- uas: add no-uas quirk for Hiksemi usb_disk
- usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
- uas: ignore UAS for Thinkplus chips
- net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
- clk: 

[Kernel-packages] [Bug 1995109] Re: bluefield-edac: Potentially overflowing expression

[Launchpad Bug Tracker]

This bug was fixed in the package linux-bluefield - 5.4.0-1054.60

---
linux-bluefield (5.4.0-1054.60) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1054.60 -proposed tracker (LP:
#1997808)

  * Increase stability with connection tracking offload (LP: #1995004)
- net: Fix return value of qdisc ingress handling on success
- netfilter: conntrack: annotate data-races around ct->timeout
- netfilter: conntrack: remove unneeded nf_ct_put
- netfilter: conntrack: convert to refcount_t api
- netfilter: flowtable: Make sure GC works periodically in idle system
- netfilter: flowtable: avoid possible false sharing
- netfilter: flowtable: fix excessive hw offload attempts after failure
- netfilter: nf_flowtable: expose nf_flow_table_gc_cleanup()
- netfilter: flowtable: add function to invoke garbage collection 
immediately
- netfilter: flowtable: fix stuck flows on cleanup due to pending work

  * bluefield-edac: Potentially overflowing expression (LP: #1995109)
- SAUCE: bluefield-edac: Fix potential integer overflow

  [ Ubuntu: 5.4.0-136.153 ]

  * focal/linux: 5.4.0-136.153 -proposed tracker (LP: #1997835)
  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates
  * [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait
(LP: #1995941)
- KVM: s390: pv: don't present the ecall interrupt twice
  * [UBUNTU 20.04] boot: Add s390x secure boot trailer (LP: #1996071)
- s390/boot: add secure boot trailer
  * Fix rfkill causing soft blocked wifi (LP: #1996198)
- platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi
  * md: Replace snprintf with scnprintf (LP: #1993315)
- md: Replace snprintf with scnprintf
  * input/keyboard: the keyboard on some Asus laptops can't work (LP: #1992266)
- ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA
- ACPI: resource: Add ASUS model S5402ZA to quirks
  * Focal update: v5.4.218 upstream stable release (LP: #1995530)
- mm: pagewalk: Fix race between unmap and page walker
- perf tools: Fixup get_current_dir_name() compilation
- firmware: arm_scmi: Add SCMI PM driver remove routine
- dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
- dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent 
API
  failure
- ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
- scsi: qedf: Fix a UAF bug in __qedf_probe()
- net/ieee802154: fix uninit value bug in dgram_sendmsg
- um: Cleanup syscall_handler_t cast in syscalls_32.h
- um: Cleanup compiler warning in arch/x86/um/tls_32.c
- arch: um: Mark the stack non-executable to fix a binutils warning
- usb: mon: make mmapped memory read only
- USB: serial: ftdi_sio: fix 300 bps rate for SIO
- mmc: core: Replace with already defined values for readability
- mmc: core: Terminate infinite loop in SD-UHS voltage switch
- rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
- nilfs2: fix leak of nilfs_root in case of writer thread creation failure
- nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
- ceph: don't truncate file in atomic_open
- random: clamp credited irq bits to maximum mixed
- ALSA: hda: Fix position reporting on Poulsbo
- efi: Correct Macmini DMI match in uefi cert quirk
- USB: serial: qcserial: add new usb-id for Dell branded EM7455
- random: restore O_NONBLOCK support
- random: avoid reading two cache lines on irq randomness
- random: use expired timer rather than wq for mixing fast pool
- Input: xpad - add supported devices as contributed on github
- Input: xpad - fix wireless 360 controller breaking after suspend
- Linux 5.4.218
  * Focal update: v5.4.217 upstream stable release (LP: #1995528)
- xfs: fix misuse of the XFS_ATTR_INCOMPLETE flag
- xfs: introduce XFS_MAX_FILEOFF
- xfs: truncate should remove all blocks, not just to the end of the page
  cache
- xfs: fix s_maxbytes computation on 32-bit kernels
- xfs: fix IOCB_NOWAIT handling in xfs_file_dio_aio_read
- xfs: refactor remote attr value buffer invalidation
- xfs: fix memory corruption during remote attr value buffer invalidation
- xfs: move incore structures out of xfs_da_format.h
- xfs: streamline xfs_attr3_leaf_inactive
- xfs: fix uninitialized variable in xfs_attr3_leaf_inactive
- xfs: remove unused variable 'done'
- Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
- docs: update mediator information in CoC docs
- Linux 5.4.217
  * Focal update: v5.4.216 upstream stable release (LP: #1995526)
- uas: add no-uas quirk for Hiksemi usb_disk
- usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
- uas: ignore UAS for Thinkplus chips
- net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
- clk: 

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

No further verifications needed on these custom kernels mentioned above.

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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions


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

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

-- 
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:
  Fix Committed
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:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  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
   

[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  Fix RPL-S support on powercap/intel_rapl

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

Bug description:
  [Impact]
  proc_thermal driver is not loaded

  [Fix]
  Add RPL-S id on device id table of powercap/intel_rapl.

  [Test Case]
  1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal

  [Where problems could occur]
  Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features.

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


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

[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  TEE Support for CCP driver

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing support for of AMD Secure Processor device for PCI ID 0x14CA.

  [Fix]

  A patch is being proposed in upstream and CC-ed stable.

  [Test Case]

  Without a proper fix, following error appears in dmesg:

ccp :02:00.5: tee: missing driver data
ccp :02:00.5: tee initialization failed

  [Where problems could occur]

  This adds a new driver data entry to support ccp device that provides
  both sev and tee feature at the same time.

  [Other Info]

  While this is proposed to stable 5.15+, all kernels >= 5.15 are
  nominated for fix.

  == original bug description ==

  Client and datacenter Zen4 SOC same PCI-ID but offer different
  functionality from the PSP.

  Genoa offers SEV, Client part offers TEE.
  This patch fixes an ERR level message and CCP driver functionality not 
working.

  ccp :02:00.5: tee: missing driver data
  ccp :02:00.5: tee initialization failed

  https://lore.kernel.org/linux-
  
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

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


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

[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

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

Bug description:
  [Impact]
  turbostat doesn't show the correct fields for RPL-S.
  This's a wrong column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI

  [Fix]
  Add RPL-S support in turbostat

  [Test Case]
  1. run "turbostat --list"
  2. check the output, this is a correct column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_%

  [Where problems could occur]
  Low, just add a devcie id to support RPL-S.

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


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

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
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]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

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


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

[Kernel-packages] [Bug 1991974] Re: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  AMD Yellow Carp system hang on HDMI plug in/out over dock station.

  [Fix]

  5 patches from mainline kernel v5.16 to be backported.

  [Test Case]

  Plug and unplug HDMI cable connected external monitor on a docking
  station connected to HP Lockheed platform to try trigger system hang.

  [Where problems could occur]

  This series tries to address null state of MST link encoder, and no know
  fix commits for them ever since till current mainline HEAD.

  [Other Info]

  While this is already available in v5.16 kernel and on, only 5.15 and
  oem-5.14 are nominated for fix.

  == original bug description ==

  In order to resolve system hang during docking scenario with HDMI plug
  in/out, these patches are needed into hwe-5.15.

  v5.16
  43dc2ad5 drm/amd/display: Fix MST link encoder availability check
  e3ab29aa drm/amd/display: Fix for link encoder access for MST
  7fb52632 drm/amd/display: FEC configuration for dpia links
  ed0ffb5d drm/amd/display: FEC configuration for dpia links in MST mode
  c9beecc5 drm/amd/display: Add work around for tunneled MST

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


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

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

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


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

[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  md: Replace snprintf with scnprintf

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  Fix ath11k deadlock on WCN6855

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

Bug description:
  [Impact]
  ath11k is in deadlock when stress reboot or suspend on WCN6855.
  sometimes kernel hang.

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions


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

[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  alsa: soc: the kernel print UBSAN calltrace on the machine with
  cs35l41 codec

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released

Bug description:
  The cs35l41 codec driver was backported to Jammy kernel a couple of
  months ago, recently the Jammy kernel was adopted as the hwe kernel
  for OEM machines and with this kernel the UBSAN calltrace was seen,
  need to backport these 2 patches. Kinetic kernel already has the
  patches, so this SRU is only for Jammy kernel.

  [Impact]
  Install the 5.15 hwe kernel on the machines with cs35l41
  codec, after booting and check the dmesg, there is a UBSAN calltrace.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, check the dmesg, there
  is no UBSAN calltrace, and test the audio functions, all input
  and output devices coudl work as well as before.

  
  [Where problems could occur]
  The patch only affects the cirruslogic asoc codec driver, if it
  could introduce the regression, it will be on the machines with
  cs codec, and it will make the audio driver initialization fail
  and make the system lose the audio function. But this possibility
  is very low, we tested the patches on many oem machines, all
  worked well.

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


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

[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  Fix rfkill causing soft blocked wifi

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Need this patch in so a BIOS upgrade won't cause issues on HP laptops.

  commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a
  Author: Jorge Lopez 
  Date:   Fri Oct 28 10:55:27 2022 -0500

   platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded
  strange char "^@" which printed out every second and makes login
  nearly impossible. Also the below messages were shown both in console
  and journal/dmesg every second:

  usb 1-3: Device not responding to setup address.
  usb 1-3: device not accepting address 4, error -71
  usb 1-3: device descriptor read/all, error -71
  usb usb1-port3: unable to enumerate USB device

  Wifi is soft blocked by checking rfkill. When unblocked manually,
  after few seconds it would be soft blocked again. So I was suspecting
  something triggered rfkill to soft block wifi.  At the end it was
  fixed by removing hp_wmi module.

  The root cause is the way hp-wmi driver handles command 1B on
  post-2009 BIOS.  In pre-2009 BIOS, command 1Bh return 0x4 to indicate
  that BIOS no longer controls the power for the wireless devices.

  Signed-off-by: Jorge Lopez 
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468
  Reviewed-by: Mario Limonciello 
  Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com
  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede 
  Signed-off-by: Hans de Goede 

  [Test case]

  test on a HP laptop with the new BIOS

  [Where problems could occur]

  from the commit:
    * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that
    * BIOS no longer controls the power for the wireless
    * devices. All features supported by this command will no
    * longer be supported.

  anyone running a laptop with obsolete pre-2009 BIOS probably won't
  notice the missing feature at this point.

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


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

[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.15.0-1032.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  Expose built-in trusted and revoked certificates

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [ Impact ]

   * Kernels have a set of builtin trusted and revoked certificates as a bundle
   * It is not very easy to access them, one needs to either download linux 
kernel package source code; or boot the kernel look up builtin hashes; and then 
find certificates externally
   * It would be more convenient for inspection to expose these in the 
buildinfo package, which already exposes auxiliary kernel information

  [ Test Plan ]

   * sudo apt install linux-buildinfo-$(uname -r)
   * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and 
contains livepatch cert
   * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists 
and contains 2012 cert

  Example output:
  $ grep Subject: -r usr/lib/linux
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = 
Canonical Ltd. Live Patch Signing
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, 
ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel 
Module Signing
  usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: 
C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical 
Ltd. Secure Boot Signing

  
  [ Where problems could occur ]

   * buildinfo is an auxiliary package not installed by default, but
  used by developer tooling and packaging.

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


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

[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install

[Sebastien Bacher]

** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
   Status: New => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  sof-hda-dsp internal mic default off after fresh install

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  Device with sof-hda-dsp sound card has internal mic off after fresh install

  [Test Plan]
  On the platform with sofhdadsp sound card
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal mic should be on by default

  [Where problems could occur]
  The change takes place on platform with sof-hda-dsp sound card, and it only 
be executed during boot sequence, it won't impact the stored state.
  However, it will change user default expectation after fresh installation.

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/259

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


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

[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops

[Sebastien Bacher]

** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
   Status: Confirmed => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

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

Title:
  Mic Mute LED doesn't work on DMIC laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  Mic mute LED doesn't work on Intel-based HP laptops.

  [Fix]
  Due to recent change on how kernel creates sound LEDs, there are two captures 
are registered, one from SoF and one from HDA. The SoF one is the "real" 
capture system uses.

  Since physical LED only gets light up when _all_ captures are muted,
  detach the HDA one so micmute LED only need to consider SoF capture's
  mute status.

  [Test]
  The mic mute LED works again on DMIC laptops.

  The legacy HDA systems are unaffected.

  [Where problems could occur]
  Theoretically the system may have more than two internal captures registered, 
then disabling one will not be enough.

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


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

[Kernel-packages] [Bug 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.19.0-1017.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-kinetic
** Tags added: kernel-spammed-kinetic-linux-azure verification-needed-kinetic

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

Title:
  [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-
  average luminance

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  The brightness is not changed obviously during 200 to 255 on AMD
  or 400 to 512 on Intel..

  [Fix]
  Read HDR meta to detect the max and min luminance.
  max_cll defines the content light luminance for individual pixel.
  max_fall defines frame-average level luminance.
  Use max_fall value instead of max_cll as a limit for brightness control.

  [Test]
  Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel 
and OLED panel. The brightness is changed more obivously on OLED panel, and
  no affect on LCD panel.

  [Where problems could occur]
  Low risk, It may cause the max brightness can't be set.

  All 3 patches are in drm-misc tree.

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


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

[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.19.0-1017.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-kinetic-linux-azure

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1983656

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following ip parameters

  $ sudo ip a a 192.168.1.7/24 dev enp7s0