date:20220920

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1017.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-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-allwinner-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1953613

Title:
  GPIO character device v1 API not enabled in kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux-allwinner-5.17 package in Ubuntu:
  Invalid
Status in linux-hwe-5.17 package in Ubuntu:
  Invalid
Status in linux-starfive-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-allwinner-5.17 source package in Jammy:
  Fix Released
Status in linux-hwe-5.17 source package in Jammy:
  Fix Committed
Status in linux-starfive-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * The libgpiod2 library and gpiod tools shipped in Jammy don't work.

   * These tools are meant to replace the old sysfs interface and be
 a better and more efficient way to manipulate GPIOs from userspace.
 Unfortunately the latest release is still using v1 of the character
 device kernel API which is not enabled in Ubuntu kernels.

   * This is Kent Gibsons reply on the linux-gpio mailing list:

  On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote:
  > Hi,
  >
  > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the
  > libgpiod package that we ship is still based on the latest version
  > 1.6.3 which does not implement the API v2. So I'd like to update
  > libgpiod, do you have any recommendations about what branch/sha1 I
  > should use? Do you plan to make a release that implements the API v2?
  >

  Firstly, libgpiod is Bart's library so he is the authority, but this
  is my understanding...

  TLDR: You should keep GPIO_CDEV_V1 enabled.

  v1 is deprecated from a development perspective, so all new feature
  development will occur on v2, and new applications should target v2.
  Existing apps targetting v1, be that directly or via libgpiod v1.6.3,
  will require GPIO_CDEV_V1 until they migrate to v2.
  The mainline kernel will continue to support v1 while userspace
  transitions.

  libgpiod v2 is in active development, and should reach its first release
  shortly.
  Note that it is NOT a plugin replacement for v1. It has a different API,
  for similar reasons to why we had to switch in the kernel, so apps will
  need to be actively migrated.

  I wouldn't suggest making any effort to package libgpiod v2 until Bart
  makes an official release.

  Cheers,
  Kent.

  [Test Plan]

   * Run gpioinfo on a machine with exposed GPIOs and check that it lists
 the GPIOs and doesn't error with

 gpioinfo: error creating line iterator: Invalid argument

  [Where problems could occur]

   * There may be code and scripts that hasn't been tested with a working
 libgpiod2/gpiod tools and uncover latent bugs.

  [Other Info]

  Original bug text:

  The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1)
  use version 1 of the GPIO character device API. However, they cannot
  work because the interface is disabled in the default kernel (tested
  with 5.13.19). After rebuilding the kernel with the option
  CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected.

  Thanks to Marek Szuba, who reported the same bug for Gentoo
  (https://bugs.gentoo.org/807334), pointing me in the right direction.

  What I expect to happen:

  $ gpiodetect
  gpiochip0 [0-003c] (8 lines)
  $ gpioinfo
  gpiochip0 - 8 lines:
   line   0:  unnamed   unused  output  active-high
   line   1:  unnamed   unused  output  active-high
   line   2:  unnamed   unused  output  active-high
   line   3:  unnamed   unused  output  active-high
   line   4:  unnamed   unused  output  active-high
   line   5:  unnamed   unused  output  active-high
   line   6:  unnamed   unused   input  active-high
   line   7:  unnamed   unused   input  active-high
  $ gpioget gpiochip0 0
  1

  What actually happens:

  $ gpiodetect
  gpiochip0 [0-003c] (8 lines)
  $ gpioinfo
  gpioinfo: error creating line iterator: Invalid argument
  $ gpioget gpiochip0 0
  gpioget: error reading GPIO values: Invalid argument

  $ cat /proc/version_signature
  Ubuntu 5.13.0-22.22-lowlatency 5.13.19

  $ apt-cache policy libgpiod2
  libgpiod2:
    Installed: 1.6.2-1
    Candidate: 1.6.2-1
    Vers

[Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device down at resuming from s2idle

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1017.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-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/1987312

Title:
  IWLMEI may cause device down at resuming from s2idle

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in backport-iwlwifi-dkms source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WiFi interfaces unsolicitedly down at resuming from s2idle.

  [Fix]

  Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN
  POR is only for Windows project design. Please remove or disable
  CONFIG_IWLMEI from Linux.

  [Test Case]

  Make sure iwlmei.ko is not built.

  [Where problems could occur]

  iwlmei was not enabled before 5.17 and was turned on automatically since
  then. This restores the state and shall not have impact on existing
  devices.

  == original bug report ==

  Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN
  POR is only for Windows project design. Please remove or disable
  CONFIG_IWLMEI from Linux.

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


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

[Kernel-packages] [Bug 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1017.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-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/1988721

Title:
  [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on
  AMD

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

Bug description:
  [Impact]
  There is no output of external 4k DP monitor via USB-C to DP dongle.

  [Fix]
  Isolate link training sequence, the external DP monitor will be good.

  [Test]
  Verified on hardware, external 4k monitor works fine after re-plugin and 
suspend.

  [Where problems could occur]
  It may break the display output on AMD GPU.

  This commit is from 5.18-rc1, and no issue on jammy kernel.
  SRU for oem-5.17 only.

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


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

[Kernel-packages] [Bug 1981069] Re: test_060_nx in ubuntu_qrt_kernel_security failed on B-gke-5.4 since 5.4.0-1071-gke

2022-09-20 Thread Steve Beattie

Sorry for the delay, I went ahead and merged the fix for this. Thanks!

** Changed in: qa-regression-testing
   Status: In Progress => Fix Released

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

** Changed in: linux-gke (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  test_060_nx in ubuntu_qrt_kernel_security failed on B-gke-5.4 since
  5.4.0-1071-gke

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  New
Status in linux-gke package in Ubuntu:
  Fix Released

Bug description:
  Test failed since 5.4.0-1071.76~18.04.3-gke AMD64 (works ok with
  5.4.0-1068-gke)

  $ sudo python2 ./test-kernel-security.py -v KernelSecurityTest.test_060_nx
  Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'5.4.0-1071.76~18.04.3 (Ubuntu 5.4.0-1071.76~18.04.3-gke 5.4.181)' arch: 
'amd64' uid: 0/0 SUDO_USER: 'google')
  test_060_nx (__main__.KernelSecurityTest)
  NX bit is working ... FAIL

  ==
  FAIL: test_060_nx (__main__.KernelSecurityTest)
  NX bit is working
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 575, in test_060_nx
  self.assertShellExitEquals(rie_expected, ["./nx-test-rie", "data"])
    File 
"/home/google/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1203, in assertShellExitEquals
  self.assertEqual(expected, rc, msg + result + report)
  AssertionError: Got exit code -11, expected 0
  Command: './nx-test-rie', 'data'
  Output:
  rodata:0x55f37cf22098
  data:  0x55f37d123010
  bss:   0x55f37d133040
  brk:   0x55f37edd7270
  rw:0x7f9b635da000
  rwx:   0x7f9b635d9000
  stack: 0x7ffd6cde4b90
  Dump of /proc/self/maps:
  55f37cf21000-55f37cf23000 r-xp  08:01 272969 
/home/google/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
  55f37d122000-55f37d123000 r--p 1000 08:01 272969 
/home/google/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
  55f37d123000-55f37d124000 rw-p 2000 08:01 272969 
/home/google/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie
  55f37d124000-55f37d134000 rw-p  00:00 0
  55f37edd6000-55f37edf7000 rw-p  00:00 0  
[heap]
  7f9b62fc1000-7f9b631a8000 r-xp  08:01 2245   
/lib/x86_64-linux-gnu/libc-2.27.so
  7f9b631a8000-7f9b633a8000 ---p 001e7000 08:01 2245   
/lib/x86_64-linux-gnu/libc-2.27.so
  7f9b633a8000-7f9b633ac000 r--p 001e7000 08:01 2245   
/lib/x86_64-linux-gnu/libc-2.27.so
  7f9b633ac000-7f9b633ae000 rw-p 001eb000 08:01 2245   
/lib/x86_64-linux-gnu/libc-2.27.so
  7f9b633ae000-7f9b633b2000 rw-p  00:00 0
  7f9b633b2000-7f9b633db000 r-xp  08:01 2240   
/lib/x86_64-linux-gnu/ld-2.27.so
  7f9b635cf000-7f9b635d1000 rw-p  00:00 0
  7f9b635d9000-7f9b635da000 rwxp  00:00 0
  7f9b635da000-7f9b635db000 rw-p  00:00 0
  7f9b635db000-7f9b635dc000 r--p 00029000 08:01 2240   
/lib/x86_64-linux-gnu/ld-2.27.so
  7f9b635dc000-7f9b635dd000 rw-p 0002a000 08:01 2240   
/lib/x86_64-linux-gnu/ld-2.27.so
  7f9b635dd000-7f9b635de000 rw-p  00:00 0
  7ffd6cdc6000-7ffd6cde7000 rwxp  00:00 0  
[stack]
  7ffd6cdfa000-7ffd6cdfd000 r--p  00:00 0  
[vvar]
  7ffd6cdfd000-7ffd6cdfe000 r-xp  00:00 0  
[vdso]
  ff60-ff601000 --xp  00:00 0  
[vsyscall]
  Attempting to execute function at 0x55f37d123010
  If this program seg-faults, the region was enforced as non-executable...

  --
  Ran 1 test in 0.880s

  FAILED (failures=1)

  Notet that this issue does not exist on B-gkeop-5.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1981069/+subscriptions


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

[Kernel-packages] [Bug 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1

Have upload logs in comment 2

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

Title:
  Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu
  22.04 and Ubuntu 22.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   SSD:931.51GB 7.2K SATA HDD   S471A08RSH20K04054  00LF039
   SSD*2(SATA 0/1):894.25GB SATA SSD
   HDD*2(SATA 2 alias tsata): 1TB SATA HDD
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

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


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

[Kernel-packages] [Bug 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part

2022-09-20 Thread Frank Heimes

Pull request was submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2022-September/thread.html#133371
changing status to 'In Progress'.

A test kernel was build on all major architectures in PPA and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1853306

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

** Changed in: linux (Ubuntu)
 Assignee: Frank Heimes (fheimes) => Canonical Kernel Team 
(canonical-kernel-team)

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

** Changed in: ubuntu-z-systems
   Status: New => In Progress

** Information type changed from Private to Public

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

Title:
  [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x -
  kernel part

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  The PCI Passthrough implementation is based on intercepting PCI I/O 
instructions which leads to a reduced I/O performance compared to execution of 
PCI instructions in LPAR. 
  For improved performance the interpretive execution of the PCI store and PCI 
load instructions get enabled. 
  Further improvement is achieved by enabling the Adapter-Event-Notification

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


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

[Kernel-packages] [Bug 1983741] Re: kernel crash and hung up while umounting xfs

2022-09-20 Thread hyz

kernel panic

** Attachment added: "kernel panic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983741/+attachment/5617607/+files/img1-1.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/1983741

Title:
  kernel crash and hung up while umounting xfs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  OS: Ubuntu 18.04.1
  Using XFS with Ceph rdb and mount by OverlayFS, sometimes system hung up with 
kernel crash like below:

  2022-07-27 16:17
  Jul 27 15:21:43 k8s-node-b01-17-05 kernel: [25666453.856553] VFS: Busy inodes 
after unmount of overlay. Self-destruct in 5 seconds.  Have a nice day...
  Jul 27 15:22:01 k8s-node-b01-17-05 kernel: [25666471.122435] XFS (rbd59): 
Unmounting Filesystem
  Jul 27 15:22:25 k8s-node-b01-17-05 kernel: [25666495.392431] BUG: Dentry 
d683c981{i=38c31f07,n=README_zh.md}  still in use (1) [unmount of xfs 
rbd23]

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


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

[Kernel-packages] [Bug 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1

** 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/1990342

Title:
  Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu
  22.04 and Ubuntu 22.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   SSD:931.51GB 7.2K SATA HDD   S471A08RSH20K04054  00LF039
   SSD*2(SATA 0/1):894.25GB SATA SSD
   HDD*2(SATA 2 alias tsata): 1TB SATA HDD
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

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


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

[Kernel-packages] [Bug 1983815] Status changed to Confirmed

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

Title:
  [ThinkPad T16 Gen 1] No detection of the HDMI monitor

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1:
  dmi.product.family: ThinkPad T16 Gen 1
  dmi.product.name: 21BVCTO1WW
  dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1
  dmi.product.version: ThinkPad T16 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

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 1990342

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

Title:
  Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu
  22.04 and Ubuntu 22.04.1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   SSD:931.51GB 7.2K SATA HDD   S471A08RSH20K04054  00LF039
   SSD*2(SATA 0/1):894.25GB SATA SSD
   HDD*2(SATA 2 alias tsata): 1TB SATA HDD
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

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


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

[Kernel-packages] [Bug 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1

** Description changed:

  Configuration:
-  
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
-  CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
-  BMC Version  0.48 (Build ID: ESX303K)
-  UEFI Version 0.62 (Build ID: ESE105G)
-  Drive 1  931.51GB 7.2K SATA HDD  S471A08RSH20K04054  00LF039 
-  Drive 12 894.25GB SATA SSD   14510638SSS7A43186  02JG559 
-  Drive 13 894.25GB SATA SSD   14510653SSS7A43186  02JG559
-  Boot mode:UEFI
+  
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
+  CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
+  BMC Version  0.48 (Build ID: ESX303K)
+  UEFI Version 0.62 (Build ID: ESE105G)
+  SSD:931.51GB 7.2K SATA HDD   S471A08RSH20K04054  00LF039
+  SSD*2(SATA 0/1):894.25GB SATA SSD
+   HDD*2(SATA 2 alias tsata): 1TB SATA HDD
+  Boot mode:UEFI
  Reproduce Steps:
-  1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
-  2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
-  3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
-  4.In the OS,the RAID of the tSATA group is not detected.
+  1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
+  2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
+  3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
+  4.In the OS,the RAID of the tSATA group is not detected.

** Description changed:

  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   SSD:931.51GB 7.2K SATA HDD   S471A08RSH20K04054  00LF039
   SSD*2(SATA 0/1):894.25GB SATA SSD
-   HDD*2(SATA 2 alias tsata): 1TB SATA HDD
+  HDD*2(SATA 2 alias tsata): 1TB SATA HDD
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

** Attachment added: "systemlog of 20.04.5"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990342/+attachment/5617589/+files/systemlog_20.04.5.zip

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

Title:
  Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu
  22.04 and Ubuntu 22.04.1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   SSD:931.51GB 7.2K SATA HDD   S471A08RSH20K04054  00LF039
   SSD*2(SATA 0/1):894.25GB SATA SSD
   HDD*2(SATA 2 alias tsata): 1TB SATA HDD
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

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


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

[Kernel-packages] [Bug 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.004.1

root@jam:~# lspci -s 00:19.0 -vvvnn
00:19.0 RAID bus controller [0104]: Intel Corporation Device [8086:282f] (rev 
11)
DeviceName: PCH Integrated SATA Controller 2
Subsystem: Lenovo Device [1d49:0116]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- https://bugs.launchpad.net/bugs/1990342

Title:
  Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu
  22.04 and Ubuntu 22.04.1

Status in linux package in Ubuntu:
  New

Bug description:
  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   Drive 1  931.51GB 7.2K SATA HDD  S471A08RSH20K04054  00LF039 
   Drive 12 894.25GB SATA SSD   14510638SSS7A43186  02JG559 
   Drive 13 894.25GB SATA SSD   14510653SSS7A43186  02JG559
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

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


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

[Kernel-packages] [Bug 1990342] [NEW] Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1

Public bug reported:

Configuration:
 
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
 CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
 BMC Version0.48 (Build ID: ESX303K)
 UEFI Version   0.62 (Build ID: ESE105G)
 Drive 1931.51GB 7.2K SATA HDD  S471A08RSH20K04054  00LF039 
 Drive 12   894.25GB SATA SSD   14510638SSS7A43186  02JG559 
 Drive 13   894.25GB SATA SSD   14510653SSS7A43186  02JG559
 Boot mode:UEFI
Reproduce Steps:
 1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set to 
"RAID",save and reboot.
 2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
 3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
 4.In the OS,the RAID of the tSATA group is not detected.

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

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

Title:
  Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu
  22.04 and Ubuntu 22.04.1

Status in linux package in Ubuntu:
  New

Bug description:
  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   Drive 1  931.51GB 7.2K SATA HDD  S471A08RSH20K04054  00LF039 
   Drive 12 894.25GB SATA SSD   14510638SSS7A43186  02JG559 
   Drive 13 894.25GB SATA SSD   14510653SSS7A43186  02JG559
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

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


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

[Kernel-packages] [Bug 1983815] Re: no detection of the hdmi display moinitor

** Bug watch removed: gitlab.freedesktop.org/drm/intel/-/issues #6401
   https://gitlab.freedesktop.org/drm/intel/-/issues/6401

** Summary changed:

- no detection of the hdmi display moinitor
+ [ThinkPad T16 Gen 1] No detection of the HDMI monitor

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

** Changed in: nvidia-graphics-drivers-515 (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/1983815

Title:
  [ThinkPad T16 Gen 1] No detection of the HDMI monitor

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1:
  dmi.product.family: ThinkPad T16 Gen 1
  dmi.product.name: 21BVCTO1WW
  dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1
  dmi.product.version: ThinkPad T16 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1983815] Re: no detection of the hdmi display moinitor

2022-09-20 Thread stkim

HDMI port is detected.

https://forums.lenovo.com/t5/Other-Linux-Discussions/Thinkpad-T16-can-t-
resume-from-suspend/m-p/5160642?page=7

$ fwupdmgr refresh
$ fwupdmgr update

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1:
  dmi.product.family: ThinkPad T16 Gen 1
  dmi.product.name: 21BVCTO1WW
  dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1
  dmi.product.version: ThinkPad T16 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

** Description changed:

  [Impact]
+ It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R) 
Silver N6005 @ 2.00GHz
  
  [Fix]
+ Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and 
found this below commit
+ 567511462387 mm/memcg: protect memcg_stock with a local_lock_t
+ For safty, I backported the series of the patch
+ https://www.spinics.net/lists/cgroups/msg31595.html
+ But I still can reproduce the issue after applied those patches on top of 
5.17 oem kernel.
+ So, I did a second round of bisecting and found below commit is required, too
+ a74c6c00b1cb mm/memremap: avoid calling kasan_remove_zero_shadow() for device 
private memory
  
  [Test]
+ Done the S3 test 400 times on the target and it's still working well.
  
  [Where problems could occur]
+ Hard to evaluate the impact, but from the overnight test, the memory usage is 
still low, so there should be no memory leakage, and can't find any fix patch 
for those applied commits from upstream and linux-next trees.
+ The patches are all from v5.18-rc1, so we only need them to be applied on 
oem-5.17 kernel, and will let QA to do thoroughly tests.

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

Title:
  System hang during S3 test

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

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

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

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

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

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


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

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

Public bug reported:

[Impact]

[Fix]

[Test]

[Where problems could occur]

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

** Affects: linux-oem-5.17 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

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

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

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

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

Title:
  System hang during S3 test

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

Bug description:
  [Impact]

  [Fix]

  [Test]

  [Where problems could occur]

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


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

[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15

2022-09-20 Thread Po-Hsu Lin

Thanks for the fix!
Tests restarted.

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  on Bionic 4.15

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  Issue found with Bionic 4.15.0-194.205

  Test failed with:

   Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
   
   ==
   FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 2976, in 
test_520_config_random_trust_cpu
   self.assertKernelConfig('RANDOM_TRUST_CPU', expected)   
 File "./test-kernel-security.py", line 233, in assertKernelConfig
   self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the 
kernel config
   
   --
   Ran 1 test in 0.003s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions


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

[Kernel-packages] [Bug 1990236] Re: 5.19.0-17.17: kernel NULL pointer dereference, address: 0000000000000084

2022-09-20 Thread Seth Arnold

** 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/1990236

Title:
  5.19.0-17.17: kernel NULL pointer dereference, address:
  0084

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up 
unexpectedly.
  Log inspection showed this:

  Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address: 
0084
  Sep 20 09:05:20 zeus kernel: #PF: supervisor read access in kernel mode
  Sep 20 09:05:20 zeus kernel: #PF: error_code(0x) - not-present page
  Sep 20 09:05:20 zeus kernel: PGD 0 P4D 0 
  Sep 20 09:05:20 zeus kernel: Oops:  [#1] PREEMPT SMP PTI
  Sep 20 09:05:20 zeus kernel: CPU: 6 PID: 4291 Comm: slack Tainted: P  
 OE 5.19.0-17-generic #17-Ubuntu
  Sep 20 09:05:20 zeus kernel: Hardware name: HP HP ZBook Studio G5/8427, BIOS 
Q71 Ver. 01.20.00 03/22/2022
  Sep 20 09:05:20 zeus kernel: RIP: 0010:unix_fs_perm.part.0+0x50/0x1e0
  Sep 20 09:05:20 zeus kernel: Code: 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8b 
81 08 03 00 00 89 75 8c 48 85 c0 0f 85 b0 00 00 00 48 8b 91 70 02 00 00 48 8d 
7d a0 <8b> 8a 84 00 00 00 0f b7 92 80 00 00 00 48 c7 45 9c 00 00 00 00 48
  Sep 20 09:05:20 zeus kernel: RSP: 0018:b014c7eb3ce0 EFLAGS: 00010246
  Sep 20 09:05:20 zeus kernel: RAX:  RBX: 94c0e0c7adb0 RCX: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: RDX:  RSI: 0004 RDI: 
b014c7eb3cf8
  Sep 20 09:05:20 zeus kernel: RBP: b014c7eb3d58 R08: 0002 R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11:  R12: 
0004
  Sep 20 09:05:20 zeus kernel: R13: 0002 R14: a044fe92 R15: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: FS:  7f6b47927c00() 
GS:94c47bd8() knlGS:
  Sep 20 09:05:20 zeus kernel: CS:  0010 DS:  ES:  CR0: 80050033
  Sep 20 09:05:20 zeus kernel: CR2: 0084 CR3: 00013e1b4003 CR4: 
003706e0
  Sep 20 09:05:20 zeus kernel: DR0:  DR1:  DR2: 

  Sep 20 09:05:20 zeus kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  Sep 20 09:05:20 zeus kernel: Call Trace:
  Sep 20 09:05:20 zeus kernel:  
  Sep 20 09:05:20 zeus kernel:  aa_unix_file_perm+0x2f2/0x400
  Sep 20 09:05:20 zeus kernel:  aa_sock_file_perm+0x5c/0x80
  Sep 20 09:05:20 zeus kernel:  aa_file_perm+0x288/0x2e0
  Sep 20 09:05:20 zeus kernel:  apparmor_file_permission+0x71/0x1a0
  Sep 20 09:05:20 zeus kernel:  security_file_permission+0x36/0x70
  Sep 20 09:05:20 zeus kernel:  rw_verify_area+0x35/0x80
  Sep 20 09:05:20 zeus kernel:  vfs_read+0x6c/0x1b0
  Sep 20 09:05:20 zeus kernel:  ksys_read+0xc9/0x100
  Sep 20 09:05:20 zeus kernel:  __x64_sys_read+0x19/0x30
  Sep 20 09:05:20 zeus kernel:  do_syscall_64+0x58/0x90
  Sep 20 09:05:20 zeus kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Sep 20 09:05:20 zeus kernel: RIP: 0033:0x7f6b46c68474
  Sep 20 09:05:20 zeus kernel: Code: 84 00 00 00 00 00 41 54 55 49 89 d4 53 48 
89 f5 89 fb 48 83 ec 10 e8 8b fc ff ff 4c 89 e2 41 89 c0 48 89 ee 89 df 31 c0 
0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 c7 fc ff ff 48
  Sep 20 09:05:20 zeus kernel: RSP: 002b:7ffc54391700 EFLAGS: 0246 
ORIG_RAX: 
  Sep 20 09:05:20 zeus kernel: RAX: ffda RBX: 0028 RCX: 
7f6b46c68474
  Sep 20 09:05:20 zeus kernel: RDX: 0008 RSI: 7ffc54391800 RDI: 
0028
  Sep 20 09:05:20 zeus kernel: RBP: 7ffc54391800 R08:  R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11: 0246 R12: 
0008
  Sep 20 09:05:20 zeus kernel: R13: 0028 R14: 7ffc54391800 R15: 


  I'll attach the full log.

  The presence apparmor in the trace correlates with the ton of permission 
problem that this kernel introduced (Chrome and Slack no longer starting, see 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064).
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2017-09-26 (1819 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  kinetic
  Uname: Linux 5.18.8-051808-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to kinetic on 2022-05-22 (120 days ago)
  UserGroups: cdrom dialout dip docker libvirt lpadmin lxd plugdev render 
sambashare src sudo tss tty uuc

[Kernel-packages] [Bug 1989258] Re: multiple kernel oops regarding hung tasks delaying boot

2022-09-20 Thread Brian Murray

We've worked around this in the autopackage test environment by
blacklisting the virtio_rng module, so I'm setting this task to Fix
Released.

** Changed in: auto-package-testing
   Status: New => Fix Released

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

Title:
  multiple kernel oops regarding hung tasks delaying boot

Status in Auto Package Testing:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kinetic amd64 instances in the autopkgtest environment are regularly
  experiencing a slow boot process due to a hung task timeout which
  happens multiple times.  The oops appears below:

  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.485373] INFO: task 
systemd-udevd:140 blocked for more than 1208 seconds.
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.487120]   Not 
tainted 5.19.0-15-generic #15-Ubuntu
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.490936] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.492717] 
task:systemd-udevd   state:D stack:0 pid:  140 ppid:   137 flags:0x4006
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.494612] Call Trace:
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.495202]  
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.495727]  
__schedule+0x23b/0x5c0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.496559]  ? 
sched_clock_cpu+0x12/0xf0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.497482]  
schedule+0x50/0xc0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.498237]  
schedule_preempt_disabled+0x15/0x30
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.499306]  
__mutex_lock.constprop.0+0x4e7/0x760
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.500409]  
__mutex_lock_slowpath+0x13/0x20
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.501420]  
mutex_lock+0x36/0x40
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.502211]  
add_early_randomness+0x1b/0xc0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.503178]  
hwrng_register+0x13e/0x1c0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.504068]  
virtrng_scan+0x19/0x30 [virtio_rng]
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.505152]  
virtio_dev_probe+0x1f9/0x2c0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.506096]  
really_probe+0x1d1/0x3a0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.506958]  
__driver_probe_device+0x11b/0x190
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.507993]  
driver_probe_device+0x24/0xd0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.508955]  
__driver_attach+0xd8/0x200
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.509859]  ? 
__device_attach_driver+0x120/0x120
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.510952]  
bus_for_each_dev+0x7c/0xc0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.511846]  
driver_attach+0x1e/0x30
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.512692]  
bus_add_driver+0x178/0x220
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.513597]  
driver_register+0x8f/0xf0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.514474]  ? 
0xc0282000
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.515257]  
register_virtio_driver+0x20/0x40
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.516277]  
virtio_rng_driver_init+0x15/0x1000 [virtio_rng]
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.517602]  
do_one_initcall+0x4a/0x210
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.518498]  ? 
kmem_cache_alloc_trace+0x181/0x300
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.519587]  ? 
do_init_module+0x27/0x200
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.520516]  
do_init_module+0x50/0x200
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.521403]  
load_module+0xb60/0xcb0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.522243]  
__do_sys_finit_module+0xbd/0x130
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.523255]  ? 
__do_sys_finit_module+0xbd/0x130
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.524312]  
__x64_sys_finit_module+0x18/0x20
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.525343]  
do_syscall_64+0x5b/0x80
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.526183]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.527287]  ? 
__x64_sys_mmap+0x33/0x50
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.528180]  ? 
do_syscall_64+0x67/0x80
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.529064]  ? 
exit_to_user_mode_prepare+0x30/0xa0
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.530182]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Sep  9 22:31:32 bdmurray-test-systemd kernel: [ 1330.531289]  ? 
__x6

