[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

[Po-Hsu Lin]

Verified with linux-intel-iotg/5.15.0-1017.22 kernel, this test is not failing 
anymore.
 # Tests passed:  40
 # Tests failed:   0
 # Tests xfailed:   0
 ok 1 selftests: net: icmp_redirect.sh

** Tags added: verification-done-jammy

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  Tests passed:  28
  Tests failed:  12
  Tests xfailed:   0

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


-- 
Mailing list: 

[Kernel-packages] [Bug 1993240] Re: amd_sfh modprobe fails when no sensor reported from AMD MP2

[You-Sheng Yang]

SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-October/134273.html (oem-6.0)

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ Some AMD platforms might not have sensor reported from MP2 controller,
+ and that fails device init.
+ 
+ [Fix]
+ 
+ Two commits targeting v6.1 release in mainline kernel.
+ 
+ [Test Case]
+ 
+ On such platforms, driver loading should be bailed out with:
+ 
+   $ sudo dmesg | grep amd_sfh1_1_hid_client_init
+   [ 1.204896] pcie_mp2_amd :62:00.7: amd_sfh1_1_hid_client_init failed
+ 
+ [Where problems could occur]
+ 
+ This skips driver loading against ineffective hardware only.
+ 
+ [Other Info]
+ 
+ While this targets oem-6.0 and above, and is already in mainline
+ v6.1-rc1, only oem-6.0 is nominated for fix.
+ 
+ == original bug report ==
+ 
  Fix amd_sfh to make each sensor with proper initialization & resource
  allocation during MP2 loaded.
  
  To be in v6.1
  
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=68266bdcceec10ea364e62c63732cd6fe5a256a8
  
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=beb18bb22cd4fb88648bb2925d56f36131c1ac21

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

Title:
  amd_sfh modprobe fails when no sensor reported from AMD MP2

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

Bug description:
  [SRU Justification]

  [Impact]

  Some AMD platforms might not have sensor reported from MP2 controller,
  and that fails device init.

  [Fix]

  Two commits targeting v6.1 release in mainline kernel.

  [Test Case]

  On such platforms, driver loading should be bailed out with:

$ sudo dmesg | grep amd_sfh1_1_hid_client_init
[ 1.204896] pcie_mp2_amd :62:00.7: amd_sfh1_1_hid_client_init failed

  [Where problems could occur]

  This skips driver loading against ineffective hardware only.

  [Other Info]

  While this targets oem-6.0 and above, and is already in mainline
  v6.1-rc1, only oem-6.0 is nominated for fix.

  == original bug report ==

  Fix amd_sfh to make each sensor with proper initialization & resource
  allocation during MP2 loaded.

  To be in v6.1

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=68266bdcceec10ea364e62c63732cd6fe5a256a8

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=beb18bb22cd4fb88648bb2925d56f36131c1ac21

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


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

[Kernel-packages] [Bug 1955353] Re: Installing linux-modules-extra-raspi in chroot triggers flash-kernel which fails

[Launchpad Bug Tracker]

This bug was fixed in the package flash-kernel - 3.104ubuntu14

---
flash-kernel (3.104ubuntu14) jammy; urgency=medium

  * Change FK_FORCE_CONTAINER to FK_FORCE and cleanly exit if running
in a chroot environment (LP: #1955353)

 -- William 'jawn-smith' Wilson   Fri, 07 Oct
2022 09:14:11 -0500

** Changed in: flash-kernel (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Installing linux-modules-extra-raspi in chroot triggers flash-kernel
  which fails

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Invalid
Status in flash-kernel source package in Jammy:
  Fix Released
Status in linux-raspi source package in Jammy:
  Invalid

Bug description:
  [Impact]
  If flash-kernel is installed in a chroot environment it will crash when 
trying to execute its postinst script. This will prevent the new design
  of ubuntu-image from building any images that have flash-kernel seeded.

  [Test Plan]
  * Create a chroot on armhf or arm64
  * sudo chroot  apt install -y flash-kernel 
linux-modules-extra-raspi
  * Observe that flash-kernel fails due to a non-existent boot partition
  * Enable -proposed in the chroot
  * Attempt to install flash_kernel and linux-modules-extra-raspi again
  * Observe that the packages now successfully install

  [Regression Potential]
  * If there are any valid existing workflows that attempt to run flash-kernel 
in a chroot, they could be affected by this change.
  * However, there is an environment variable in place, FK_FORCE, that will 
enable these workflows to succeed again
  * Testing should be done in some other valid non-chroot use cases to ensure 
no false positives in the chroot detection.

  [Original Description]
  Hey, following up on: 
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947601?comments=all

  Its not possible install linux-modules-extra-raspi in chroot, because it 
activates flash-kernel which fails.
  I also tried to bypass flash-kernel by moving /sbin/flash-kernel aside before 
installing, but then the issue of docker failing does not get fixed.

  This means that a number of distros I maintain can't have docker
  running correctly.

  Related: https://github.com/guysoft/CustomPiOS/issues/149

  Output:
  12:36:15 I: /boot/initrd.img is now a symlink to initrd.img-5.13.0-1011-raspi
  12:36:16 Setting up linux-modules-extra-5.13.0-1011-raspi (5.13.0-1011.13) ...
  12:36:20 Setting up linux-modules-5.13.0-1011-raspi (5.13.0-1011.13) ...
  12:36:25 Setting up linux-modules-extra-raspi (5.13.0.1011.17) ...
  12:36:25 Processing triggers for linux-image-5.13.0-1011-raspi 
(5.13.0-1011.13) ...
  12:36:25 /etc/kernel/postinst.d/initramfs-tools:
  12:36:25 update-initramfs: Generating /boot/initrd.img-5.13.0-1011-raspi
  12:36:45 cryptsetup: ERROR: Couldn't find sysfs directory for 7:0
  12:36:47 Label writable not found in /dev/disk/by-label
  12:36:48 Warning: root device LABEL=writable does not exist
  12:37:07 W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
  12:37:07 W: mdadm: failed to auto-generate temporary mdadm.conf file.
  12:38:59 flash-kernel: deferring update (trigger activated)
  12:38:59 /etc/kernel/postinst.d/zz-flash-kernel:
  12:38:59 flash-kernel: deferring update (trigger activated)
  12:38:59 Processing triggers for flash-kernel (3.104ubuntu5) ...
  12:39:00 Unsupported platform 'BCM2835'.
  12:39:00 dpkg: error processing package flash-kernel (--configure):
  12:39:00  installed flash-kernel package post-installation script subprocess 
returned error exit status 1
  12:39:00 Errors were encountered while processing:
  12:39:00  flash-kernel
  12:39:01 needrestart is being skipped since dpkg has failed
  12:39:09 E: Sub-process /usr/bin/dpkg returned an error code (1)
  12:39:09  echo_red 'build failed, unmounting image...'

  Things I tried:

  Patching as describe here: 
https://forums.raspberrypi.com/viewtopic.php?t=258056
  Then moving before install /sbin/flash-kernel to /sbin/flash-kernel.bak

  Results in the following output:

  13:14:27
  13:14:27 Pending kernel upgrade!
  13:14:27
  13:14:27 Running kernel version:
  13:14:27   5.10.81-v8+
  13:14:27
  13:14:27 Diagnostics:
  13:14:27   The currently running kernel version is not the expected kernel 
version 5.13.0-1011-raspi.
  13:14:27
  13:14:27 Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting. [Return]
  13:14:27
  13:14:27 Failed to check for processor microcode upgrades.
  13:14:27
  13:14:27 No services need to be restarted.
  13:14:27
  13:14:27 No containers need to be restarted.
  13:14:27
  13:14:27 No user sessions are running outdated binaries.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1994442] Re: XPS 9315 camera not working

[Kai-Chuan Hsieh]

** Description changed:

  The Camera doesn't work with 5.15.0-52-generic
+ 
+ The userspace packages list:
+ 
http://dell.archive.canonical.com/dists/focal-somerville-psyduck/public/binary-amd64/Packages
  
  Report kernel error:
  
-  十  26 09:50:30 PORT-DVT2-D1 kernel: ljca 3-4:1.0: bridge write failed 
ret:-110 total_len:64
- 
-  十  26 09:50:30 PORT-DVT2-D1 kernel: ljca-spi ljca-spi.16.auto: ljca spi 
transfer failed!
-  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: SPI transfer 
failed: -110
-  十  26 09:50:30 PORT-DVT2-D1 kernel: spi_master spi2: failed to transfer one 
message from queue
-  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: hw_reset failed 
ret = -19
-  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: reset failed 
ret = -19
-  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: link layer 
initialization failed.
-  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: init hw failure.
-  十  26 09:50:30 PORT-DVT2-D1 kernel: intel_tcc_cooling: Programmable TCC 
Offset detected
+  十  26 09:50:30 PORT-DVT2-D1 kernel: ljca 3-4:1.0: bridge write failed
+ ret:-110 total_len:64
+ 
+  十  26 09:50:30 PORT-DVT2-D1 kernel: ljca-spi ljca-spi.16.auto: ljca spi 
transfer failed!
+  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: SPI transfer 
failed: -110
+  十  26 09:50:30 PORT-DVT2-D1 kernel: spi_master spi2: failed to transfer one 
message from queue
+  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: hw_reset failed 
ret = -19
+  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: reset failed 
ret = -19
+  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: link layer 
initialization failed.
+  十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: init hw failure.
+  十  26 09:50:30 PORT-DVT2-D1 kernel: intel_tcc_cooling: Programmable TCC 
Offset detected
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 26 09:53:07 2022
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X196
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X196
  InstallationDate: Installed on 2022-10-19 (6 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  XPS 9315 camera not working

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

Bug description:
  The Camera doesn't work with 5.15.0-52-generic

  The userspace packages list:
  
http://dell.archive.canonical.com/dists/focal-somerville-psyduck/public/binary-amd64/Packages

  Report kernel error:

   十  26 09:50:30 PORT-DVT2-D1 kernel: ljca 3-4:1.0: bridge write failed
  ret:-110 total_len:64

   十  26 09:50:30 PORT-DVT2-D1 kernel: ljca-spi ljca-spi.16.auto: ljca spi 
transfer failed!
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: SPI transfer 
failed: -110
   十  26 09:50:30 PORT-DVT2-D1 kernel: spi_master spi2: failed to transfer one 
message from queue
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: hw_reset failed 
ret = -19
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: reset failed 
ret = -19
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: link layer 
initialization failed.
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: init hw failure.
   十  26 09:50:30 PORT-DVT2-D1 kernel: intel_tcc_cooling: Programmable TCC 
Offset detected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 26 09:53:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X196
  

[Kernel-packages] [Bug 1994442] [NEW] XPS 9315 camera not working

[Kai-Chuan Hsieh]

Public bug reported:

The Camera doesn't work with 5.15.0-52-generic

Report kernel error:

 十  26 09:50:30 PORT-DVT2-D1 kernel: ljca 3-4:1.0: bridge write failed ret:-110 
total_len:64

 十  26 09:50:30 PORT-DVT2-D1 kernel: ljca-spi ljca-spi.16.auto: ljca spi 
transfer failed!
 十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: SPI transfer 
failed: -110
 十  26 09:50:30 PORT-DVT2-D1 kernel: spi_master spi2: failed to transfer one 
message from queue
 十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: hw_reset failed 
ret = -19
 十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: reset failed ret 
= -19
 十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: link layer 
initialization failed.
 十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: init hw failure.
 十  26 09:50:30 PORT-DVT2-D1 kernel: intel_tcc_cooling: Programmable TCC Offset 
detected

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 26 09:53:07 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X196
InstallationDate: Installed on 2022-10-19 (6 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal fossa-psyduck

** Tags added: fossa-psyduck

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

Title:
  XPS 9315 camera not working

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

Bug description:
  The Camera doesn't work with 5.15.0-52-generic

  Report kernel error:

   十  26 09:50:30 PORT-DVT2-D1 kernel: ljca 3-4:1.0: bridge write failed 
ret:-110 total_len:64
  
   十  26 09:50:30 PORT-DVT2-D1 kernel: ljca-spi ljca-spi.16.auto: ljca spi 
transfer failed!
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: SPI transfer 
failed: -110
   十  26 09:50:30 PORT-DVT2-D1 kernel: spi_master spi2: failed to transfer one 
message from queue
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: hw_reset failed 
ret = -19
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: reset failed 
ret = -19
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: link layer 
initialization failed.
   十  26 09:50:30 PORT-DVT2-D1 kernel: mei_vsc spi-INTC1094:00: init hw failure.
   十  26 09:50:30 PORT-DVT2-D1 kernel: intel_tcc_cooling: Programmable TCC 
Offset detected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 26 09:53:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X196
  InstallationDate: Installed on 2022-10-19 (6 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  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/1994442/+subscriptions


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

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

[Kim Naru]

tags:   added: verification-done-jammy
removed: verification-needed-jammy

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

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

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

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


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

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

[Kim Naru]

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

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

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

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


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

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

[Kim Naru]

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

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

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

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


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

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

[Kim Naru]

verification-done-focal

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

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

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

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


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

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

[Mario Limonciello]

FYI - one of those commits has reverted in 6.1 due to regressions.

See this commit:
5632e2beaf9d5 ("Revert "PCI: Distribute available resources for root buses, 
too"")

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

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

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

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


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

[Kernel-packages] [Bug 1969434] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.53.59~20.04.21)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-hwe-5.15 
(5.15.0.53.59~20.04.21) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.15/5.15.0-53.59~20.04.1 (armhf)


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/focal/update_excuses.html#linux-meta-hwe-5.15

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

Title:
  build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-meta source package in Focal:
  Invalid
Status in linux-meta-hwe-5.15 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-meta source package in Jammy:
  Fix Released
Status in linux-meta-hwe-5.15 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justfication]

  [Impact]

  Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress,
  and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16.
  Not reproducible on every platform with AX211 installed, and the chances
  of such failures vary from one to another.

  [Fix]

  A few solutions were considered. The very first one is to ask Intel to
  fix -64 firmware directly, and the answer is a solid no claimed -64 is
  not the planned production version of AX211.

  It's also possible to backport FW API from v5.16, but while iwlwifi FW
  API is more or less a black box to us and the new FW APIs also depends
  on updates on the wireless stack, this is going to be very risky and
  actually we had regressions before after such backports.

  The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on
  the effected platforms. This means oem-5.14 and its migration target,
  hwe-5.15 will not be able to drive this piece of hw flawlessly without
  backport-iwlwifi-dkms installed.

  However, while we need secureboot to be enabled on these platforms,
  backport-iwlwifi-dkms must also be signed somehow. There are two
  possible method to achieve this, too. One, to prebuild this dkms as zfs
  and v4l2loopback does. However, while backport-iwlwifi-dkms generates
  kernel modules with exactly the same name as the in-tree ones, when
  prebuilt, they'll be available directly from the linux-modules package
  and therefore overrides the in-tree ones always, turning the in-tree
  driver completely useless and risk the stability of all other generic
  installations.

  The second one is to build backport-iwlwifi-dkms as nvidia graphic
  drivers in the linux-restricted-modules source package. In this way,
  affected platforms may install the corresponding packages when needed
  without interfering others. However, l-r-m is for restricted modules
  that needs special care of redistribution of its binaries, and
  backport-iwlwifi-dkms is GPL licensed.

  Here a similar but simpler process in the main kernel tree is
  re-implemented. Two additional packages,
  linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package
  linux-modules-MODULE-FLAVOUR will be created.

  [Test Case]

  Test builds:
  ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb
  ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb
  ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb
  ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb
  ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb
  ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb
  
./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb
  ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb

  [Where problems could occur]

  The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails
  to build under this proposed process. Debdiff attached to the same
  

[Kernel-packages] [Bug 1994164] Re: Kinetic update: v5.19.16 upstream stable release

[Kamal Mostafa]

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

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

Title:
  Kinetic update: v5.19.16 upstream stable release

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

Bug description:
  SRU Justification

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

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

  nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
  nilfs2: fix use-after-free bug of struct nilfs_root
  nilfs2: fix leak of nilfs_root in case of writer thread creation failure
  nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
  ceph: don't truncate file in atomic_open
  nvme-pci: set min_align_mask before calculating max_hw_sectors
  random: restore O_NONBLOCK support
  random: clamp credited irq bits to maximum mixed
  ALSA: hda: Fix position reporting on Poulsbo
  ALSA: hda/realtek: Add quirk for HP Zbook Firefly 14 G9 model
  efi: Correct Macmini DMI match in uefi cert quirk
  USB: serial: qcserial: add new usb-id for Dell branded EM7455
  Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG -> 
peripheral if extcon is present""
  Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is present"
  Revert "powerpc/rtas: Implement reentrant rtas call"
  Revert "crypto: qat - reduce size of mapped region"
  random: avoid reading two cache lines on irq randomness
  random: use expired timer rather than wq for mixing fast pool
  mctp: prevent double key removal and unref
  Input: xpad - add supported devices as contributed on github
  Input: xpad - fix wireless 360 controller breaking after suspend
  misc: pci_endpoint_test: Aggregate params checking for xfer
  misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
  Linux 5.19.16
  UBUNTU: Upstream stable to v5.19.16

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


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

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Arun]

I have send you the output of the above commands. Hope they are useful
:)

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

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Arun]

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+attachment/5626717/+files/dmesg.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/1981433

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Arun]

