[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1019.19)

[Ubuntu SRU Bot]

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

lttng-modules/2.13.1-1 (arm64, 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-aws

[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 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices

[Kinga Tanska]

We've installed Ubuntu Kinetic with 5.15 kernel and updated it to 5.19.0-051900 
(which was not available in default ubuntu repo, and was taken from here 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/amd64/ ).
Issue does not occur with this configuration.

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

Title:
  [VROC] Kernel does not contain fixes for iostat for md devices

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.13 source package in Focal:
  In Progress
Status in linux source package in Impish:
  Won't Fix
Status in linux-hwe-5.13 source package in Impish:
  Invalid

Bug description:
  Hello,

  I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does
  not contain fixes for IO statistics for md devices. IO statistics for
  md devices were added to kernel 5.10
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d)
  but then bug for double fault was reported and this patch was reverted
  by Guoqing Jiang
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8).

  Guoqing Jiang added series of patches which fixes problem and adds IO stats 
for md devices on top on the revert patch:
  - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f)
  - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b)

  I checked that kernel used in ubuntu 22.04 contains only patch with revert - 
iostat does not report for md devices 
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang)
  Please consider adding series of patches described above.

  Regards,
  Kinga Tanska

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


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

[Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS

[conie chang]

Reply Christian's suggest #7

I tried not to create one VM and check the syslog after run "virt-
manager", and then it also shows the these error message.


I am trying to narrow down the issue, and only execue the "systemctl restart 
libvirtd" instead of open "virt-manager". And the error message is also shown 
in syslog.

"internal error: A field data length violates the resource length
boundary."

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

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release

[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)

[Juerg Haefliger]

** Changed in: linux-firmware (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable
  (non-free)

Status in amd64-microcode package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2
  to 3.20220411.1ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions


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

[Kernel-packages] [Bug 1986796] Re: amd64-microcode conflicts with linux-firmware

[Juerg Haefliger]

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: linux-firmware (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  amd64-microcode conflicts with linux-firmware

Status in amd64-microcode package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Occurs on kubuntu, gnome and xfce versions of kinetic proposed -- most
  recent updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: amd64-microcode 3.20191218.1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Aug 17 08:07:09 2022
  InstallationDate: Installed on 2022-06-10 (67 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220610)
  SourcePackage: amd64-microcode
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1986796/+subscriptions


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

[Kernel-packages] [Bug 1987037] [NEW] Backport libbpf (0.5.0-1) to focal

[ethan.hsieh]

Public bug reported:

[Impact]
Backport libbpf (0.5.0-1) to focal

[Where problems could occur]
libbpf is not available on focal

[Test Case]
N/A

[Regression Potential]
No regression issue because it will be a new package on focal


[Other Info]
See LP: #1961130

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


** Tags: oem-priority originate-from-1961130

** Tags added: oem-priority originate-from-1961130

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

Title:
  Backport libbpf (0.5.0-1) to focal

Status in libbpf package in Ubuntu:
  New

Bug description:
  [Impact]
  Backport libbpf (0.5.0-1) to focal

  [Where problems could occur]
  libbpf is not available on focal

  [Test Case]
  N/A

  [Regression Potential]
  No regression issue because it will be a new package on focal

  
  [Other Info]
  See LP: #1961130

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


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

[Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS

[conie chang]

Even I does not create one VM, the messages still show below errors.
I will try Christian's suggest as comment#7 if it works.

===error message===
Aug 19 03:39:32 conie libvirtd[7772]: internal error: A field data length 
violates the resource length boundary.
Aug 19 03:39:32 conie libvirtd[7772]: message repeated 3 times: [ internal 
error: A field data length violates the resource length boundary.]

Thank you.

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

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.fir

[Kernel-packages] [Bug 1986520] ProcCpuinfoMinimal.txt

[conie chang]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609778/+files/ProcCpuinfoMinimal.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEd

[Kernel-packages] [Bug 1986520] ProcCpuinfo.txt

[conie chang]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609777/+files/ProcCpuinfo.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi

[Kernel-packages] [Bug 1986520] Lsusb-v.txt

[conie chang]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609775/+files/Lsusb-v.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product

[Kernel-packages] [Bug 1986520] WifiSyslog.txt

[conie chang]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609782/+files/WifiSyslog.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.p

[Kernel-packages] [Bug 1986520] acpidump.txt

[conie chang]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609783/+files/acpidump.txt

** Changed in: libvirt (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.pro

[Kernel-packages] [Bug 1986520] UdevDb.txt

[conie chang]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1986520/+attachment/5609781/+files/UdevDb.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sk

[Kernel-packages] [Bug 1986520] ProcModules.txt

[conie chang]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609780/+files/ProcModules.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi

[Kernel-packages] [Bug 1986520] ProcInterrupts.txt

[conie chang]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609779/+files/ProcInterrupts.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450

[Kernel-packages] [Bug 1986520] PaInfo.txt

[conie chang]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1986520/+attachment/5609776/+files/PaInfo.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sk

[Kernel-packages] [Bug 1986520] Lspci-vt.txt

[conie chang]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609773/+files/Lspci-vt.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.produ

[Kernel-packages] [Bug 1986520] Lsusb-t.txt

[conie chang]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609774/+files/Lsusb-t.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product

[Kernel-packages] [Bug 1986520] Lspci.txt

[conie chang]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1986520/+attachment/5609772/+files/Lspci.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku:

[Kernel-packages] [Bug 1986520] KernLog.txt

[conie chang]

apport information

** Attachment added: "KernLog.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609771/+files/KernLog.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product

[Kernel-packages] [Bug 1986520] IwConfig.txt

[conie chang]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609770/+files/IwConfig.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.produ

[Kernel-packages] [Bug 1986520] CurrentDmesg.txt

[conie chang]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609769/+files/CurrentDmesg.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  d

[Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS

[conie chang]

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB
  
  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )
  
  Expected behaviors:
  There are no any unexpected errors in system logs.
  
  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-08-18 (0 days ago)
+ InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
+  Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
+  Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Lenovo ThinkEdge SE450
+ Package: linux (not installed)
+ ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 astdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
+ ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-46-generic N/A
+  linux-backports-modules-5.15.0-46-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.4
+ RfKill:
+  
+ Tags:  jammy uec-images
+ Uname: Linux 5.15.0-46-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 08/08/2022
+ dmi.bios.release: 1.23
+ dmi.bios.vendor: Lenovo
+ dmi.bios.version: CME105F-1.23
+ dmi.board.asset.tag: none
+ dmi.board.name: 7D8TCTO1WW
+ dmi.board.vendor: Lenovo
+ dmi.board.version: 05
+ dmi.chassis.asset.tag: none
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: Lenovo
+ dmi.chassis.version: none
+ dmi.ec.firmware.release: 1.40
+ dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
+ dmi.product.family: ThinkSystem
+ dmi.product.name: ThinkEdge SE450
+ dmi.product.sku: 7D8TCTO1WW
+ dmi.product.version: 05
+ dmi.sys.vendor: Lenovo

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1986520/+attachment/5609768/+files/AlsaInfo.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/1986520

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  

[Kernel-packages] [Bug 1899235] Re: [Dell Inspiron 3180] Touchpad freeze after overnight sleep

[Daniel van Vugt]

** Tags added: 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/1899235

Title:
  [Dell Inspiron 3180] Touchpad freeze after overnight sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The real issue is touchpad freeze after wakeup from overnight sleep.
  Mouse though does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Oct 10 08:14:07 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2020-09-03 (36 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3180
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1987004] Re: [Dell Inspiron 3180] Touchpad stops functioning after wakeup

[Daniel van Vugt]

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

** Summary changed:

- Touchpad stops functioning after wakeup
+ [Dell Inspiron 3180] Touchpad stops functioning after wakeup

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** This bug has been marked a duplicate of bug 1899235
   [Dell Inspiron 3180] Touchpad freeze after overnight sleep

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

Title:
  [Dell Inspiron 3180] Touchpad stops functioning after wakeup

Status in linux package in Ubuntu:
  New

Bug description:
  Although it happens randomly. The touchpad stops working where the
  cursor freezes after the system wakes up from suspension mode. The
  mouse, though, does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Aug 18 15:15:02 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Today
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/ubuntu/+source/linux/+bug/1987004/+subscriptions


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

[Kernel-packages] [Bug 1987004] [NEW] [Dell Inspiron 3180] Touchpad stops functioning after wakeup

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Although it happens randomly. The touchpad stops working where the
cursor freezes after the system wakes up from suspension mode. The
mouse, though, does work.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Aug 18 15:15:02 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Once a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Today
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
   Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
MachineType: Dell Inc. Inspiron 3180
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.release: 5.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0918N8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.3.0
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3180
dmi.product.sku: 087E
dmi.product.version: 1.3.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
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

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


** Tags: amd64 apport-bug freeze jammy ubuntu wayland-session
-- 
[Dell Inspiron 3180] Touchpad stops functioning after wakeup
https://bugs.launchpad.net/bugs/1987004
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1018.18)

[Ubuntu SRU Bot]

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

systemd/249.11-0ubuntu3.4 (arm64)
lttng-modules/2.13.1-1 (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-aws

[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 1982014] Re: kernel panics/hangs after upgrading to linux-image-5.4.0-122-generic:amd64

[Angelo Hongens]

Did you get any update on this?

Got some users on the proxmox that also have what seems like the same
problem, including me.

https://forum.proxmox.com/threads/ubuntu-20-04-04-machine-
freezes.112507/#post-488816

I haven’t been able to reproduce it, since I’m not running Ubuntu in
production anymore with a lot of load. I was running CentOS7 and wanted
to switch to Ubuntu, but since my first Ubuntu production machine was
freezing quite some times during a weekend and I lost quite some
customers over it, I switched back to centos here unfortunately.

Hope Ubuntu will one day be stable enough to run in production for my
workload ;)

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

Title:
  kernel panics/hangs after upgrading to linux-
  image-5.4.0-122-generic:amd64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We had a series of unattended-upgrades:
  ```
  Start-Date: 2022-07-13  06:19:32
  Commandline: /usr/bin/unattended-upgrade
  Install: linux-modules-extra-5.4.0-122-generic:amd64 (5.4.0-122.138, 
automatic), linux-modules-5.4.0-122-generic:amd64 (5.4.0-122.138, automatic), 
linux-headers-5.4.0-122:amd64 (5.4.0-122.138, automatic), 
linux-headers-5.4.0-122-generic:amd64 (5.4.0-122.138, automatic), 
linux-image-5.4.0-122-generic:amd64 (5.4.0-122.138, automatic)
  Upgrade: linux-headers-generic:amd64 (5.4.0.121.122, 5.4.0.122.123), 
linux-image-generic:amd64 (5.4.0.121.122, 5.4.0.122.123), linux-generic:amd64 
(5.4.0.121.122, 5.4.0.122.123)
  End-Date: 2022-07-13  06:20:56

  Start-Date: 2022-07-13  06:21:00
  Commandline: /usr/bin/unattended-upgrade
  Remove: linux-headers-5.4.0-120-generic:amd64 (5.4.0-120.136), 
linux-headers-5.4.0-120:amd64 (5.4.0-120.136)
  End-Date: 2022-07-13  06:21:05

  Start-Date: 2022-07-13  06:21:09
  Commandline: /usr/bin/unattended-upgrade
  Remove: linux-modules-extra-5.4.0-120-generic:amd64 (5.4.0-120.136), 
linux-modules-5.4.0-120-generic:amd64 (5.4.0-120.136), 
linux-image-5.4.0-120-generic:amd64 (5.4.0-120.136)
  End-Date: 2022-07-13  06:21:28
  ```

  The same day, I performed a manual upgrade:
  ```
  Start-Date: 2022-07-13  14:20:07
  Commandline: apt upgrade
  Upgrade: pdns-backend-pgsql:amd64 (4.6.2-1pdns.focal, 4.6.3-1pdns.focal), 
pdns-server:amd64 (4.6.2-1pdns.focal, 4.6.3-1pdns.focal), git-man:amd64 
(1:2.25.1-1ubuntu3.4, 1:2.25.1-1ubuntu3.5), git:amd64 (1:2.25.1-1ubuntu3.4, 
1:2.25.1-1ubuntu3.5), linux-firmware:amd64 (1.187.31, 1.187.32), 
pdns-backend-bind:amd64 (4.6.2-1pdns.focal, 4.6.3-1pdns.focal)
  End-Date: 2022-07-13  14:22:01
  ```

  followed by a reboot.

  Within a short period, the computer (bare metal, living in a data
  center) would hang (not respond to console, ping, ssh, ...) or panic.

  After a couple of rounds of asking the IT staff to find the box and
  kick it (sometimes they saw an actual report of a panic, and sometimes
  it just didn't show anything), I reverted `linux-firmware:amd64` to
  `1.187.31` and rebooted. This did not fix the problem.

  Eventually we realized that the earlier thing had upgraded the kernel
  separately. Reverting that to the previous (5.4.0-121.137) kernel
  resulted in a reliable happy box.

  ```
  ii  binutils-x86-64-linux-gnu 2.34-6ubuntu1.3 
 amd64GNU binary utilities, for x86-64-linux-gnu target
  ii  linux-base4.5ubuntu3.7
 all  Linux image base package
  ii  linux-firmware1.187.31
 all  Firmware for Linux kernel drivers
  ii  linux-headers-5.4.0-121   5.4.0-121.137   
 all  Header files related to Linux kernel version 5.4.0
  ii  linux-headers-5.4.0-121-generic   5.4.0-121.137   
 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
  rc  linux-image-5.4.0-100-generic 5.4.0-100.113   
 amd64Signed kernel image generic
  rc  linux-image-5.4.0-104-generic 5.4.0-104.118   
 amd64Signed kernel image generic
  rc  linux-image-5.4.0-105-generic 5.4.0-105.119   
 amd64Signed kernel image generic
  rc  linux-image-5.4.0-107-generic 5.4.0-107.121   
 amd64Signed kernel image generic
  rc  linux-image-5.4.0-109-generic 5.4.0-109.123   
 amd64Signed kernel image generic
  rc  linux-image-5.4.0-110-generic 5.4.0-110.124   
 amd64Signed kernel image generic
  rc  linux-image-5.4.0-113-generic 5.4.0-113.127   
 amd64Signed kernel image generic
  rc  linux-image-5.4.0-117-generic 5.4.0-117.132 

[Kernel-packages] [Bug 1959681] Re: mic not working on HP-EliteBook-830-G7

[Hui Wang]

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

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

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

Title:
  mic not working on HP-EliteBook-830-G7

Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Bionic:
  Incomplete
Status in linux-firmware source package in Focal:
  Incomplete

Bug description:
  There is no audio input from the built-in mic available on Bionic &
  Focal on certain intel audio hw (00:1f.3 Multimedia audio controller
  [0401]: Intel Corporation Device [8086:02c8]) despite trying different
  kernel cmdline options (snd_hda_intel.dmic_detect=0 or
  snd_intel_dspcfg.dsp_driver=1).

  The behavior was similar on Bionic and Focal - no mic listed in 
alsa/pulseaudio mixers. Additionally the following can be found in the kernel 
log:
sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using 
SOF driver
sof-audio-pci :00:1f.3: enabling device ( -> 0002)
sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found

  The situation is different on impish - on this release the mic is
  available out of the box.

  I made a simple test of overwriting sof files inside Focal's linux-
  firmware package with the contents of firmware-sof-signed package from
  impish finding it solved the issue without any trace of errors in the
  logs.

  The same approach did not work on Bionic (despite similar kernel versions 
used in both 5.4.0) - due to HWE). These are some excerpts from Bionic 
launching impish SOF firmware:
   sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel
   sof-audio-pci :00:1f.3: firmware boot complete
   sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU 
Playback not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU 
Capture not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not 
handled

  [ Test Plan ]
  1. Launch Ubuntu desktop on affected hardware.
  2. Open audio mixer (e.g. pulsemixer).
  3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo).

  Expected result:
  Built-in mic is available for use.

  Actual result:
  Built-in mic is missing.

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


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

[Kernel-packages] [Bug 1986796] Re: amd64-microcode conflicts with linux-firmware

[Mark Esler]

The conflicts are resolved with patches for amd64-microcode and linux-
firmware here:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409

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

Title:
  amd64-microcode conflicts with linux-firmware

Status in amd64-microcode package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  Occurs on kubuntu, gnome and xfce versions of kinetic proposed -- most
  recent updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: amd64-microcode 3.20191218.1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Aug 17 08:07:09 2022
  InstallationDate: Installed on 2022-06-10 (67 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220610)
  SourcePackage: amd64-microcode
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1986796/+subscriptions


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

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Ben Hoyt]

A couple of days ago I upgraded my 21.10 system to 22.04 and got this
"out of memory" issue (Dell XPS 15 9550 with 3840x2160 display).

The fix in comment #41 worked (changing the compression to 19), and the
sequence of commands in #44 helped. However, just noting that there are
several typos in #44 that had me stumped for a while (it's the first
time I've used chroot to update grub).

So here are (I think!) the corrected commands to update grub:

$ sudo su -
# mkdir root
# mkdir boot
# mkdir efi
# cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt
# mount /dev/mapper/vgubuntu-root ./root
# mount /dev/nvme0n1p1 ./efi   # was "nvme01p1"
# mount /dev/nvme0n1p2 ./boot  # was "nvme01p2"
# mount -B ./boot ./root/boot
# mount -B ./efi ./root/boot/efi
# mount -B /dev ./root/dev # was: mount -B ./dev ./root/boot/dev
# mount -B /dev/pts ./root/dev/pts # was: mount -B ./dev/pts ./root/boot/dev/pts
# mount -B /proc ./root/proc   # was: mount -B ./proc ./root/proc
# mount -B /sys ./root/sys # was: mount -B ./sys ./root/sys
# chroot ./root
# ### Now edit line 196 of /usr/sbin/mkinitramfs to to use -19 instead of -1
# update-initramfs -u -k all
# update-grub
# exit
# reboot

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent

[Kernel-packages] [Bug 1986995] Re: Focal update: v5.4.202 upstream stable release

[Kamal Mostafa]

** Description changed:

  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.4.202 upstream stable release
     from git://git.kernel.org/
  
- dm: remove special-casing of bio-based immutable singleton target on NVMe
- usb: gadget: u_ether: fix regression in setting fixed MAC address
- tcp: add some entropy in __inet_hash_connect()
- tcp: use different parts of the port_offset for index and offset
- tcp: add small random increments to the source port
- tcp: dynamically allocate the perturb table used by source ports
- tcp: increase source port perturb table to 2^16
- tcp: drop the hash_32() part from the index calculation
- arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer
- Linux 5.4.201
- UBUNTU: Upstream stable to v5.4.201
  random: schedule mix_interrupt_randomness() less often
  ALSA: hda/via: Fix missing beep setup
  ALSA: hda/conexant: Fix missing beep setup
  ALSA: hda/realtek - ALC897 headset MIC no sound
  ALSA: hda/realtek: Add quirk for Clevo PD70PNT
  net: openvswitch: fix parsing of nw_proto for IPv6 fragments
  mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
  ata: libata: add qc->flags in ata_qc_complete_template tracepoint
  dm era: commit metadata in postsuspend after worker stops
  dm mirror log: clear log bits up to BITS_PER_LONG boundary
  random: quiet urandom warning ratelimit suppression message
  USB: serial: option: add Telit LE910Cx 0x1250 composition
  USB: serial: option: add Quectel EM05-G modem
  USB: serial: option: add Quectel RM500K module support
  bpf: Fix request_sock leak in sk lookup helpers
  phy: aquantia: Fix AN when higher speeds than 1G are not advertised
  bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
  net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
  drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
  erspan: do not assume transport header is always set
  net/tls: fix tls_sk_proto_close executed repeatedly
  udmabuf: add back sanity check
  x86/xen: Remove undefined behavior in setup_features()
  MIPS: Remove repetitive increase irq_err_count
  afs: Fix dynamic root getattr
  ice: ethtool: advertise 1000M speeds properly
  regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
  igb: Make DMA faster when CPU is active on the PCIe link
  virtio_net: fix xdp_rxq_info bug after suspend/resume
  Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
  gpio: winbond: Fix error code in winbond_gpio_get()
  s390/cpumf: Handle events cycles and instructions identical
  iio: adc: vf610: fix conversion mode sysfs node name
  xhci: turn off port power in shutdown
  usb: chipidea: udc: check request status before setting device address
  iio:chemical:ccs811: rearrange iio trigger get and register
  iio:accel:bma180: rearrange iio trigger get and register
  iio:accel:mxc4005: rearrange iio trigger get and register
  iio: accel: mma8452: ignore the return value of reset operation
  iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
  iio: trigger: sysfs: fix use-after-free on remove
  iio: adc: stm32: fix maximum clock rate for stm32mp15x
  iio: adc: axp288: Override TS pin bias current for some models
  xtensa: xtfpga: Fix refcount leak bug in setup
  xtensa: Fix refcount leak bug in time.c
  parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
  powerpc: Enable execve syscall exit tracepoint
  powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
  powerpc/powernv: wire up rng during setup_arch
  ARM: dts: imx6qdl: correct PU regulator ramp delay
  ARM: exynos: Fix refcount leak in exynos_map_pmu
  soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
  ARM: Fix refcount leak in axxia_boot_secondary
  ARM: cns3xxx: Fix refcount leak in cns3xxx_init
  modpost: fix section mismatch check for exported init/exit sections
  random: update comment from copy_to_user() -> copy_to_iter()
  kbuild: link vmlinux only once for CONFIG_TRIM_UNUSED_KSYMS (2nd attempt)
  powerpc/pseries: wire up rng during setup_arch()
  Linux 5.4.202
  UBUNTU: Upstream stable to v5.4.202

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

Title:
  Focal update: v5.4.202 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in s

[Kernel-packages] [Bug 1986999] Re: Focal update: v5.4.203 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.4.203 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.203 upstream stable release
-from git://git.kernel.org/
+ drm: remove drm_fb_helper_modinit
+ powerpc/ftrace: Remove ftrace init tramp once kernel init is complete
+ kexec_file: drop weak attribute from arch_kexec_apply_relocations[_add]
+ net: mscc: ocelot: allow unregistered IP multicast flooding
+ ARM: 8989/1: use .fpu assembler directives instead of assembler arguments
+ ARM: 8990/1: use VFP assembler mnemonics in register load/store macros
+ ARM: 8971/1: replace the sole use of a symbol with its definition
+ crypto: arm/sha256-neon - avoid ADRL pseudo instruction
+ crypto: arm/sha512-neon - avoid ADRL pseudo instruction
+ ARM: 8933/1: replace Sun/Solaris style flag on section directive
+ ARM: 8929/1: use APSR_nzcv instead of r15 as mrc operand
+ ARM: OMAP2+: drop unnecessary adrl
+ ARM: 9029/1: Make iwmmxt.S support Clang's integrated assembler
+ crypto: arm - use Kconfig based compiler checks for crypto opcodes
+ crypto: arm/ghash-ce - define fpu before fpu registers are referenced
+ Linux 5.4.203
+ UBUNTU: Upstream stable to v5.4.203

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

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

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

** Changed in: linux (Ubuntu Focal)
 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/1986999

Title:
  Focal update: v5.4.203 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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.4.203 upstream stable release
     from git://git.kernel.org/

  drm: remove drm_fb_helper_modinit
  powerpc/ftrace: Remove ftrace init tramp once kernel init is complete
  kexec_file: drop weak attribute from arch_kexec_apply_relocations[_add]
  net: mscc: ocelot: allow unregistered IP multicast flooding
  ARM: 8989/1: use .fpu assembler directives instead of assembler arguments
  ARM: 8990/1: use VFP assembler mnemonics in register load/store macros
  ARM: 8971/1: replace the sole use of a symbol with its definition
  crypto: arm/sha256-neon - avoid ADRL pseudo instruction
  crypto: arm/sha512-neon - avoid ADRL pseudo instruction
  ARM: 8933/1: replace Sun/Solaris style flag on section directive
  ARM: 8929/1: use APSR_nzcv instead of r15 as mrc operand
  ARM: OMAP2+: drop unnecessary adrl
  ARM: 9029/1: Make iwmmxt.S support Clang's integrated assembler
  crypto: arm - use Kconfig based compiler checks for crypto opcodes
  crypto: arm/ghash-ce - define fpu before fpu registers are referenced
  Linux 5.4.203
  UBUNTU: Upstream stable to v5.4.203

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


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

[Kernel-packages] [Bug 1986999] [NEW] Focal update: v5.4.203 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.4.203 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Focal)
   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/1986999

Title:
  Focal update: v5.4.203 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New

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.4.203 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1986995] Re: Focal update: v5.4.202 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.4.202 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.202 upstream stable release
-from git://git.kernel.org/
+ dm: remove special-casing of bio-based immutable singleton target on NVMe
+ usb: gadget: u_ether: fix regression in setting fixed MAC address
+ tcp: add some entropy in __inet_hash_connect()
+ tcp: use different parts of the port_offset for index and offset
+ tcp: add small random increments to the source port
+ tcp: dynamically allocate the perturb table used by source ports
+ tcp: increase source port perturb table to 2^16
+ tcp: drop the hash_32() part from the index calculation
+ arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer
+ Linux 5.4.201
+ UBUNTU: Upstream stable to v5.4.201
+ random: schedule mix_interrupt_randomness() less often
+ ALSA: hda/via: Fix missing beep setup
+ ALSA: hda/conexant: Fix missing beep setup
+ ALSA: hda/realtek - ALC897 headset MIC no sound
+ ALSA: hda/realtek: Add quirk for Clevo PD70PNT
+ net: openvswitch: fix parsing of nw_proto for IPv6 fragments
+ mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
+ ata: libata: add qc->flags in ata_qc_complete_template tracepoint
+ dm era: commit metadata in postsuspend after worker stops
+ dm mirror log: clear log bits up to BITS_PER_LONG boundary
+ random: quiet urandom warning ratelimit suppression message
+ USB: serial: option: add Telit LE910Cx 0x1250 composition
+ USB: serial: option: add Quectel EM05-G modem
+ USB: serial: option: add Quectel RM500K module support
+ bpf: Fix request_sock leak in sk lookup helpers
+ phy: aquantia: Fix AN when higher speeds than 1G are not advertised
+ bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
+ net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
+ drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
+ erspan: do not assume transport header is always set
+ net/tls: fix tls_sk_proto_close executed repeatedly
+ udmabuf: add back sanity check
+ x86/xen: Remove undefined behavior in setup_features()
+ MIPS: Remove repetitive increase irq_err_count
+ afs: Fix dynamic root getattr
+ ice: ethtool: advertise 1000M speeds properly
+ regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
+ igb: Make DMA faster when CPU is active on the PCIe link
+ virtio_net: fix xdp_rxq_info bug after suspend/resume
+ Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
+ gpio: winbond: Fix error code in winbond_gpio_get()
+ s390/cpumf: Handle events cycles and instructions identical
+ iio: adc: vf610: fix conversion mode sysfs node name
+ xhci: turn off port power in shutdown
+ usb: chipidea: udc: check request status before setting device address
+ iio:chemical:ccs811: rearrange iio trigger get and register
+ iio:accel:bma180: rearrange iio trigger get and register
+ iio:accel:mxc4005: rearrange iio trigger get and register
+ iio: accel: mma8452: ignore the return value of reset operation
+ iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
+ iio: trigger: sysfs: fix use-after-free on remove
+ iio: adc: stm32: fix maximum clock rate for stm32mp15x
+ iio: adc: axp288: Override TS pin bias current for some models
+ xtensa: xtfpga: Fix refcount leak bug in setup
+ xtensa: Fix refcount leak bug in time.c
+ parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
+ powerpc: Enable execve syscall exit tracepoint
+ powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
+ powerpc/powernv: wire up rng during setup_arch
+ ARM: dts: imx6qdl: correct PU regulator ramp delay
+ ARM: exynos: Fix refcount leak in exynos_map_pmu
+ soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
+ ARM: Fix refcount leak in axxia_boot_secondary
+ ARM: cns3xxx: Fix refcount leak in cns3xxx_init
+ modpost: fix section mismatch check for exported init/exit sections
+ random: update comment from copy_to_user() -> copy_to_iter()
+ kbuild: link vmlinux only once for CONFIG_TRIM_UNUSED_KSYMS (2nd attempt)
+ powerpc/pseries: wir

[Kernel-packages] [Bug 1986993] [NEW] Focal update: v5.4.201 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.4.201 upstream stable release
   from git://git.kernel.org/

dm: remove special-casing of bio-based immutable singleton target on NVMe
usb: gadget: u_ether: fix regression in setting fixed MAC address
tcp: add some entropy in __inet_hash_connect()
tcp: use different parts of the port_offset for index and offset
tcp: add small random increments to the source port
tcp: dynamically allocate the perturb table used by source ports
tcp: increase source port perturb table to 2^16
tcp: drop the hash_32() part from the index calculation
arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer
Linux 5.4.201
UBUNTU: Upstream stable to v5.4.201

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

** Affects: linux (Ubuntu Focal)
 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 Focal)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux (Ubuntu Focal)
 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.4.201 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.201 upstream stable release
-from git://git.kernel.org/
+ dm: remove special-casing of bio-based immutable singleton target on NVMe
+ usb: gadget: u_ether: fix regression in setting fixed MAC address
+ tcp: add some entropy in __inet_hash_connect()
+ tcp: use different parts of the port_offset for index and offset
+ tcp: add small random increments to the source port
+ tcp: dynamically allocate the perturb table used by source ports
+ tcp: increase source port perturb table to 2^16
+ tcp: drop the hash_32() part from the index calculation
+ arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer
+ Linux 5.4.201
+ UBUNTU: Upstream stable to v5.4.201

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

Title:
  Focal update: v5.4.201 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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.4.201 upstream stable release
     from git://git.kernel.org/

  dm: remove special-casing of bio-based immutable singleton target on NVMe
  usb: gadget: u_ether: fix regression in setting fixed MAC address
  tcp: add some entropy in __inet_hash_connect()
  tcp: use different parts of the port_offset for index and offset
  tcp: add small random increments to the source port
  tcp: dynamically allocate the perturb table used by source ports
  tcp: increase source port perturb table to 2^16
  tcp: drop the hash_32() part from the index calculation
  arm64

[Kernel-packages] [Bug 1986995] [NEW] Focal update: v5.4.202 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.4.202 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Focal)
 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 Focal)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux (Ubuntu Focal)
 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/1986995

Title:
  Focal update: v5.4.202 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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.4.202 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Wei]

I am pretty sure ``the Sensel Forcepad Device Firmware'' does not
available outside Windows, at least they are not listed on the support
page posted by Alan.

I suggest you can set up a dual boot and install Windows. It is likely
windows will be automatically activated. I guess many firmware updates
might only be available in windows.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  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.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Roland Dreier]

I don't see Linux versions of the touchpad firmware?

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  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.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1956821] Re: System hangs on reboot and shutdown

[Yury Krasouski]

Sounds strange but I have the same issue on 5.14.0-1048-oem

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

Title:
  System hangs on reboot and shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic,
  the system cannot be powered down or rebooted, just hangs
  indefinitely.

  A screenshot with the final screen is shown here:
  https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff

  I can restore the previous behavior (i.e. a correct shutdown) with
  choosing the previous kernel in the grub menu on boot.

  
  Is there anything I can do to provide more information and debug this further?

  My system information:
  Description:  Ubuntu 21.10
  Release:  21.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  petr   1146 F pulseaudio
   /dev/snd/controlC0:  petr   1146 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-07 (62 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20YA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/vgxubuntu-root ro
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 04/07/2021
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMCN21WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G3 ACN
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN:
  dmi.product.family: ThinkBook 13s G3 ACN
  dmi.product.name: 20YA
  dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN
  dmi.product.version: ThinkBook 13s G3 ACN
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1986987] 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 1986987

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

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

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

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

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

Title:
  network interface down/up removes local lookup table from routing
  policy db

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, the IRC guys suggested to file a bug here with 'linux'.

  # cat /proc/version_signature
  Ubuntu 5.15.0-46.49-generic 5.15.39

  Description:Ubuntu 22.04.1 LTS
  Release:22.04

  
  I'm not able to attach the lspci output - but it's happening on various 
hardware flavors (intel i350 nic, mellanox connectx-6, xeon/epyc cpu's, etc) so 
it doesn't look hardware related. If you want to know something hardware 
specific let me know.

  
  $ ip rule show 
  100:from all lookup local
  32766:  from all lookup main
  32767:  from all lookup default

  $ ping localhost -c3
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.044 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.050 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.050 ms

  --- localhost ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2040ms
  rtt min/avg/max/mdev = 0.044/0.048/0.050/0.003 ms

  $ ip link set dev eno1 down

  $ ip link set dev eno1 up

  $ ip rule show 
  32766:  from all lookup main
  32767:  from all lookup default
  > NO LOCAL 

  $ ping localhost -c3
  PING localhost (127.0.0.1) 56(84) bytes of data.

  --- localhost ping statistics ---
  3 packets transmitted, 0 received, 100% packet loss, time 2051ms

  $ ip rule add from all lookup local pref 100

  $ ip rule show 
  100:from all lookup local
  32766:  from all lookup main
  32767:  from all lookup default

  $ ping localhost -c3
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.066 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.054 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.050 ms

  --- localhost ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2024ms
  rtt min/avg/max/mdev = 0.050/0.056/0.066/0.006 ms

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


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

[Kernel-packages] [Bug 1986987] [NEW] network interface down/up removes local lookup table from routing policy db

[Jan Smets]

Public bug reported:

Hi, the IRC guys suggested to file a bug here with 'linux'.

# cat /proc/version_signature
Ubuntu 5.15.0-46.49-generic 5.15.39

Description:Ubuntu 22.04.1 LTS
Release:22.04


I'm not able to attach the lspci output - but it's happening on various 
hardware flavors (intel i350 nic, mellanox connectx-6, xeon/epyc cpu's, etc) so 
it doesn't look hardware related. If you want to know something hardware 
specific let me know.


$ ip rule show 
100:from all lookup local
32766:  from all lookup main
32767:  from all lookup default

$ ping localhost -c3
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.044 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.050 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.050 ms

--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2040ms
rtt min/avg/max/mdev = 0.044/0.048/0.050/0.003 ms

$ ip link set dev eno1 down

$ ip link set dev eno1 up

$ ip rule show 
32766:  from all lookup main
32767:  from all lookup default
> NO LOCAL 

$ ping localhost -c3
PING localhost (127.0.0.1) 56(84) bytes of data.

--- localhost ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2051ms

$ ip rule add from all lookup local pref 100

$ ip rule show 
100:from all lookup local
32766:  from all lookup main
32767:  from all lookup default

$ ping localhost -c3
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.066 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.054 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.050 ms

--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2024ms
rtt min/avg/max/mdev = 0.050/0.056/0.066/0.006 ms

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

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

Title:
  network interface down/up removes local lookup table from routing
  policy db

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, the IRC guys suggested to file a bug here with 'linux'.

  # cat /proc/version_signature
  Ubuntu 5.15.0-46.49-generic 5.15.39

  Description:Ubuntu 22.04.1 LTS
  Release:22.04

  
  I'm not able to attach the lspci output - but it's happening on various 
hardware flavors (intel i350 nic, mellanox connectx-6, xeon/epyc cpu's, etc) so 
it doesn't look hardware related. If you want to know something hardware 
specific let me know.

  
  $ ip rule show 
  100:from all lookup local
  32766:  from all lookup main
  32767:  from all lookup default

  $ ping localhost -c3
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.044 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.050 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.050 ms

  --- localhost ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2040ms
  rtt min/avg/max/mdev = 0.044/0.048/0.050/0.003 ms

  $ ip link set dev eno1 down

  $ ip link set dev eno1 up

  $ ip rule show 
  32766:  from all lookup main
  32767:  from all lookup default
  > NO LOCAL 

  $ ping localhost -c3
  PING localhost (127.0.0.1) 56(84) bytes of data.

  --- localhost ping statistics ---
  3 packets transmitted, 0 received, 100% packet loss, time 2051ms

  $ ip rule add from all lookup local pref 100

  $ ip rule show 
  100:from all lookup local
  32766:  from all lookup main
  32767:  from all lookup default

  $ ping localhost -c3
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.066 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.054 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.050 ms

  --- localhost ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2024ms
  rtt min/avg/max/mdev = 0.050/0.056/0.066/0.006 ms

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


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

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Alan Ferrier]

Lenovo appears to provide all the software and drivers with both Windows
and Linux utilities to install them here:
https://pcsupport.lenovo.com/gb/en/products/laptops-and-
netbooks/thinkpad-x-series-laptops/thinkpad-x1-titanium-
type-20qa-20qb/downloads/driver-list/

You probably have to install them one-at-a-time, which is a bit of a
PITA.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  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.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Rolf Koch]

Confirmed affecting GIGABYTE Z690 AORUS ELITE DDR4 (LGA1700, USB 3.2,
PCIe 5.0) after installing nvidia-driver-515

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  `/var/cache/pbuilder/build/276481/build/grub2-2.06/ob

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Roland Dreier]

Is there any way to perform these updates without Windows? I overwrote
the whole drive when I obtained Ubuntu. I have performed a few BIOS / EC
updates via fwupdmgr, but the system shows as up-to-date now.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  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.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Alan Ferrier]

As an added bonus, I'm fairly sure the driver updates have significantly
improved my battery life, so two thumbs-up.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  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.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1986420] Re: I don't know

[Kleber Sacilotto de Souza]

** Changed in: linux-signed-hwe-5.15 (Ubuntu)
   Status: New => Invalid

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

Title:
  I don't know

Status in linux-signed-hwe-5.15 package in Ubuntu:
  Invalid

Bug description:
  I don't know

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat Aug 13 11:31:29 2022
  InstallationDate: Installed on 2022-01-31 (193 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1986420/+subscriptions


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

[Kernel-packages] [Bug 1986796] Re: amd64-microcode conflicts with linux-firmware

[Matthieu Clemenceau]

** Tags added: fr-2608

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

Title:
  amd64-microcode conflicts with linux-firmware

Status in amd64-microcode package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  Occurs on kubuntu, gnome and xfce versions of kinetic proposed -- most
  recent updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: amd64-microcode 3.20191218.1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Aug 17 08:07:09 2022
  InstallationDate: Installed on 2022-06-10 (67 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220610)
  SourcePackage: amd64-microcode
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1986796/+subscriptions


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

[Kernel-packages] [Bug 1986970] [NEW] PolarFire Icicle Kit: missing USB support

[Heinrich Schuchardt]

Public bug reported:

[Impact]

The 5.19 kernel contains support for the PolarFire Icicle board but the
USB driver is missing.

The following patches are available in Linux v6.0-rc1 and are sufficient
to make USB usable on the PolarFire Icicle board. Please, apply them to
the 5.19 kernel and set CONFIG_USB_MUSB_POLARFIRE_SOC=m.

7a96b6ea90a4 ("usb: musb: Add support for PolarFire SoC's musb controller")
https://lore.kernel.org/r/20220613114642.1615292-2-conor.doo...@microchip.com

21cdd6a0e844 ("usb: musb: mpfs: Fix error codes in probe()")
https://lore.kernel.org/r/YrVmLEc/FOEzNdzj@kili

98ceba755928 ("usb: musb: mpfs: add missing clk_disable_unprepare() in 
mpfs_remove()"
https://lore.kernel.org/all/YrVmLEc%2FFOEzNdzj@kili/

With this change internal USB devices are fully usable. External devices
are supported with the following Jumper settings:

* J17 closed
* J15 open

[Test Plan]

Ensure the correct jumper settings:

* J17 closed
* J15 open

Use the SiFive Unmatched preinstalled image and install the 5.19 kernel.
Try to boot on the Polarfire Icicle board.

* Run lsusb.
* Attach a USB device to J16 (USB port beside SD-card slot)
* Run lsusb again. The new device appears.

[Where problems could occur]

The fix only concerns a board which has been unsupported by Ubuntu yet.

In case of an incorrect fix the board might not boot or otherwise
malfunction.

Best regards

Heinrich

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

** Description changed:

  [Impact]
  
  The 5.19 kernel contains support for the PolarFire Icicle board but the
  USB driver is missing.
  
  The following patches are available in Linux v6.0-rc1 and are sufficient
  to make USB usable on the PolarFire Icicle board. Please, apply them to
- the 5.19 kernel set CONFIG_USB_MUSB_POLARFIRE_SOC=m.
+ the 5.19 kernel and set CONFIG_USB_MUSB_POLARFIRE_SOC=m.
  
  7a96b6ea90a4 ("usb: musb: Add support for PolarFire SoC's musb controller")
  https://lore.kernel.org/r/20220613114642.1615292-2-conor.doo...@microchip.com
  
  21cdd6a0e844 ("usb: musb: mpfs: Fix error codes in probe()")
  https://lore.kernel.org/r/YrVmLEc/FOEzNdzj@kili
  
  98ceba755928 ("usb: musb: mpfs: add missing clk_disable_unprepare() in 
mpfs_remove()"
  https://lore.kernel.org/all/YrVmLEc%2FFOEzNdzj@kili/
  
  With this change internal USB devices are fully usable. External devices
  are supported with the following Jumper settings:
  
  * J17 closed
  * J15 open
  
  [Test Plan]
  
  Ensure the correct jumper settings:
  
  * J17 closed
  * J15 open
  
  Use the SiFive Unmatched preinstalled image and install the 5.19 kernel.
  Try to boot on the Polarfire Icicle board.
  
  * Run lsusb.
  * Attach a USB device to J16 (USB port beside SD-card slot)
  * Run lsusb again. The new device appears.
  
  [Where problems could occur]
  
  The fix only concerns a board which has been unsupported by Ubuntu yet.
  
  In case of an incorrect fix the board might not boot or otherwise
  malfunction.
  
  Best regards
  
  Heinrich

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

Title:
  PolarFire Icicle Kit: missing USB support

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  [Impact]

  The 5.19 kernel contains support for the PolarFire Icicle board but
  the USB driver is missing.

  The following patches are available in Linux v6.0-rc1 and are
  sufficient to make USB usable on the PolarFire Icicle board. Please,
  apply them to the 5.19 kernel and set CONFIG_USB_MUSB_POLARFIRE_SOC=m.

  7a96b6ea90a4 ("usb: musb: Add support for PolarFire SoC's musb controller")
  https://lore.kernel.org/r/20220613114642.1615292-2-conor.doo...@microchip.com

  21cdd6a0e844 ("usb: musb: mpfs: Fix error codes in probe()")
  https://lore.kernel.org/r/YrVmLEc/FOEzNdzj@kili

  98ceba755928 ("usb: musb: mpfs: add missing clk_disable_unprepare() in 
mpfs_remove()"
  https://lore.kernel.org/all/YrVmLEc%2FFOEzNdzj@kili/

  With this change internal USB devices are fully usable. External
  devices are supported with the following Jumper settings:

  * J17 closed
  * J15 open

  [Test Plan]

  Ensure the correct jumper settings:

  * J17 closed
  * J15 open

  Use the SiFive Unmatched preinstalled image and install the 5.19
  kernel. Try to boot on the Polarfire Icicle board.

  * Run lsusb.
  * Attach a USB device to J16 (USB port beside SD-card slot)
  * Run lsusb again. The new device appears.

  [Where problems could occur]

  The fix only concerns a board which has been unsupported by Ubuntu
  yet.

  In case of an incorrect fix the board might not boot or otherwise
  malfunction.

  Best regards

  Heinrich

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


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

[Kernel-packages] [Bug 1981487] Re: kernel BUG/Oops errors from modprobe while the DRBG has not yet initialized (focal/fips-updates)

[Mauricio Faria de Oliveira]

[Focal/FIPS][PATCH v2] UBUNTU: SAUCE: random: fallback to CRNG while DRBG is 
not yet initialized
(code-style change)

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

Title:
  kernel BUG/Oops errors from modprobe while the DRBG has not yet
  initialized (focal/fips-updates)

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

Bug description:
  [Impact]

   * The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
     errors during boot with the FIPS OpenSSL library installed
     (but those don't cause issues), when it runs modprobe with
     request_module() when looking up crypto algorithms/modules.

   * The modprobe command happens to call the OpenSSL library,
     and the FIPS version of OpenSSL calls getrandom(),
     and the FIPS kernel calls the DRBG for that,
     BUT it's _not yet_ initialized that early during boot
     when the kernel can run modprobe via request_module().
     (e.g., IPv6 initialization time.)

   * The issue impacts the kernels in fips-updates only, per:
     "UBUNTU: SAUCE: random: Use Crypto API DRBG for urandom in FIPS mode"
     which exists in Focal, but not in Xenial/Bionic/Jammy.

   * The issue only happens with the crypto algorithms, even
     if they're built-in (i.e., modprobe is not needed).

  [Fix]

   * Fall back to CRNG while the DRBG is not yet initialized.
     (Marcelo Cerri confirmed it's OK per other discussions.)

   * The fix doesn't change the list and details of algorithms
     as in /proc/crypto (e.g., name, driver, module,  priority)
     by the time the DRBG is initialized / initramfs started,
     so even though behavior changes, the net effect doesn't.

   * (Note: it's not possible to just use an initcall level
  earlier than rootfs_initcall() so modprobe isn't there,
  because fips_drbg_init() must run _after_ module_init()
  level so that crypto_rng_reset() works, even though its
  required module is built-in too.

  [Test Steps]

   * Install the kernel and openssl from fips-updates,
     boot with fips=1, check dmesg for BUG/Oops errors:

     $ sudo apt install linux-image-fips libssl1.1 # fips-updates
     $ sudo vim /etc/default/grub # append fips=1 boot option
     $ sudo update-grub && sudo reboot
     $ sudo dmesg | grep BUG:

   * Check/store the /proc/crypto file for comparisons.
     You can boot with break=top as well, to check that
     as early as possible, and copy into /run/initramfs/
     then exit, to get it later in the rootfs.

  [Regression Potential]

   * The fix falls back to the regular CRNG for a while
     in early boot. The CRNG is used permanently in the
     non-FIPS kernels (and in FIPS kernels w/out fips=1),
     so the code path is exercised/tested frequently.

   * Regressions would most likely occur in calls to
     getrandom() before the DRBG is initialized, but
     that currently hits a BUG/Oops anyway.

  [Original Bug Description]

  $ sudo apt install --yes linux-image-fips # fips-updates
  $ sudo vim /etc/default/grub # fips=1
  $ sudo update-grub && sudo reboot

  $ uname -r
  5.4.0-1056-fips

  $ cat /proc/cmdline
  ... fips=1

  No errors with the original/non-FIPS openssl, because it does NOT call
  getrandom():

  $ dmesg | grep -c BUG:
  0

  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.15

  $ strace -e getrandom modprobe --version
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++

  But if you install the FIPS openssl, it calls getrandom(), then
  BUG/Oops happen:

  $ sudo apt install libssl1.1 # updates initramfs

  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.fips.13.1

  $ strace -e getrandom modprobe --version
  getrandom("\xc4\x84\x26\x25\x6f\xd4\xed\x38\xdf\xa9\x67\xee\x15\x1c\xe3\x98", 
16, GRND_NONBLOCK) = 16
  getrandom("\xa1\xd6\x67\x3e\xe4\x90\xb3\x8b\xdf\xe6\x34\x2a\xa7\x50\xbc\x2f", 
16, GRND_NONBLOCK) = 16
  getrandom("\xf1\x3e\xe4\x27\x9d\x47\x8c\x4b\x8a\x39\x8c\xe1\x2e\xee\xfa\x45", 
16, GRND_NONBLOCK) = 16
  getrandom("\xfb\x34\x18\x44\xd8\x23\x4c\x87\x13\x2e\x6b\x03\x79\xa7\x99\xf8", 
16, 0) = 16
  getrandom("\xdd\x83\xa7\x02\x10\x51\x2b\x4f\x21\x6b\xc1\xf1\x0d\xe7\x44\xb7", 
16, 0) = 16
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++

  $ sudo reboot

  $ dmesg | grep -c BUG:
  22

  $ dmesg
  ...
  [1.595759] NET: Registered protocol family 10
  [1.600256] BUG: kernel NULL pointer dereference, address: 0038
  ...
  [1.603829] CPU: 2 PID: 137 Comm: modprobe Not tainted 5.4.0-1056-fips 
#64-Ubuntu
  [1.603829] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
  [1.603829] RIP: 0010:urandom_read+0x268/0x480
  ...

[Kernel-packages] [Bug 1986792] ProcInterrupts.txt

[conie chang]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609668/+files/ProcInterrupts.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] acpidump.txt

[conie chang]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609672/+files/acpidump.txt

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

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

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1918252] Re: WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c]

[tomas muehlhoff]

This below seems to affect the same HW, just re-branded to Intel:

https://patchwork.kernel.org/project/linux-
pci/patch/20210329052339.20882-1-kai.heng.f...@canonical.com/#24107379

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

Title:
  WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is no driver for it [03f0:0a6c].

  using 5.10 kernel.

  $ sudo lspci -nnnv -s 55:00.0
  55:00.0 Wireless controller [0d40]: Device [03f0:0a6c]
Subsystem: Hewlett-Packard Company Device [103c:877f]
Flags: fast devsel
Memory at 6e30 (64-bit, non-prefetchable) [disabled] [size=4K]
Memory at 6e301000 (64-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Secondary PCI Express
Capabilities: [168] Physical Layer 16.0 GT/s 
Capabilities: [18c] Lane Margining at the Receiver 
Capabilities: [19c] Transaction Processing Hints
Capabilities: [228] Latency Tolerance Reporting
Capabilities: [230] L1 PM Substates
Capabilities: [240] Data Link Feature 

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


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

[Kernel-packages] [Bug 1986792] Re: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

[conie chang]

yes! I update the logs. Please review it.

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

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] ProcModules.txt

[conie chang]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609669/+files/ProcModules.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] UdevDb.txt

[conie chang]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1986792/+attachment/5609670/+files/UdevDb.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] WifiSyslog.txt

[conie chang]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609671/+files/WifiSyslog.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] Lspci-vt.txt

[conie chang]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609663/+files/Lspci-vt.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] Lsusb-v.txt

[conie chang]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609665/+files/Lsusb-v.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] ProcCpuinfoMinimal.txt

[conie chang]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609667/+files/ProcCpuinfoMinimal.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] Lsusb-t.txt