[Kernel-packages] [Bug 1990318] Status changed to Confirmed

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

Title:
  iwlwifi causes kernel panic on resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After I suspend and resume my laptop, everything works fine for about
  60 seconds. From there, my system locks up and the kernel panics. I
  have narrowed down the kernel panic happen only when iwlwifi is
  loaded. Unloading iwlwifi prevents the kernel panic. I have tried
  installing backport-iwlwifi-dkms and confirmed that iwlmei.ko is now
  not loaded per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987312

  This report was generated via kdump.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaahh  2141 F wireplumber
   /dev/snd/seq:aaahh  2137 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep 20 18:03:21 2022
  InstallationDate: Installed on 2022-06-10 (102 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608)
  MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3400PA_K3400PA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=b4b8a8e0-4db7-4db5-87ef-acecd2aed677 ro quiet splash 
crashkernel=384M-:512M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X3400PA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X3400PA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3400PA.300:bd02/14/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3400PA_K3400PA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3400PA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: Vivobook_ASUSLaptop X3400PA_K3400PA
  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/1990318/+subscriptions


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

[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15

2022-09-20 Thread Steve Beattie

Applied Luke's patch to the qa-regression-testing repo:
https://git.launchpad.net/qa-regression-
testing/commit/?id=7fb27c11cc22f99ed39ebb7c04e62b3eccf3ab64 (with added
references to this bug report), thanks!

(We happily take merge requests via the above, but can take patches
however people submit them, via `git am` in this case.)

** Changed in: qa-regression-testing
   Status: New => Fix Released

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

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

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  on Bionic 4.15

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  Issue found with Bionic 4.15.0-194.205

  Test failed with:

   Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
   
   ==
   FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 2976, in 
test_520_config_random_trust_cpu
   self.assertKernelConfig('RANDOM_TRUST_CPU', expected)   
 File "./test-kernel-security.py", line 233, in assertKernelConfig
   self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the 
kernel config
   
   --
   Ran 1 test in 0.003s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions


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

[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15

2022-09-20 Thread Luke Nowakowski-Krijger

@alexmurray Submited merge request :) Thanks

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  on Bionic 4.15

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  Issue found with Bionic 4.15.0-194.205

  Test failed with:

   Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
   
   ==
   FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 2976, in 
test_520_config_random_trust_cpu
   self.assertKernelConfig('RANDOM_TRUST_CPU', expected)   
 File "./test-kernel-security.py", line 233, in assertKernelConfig
   self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the 
kernel config
   
   --
   Ran 1 test in 0.003s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions


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

[Kernel-packages] [Bug 1990318] Re: iwlwifi causes kernel panic on resume from suspend

2022-09-20 Thread Aaahh Ahh

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990318/+attachment/5617540/+files/dmesg.202209201802

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

Title:
  iwlwifi causes kernel panic on resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After I suspend and resume my laptop, everything works fine for about
  60 seconds. From there, my system locks up and the kernel panics. I
  have narrowed down the kernel panic happen only when iwlwifi is
  loaded. Unloading iwlwifi prevents the kernel panic. I have tried
  installing backport-iwlwifi-dkms and confirmed that iwlmei.ko is now
  not loaded per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987312

  This report was generated via kdump.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaahh  2141 F wireplumber
   /dev/snd/seq:aaahh  2137 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep 20 18:03:21 2022
  InstallationDate: Installed on 2022-06-10 (102 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608)
  MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3400PA_K3400PA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=b4b8a8e0-4db7-4db5-87ef-acecd2aed677 ro quiet splash 
crashkernel=384M-:512M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X3400PA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X3400PA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3400PA.300:bd02/14/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3400PA_K3400PA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3400PA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: Vivobook_ASUSLaptop X3400PA_K3400PA
  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/1990318/+subscriptions


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

[Kernel-packages] [Bug 1990318] [NEW] iwlwifi causes kernel panic on resume from suspend

2022-09-20 Thread Aaahh Ahh

Public bug reported:

After I suspend and resume my laptop, everything works fine for about 60
seconds. From there, my system locks up and the kernel panics. I have
narrowed down the kernel panic happen only when iwlwifi is loaded.
Unloading iwlwifi prevents the kernel panic. I have tried installing
backport-iwlwifi-dkms and confirmed that iwlmei.ko is now not loaded per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987312

This report was generated via kdump.

ProblemType: KernelCrash
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aaahh  2141 F wireplumber
 /dev/snd/seq:aaahh  2137 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Sep 20 18:03:21 2022
InstallationDate: Installed on 2022-06-10 (102 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608)
MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3400PA_K3400PA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=b4b8a8e0-4db7-4db5-87ef-acecd2aed677 ro quiet splash 
crashkernel=384M-:512M vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-15-generic N/A
 linux-backports-modules-5.19.0-15-generic  N/A
 linux-firmware 20220831.gitd3c92280-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: X3400PA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X3400PA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3400PA.300:bd02/14/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3400PA_K3400PA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3400PA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: Vivobook_ASUSLaptop X3400PA_K3400PA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-kernelcrash 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/1990318

Title:
  iwlwifi causes kernel panic on resume from suspend

Status in linux package in Ubuntu:
  New

Bug description:
  After I suspend and resume my laptop, everything works fine for about
  60 seconds. From there, my system locks up and the kernel panics. I
  have narrowed down the kernel panic happen only when iwlwifi is
  loaded. Unloading iwlwifi prevents the kernel panic. I have tried
  installing backport-iwlwifi-dkms and confirmed that iwlmei.ko is now
  not loaded per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987312

  This report was generated via kdump.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaahh  2141 F wireplumber
   /dev/snd/seq:aaahh  2137 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep 20 18:03:21 2022
  InstallationDate: Installed on 2022-06-10 (102 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608)
  MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3400PA_K3400PA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=b4b8a8e0-4db7-4db5-87ef-acecd2aed677 ro quiet splash 
crashkernel=384M-:512M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X3400PA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X3400PA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3400PA.300:bd02/14/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_AS

[Kernel-packages] [Bug 1918085] Re: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump

2022-09-20 Thread Aaahh Ahh

Also in 22.10

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

Title:
  Package linux-crashdump in 20.04 configures kernel cmdline crashkernel
  incorrectly causing lock-up on kernel dump

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Package linux-crashdump in 20.04 configures kernel cmdline crashkernel
  incorrectly causing lock-up on kernel dump.

  It is very simple to replicate. I was testing using QEmu
  virtualisation software, where I had QEmu running a 20.04 install
  within another 20.04 install.

  Within the virtualisation install, simply install the package 
"linux-crashdump":
  $ sudo apt install linux-crashdump

  Answering Yes and Yes to the two questions asked:

   || Configuring kexec-tools ||
   |   |
   |   |
   | If you choose this option, a system reboot will trigger a restart into a  |
   | kernel loaded by kexec instead of going through the full system boot  |
   | loader process.   |
   |   |
   | Should kexec-tools handle reboots (sysvinit only)?|
   |   |
   |  |
   |   |
   |---|

   || Configuring kdump-tools ||
   |   |
   |   |
   | If you choose this option, the kdump-tools mechanism will be enabled.  A  |
   | reboot is still required in order to enable the crashkernel kernel|
   | parameter.|
   |   |
   | Should kdump-tools be enabled be default? |
   |   |
   |  |
   |   |
   |---|

  Check the kernel command-line Grub configured by package install:
  $ cat /proc/cmdline 
  BOOT_IMAGE=/vmlinuz-5.4.0-66-lowlatency root=/dev/mapper/rootlvm-rootpart ro 
crashkernel=512M-:192M

  As you can see "crashkernel=512M-:192M" is definitely a syntax error.

  Furthermore, when I test with this default configuration by forcing a crash:
  Enable dump then reboot testing with the following command:
  sudo sysctl -w kernel.sysrq=1
  Once this is done, you must become root, as just using sudo will not be 
sufficient. As the root user, you will have to issue the command echo c > 
/proc/sysrq-trigger.

  Once the "echo c > /proc/sysrq-trigger" command is issued as root, the
  virtual host being tested locks-up at 100% CPU indefinitely. Forcing
  shutdown and reboot shows no crash file in /var/crash folder however I
  can only see files "kexec_cmd" and "kdump_lock".

  To manually fix this issue I changed to "crashkernel=512M-:192M" to 
"crashkernel=384M-:512M" by editing (i.e. make the small number/larger number 
order correct):
  $ sudo vim /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=384M-:512M"

  After reboot and retest of the forced crash commands, the kdump works and all 
the needed files are present after self-reboot:
  $ ls /var/crash/
  202103081345  kdump_lock  kexec_cmd  
linux-image-5.4.0-66-lowlatency-202103081345.crash
  $ ls /var/crash/202103081345/
  dmesg.202103081345  dump.202103081345

  In summary the problem is that the default kernel command-line
  configured by default "crashkernel=512M-:192M" is faulty in some way
  or other and causes the kernel to lock-up at 100% CPU indefinitely
  when kdump is triggered.

  This can be manually fixed giving a workaround but future user will
  suffer until the default installation configuration is fixed.

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


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

[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15

2022-09-20 Thread Alex Murray

@lukenow could you please submit it as a merge request for the QA
Regression Testing project in Launchpad? https://code.launchpad.net/qa-
regression-testing

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  on Bionic 4.15

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Issue found with Bionic 4.15.0-194.205

  Test failed with:

   Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
   
   ==
   FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 2976, in 
test_520_config_random_trust_cpu
   self.assertKernelConfig('RANDOM_TRUST_CPU', expected)   
 File "./test-kernel-security.py", line 233, in assertKernelConfig
   self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the 
kernel config
   
   --
   Ran 1 test in 0.003s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions


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

[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15

2022-09-20 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  on Bionic 4.15

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Issue found with Bionic 4.15.0-194.205

  Test failed with:

   Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
   
   ==
   FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 2976, in 
test_520_config_random_trust_cpu
   self.assertKernelConfig('RANDOM_TRUST_CPU', expected)   
 File "./test-kernel-security.py", line 233, in assertKernelConfig
   self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the 
kernel config
   
   --
   Ran 1 test in 0.003s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions


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

[Kernel-packages] [Bug 1990304] Re: package linux-generic-hwe-20.04 5.15.0.46.49~20.04.16 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2022-09-20 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

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

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

Title:
  package linux-generic-hwe-20.04 5.15.0.46.49~20.04.16 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

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

Bug description:
  ramiro@HP-s151nr:~$ lsb_release -rd
  Description:  Ubuntu 20.04.5 LTS
  Release:  20.04
  ramiro@HP-s151nr:~$ 

  
  ramiro@HP-s151nr:~$ sudo apt update
  [sudo] password for ramiro: 
  Hit:1 http://co.archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://security.ubuntu.com/ubuntu focal-security InRelease
  Hit:3 http://co.archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:4 http://co.archive.ubuntu.com/ubuntu focal-backports InRelease
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  9 packages can be upgraded. Run 'apt list --upgradable' to see them.
  ramiro@HP-s151nr:~$ sudo apt -f install
  ^Ziting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is 
held by process 3000 (apt)... 14s
  [1]+  Stopped sudo apt -f install
  ramiro@HP-s151nr:~$ dpkg --configure -a
  dpkg: error: requested operation requires superuser privilege
  ramiro@HP-s151nr:~$ sudo dpkg --configure -a
  dpkg: error: dpkg frontend lock is locked by another process
  ramiro@HP-s151nr:~$ sudo dpkg --configure -a
  dpkg: error: dpkg frontend lock is locked by another process
  ramiro@HP-s151nr:~$ sudo rm /var/lib/apt/lists/lock
  ramiro@HP-s151nr:~$ sudo rm /var/lib/dpkg/lock
  ramiro@HP-s151nr:~$ sudo rm /var/lib/dpkg/lock-front-end
  rm: cannot remove '/var/lib/dpkg/lock-front-end': No such file or directory
  ramiro@HP-s151nr:~$ sudo rm /var/cache/apt/archives/lock
  ramiro@HP-s151nr:~$ sudo dpkg --configure -a
  dpkg: error: dpkg frontend lock is locked by another process
  ramiro@HP-s151nr:~$ sudo apt clean
  ramiro@HP-s151nr:~$ sudo apt install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
  7 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up xxd (2:8.1.2269-1ubuntu5.9) ...
  Setting up vim-common (2:8.1.2269-1ubuntu5.9) ...
  Setting up libtiff5:amd64 (4.1.0+git191117-2ubuntu0.20.04.5) ...
  Setting up vim-tiny (2:8.1.2269-1ubuntu5.9) ...
  Setting up linux-image-5.15.0-48-generic (5.15.0-48.54~20.04.1) ...
  I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.15.0-46-generic
  I: /boot/vmlinuz is now a symlink to vmlinuz-5.15.0-48-generic
  I: /boot/initrd.img is now a symlink to initrd.img-5.15.0-48-generic
  Setting up linux-modules-extra-5.15.0-48-generic (5.15.0-48.54~20.04.1) ...
  Setting up linux-modules-5.15.0-48-generic (5.15.0-48.54~20.04.1) ...
  Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
  Processing triggers for mime-support (3.64ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
  Processing triggers for libc-bin (2.31-0ubuntu9.9) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for linux-image-5.15.0-48-generic (5.15.0-48.54~20.04.1) 
...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic
  /etc/kernel/postinst.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-5.15.0-48-generic
  Found initrd image: /boot/initrd.img-5.15.0-48-generic
  Found linux image: /boot/vmlinuz-5.15.0-46-generic
  Found initrd image: /boot/initrd.img-5.15.0-46-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  done
  ramiro@HP-s151nr:~$ sudo apt install synaptic
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libept1.6.0 libxapian3

[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15

2022-09-20 Thread Luke Nowakowski-Krijger

I attached a patch that updates the test case in qa-regression-testing,
do you know where I would submit this patch or who I would talk to?

** Patch added: 
"0001-test-kernel-security.py-Update-RANDOM_TRUST_CPU-test.patch"
   
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990090/+attachment/5617507/+files/0001-test-kernel-security.py-Update-RANDOM_TRUST_CPU-test.patch

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  on Bionic 4.15

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Issue found with Bionic 4.15.0-194.205

  Test failed with:

   Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
   
   ==
   FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 2976, in 
test_520_config_random_trust_cpu
   self.assertKernelConfig('RANDOM_TRUST_CPU', expected)   
 File "./test-kernel-security.py", line 233, in assertKernelConfig
   self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the 
kernel config
   
   --
   Ran 1 test in 0.003s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions


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

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

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 1990292

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

Title:
  Mistery memory usage in linux Kernel >= 5.14

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My hardware is SuperMicro X11SDV-8C-TP8F with Intel D-2146NT.
  I've tested this issue with:

  * Ubuntu 22.04 Kernel 5.15
  * Ubuntu 22.04 Kernel 5.17
  * Ubuntu 20.04 Kernel 5.15
  * Ubuntu 20.04 Kernel 5.14

  Using Ubuntu 20.04 with kernel 5.13 or lower will NOT trigger this
  issue.

  The issue is that I have high RAM usage from the server startup I
  cannot explain.

  At startup without any services active I have nearly 6GiB of RAM used:
  ```
  # free -m
 totalusedfree  shared  buff/cache   
available
  Mem:   1566359988936 155 728
9213
  Swap:  0   0   0
  ```

  Using ps the sum of RSS memory does not adds up: it shows less than 1GiB used:
  ```
  # ps aux | awk '{sum+=$6} END {print sum / 1024}'
  944.879
  ```

  This is the meminfo output
  ```
  cat /proc/meminfo 
  MemTotal:   16039044 kB
  MemFree: 8486372 kB
  MemAvailable:9607120 kB
  Buffers:   79440 kB
  Cached:  1300092 kB
  SwapCached:0 kB
  Active:   575856 kB
  Inactive:1141004 kB
  Active(anon):  24184 kB
  Inactive(anon):   369940 kB
  Active(file): 551672 kB
  Inactive(file):   771064 kB
  Unevictable:   27884 kB
  Mlocked:   27884 kB
  SwapTotal:   2097148 kB
  SwapFree:2097148 kB
  Dirty:36 kB
  Writeback: 0 kB
  AnonPages:365256 kB
  Mapped:   304856 kB
  Shmem: 50208 kB
  KReclaimable: 110308 kB
  Slab: 455680 kB
  SReclaimable: 110308 kB
  SUnreclaim:   345372 kB
  KernelStack:7664 kB
  PageTables: 6352 kB
  NFS_Unstable:  0 kB
  Bounce:0 kB
  WritebackTmp:  0 kB
  CommitLimit:10116668 kB
  Committed_AS:2497484 kB
  VmallocTotal:   34359738367 kB
  VmallocUsed:   31940 kB
  VmallocChunk:  0 kB
  Percpu:12800 kB
  HardwareCorrupted: 0 kB
  AnonHugePages:  4096 kB
  ShmemHugePages:0 kB
  ShmemPmdMapped:0 kB
  FileHugePages: 0 kB
  FilePmdMapped: 0 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  Hugetlb:   0 kB
  DirectMap4k:  315700 kB
  DirectMap2M:11919360 kB
  DirectMap1G: 6291456 kB
  ```
  And this is the `slabtop` header:
  ```
   Active / Total Objects (% used): 1095487 / 1172800 (93.4%)
   Active / Total Slabs (% used)  : 28258 / 28258 (100.0%)
   Active / Total Caches (% used) : 121 / 176 (68.8%)
   Active / Total Size (% used)   : 401911.16K / 415423.19K (96.7%)
   Minimum / Average / Maximum Object : 0.01K / 0.35K / 10.62K
  ```

  This is the `df -h` output:
  ```
  df -h
  Filesystem Size  Used Avail Use% Mounted on
  tmpfs  1.6G   50M  1.5G   4% /run
  /dev/mapper/ubuntu--vg-ubuntu--lv   14G  3.8G  9.0G  30% /
  tmpfs  7.7G   20K  7.7G   1% /dev/shm
  tmpfs  5.0M 0  5.0M   0% /run/lock
  /dev/sda2  2.0G  127M  1.7G   7% /boot
  /dev/mapper/vg0-var_log9.8G  127M  9.2G   2% /var/log
  /dev/mapper/vg0-tmp9.8G   68K  9.3G   1% /tmp
  /dev/mapper/vg0-var_tmp9.8G   96K  9.3G   1% /var/tmp
  /dev/mapper/vg0-var_lib_docker 1.7T   11G  1.6T   1% /var/lib/docker
  tmpfs  1.6G 0  1.6G   0% /run/user/2010
  tmpfs  1.6G 0  1.6G   0% /run/user/2023
  ```

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


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

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

2022-09-20 Thread Ubuntu SRU Bot

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

linux/4.15.0-194.205 (i386, amd64, s390x, ppc64el)


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/bionic/update_excuses.html#linux-meta

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1990292] Re: Mistery memory usage in linux Kernel >= 5.14

2022-09-20 Thread Paul White

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

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

Title:
  Mistery memory usage in linux Kernel >= 5.14

Status in linux package in Ubuntu:
  New

Bug description:
  My hardware is SuperMicro X11SDV-8C-TP8F with Intel D-2146NT.
  I've tested this issue with:

  * Ubuntu 22.04 Kernel 5.15
  * Ubuntu 22.04 Kernel 5.17
  * Ubuntu 20.04 Kernel 5.15
  * Ubuntu 20.04 Kernel 5.14

  Using Ubuntu 20.04 with kernel 5.13 or lower will NOT trigger this
  issue.

  The issue is that I have high RAM usage from the server startup I
  cannot explain.

  At startup without any services active I have nearly 6GiB of RAM used:
  ```
  # free -m
 totalusedfree  shared  buff/cache   
available
  Mem:   1566359988936 155 728
9213
  Swap:  0   0   0
  ```

  Using ps the sum of RSS memory does not adds up: it shows less than 1GiB used:
  ```
  # ps aux | awk '{sum+=$6} END {print sum / 1024}'
  944.879
  ```

  This is the meminfo output
  ```
  cat /proc/meminfo 
  MemTotal:   16039044 kB
  MemFree: 8486372 kB
  MemAvailable:9607120 kB
  Buffers:   79440 kB
  Cached:  1300092 kB
  SwapCached:0 kB
  Active:   575856 kB
  Inactive:1141004 kB
  Active(anon):  24184 kB
  Inactive(anon):   369940 kB
  Active(file): 551672 kB
  Inactive(file):   771064 kB
  Unevictable:   27884 kB
  Mlocked:   27884 kB
  SwapTotal:   2097148 kB
  SwapFree:2097148 kB
  Dirty:36 kB
  Writeback: 0 kB
  AnonPages:365256 kB
  Mapped:   304856 kB
  Shmem: 50208 kB
  KReclaimable: 110308 kB
  Slab: 455680 kB
  SReclaimable: 110308 kB
  SUnreclaim:   345372 kB
  KernelStack:7664 kB
  PageTables: 6352 kB
  NFS_Unstable:  0 kB
  Bounce:0 kB
  WritebackTmp:  0 kB
  CommitLimit:10116668 kB
  Committed_AS:2497484 kB
  VmallocTotal:   34359738367 kB
  VmallocUsed:   31940 kB
  VmallocChunk:  0 kB
  Percpu:12800 kB
  HardwareCorrupted: 0 kB
  AnonHugePages:  4096 kB
  ShmemHugePages:0 kB
  ShmemPmdMapped:0 kB
  FileHugePages: 0 kB
  FilePmdMapped: 0 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  Hugetlb:   0 kB
  DirectMap4k:  315700 kB
  DirectMap2M:11919360 kB
  DirectMap1G: 6291456 kB
  ```
  And this is the `slabtop` header:
  ```
   Active / Total Objects (% used): 1095487 / 1172800 (93.4%)
   Active / Total Slabs (% used)  : 28258 / 28258 (100.0%)
   Active / Total Caches (% used) : 121 / 176 (68.8%)
   Active / Total Size (% used)   : 401911.16K / 415423.19K (96.7%)
   Minimum / Average / Maximum Object : 0.01K / 0.35K / 10.62K
  ```

  This is the `df -h` output:
  ```
  df -h
  Filesystem Size  Used Avail Use% Mounted on
  tmpfs  1.6G   50M  1.5G   4% /run
  /dev/mapper/ubuntu--vg-ubuntu--lv   14G  3.8G  9.0G  30% /
  tmpfs  7.7G   20K  7.7G   1% /dev/shm
  tmpfs  5.0M 0  5.0M   0% /run/lock
  /dev/sda2  2.0G  127M  1.7G   7% /boot
  /dev/mapper/vg0-var_log9.8G  127M  9.2G   2% /var/log
  /dev/mapper/vg0-tmp9.8G   68K  9.3G   1% /tmp
  /dev/mapper/vg0-var_tmp9.8G   96K  9.3G   1% /var/tmp
  /dev/mapper/vg0-var_lib_docker 1.7T   11G  1.6T   1% /var/lib/docker
  tmpfs  1.6G 0  1.6G   0% /run/user/2010
  tmpfs  1.6G 0  1.6G   0% /run/user/2023
  ```

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


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

[Kernel-packages] [Bug 1990292] [NEW] Mistery memory usage in linux Kernel >= 5.14

You have been subscribed to a public bug:

My hardware is SuperMicro X11SDV-8C-TP8F with Intel D-2146NT.
I've tested this issue with:

* Ubuntu 22.04 Kernel 5.15
* Ubuntu 22.04 Kernel 5.17
* Ubuntu 20.04 Kernel 5.15
* Ubuntu 20.04 Kernel 5.14

Using Ubuntu 20.04 with kernel 5.13 or lower will NOT trigger this
issue.

The issue is that I have high RAM usage from the server startup I cannot
explain.

At startup without any services active I have nearly 6GiB of RAM used:
```
# free -m
   totalusedfree  shared  buff/cache   available
Mem:   1566359988936 155 7289213
Swap:  0   0   0
```

Using ps the sum of RSS memory does not adds up: it shows less than 1GiB used:
```
# ps aux | awk '{sum+=$6} END {print sum / 1024}'
944.879
```

This is the meminfo output
```
cat /proc/meminfo 
MemTotal:   16039044 kB
MemFree: 8486372 kB
MemAvailable:9607120 kB
Buffers:   79440 kB
Cached:  1300092 kB
SwapCached:0 kB
Active:   575856 kB
Inactive:1141004 kB
Active(anon):  24184 kB
Inactive(anon):   369940 kB
Active(file): 551672 kB
Inactive(file):   771064 kB
Unevictable:   27884 kB
Mlocked:   27884 kB
SwapTotal:   2097148 kB
SwapFree:2097148 kB
Dirty:36 kB
Writeback: 0 kB
AnonPages:365256 kB
Mapped:   304856 kB
Shmem: 50208 kB
KReclaimable: 110308 kB
Slab: 455680 kB
SReclaimable: 110308 kB
SUnreclaim:   345372 kB
KernelStack:7664 kB
PageTables: 6352 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit:10116668 kB
Committed_AS:2497484 kB
VmallocTotal:   34359738367 kB
VmallocUsed:   31940 kB
VmallocChunk:  0 kB
Percpu:12800 kB
HardwareCorrupted: 0 kB
AnonHugePages:  4096 kB
ShmemHugePages:0 kB
ShmemPmdMapped:0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
Hugetlb:   0 kB
DirectMap4k:  315700 kB
DirectMap2M:11919360 kB
DirectMap1G: 6291456 kB
```
And this is the `slabtop` header:
```
 Active / Total Objects (% used): 1095487 / 1172800 (93.4%)
 Active / Total Slabs (% used)  : 28258 / 28258 (100.0%)
 Active / Total Caches (% used) : 121 / 176 (68.8%)
 Active / Total Size (% used)   : 401911.16K / 415423.19K (96.7%)
 Minimum / Average / Maximum Object : 0.01K / 0.35K / 10.62K
```

This is the `df -h` output:
```
df -h
Filesystem Size  Used Avail Use% Mounted on
tmpfs  1.6G   50M  1.5G   4% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   14G  3.8G  9.0G  30% /
tmpfs  7.7G   20K  7.7G   1% /dev/shm
tmpfs  5.0M 0  5.0M   0% /run/lock
/dev/sda2  2.0G  127M  1.7G   7% /boot
/dev/mapper/vg0-var_log9.8G  127M  9.2G   2% /var/log
/dev/mapper/vg0-tmp9.8G   68K  9.3G   1% /tmp
/dev/mapper/vg0-var_tmp9.8G   96K  9.3G   1% /var/tmp
/dev/mapper/vg0-var_lib_docker 1.7T   11G  1.6T   1% /var/lib/docker
tmpfs  1.6G 0  1.6G   0% /run/user/2010
tmpfs  1.6G 0  1.6G   0% /run/user/2023
```

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


** Tags: bot-comment
-- 
Mistery memory usage in linux Kernel >= 5.14
https://bugs.launchpad.net/bugs/1990292
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

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 1990294

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

Title:
  Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot
  services..."

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

Bug description:
  When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no
  output appeared on the console after the EFI stub:

  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint A0
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint AD
  EFI stub: Booting Linux Kernel...
  EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services...

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


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

[Kernel-packages] [Bug 1990304] [NEW] package linux-generic-hwe-20.04 5.15.0.46.49~20.04.16 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2022-09-20 Thread Ramiro Arias

Public bug reported:

ramiro@HP-s151nr:~$ lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
ramiro@HP-s151nr:~$ 


ramiro@HP-s151nr:~$ sudo apt update
[sudo] password for ramiro: 
Hit:1 http://co.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:3 http://co.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:4 http://co.archive.ubuntu.com/ubuntu focal-backports InRelease
Reading package lists... Done
Building dependency tree   
Reading state information... Done
9 packages can be upgraded. Run 'apt list --upgradable' to see them.
ramiro@HP-s151nr:~$ sudo apt -f install
^Ziting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is 
held by process 3000 (apt)... 14s
[1]+  Stopped sudo apt -f install
ramiro@HP-s151nr:~$ dpkg --configure -a
dpkg: error: requested operation requires superuser privilege
ramiro@HP-s151nr:~$ sudo dpkg --configure -a
dpkg: error: dpkg frontend lock is locked by another process
ramiro@HP-s151nr:~$ sudo dpkg --configure -a
dpkg: error: dpkg frontend lock is locked by another process
ramiro@HP-s151nr:~$ sudo rm /var/lib/apt/lists/lock
ramiro@HP-s151nr:~$ sudo rm /var/lib/dpkg/lock
ramiro@HP-s151nr:~$ sudo rm /var/lib/dpkg/lock-front-end
rm: cannot remove '/var/lib/dpkg/lock-front-end': No such file or directory
ramiro@HP-s151nr:~$ sudo rm /var/cache/apt/archives/lock
ramiro@HP-s151nr:~$ sudo dpkg --configure -a
dpkg: error: dpkg frontend lock is locked by another process
ramiro@HP-s151nr:~$ sudo apt clean
ramiro@HP-s151nr:~$ sudo apt install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
7 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up xxd (2:8.1.2269-1ubuntu5.9) ...
Setting up vim-common (2:8.1.2269-1ubuntu5.9) ...
Setting up libtiff5:amd64 (4.1.0+git191117-2ubuntu0.20.04.5) ...
Setting up vim-tiny (2:8.1.2269-1ubuntu5.9) ...
Setting up linux-image-5.15.0-48-generic (5.15.0-48.54~20.04.1) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.15.0-46-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.15.0-48-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.15.0-48-generic
Setting up linux-modules-extra-5.15.0-48-generic (5.15.0-48.54~20.04.1) ...
Setting up linux-modules-5.15.0-48-generic (5.15.0-48.54~20.04.1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.9) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for linux-image-5.15.0-48-generic (5.15.0-48.54~20.04.1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.0-48-generic
Found initrd image: /boot/initrd.img-5.15.0-48-generic
Found linux image: /boot/vmlinuz-5.15.0-46-generic
Found initrd image: /boot/initrd.img-5.15.0-46-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
ramiro@HP-s151nr:~$ sudo apt install synaptic
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libept1.6.0 libxapian30
Suggested packages:
  xapian-tools dwww menu deborphan apt-xapian-index tasksel
The following NEW packages will be installed:
  libept1.6.0 libxapian30 synaptic
0 upgraded, 3 newly installed, 0 to remove and 5 not upgraded.
Need to get 1.362 kB of archives.
After this operation, 6.346 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://co.archive.ubuntu.com/ubuntu focal/universe amd64 libept1.6.0 
amd64 1.1+nmu3ubuntu3 [79,6 kB]
Get:2 http://co.archive.ubuntu.com/ubuntu focal/universe amd64 libxapian30 
amd64 1.4.14-2 [661 kB]
Get:3 http://co.archive.ubuntu.com/ubuntu focal/universe amd64 synaptic amd64 
0.84.6ubuntu5 [622 kB]
Fetched 1.362 kB in 1s (1.160 kB/s)
Selecting previously unselected package libept1.6.0:amd64.
(Reading database ... 168203 files and directories currently installed.)
Preparing to unpack .../libept1.6.0_1.1+nmu3ubuntu3_amd64.deb ...
Unpacking libept1.6.0:amd64 (1.1+nmu3ubuntu3) ...
Selecting previously unselected package libxapian30:amd64.
Preparing to unpack .../libxapian30_1.4.14-2_amd64.deb ...
Unpacking libxapian30:amd64 (1.4.14-2) ...
Selecting previously unselected package synaptic.
Preparing to unpack .../synaptic_0.84.6ubuntu5_amd64.deb ...
Unpacking synaptic (0.84.6ubuntu5) ...
Setting up libxapian30:amd64 (1.4.1

[Kernel-packages] [Bug 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."

2022-09-20 Thread dann frazier

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

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

** No longer affects: ubuntu

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

Title:
  Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot
  services..."

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no
  output appeared on the console after the EFI stub:

  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint A0
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint AD
  EFI stub: Booting Linux Kernel...
  EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services...

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


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

[Kernel-packages] [Bug 1990296] Status changed to Confirmed

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

Title:
  package linux-tools-5.15.0-48 (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/lib/libcpupower.so.5.15.0-48', which is also in package linux-
  lowlatency-tools-5.15.0-48 5.15.0-48.54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  having issues installing linux-tools-lowlatency beside linux-tools-
  generic. Never had this issue before.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-5.15.0-48 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-47.53-lowlatency 5.15.46
  Uname: Linux 5.15.0-47-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-tools-5.15.0-48:amd64: Install
   linux-tools-5.15.0-48-generic:amd64: Install
   linux-tools-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brad   3893 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Tue Sep 20 12:15:30 2022
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb ...
   Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  DuplicateSignature:
   package:linux-tools-5.15.0-48:(not installed)
   Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which 
is also in package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  HibernationDevice: RESUME=UUID=9419e6bd-7ab8-447c-913d-98351acfc367
  InstallationDate: Installed on 2013-09-08 (3298 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   CloudflareWARP  no wireless extensions.
  MachineType: Hewlett-Packard 320-1030
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-lowlatency 
root=UUID=52c25727-125e-44b2-86c1-5ef593ad77e8 ro threadirqs noapic quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-tools-5.15.0-48 (not installed) failed to 
install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which 
is also in package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  UpgradeStatus: Upgraded to jammy on 2022-08-23 (28 days ago)
  dmi.bios.date: 04/12/2012
  dmi.bios.release: 7.15
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.15
  dmi.board.asset.tag: 3CR136220V
  dmi.board.name: 2ACB
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 3CR136220V
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.15:bd04/12/2012:br7.15:svnHewlett-Packard:pn320-1030:pvr:rvnPEGATRONCORPORATION:rn2ACB:rvr1.03:cvnHewlett-Packard:ct3:cvr:skuQP788AA#ABA:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 320-1030
  dmi.product.sku: QP788AA#ABA
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1990296] Re: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in package linux-low

2022-09-20 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-tools-5.15.0-48 (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/lib/libcpupower.so.5.15.0-48', which is also in package linux-
  lowlatency-tools-5.15.0-48 5.15.0-48.54

Status in linux package in Ubuntu:
  New

Bug description:
  having issues installing linux-tools-lowlatency beside linux-tools-
  generic. Never had this issue before.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-5.15.0-48 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-47.53-lowlatency 5.15.46
  Uname: Linux 5.15.0-47-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-tools-5.15.0-48:amd64: Install
   linux-tools-5.15.0-48-generic:amd64: Install
   linux-tools-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brad   3893 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Tue Sep 20 12:15:30 2022
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb ...
   Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  DuplicateSignature:
   package:linux-tools-5.15.0-48:(not installed)
   Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which 
is also in package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  HibernationDevice: RESUME=UUID=9419e6bd-7ab8-447c-913d-98351acfc367
  InstallationDate: Installed on 2013-09-08 (3298 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   CloudflareWARP  no wireless extensions.
  MachineType: Hewlett-Packard 320-1030
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-lowlatency 
root=UUID=52c25727-125e-44b2-86c1-5ef593ad77e8 ro threadirqs noapic quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-tools-5.15.0-48 (not installed) failed to 
install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which 
is also in package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  UpgradeStatus: Upgraded to jammy on 2022-08-23 (28 days ago)
  dmi.bios.date: 04/12/2012
  dmi.bios.release: 7.15
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.15
  dmi.board.asset.tag: 3CR136220V
  dmi.board.name: 2ACB
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 3CR136220V
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.15:bd04/12/2012:br7.15:svnHewlett-Packard:pn320-1030:pvr:rvnPEGATRONCORPORATION:rn2ACB:rvr1.03:cvnHewlett-Packard:ct3:cvr:skuQP788AA#ABA:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 320-1030
  dmi.product.sku: QP788AA#ABA
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1990296] Re: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in package linux-low

2022-09-20 Thread Brad Needham

Never happened in previous versions of Ubuntu. Only in current 22.04.1

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

Title:
  package linux-tools-5.15.0-48 (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/lib/libcpupower.so.5.15.0-48', which is also in package linux-
  lowlatency-tools-5.15.0-48 5.15.0-48.54

Status in linux package in Ubuntu:
  New

Bug description:
  having issues installing linux-tools-lowlatency beside linux-tools-
  generic. Never had this issue before.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-5.15.0-48 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-47.53-lowlatency 5.15.46
  Uname: Linux 5.15.0-47-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-tools-5.15.0-48:amd64: Install
   linux-tools-5.15.0-48-generic:amd64: Install
   linux-tools-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brad   3893 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Tue Sep 20 12:15:30 2022
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb ...
   Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  DuplicateSignature:
   package:linux-tools-5.15.0-48:(not installed)
   Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which 
is also in package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  HibernationDevice: RESUME=UUID=9419e6bd-7ab8-447c-913d-98351acfc367
  InstallationDate: Installed on 2013-09-08 (3298 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   CloudflareWARP  no wireless extensions.
  MachineType: Hewlett-Packard 320-1030
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-lowlatency 
root=UUID=52c25727-125e-44b2-86c1-5ef593ad77e8 ro threadirqs noapic quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-tools-5.15.0-48 (not installed) failed to 
install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which 
is also in package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  UpgradeStatus: Upgraded to jammy on 2022-08-23 (28 days ago)
  dmi.bios.date: 04/12/2012
  dmi.bios.release: 7.15
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.15
  dmi.board.asset.tag: 3CR136220V
  dmi.board.name: 2ACB
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 3CR136220V
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.15:bd04/12/2012:br7.15:svnHewlett-Packard:pn320-1030:pvr:rvnPEGATRONCORPORATION:rn2ACB:rvr1.03:cvnHewlett-Packard:ct3:cvr:skuQP788AA#ABA:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 320-1030
  dmi.product.sku: QP788AA#ABA
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1990296] [NEW] package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in package linux-l

2022-09-20 Thread Brad Needham

Public bug reported:

having issues installing linux-tools-lowlatency beside linux-tools-
generic. Never had this issue before.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-tools-5.15.0-48 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-47.53-lowlatency 5.15.46
Uname: Linux 5.15.0-47-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering:
 linux-tools-5.15.0-48:amd64: Install
 linux-tools-5.15.0-48-generic:amd64: Install
 linux-tools-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  brad   3893 F pulseaudio
CasperMD5CheckResult: unknown
Date: Tue Sep 20 12:15:30 2022
DpkgTerminalLog:
 Preparing to unpack .../linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb ...
 Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
  trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
DuplicateSignature:
 package:linux-tools-5.15.0-48:(not installed)
 Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
  trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is 
also in package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
HibernationDevice: RESUME=UUID=9419e6bd-7ab8-447c-913d-98351acfc367
InstallationDate: Installed on 2013-09-08 (3298 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
 
 CloudflareWARP  no wireless extensions.
MachineType: Hewlett-Packard 320-1030
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-lowlatency 
root=UUID=52c25727-125e-44b2-86c1-5ef593ad77e8 ro threadirqs noapic quiet 
splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/libcpupower.so.5.15.0-48', which is also in 
package linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
UpgradeStatus: Upgraded to jammy on 2022-08-23 (28 days ago)
dmi.bios.date: 04/12/2012
dmi.bios.release: 7.15
dmi.bios.vendor: AMI
dmi.bios.version: 7.15
dmi.board.asset.tag: 3CR136220V
dmi.board.name: 2ACB
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.03
dmi.chassis.asset.tag: 3CR136220V
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr7.15:bd04/12/2012:br7.15:svnHewlett-Packard:pn320-1030:pvr:rvnPEGATRONCORPORATION:rn2ACB:rvr1.03:cvnHewlett-Packard:ct3:cvr:skuQP788AA#ABA:
dmi.product.family: 103C_53316J G=D
dmi.product.name: 320-1030
dmi.product.sku: QP788AA#ABA
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package jammy need-duplicate-check package-conflict

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

Title:
  package linux-tools-5.15.0-48 (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/lib/libcpupower.so.5.15.0-48', which is also in package linux-
  lowlatency-tools-5.15.0-48 5.15.0-48.54

Status in linux package in Ubuntu:
  New

Bug description:
  having issues installing linux-tools-lowlatency beside linux-tools-
  generic. Never had this issue before.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-5.15.0-48 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-47.53-lowlatency 5.15.46
  Uname: Linux 5.15.0-47-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   linux-tools-5.15.0-48:amd64: Install
   linux-tools-5.15.0-48-generic:amd64: Install
   linux-tools-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brad   3893 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Tue Sep 20 12:15:30 2022
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb ...
   Unpacking linux-tools-5.15.0-48 (5.15.0-48.54) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-5.15.0-48_5.15.0-48.54_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpupowe

[Kernel-packages] [Bug 1981554] Re: [Ubuntu-22.04] Video mode is not working with the external monitor

2022-09-20 Thread Michael Reed

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Ubuntu-22.04] Video mode is not working  with the external monitor

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description: 
  The SUT Dell EMC Poweredge R440 can not display video mode with external 
monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC 
virtual console.

  Steps to Reproduce:
  1. Connect External monitor to SUT using VGA cable.
  2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console.
  3. Start to install the OS and click "Try or Install Ubuntu server".
  4. The SUT can not display video mode with monitor when OS boots.

  
  Expected Results:
  Video mode should work properly when OS boots with external monitor.

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


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

[Kernel-packages] [Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)

2022-09-20 Thread Stefan

Managed to capture the kernel crash during LiveUSB boot

** Attachment added: "USB 22.04 boot crash"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+attachment/5617448/+files/image20220811_223937394.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/1970127

Title:
Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7
3700U)

Status in linux package in Ubuntu:
Confirmed

Bug description:
The ubuntu-22.04-desktop-amd64.iso live cd does not boot on a HP ENVY
X360 notebook (Ryzen 7 3700U).

Model:
HP ENVY X360
13-ar0777ng
9YN58EA#ABD

After a few minutes the screen simply switches to black. No
possibility to get a console by pressing CTRL-ALT-F1, F2, ...

I removed the boot options "quiet splash" and recorded the boot via video.
(just ask if you need the full video)
I attach a significantly looking screenshot from that video, showing a kernel
bug message.

Currently the notebook runs with Ubuntu-20.04 using the Linux-5.11 HWE kernel.
But suspend to memory isn't working.
Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292

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

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

[Kernel-packages] [Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches

2022-09-20 Thread Michael Reed

Hi Sreekanth,

Have you had an opportunity to test the test kernel in comment #8?

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

Title:
  [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches

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

Bug description:
  Request to include below mpt3sas driver bug fix patches in Ubuntu
  22.04 kernel. These patches got accepted by the upstream and please
  find the corresponding commit IDs as below,

  5db207d66d mpt3sas: Fix incorrect 4gb boundary check
  ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
  9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface

  Below is the summary of each of the above bug fix commits,

  1. mpt3sas: Fix incorrect 4gb boundary check:
 Without this patch, driver was checking whether any of it's pool crosses 
the 4gb boundary or not using the pool's virtual address instead of using it's 
dma address. So some time driver may false positively assume that the pool as 
crossed the 4gb boundary region (as it observes that pool's virtual address is 
crossing the 4gb boundary) even though it is really not.

  2. mpt3sas: Remove scsi_dma_map errors messages:
 When driver set the DMA mask to 32bit then we observe that the SWIOTLB 
bounce buffers are getting exhausted quickly. For most of the IOs driver 
observe that scsi_dma_map() API returned with failure status and hence driver 
was printing below error message. Since this error message is getting printed 
per IO and if user issues heavy IOs then we observe that kernel overwhelmed 
with this error message. Also we will observe the kernel panic when the serial 
console is enabled. So to limit this issue, we removed this error message 
though this patch.
  "scsi_dma_map failed: request for 1310720 bytes!"  

  3. mpt3sas: Update persistent trigger pages from sysfs interface:
 When user set's any diag buffer trigger conditions then driver has to save 
these trigger conditions in the controller Firmware's NVRAM region. So that 
when system reboots then driver can get these trigger conditions from 
Firmware's NVRAM region and set these trigger conditions automatically. so that 
user no need to set these conditions again. Without this patch driver was not 
not saving these user provided trigger conditions in the Firmware's NVRAM 
region.   
  
  Please let me if I have missed to add any data.

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


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

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

2022-09-20 Thread John Smith

I just noticed, why is the importance marked as "wishlist"?

it is confirmed bug as,

A function (wake on touchpad interaction) was working in several past version 
of Ubuntu 
(atleast 18.04 to 21.04), but stopped working with Ubuntu 21.10 (Kernel 5.15).

Kernel: 5.13 -> bug -> 5.14

Last when I was looking into it, I managed to identify the buggy kernel version 
to between 5.13 & 5.14.
(After that I got ill for half a month, then, my main internet connection broke 
for half a month),

After that it just got backlogged in mind.

Now my main internet is again broken, so I was checking on progress of this bug,
unfortunately, I can't really make any progress as I am on very limited data 
connection.

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

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


-- 
Mailing li

[Kernel-packages] [Bug 1990286] Status changed to Confirmed

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

Title:
  X display crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Display frequently crashes when running windows 10 pro in KVM Virtual
  Machine. When the system is in too much pressure in memory consumption
  and workload then also display crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-47-generic 5.15.0-47.51
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nzeo   3428 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 20 19:35:55 2022
  InstallationDate: Installed on 2022-04-26 (147 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541NA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-47-generic N/A
   linux-backports-modules-5.15.0-47-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541NA.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541NA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541NA.309:bd05/25/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: X
  dmi.product.name: X541NA
  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/1990286/+subscriptions


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

[Kernel-packages] [Bug 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support

2022-09-20 Thread Graham Inggs

** Summary changed:

- PolarFire Icicle Kit: enable PCIe support
+ [FFe] PolarFire Icicle Kit: enable PCIe support

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

Title:
  [FFe] PolarFire Icicle Kit: enable PCIe support

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it
  is not usable. Please, add the following patches:

  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/
  riscv: dts: microchip: add pci dma ranges for the icicle
  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/
  riscv: dts: microchip: move the mpfs' pci node to
  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/
  riscv: dts: microchip: icicle: update pci address
  # 
https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/
  riscv: dts: microchip: icicle: re-jig fabric peripheral
  # 
https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/
 
  riscv: dts: microchip: add fabric address translation
  # 
https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/
  PCI: microchip: add fabric address translation properties

  All patches are strictly restricted to the PolarFire Icicle Kit and
  have no impact on any other RISC-V boards that we support.

  Best regards

  Heinrich

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


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

[Kernel-packages] [Bug 1990286] [NEW] X display crash

2022-09-20 Thread Anjan Bora

Public bug reported:

Display frequently crashes when running windows 10 pro in KVM Virtual
Machine. When the system is in too much pressure in memory consumption
and workload then also display crashes.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-47-generic 5.15.0-47.51
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nzeo   3428 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 20 19:35:55 2022
InstallationDate: Installed on 2022-04-26 (147 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam
 Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X541NA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-47-generic N/A
 linux-backports-modules-5.15.0-47-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/25/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X541NA.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X541NA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541NA.309:bd05/25/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: X
dmi.product.name: X541NA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/1990286/+attachment/5617408/+files/journal.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/1990286

Title:
  X display crash

Status in linux package in Ubuntu:
  New

Bug description:
  Display frequently crashes when running windows 10 pro in KVM Virtual
  Machine. When the system is in too much pressure in memory consumption
  and workload then also display crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-47-generic 5.15.0-47.51
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nzeo   3428 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 20 19:35:55 2022
  InstallationDate: Installed on 2022-04-26 (147 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 005: ID 04ca:3010 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541NA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-47-generic N/A
   linux-backports-modules-5.15.0-47-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541NA.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541NA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541NA.309:bd05/25/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541

[Kernel-packages] [Bug 1990275] Re: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04

2022-09-20 Thread Frank Heimes

Since kinetic/22.10 is based on 5.19 and all patches got upstream
accepted with at least v5.18 (one 5.17), everything needed is included
in kinetic/22.10.

For jammy/22.04 I checked master-next and found all patches in
Ubuntu-5.15.0-41 or later, so jammy/22.04 incl. all the fixes and is not
(or better no longer) affected.

But neither of these patches is incl. in focal/20.04 master-next, so
only focal is affected (and with that also bionic-hwe-5.4)

So I'm marking this ticket as affecting focal.
(Btw. it would have been great if these patches would have been marked for 5.4 
upstream stable too, since 5.4 is upstream also a long-term kernel; in such a 
case the fixes would have landed automatically in Ubuntu's focal/20.04 - and in 
bionic-hwe-5.4).

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

Title:
  [UBUNTU 20.04] Unexpected  LAG affinity behaviour with  mlx5_core
  driver in Ubuntu 20.04

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

Bug description:
  == Comment: #0 - KISHORE KUMAR  G  - 2022-09-19 
04:39:42 ==
  ---Problem Description---
  On a  Ubuntu/s390 system that houses a Mellanox CX5 Adapter  with two ports 
connected to the a pair of TOR switches , act as entry point to cluster of 
compute nodes to access public network ( edge node) with following level of mlx 
firmware :

  ethtool -i p0

  driver: mlx5e_rep
  version: 5.4.0-104.118-
  firmware-version: 16.27.1016 (MT_13)
  expansion-rom-version:
  bus-info: 0100:00:00.0
  supports-statistics: yes
  supports-test: no
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: no


  The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to
  routing events and sets the LAG affinity accordingly , whereas in one
  of  custom services  has  Fabcon service listens to the routing events
  and sets the LAG affinity in the mellanox driver accordingly.

  The edge node routes defined in  compute nodes  use both the two  interfaces 
(port1 -P0 and port2- P1) for the LAG affinity. For instance 
  10.66.0.170 proto bgp src 10.66.11.43 metric 20 
  nexthop via 172.31.22.42 dev p0 weight 1 
  nexthop via 172.31.22.170 dev p1 weight 1

  As an example post an edge node bootup ,  LAG mapping gets converged to use 
both  port1(P0) and port2 (P1) by default 
  root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
  [  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2  
   
  [  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 
(<-- Both ports are equally mapped)

  The issue comes, when the mlx5_core driver  cannot derive the LAG
  configuration from specific routes. For instance,an operation of
  disabling an interface from edge node above (10.66.0.170) or
  addition/removal of the interface, causes mlx5_core driver to listen
  on the routing change and change the LAG affinity to use a single
  network interface only.

  In the following example ,a new static route entry  to a single
  destination  (10.66.47.34) is added  as below

   ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via
  172.31.22.42 dev p0

  Caused  the LAG mapping change to port1(p0)   as detected as following

  root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
  [  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2
  [  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2
  [  757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1

[Kernel-packages] [Bug 1990275] Re: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04

2022-09-20 Thread Frank Heimes

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes 
(fheimes)

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

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

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

Title:
  [UBUNTU 20.04] Unexpected  LAG affinity behaviour with  mlx5_core
  driver in Ubuntu 20.04

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

Bug description:
  == Comment: #0 - KISHORE KUMAR  G  - 2022-09-19 
04:39:42 ==
  ---Problem Description---
  On a  Ubuntu/s390 system that houses a Mellanox CX5 Adapter  with two ports 
connected to the a pair of TOR switches , act as entry point to cluster of 
compute nodes to access public network ( edge node) with following level of mlx 
firmware :

  ethtool -i p0

  driver: mlx5e_rep
  version: 5.4.0-104.118-
  firmware-version: 16.27.1016 (MT_13)
  expansion-rom-version:
  bus-info: 0100:00:00.0
  supports-statistics: yes
  supports-test: no
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: no


  The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to
  routing events and sets the LAG affinity accordingly , whereas in one
  of  custom services  has  Fabcon service listens to the routing events
  and sets the LAG affinity in the mellanox driver accordingly.

  The edge node routes defined in  compute nodes  use both the two  interfaces 
(port1 -P0 and port2- P1) for the LAG affinity. For instance 
  10.66.0.170 proto bgp src 10.66.11.43 metric 20 
  nexthop via 172.31.22.42 dev p0 weight 1 
  nexthop via 172.31.22.170 dev p1 weight 1

  As an example post an edge node bootup ,  LAG mapping gets converged to use 
both  port1(P0) and port2 (P1) by default 
  root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
  [  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2  
   
  [  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 
(<-- Both ports are equally mapped)

  The issue comes, when the mlx5_core driver  cannot derive the LAG
  configuration from specific routes. For instance,an operation of
  disabling an interface from edge node above (10.66.0.170) or
  addition/removal of the interface, causes mlx5_core driver to listen
  on the routing change and change the LAG affinity to use a single
  network interface only.

  In the following example ,a new static route entry  to a single
  destination  (10.66.47.34) is added  as below

   ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via
  172.31.22.42 dev p0

  Caused  the LAG mapping change to port1(p0)   as detected as following

  root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
  [  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2
  [  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2
  [  757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1

[Kernel-packages] [Bug 1990275] [NEW] [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04

2022-09-20 Thread bugproxy

Public bug reported:

== Comment: #0 - KISHORE KUMAR  G  - 2022-09-19 04:39:42 
==
---Problem Description---
On a  Ubuntu/s390 system that houses a Mellanox CX5 Adapter  with two ports 
connected to the a pair of TOR switches , act as entry point to cluster of 
compute nodes to access public network ( edge node) with following level of mlx 
firmware :

ethtool -i p0

driver: mlx5e_rep
version: 5.4.0-104.118-
firmware-version: 16.27.1016 (MT_13)
expansion-rom-version:
bus-info: 0100:00:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no


The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to
routing events and sets the LAG affinity accordingly , whereas in one of
custom services  has  Fabcon service listens to the routing events and
sets the LAG affinity in the mellanox driver accordingly.

The edge node routes defined in  compute nodes  use both the two  interfaces 
(port1 -P0 and port2- P1) for the LAG affinity. For instance 
10.66.0.170 proto bgp src 10.66.11.43 metric 20 
nexthop via 172.31.22.42 dev p0 weight 1 
nexthop via 172.31.22.170 dev p1 weight 1

As an example post an edge node bootup ,  LAG mapping gets converged to use 
both  port1(P0) and port2 (P1) by default 
root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
[  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2
 
[  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 
(<-- Both ports are equally mapped)

The issue comes, when the mlx5_core driver  cannot derive the LAG
configuration from specific routes. For instance,an operation of
disabling an interface from edge node above (10.66.0.170) or
addition/removal of the interface, causes mlx5_core driver to listen on
the routing change and change the LAG affinity to use a single network
interface only.

In the following example ,a new static route entry  to a single
destination  (10.66.47.34) is added  as below

 ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via
172.31.22.42 dev p0

Caused  the LAG mapping change to port1(p0)   as detected as following

root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
[  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2
[  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2
[  757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1

[Kernel-packages] [Bug 1990275] [NEW] [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04

You have been subscribed to a public bug:

== Comment: #0 - KISHORE KUMAR  G  - 2022-09-19 04:39:42 
==
---Problem Description---
On a  Ubuntu/s390 system that houses a Mellanox CX5 Adapter  with two ports 
connected to the a pair of TOR switches , act as entry point to cluster of 
compute nodes to access public network ( edge node) with following level of mlx 
firmware :

ethtool -i p0

driver: mlx5e_rep
version: 5.4.0-104.118-
firmware-version: 16.27.1016 (MT_13)
expansion-rom-version:
bus-info: 0100:00:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no


The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to
routing events and sets the LAG affinity accordingly , whereas in one of
custom services  has  Fabcon service listens to the routing events and
sets the LAG affinity in the mellanox driver accordingly.

The edge node routes defined in  compute nodes  use both the two  interfaces 
(port1 -P0 and port2- P1) for the LAG affinity. For instance 
10.66.0.170 proto bgp src 10.66.11.43 metric 20 
nexthop via 172.31.22.42 dev p0 weight 1 
nexthop via 172.31.22.170 dev p1 weight 1

As an example post an edge node bootup ,  LAG mapping gets converged to use 
both  port1(P0) and port2 (P1) by default 
root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
[  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2
 
[  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 
(<-- Both ports are equally mapped)

The issue comes, when the mlx5_core driver  cannot derive the LAG
configuration from specific routes. For instance,an operation of
disabling an interface from edge node above (10.66.0.170) or
addition/removal of the interface, causes mlx5_core driver to listen on
the routing change and change the LAG affinity to use a single network
interface only.

In the following example ,a new static route entry  to a single
destination  (10.66.47.34) is added  as below

 ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via
172.31.22.42 dev p0

Caused  the LAG mapping change to port1(p0)   as detected as following

root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag
[  282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2
[  282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2
[  757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1

[Kernel-packages] [Bug 1908916] Re: brcmfmac bug while going to sleep

2022-09-20 Thread Narwaro

Thanks, this workaround is a great idea and works flawlessly!

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

Title:
  brcmfmac bug while going to sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439355] BUG: kernel NULL 
pointer dereference, address: 0050
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439365] #PF: supervisor read 
access in kernel mode
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439368] #PF: error_code(0x) 
- not-present page
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439371] PGD 0 P4D 0 
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439379] Oops:  [#1] SMP PTI
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439386] CPU: 2 PID: 869 Comm: 
wpa_supplicant Tainted: G   OE 5.4.0-58-generic #64-Ubuntu
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439389] Hardware name: Apple 
Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS 184.0.0.0.0 04/11/2019
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439427] RIP: 
0010:brcmf_remove_interface+0x4e/0x80 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439433] Code: 00 00 75 4c 44 8b 
47 60 41 89 f4 bf 02 00 00 00 48 c7 c2 90 b8 8e c0 48 c7 c6 90 3b 8e c0 e8 19 
dc ff ff 48 8b 3b 48 8b 47 08 <48> 8b 40 50 48 85 c0 74 0b 48 89 df e8 71 b9 b3 
d6 48 8b 3b 8b 73
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439437] RSP: 
0018:aa0f00bab9a8 EFLAGS: 00010286
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439441] RAX:  
RBX: 95ffd50b1000 RCX: 0001
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439445] RDX: c08eb890 
RSI: c08e3b90 RDI: 95ffd6a647a0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439448] RBP: aa0f00bab9b8 
R08:  R09: 
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439451] R10: 017f4b2f6a93 
R11: 0396353f R12: 0001
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439454] R13: 000a 
R14:  R15: 95ffd59a8000
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439458] FS:  
7f1031058140() GS:95ffdeb0() knlGS:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439462] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439465] CR2: 0050 
CR3: 000453dd2003 CR4: 003606e0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439468] Call Trace:
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439495]  
brcmf_p2p_del_vif+0x256/0x280 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439517]  
brcmf_cfg80211_del_iface+0x194/0x210 [brcmfmac]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439599]  
nl80211_del_interface+0x4f/0x110 [cfg80211]
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439609]  
genl_family_rcv_msg+0x1b9/0x470
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439618]  genl_rcv_msg+0x4c/0xa0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439624]  ? 
_cond_resched+0x19/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439630]  ? 
genl_family_rcv_msg+0x470/0x470
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439635]  
netlink_rcv_skb+0x50/0x120
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439641]  genl_rcv+0x29/0x40
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439646]  
netlink_unicast+0x187/0x220
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439652]  
netlink_sendmsg+0x222/0x3e0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439660]  sock_sendmsg+0x65/0x70
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439666]  
sys_sendmsg+0x212/0x280
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439673]  
___sys_sendmsg+0x88/0xd0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439681]  ? dentry_free+0x37/0x70
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439688]  ? 
security_file_free+0x54/0x60
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439695]  ? 
get_max_files+0x20/0x20
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439703]  ? 
__cgroup_bpf_run_filter_setsockopt+0xae/0x2d0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439708]  ? 
_cond_resched+0x19/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439714]  ? aa_sk_perm+0x43/0x170
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439722]  __sys_sendmsg+0x5c/0xa0
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439730]  
__x64_sys_sendmsg+0x1f/0x30
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439738]  
do_syscall_64+0x57/0x190
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439745]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439750] RIP: 0033:0x7f10313e8747
  Dec 20 10:59:18 nir-MacBookPro kernel: [ 1646.439755] Code: 64 89 02 48 c7 c0 
ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 
c0 75 10 b8 2e 00 00 00 0f