** Attachment added: "pacmd-list-sinks.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+attachment/5626716/+files/pacmd-list-sinks.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/1981433

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Arun]

** Attachment added: "pacmd-list-cards.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+attachment/5626713/+files/pacmd-list-cards.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/1981433

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Dave Chiluk]

So where are we on this folks?

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception 

[Kernel-packages] [Bug 1993884] Re: since 22.10 upgrade audio card no more detected

[Neo]

Link to the regression analysis :
https://www.spinics.net/lists/alsa-devel/msg146961.html

Kernel 5.19.9 
https://lwn.net/Articles/908139/

Takashi Iwai (6):
  [...]
  ALSA: hda: Once again fix regression of page allocations with IOMMU
  [...]

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

Title:
  since 22.10 upgrade  audio card no more  detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux neo-desktop 5.19.0-21-generic #21-Ubuntu SMP PREEMPT_DYNAMIC Wed
  Oct 12 18:33:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  CPU : AMD Ryzen 5 3600X  / 8GB RAM

  Loss of audio board detection from the kernel

  Extract from syslog :

  ct 22 10:51:45 neo-desktop kernel: [6.015793] snd_hda_intel :06:00.0: 
Disabling MSI
  Oct 22 10:51:45 neo-desktop kernel: [6.015796] snd_hda_intel 
:06:00.0: Force to non-snoop mode
  Oct 22 10:51:45 neo-desktop kernel: [6.015940] snd_hda_intel 
:07:00.1: Disabling MSI
  Oct 22 10:51:45 neo-desktop kernel: [6.015945] snd_hda_intel 
:07:00.1: Handle vga_switcheroo audio client
  Oct 22 10:51:45 neo-desktop kernel: [6.019066] hdaudio hdaudioC0D0: no 
AFG or MFG node found
  Oct 22 10:51:45 neo-desktop kernel: [6.019070] snd_hda_intel 
:06:00.0: no codecs initialized

  The HDA Nvidia HDMI is well detected :
  Oct 22 10:51:45 neo-desktop kernel: [6.027982] snd_hda_intel 
:07:00.1: bound :07:00.0 (ops nv50_audio_component_bind_ops [nouveau])
  Oct 22 10:51:45 neo-desktop kernel: [6.062868] input: HDA NVidia 
HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card1/input19
  Oct 22 10:51:45 neo-desktop kernel: [6.062906] input: HDA NVidia 
HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card1/input20
  Oct 22 10:51:45 neo-desktop kernel: [6.062939] input: HDA NVidia 
HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card1/input21
  Oct 22 10:51:45 neo-desktop kernel: [6.062977] input: HDA NVidia 
HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card1/input22
  Oct 22 10:51:45 neo-desktop kernel: [6.063011] input: HDA NVidia 
HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card1/input23


  This seems to be a regression on kernel 5.19.0 fixed in version 5.19.9
  When this regression will be solved ?
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neo1357 F pipewire
neo1360 F wireplumber
   /dev/snd/pcmC1D3p:   neo1357 F...m pipewire
   /dev/snd/seq:neo1357 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-12 (9 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Daily amd64 (20221012)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic 
root=UUID=d2fe7a04-00cb-4cc8-a751-0a3c6bcd992b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-21-generic N/A
   linux-backports-modules-5.19.0-21-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-21-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: 08/04/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.30
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.30:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


-- 
Mailing list: 

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

nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
nilfs2: fix use-after-free bug of struct nilfs_root
nilfs2: fix leak of nilfs_root in case of writer thread creation failure
nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
ceph: don't truncate file in atomic_open
nvme-pci: set min_align_mask before calculating max_hw_sectors
random: restore O_NONBLOCK support
random: clamp credited irq bits to maximum mixed
ALSA: hda: Fix position reporting on Poulsbo
ALSA: hda/realtek: Add quirk for HP Zbook Firefly 14 G9 model
efi: Correct Macmini DMI match in uefi cert quirk
USB: serial: qcserial: add new usb-id for Dell branded EM7455
Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG -> 
peripheral if extcon is present""
Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is present"
Revert "powerpc/rtas: Implement reentrant rtas call"
Revert "crypto: qat - reduce size of mapped region"
random: avoid reading two cache lines on irq randomness
random: use expired timer rather than wq for mixing fast pool
mctp: prevent double key removal and unref
Input: xpad - add supported devices as contributed on github
Input: xpad - fix wireless 360 controller breaking after suspend
misc: pci_endpoint_test: Aggregate params checking for xfer
misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
Linux 5.19.16
UBUNTU: Upstream stable to v5.19.16

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

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

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

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

** Changed in: linux (Ubuntu Kinetic)
 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.19.16 upstream stable release
+    from git://git.kernel.org/
  
-v5.19.16 upstream stable release
-from git://git.kernel.org/
+ nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
+ nilfs2: fix use-after-free bug of struct nilfs_root
+ nilfs2: fix leak of nilfs_root in case of writer thread creation failure
+ nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
+ ceph: don't truncate file in atomic_open
+ nvme-pci: set min_align_mask before calculating max_hw_sectors
+ random: restore O_NONBLOCK support
+ random: clamp credited irq bits to maximum mixed
+ ALSA: hda: Fix position reporting on Poulsbo
+ ALSA: hda/realtek: Add quirk for HP Zbook Firefly 14 G9 model
+ efi: Correct Macmini DMI match in uefi cert quirk
+ USB: serial: qcserial: add new usb-id for Dell branded EM7455
+ Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG -> 
peripheral if extcon is present""
+ Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is present"
+ Revert "powerpc/rtas: Implement reentrant rtas call"
+ Revert "crypto: qat - reduce size of mapped region"
+ random: avoid reading two cache lines on irq randomness
+ random: use expired timer rather than wq for mixing fast pool
+ mctp: prevent double key removal and unref
+ 

[Kernel-packages] [Bug 1994079] Re: fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to generate SIGXFSZ signal

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=216626.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2022-10-25T16:46:18+00:00 colin.i.king wrote:

Created attachment 303085
C source to reproduce the fallocate/SIGXFSZ issue

This is a corner case on 32 bit systems when using large file offsets,
fallocate and setrlimit. Issue found on ext4, probably also on other
file systems(?).

Setting the RLIMIT_FSIZE with setrlimit to 0x and then
fallocating 1 or more bytes at the offset of 0x should make the
fallocate fail with EFBIG and generate a SIGXFSZ signal. On 64 bit
platforms this works, on 32 bit platforms such as i386 4.15 kernels
through to linux 6.0 it fails to generate EFBIG errors and SIGXFSZ.

Attached is a test program to illustrate the problem. It sets the file
size limit and allocates 1024 bytes at the boundary file size limit for
3 offsets:

On 64 bit systems we get the expected results:
got signal SIGXFSZ
offset: 65536 (0x1), fallocate returned: -1
got signal SIGXFSZ
offset: 4294966271 (0xfbff), fallocate returned: -1
got signal SIGXFSZ
offset: 4294967295 (0x), fallocate returned: -1

On 32 bit systems the code fails on the 0x offset:

got signal SIGXFSZ
offset: 65536 (0x1), fallocate returned: -1
got signal SIGXFSZ
offset: 4294966271 (0xfbff), fallocate returned: -1
offset: 4294967295 (0x), fallocate returned: 0

Attached is the reproducer.

I found this while developing a file limit boundary test case in stress-
ng and discovered it breaks on all 32 bit kernels (armhf, i386, etc),
even with recent 5.15 and 6.0 kernels.

attached is a simple reproducer

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994079/comments/4


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to
  generate SIGXFSZ signal

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

Bug description:
  This is a corner case on 32 bit systems when using large file offsets,
  fallocate and setrlimit.

  Setting the RLIMIT_FSIZE with setrlimit to 0x and then
  fallocating 1 or more bytes at the offset of 0x should make
  the fallocate fail with EFBIG and generate a SIGXFSZ signal. On 64 bit
  platforms this works, on 32 bit platforms such as i386 Ubuntu bionic
  with 4.15 kernels it fails to generate EFBIG errors and SIGXFSZ.

  Attached is a test program to illustrate the problem. It sets the file
  size limit and allocates 1024 bytes at the boundary file size limit
  for 3 offsets:

  On 64 bit systems we get the expected results:
  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294967295 (0x), fallocate returned: -1

  On 32 bit systems the code fails on the 0x offset:

  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  offset: 4294967295 (0x), fallocate returned: 0

  Attached is the reproducer.

  I found this while developing a file limit boundary test case in
  stress-ng and discovered it breaks on all 32 bit kernels (armhf, i386,
  etc), even with recent 5.15 kernels.

  This could be seen as a security issue; the sysadmin can set the file
  size limit and yet a 32 bit system can use a corner case like this to
  fallocate a much larger file by using the 0x offset and a huge
  fallocate size.

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


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

[Kernel-packages] [Bug 1994079] Re: fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to generate SIGXFSZ signal

[Colin Ian King]

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=216626
   Importance: Unknown
   Status: Unknown

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

Title:
  fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to
  generate SIGXFSZ signal

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

Bug description:
  This is a corner case on 32 bit systems when using large file offsets,
  fallocate and setrlimit.

  Setting the RLIMIT_FSIZE with setrlimit to 0x and then
  fallocating 1 or more bytes at the offset of 0x should make
  the fallocate fail with EFBIG and generate a SIGXFSZ signal. On 64 bit
  platforms this works, on 32 bit platforms such as i386 Ubuntu bionic
  with 4.15 kernels it fails to generate EFBIG errors and SIGXFSZ.

  Attached is a test program to illustrate the problem. It sets the file
  size limit and allocates 1024 bytes at the boundary file size limit
  for 3 offsets:

  On 64 bit systems we get the expected results:
  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294967295 (0x), fallocate returned: -1

  On 32 bit systems the code fails on the 0x offset:

  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  offset: 4294967295 (0x), fallocate returned: 0

  Attached is the reproducer.

  I found this while developing a file limit boundary test case in
  stress-ng and discovered it breaks on all 32 bit kernels (armhf, i386,
  etc), even with recent 5.15 kernels.

  This could be seen as a security issue; the sysadmin can set the file
  size limit and yet a 32 bit system can use a corner case like this to
  fallocate a much larger file by using the 0x offset and a huge
  fallocate size.

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


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

[Kernel-packages] [Bug 1994079] Re: fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to generate SIGXFSZ signal

[Colin Ian King]

occurs on 6.0 i386 kernels too

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

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

Title:
  fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to
  generate SIGXFSZ signal

Status in linux package in Ubuntu:
  New

Bug description:
  This is a corner case on 32 bit systems when using large file offsets,
  fallocate and setrlimit.

  Setting the RLIMIT_FSIZE with setrlimit to 0x and then
  fallocating 1 or more bytes at the offset of 0x should make
  the fallocate fail with EFBIG and generate a SIGXFSZ signal. On 64 bit
  platforms this works, on 32 bit platforms such as i386 Ubuntu bionic
  with 4.15 kernels it fails to generate EFBIG errors and SIGXFSZ.

  Attached is a test program to illustrate the problem. It sets the file
  size limit and allocates 1024 bytes at the boundary file size limit
  for 3 offsets:

  On 64 bit systems we get the expected results:
  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294967295 (0x), fallocate returned: -1

  On 32 bit systems the code fails on the 0x offset:

  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  offset: 4294967295 (0x), fallocate returned: 0

  Attached is the reproducer.

  I found this while developing a file limit boundary test case in
  stress-ng and discovered it breaks on all 32 bit kernels (armhf, i386,
  etc), even with recent 5.15 kernels.

  This could be seen as a security issue; the sysadmin can set the file
  size limit and yet a 32 bit system can use a corner case like this to
  fallocate a much larger file by using the 0x offset and a huge
  fallocate size.

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


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

[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot

[ltkarrde]

Appears to be fixed in 5.15.0-53-lowlatency; no longer appearing in my
error logs.

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

Title:
  Aquantia GbE LAN driver causes UBSAN error during kernel boot

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  The undefined behaviour sanitiser picks up an array-index-out-of-
  bounds in the aquantia atlantic driver. The NIC is (I think) built
  into my gigabyte motherboard
  (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME-
  rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to
  22.04 (or at least dmesg didn't previously complain).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 13:02:10 2022
  InstallationDate: Installed on 2019-08-07 (899 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1994082] Re: vlc will only sometimes show video with nvidia drivers 515 (and 510) following update to 22.10

[Ian]

Also happens with the nouveau drivers, so not just the nvidia-graphics
ones

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

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

Title:
  vlc will only sometimes show video with nvidia drivers 515 (and 510)
  following update to 22.10

Status in vlc package in Ubuntu:
  New

Bug description:
  Typically.. the first video will play, but subsequent ones show a
  blank black screen although the audio is heard.

  Restarting vlc will usually allow you to see the video, but again,
  only for the first one.

  The attached extract from .xsessions-errors is when trying with the
  510 drivers, but the same thing happens with 515.

  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  vlc3.0.17.4-5   amd64multimedia player and streamer

  ii  nvidia-compute-utils-510  510.85.02-0ubuntu2  amd64NVIDIA 
compute utilities
  ii  nvidia-dkms-510   510.85.02-0ubuntu2  amd64NVIDIA 
DKMS package
  ii  nvidia-driver-510 510.85.02-0ubuntu2  amd64NVIDIA 
driver metapackage
  ii  nvidia-kernel-common-510  510.85.02-0ubuntu2  amd64Shared 
files used with the kernel module
  ii  nvidia-kernel-source-510  510.85.02-0ubuntu2  amd64NVIDIA 
kernel source package
  ii  nvidia-prime  0.8.17.1all  Tools 
to enable NVIDIA's Prime
  ii  nvidia-settings   510.47.03-0ubuntu1  amd64Tool 
for configuring the NVIDIA graphics driver
  ii  nvidia-utils-510  510.85.02-0ubuntu2  amd64NVIDIA 
driver support binaries

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


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

[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules

[Brian Murray]

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

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

Title:
  fails to sign kernel modules

Status in Release Notes for Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Committed

Bug description:
  Expected on kinetic:  dkms will sign built modules with MOK key if
  requested.

  What happens:
  dkms outputs "Binary kmod-sign not found, modules won't be signed"

  Fix:
  update dkms to 3.0.7:  https://github.com/dell/dkms/pull/242

  ---

  dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve
  this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+subscriptions


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

[Kernel-packages] [Bug 1994157] [NEW] Chromium and Firefox snap won't launch with Linux 6.0.0-1006-oem Kernel

[Sebastian Heiden]

Private bug reported:

When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and Chromium
won't open anymore.

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

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

** Information type changed from Public to Private

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

Title:
  Chromium and Firefox snap won't launch with Linux 6.0.0-1006-oem
  Kernel

Status in linux-oem-6.0 package in Ubuntu:
  Invalid

Bug description:
  When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and
  Chromium won't open anymore.

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


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

[Kernel-packages] [Bug 1994153] Re: package linux-image-5.17.0-1020-oem 5.17.0-1020.21 failed to install/upgrade: installed linux-image-5.17.0-1020-oem package pre-removal script subprocess returned e

[apostol]

It seems that this is an installation problem. I fixed it by installing the 
missing packages:
sudo apt install linux-headers-5.17.0-1020-oem
sudo apt install linux-modules-nvidia-515-5.17.0-1020-oem
This fixes the problem completely.

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

Title:
  package linux-image-5.17.0-1020-oem 5.17.0-1020.21 failed to
  install/upgrade: installed linux-image-5.17.0-1020-oem package pre-
  removal script subprocess returned error exit status 1

Status in linux-signed-oem-5.17 package in Ubuntu:
  New

Bug description:
  Dual screen mode does not work, although it works with the previous
  version, linux-image-5.15.0-52-generic.

  1) Output of lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  2) Output of apt-cache policy linux-image-5.17.0-1020-oem
  linux-image-5.17.0-1020-oem:
Installed: 5.17.0-1020.21
Candidate: 5.17.0-1020.21
Version table:
   *** 5.17.0-1020.21 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  3) I expected dual screen mode to work and in Settings->Display two monitors 
to appear.
  4) Dual screen mode does not work and in Settings->Display only one monitor 
appears, the built-in (Dell laptop) while the HDMI connected (LG) does not 
appear. They appear correctly when I boot kernel linux-image-5.15.0-52-generic 
(with nvidia driver). They also appear correctly when I boot kernel 5.17 with 
the nouveau (instead of the nvidia) driver.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21
  ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
  Uname: Linux 5.17.0-1020-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-signatures-nvidia-5.17.0-1020-oem:amd64: Remove
   linux-modules-5.17.0-1020-oem:amd64: Remove
   linux-image-5.17.0-1020-oem:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Oct 25 17:56:22 2022
  ErrorMessage: installed linux-image-5.17.0-1020-oem package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-07-14 (832 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: linux-signed-oem-5.17
  Title: package linux-image-5.17.0-1020-oem 5.17.0-1020.21 failed to 
install/upgrade: installed linux-image-5.17.0-1020-oem package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1994153] [NEW] package linux-image-5.17.0-1020-oem 5.17.0-1020.21 failed to install/upgrade: installed linux-image-5.17.0-1020-oem package pre-removal script subprocess returned

[apostol]

Public bug reported:

Dual screen mode does not work, although it works with the previous
version, linux-image-5.15.0-52-generic.

1) Output of lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
2) Output of apt-cache policy linux-image-5.17.0-1020-oem
linux-image-5.17.0-1020-oem:
  Installed: 5.17.0-1020.21
  Candidate: 5.17.0-1020.21
  Version table:
 *** 5.17.0-1020.21 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