[conie chang]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609664/+files/Lsusb-t.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] ProcCpuinfo.txt

[conie chang]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609666/+files/ProcCpuinfo.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986792] Re: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

[conie chang]

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
+  crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-08-18 (0 days ago)
+ InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
+  Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
+  Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Lenovo ThinkEdge SE450
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 astdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
+ ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-46-generic N/A
+  linux-backports-modules-5.15.0-46-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.4
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  jammy uec-images
+ Uname: Linux 5.15.0-46-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 08/08/2022
+ dmi.bios.release: 1.23
+ dmi.bios.vendor: Lenovo
+ dmi.bios.version: CME105F-1.23
+ dmi.board.asset.tag: none
+ dmi.board.name: 7D8TCTO1WW
+ dmi.board.vendor: Lenovo
+ dmi.board.version: 05
+ dmi.chassis.asset.tag: none
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: Lenovo
+ dmi.chassis.version: none
+ dmi.ec.firmware.release: 1.40
+ dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
+ dmi.product.family: ThinkSystem
+ dmi.product.name: ThinkEdge SE450
+ dmi.product.sku: 7D8TCTO1WW
+ dmi.product.version: 05
+ dmi.sys.vendor: Lenovo

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1986792/+attachment/5609661/+files/CurrentDmesg.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 0