[Kernel-packages] [Bug 1990272] Status changed to Confirmed

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

Title:
  PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0],AER
  UnsupReq

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1
  Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine.

  The errors come in random waves of 60..160 back-to-back errors with an
  interval of 130..140 microseconds.

  Device [8086:51b0] is the PCI/thunderbolt bridge.

  [   20.086628] pcieport :00:1d.0: AER: Uncorrected (Non-Fatal) error 
received: :00:1d.0
  [   20.086671] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [   20.086680] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
  [   20.086688] pcieport :00:1d.0:[20] UnsupReq   (First)
  [   20.086694] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
  [   20.086810] thunderbolt :22:00.0: AER: can't recover (no 
error_detected callback)
  [   20.086846] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
  [   20.086878] pcieport :00:1d.0: AER: device recovery failed
  [   20.106033] pcieport :00:1d.0: AER: Multiple Uncorrected (Non-Fatal) 
error received: :00:1d.0
  [   20.106082] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [   20.106093] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
  [   20.106101] pcieport :00:1d.0:[20] UnsupReq   (First)
  [   20.106108] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
  [   20.106219] thunderbolt :22:00.0: AER: can't recover (no 
error_detected callback)
  [   20.106257] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
  [   20.106301] pcieport :00:1d.0: AER: device recovery failed

  Another wave was at 418s, 440s, 1168s, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-48-generic 5.15.0-48.54
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  me 1827 F pulseaudio
   /dev/snd/controlC0:  me 1827 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Sep 20 13:34:43 2022
  InstallationDate: Installed on 2022-08-31 (19 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21DE001QMH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro
  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-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2022
  dmi.bios.release: 1.8
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3JET24W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21DE001QMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3JET24W(1.08):bd07/21/2022:br1.8:efr1.5:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5:
  dmi.product.family: ThinkPad X1 Extreme Gen 5
  dmi.product.name: 21DE001QMH
  dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5
  dmi.product.version: ThinkPad X1 Extreme Gen 5
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1990262] Re: Screen reset randomly when moving cursors