3) I expected dual screen mode to work and in Settings->Display two monitors to 
appear.
4) Dual screen mode does not work and in Settings->Display only one monitor 
appears, the built-in (Dell laptop) while the HDMI connected (LG) does not 
appear. They appear correctly when I boot kernel linux-image-5.15.0-52-generic 
(with nvidia driver). They also appear correctly when I boot kernel 5.17 with 
the nouveau (instead of the nvidia) driver.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21
ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
Uname: Linux 5.17.0-1020-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering:
 linux-signatures-nvidia-5.17.0-1020-oem:amd64: Remove
 linux-modules-5.17.0-1020-oem:amd64: Remove
 linux-image-5.17.0-1020-oem:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Oct 25 17:56:22 2022
ErrorMessage: installed linux-image-5.17.0-1020-oem package pre-removal script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-07-14 (832 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.6, unpackaged
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: linux-signed-oem-5.17
Title: package linux-image-5.17.0-1020-oem 5.17.0-1020.21 failed to 
install/upgrade: installed linux-image-5.17.0-1020-oem package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-oem-5.17 (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 linux-signed-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1994153

Title:
  package linux-image-5.17.0-1020-oem 5.17.0-1020.21 failed to
  install/upgrade: installed linux-image-5.17.0-1020-oem package pre-
  removal script subprocess returned error exit status 1

Status in linux-signed-oem-5.17 package in Ubuntu:
  New

Bug description:
  Dual screen mode does not work, although it works with the previous
  version, linux-image-5.15.0-52-generic.

  1) Output of lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  2) Output of apt-cache policy linux-image-5.17.0-1020-oem
  linux-image-5.17.0-1020-oem:
Installed: 5.17.0-1020.21
Candidate: 5.17.0-1020.21
Version table:
   *** 5.17.0-1020.21 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  3) I expected dual screen mode to work and in Settings->Display two monitors 
to appear.
  4) Dual screen mode does not work and in Settings->Display only one monitor 