[Kernel-packages] [Bug 1986792] Lspci.txt

[conie chang]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1986792/+attachment/5609662/+files/Lspci.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/1986792

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
  where
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Aug 18 14:57 seq
   crw-rw+ 1 root audio 116, 33 Aug 18 14:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 1986965] Re: 12th gen intel PC can't boot with kernel 5.15.0-46

[cm-t 🦄🏂🌈🎵]

** Attachment added: "4-stuck-here-must-reboot.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986965/+attachment/5609660/+files/4-stuck-here-must-reboot.png

** Description changed:

  Hi,
  
  Ubuntu 22.04 LTS here.
  
  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.
  
  After installing, I never was able to boot on it.
  
  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
- - a few line of log appears (same on working boot)
- - then default boot screen "MSI + ubuntu logo" appears, but "long time"
- - then  [ OK ] linux boot log  got displayed and stay on same line for few 
moment too
- - then black screen with top left corner with the white blinky cursor
+ - [see 1st attached PNG] a few line of log appears (same on working boot)
+ - [see 2nd attached PNG]then default boot screen "MSI + ubuntu logo" appears, 
but "long time"
+ - [see 3rd attached PNG]then  [ OK ] linux boot log  got displayed and stay 
on same line for few moment too. I guess that's the attached image that show 
the most important stuff.
+ - [see 4th attached PNG]then black screen with top left corner with the white 
blinky cursor
  - CTRL+ALT+DEL to reboot
  
  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.
  
  Do you need more info/logs ?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 18 16:18:56 2022
  InstallationDate: Installed on 2022-04-29 (111 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
  
   enp4s0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

** Description changed:

  Hi,
  
  Ubuntu 22.04 LTS here.
  
  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.
  
  After installing, I never was able to boot on it.
  
  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
  - [see 1st attached PNG] a few line of log appears (same on working boot)
- - [see 2nd attached PNG]then default boot screen "MSI + ubuntu logo" appears, 
but "long time"
- - [see 3rd attached PNG]then  [ OK ] linux boot log  got displayed and stay 
on same line for few moment too. I guess that's the attached image that show 
the most important stuff.
- - [see 4th attached PNG]then black screen with top left corner with the white 
blinky cursor
+ - [see 2nd attached PNG] then default boot screen "MSI + ubuntu logo" 
appears, but "long time"
+ - [see 3rd attached PNG] then  [ OK ] linux boot log  got displayed and stay 
on same line for few moment too. I guess that's the

[Kernel-packages] [Bug 1986965] Re: 12th gen intel PC can't boot with kernel 5.15.0-46

[cm-t 🦄🏂🌈🎵]

** Attachment added: "3-logs-not-normal.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986965/+attachment/5609659/+files/3-logs-not-normal.png

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

Title:
  12th gen intel PC can't boot with kernel 5.15.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 22.04 LTS here.

  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.

  After installing, I never was able to boot on it.

  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
  - [see 1st attached PNG] a few line of log appears (same on working boot)
  - [see 2nd attached PNG] then default boot screen "MSI + ubuntu logo" 
appears, but "long time"
  - [see 3rd attached PNG] then  [ OK ] linux boot log  got displayed and stay 
on same line for few moment too. I guess that's the attached image that show 
the most important stuff.
  - [see 4th attached PNG] then black screen with top left corner with the 
white blinky cursor
  - CTRL+ALT+DEL to reboot

  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.

  Do you need more info/logs ?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 18 16:18:56 2022
  InstallationDate: Installed on 2022-04-29 (111 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.

   enp4s0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 1986965] Re: 12th gen intel PC can't boot with kernel 5.15.0-46

[cm-t 🦄🏂🌈🎵]

** Attachment added: "2-loading-screen.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986965/+attachment/5609658/+files/2-loading-screen.png

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

Title:
  12th gen intel PC can't boot with kernel 5.15.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 22.04 LTS here.

  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.

  After installing, I never was able to boot on it.

  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
  - [see 1st attached PNG] a few line of log appears (same on working boot)
  - [see 2nd attached PNG] then default boot screen "MSI + ubuntu logo" 
appears, but "long time"
  - [see 3rd attached PNG] then  [ OK ] linux boot log  got displayed and stay 
on same line for few moment too. I guess that's the attached image that show 
the most important stuff.
  - [see 4th attached PNG] then black screen with top left corner with the 
white blinky cursor
  - CTRL+ALT+DEL to reboot

  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.

  Do you need more info/logs ?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 18 16:18:56 2022
  InstallationDate: Installed on 2022-04-29 (111 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.

   enp4s0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 1986965] Re: 12th gen intel PC can't boot with kernel 5.15.0-46

[cm-t 🦄🏂🌈🎵]

** Attachment added: "1-log_usually_displayed.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986965/+attachment/5609657/+files/1-log_usually_displayed.png

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

Title:
  12th gen intel PC can't boot with kernel 5.15.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 22.04 LTS here.

  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.

  After installing, I never was able to boot on it.

  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
  - [see 1st attached PNG] a few line of log appears (same on working boot)
  - [see 2nd attached PNG] then default boot screen "MSI + ubuntu logo" 
appears, but "long time"
  - [see 3rd attached PNG] then  [ OK ] linux boot log  got displayed and stay 
on same line for few moment too. I guess that's the attached image that show 
the most important stuff.
  - [see 4th attached PNG] then black screen with top left corner with the 
white blinky cursor
  - CTRL+ALT+DEL to reboot

  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.

  Do you need more info/logs ?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 18 16:18:56 2022
  InstallationDate: Installed on 2022-04-29 (111 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.

   enp4s0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 1986965] Re: 12th gen intel PC can't boot with kernel 5.15.0-46

[cm-t 🦄🏂🌈🎵]

** Description changed:

  Hi,
  
  Ubuntu 22.04 LTS here.
  
  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.
  
  After installing, I never was able to boot on it.
  
  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
- - instead of displaying the default boot screen "MSI + ubuntu logo" it just 
appears 0.1sec
- - then  [ OK ] linux boot log  got displayed and stay on same line for a 
minutes
+ - a few line of log appears (same on working boot)
+ - then default boot screen "MSI + ubuntu logo" appears, but "long time"
+ - then  [ OK ] linux boot log  got displayed and stay on same line for few 
moment too
  - then black screen with top left corner with the white blinky cursor
  - CTRL+ALT+DEL to reboot
  
- 
  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.
- 
  
  Do you need more info/logs ?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 18 16:18:56 2022
  InstallationDate: Installed on 2022-04-29 (111 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
-  lono wireless extensions.
-  
-  enp4s0no wireless extensions.
+  lono wireless extensions.
+ 
+  enp4s0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-41-generic N/A
-  linux-backports-modules-5.15.0-41-generic  N/A
-  linux-firmware 20220329.git681281e4-0ubuntu3.4
+  linux-restricted-modules-5.15.0-41-generic N/A
+  linux-backports-modules-5.15.0-41-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

Title:
  12th gen intel PC can't boot with kernel 5.15.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 22.04 LTS here.

  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.

  After installing, I never was able to boot on it.

  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
  - a few line of log appears (same on working boot)
  - then default boot screen "MSI + ubuntu logo" appears, but "long time"
  - then  [ OK ] linux boot log  got displayed and stay on same line for few 
moment too
  - then black screen with top left corner with the white blinky cursor
  - CTRL+ALT+DEL to reboot

  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every 

[Kernel-packages] [Bug 1986964] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module failed to build

[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 bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1986964

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: sdhci_pci cqhci sdhci r8169 i2c_piix4 realtek wmi 
i2c_scmi
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DKMSKernelVersion: 5.17.0-1015-oem
  Date: Thu Aug 18 16:08:37 2022
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26:
 error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2022-01-30 (200 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu8
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: Upgraded to jammy on 2022-08-18 (0 days ago)

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


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

[Kernel-packages] [Bug 1986965] 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/1986965

Title:
  12th gen intel PC can't boot with kernel 5.15.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 22.04 LTS here.

  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.

  After installing, I never was able to boot on it.

  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
  - a few line of log appears (same on working boot)
  - then default boot screen "MSI + ubuntu logo" appears, but "long time"
  - then  [ OK ] linux boot log  got displayed and stay on same line for few 
moment too
  - then black screen with top left corner with the white blinky cursor
  - CTRL+ALT+DEL to reboot

  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.

  Do you need more info/logs ?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 18 16:18:56 2022
  InstallationDate: Installed on 2022-04-29 (111 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.

   enp4s0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 1986964] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module failed to build

[Giorgio Mattia]

Public bug reported:

bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
failed to build

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
NonfreeKernelModules: sdhci_pci cqhci sdhci r8169 i2c_piix4 realtek wmi i2c_scmi
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
DKMSKernelVersion: 5.17.0-1015-oem
Date: Thu Aug 18 16:08:37 2022
DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26:
 error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? 
[-Werror=implicit-function-declaration]
InstallationDate: Installed on 2022-01-30 (200 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageVersion: 6.30.223.271+bdcom-0ubuntu8
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
UpgradeStatus: Upgraded to jammy on 2022-08-18 (0 days ago)

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


** Tags: amd64 apport-package jammy

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: sdhci_pci cqhci sdhci r8169 i2c_piix4 realtek wmi 
i2c_scmi
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DKMSKernelVersion: 5.17.0-1015-oem
  Date: Thu Aug 18 16:08:37 2022
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26:
 error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2022-01-30 (200 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu8
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: Upgraded to jammy on 2022-08-18 (0 days ago)

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


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

[Kernel-packages] [Bug 1986965] [NEW] 12th gen intel PC can't boot with kernel 5.15.0-46

[cm-t 🦄🏂🌈🎵]

Public bug reported:

Hi,

Ubuntu 22.04 LTS here.

I don't know if it is a bug directly linked to linux kernel but:
Before my July holidays, PC booted fine, in less than 3sec, when I came back in 
august, there were some updates to install, including new kernel 5.15.0-46.

After installing, I never was able to boot on it.

- PC boot
- GRUB will load
- default select lastest kernel (5.15.0-46)
- a few line of log appears (same on working boot)
- then default boot screen "MSI + ubuntu logo" appears, but "long time"
- then  [ OK ] linux boot log  got displayed and stay on same line for few 
moment too
- then black screen with top left corner with the white blinky cursor
- CTRL+ALT+DEL to reboot

To use my PC I have to choose additional ubuntu options and select 5.15.0-41 in 
grub.
Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.

Do you need more info/logs ?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-41-generic 5.15.0-41.44
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 18 16:18:56 2022
InstallationDate: Installed on 2022-04-29 (111 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
IwConfig:
 lono wireless extensions.

 enp4s0no wireless extensions.
MachineType: Micro-Star International Co., Ltd. MS-7D25
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-41-generic N/A
 linux-backports-modules-5.15.0-41-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.4
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2021
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.00
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A DDR4(MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D25
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug 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/1986965

Title:
  12th gen intel PC can't boot with kernel 5.15.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 22.04 LTS here.

  I don't know if it is a bug directly linked to linux kernel but:
  Before my July holidays, PC booted fine, in less than 3sec, when I came back 
in august, there were some updates to install, including new kernel 5.15.0-46.

  After installing, I never was able to boot on it.

  - PC boot
  - GRUB will load
  - default select lastest kernel (5.15.0-46)
  - a few line of log appears (same on working boot)
  - then default boot screen "MSI + ubuntu logo" appears, but "long time"
  - then  [ OK ] linux boot log  got displayed and stay on same line for few 
moment too
  - then black screen with top left corner with the white blinky cursor
  - CTRL+ALT+DEL to reboot

  To use my PC I have to choose additional ubuntu options and select 5.15.0-41 
in grub.
  Using this option allow to boot normaly, and got livepatch applying an update 
at every reboot (so if it apply the -46, it works during live patch, but sadly 
not on hard reboot.

  Do you need more info/logs ?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 18 16:18:56 2022
  InstallationDate: 

[Kernel-packages] [Bug 1981487] Re: kernel BUG/Oops errors from modprobe while the DRBG has not yet initialized (focal/fips-updates)

[Mauricio Faria de Oliveira]

The patchset in comment #2
  [Focal/FIPS][PATCH 0/4] Fix kernel BUG/Oops errors from modprobe while the 
DRBG has not yet initialized (focal/fips-updates)

is now superseded by patch:
  [Focal/FIPS][PATCH] UBUNTU: SAUCE: random: fallback to CRNG while DRBG is not 
yet initialized

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

Title:
  kernel BUG/Oops errors from modprobe while the DRBG has not yet
  initialized (focal/fips-updates)

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

Bug description:
  [Impact]

   * The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
     errors during boot with the FIPS OpenSSL library installed
     (but those don't cause issues), when it runs modprobe with
     request_module() when looking up crypto algorithms/modules.

   * The modprobe command happens to call the OpenSSL library,
     and the FIPS version of OpenSSL calls getrandom(),
     and the FIPS kernel calls the DRBG for that,
     BUT it's _not yet_ initialized that early during boot
     when the kernel can run modprobe via request_module().
     (e.g., IPv6 initialization time.)

   * The issue impacts the kernels in fips-updates only, per:
     "UBUNTU: SAUCE: random: Use Crypto API DRBG for urandom in FIPS mode"
     which exists in Focal, but not in Xenial/Bionic/Jammy.

   * The issue only happens with the crypto algorithms, even
     if they're built-in (i.e., modprobe is not needed).

  [Fix]

   * Fall back to CRNG while the DRBG is not yet initialized.
     (Marcelo Cerri confirmed it's OK per other discussions.)

   * The fix doesn't change the list and details of algorithms
     as in /proc/crypto (e.g., name, driver, module,  priority)
     by the time the DRBG is initialized / initramfs started,
     so even though behavior changes, the net effect doesn't.

   * (Note: it's not possible to just use an initcall level
  earlier than rootfs_initcall() so modprobe isn't there,
  because fips_drbg_init() must run _after_ module_init()
  level so that crypto_rng_reset() works, even though its
  required module is built-in too.

  [Test Steps]

   * Install the kernel and openssl from fips-updates,
     boot with fips=1, check dmesg for BUG/Oops errors:

     $ sudo apt install linux-image-fips libssl1.1 # fips-updates
     $ sudo vim /etc/default/grub # append fips=1 boot option
     $ sudo update-grub && sudo reboot
     $ sudo dmesg | grep BUG:

   * Check/store the /proc/crypto file for comparisons.
     You can boot with break=top as well, to check that
     as early as possible, and copy into /run/initramfs/
     then exit, to get it later in the rootfs.

  [Regression Potential]

   * The fix falls back to the regular CRNG for a while
     in early boot. The CRNG is used permanently in the
     non-FIPS kernels (and in FIPS kernels w/out fips=1),
     so the code path is exercised/tested frequently.

   * Regressions would most likely occur in calls to
     getrandom() before the DRBG is initialized, but
     that currently hits a BUG/Oops anyway.

  [Original Bug Description]

  $ sudo apt install --yes linux-image-fips # fips-updates
  $ sudo vim /etc/default/grub # fips=1
  $ sudo update-grub && sudo reboot

  $ uname -r
  5.4.0-1056-fips

  $ cat /proc/cmdline
  ... fips=1

  No errors with the original/non-FIPS openssl, because it does NOT call
  getrandom():

  $ dmesg | grep -c BUG:
  0

  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.15

  $ strace -e getrandom modprobe --version
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++

  But if you install the FIPS openssl, it calls getrandom(), then
  BUG/Oops happen:

  $ sudo apt install libssl1.1 # updates initramfs

  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.fips.13.1

  $ strace -e getrandom modprobe --version
  getrandom("\xc4\x84\x26\x25\x6f\xd4\xed\x38\xdf\xa9\x67\xee\x15\x1c\xe3\x98", 
16, GRND_NONBLOCK) = 16
  getrandom("\xa1\xd6\x67\x3e\xe4\x90\xb3\x8b\xdf\xe6\x34\x2a\xa7\x50\xbc\x2f", 
16, GRND_NONBLOCK) = 16
  getrandom("\xf1\x3e\xe4\x27\x9d\x47\x8c\x4b\x8a\x39\x8c\xe1\x2e\xee\xfa\x45", 
16, GRND_NONBLOCK) = 16
  getrandom("\xfb\x34\x18\x44\xd8\x23\x4c\x87\x13\x2e\x6b\x03\x79\xa7\x99\xf8", 
16, 0) = 16
  getrandom("\xdd\x83\xa7\x02\x10\x51\x2b\x4f\x21\x6b\xc1\xf1\x0d\xe7\x44\xb7", 
16, 0) = 16
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++

  $ sudo reboot

  $ dmesg | grep -c BUG:
  22

  $ dmesg
  ...
  [1.595759] NET: Registered protocol family 10
  [1.600256] BUG: kernel NULL pointer dereference, address: 0038
  ...
  [1.603829] CPU: 2 PID: 137 Comm: modprobe Not tainted 5.4.0-1056-fips 
#64-Ubuntu
  

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Alan Ferrier]

I can confirm that after installing ALL Windows 10 updates, recommended
and optional AND all updates using the bundled "Lenovo Commercial
Vantage" application (which also updated the BIOS) it does indeed appear
that this issue is resolved.

Thanks to Wei and Gamithra for their suggestions and assistance.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  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.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1981487] Re: kernel BUG/Oops errors from modprobe while the DRBG has not yet initialized (focal/fips-updates)

[Mauricio Faria de Oliveira]

** Description changed:

  [Impact]
  
   * The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
     errors during boot with the FIPS OpenSSL library installed
     (but those don't cause issues), when it runs modprobe with
     request_module() when looking up crypto algorithms/modules.
  
   * The modprobe command happens to call the OpenSSL library,
     and the FIPS version of OpenSSL calls getrandom(),
     and the FIPS kernel calls the DRBG for that,
     BUT it's _not yet_ initialized that early during boot
     when the kernel can run modprobe via request_module().
     (e.g., IPv6 initialization time.)
  
   * The issue impacts the kernels in fips-updates only, per:
     "UBUNTU: SAUCE: random: Use Crypto API DRBG for urandom in FIPS mode"
     which exists in Focal, but not in Xenial/Bionic/Jammy.
  
+  * The issue only happens with the crypto algorithms, even
+    if they're built-in (i.e., modprobe is not needed).
+ 
+ 
  [Fix]
  
-  * The issue only happens with the crypto algorithms, even
-    if they're built-in (i.e., modprobe is not needed), so
-    the fix approach is to set CRYPTO_NOLOAD while the DRBG
-    isn't yet initialized; this skips request_module() calls.
+  * Fall back to CRNG while the DRBG is not yet initialized.
+    (Marcelo Cerri confirmed it's OK per other discussions.)
  
   * The fix doesn't change the list and details of algorithms
     as in /proc/crypto (e.g., name, driver, module,  priority)
     by the time the DRBG is initialized / initramfs started,
     so even though behavior changes, the net effect doesn't.
  
   * (Note: it's not possible to just use an initcall level
  earlier than rootfs_initcall() so modprobe isn't there,
  because fips_drbg_init() must run _after_ module_init()
  level so that crypto_rng_reset() works, even though its
- required module is built-in too.
+ required module is built-in too.
  
  [Test Steps]
  
   * Install the kernel and openssl from fips-updates,
     boot with fips=1, check dmesg for BUG/Oops errors:
  
     $ sudo apt install linux-image-fips libssl1.1 # fips-updates
     $ sudo vim /etc/default/grub # append fips=1 boot option
     $ sudo update-grub && sudo reboot
     $ sudo dmesg | grep BUG:
  
   * Check/store the /proc/crypto file for comparisons.
     You can boot with break=top as well, to check that
     as early as possible, and copy into /run/initramfs/
     then exit, to get it later in the rootfs.
  
  [Regression Potential]
  
-  * The fix skips calls to request_module()/modprobe on
-    early boot until the FIPS DRBG is initialized (only
-    in the crypto subsystem) thus potential regressions
-    would show up as early boot kernel errors messages
-    or crypto algorithms not up after system booted.
-    (These should have no impact, theoretically, as it
- currently doesn't run anyway, because of BUG/Oops.)
- 
-  * The fix also adds a panic() call in request_module()
-    if other/non-crypto kernel code attempts to load a
-    module while the DRBG isn't ready yet (so we catch
-    that earlier). It's possible to use a boot option
-    to disable that behavior, but it disables FIPS mode
-    for strictness.
+  * The fix falls back to the regular CRNG for a while
+    in early boot. The CRNG is used permanently in the
+    non-FIPS kernels (and in FIPS kernels w/out fips=1),
+    so the code path is exercised/tested frequently.
+    
+  * Regressions would most likely occur in calls to
+    getrandom() before the DRBG is initialized, but
+    that currently hits a BUG/Oops anyway.
  
  [Original Bug Description]
  
  $ sudo apt install --yes linux-image-fips # fips-updates
  $ sudo vim /etc/default/grub # fips=1
  $ sudo update-grub && sudo reboot
  
  $ uname -r
  5.4.0-1056-fips
  
  $ cat /proc/cmdline
  ... fips=1
  
  No errors with the original/non-FIPS openssl, because it does NOT call
  getrandom():
  
  $ dmesg | grep -c BUG:
  0
  
  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.15
  
  $ strace -e getrandom modprobe --version
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++
  
  But if you install the FIPS openssl, it calls getrandom(), then BUG/Oops
  happen:
  
  $ sudo apt install libssl1.1 # updates initramfs
  
  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.fips.13.1
  
  $ strace -e getrandom modprobe --version
  getrandom("\xc4\x84\x26\x25\x6f\xd4\xed\x38\xdf\xa9\x67\xee\x15\x1c\xe3\x98", 
16, GRND_NONBLOCK) = 16
  getrandom("\xa1\xd6\x67\x3e\xe4\x90\xb3\x8b\xdf\xe6\x34\x2a\xa7\x50\xbc\x2f", 
16, GRND_NONBLOCK) = 16
  getrandom("\xf1\x3e\xe4\x27\x9d\x47\x8c\x4b\x8a\x39\x8c\xe1\x2e\xee\xfa\x45", 
16, GRND_NONBLOCK) = 16
  getrandom("\xfb\x34\x18\x44\xd8\x23\x4c\x87\x13\x2e\x6b\x03\x79\xa7\x99\xf8", 
16, 0) = 16
  getrandom("\xdd\x83\xa7\x02\x10\x51\x2b\x4f\x21\x6b\xc1\xf1\x0d\xe7\x44\xb7", 
16, 0) = 16
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++
 

[Kernel-packages] [Bug 1985901] Re: kernel hang when connecting monitor

[Timo Aaltonen]

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

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

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

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

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

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  New
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L1

[Kernel-packages] [Bug 1095539] Re: Ubuntu 12.04 latest update caused machine to crash

[Lina Marine]

Never allow the update immediately it rolled out, because sometime is
cause issues and the makers roll it back, that is why we are called to
avoid switching on the auto update feature.
https://www.gamingzaming.com/best-power-supply-for-rtx-2060/ never do
that in the future. Always update the system after 5 to 10 hours.

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

Title:
  Ubuntu 12.04 latest update caused machine to crash

Status in Linux:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello All,

  [Ubuntu 12.04 LTS] Earlier this afternoon I allowed the automatic update to 
run and restarted the computer. After restarting the system presents the 
following error message:
  [ 6.668278] 2:3:4: cannot set freq 48000 to ep 0x86

  As a result there is only the text based logon screen available which
  appears to work correctly. In this I have executed the "sudo apt-get
  update" command however this appears to cycle through a number of
  files but it has not resolved my problem at all.

  Any help to recover the system will be appreciated as (always) I have
  some important work in Blender, Salome and others that I have been
  bashing my head against a brick wall for a couple of months and need
  to continue working with for Uni.

  Best regards
  J

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


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

[Kernel-packages] [Bug 1161528] Re: unable to install linux-image, which is required by update-manager

[Lina Marine]

Does your issue is resolved or still you are facing the same.. This bug
really reduce the visibility on images on multiple websites. I have open
this one https://getmodz.com/uc-mini-mod-apk/ but the images doesn't
appear on it, what should I do now???

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

Title:
  unable to install linux-image, which is required by update-manager

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  update-manager fails and instructs me to run apt-get install -f. When
  doing so, I get:

  sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following extra packages will be installed:
linux-image-3.8.0-15-generic
  Suggested packages:
fdutils linux-doc-3.8.0 linux-source-3.8.0 linux-tools
  The following NEW packages will be installed:
linux-image-3.8.0-15-generic
  0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded.
  14 not fully installed or removed.
  Need to get 0 B/12,5 MB of archives.
  After this operation, 33,8 MB of additional disk space will be used.
  Do you want to continue [Y/n]? 
  Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 44,  chunk 3.
  Use of uninitialized value in -e at /usr/share/perl5/Debconf/DbDriver/File.pm 
line 46,  chunk 3.
  Use of uninitialized value in pattern match (m//) at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 47,  chunk 3.
  Use of uninitialized value $directory in -d at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 48,  chunk 3.
  Use of uninitialized value $directory in concatenation (.) or string at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 49,  chunk 3.
  debconf: DbDriver "config": mkdir :No such file or directory
  (Reading database ... 656388 files and directories currently installed.)
  Unpacking linux-image-3.8.0-15-generic (from 
.../linux-image-3.8.0-15-generic_3.8.0-15.25_amd64.deb) ...
  Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 44,  chunk 3.
  Use of uninitialized value in -e at /usr/share/perl5/Debconf/DbDriver/File.pm 
line 46,  chunk 3.
  Use of uninitialized value in pattern match (m//) at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 47,  chunk 3.
  Use of uninitialized value $directory in -d at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 48,  chunk 3.
  Use of uninitialized value $directory in concatenation (.) or string at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 49,  chunk 3.
  debconf: DbDriver "config": mkdir :No such file or directory
  dpkg: error processing 
/var/cache/apt/archives/linux-image-3.8.0-15-generic_3.8.0-15.25_amd64.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Examining 
/etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.8.0-15-generic 
/boot/vmlinuz-3.8.0-15-generic
  run-parts: executing /etc/kernel/postrm.d/zz-extlinux 3.8.0-15-generic 
/boot/vmlinuz-3.8.0-15-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.8.0-15-generic 
/boot/vmlinuz-3.8.0-15-generic
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-3.8.0-15-generic_3.8.0-15.25_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-15-generic (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giorgos1942 F pulseaudio
   /dev/snd/controlC0:  giorgos1942 F pulseaudio
  CRDA:
   country GR:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Date: Thu Mar 28 19:36:18 2013
  HibernationDevice: RESUME=UUID=f0c659d3-c27f-42dc-b115-9ee61c296254
  InstallationDate: Installed on 2011-11-01 (513 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: TOSHIBA Satellite L40
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic 
root=UUID=c06adce9-5953-41a7-b07f-5d32b03f35b5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-13-generic N/A
   linux-backports-modules-3.8.0-13-generic  N/A
   linux-firmware1.104
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-03-21 (6 days ago)
  dmi.bios.date: 09/19/

[Kernel-packages] [Bug 1970065] Re: System not going to be completly powered off

[Josef Cacek]

I had the issue on my Thinkpad T460p running Ubuntu 22.04. It was surely
present during May. It got fixed with some system update later (June or
July). The shutdown works properly on the machine now.

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

Title:
  System not going to be completly powered off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When i shutdown (Apr 23 23:15), it seems everything powered of except the 
keyboard lights. Then, i try to power on again, but, nothing happened because 
the notebook are still powered on. So, it's never powered off correctly?
  Now i force power off (Apr 23 23:20). After Start, the logs look like this:

  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Create System 
Users.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: swapfile.swap: 
Deactivated successfully.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Deactivated swap 
/swapfile.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Unmount 
All Filesystems.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: 
systemd-remount-fs.service: Deactivated successfully.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Remount Root 
and Kernel File Systems.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System 
Shutdown.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Late 
Shutdown Services.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: 
systemd-poweroff.service: Deactivated successfully.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Finished System Power 
Off.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System 
Power Off.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Shutting down.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Syncing 
filesystems and block devices.
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Sending 
SIGTERM to remaining processes...
  Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-journald[258]: Journal 
stopped
  -- Boot 286bc7f0640748e9996bbc70b090eb57 --
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: microcode: microcode 
updated early to revision 0xea, date = 2021-01-25
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Linux version 
5.15.0-25-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld 
(GNU Binutils for Ubuntu) 2.38) #25-Ubuntu SMP Wed Mar 30 >
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=945f3621-37dd-40d0-be8d-295ac422c82f ro quiet splash vt.handoff=7
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: KERNEL supported cpus:
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel:   Intel GenuineIntel
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel:   AMD AuthenticAMD
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel:   Hygon HygonGenuine
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel:   Centaur CentaurHauls
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel:   zhaoxin   Shanghai
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE 
feature 0x001: 'x87 floating point registers'
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE 
feature 0x002: 'SSE registers'
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE 
feature 0x004: 'AVX registers'
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE 
feature 0x008: 'MPX bounds registers'
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE 
feature 0x010: 'MPX CSR'
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[2]:  
576, xstate_sizes[2]:  256
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[3]:  
832, xstate_sizes[3]:   64
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[4]:  
896, xstate_sizes[4]:   64
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Enabled xstate 
features 0x1f, context size is 960 bytes, using 'compacted' format.
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: signal: max sigframe size: 
2032
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-provided physical RAM 
map:
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 
0x-0x00057fff] usable
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 
0x00058000-0x00058fff] reserved
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 
0x00059000-0x0009cfff] usable
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 
0x0009d000-0x000f] reserved
  Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 
0x0010-0xc3eecfff] usable

[Kernel-packages] [Bug 1970066] Re: (Encrypted) ZFS breaks 22.04 installation

[Rufus Filigrane]

I have a related error after a fresh install of xubuntu 22.04.1 with zfs
+ encryption:

After doing a first "apt update" followed by an "apt install" of a
package, apt and the whole X session crash and apt is broken from then
on.

Steps to reproduce:

1. Install (x)ubuntu 22.04.1 with zfs + encryption and boot installed system 
for the first time
2. apt update
3. apt install 
→  apt and x session crash

It seems that the apt install triggers systemd to unmount every zfs
mount because systemd mistakenly thinks the rpool key is not loaded. It
fails unmounting /var/lib or / but succeeds with /var/lib/apt,
/var/lib/dpkg. This causes apt to not work anymore.

I observed the following:

• Somehow after the first boot of the freshly installed system, the service 
unit /run/systemd/generator/zfs-load-key-rpool.service is not generated by 
zfs-mount-generator
• Because this unit must be available and active, this seems to cause systemd 
to think that the key for the rpool is not loaded → systemd starts unmounting 
all zfs mounts after some trigger

Workaround: Reboot immediately after the first boot → service unit gets
generated and started correctly.

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

Title:
  (Encrypted) ZFS breaks 22.04 installation

Status in snapd package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed

Bug description:
  On a freshly installed 22.04.0 amd64 Desktop with (encrypted) ZFS, removing 
the Firefox snap breaks:
  * the current gnome-shell session - it returns to gdm3 login prompt
  * snapd - all snaps are marked 'broken'
  * dpkg - dpkg status database is lost

  Reproducible on dedicated hardware and VMs. Not reproducible on a
  default (/ on ext4) installation.

  Video showing the whole process on a freshly installed system:
  
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583102/+files/1970066.webm

  journalctl -b output:
  
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583100/+files/1970066_journal.txt

  /proc/self/mountinfo:
  
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583101/+files/1970066_mountinfo.txt

  Installation procedure: 
  - Minimal installation
  - Tick 'download updates'
  - Tick 'install third party software'
  - Erase disk and use ZFS + encrypt
  - Require password to log in

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


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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Stefan Bader]

** Patch added: "Updated proposal debdiff (version adjusted to ubuntu0.22.04.1)"
   
https://bugs.launchpad.net/ubuntu/jammy/+source/lttng-modules/+bug/1986921/+attachment/5609564/+files/jammy-proposed.debdiff

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  Impact: The kernel upstream changed in v5.18 and dropped tracepoints
  for random. This change was backported to 5.15/jammy in upstream
  stable 5.15.44. With that the build of lttng-modules-dkms fails.

  Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
  be aware of the missing probe module.

  Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and
  -47 or later. Currently -47 and later will fail. With the change both
  should complete.

  Regression Potential: This changes whether lttng-probe-random.ko is
  available or not (if it is available the code is unchanged). User-
  space might be affected if this module is always expected.

  ---

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

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


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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Stefan Bader]

I did run above changes for 5.15.0-46 and -47. Both work and -46 also
installs lttng-probe-random.

** Description changed:

+ SRU Justification:
+ 
+ Impact: The kernel upstream changed in v5.18 and dropped tracepoints for
+ random. This change was backported to 5.15/jammy in upstream stable
+ 5.15.44. With that the build of lttng-modules-dkms fails.
+ 
+ Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
+ be aware of the missing probe module.
+ 
+ Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47
+ or later. Currently -47 and later will fail. With the change both should
+ complete.
+ 
+ Regression Potential: This changes whether lttng-probe-random.ko is
+ available or not (if it is available the code is unchanged). User-space
+ might be affected if this module is always expected.
+ 
+ ---
+ 
  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by
  the dep8 tests of the tested source or the kernel has yet to be
  determined.
  
  Testing failed on:
- amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
- arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
- ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
- s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz
+ amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
+ arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
+ ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
+ s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  Impact: The kernel upstream changed in v5.18 and dropped tracepoints
  for random. This change was backported to 5.15/jammy in upstream
  stable 5.15.44. With that the build of lttng-modules-dkms fails.

  Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
  be aware of the missing probe module.

  Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and
  -47 or later. Currently -47 and later will fail. With the change both
  should complete.

  Regression Potential: This changes whether lttng-probe-random.ko is
  available or not (if it is available the code is unchanged). User-
  space might be affected if this module is always expected.

  ---

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

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


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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Stefan Bader]

Upstream fixed this by doing a build-time check for the random.h file.
This requires doing the same to decide whether the resulting module
should be considered by the DKMS build.

** Patch added: "Proposal for fixing this"
   
https://bugs.launchpad.net/ubuntu/jammy/+source/lttng-modules/+bug/1986921/+attachment/5609560/+files/jammy-proposed.debdiff

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  In Progress

Bug description:
  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

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


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

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[robinkooli]

Confirmed affecting Samsung Galaxy Book2 (i7-1255U, Intel Iris Xe
Graphics, 16GB LPDDR4x / NP750XED-KC4SE).

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  `/var/cache/pbuilder/build/276481/build/grub2-2.06/obj/monol

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Gamithra M]

After trying out Alan's method (which did work well), I installed the
drivers recommended by Wei and the problem seems to be resolved!

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  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.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Po-Hsu Lin]

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20220808 ubuntu-lttng-smoke-test

** Tags added: 5.15 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/1986921

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  In Progress

Bug description:
  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

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


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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Stefan Bader]

This is caused by upstream dropping trace points in random (again). That
change got backported to v5.15.44. There is an upstream fix for lttng-
modules which needs to be applied to fix this:

commit ed1149ef
Author: Michael Jeanson 
Date:   Tue May 31 15:24:48 2022 -0400

fix: 'random' tracepoints removed in stable kernels

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

** Also affects: lttng-modules (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Jammy)
   Status: New => Won't Fix

** Changed in: lttng-modules (Ubuntu)
   Status: New => Invalid

** Changed in: lttng-modules (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: lttng-modules (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: lttng-modules (Ubuntu Jammy)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  In Progress

Bug description:
  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

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


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

[Kernel-packages] [Bug 1986921] [NEW] lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Stefan Bader]

Public bug reported:

This is a scripted bug report about ADT failures while running lttng-
modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.

Testing failed on:
amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Won't Fix

** Affects: lttng-modules (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Won't Fix

** Affects: lttng-modules (Ubuntu Jammy)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: 5.15 jammy kernel-adt-failure sru-20220808 ubuntu-lttng-smoke-test

** Tags added: kernel-adt-failure

** Changed in: linux (Ubuntu)
   Status: New => Won't Fix

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  In Progress

Bug description:
  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

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


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

[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash

[caine]

also issue with the new drivers :
- nvidia-graphics-drivers-515 (Ubuntu)

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

Title:
  No video after wake from S3 due to Nvidia driver crash

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake 
from suspend. It does start running again, but there is no video output. I'm 
attaching text for two crashes from kernel log output. First is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 
nv_restore_user_channels+0xce/0xe0 [nvidia]
  Second is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 
nv_set_system_power_state+0x2c8/0x3d0 [nvidia]

  Apparently I'm not the only one having this problem with 470 drivers.
  https://forums.linuxmint.com/viewtopic.php?t=354445
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150

  Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system-
  sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu
  21.04 and sleep was reliable then. Right now I'm going back to driver
  460.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.63.01-0ubuntu4
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct  6 23:24:02 2021
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago)

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


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