If you don't find it's bug 1958191 which was fixed in mainline kernel
5.17.7 then please also try other mainline kernels to see if a fix for
this does exist in some newer version:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

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

Title:
  Screen reset randomly when moving cursors

Status in linux-oem-5.17 package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  The monitor occurs the flicker problem while moving the mouse if the external 
monitor is connected to type-c port via type-c-to-DP/HDMI dongle.

  [Steps to reproduce]
  1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to 
type-c-port
  2. Moving the mouse

  [Expected result]
  No broken screen while moving the mouse

  [Actual result]
  Screen broken sometimes

  [Failure rate]
  2/2

- video record:
  
https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing

  [Additional information]
  system-manufacturer: LENOVO
  system-product-name: ThinkStation P360 Ultra
  bios-version: S0FKT22A
  CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x)
  GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] 
(rev 0c)
  6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:2438] (rev a1)
  kernel-version: 5.17.0-1015-oem
  monitor: BenQ 4K EL2870U

  Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan 
(box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed
  Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
../clutter/clutter/clutter-actor.c:9279: Actor 
'[:0x557b77d66170]' tried to allocate a size of 
-2147483648.00 x -2147483648.00
  Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
../clutter/clutter/clutter-actor.c:9279: Actor 
'[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 
x -2147483648.00
  Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b75686370] is on because it needs an 