appears, the built-in (Dell laptop) while the HDMI connected (LG) does not 
appear. They appear correctly when I boot kernel linux-image-5.15.0-52-generic 
(with nvidia driver). They also appear correctly when I boot kernel 5.17 with 
the nouveau (instead of the nvidia) driver.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21
  ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
  Uname: Linux 5.17.0-1020-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-signatures-nvidia-5.17.0-1020-oem:amd64: Remove
   linux-modules-5.17.0-1020-oem:amd64: Remove
   linux-image-5.17.0-1020-oem:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Oct 25 17:56:22 2022
  ErrorMessage: installed linux-image-5.17.0-1020-oem package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-07-14 (832 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: linux-signed-oem-5.17
  Title: package linux-image-5.17.0-1020-oem 

[Kernel-packages] [Bug 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel

[AaronMa]

** Tags added: verification-done-jammy

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

Title:
  Fix blank screen on Thinkpad ADL 4K+ panel

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

Bug description:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  It's a upstream kernel regression.
  And reverted by upstream.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  Low risk, it reverts a regression and may break i915 driver.

  On 5.14-oem and Jammy kernel, This commit was claimed to backport
  commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for 
max dp source rate")
  But it's not kind of it.
  So revert it instead.

  On 5.17 kernel, revert it by upstream commit.

  Unstable kernel already got it.

  
  V2:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  Reload link rate as WA to fix the issue.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  It may break DP output on Intel platform.

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


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

[Kernel-packages] [Bug 1953575] Re: Update gvnic driver code

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Update gvnic driver code

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-gcp source package in Impish:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Committed

Bug description:
  The GCE internal team responsible for gVNIC would like to have driver
  updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS.


  [Impact]
  Missing functionality from the Google gvnic driver

  
  [Test Plan]
  Confirm that gvnic module still loads and operates the gvnic driver. More 
extensive testing done by the gvnic developers at GCE

  
  [Regression potential]
  Possible regression in gvnic behaviour or functionality. Changes are confined 
to the gvnic driver code so regression potential is limited to gvnic only.


  
  List of changes:

  3712db620c613 gve: DQO: Configure interrupts on device up
  a9fd7559a367a gve: Check TX QPL was actually assigned
  c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check
  f48adc2842b17 gve: DQO: Remove incorrect prefetch
  98fd04939ae7e gve: Simplify code and axe the use of a deprecated API
  56c0904d8491d gve: Propagate error codes to caller
  86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo()
  ea364622fb118 gve: Fix warnings reported for DQO patchset
  8890e8783c6e6 gve: DQO: Add RX path
  abfc55f80d423 gve: DQO: Add TX path
  ef63867982913 gve: DQO: Add ring allocation and initialization
  dc3e0aef11bf0 gve: DQO: Add core netdev features
  873fd9825efd7 gve: Update adminq commands to support DQO queues
  543dc0e670472 gve: Add DQO fields for core data structures
  b580730931348 gve: Add dqo descriptors
  74e123d3c62b2 gve: Add support for DQO RX PTYPE map
  a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic
  3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format`
  a6b09c93c1735 gve: Introduce a new model for device options
  34d6b75678979 gve: Add support for raw addressing in the tx path
  30b6221596699 Revert "gve: Check TX QPL was actually assigned"
  98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset
  ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument
  5fc5c482008b5 gve: Move some static functions to a common file
  ed1e0daeee1ac gve: Rx Buffer Recycling
  da57760d6370d gve: Add support for raw addressing to the rx path
  b512608f33d8e gve: Add support for raw addressing device option
  e85394c77cdce gve: Enable Link Speed Reporting in the driver.
  8961791d8ba16 gve: Batch AQ commands for creating and destroying queues.
  50bafd6d5a041 gve: NIC stats for report-stats and for ethtool
  feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags.
  08578185ab296 gve: Use dev_info/err instead of netif_info/err.
  613ed2d16246f gve: Add stats for gve.
  250d220740d21 gve: Get and set Rx copybreak via ethtool

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


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

[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  refactoring of overlayfs fix to properly support shiftfs

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
  Confirmed

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch is required to use overlayfs on top of shiftfs and without
  this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  However, we made this patch dependent on AUFS, starting with Jammy
  we're not enabling AUFS anymore, so this fix becomes a no-op.

  So we need to re-introduce this fix with a bit of refactoring to not
  depend on AUFS.

  [Test case]

  The following script can be used to trigger the issue:

    #!/bin/bash

    cat > test.py << EOF
    import sys

    f = open("/proc/self/maps")

    for l in f.readlines():
  if "python" not in l:
    continue
  print(l)
  s = l.split()
  start, end = s[0].split("-")
  fname = s[-1]
  print(start, end, fname)
  break
    else:
  sys.exit(1)

    test_file1 = open(fname)
    test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))

    fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
    fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()

    if fdinfo1 != fdinfo2:
  print("FAIL")
  print(test_file1)
  print(fdinfo1)
  print(test_file2)
  print(fdinfo2)
  sys.exit(1)
    print("PASS")
    EOF
    sudo docker run -it --privileged --rm -v `pwd`:/mnt python python 
/mnt/test.py

  [Fix]

  Import the right pieces from AUFS to properly support the fix and get 
  rid of the AUFS dependency across all our kernels and re-apply the 
  overlayfs fix without the AUFS dependency.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs, especially when containers are used.

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


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

[Kernel-packages] [Bug 1986798] Re: Remove unused variable from i915 psr

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Remove unused variable from i915 psr

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
  SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")

  [Fix]
  The variable is unused, remove it.

  [Test]
  Compiler no longer warns about it.

  [Where problems could occur]
  Nothing.

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


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

[Kernel-packages] [Bug 1989495] Re: mlxbf_gige: need to clear MDIO gateway lock after read

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  mlxbf_gige: need to clear MDIO gateway lock after read

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The BlueField-2 GIGE logic accesses the MDIO device via reads/writes
  to a gateway (GW) register. The MDIO GW lock is set after read. Make
  sure to always clear to indicate that the GW register is not being used.
  If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO
  accesses will be blocked and PHY device will be inaccessible.

  [Fix]
  For each MDIO read and write transaction, the last step should
  be to clear the MDIO GW lock.

  [Test Case]
  Boot the BlueField-2 platform
  Bring up the "oob_net0" interface via DHCP or static IP
  Ping and file transfer over "oob_net0" should work properly
  Bounce the "oob_net0" interface a few times and repeat tests

  [Regression Potential]
  * Low risk for causing a regression, tested well in our lab.

  [Other]
  * None

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


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

[Kernel-packages] [Bug 1991112] Re: mlxbf_gige: compute MDIO period based on i1clk

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  mlxbf_gige: compute MDIO period based on i1clk

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  The following upstream patch should be cherry picked to jammy kernel:

  3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk

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


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

[Kernel-packages] [Bug 1991151] Re: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  The Jammy repo contains the following SAUCE patch:
  UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read

  This patch is now in mainline Linux kernel, so the SAUCE patch
  can be reverted and replaced with the upstream commit SHA.

  [Fix]

  The fix requires two parts, the first of which is addressed by
  this bug. A second bug will be created to add the upstream
  commit to the repo. The fix to this bug is a revert of the SAUCE patch
  8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read

  [Test Case]

  Boot platform and bring up "oob_net0" interface properly
  Test that network traffic works properly

  [Regression Potential]

  Low, as this logic is well tested.

  [Other]

  Will add a note to this bug with the second bug's number,
  after the second bug is created. The second bug is for
  adding the upstream commit to the Jammy repo.

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


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

[Kernel-packages] [Bug 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Fix blank screen on Thinkpad ADL 4K+ panel

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

Bug description:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  It's a upstream kernel regression.
  And reverted by upstream.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  Low risk, it reverts a regression and may break i915 driver.

  On 5.14-oem and Jammy kernel, This commit was claimed to backport
  commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for 
max dp source rate")
  But it's not kind of it.
  So revert it instead.

  On 5.17 kernel, revert it by upstream commit.

  Unstable kernel already got it.

  
  V2:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  Reload link rate as WA to fix the issue.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  It may break DP output on Intel platform.

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


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

[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1983656

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following ip parameters

  $ sudo ip a a 192.168.1.7/24 dev enp7s0
  $ sudo ip link set up dev enp7s0
  $ sudo ip link set mtu 9000 

[Kernel-packages] [Bug 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Jammy: Add OVS Internal Port HW Offload to mlx5 driver

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  A request has been made, originating from
  https://bugs.launchpad.net/bugs/1980730, to add support for OVS
  internal port offload for the mlx5 driver. This feature takes care of
  certain traffic workloads that are not currently being offloaded to
  the hardware.

  [Test Case]

  Tested by the requester.

  [Where things could go wrong]

  These changes could potentially introduce regressions in behavior of
  the mlx5 driver.

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


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

[Kernel-packages] [Bug 1989578] Re: Add HDMI codec ID for Intel Raptor Lake

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Add HDMI codec ID for Intel Raptor Lake

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

Bug description:
  [SRU Justification]

  [Impact]
  The HDAudio is not functional on some RaptorLake machines. The audio codec is 
failed to be probed so no PCM stream available for audio functions.

  [Fix]
  Backport the patch from upstream which adds the support for the HDMI codec ID 
on RaptorLake.

  [Test]
  Power on the machine and check if the audio function's working with alsa 
utilities.

  [Where problems could occur]
  The change only applies to the new RaptorLake Intel HDA controller and HDMI 
codec.

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


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

[Kernel-packages] [Bug 1987699] Re: azure: CIFS Backport Updates to 5.15 Kernel

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  azure: CIFS Backport Updates to 5.15 Kernel

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested updating CIFS to the 5.15 backport as
  published in 'git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport'.

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  CIFS network connections could misbehave

  [Other Info]

  SF: #00343105

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


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

[Kernel-packages] [Bug 1987998] Re: LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1987998

  [Impact]

  The Ubuntu kernel carries an out of tree patchet, known as "LSM:
  Module stacking for AppArmor" upstream, to enable stackable LSMs for
  containers. The revision the Ubuntu kernel carries is an older one,
  from 2020, and has some slight divergences from the latest revision in
  development.

  One such divergence, is support for Landlock as a stackable LSM. When
  the stackable LSM patchset was applied, Landlock was still in
  development and not mainlined yet, and wasn't present in the earlier
  revision of the "LSM: Module stacking for AppArmor" patchset. Support
  for this was added by us.

  There was a minor omission made during enabling support for Landlock.
  The LSM slot type was marked as LSMBLOB_NEEDED, when it should have
  been LSMBLOB_NOT_NEEDED.

  Landlock itself does not provide any of the hooks that use a struct
  lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid,
  cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and
  ipc_getsecid.

  When we set .slot = LSMBLOB_NEEDED, this indicates that we need an
  entry in struct lsmblob, and we need to increment LSMBLOB_ENTRIES by
  one to fit the entry into the secid array:

  #define LSMBLOB_ENTRIES ( \
     (IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0))

  struct lsmblob {
     u32 secid[LSMBLOB_ENTRIES];
  };

  Currently, we don't increment LSMBLOB_ENTRIES by one to make an entry
  for Landlock, so for the Ubuntu kernel, we can fit a maximum of two
  entries, one for Apparmor and one for bpf.

  If you try and configure three LSMs like so and reboot:

  GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"

  You will receive the following panic:

  LSM: Security Framework initializing
  landlock: Up and running.
  LSM support for eBPF active
  Kernel panic - not syncing: security_add_hooks Too many LSMs registered.
  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
  Call Trace:
   
   show_stack+0x52/0x5c
   dump_stack_lvl+0x4a/0x63
   dump_stack+0x10/0x16
   panic+0x149/0x321
   security_add_hooks+0x45/0x13a
   apparmor_init+0x189/0x1ef
   initialize_lsm+0x54/0x74
   ordered_lsm_init+0x379/0x392
   security_init+0x40/0x49
   start_kernel+0x466/0x4dc
   x86_64_start_reservations+0x24/0x2a
   x86_64_start_kernel+0xe4/0xef
   secondary_startup_64_no_verify+0xc2/0xcb
   
  ---[ end Kernel panic - not syncing: security_add_hooks Too many LSMs 
registered. ]---

  There is a check added in security_add_hooks() that makes sure that
  you cannot configure too many LSMs:

  if (lsmid->slot == LSMBLOB_NEEDED) {
   if (lsm_slot >= LSMBLOB_ENTRIES)
    panic("%s Too many LSMs registered.\n", __func__);
   lsmid->slot = lsm_slot++;
   init_debug("%s assigned lsmblob slot %d\n", lsmid->lsm,
   lsmid->slot);
  }

  A workaround is to enable no more than 2 LSMs until this is fixed.

  [Fix]

  If you read the following mailing list thread on linux-security-
  modules from May 2021:

  https://lore.kernel.org/selinux/202105141224.942DE93@keescook/T/

  It is explained that Landlock does not provide any of the hooks that
  use a struct lsmblob, such as secid_to_secctx, secctx_to_secid,
  inode_getsecid, cred_getsecid, kernel_act_as task_getsecid_subj
  task_getsecid_obj and ipc_getsecid.

  I verified this with:

  ubuntu-jammy$ grep -Rin "secid_to_secctx" security/landlock/
  ubuntu-jammy$ grep -Rin "secctx_to_secid" security/landlock/
  ubuntu-jammy$ grep -Rin "inode_getsecid" security/landlock/
  ubuntu-jammy$ grep -Rin "cred_getsecid" security/landlock/
  ubuntu-jammy$ grep -Rin "kernel_act_as" security/landlock/
  ubuntu-jammy$ grep -Rin "task_getsecid_subj" 

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception  

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

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

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

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


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

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

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

  [Test]
  Verified on the target machine.

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

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


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

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

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

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

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


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

[Kernel-packages] [Bug 1991113] Re: "source" PKA driver Kconfig in mellanox/Kconfig

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  "source" PKA driver Kconfig in mellanox/Kconfig

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  PKA driver Kconfig needs to be "sourced" in mellanox/Kconfig. This
  makes MLXBF_PKA config option visible by the kernel configuration
  system and is needed to actually build PKA driver.

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


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

[Kernel-packages] [Bug 1991134] Re: Azure: PCI: Fix synchronization

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Azure: PCI: Fix synchronization

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has asked that the following commits be added to fix some
  Hyperv PCI synchronization issues.

  
  2022-05-13
  PCI: hv: Fix synchronization between channel callback and hv_pci_bus_exit()
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5=b4927bd272623694314f37823302f9d67aa5964c

  2022-04-25
  PCI: hv: Fix synchronization between channel callback and hv_compose_msi_msg()
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5=a765ed47e45166451680ee9af2b9e435c82ec3ba

  2022-04-25
  Drivers: hv: vmbus: Introduce {lock, unlock}_requestor()
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5=b91eaf7267cf7aec0a4e087decf7770dfb694d78

  2022-04-25
  Drivers: hv: vmbus: Introduce vmbus_request_addr_match()
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5=0aadb6a7bb811554cf39318b5d18e8ec50dd9f02

  2022-04-25
  Drivers: hv: vmbus: Introduce vmbus_sendpacket_getid()
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5=b03afa57c65e1e045e02df49777e953742745f4c

  2022-04-25
  PCI: hv: Use vmbus_requestor to generate transaction IDs for VMbus hardening
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc5=de5ddb7d44347ad8b00533c1850a4e2e636a1ce9

  [Test Plan]

  Boot tested, Microsoft tested

  [Where things could go wrong]

  Hyperv drivers could fail to load correctly.

  [Other Info]

  SF: #00345197

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


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

[Kernel-packages] [Bug 1991403] Re: mlxbf_gige: fix devm_ioremap error handling

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  mlxbf_gige: fix devm_ioremap error handling

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  The following upstream commit was recently added to Jammy:
3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk

  This patch added driver logic that includes a "devm_ioremap"
  call, but the error handling logic pertaining to this call
  is incorrect.

  [Fix]

  The "devm_ioremap" function returns NULL on error, it doesn't 
  return error pointers.  The error handling logic has been
  fixed accordingly.

  [Test Case]

  Boot platform and bring up "oob_net0" interface properly
  Test that network traffic works properly

  [Regression Potential]

  Low, as the patch was reviewed upstream

  [Other]

  None

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


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

[Kernel-packages] [Bug 1991551] Re: i2c-mlxbf.c: Sync up driver with upstreaming

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  i2c-mlxbf.c: Sync up driver with upstreaming

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4)
  and Jammy (5.15) and cherry-pick all changes from linux-next master.

  IMPORTANT NOTE: The new linux i2c support for BF3 also REQUIRES
  upgrading the UEFI firmware version. For BF1 and BF2 however, this
  driver should be backward compatible with older UEFI versions.

  [Fix]

  * There is a total of 17 commits: 8 reverts, 8 cherry-picks from
  linux-next and one internal "UBUNTU: SAUCE:" to ad the driver version.
  Following is the list of commits cherry-picked.

  * i2c: mlxbf: incorrect base address passed during io write
  From 


  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
  From 


  * i2c: mlxbf: remove IRQF_ONESHOT
  From 


  * i2c: mlxbf: Fix frequency calculation
  From 


  * i2c: mlxbf: support lock mechanism
  From 


  * i2c: mlxbf: add multi slave functionality
  From 


  * i2c: mlxbf: support BlueField-3 SoC
  From 


  * i2c: mlxbf: remove device tree support
  From 


  * Also add the i2c driver version to keep track of the changes
  internally.

  [Test Case]

  * Check that the i2c driver loads without errors on BF1 and BF2 (dmesg, and 
check i2c1 sysfs is created)
  * Check that the i2c module can be removed and reloaded without errors.
  * Check that IPMB services work successfully on systems with BMC. This is the 
best way to test the i2c driver. Run ipmitool command from the BF: ipmitool mc 
info
  * Run ipmitool from the BMC as well: ipmitool -I ipmb mc info
  * This driver should be backward compatible
  * Make sure this driver is backward compatible with older UEFI version (only 
applicable for BF1 and BF2)
  * Make sure this driver works for BF1, BF2 and BF3 with the latest UEFI 
version.

  [Regression Potential]

  * The i2c driver could fail to load because the UEFI firmware hasn't been 
upgraded
  * The i2c driver would fail to load due to a bug
  * IPMB code which utilises the i2c driver fails to work (ipmitool commands)

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


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

[Kernel-packages] [Bug 1992484] Re: Kernel regresses openjdk on riscv64

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Kernel regresses openjdk on riscv64

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Over at https://lore.kernel.org/linux-
  riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2
  it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses
  userspace (openjdk) on riscv64.

  This commit has already been released in v6.0 kernel upstream, but has
  also been included in the stable patch series all the way back to
  v4.19.y

  There is a proposed fix for this at https://lore.kernel.org/linux-
  riscv/20220915193702.2201018-1-abres...@rivosinc.com/ which has not
  yet been merged upstream or in stable series.

  Please review and merge above proposed fix, or please revert
  2139619bcad7ac44cc8f6f749089120594056613 to stop the regression
  spreading to all the distributions.

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


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

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

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  md: Replace snprintf with scnprintf

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

Bug description:
  SRU Justification

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

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

  [Fix]

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

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1993217] Re: old commit make HDMI audio not available if not eld_valid

[Paul Dufresne]

Previous link for the patch may be wrong, here a new one:
https://gitlab.freedesktop.org/agd5f/linux/-/commit/34d84636e5e09521d031863a01f9b9fb22ffa875

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

Title:
  old commit make HDMI audio not available if not eld_valid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on my friend laptop with his TV.
  HDMI audio not available in pavucontrol (profile say unplugged, unavailable) 
in kernel versions with bugs.
  It is just shown as an audio output (HDMI audio) on kernels where it is 
working.
  When not working, I can play with aplay -D HDMI ... 
  When working... I select HDMI audio in output, and test sound ok, Youtube 
videos ok, etc.

  4.9.177 working.
  4.9.178 not working.

  I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
  is between those versions, and is related to audio (realtek in part).

  More info at:
  https://forums.linuxmint.com/viewtopic.php?f=49=383607=2246352#p2246352
  although the laptop now runs ... 17.10 I think (a version with a not broken 
kernel).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  client 1023 F pulseaudio
   /dev/snd/pcmC0D0p:   client 1023 F...m pulseaudio
   /dev/snd/controlC1:  client 1023 F pulseaudio
  CasperMD5json: {
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  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-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  Tags:  vanessa apport-hook-error
  Uname: Linux 5.15.0-50-generic x86_64
  UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 10/16/2010
  dmi.bios.release: 2.0
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 02UF
  dmi.board.name: R425D/R525D
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr02UF:bd10/16/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425D/R525D:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425D/R525D:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:sku:
  dmi.product.name: R425D/R525D
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Kernel-packages] [Bug 1993217] Re: old commit make HDMI audio not available if not eld_valid

[Paul Dufresne]

v.4. of the patch https://gitlab.freedesktop.org/drm/amd/ ... t-v4.patch
published yesterday, have been accepted by the radeon maintainer:
https://lore.kernel.org/all/CADnq5_N-4t ... gmail.com/ I tested it
yesterday on top of 6.0.1-rc2 kernel and it was working fine.

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

Title:
  old commit make HDMI audio not available if not eld_valid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on my friend laptop with his TV.
  HDMI audio not available in pavucontrol (profile say unplugged, unavailable) 
in kernel versions with bugs.
  It is just shown as an audio output (HDMI audio) on kernels where it is 
working.
  When not working, I can play with aplay -D HDMI ... 
  When working... I select HDMI audio in output, and test sound ok, Youtube 
videos ok, etc.

  4.9.177 working.
  4.9.178 not working.

  I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
  is between those versions, and is related to audio (realtek in part).

  More info at:
  https://forums.linuxmint.com/viewtopic.php?f=49=383607=2246352#p2246352
  although the laptop now runs ... 17.10 I think (a version with a not broken 
kernel).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  client 1023 F pulseaudio
   /dev/snd/pcmC0D0p:   client 1023 F...m pulseaudio
   /dev/snd/controlC1:  client 1023 F pulseaudio
  CasperMD5json: {
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  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-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  Tags:  vanessa apport-hook-error
  Uname: Linux 5.15.0-50-generic x86_64
  UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 10/16/2010
  dmi.bios.release: 2.0
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 02UF
  dmi.board.name: R425D/R525D
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr02UF:bd10/16/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425D/R525D:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425D/R525D:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:sku:
  dmi.product.name: R425D/R525D
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Kernel-packages] [Bug 1992118] Re: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel

[Jian Hui Lee]

verified linux-firmware 1.187.34 on focal 5.15-0-1016-intel-iotg and the
issue is gone.

** Tags added: verification-done-focal

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

Title:
  AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15
  intel IoTG kernel

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  AX210 (8086:e024) WLAN init failed ucode -5  after upgrading to 5.15 Intel 
IoTG kernel.

  [Steps to reproduce]
  $ sudo apt update
  $ sudo apt upgrade
  $ reboot

  [Expected result]
  WLAN works with no problem.

  [Actual result]
  Can't detect WLAN.

  [Failure rate]
  100%

  [Other Info]
  [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002)
  [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported 
by driver
  [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
0.63.2.2
  [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode op_mode iwlmvm
  [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
  [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000
  [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 
0x0.
  [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6
  [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode
  [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0
  [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1
  [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2
  [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1
  [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2
  [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1
  [4.812520] iwlwifi :02:00.0: 0x0010 | data2
  [4.812523] iwlwifi :02:00.0: 0x | data3
  [4.812527] iwlwifi :02:00.0: 0x | beacon time
  [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low
  [4.812533] iwlwifi :02:00.0: 0x | tsf hi
  [4.812536] iwlwifi :02:00.0: 0x | time gp1
  [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2
  [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type
  [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major
  [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor
  [4.812553] iwlwifi :02:00.0: 0x0420 | hw version
  [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version
  [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd
  [4.812563] iwlwifi :02:00.0: 0x0002 | isr0
  [4.812566] iwlwifi :02:00.0: 0x6000 | isr1
  [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2
  [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3
  [4.812575] iwlwifi :02:00.0: 0x | isr4
  [4.812578] iwlwifi :02:00.0: 0x | last cmd Id
  [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event
  [4.812584] iwlwifi :02:00.0: 0x | l2p_control
  [4.812588] iwlwifi :02:00.0: 0x | l2p_duration
  [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid
  [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match
  [4.812597] iwlwifi :02:00.0: 0x0009 | lmpm_pmg_sel
  [4.812600] iwlwifi :02:00.0: 0x | timestamp
  [4.812603] iwlwifi :02:00.0: 0x0024 | flow_handler
  [4.812640] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [4.812643] iwlwifi :02:00.0: Transport status: 0x004A, valid: 7
  [4.812647] iwlwifi :02:00.0: 0x2010070D | ADVANCED_SYSASSERT
  [4.812651] iwlwifi :02:00.0: 0x | umac branchlink1
  [4.812654] iwlwifi :02:00.0: 0x8045DFC6 | umac branchlink2
  [4.812658] iwlwifi :02:00.0: 0x010910FE | umac interruptlink1
  [4.812661] iwlwifi :02:00.0: 0x | umac interruptlink2
  [4.812664] iwlwifi :02:00.0: 0x0005 | umac data1
  [4.812667] iwlwifi :02:00.0: 0xDEADBEEF | umac data2
  [4.812670] iwlwifi :02:00.0: 0xDEADBEEF | umac data3
  [4.812673] iwlwifi :02:00.0: 0x0042 | umac major
  [4.812677] iwlwifi :02:00.0: 0xF1C864E0 | umac minor
  [4.812680] iwlwifi :02:00.0: 0x000244D8 | frame pointer
  [4.812683] iwlwifi :02:00.0: 0xC0885E88 | stack pointer
  [4.812686] iwlwifi :02:00.0: 0x00010C00 | last host cmd
  [4.812689] iwlwifi :02:00.0: 

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

[John Rose]

I've tried the solution for the 7265 chip at 
https://bugzilla.kernel.org/show_bug.cgi?id=207409
i.e. using sudo, create a file /etc/modprobe.d/wifihacks
admin@Server:~$ cat /etc/modprobe.d/wifihacks.conf
options iwlwifi swcrypt=0
options iwlwifi power_save=0
options iwlmvm power_scheme=1
options iwlwifi uapsd_disable=1 
followed by a reboot
But that didn't work

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU

[koba]

** Description changed:

  [Impact]
   * thermald prematurely throttling GPU
  
  [Test Plan]
  Test1,
   * Run game on the target machine.
-  * the FPS must not be throttled below 20FPS.
+  * the FPS must not be significantly reduced.
  Test2,
-  * Run on others platform, e.g. TGL/CML.
-  * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.
+  * Run on others platform, e.g. TGL/CML.
+  * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.
  
  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.
  
  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes
  
  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C
  
  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop
  
  But more importantly I was given no indication this was happening. I had
  to sleuth it out myself.
  
  Perhaps it is impossible to determine good defaults for all hardware, I
  don't know. However without an indication that this is happening there
  will be a lot of people with a mysteriously broken experience. This was
  extremely difficult for me to find and I had several friend who are
  experts on linux gaming and video drivers trying to track this down. I
  discovered it by luck and perseverance.
  
  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a conservative
  default if at all possible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

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

Title:
  thermald prematurely throttling GPU

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be significantly reduced.
  Test2,
   * Run on others platform, e.g. TGL/CML.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  

[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Arif Ali]

The kernel was tested on 2 instances below is my testing transcript

1. Enable proposed on one of the VMs
2. Install linux-image-generic, which installed kernel 5.4.0-132.148 
3. Rebooted the node, and was able to set the IP, and ping another VM
4. Set the MTU to 9000, and was still able to ping the other VM
5. On the second VM, changed the MTU 9000 (this still had old kernel), and the 
ping stopped. The error in  dmesg was there as per the first comment
5. Upgraded the kernel on the second VM from proposed, and rebooted the VM
6. Ping started, when the second VM came up
7. Set the MTU to 9000, and the ping still continued

The same steps were repeated with setting the MTU in netplan, and we didn't 
have any issues
We also tested an MTU of 1550, to go outside of the standard 1500 and 9000, and 
we didn't see any issues either


** Tags added: verification-done-focal

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1983656

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start 

[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU

[Colette Kerr]

Hmm, I think that when i said that it throttled below 20 fps it was
mistaken for some sort of par or expectation. That was meant to show the
extent of the throttling I was experiencing not setting an expectation

Might want to change this line:
* the FPS must not be throttled below 20FPS.

To something more like:
* the FPS must not be significantly reduced 

Or however you think best to phrase the idea that unless the cooling
system can't keep up with the load that performance shouldn't be
noticeably impacted

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

Title:
  thermald prematurely throttling GPU

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be throttled below 20FPS.
  Test2,
   * Run on others platform, e.g. TGL/CML.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

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


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

[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property

[lirel]

** Tags removed: jammy
** Tags added: kinetic

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU

[koba]

@Chris, 
I ran thermald 2.5.1 on others platform. e.g. CML/TGL.


** Description changed:

  [Impact]
-  * thermald prematurely throttling GPU
+  * thermald prematurely throttling GPU
  
  [Test Plan]
-  * Run game on the target machine.
-  * the FPS must not be throttled below 20FPS.
+ Test1,
+  * Run game on the target machine.
+  * the FPS must not be throttled below 20FPS.
+ Test2,
+  * Run on others platform, e.g. TGL/CML.
+  * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.
  
  [Where problems could occur]
-  * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.
+  * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.
  
  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes
  
  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C
  
  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop
  
  But more importantly I was given no indication this was happening. I had
  to sleuth it out myself.
  
  Perhaps it is impossible to determine good defaults for all hardware, I
  don't know. However without an indication that this is happening there
  will be a lot of people with a mysteriously broken experience. This was
  extremely difficult for me to find and I had several friend who are
  experts on linux gaming and video drivers trying to track this down. I
  discovered it by luck and perseverance.
  
  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a conservative
  default if at all possible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

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

Title:
  thermald prematurely throttling GPU

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be throttled below 20FPS.
  Test2,
   * Run on others platform, e.g. TGL/CML.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

[John Rose]

I've tried the solution for the 7265 chip at 
https://bugzilla.kernel.org/show_bug.cgi?id=207409
i.e. using sudo, create a file /etc/modprobe.d/wifihacks
admin@Server:~$ cat /etc/modprobe.d/wifihacks.conf
options iwlwifi swcrypt=0
options iwlwifi power_save=0
options iwlmvm power_scheme=1
options iwlwifi uapsd_disable=1 
followed by a reboot
But that didn't work

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

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

[lirel]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1994126/+attachment/5626657/+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/1994126

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1994126] PulseList.txt

[lirel]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1994126/+attachment/5626653/+files/PulseList.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/1994126

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1994126] RfKill.txt

[lirel]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1994126/+attachment/5626654/+files/RfKill.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/1994126

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1994126] ProcEnviron.txt

[lirel]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1994126/+attachment/5626650/+files/ProcEnviron.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/1994126

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1994126] Lsusb.txt

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property

[lirel]

I could not run the specified command running the affected kernel because its 
an kernel panic.
I could still run the command from an ubuntu 22.04 if logs about the hardware 
are interesting?

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

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

[lirel]

apport information

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1994126] CRDA.txt

[lirel]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1994126/+attachment/5626639/+files/CRDA.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/1994126

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property

[lirel]

apport information

** Tags added: apport-collected jammy

** Description changed:

  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot
  
  backtrace via OCR from picture of kernel panic:
  
  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.
  
  Started Refresh fuupd metadate regularly. Started Daily rotation of
  log files.
  
  Started Daily man-db regeneration.
  
  Started Message of the Day.
  
  Started Daily Cleanup of Temporary Directories.
  
  Started Ubuntu Advantage Timer for running repeated jobs.
  
  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.
  
  1 Listening on CUPS Scheduler.
  
  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...
  
  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.
  
  Reached target Socket Units. 1 Reached target Basic System.
  
  20.300662) BUG: Kernel NULL pointer dereference, address:
  
  
  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page
  
  20.302458) PGD O P40 0
  
  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)
  
  CPU: 4 PID: 1 Comm: systemd Tainted: P
  
  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022
  
  20.304190)
  
  20.304774) RIP: 0010:0N0
  
  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202
  
  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800
  
  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0
  
  20.308627) R10:  R11:  R12:
  00
  
  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288
  
  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033
  
  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0
  
  20.312241) Call Trace:
  
  20.312992) https://bugs.launchpad.net/bugs/1994126/+attachment/5626638/+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/1994126

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 

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

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions


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

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

[John Rose]

I should have mentioned that the idea for the above fix originated at 
https://bugzilla.kernel.org/show_bug.cgi?id=207409

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

[John Rose]

I've tried a suggestion from https://ubuntuforums.org/showthread.php?t=2480193 
but after rebooting that didn't get wthe wifi working:
echo 'options iwlwifi power_save=0 uapsd_disable=0' | sudo tee -a 
/etc/modprobe.d/wifihacks.conf
echo 'options iwlmvm power_scheme=1' | sudo tee -a 
/etc/modprobe.d/wifihacks.conf

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

[kruisoc]

maybe unrelated to your issue, but my touchpad stopped working properly
after using a GRUB theme installation script, on a Clevo NV41MZ, Ubuntu
18 to 22

what solved the issue for me was updating the /etc/default/grub file by 
changing this line :
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_os_name=Linux acpi_osi="
to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

(then use sudo update-grub, then 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/1722478

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property

[lirel]

** Attachment added: "only log on "writable" containing bytes"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+attachment/5626633/+files/casper.log

** Description changed:

- Ubuntu 22.10 final realease boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
+ Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot
  
  backtrace via OCR from picture of kernel panic:
  
+ Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
+ Discard unused blocks once a week.
  
- Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
- Discard unused blocks once a week.
- 
- Started Refresh fuupd metadate regularly. Started Daily rotation of
+ Started Refresh fuupd metadate regularly. Started Daily rotation of
  log files.
  
- Started Daily man-db regeneration.
+ Started Daily man-db regeneration.
  
- Started Message of the Day.
+ Started Message of the Day.
  
- Started Daily Cleanup of Temporary Directories.
+ Started Daily Cleanup of Temporary Directories.
  
- Started Ubuntu Advantage Timer for running repeated jobs.
+ Started Ubuntu Advantage Timer for running repeated jobs.
  
- Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
- Socket.
+ Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
+ Socket.
  
- 1 Listening on CUPS Scheduler.
+ 1 Listening on CUPS Scheduler.
  
- 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
- for snappy deeson...
+ 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
+ for snappy deeson...
  
- Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
- for snappy daemon.
+ Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
+ for snappy daemon.
  
- Reached target Socket Units. 1 Reached target Basic System.
+ Reached target Socket Units. 1 Reached target Basic System.
  
- 20.300662) BUG: Kernel NULL pointer dereference, address:
+ 20.300662) BUG: Kernel NULL pointer dereference, address:
  
  
- 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
- error code (0x0010) - not-present page
+ 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
+ error code (0x0010) - not-present page
  
- 20.302458) PGD O P40 0
+ 20.302458) PGD O P40 0
  
- 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)
+ 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)
  
- CPU: 4 PID: 1 Comm: systemd Tainted: P
+ CPU: 4 PID: 1 Comm: systemd Tainted: P
  
- 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
- BIOS N24ET7ON (1.45) 07/22/2022
+ 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
+ BIOS N24ET7ON (1.45) 07/22/2022
  
- 20.304190)
+ 20.304190)
  
- 20.304774) RIP: 0010:0N0
+ 20.304774) RIP: 0010:0N0
  
- 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
- 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202
+ 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
+ 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202
  
- 20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
- 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800
+ 20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
+ 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800
  
- 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
+ 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0
  
- 20.308627) R10:  R11:  R12:
+ 20.308627) R10:  R11:  R12:
  00
  
- 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
+ 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288
  
- 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
- 20.310762) CS: 0010 DS:  ES:  CRO: 80050033
+ 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
+ 20.310762) CS: 0010 DS:  ES:  CRO: 80050033
  
- 20.311491) CR2:  fffds CRS: 00011eida002 CR4:
+ 20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0
  
- 20.312241) Call Trace:
+ 20.312241) Call Trace:
  
- 20.312992) https://bugs.launchpad.net/bugs/1994126

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing 

[Kernel-packages] [Bug 1994126] [NEW] NULL pointer dereference in power_supply_get_property

[lirel]

Public bug reported:

Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 (containing 
nvidia gpu)
reproducible kernel panic during boot

backtrace via OCR from picture of kernel panic:

Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
Discard unused blocks once a week.

Started Refresh fuupd metadate regularly. Started Daily rotation of
log files.

Started Daily man-db regeneration.

Started Message of the Day.

Started Daily Cleanup of Temporary Directories.

Started Ubuntu Advantage Timer for running repeated jobs.

Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
Socket.

1 Listening on CUPS Scheduler.

1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
for snappy deeson...

Listening on UUID deemon activation socket. 1 Listening on Socket activation
for snappy daemon.

Reached target Socket Units. 1 Reached target Basic System.

20.300662) BUG: Kernel NULL pointer dereference, address:


20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 WPF:
error code (0x0010) - not-present page

20.302458) PGD O P40 0

20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

CPU: 4 PID: 1 Comm: systemd Tainted: P

0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 20L5000BGE/20L5000BGE,
BIOS N24ET7ON (1.45) 07/22/2022

20.304190)

20.304774) RIP: 0010:0N0

20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

20.3066231 RAX:  RBX: 95538288 RCX: 8c43c1d89800
20.307282) RDX: b17180087cdo RSI: 0004 RDI: 8c43c1d89800

20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
0

20.308627) R10:  R11:  R12:
00

20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
9553a288

20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
20.310762) CS: 0010 DS:  ES:  CRO: 80050033

20.311491) CR2:  fffds CRS: 00011eida002 CR4:
003706e0

20.312241) Call Trace:

20.312992) https://bugs.launchpad.net/bugs/1994126/+attachment/5626632/+files/ubuntu-22.10-live-thinkpadT480-20221025_091343.jpg

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  

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

Title:
  Gnome desktop freezes after reboot or resume after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a reboot or resuming from sleep, the desktop appears and is
  fully functional for about 20 seconds. Then the desktop freezes, the
  fan spins up but the mouse still moves. Now click around, open
  programs, execute  to switch programs does nothing. The
  system stays this way for 60 seconds. Then the desktop becomes
  responsive again and all click and keystrokes executed during this
  time are executed. After that the system stays responsive and normal.
  The system log fills up with the following lines (many of them) during
  this period, pointing at a gnome javascript / message queue issue :

  ```
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-23-generic 5.19.0-23.24
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2224 F wireplumber
   /dev/snd/controlC1:  robert 2224 F wireplumber
   /dev/snd/seq:robert 2221 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 09:49:23 2022
  InstallationDate: Installed on 2022-10-23 (1 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC
   Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote 
Control
   Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 
2009" quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1988429] Re: support linux-oem-6.0

[Timo Aaltonen]

reopening, as the current version doesn't build against 6.0

** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy)
   Status: Fix Released => Triaged

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

Title:
  support linux-oem-6.0

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-510 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Triaged

Bug description:
  [Impact]

  Building nvidia dkms against linux 6.0 fails.

  The compat code needs updates to support 6.0.

  [Test case]

  Check that it builds after fixes applied.

  [What could go wrong]

  The compat code changes affect only builds on 6.0, so there's no
  chance of it breaking build for other kernels.

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


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

[Kernel-packages] [Bug 1994125] [NEW] Gnome desktop freezes after reboot or resume after sleep

[Robert]

Public bug reported:

After a reboot or resuming from sleep, the desktop appears and is fully
functional for about 20 seconds. Then the desktop freezes, the fan spins
up but the mouse still moves. Now click around, open programs, execute
 to switch programs does nothing. The system stays this way
for 60 seconds. Then the desktop becomes responsive again and all click
and keystrokes executed during this time are executed. After that the
system stays responsive and normal. The system log fills up with the
following lines (many of them) during this period, pointing at a gnome
javascript / message queue issue :

```
Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy 
signals connected, but can also be cau
sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
and the JS callback not invoked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy 
signals connected, but can also be cau
sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
and the JS callback not invoked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
```

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-23-generic 5.19.0-23.24
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  robert 2224 F wireplumber
 /dev/snd/controlC1:  robert 2224 F wireplumber
 /dev/snd/seq:robert 2221 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 25 09:49:23 2022
InstallationDate: Installed on 2022-10-23 (1 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC
 Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote 
Control
 Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 
2009" quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-23-generic N/A
 linux-backports-modules-5.19.0-23-generic  N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2018
dmi.bios.release: 1.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16Q2IMS.10E
dmi.board.asset.tag: Default string
dmi.board.name: MS-16Q2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A

[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU

[Jay Chen]

just to add on the wish list- Oasis platform can be the pilot carrying thermald 
2.5.1 forward. 
for this goal we need to have thermald 2.5.1 package reach -proposed at least, 
by 28-Oct

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

Title:
  thermald prematurely throttling GPU

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
   * Run game on the target machine.
   * the FPS must not be throttled below 20FPS.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

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


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

[Kernel-packages] [Bug 1992118] Re: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel

[Jason Yen]

Checked with the customer who impacted by this regression. They
confirmed the fix in proposed channel.

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

Title:
  AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15
  intel IoTG kernel

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  AX210 (8086:e024) WLAN init failed ucode -5  after upgrading to 5.15 Intel 
IoTG kernel.

  [Steps to reproduce]
  $ sudo apt update
  $ sudo apt upgrade
  $ reboot

  [Expected result]
  WLAN works with no problem.

  [Actual result]
  Can't detect WLAN.

  [Failure rate]
  100%

  [Other Info]
  [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002)
  [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported 
by driver
  [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
0.63.2.2
  [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode op_mode iwlmvm
  [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
  [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000
  [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 
0x0.
  [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6
  [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode
  [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0
  [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1
  [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2
  [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1
  [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2
  [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1
  [4.812520] iwlwifi :02:00.0: 0x0010 | data2
  [4.812523] iwlwifi :02:00.0: 0x | data3
  [4.812527] iwlwifi :02:00.0: 0x | beacon time
  [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low
  [4.812533] iwlwifi :02:00.0: 0x | tsf hi
  [4.812536] iwlwifi :02:00.0: 0x | time gp1
  [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2
  [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type
  [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major
  [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor
  [4.812553] iwlwifi :02:00.0: 0x0420 | hw version
  [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version
  [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd
  [4.812563] iwlwifi :02:00.0: 0x0002 | isr0
  [4.812566] iwlwifi :02:00.0: 0x6000 | isr1
  [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2
  [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3
  [4.812575] iwlwifi :02:00.0: 0x | isr4
  [4.812578] iwlwifi :02:00.0: 0x | last cmd Id
  [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event
  [4.812584] iwlwifi :02:00.0: 0x | l2p_control
  [4.812588] iwlwifi :02:00.0: 0x | l2p_duration
  [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid
  [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match
  [4.812597] iwlwifi :02:00.0: 0x0009 | lmpm_pmg_sel
  [4.812600] iwlwifi :02:00.0: 0x | timestamp
  [4.812603] iwlwifi :02:00.0: 0x0024 | flow_handler
  [4.812640] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [4.812643] iwlwifi :02:00.0: Transport status: 0x004A, valid: 7
  [4.812647] iwlwifi :02:00.0: 0x2010070D | ADVANCED_SYSASSERT
  [4.812651] iwlwifi :02:00.0: 0x | umac branchlink1
  [4.812654] iwlwifi :02:00.0: 0x8045DFC6 | umac branchlink2
  [4.812658] iwlwifi :02:00.0: 0x010910FE | umac interruptlink1
  [4.812661] iwlwifi :02:00.0: 0x | umac interruptlink2
  [4.812664] iwlwifi :02:00.0: 0x0005 | umac data1
  [4.812667] iwlwifi :02:00.0: 0xDEADBEEF | umac data2
  [4.812670] iwlwifi :02:00.0: 0xDEADBEEF | umac data3
  [4.812673] iwlwifi :02:00.0: 0x0042 | umac major
  [4.812677] iwlwifi :02:00.0: 0xF1C864E0 | umac minor
  [4.812680] iwlwifi :02:00.0: 0x000244D8 | frame pointer
  [4.812683] iwlwifi :02:00.0: 0xC0885E88 | stack pointer
  [4.812686] iwlwifi :02:00.0: 0x00010C00 | last host cmd
  [4.812689] iwlwifi :02:00.0: 0x | isr status 

[Kernel-packages] [Bug 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"

[Johnsandman]

Same problem after the update in 22.04 of 5.17.0-1020.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/1979633

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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


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

[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

[Andrea Righi]

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

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

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant kernel: [  281.052899]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Oct 21 20:41:38 tyrant kernel: [  281.052902]  ? __x64_sys_kcmp+0x1f/0x30
  Oct 21 20:41:38 tyrant kernel: [  281.052905]  ? do_syscall_64+0x67/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052908]  ? 
sysvec_apic_timer_interrupt+0x4b/0xd0
  Oct 21 20:41:38 tyrant kernel: [  281.052911]  
entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Oct 21 20:41:38 tyrant kernel: [  281.052915] RIP: 0033:0x7f5540712d8f
  Oct 21 20:41:38 tyrant kernel: [  281.052919] Code: 00 48 89 44 24 18 31 c0 
48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 

[Kernel-packages] [Bug 1992435] Re: sof-hda-dsp Dmic0 not initial correctly

[Launchpad Bug Tracker]

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

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

  * Backport patch to fix sof-hda-dsp Dmic0 initial. (LP: #1992435)

 -- Dirk Su   Tue, 11 Oct 2022 16:09:17 +0800

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

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

Title:
  sof-hda-dsp Dmic0 not initial correctly

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

Bug description:
  [Impact]
  Device use sof-hda-dsp driver will not able to initial the Dmic0 status 
correctly

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Dmic should be on and volume set to 70%

  [Where problems could occur]
  Only fix for Dmic0 control and upstream already merged the code. The risk 
will be low

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/132

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


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

[Kernel-packages] [Bug 1992435] Update Released

[Chris Halse Rogers]

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

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

Title:
  sof-hda-dsp Dmic0 not initial correctly

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

Bug description:
  [Impact]
  Device use sof-hda-dsp driver will not able to initial the Dmic0 status 
correctly

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Dmic should be on and volume set to 70%

  [Where problems could occur]
  Only fix for Dmic0 control and upstream already merged the code. The risk 
will be low

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/132

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


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