allocation.
  Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b7712a730] is on because it needs an 
allocation.
  Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b7712c6c0] is on because it needs an 
allocation.

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


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

[Kernel-packages] [Bug 1990262] Re: Screen reset randomly when moving cursors

Moved to the kernel because flickering like that is always the kernel's
fault/responsibility. There's nothing mutter can do to make sub-frame
flickers.

Please check bug 1958191 to see if it's the same issue fixed in 5.17.7
and later or by i915.enable_dc=0 intel_idle.max_cstate=2

If that's not the issue then when the flickering is happening next
please run:

  lspci -k > lspci.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.

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

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

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

Title:
  Screen reset randomly when moving cursors

Status in linux-oem-5.17 package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  The monitor occurs the flicker problem while moving the mouse if the external 
monitor is connected to type-c port via type-c-to-DP/HDMI dongle.

  [Steps to reproduce]
  1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to 
type-c-port
  2. Moving the mouse

  [Expected result]
  No broken screen while moving the mouse

  [Actual result]
  Screen broken sometimes

  [Failure rate]
  2/2

- video record:
  
https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing

  [Additional information]
  system-manufacturer: LENOVO
  system-product-name: ThinkStation P360 Ultra
  bios-version: S0FKT22A
  CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x)
  GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] 
(rev 0c)
  6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:2438] (rev a1)
  kernel-version: 5.17.0-1015-oem
  monitor: BenQ 4K EL2870U

  Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan 
(box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed
  Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
../clutter/clutter/clutter-actor.c:9279: Actor 
'[:0x557b77d66170]' tried to allocate a size of 
-2147483648.00 x -2147483648.00
  Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
../clutter/clutter/clutter-actor.c:9279: Actor 
'[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 
x -2147483648.00
  Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b75686370] is on because it needs an 
allocation.
  Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b7712a730] is on because it needs an 
allocation.
  Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b7712c6c0] is on because it needs an 
allocation.

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


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

[Kernel-packages] [Bug 1990272] [NEW] PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq

2022-09-20 Thread rustyx

Public bug reported:

My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1
Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine.

The errors come in random waves of 60..160 back-to-back errors with an
interval of 130..140 microseconds.

Device [8086:51b0] is the PCI/thunderbolt bridge.

[   20.086628] pcieport :00:1d.0: AER: Uncorrected (Non-Fatal) error 
received: :00:1d.0
[   20.086671] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
[   20.086680] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
[   20.086688] pcieport :00:1d.0:[20] UnsupReq   (First)
[   20.086694] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
[   20.086810] thunderbolt :22:00.0: AER: can't recover (no error_detected 
callback)
[   20.086846] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
[   20.086878] pcieport :00:1d.0: AER: device recovery failed
[   20.106033] pcieport :00:1d.0: AER: Multiple Uncorrected (Non-Fatal) 
error received: :00:1d.0
[   20.106082] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
[   20.106093] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
[   20.106101] pcieport :00:1d.0:[20] UnsupReq   (First)
[   20.106108] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
[   20.106219] thunderbolt :22:00.0: AER: can't recover (no error_detected 
callback)
[   20.106257] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
[   20.106301] pcieport :00:1d.0: AER: device recovery failed

Another wave was at 418s, 440s, 1168s, etc.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-48-generic 5.15.0-48.54
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  me 1827 F pulseaudio
 /dev/snd/controlC0:  me 1827 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Sep 20 13:34:43 2022
InstallationDate: Installed on 2022-08-31 (19 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 21DE001QMH
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro
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-48-generic N/A
 linux-backports-modules-5.15.0-48-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2022
dmi.bios.release: 1.8
dmi.bios.vendor: LENOVO
dmi.bios.version: N3JET24W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21DE001QMH
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.5
dmi.modalias: 
dmi:bvnLENOVO:bvrN3JET24W(1.08):bd07/21/2022:br1.8:efr1.5:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5:
dmi.product.family: ThinkPad X1 Extreme Gen 5
dmi.product.name: 21DE001QMH
dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5
dmi.product.version: ThinkPad X1 Extreme Gen 5
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy

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

Title:
  PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0],AER
  UnsupReq

Status in linux package in Ubuntu:
  New

Bug description:
  My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1
  Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine.

  The errors come in random waves of 60..160 back-to-back errors with an
  interval of 130..140 microseconds.

  Device [8086:51b0] is the PCI/thunderbolt bridge.

  [   20.086628] pcieport :00:1d.0: AER: Uncorrected (Non-Fatal) error 
received: :00:1d.0
  [   20.086671] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [   20.086680] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
  [   20.086688] pcieport 000

[Kernel-packages] [Bug 1990262] [NEW] Screen reset randomly when moving cursors

You have been subscribed to a public bug:

[Summary]
The monitor occurs the flicker problem while moving the mouse if the external 
monitor is connected to type-c port via type-c-to-DP/HDMI dongle.

[Steps to reproduce]
1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port
2. Moving the mouse

[Expected result]
No broken screen while moving the mouse

[Actual result]
Screen broken sometimes

[Failure rate]
2/2

  - video record:
https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing

[Additional information]
system-manufacturer: LENOVO
system-product-name: ThinkStation P360 Ultra
bios-version: S0FKT22A
CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x)
GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] 
(rev 0c)
6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] 
(rev a1)
kernel-version: 5.17.0-1015-oem
monitor: BenQ 4K EL2870U

Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan 
(box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed
Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
../clutter/clutter/clutter-actor.c:9279: Actor 
'[:0x557b77d66170]' tried to allocate a size of 
-2147483648.00 x -2147483648.00
Sep 07 13:22:50 ubuntu gnome-shell[1853]: 
../clutter/clutter/clutter-actor.c:9279: Actor 
'[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 
x -2147483648.00
Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b75686370] is on because it needs an 
allocation.
Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b7712a730] is on because it needs an 
allocation.
Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor 
[:0x557b7712c6c0] is on because it needs an 
allocation.

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

-- 
Screen reset randomly when moving cursors
https://bugs.launchpad.net/bugs/1990262
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-oem-5.17 in Ubuntu.

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

[Kernel-packages] [Bug 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] ERROR Failed to open channel.

Please use one of these commands to provide a full log.

If you have not rebooted since the freeze:

  journalctl -b0 > journal.txt

Or after you have rebooted:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1988488

Title:
  Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl
  [vmwgfx]] *ERROR* Failed to open channel.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Kernel-packages] [Bug 1990256] Re: [regression] Non-default GPUs (vboxvideo) in VirtualBox hang at the login screen

Based on comments in
https://gitlab.gnome.org/GNOME/mutter/-/issues/2384, a new fix might be
coming in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2482

** Changed in: linux (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

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

Title:
  [regression] Non-default GPUs (vboxvideo) in VirtualBox freeze at the
  login screen

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen.

  This is a regression of what was previously fixed in
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then
  broken again upstream.

  Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to 
set mode 2008x1274 on CRTC 32: Invalid argument
  Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: 
drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented

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


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

[Kernel-packages] [Bug 1990256] [NEW] [regression] Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen

Public bug reported:

Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen.

This is a regression of what was previously fixed in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then
broken again upstream.

Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to set 
mode 2008x1274 on CRTC 32: Invalid argument
Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: 
drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented

** Affects: mutter (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: jammy virtualbox

** Tags added: jammy

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2384
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2384

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

Title:
  [regression] Non-default GPUs (vboxvideo) in VirtualBox freeze at the
  login screen

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen.

  This is a regression of what was previously fixed in
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then
  broken again upstream.

  Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to 
set mode 2008x1274 on CRTC 32: Invalid argument
  Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: 
drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented

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


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

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

2022-09-20 Thread y0zg

The same bug is reproducible on AWS EKS 1.23

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-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.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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/linux/+bug/1924298/+subscriptions


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

2022-09-20 Thread Stefan Bader

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

** Changed in: linux (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: Triaged => 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/1990124

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

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

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: https://launc

[Kernel-packages] [Bug 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

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

** Description changed:

  [Impact]
+ The TBT ID[8086:1134] the new project uses is not listed in the driver.
  
  [Fix]
- 
- [Test]
+ 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.

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Incomplete

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

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

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

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

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

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

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

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

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

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

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

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

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  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
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  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 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1981111] Re: Focal update: v5.4.196 upstream stable release

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1982409] Re: Focal update: v5.4.198 upstream stable release

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1982968] Re: Jammy update: v5.15.47 upstream stable release

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1981758] Re: Focal update: v5.4.197 upstream stable release

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1983149] Re: Jammy update: v5.15.49 upstream stable release

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1983146] Re: Jammy update: v5.15.48 upstream stable release

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1983152] Re: Focal update: v5.4.200 upstream stable release

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1983150] Re: Focal update: v5.4.199 upstream stable release

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1983297] Re: Additional fix for TGL + AUO panel flickering

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1052.59

---
linux-oem-5.14 (5.14.0-1052.59) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1052.59 -proposed tracker (LP:
#1987820)

  * Additional fix for TGL + AUO panel flickering (LP: #1983297)
- Revert "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO 
panel"
- drm/i915/display: Fix sel fetch plane offset calculation
- drm/i915: Nuke ORIGIN_GTT
- drm/i915/display: Drop PSR support from HSW and BDW
- drm/i915/display/psr: Handle plane and pipe restrictions at every page 
flip
- drm/i915/display/psr: Do full fetch when handling multi-planar formats
- drm/i915/display: Drop unnecessary frontbuffer flushes
- drm/i915/display: Handle frontbuffer rendering when PSR2 selective fetch 
is
  enabled
- drm/i915/display: Fix glitches when moving cursor with PSR2 selective 
fetch
  enabled
- drm/i915/display/adlp: Optimize PSR2 power-savings in corner cases
- drm/i915/display/adlp: Allow PSR2 to be enabled
- SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker

 -- Timo Aaltonen   Fri, 09 Sep 2022
11:29:14 +0300

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

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

Title:
  Additional fix for TGL + AUO panel flickering

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

Bug description:
  [Impact] 
  "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel"
  alone used to fix the issue on the AUO panel. But the panel starts to
  flicker like crazy on top of the new stable commits. 

  [Fix]
  Backport full fix for PSR2 selective fetch, but only enable it on TGL +
  specific AUO panel. The last three patches which enable PSR2 on ADL-P
  are dropped.

  [Test]
  Originally the backport regressed ADL + BOE panel, so this time we
  put extra effort to ensure those system are unaffected, while TGL + AUO
  panel is still fixed.
   
  [Where problems could occur]
  Most code changes only have functional impact when PSR2 selective fetch
  is enabled. Some of changes are under more general call path for
  hardware cursor rendering.

  Notes are added to describe the functional impact for each patch, so if
  regression really occurrs it's easier to spot the offending commit.

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


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

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

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

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1983519] Re: [linux 5.19] rcu_preempt detected expedited stalls on CPUs/tasks: { 0-... } 272 jiffies s: 49 root: 0x1/.

2022-09-20 Thread Matthijs

I'm experiencing the same issue.

I am running Ubuntu 20.04 with kernel 5.19.7-051907-generic

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

Title:
  [linux 5.19] rcu_preempt detected expedited stalls on CPUs/tasks: {
  0-... } 272 jiffies s: 49 root: 0x1/.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A lot of traces in dmesg from RCU in released 5.19.0-051900-generic
  (from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/):

  [   11.878971] rcu: INFO: rcu_preempt detected expedited stalls on 
CPUs/tasks: { 0-... } 6 jiffies s: 49 root: 0x1/.
  [   11.879016] rcu: blocking rcu_node structures (internal RCU debug):
  [   11.879037] Task dump for CPU 0:
  [   11.879038] task:systemd-udevd   state:R  running task stack:0 
pid:  383 ppid:   357 flags:0x400a
  [   11.879043] Call Trace:
  [   11.879045]  
  [   11.879050]  ? find_kallsyms_symbol+0x92/0x1a0
  [   11.879056]  ? amdgpu_ras_query_err_status+0x100/0x100 [amdgpu]
  [   11.879370]  ? xgpu_ai_request_full_gpu_access+0x20/0x20 [amdgpu]
  [   11.879590]  ? module_address_lookup+0x68/0xc0
  [   11.879593]  ? xgpu_ai_request_init_data+0x50/0x50 [amdgpu]
  [   11.879813]  ? kallsyms_lookup_buildid+0xf7/0x180
  [   11.879817]  ? kallsyms_lookup+0x14/0x20
  [   11.879819]  ? test_for_valid_rec+0x38/0x80
  [   11.879822]  ? change_page_attr_set_clr+0x150/0x1c0
  [   11.879826]  ? ftrace_module_enable+0xa6/0x210
  [   11.879829]  ? load_module+0xa93/0xd30
  [   11.879831]  ? security_kernel_post_read_file+0x5c/0x70
  [   11.879834]  ? kernel_read_file+0x230/0x290
  [   11.879837]  ? __do_sys_finit_module+0xc8/0x140
  [   11.879839]  ? __do_sys_finit_module+0xc8/0x140
  [   11.879842]  ? __x64_sys_finit_module+0x18/0x20
  [   11.879844]  ? do_syscall_64+0x5c/0x90
  [   11.879848]  ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [   11.879851]  
  [   11.954966] rcu: INFO: rcu_preempt detected expedited stalls on 
CPUs/tasks: { 0-... } 25 jiffies s: 49 root: 0x1/.
  [   11.955002] rcu: blocking rcu_node structures (internal RCU debug):
  [   11.955022] Task dump for CPU 0:
  [   11.955023] task:systemd-udevd   state:R  running task stack:0 
pid:  383 ppid:   357 flags:0x400a
  [   11.955027] Call Trace:
  [   11.955028]  
  [   11.955030]  ? find_kallsyms_symbol+0x9a/0x1a0
  [   11.955033]  ? amdgpu_ras_query_err_status+0x100/0x100 [amdgpu]
  [   11.955249]  ? tonga_ih_check_soft_reset+0x60/0x60 [amdgpu]
  [   11.955474]  ? module_address_lookup+0x68/0xc0
  [   11.955476]  ? tonga_ih_disable_interrupts+0x70/0x70 [amdgpu]
  [   11.955701]  ? kallsyms_lookup_buildid+0xf7/0x180
  [   11.955704]  ? kallsyms_lookup+0x14/0x20
  [   11.955707]  ? test_for_valid_rec+0x38/0x80
  [   11.955710]  ? change_page_attr_set_clr+0x150/0x1c0
  [   11.955713]  ? ftrace_module_enable+0xa6/0x210
  [   11.955715]  ? load_module+0xa93/0xd30
  [   11.955717]  ? security_kernel_post_read_file+0x5c/0x70
  [   11.955719]  ? kernel_read_file+0x230/0x290
  [   11.955722]  ? __do_sys_finit_module+0xc8/0x140
  [   11.955724]  ? __do_sys_finit_module+0xc8/0x140
  [   11.955727]  ? __x64_sys_finit_module+0x18/0x20
  [   11.955729]  ? do_syscall_64+0x5c/0x90
  [   11.955732]  ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [   11.955735]  
  [   12.030963] rcu: INFO: rcu_preempt detected expedited stalls on 
CPUs/tasks: { 0-... } 44 jiffies s: 49 root: 0x1/.
  [   12.031003] rcu: blocking rcu_node structures (internal RCU debug):
  [   12.031025] Task dump for CPU 0:
  [   12.031027] task:systemd-udevd   state:R  running task stack:0 
pid:  383 ppid:   357 flags:0x400a
  [   12.031031] Call Trace:
  [   12.031033]  
  [   12.031035]  ? find_kallsyms_symbol+0x92/0x1a0
  [   12.031040]  ? amdgpu_ras_query_err_status+0x100/0x100 [amdgpu]
  [   12.031326]  ? gfx_v9_0_fault.isra.0+0xd0/0xd0 [amdgpu]
  [   12.031634]  ? module_address_lookup+0x68/0xc0
  [   12.031638]  ? gfx_v9_0_set_clockgating_state+0xe0/0xe0 [amdgpu]
  [   12.031945]  ? kallsyms_lookup_buildid+0xf7/0x180
  [   12.031949]  ? kallsyms_lookup+0x14/0x20
  [   12.031952]  ? test_for_valid_rec+0x38/0x80
  [   12.031956]  ? change_page_attr_set_clr+0x150/0x1c0
  [   12.031960]  ? ftrace_module_enable+0xa6/0x210
  [   12.031963]  ? load_module+0xa93/0xd30
  [   12.031966]  ? security_kernel_post_read_file+0x5c/0x70
  [   12.031969]  ? kernel_read_file+0x230/0x290
  [   12.031972]  ? __do_sys_finit_module+0xc8/0x140
  [   12.031975]  ? __do_sys_finit_module+0xc8/0x140
  [   12.031979]  ? __x64_sys_finit_module+0x18/0x20
  [   12.031982]  ? do_syscall_64+0x5c/0x90
  [   12.031985]  ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [   12.031989]  
  [   12.106963] rcu: INFO: rcu_preempt detected expedited stalls on 
CPUs/tasks: { 0-... } 63 jiffies s: 49 root: 0x1/.
  [   12.107003] rcu: blocking rcu_node structures (internal RCU debug):
  [   12.107025] Task dump for CPU

[Kernel-packages] [Bug 1984011] Re: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1986718] Re: Jammy update: v5.15.51 upstream stable release

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1986715] Re: Jammy update: v5.15.50 upstream stable release

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1986728] Re: Jammy update: v5.15.53 upstream stable release

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1986724] Re: Jammy update: v5.15.52 upstream stable release

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

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

This bug was fixed in the package linux - 5.15.0-48.54

---
linux (5.15.0-48.54) jammy; urgency=medium

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)

  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume

  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing

  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported

  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable

  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency

  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events
- vdpa/mlx5: Update Control VQ callback information
- s390: remove unneeded 'select BUILD_BIN2C'
- netfilter: nft_dynset: restore set element counter when failing to update
- net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup()
- net/sched: act_api: Notify user space if any actions were flushed before
  error
- net: asix: fix "can't send until first packet is send" issue
- net: bonding: fix possible N

[Kernel-packages] [Bug 1986993] Re: Focal update: v5.4.201 upstream stable release

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

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

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1986999] Re: Focal update: v5.4.203 upstream stable release

This bug was fixed in the package linux - 5.4.0-126.142

---
linux (5.4.0-126.142) focal; urgency=medium

  * focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)

  * [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change shost_printk() to FNIC_FCS_DBG()
- scsi: fnic: Avoid looping in TRANS ETH on unload
- scsi: fnic: Change shost_printk() to FNIC_MAIN_DBG()
- scsi: fnic: Set scsi_set_resid() only for underflow
- scsi: fnic: Validate io_req before others

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

  * Focal update: v5.4.202 upstream stable release (LP: #1986995)
- random: schedule mix_interrupt_randomness() less often
- ALSA: hda/via: Fix missing beep setup
- ALSA: hda/conexant: Fix missing beep setup
- ALSA: hda/realtek - ALC897 headset MIC no sound
- ALSA: hda/realtek: Add quirk for Clevo PD70PNT
- net: openvswitch: fix parsing of nw_proto for IPv6 fragments
- mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing
- ata: libata: add qc->flags in ata_qc_complete_template tracepoint
- dm era: commit metadata in postsuspend after worker stops
- dm mirror log: clear log bits up to BITS_PER_LONG boundary
- random: quiet urandom warning ratelimit suppression message
- USB: serial: option: add Telit LE910Cx 0x1250 composition
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: option: add Quectel RM500K module support
- bpf: Fix request_sock leak in sk lookup helpers
- phy: aquantia: Fix AN when higher speeds than 1G are not advertised
- bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers
- net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
- drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf
- erspan: do not assume transport header is always set
- net/tls: fix tls_sk_proto_close executed repeatedly
- udmabuf: add back sanity check
- x86/xen: Remove undefined behavior in setup_features()
- MIPS: Remove repetitive increase irq_err_count
- afs: Fix dynamic root getattr
- ice: ethtool: advertise 1000M speeds properly
- regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
- igb: Make DMA faster when CPU is active on the PCIe link
- virtio_net: fix xdp_rxq_info bug after suspend/resume
- Revert "net/tls: fix tls_sk_proto_close executed repeatedly"
- gpio: winbond: Fix error code in winbond_gpio_get()
- s390/cpumf: Handle events cycles and instructions identical
- iio: adc: vf610: fix conversion mode sysfs node name
- xhci: turn off port power in shutdown
- usb: chipidea: udc: check request status before setting device address
- iio:chemical:ccs811: rearrange iio trigger get and register
- iio:accel:bma180: rearrange iio trigger get and register
- iio:accel:mxc4005: rearrange iio trigger get and register
- iio: accel: mma8452: ignore the return value of reset operation
- iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up()
- iio: trigger: sysfs: fix use-after-free on remove
- iio: adc: stm32: fix maximum clock rate for stm32mp15x
- iio: adc: axp288: Override TS pin bias current for some models
- xtensa: xtfpga: Fix refcount leak bug in setup
- xtensa: Fix refcount leak bug in time.c
- parisc: Enable ARCH_HAS_STRICT_MODULE_RWX
- powerpc: Enable execve syscall exit tracepoint
- powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address
- powerpc/powernv: wire up rng during setup_arch
- ARM: dts: imx6qdl: correct PU regulator ramp delay
- ARM: exynos: Fix refcount leak in exynos_map_pmu
- soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
- ARM: Fix refcount leak in axxia_boot_secondary
- ARM: cns3xxx: Fix refcount leak in cns3xxx_init
- modpost: fix section mismatch check for

[Kernel-packages] [Bug 1988434] Re: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n

This bug was fixed in the package linux-azure - 5.15.0-1020.25

---
linux-azure (5.15.0-1020.25) jammy; urgency=medium

  * jammy/linux-azure: 5.15.0-1020.25 -proposed tracker (LP: #1987744)

  * Jammy update: v5.15.49 upstream stable release (LP: #1983149)
- [Config] azure: updateconfigs for LIB_MEMNEQ

  * azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n (LP: #1988434)
- [Config] azure: arm64: CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n

  * azure: Replace hyperv_fb with hyperv_drm (LP: #1986713)
- [Packaging] azure: Include hyperv_drm, exclude hyperv_fb from 
linux-modules

  [ Ubuntu: 5.15.0-48.54 ]

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
  * System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
  suspend/resume
  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
luminance (LP: #1978986)
- SAUCE: drm: New function to get luminance range based on static hdr 
metadata
- SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
- SAUCE: drm/i915: Use luminance range calculated during edid parsing
  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
- net/mlx5e: Refactor rx handler of represetor device
- net/mlx5e: Use generic name for the forwarding dev pointer
- net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
- net/mlx5e: Support accept action
- net/mlx5e: Accept action skbedit in the tc actions list
- net/mlx5e: Offload tc rules that redirect to ovs internal port
- net/mlx5e: Offload internal port as encap route device
- net/mlx5e: Enable TC offload for ingress MACVLAN
- net/mlx5e: Add indirect tc offload of ovs internal port
- net/mlx5e: Term table handling of internal port rules
- net/mlx5: Support internal port as decap route device
- net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
- net/mlx5e: TC, Fix memory leak with rules with internal port
- net/mlx5e: Fix skb memory leak when TC classifier action offloads are
  disabled
- net/mlx5e: Fix nullptr on deleting mirroring rule
- net/mlx5e: Avoid implicit modify hdr for decap drop rule
- net/mlx5e: Fix wrong source vport matching on tunnel rule
- net/mlx5e: TC, fix decap fallback to uplink when int port not supported
  * Remove unused variable from i915 psr (LP: #1986798)
- SAUCE: drm/i915/display/psr: Remove unused variable
  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency
  * Jammy update: v5.15.53 upstream stable release (LP: #1986728)
- Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
- drm/amdgpu: To flush tlb for MMHUB of RAVEN series
- ksmbd: set the range of bytes to zero without extending file size in
  FSCTL_ZERO_DATA
- ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA
- ksmbd: use vfs_llseek instead of dereferencing NULL
- ipv6: take care of disable_policy when restoring routes
- net: phy: Don't trigger state machine while in suspend
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX
  S40G)
- nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1
- nvdimm: Fix badblocks clear off-by-one error
- powerpc/prom_init: Fix kernel config grep
- powerpc/book3e: Fix PUD allocation size in map_kernel_page()
- powerpc/bpf: Fix use of user_pt_regs in uapi
- dm raid: fix accesses beyond end of raid member array
- dm raid: fix KASAN warning in raid5_add_disks
- s390/archrandom: simplify back to earlier design and initialize earlier
- SUNRPC: Fix READ_PLUS crasher
- net: rose: fix UAF bugs caused by timer handler
- net: usb: ax88179_178a: Fix packet receiving
- virtio-net: fix race between ndo_open() and virtio_device_ready()
- selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test
- net: dsa: bcm_sf2: force pause link settings
- net: tun: unlink NAPI from device on destruction
- net: tun: stop NAPI when detaching queues
- net: dp83822: disable false carrier interrupt
- net: dp83822: disable rx error interrupt
- RDMA/qedr: Fix reporting QP timeout attribute
- RDMA/cm: Fix memory leak in ib_cm_insert_listen
- linux/dim: Fix divide by 0 in RDMA DIM
- net: usb: asix: do not force pause frames support
- usbnet: fix memory allocation in helpers
- selftests: mptcp: more stable diag tests
- net: ipv6: unexport __init-annotated seg6_hmac_net_init()
- NFSD: restore EINVAL error translation in nfsd_commit()
- vfs: fix copy_file_range() regression in cross-fs copies
- caif_virtio: fix race between virtio_device_ready() and ndo_open()
- PM / devfreq

[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop

2022-09-20 Thread Stefan Bader

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

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

Title:
  ip/nexthop: fix default address selection for connected nexthop

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

Bug description:
  [Impact]

  Packets sent by userland apps are rejected/dropped if the source
  address is not specified and the corresponding route is using a
  connected nexthop object.

  This bug exists since linux v5.3 and has been fixed in v5.19 by the following 
upstream commits:
   - 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
   - cd72e61bad14 ("selftests/net: test nexthop without gw")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
   - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd

  The last commit (v6.0) fixes a regression introduced by the first
  commit.

  [Test Case]

  A detailed test case is explained in the first commit and a self-test
  is added in the second commit.

  [Regression Potential]

  The patch modifies some internal routing states. It has been living in the 
upstream trees for 2 months and the reported regression about icmp redirects 
has been fixed.
  The risk of regression should be contained.

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


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

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

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 1990236

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

Title:
  5.19.0-17.17: kernel NULL pointer dereference, address:
  0084

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up 
unexpectedly.
  Log inspection showed this:

  Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address: 
0084
  Sep 20 09:05:20 zeus kernel: #PF: supervisor read access in kernel mode
  Sep 20 09:05:20 zeus kernel: #PF: error_code(0x) - not-present page
  Sep 20 09:05:20 zeus kernel: PGD 0 P4D 0 
  Sep 20 09:05:20 zeus kernel: Oops:  [#1] PREEMPT SMP PTI
  Sep 20 09:05:20 zeus kernel: CPU: 6 PID: 4291 Comm: slack Tainted: P  
 OE 5.19.0-17-generic #17-Ubuntu
  Sep 20 09:05:20 zeus kernel: Hardware name: HP HP ZBook Studio G5/8427, BIOS 
Q71 Ver. 01.20.00 03/22/2022
  Sep 20 09:05:20 zeus kernel: RIP: 0010:unix_fs_perm.part.0+0x50/0x1e0
  Sep 20 09:05:20 zeus kernel: Code: 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8b 
81 08 03 00 00 89 75 8c 48 85 c0 0f 85 b0 00 00 00 48 8b 91 70 02 00 00 48 8d 
7d a0 <8b> 8a 84 00 00 00 0f b7 92 80 00 00 00 48 c7 45 9c 00 00 00 00 48
  Sep 20 09:05:20 zeus kernel: RSP: 0018:b014c7eb3ce0 EFLAGS: 00010246
  Sep 20 09:05:20 zeus kernel: RAX:  RBX: 94c0e0c7adb0 RCX: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: RDX:  RSI: 0004 RDI: 
b014c7eb3cf8
  Sep 20 09:05:20 zeus kernel: RBP: b014c7eb3d58 R08: 0002 R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11:  R12: 
0004
  Sep 20 09:05:20 zeus kernel: R13: 0002 R14: a044fe92 R15: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: FS:  7f6b47927c00() 
GS:94c47bd8() knlGS:
  Sep 20 09:05:20 zeus kernel: CS:  0010 DS:  ES:  CR0: 80050033
  Sep 20 09:05:20 zeus kernel: CR2: 0084 CR3: 00013e1b4003 CR4: 
003706e0
  Sep 20 09:05:20 zeus kernel: DR0:  DR1:  DR2: 

  Sep 20 09:05:20 zeus kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  Sep 20 09:05:20 zeus kernel: Call Trace:
  Sep 20 09:05:20 zeus kernel:  
  Sep 20 09:05:20 zeus kernel:  aa_unix_file_perm+0x2f2/0x400
  Sep 20 09:05:20 zeus kernel:  aa_sock_file_perm+0x5c/0x80
  Sep 20 09:05:20 zeus kernel:  aa_file_perm+0x288/0x2e0
  Sep 20 09:05:20 zeus kernel:  apparmor_file_permission+0x71/0x1a0
  Sep 20 09:05:20 zeus kernel:  security_file_permission+0x36/0x70
  Sep 20 09:05:20 zeus kernel:  rw_verify_area+0x35/0x80
  Sep 20 09:05:20 zeus kernel:  vfs_read+0x6c/0x1b0
  Sep 20 09:05:20 zeus kernel:  ksys_read+0xc9/0x100
  Sep 20 09:05:20 zeus kernel:  __x64_sys_read+0x19/0x30
  Sep 20 09:05:20 zeus kernel:  do_syscall_64+0x58/0x90
  Sep 20 09:05:20 zeus kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Sep 20 09:05:20 zeus kernel: RIP: 0033:0x7f6b46c68474
  Sep 20 09:05:20 zeus kernel: Code: 84 00 00 00 00 00 41 54 55 49 89 d4 53 48 
89 f5 89 fb 48 83 ec 10 e8 8b fc ff ff 4c 89 e2 41 89 c0 48 89 ee 89 df 31 c0 
0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 c7 fc ff ff 48
  Sep 20 09:05:20 zeus kernel: RSP: 002b:7ffc54391700 EFLAGS: 0246 
ORIG_RAX: 
  Sep 20 09:05:20 zeus kernel: RAX: ffda RBX: 0028 RCX: 
7f6b46c68474
  Sep 20 09:05:20 zeus kernel: RDX: 0008 RSI: 7ffc54391800 RDI: 
0028
  Sep 20 09:05:20 zeus kernel: RBP: 7ffc54391800 R08:  R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11: 0246 R12: 
0008
  Sep 20 09:05:20 zeus kernel: R13: 0028 R14: 7ffc54391800 R15: 


  I'll attach the full log.

  The presence apparmor in the trace correlates with the ton of permission 
problem that this kernel introduced (Chrome and Slack no longer starting, see 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064).
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  DistroRelease

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

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 1990240

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

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

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  New
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
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  New

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] [NEW] Intel graphic driver is not probing[8086:468b]

Public bug reported:

[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.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

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

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-5.17 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

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


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

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

** Description changed:

  [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.

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

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

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

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

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

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

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

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

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  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
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

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

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

  [Test]
  Verified on the target machine.

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

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


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

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

Public bug reported:

[Impact]

[Fix]

[Test]

[Where problems could occur]

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

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


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

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

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

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

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  [Fix]

  [Test]

  [Where problems could occur]

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 1990236] Re: 5.19.0-17.17: kernel NULL pointer dereference, address: 0000000000000084

Note: the bot wants me to run apport on this bug, however I can not run
apport on the broken kernel and running it on the working kernel is
likely to produce wrong logs.

Please look at the boot log that I attached manually instead.

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

Title:
  5.19.0-17.17: kernel NULL pointer dereference, address:
  0084

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up 
unexpectedly.
  Log inspection showed this:

  Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address: 
0084
  Sep 20 09:05:20 zeus kernel: #PF: supervisor read access in kernel mode
  Sep 20 09:05:20 zeus kernel: #PF: error_code(0x) - not-present page
  Sep 20 09:05:20 zeus kernel: PGD 0 P4D 0 
  Sep 20 09:05:20 zeus kernel: Oops:  [#1] PREEMPT SMP PTI
  Sep 20 09:05:20 zeus kernel: CPU: 6 PID: 4291 Comm: slack Tainted: P  
 OE 5.19.0-17-generic #17-Ubuntu
  Sep 20 09:05:20 zeus kernel: Hardware name: HP HP ZBook Studio G5/8427, BIOS 
Q71 Ver. 01.20.00 03/22/2022
  Sep 20 09:05:20 zeus kernel: RIP: 0010:unix_fs_perm.part.0+0x50/0x1e0
  Sep 20 09:05:20 zeus kernel: Code: 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8b 
81 08 03 00 00 89 75 8c 48 85 c0 0f 85 b0 00 00 00 48 8b 91 70 02 00 00 48 8d 
7d a0 <8b> 8a 84 00 00 00 0f b7 92 80 00 00 00 48 c7 45 9c 00 00 00 00 48
  Sep 20 09:05:20 zeus kernel: RSP: 0018:b014c7eb3ce0 EFLAGS: 00010246
  Sep 20 09:05:20 zeus kernel: RAX:  RBX: 94c0e0c7adb0 RCX: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: RDX:  RSI: 0004 RDI: 
b014c7eb3cf8
  Sep 20 09:05:20 zeus kernel: RBP: b014c7eb3d58 R08: 0002 R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11:  R12: 
0004
  Sep 20 09:05:20 zeus kernel: R13: 0002 R14: a044fe92 R15: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: FS:  7f6b47927c00() 
GS:94c47bd8() knlGS:
  Sep 20 09:05:20 zeus kernel: CS:  0010 DS:  ES:  CR0: 80050033
  Sep 20 09:05:20 zeus kernel: CR2: 0084 CR3: 00013e1b4003 CR4: 
003706e0
  Sep 20 09:05:20 zeus kernel: DR0:  DR1:  DR2: 

  Sep 20 09:05:20 zeus kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  Sep 20 09:05:20 zeus kernel: Call Trace:
  Sep 20 09:05:20 zeus kernel:  
  Sep 20 09:05:20 zeus kernel:  aa_unix_file_perm+0x2f2/0x400
  Sep 20 09:05:20 zeus kernel:  aa_sock_file_perm+0x5c/0x80
  Sep 20 09:05:20 zeus kernel:  aa_file_perm+0x288/0x2e0
  Sep 20 09:05:20 zeus kernel:  apparmor_file_permission+0x71/0x1a0
  Sep 20 09:05:20 zeus kernel:  security_file_permission+0x36/0x70
  Sep 20 09:05:20 zeus kernel:  rw_verify_area+0x35/0x80
  Sep 20 09:05:20 zeus kernel:  vfs_read+0x6c/0x1b0
  Sep 20 09:05:20 zeus kernel:  ksys_read+0xc9/0x100
  Sep 20 09:05:20 zeus kernel:  __x64_sys_read+0x19/0x30
  Sep 20 09:05:20 zeus kernel:  do_syscall_64+0x58/0x90
  Sep 20 09:05:20 zeus kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Sep 20 09:05:20 zeus kernel: RIP: 0033:0x7f6b46c68474
  Sep 20 09:05:20 zeus kernel: Code: 84 00 00 00 00 00 41 54 55 49 89 d4 53 48 
89 f5 89 fb 48 83 ec 10 e8 8b fc ff ff 4c 89 e2 41 89 c0 48 89 ee 89 df 31 c0 
0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 c7 fc ff ff 48
  Sep 20 09:05:20 zeus kernel: RSP: 002b:7ffc54391700 EFLAGS: 0246 
ORIG_RAX: 
  Sep 20 09:05:20 zeus kernel: RAX: ffda RBX: 0028 RCX: 
7f6b46c68474
  Sep 20 09:05:20 zeus kernel: RDX: 0008 RSI: 7ffc54391800 RDI: 
0028
  Sep 20 09:05:20 zeus kernel: RBP: 7ffc54391800 R08:  R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11: 0246 R12: 
0008
  Sep 20 09:05:20 zeus kernel: R13: 0028 R14: 7ffc54391800 R15: 


  I'll attach the full log.

  The presence apparmor in the trace correlates with the ton of permission 
problem that this kernel introduced (Chrome and Slack no longer starting, see 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064).
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2017-09-26 (1819 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  kinetic
  Uname: Linux 5.18.8-051808-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatu

[Kernel-packages] [Bug 1990236] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1990236/+attachment/5617328/+files/ProcEnviron.txt

** 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/1990236

Title:
  5.19.0-17.17: kernel NULL pointer dereference, address:
  0084

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up 
unexpectedly.
  Log inspection showed this:

  Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address: 
0084
  Sep 20 09:05:20 zeus kernel: #PF: supervisor read access in kernel mode
  Sep 20 09:05:20 zeus kernel: #PF: error_code(0x) - not-present page
  Sep 20 09:05:20 zeus kernel: PGD 0 P4D 0 
  Sep 20 09:05:20 zeus kernel: Oops:  [#1] PREEMPT SMP PTI
  Sep 20 09:05:20 zeus kernel: CPU: 6 PID: 4291 Comm: slack Tainted: P  
 OE 5.19.0-17-generic #17-Ubuntu
  Sep 20 09:05:20 zeus kernel: Hardware name: HP HP ZBook Studio G5/8427, BIOS 
Q71 Ver. 01.20.00 03/22/2022
  Sep 20 09:05:20 zeus kernel: RIP: 0010:unix_fs_perm.part.0+0x50/0x1e0
  Sep 20 09:05:20 zeus kernel: Code: 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8b 
81 08 03 00 00 89 75 8c 48 85 c0 0f 85 b0 00 00 00 48 8b 91 70 02 00 00 48 8d 
7d a0 <8b> 8a 84 00 00 00 0f b7 92 80 00 00 00 48 c7 45 9c 00 00 00 00 48
  Sep 20 09:05:20 zeus kernel: RSP: 0018:b014c7eb3ce0 EFLAGS: 00010246
  Sep 20 09:05:20 zeus kernel: RAX:  RBX: 94c0e0c7adb0 RCX: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: RDX:  RSI: 0004 RDI: 
b014c7eb3cf8
  Sep 20 09:05:20 zeus kernel: RBP: b014c7eb3d58 R08: 0002 R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11:  R12: 
0004
  Sep 20 09:05:20 zeus kernel: R13: 0002 R14: a044fe92 R15: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: FS:  7f6b47927c00() 
GS:94c47bd8() knlGS:
  Sep 20 09:05:20 zeus kernel: CS:  0010 DS:  ES:  CR0: 80050033
  Sep 20 09:05:20 zeus kernel: CR2: 0084 CR3: 00013e1b4003 CR4: 
003706e0
  Sep 20 09:05:20 zeus kernel: DR0:  DR1:  DR2: 

  Sep 20 09:05:20 zeus kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  Sep 20 09:05:20 zeus kernel: Call Trace:
  Sep 20 09:05:20 zeus kernel:  
  Sep 20 09:05:20 zeus kernel:  aa_unix_file_perm+0x2f2/0x400
  Sep 20 09:05:20 zeus kernel:  aa_sock_file_perm+0x5c/0x80
  Sep 20 09:05:20 zeus kernel:  aa_file_perm+0x288/0x2e0
  Sep 20 09:05:20 zeus kernel:  apparmor_file_permission+0x71/0x1a0
  Sep 20 09:05:20 zeus kernel:  security_file_permission+0x36/0x70
  Sep 20 09:05:20 zeus kernel:  rw_verify_area+0x35/0x80
  Sep 20 09:05:20 zeus kernel:  vfs_read+0x6c/0x1b0
  Sep 20 09:05:20 zeus kernel:  ksys_read+0xc9/0x100
  Sep 20 09:05:20 zeus kernel:  __x64_sys_read+0x19/0x30
  Sep 20 09:05:20 zeus kernel:  do_syscall_64+0x58/0x90
  Sep 20 09:05:20 zeus kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Sep 20 09:05:20 zeus kernel: RIP: 0033:0x7f6b46c68474
  Sep 20 09:05:20 zeus kernel: Code: 84 00 00 00 00 00 41 54 55 49 89 d4 53 48 
89 f5 89 fb 48 83 ec 10 e8 8b fc ff ff 4c 89 e2 41 89 c0 48 89 ee 89 df 31 c0 
0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 c7 fc ff ff 48
  Sep 20 09:05:20 zeus kernel: RSP: 002b:7ffc54391700 EFLAGS: 0246 
ORIG_RAX: 
  Sep 20 09:05:20 zeus kernel: RAX: ffda RBX: 0028 RCX: 
7f6b46c68474
  Sep 20 09:05:20 zeus kernel: RDX: 0008 RSI: 7ffc54391800 RDI: 
0028
  Sep 20 09:05:20 zeus kernel: RBP: 7ffc54391800 R08:  R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11: 0246 R12: 
0008
  Sep 20 09:05:20 zeus kernel: R13: 0028 R14: 7ffc54391800 R15: 


  I'll attach the full log.

  The presence apparmor in the trace correlates with the ton of permission 
problem that this kernel introduced (Chrome and Slack no longer starting, see 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064).
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2017-09-26 (1819 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  kinetic
  Uname: Linux 5.18.8-051808-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to kinetic

[Kernel-packages] [Bug 1990236] Re: 5.19.0-17.17: kernel NULL pointer dereference, address: 0000000000000084

apport information

** Tags added: apport-collected kinetic

** Description changed:

  After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up 
unexpectedly.
  Log inspection showed this:
  
  Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address: 
0084
  Sep 20 09:05:20 zeus kernel: #PF: supervisor read access in kernel mode
  Sep 20 09:05:20 zeus kernel: #PF: error_code(0x) - not-present page
  Sep 20 09:05:20 zeus kernel: PGD 0 P4D 0 
  Sep 20 09:05:20 zeus kernel: Oops:  [#1] PREEMPT SMP PTI
  Sep 20 09:05:20 zeus kernel: CPU: 6 PID: 4291 Comm: slack Tainted: P  
 OE 5.19.0-17-generic #17-Ubuntu
  Sep 20 09:05:20 zeus kernel: Hardware name: HP HP ZBook Studio G5/8427, BIOS 
Q71 Ver. 01.20.00 03/22/2022
  Sep 20 09:05:20 zeus kernel: RIP: 0010:unix_fs_perm.part.0+0x50/0x1e0
  Sep 20 09:05:20 zeus kernel: Code: 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8b 
81 08 03 00 00 89 75 8c 48 85 c0 0f 85 b0 00 00 00 48 8b 91 70 02 00 00 48 8d 
7d a0 <8b> 8a 84 00 00 00 0f b7 92 80 00 00 00 48 c7 45 9c 00 00 00 00 48
  Sep 20 09:05:20 zeus kernel: RSP: 0018:b014c7eb3ce0 EFLAGS: 00010246
  Sep 20 09:05:20 zeus kernel: RAX:  RBX: 94c0e0c7adb0 RCX: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: RDX:  RSI: 0004 RDI: 
b014c7eb3cf8
  Sep 20 09:05:20 zeus kernel: RBP: b014c7eb3d58 R08: 0002 R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11:  R12: 
0004
  Sep 20 09:05:20 zeus kernel: R13: 0002 R14: a044fe92 R15: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: FS:  7f6b47927c00() 
GS:94c47bd8() knlGS:
  Sep 20 09:05:20 zeus kernel: CS:  0010 DS:  ES:  CR0: 80050033
  Sep 20 09:05:20 zeus kernel: CR2: 0084 CR3: 00013e1b4003 CR4: 
003706e0
  Sep 20 09:05:20 zeus kernel: DR0:  DR1:  DR2: 

  Sep 20 09:05:20 zeus kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  Sep 20 09:05:20 zeus kernel: Call Trace:
  Sep 20 09:05:20 zeus kernel:  
  Sep 20 09:05:20 zeus kernel:  aa_unix_file_perm+0x2f2/0x400
  Sep 20 09:05:20 zeus kernel:  aa_sock_file_perm+0x5c/0x80
  Sep 20 09:05:20 zeus kernel:  aa_file_perm+0x288/0x2e0
  Sep 20 09:05:20 zeus kernel:  apparmor_file_permission+0x71/0x1a0
  Sep 20 09:05:20 zeus kernel:  security_file_permission+0x36/0x70
  Sep 20 09:05:20 zeus kernel:  rw_verify_area+0x35/0x80
  Sep 20 09:05:20 zeus kernel:  vfs_read+0x6c/0x1b0
  Sep 20 09:05:20 zeus kernel:  ksys_read+0xc9/0x100
  Sep 20 09:05:20 zeus kernel:  __x64_sys_read+0x19/0x30
  Sep 20 09:05:20 zeus kernel:  do_syscall_64+0x58/0x90
  Sep 20 09:05:20 zeus kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Sep 20 09:05:20 zeus kernel: RIP: 0033:0x7f6b46c68474
  Sep 20 09:05:20 zeus kernel: Code: 84 00 00 00 00 00 41 54 55 49 89 d4 53 48 
89 f5 89 fb 48 83 ec 10 e8 8b fc ff ff 4c 89 e2 41 89 c0 48 89 ee 89 df 31 c0 
0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 c7 fc ff ff 48
  Sep 20 09:05:20 zeus kernel: RSP: 002b:7ffc54391700 EFLAGS: 0246 
ORIG_RAX: 
  Sep 20 09:05:20 zeus kernel: RAX: ffda RBX: 0028 RCX: 
7f6b46c68474
  Sep 20 09:05:20 zeus kernel: RDX: 0008 RSI: 7ffc54391800 RDI: 
0028
  Sep 20 09:05:20 zeus kernel: RBP: 7ffc54391800 R08:  R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11: 0246 R12: 
0008
  Sep 20 09:05:20 zeus kernel: R13: 0028 R14: 7ffc54391800 R15: 

  
  I'll attach the full log.
  
- The presence apparmor in the trace correlates with the ton of permission
- problem that this kernel introduced (Chrome and Slack no longer
- starting, see
- https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064).
+ The presence apparmor in the trace correlates with the ton of permission 
problem that this kernel introduced (Chrome and Slack no longer starting, see 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.0-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2017-09-26 (1819 days ago)
+ InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ Tags:  kinetic
+ Uname: Linux 5.18.8-051808-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to kinetic on 2022-05-22 (120 days ago)
+ UserGroups: cdrom dialout dip docker libvirt lpadmin lxd plugdev render 
sambashare src sudo tss tty uucp video wireshark
+ _MarkForUpload: True

** Attachment added: "Proc

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

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 1990236

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

Title:
  5.19.0-17.17: kernel NULL pointer dereference, address:
  0084

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up 
unexpectedly.
  Log inspection showed this:

  Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address: 
0084
  Sep 20 09:05:20 zeus kernel: #PF: supervisor read access in kernel mode
  Sep 20 09:05:20 zeus kernel: #PF: error_code(0x) - not-present page
  Sep 20 09:05:20 zeus kernel: PGD 0 P4D 0 
  Sep 20 09:05:20 zeus kernel: Oops:  [#1] PREEMPT SMP PTI
  Sep 20 09:05:20 zeus kernel: CPU: 6 PID: 4291 Comm: slack Tainted: P  
 OE 5.19.0-17-generic #17-Ubuntu
  Sep 20 09:05:20 zeus kernel: Hardware name: HP HP ZBook Studio G5/8427, BIOS 
Q71 Ver. 01.20.00 03/22/2022
  Sep 20 09:05:20 zeus kernel: RIP: 0010:unix_fs_perm.part.0+0x50/0x1e0
  Sep 20 09:05:20 zeus kernel: Code: 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8b 
81 08 03 00 00 89 75 8c 48 85 c0 0f 85 b0 00 00 00 48 8b 91 70 02 00 00 48 8d 
7d a0 <8b> 8a 84 00 00 00 0f b7 92 80 00 00 00 48 c7 45 9c 00 00 00 00 48
  Sep 20 09:05:20 zeus kernel: RSP: 0018:b014c7eb3ce0 EFLAGS: 00010246
  Sep 20 09:05:20 zeus kernel: RAX:  RBX: 94c0e0c7adb0 RCX: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: RDX:  RSI: 0004 RDI: 
b014c7eb3cf8
  Sep 20 09:05:20 zeus kernel: RBP: b014c7eb3d58 R08: 0002 R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11:  R12: 
0004
  Sep 20 09:05:20 zeus kernel: R13: 0002 R14: a044fe92 R15: 
94be5003ac00
  Sep 20 09:05:20 zeus kernel: FS:  7f6b47927c00() 
GS:94c47bd8() knlGS:
  Sep 20 09:05:20 zeus kernel: CS:  0010 DS:  ES:  CR0: 80050033
  Sep 20 09:05:20 zeus kernel: CR2: 0084 CR3: 00013e1b4003 CR4: 
003706e0
  Sep 20 09:05:20 zeus kernel: DR0:  DR1:  DR2: 

  Sep 20 09:05:20 zeus kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  Sep 20 09:05:20 zeus kernel: Call Trace:
  Sep 20 09:05:20 zeus kernel:  
  Sep 20 09:05:20 zeus kernel:  aa_unix_file_perm+0x2f2/0x400
  Sep 20 09:05:20 zeus kernel:  aa_sock_file_perm+0x5c/0x80
  Sep 20 09:05:20 zeus kernel:  aa_file_perm+0x288/0x2e0
  Sep 20 09:05:20 zeus kernel:  apparmor_file_permission+0x71/0x1a0
  Sep 20 09:05:20 zeus kernel:  security_file_permission+0x36/0x70
  Sep 20 09:05:20 zeus kernel:  rw_verify_area+0x35/0x80
  Sep 20 09:05:20 zeus kernel:  vfs_read+0x6c/0x1b0
  Sep 20 09:05:20 zeus kernel:  ksys_read+0xc9/0x100
  Sep 20 09:05:20 zeus kernel:  __x64_sys_read+0x19/0x30
  Sep 20 09:05:20 zeus kernel:  do_syscall_64+0x58/0x90
  Sep 20 09:05:20 zeus kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Sep 20 09:05:20 zeus kernel: RIP: 0033:0x7f6b46c68474
  Sep 20 09:05:20 zeus kernel: Code: 84 00 00 00 00 00 41 54 55 49 89 d4 53 48 
89 f5 89 fb 48 83 ec 10 e8 8b fc ff ff 4c 89 e2 41 89 c0 48 89 ee 89 df 31 c0 
0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 c7 fc ff ff 48
  Sep 20 09:05:20 zeus kernel: RSP: 002b:7ffc54391700 EFLAGS: 0246 
ORIG_RAX: 
  Sep 20 09:05:20 zeus kernel: RAX: ffda RBX: 0028 RCX: 
7f6b46c68474
  Sep 20 09:05:20 zeus kernel: RDX: 0008 RSI: 7ffc54391800 RDI: 
0028
  Sep 20 09:05:20 zeus kernel: RBP: 7ffc54391800 R08:  R09: 

  Sep 20 09:05:20 zeus kernel: R10:  R11: 0246 R12: 
0008
  Sep 20 09:05:20 zeus kernel: R13: 0028 R14: 7ffc54391800 R15: 


  I'll attach the full log.

  The presence apparmor in the trace correlates with the ton of
  permission problem that this kernel introduced (Chrome and Slack no
  longer starting, see
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064).

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


-- 
Mailing list: http

[Kernel-packages] [Bug 1990236] [NEW] 5.19.0-17.17: kernel NULL pointer dereference, address: 0000000000000084