[Kernel-packages] [Bug 2008992] [NEW] suspend fails on Dell XPS 9350

[John Steele Scott]

Public bug reported:

After upgrading to 5.17.0-1027-oem, my laptop fails to suspend. Instead
it turns off.

Journald output:

Mar 02 17:31:47 nugget systemd[1]: NetworkManager-dispatcher.service: 
Deactivated successfully.
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.3571] manager: 
sleep: sleep requested (sleeping: no  enabled: yes)
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.3575] device 
(p2p-dev-wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Mar 02 17:31:53 nugget ModemManager[1061]:   [sleep-monitor] system is 
about to suspend
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.3593] manager: 
NetworkManager state is now ASLEEP
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.3602] device 
(wlp58s0): state change: activated -> deactivating (reason 'sleeping', 
sys-iface-state: 'managed')
Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 
pid=940 comm="/usr/sbin/NetworkManager -->
Mar 02 17:31:53 nugget systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Mar 02 17:31:53 nugget dbus-daemon[939]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
Mar 02 17:31:53 nugget systemd[1]: Started Network Manager Script Dispatcher 
Service.
Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DISCONNECTED 
bssid=6c:70:9f:ea:29:9f reason=3 locally_generated=1
Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY 
clear_all
Mar 02 17:31:53 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.4826] device 
(wlp58s0): supplicant interface state: completed -> disconnected
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.4834] device 
(wlp58s0): state change: deactivating -> disconnected (reason 'sleeping', 
sys-iface-state: 'managed')
Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for 
fe80::7389:c602:b63c:8452 on wlp58s0.
Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on 
interface wlp58s0.IPv6 with address fe80::7389:c602:b63c:8452.
Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv6 no longer 
relevant for mDNS.
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.5110] dhcp4 
(wlp58s0): canceled DHCP transaction
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.5111] dhcp4 
(wlp58s0): activation: beginning transaction (timeout in 45 seconds)
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.5112] dhcp4 
(wlp58s0): state changed no lease
Mar 02 17:31:53 nugget avahi-daemon[932]: Withdrawing address record for 
192.168.1.217 on wlp58s0.
Mar 02 17:31:53 nugget avahi-daemon[932]: Leaving mDNS multicast group on 
interface wlp58s0.IPv4 with address 192.168.1.217.
Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset search 
domain list.
Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client set default 
route setting: no
Mar 02 17:31:53 nugget avahi-daemon[932]: Interface wlp58s0.IPv4 no longer 
relevant for mDNS.
Mar 02 17:31:53 nugget systemd-resolved[806]: wlp58s0: Bus client reset DNS 
server list.
Mar 02 17:31:53 nugget NetworkManager[940]:   [1677740513.5824] device 
(wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: 
CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:31:54 nugget wpa_supplicant[981]: p2p-dev-wlp58s0: 
CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit 
ifname=p2p-dev-wlp58s0 disabled_11b_rates=0
Mar 02 17:31:54 nugget systemd[1]: Reached target Sleep.
Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY 
clear_all
Mar 02 17:31:54 nugget systemd[1]: Starting Record successful boot for GRUB...
Mar 02 17:31:54 nugget systemd[1]: Starting System Suspend...
Mar 02 17:31:54 nugget wpa_supplicant[981]: wlp58s0: CTRL-EVENT-DSCP-POLICY 
clear_all
Mar 02 17:31:54 nugget wpa_supplicant[981]: nl80211: deinit ifname=wlp58s0 
disabled_11b_rates=0
Mar 02 17:31:54 nugget systemd[1]: grub-common.service: Deactivated 
successfully.
Mar 02 17:31:54 nugget systemd[1]: Finished Record successful boot for GRUB.
Mar 02 17:31:54 nugget systemd[1]: Starting GRUB failed boot detection...
Mar 02 17:31:54 nugget systemd[1]: grub-initrd-fallback.service: Deactivated 
successfully.
Mar 02 17:31:54 nugget systemd[1]: Finished GRUB failed boot detection.
Mar 02 17:31:54 nugget systemd-sleep[3429]: Entering sleep state 'suspend'...
Mar 02 17:31:54 nugget kernel: PM: suspend entry (deep)


Suspend was working find when I was running 5.17.0-1021-oem.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1027-oem 5.17.0-1027.28
ProcVers

[Kernel-packages] [Bug 2006895] Re: kernel 5.15.0-60-generic out of memory on boot

[fantaz]

After the upgrade of grub-efi-amd64-bin 2.06-2ubuntu14.1 and 
grub-efi-amd64-signed 2.06-2ubuntu14.1,
everything runs as it should. 
Oh, I had also installed the updated kernel - 5.15.0-67-generic x86_64

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

Title:
  kernel 5.15.0-60-generic out of memory on boot

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Using kubuntu 22.04, and after a kernel update and after a reboot, the 
machine just spits out the "out of memory" message. The 5.15.0-58-generic works 
just fine.
  For what it's worth, I had the similar issue with the kernel prior to 58. 
Additionally, grub-efi-amd64-bin, grub-efi-amd64-signed, 
ubuntu-advantage-tools, update-notifier-common, software-properties-common and 
software-properties-qt updates are held back.

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


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

[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode

[koba]

as per Cyrus, 
'''
kernel 5.15.0-68.75 verified pass.

Kernel: 5.15.0-68.75
SKU: Alxd-Low-DVT-C1_202209-30619
Monitor: PA238Q (FHD)
Monitor: Gechi On-Lap 1303 (FHD)
'''

Cyrus, thanks

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

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

Title:
  RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror
  mode

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-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The Screen is shaking connected monitor to Onboard HDMI port.

  [Fix]
  The interlaced mode is not supported for Intel Gen 12 onwards.
  Disable interlaced mode for DP&HDMI on Display >= 12.

  Due to schedule, SRU for OEM kernels first.
  After these patches are merged to mainline/drmtip kernel, will SRU for 
generic kernels.

  [Test Case]
  1.Connected two external Monitor to the onboard HDMI/DP port .
  2.Boot OS.
  2.set mirror mode. (onboard HDMI / onboard DP)
  3.check if screen shakes.

  [Where problems could occur]
  Low, Remove interlace support for Display >= 12 so it wouldn't cause a 
regression.

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


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

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

[Daniel van Vugt]

Also happens on (all?) lunar machines with the 5.19 kernel.

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

** Tags added: lunar

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

Title:
  blacklist: Problem blacklisting hash

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

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

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

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


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

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  blacklist: Problem blacklisting hash

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

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

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

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


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

[Kernel-packages] [Bug 2007516] Re: screen flicker after PSR2 enabled

[Kai-Chuan Hsieh]

** Summary changed:

- XPS 9320 screen flicker on UHD panel 3840x2400
+ screen flicker after PSR2 enabled

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

Title:
  screen flicker after PSR2 enabled

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing

[Po-Hsu Lin]

Didn't see this failure with B-azure 4.15.0-1162.177

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

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

Title:
  rtcpie in timers from ubuntu_kernel_selftests randomly failing

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  Node: Standard_D11_v2
  Kernel: 4.18.0-1008.8~18.04.1

   selftests: timers: rtcpie
   
   Periodic IRQ rate is 1024Hz.
   Counting 20 interrupts at:
   2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   32Hz:1 2 3 4 5 6 7
   PIE delta error: 0.034667 should be close to 0.031250
  181.  01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: 
timers: rtcpie [FAIL]

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


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

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

[Daniel van Vugt]

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

Ubuntu 21.04 is no longer supported but the same issue is being tracked
in bug 1980831.

** This bug has been marked a duplicate of bug 1980831
   GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* 
Waiting for fences timed out!

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen and
  [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences
  timed out!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi

[Kernel-packages] [Bug 1950205] Re: Some shaders can crash the amdgpu kernel module, tainting

[Daniel van Vugt]

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

Ubuntu 21.10 is no longer supported but the same issue is being tracked
in bug 1980831.

** This bug has been marked a duplicate of bug 1980831
   GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* 
Waiting for fences timed out!

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

Title:
  Some shaders can crash the amdgpu kernel module, tainting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  I am experiencing, at random, the AMD-GPU "fences timed out!" bug
  reported previously as being either a kernel issue
  (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa
  (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The
  later was apparently fixed in 21.2.4 -- I have experienced it both on
  the stock mesa package versions current in play in 21.10 and the
  "bleeding edge" git-based builds. It is difficult to reproduce
  deterministically. For me, at present, roleplaying game Pathfinder:
  Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine
  version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far
  more infrequently on the lowest graphics settings, but occasionally
  absolutely deterministically at certain points (I have a save game
  that can do this in the highly unlikely event that anyone wants to
  take me up on the issue and has the GOG game -- email me at
  jack.mil...@physics.org).

  This manifests as extreme screen corruption requiring a restart of at
  a minimum lightdm to fix, and more likely the whole computer. Memory
  issues can occur either on the card or on the host, namely:

  [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for 
fences timed out!
  [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, 
signaled seq=112591, emitted seq=112593
  [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984
  [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin!
  [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for 
fences timed out!
  [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK!
  [ 1213.509424] amdgpu: cp is busy, skip halt cp
  [ 1213.95] amdgpu: rlc is busy, skip halt rlc
  [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset
  [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to 
resume
  [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000).
  [ 1214.427335] [drm] VRAM is lost due to GPU reset!
  [ 1214.600175] [ cut here ]
  [ 1214.600178] amdgpu :08:00.0: 
drm_WARN_ON(atomic_read(&vblank->refcount) == 0)
  [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 
drm_vblank_put+0xef/0x100 [drm]
  [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype 
br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) 
binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter 
xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat 
nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue 
nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep 
overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) 
zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) 
snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi 
edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec 
kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm 
btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi
  [ 1214.600304]  ecdh_generic joydev mac80211 snd_seq ecc input_leds 
snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp 
efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 
hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple 
hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap 
amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea 
aesni_intel sysfillrect sysimgblt fb_sys_fops cec crypto_simd rc_core cryptd 
drm r8169 ahci i2c_piix4 xhci_pci libahci xhci_pci_renesas realtek wmi
  [ 1214.600336] CPU: 7 PID: 0 Com

[Kernel-packages] [Bug 2008599] Re: Kernel Trace with Graphics Crash

[Daniel van Vugt]

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

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2282
   https://gitlab.freedesktop.org/drm/amd/-/issues/2282

** Changed in: linux
 Remote watch: gitlab.freedesktop.org/drm/amd/-/issues #2135 => 
gitlab.freedesktop.org/drm/amd/-/issues #2282

** This bug has been marked a duplicate of bug 1980831
   GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* 
Waiting for fences timed out!

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

Title:
  Kernel Trace with Graphics Crash

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

Bug description:
  System Info:
  
  Kernel: 5.19.0-31-generic
  Release: kinetic
  CPU: AMD Ryzen 5 2600 Six-Core Processor
  GPU: AMD Radeon RX Vega

  Symptoms:
  =
  Graphics crash - all monitors go black. No reproducer, but this happens once 
or twice a week.

  This bears strong resemblance to LP 1980831 and [1], with the addition
  of kernel call traces in dmesg (see attached logs).

  Feb 25 17:51:20 arc kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

  With the addition of a few different call traces in the kernel log
  (this is the first one):

  Feb 25 17:53:42 arc kernel: Workqueue: amdgpu-reset-dev 
drm_sched_job_timedout [gpu_sched]
  Feb 25 17:53:42 arc kernel: Call Trace:
  Feb 25 17:53:42 arc kernel:  
  Feb 25 17:53:42 arc kernel:  show_stack+0x4e/0x61
  Feb 25 17:53:42 arc kernel:  dump_stack_lvl+0x4a/0x6f
  Feb 25 17:53:42 arc kernel:  dump_stack+0x10/0x18
  Feb 25 17:53:42 arc kernel:  amdgpu_do_asic_reset+0x2b/0x45e [amdgpu]
  Feb 25 17:53:42 arc kernel:  amdgpu_device_gpu_recover_imp.cold+0x748/0x7f0 
[amdgpu]
  Feb 25 17:53:42 arc kernel:  amdgpu_job_timedout+0x196/0x1d0 [amdgpu]
  Feb 25 17:53:42 arc kernel:  ? finish_task_switch.isra.0+0x85/0x290
  Feb 25 17:53:42 arc kernel:  drm_sched_job_timedout+0x70/0x120 [gpu_sched]
  Feb 25 17:53:42 arc kernel:  process_one_work+0x225/0x400
  Feb 25 17:53:42 arc kernel:  worker_thread+0x50/0x3e0
  Feb 25 17:53:42 arc kernel:  ? rescuer_thread+0x3c0/0x3c0
  Feb 25 17:53:42 arc kernel:  kthread+0xe9/0x110
  Feb 25 17:53:42 arc kernel:  ? kthread_complete_and_exit+0x20/0x20
  Feb 25 17:53:42 arc kernel:  ret_from_fork+0x22/0x30
  Feb 25 17:53:42 arc kernel:  

  I don't have a reproducer, but have noticed infrequent graphics
  crashes since upgrading to Kinetic. I see mentioned in [1] that this
  is fixed in upstream 6.0.8, so I was going to try upgrading to Lunar
  to test this out, however I see that Lunar's version is 5.19.0.21.21.

  [1] https://gitlab.freedesktop.org/drm/amd/-/issues/2135

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

[Dmitry Pashkevich]

I am also experiencing this issue on a brand new Lenovo X1 Carbon Gen 10
with a regular HD screen (1920x1200). The workaround of disabling PSR
via altering grub options worked for me:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0"


Should this bug description be generalized?

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

[Daniel van Vugt]

Now tracking in:
https://gitlab.freedesktop.org/drm/amd/-/issues/2282

** Tags removed: fixed-in-linux-6.1 fixed-upstream

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

[Daniel van Vugt]

Nope, not fixed in 5.19.0-32-generic

https://bugs.launchpad.net/ubuntu/+bug/2008540/comments/5

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

** Changed in: linux-hwe-5.19 (Ubuntu)
   Status: Fix Released => Confirmed

** No longer affects: linux

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2282
   https://gitlab.freedesktop.org/drm/amd/-/issues/2282

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/2282
   Importance: Unknown
   Status: Unknown

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2008977] Re: Make Wayland sessions work with fbdev

[Daniel van Vugt]

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

Title:
  Make Wayland sessions work with fbdev

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

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Kernel-packages] [Bug 2008971] Re: Do not sort the task scan result from /proc when synthesizing perf events

[ChengEn, Du]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => ChengEn, Du (chengendu)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => ChengEn, Du (chengendu)

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

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

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

Title:
  Do not sort the task scan result from /proc when synthesizing perf
  events

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

Bug description:
  [Impact]
  The perf tool use scandir() to iterate threads and sort in alphabetical order 
when synthesizing PERF_RECORD_ events.
  If the process ID is  and it has one thread (tid = 1), the thread 
will be processed before the process.
  It results in PERF_RECORD_FORK events that come before PERF_RECORD_MMAP2 
events.
  The callstack will have missing symbols for threads where `PERF_RECORD_FORK` 
events are processed before the `PERF_RECORD_MMAP2` event for the corresponding 
process. 

  [Fix]
  Do not use alphasort when calling scandir()

  363afa3aef24f5e08df6a539f5dc3aae4cddcc1a (perf synthetic-events: Don't
  sort the task scan result from /proc)

  [Test Plan]
  
  function update_last_pid()
local file  = io.open("/proc/sys/kernel/ns_last_pid", "w")
file:write(9997)
  end

  update_last_pid()
  os.execute("~/reproducer")

  
  #include 
  #include 
  #include 

  constexpr int kThreadNum = 10;

  void thread_job() { sleep(30); }

  int main(void) {
std::thread threads[kThreadNum];

std::cout << "Parent process with pid " << getpid() << std::endl;

for (int i = 0; i < kThreadNum; ++i) {
  threads[i] = std::thread(thread_job);
}

for (int i = 0; i < kThreadNum; ++i) {
  threads[i].join();
}

std::cout << "All threads have finished" << std::endl;
return 0;
  }

  The flow is to set /proc/sys/kernel/ns_last_pid first, which represents the 
last pid allocated in the current pid namespace.
  The script (test.lua) sets ns_last_pid to 9997 and executes the reproducer 
(reproducer.cpp).
  After the reproducer creates ten threads, we execute the perf command as 
follows: perf record -F 49 -e cpu-clock -a -g sleep 20.
  Here is the result of command: perf report -f --tasks --mmaps -D | egrep -i 
'perf_record_fork|perf_record_mmap' | grep 

  Before applying the patch, the output of the perf command was as follows:
  0 0 0x34910 [0x40]: PERF_RECORD_FORK(:1):(:)
  0 0 0x34990 [0x40]: PERF_RECORD_FORK(:10001):(:)
  0 0 0x34a10 [0x40]: PERF_RECORD_FORK(:10002):(:)
  0 0 0x34a90 [0x40]: PERF_RECORD_FORK(:10003):(:)
  0 0 0x34b10 [0x40]: PERF_RECORD_FORK(:10004):(:)
  0 0 0x34b90 [0x40]: PERF_RECORD_FORK(:10005):(:)
  0 0 0x34c10 [0x40]: PERF_RECORD_FORK(:10006):(:)
  0 0 0x34c90 [0x40]: PERF_RECORD_FORK(:10007):(:)
  0 0 0x34d10 [0x40]: PERF_RECORD_FORK(:10008):(:)
  0 0 0x34d90 [0x40]: PERF_RECORD_FORK(:10009):(:)
  0 0 0x34e10 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
  0 0 0x34e90 [0x80]: PERF_RECORD_MMAP2 /: [0x555de0159000(0x1000) @ 
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
  0 0 0x34f10 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd17f8000(0x7c000) @ 
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
  0 0 0x34fa0 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd18f9000(0x195000) @ 
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_64-linux-gnu/libc.so.6
  0 0 0x35030 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd1afc000(0x17000) @ 
0x3000 fd:00 1054745 0]: r-xp /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
  0 0 0x350c0 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1bb3000(0x11) @ 
0x9a000 fd:00 1068050 0]: r-xp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
  0 0 0x35158 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1d4e000(0x2a000) @ 
0x2000 fd:00 1054949 0]: r-xp /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  0 0 0x351f0 [0x70]: PERF_RECORD_MMAP2 /: [0x7ffc983bb000(0x2000) @ 0 
00:00 0 0]: r-xp [vdso]
  0 0 0x35260 [0x78]: PERF_RECORD_MMAP2 /: [0xff60(0x1000) 
@ 0 00:00 0 0]: --xp [vsyscall]

  After applying the patch, the output of the perf command is as follows:
  0 0 0x30c28 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
  0 0 0x30ca8 [0x80]: PERF_RECORD_MMAP2 /: [0x5642c7635000(0x1000) @ 
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
  0 0 0x30d28 [0x90]: PERF_RECORD_MMAP2 /: [0x7f8ada03d000(0x7c000) @ 
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
  0 0 0x30db8 [0x90]: PERF_RECORD_MMAP2 /: [0x7f8ada13e000(0x195000) @ 
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_6

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

[Ubuntu Kernel Bot]

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

apport-collect 2008977

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

Title:
  Make Wayland sessions work with fbdev

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

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Kernel-packages] [Bug 2008977] Re: Make Wayland sessions work with fbdev

[Daniel van Vugt]

We will also need to fix bug 1919400 before Xorg is ever retired. But
this is all in the distant future.

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

Title:
  Make Wayland sessions work with fbdev

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

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Kernel-packages] [Bug 2008977] [NEW] Make Wayland sessions work with fbdev

[Daniel van Vugt]

Public bug reported:

Make Wayland sessions work with fbdev. For when KMS/DRM support is
missing in the kernel but the device still has legacy graphics.

Currently Xorg already does this with a custom driver that allows it to
fall back to using fbdev. We could do the same with mutter but it's
unlikely to be accepted by upstream since Fedora opted to solve it by
just enabling SimpleDRM in the kernel:

https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

This started out being a personal goal for me but will also be a
business requirement in future as Ubuntu Core Desktop does not ship Xorg
(but does ship Xwayland). So we need to give mutter some way of using
fbdev graphics.

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

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

** Also 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/2008977

Title:
  Make Wayland sessions work with fbdev

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

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

[Daniel van Vugt]

The fix is in jammy linux-hwe-5.19 and also in kinetic 5.19.0-35.36 ...
but still not in lunar until 6.1 is released.

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

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 
154558
 

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

[Ubuntu Kernel Bot]

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

apport-collect 2008971

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

Title:
  Do not sort the task scan result from /proc when synthesizing perf
  events

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The perf tool use scandir() to iterate threads and sort in alphabetical order 
when synthesizing PERF_RECORD_ events.
  If the process ID is  and it has one thread (tid = 1), the thread 
will be processed before the process.
  It results in PERF_RECORD_FORK events that come before PERF_RECORD_MMAP2 
events.
  The callstack will have missing symbols for threads where `PERF_RECORD_FORK` 
events are processed before the `PERF_RECORD_MMAP2` event for the corresponding 
process. 

  [Fix]
  Do not use alphasort when calling scandir()

  363afa3aef24f5e08df6a539f5dc3aae4cddcc1a (perf synthetic-events: Don't
  sort the task scan result from /proc)

  [Test Plan]
  
  function update_last_pid()
local file  = io.open("/proc/sys/kernel/ns_last_pid", "w")
file:write(9997)
  end

  update_last_pid()
  os.execute("~/reproducer")

  
  #include 
  #include 
  #include 

  constexpr int kThreadNum = 10;

  void thread_job() { sleep(30); }

  int main(void) {
std::thread threads[kThreadNum];

std::cout << "Parent process with pid " << getpid() << std::endl;

for (int i = 0; i < kThreadNum; ++i) {
  threads[i] = std::thread(thread_job);
}

for (int i = 0; i < kThreadNum; ++i) {
  threads[i].join();
}

std::cout << "All threads have finished" << std::endl;
return 0;
  }

  The flow is to set /proc/sys/kernel/ns_last_pid first, which represents the 
last pid allocated in the current pid namespace.
  The script (test.lua) sets ns_last_pid to 9997 and executes the reproducer 
(reproducer.cpp).
  After the reproducer creates ten threads, we execute the perf command as 
follows: perf record -F 49 -e cpu-clock -a -g sleep 20.
  Here is the result of command: perf report -f --tasks --mmaps -D | egrep -i 
'perf_record_fork|perf_record_mmap' | grep 

  Before applying the patch, the output of the perf command was as follows:
  0 0 0x34910 [0x40]: PERF_RECORD_FORK(:1):(:)
  0 0 0x34990 [0x40]: PERF_RECORD_FORK(:10001):(:)
  0 0 0x34a10 [0x40]: PERF_RECORD_FORK(:10002):(:)
  0 0 0x34a90 [0x40]: PERF_RECORD_FORK(:10003):(:)
  0 0 0x34b10 [0x40]: PERF_RECORD_FORK(:10004):(:)
  0 0 0x34b90 [0x40]: PERF_RECORD_FORK(:10005):(:)
  0 0 0x34c10 [0x40]: PERF_RECORD_FORK(:10006):(:)
  0 0 0x34c90 [0x40]: PERF_RECORD_FORK(:10007):(:)
  0 0 0x34d10 [0x40]: PERF_RECORD_FORK(:10008):(:)
  0 0 0x34d90 [0x40]: PERF_RECORD_FORK(:10009):(:)
  0 0 0x34e10 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
  0 0 0x34e90 [0x80]: PERF_RECORD_MMAP2 /: [0x555de0159000(0x1000) @ 
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
  0 0 0x34f10 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd17f8000(0x7c000) @ 
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
  0 0 0x34fa0 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd18f9000(0x195000) @ 
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_64-linux-gnu/libc.so.6
  0 0 0x35030 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd1afc000(0x17000) @ 
0x3000 fd:00 1054745 0]: r-xp /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
  0 0 0x350c0 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1bb3000(0x11) @ 
0x9a000 fd:00 1068050 0]: r-xp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
  0 0 0x35158 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1d4e000(0x2a000) @ 
0x2000 fd:00 1054949 0]: r-xp /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  0 0 0x351f0 [0x70]: PERF_RECORD_MMAP2 /: [0x7ffc983bb000(0x2000) @ 0 
00:00 0 0]: r-xp [vdso]
  0 0 0x35260 [0x78]: PERF_RECORD_MMAP2 /: [0xff60(0x1000) 
@ 0 00:00 0 0]: --xp [vsyscall]

  After applying the patch, the output of the perf command is as follows:
  0 0 0x30c28 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
  0 0 0x30ca8 [0x80]: PERF_RECORD_MMAP2 /: [0x5642c7635000(0x1000) @ 
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
  0 0 0x30d28 [0x90]: PERF_RECORD_MMAP2 /: [0x7f8ada03d000(0x7c000) @ 
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64

[Kernel-packages] [Bug 2008971] [NEW] Do not sort the task scan result from /proc when synthesizing perf events

[ChengEn, Du]

Public bug reported:

[Impact]
The perf tool use scandir() to iterate threads and sort in alphabetical order 
when synthesizing PERF_RECORD_ events.
If the process ID is  and it has one thread (tid = 1), the thread will 
be processed before the process.
It results in PERF_RECORD_FORK events that come before PERF_RECORD_MMAP2 events.
The callstack will have missing symbols for threads where `PERF_RECORD_FORK` 
events are processed before the `PERF_RECORD_MMAP2` event for the corresponding 
process. 

[Fix]
Do not use alphasort when calling scandir()

363afa3aef24f5e08df6a539f5dc3aae4cddcc1a (perf synthetic-events: Don't
sort the task scan result from /proc)

[Test Plan]

function update_last_pid()
  local file  = io.open("/proc/sys/kernel/ns_last_pid", "w")
  file:write(9997)
end

update_last_pid()
os.execute("~/reproducer")


#include 
#include 
#include 

constexpr int kThreadNum = 10;

void thread_job() { sleep(30); }

int main(void) {
  std::thread threads[kThreadNum];

  std::cout << "Parent process with pid " << getpid() << std::endl;

  for (int i = 0; i < kThreadNum; ++i) {
threads[i] = std::thread(thread_job);
  }

  for (int i = 0; i < kThreadNum; ++i) {
threads[i].join();
  }

  std::cout << "All threads have finished" << std::endl;
  return 0;
}

The flow is to set /proc/sys/kernel/ns_last_pid first, which represents the 
last pid allocated in the current pid namespace.
The script (test.lua) sets ns_last_pid to 9997 and executes the reproducer 
(reproducer.cpp).
After the reproducer creates ten threads, we execute the perf command as 
follows: perf record -F 49 -e cpu-clock -a -g sleep 20.
Here is the result of command: perf report -f --tasks --mmaps -D | egrep -i 
'perf_record_fork|perf_record_mmap' | grep 

Before applying the patch, the output of the perf command was as follows:
0 0 0x34910 [0x40]: PERF_RECORD_FORK(:1):(:)
0 0 0x34990 [0x40]: PERF_RECORD_FORK(:10001):(:)
0 0 0x34a10 [0x40]: PERF_RECORD_FORK(:10002):(:)
0 0 0x34a90 [0x40]: PERF_RECORD_FORK(:10003):(:)
0 0 0x34b10 [0x40]: PERF_RECORD_FORK(:10004):(:)
0 0 0x34b90 [0x40]: PERF_RECORD_FORK(:10005):(:)
0 0 0x34c10 [0x40]: PERF_RECORD_FORK(:10006):(:)
0 0 0x34c90 [0x40]: PERF_RECORD_FORK(:10007):(:)
0 0 0x34d10 [0x40]: PERF_RECORD_FORK(:10008):(:)
0 0 0x34d90 [0x40]: PERF_RECORD_FORK(:10009):(:)
0 0 0x34e10 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
0 0 0x34e90 [0x80]: PERF_RECORD_MMAP2 /: [0x555de0159000(0x1000) @ 
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
0 0 0x34f10 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd17f8000(0x7c000) @ 
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
0 0 0x34fa0 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd18f9000(0x195000) @ 
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_64-linux-gnu/libc.so.6
0 0 0x35030 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd1afc000(0x17000) @ 
0x3000 fd:00 1054745 0]: r-xp /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
0 0 0x350c0 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1bb3000(0x11) @ 
0x9a000 fd:00 1068050 0]: r-xp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
0 0 0x35158 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1d4e000(0x2a000) @ 
0x2000 fd:00 1054949 0]: r-xp /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
0 0 0x351f0 [0x70]: PERF_RECORD_MMAP2 /: [0x7ffc983bb000(0x2000) @ 0 
00:00 0 0]: r-xp [vdso]
0 0 0x35260 [0x78]: PERF_RECORD_MMAP2 /: [0xff60(0x1000) @ 
0 00:00 0 0]: --xp [vsyscall]

After applying the patch, the output of the perf command is as follows:
0 0 0x30c28 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
0 0 0x30ca8 [0x80]: PERF_RECORD_MMAP2 /: [0x5642c7635000(0x1000) @ 
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
0 0 0x30d28 [0x90]: PERF_RECORD_MMAP2 /: [0x7f8ada03d000(0x7c000) @ 
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
0 0 0x30db8 [0x90]: PERF_RECORD_MMAP2 /: [0x7f8ada13e000(0x195000) @ 
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_64-linux-gnu/libc.so.6
0 0 0x30e48 [0x90]: PERF_RECORD_MMAP2 /: [0x7f8ada341000(0x17000) @ 
0x3000 fd:00 1054745 0]: r-xp /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
0 0 0x30ed8 [0x98]: PERF_RECORD_MMAP2 /: [0x7f8ada3f8000(0x11) @ 
0x9a000 fd:00 1068050 0]: r-xp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
0 0 0x30f70 [0x98]: PERF_RECORD_MMAP2 /: [0x7f8ada593000(0x2a000) @ 
0x2000 fd:00 1054949 0]: r-xp /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
0 0 0x31008 [0x70]: PERF_RECORD_MMAP2 /: [0x7ffcb2116000(0x2000) @ 0 
00:00 0 0]: r-xp [vdso]
0 0 0x31078 [0x78]: PERF_RECORD_MMAP2 /: [0xff60(0x1000) @ 
0 00:00 0 0]: --xp [vsyscall]
0 0 0x310f0 [0x40]: PERF_RECORD_FORK(:1):(:)
0 0 0x31170 [0x40]: PERF_RECORD_FORK(:10001):(:)
0 0 0x311f0 [0x40]: PERF_RECORD_FORK(:10002):(:)
0 0 0x31270

[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

[Daniel van Vugt]

Confirmed the fix is in linux-hwe-5.19 ... it looks like this:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77c092e054262b594614bad5e5f47e57c5d29639

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

** Changed in: linux-hwe-5.19 (Ubuntu)
   Status: New => Fix Released

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

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

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

** Tags added: fixed-in-linux-6.1 fixed-upstream

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

[Daniel van Vugt]

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

** Changed in: linux-hwe-5.19 (Ubuntu)
   Status: New => Fix Released

** No longer affects: linux-hwe-5.19 (Ubuntu Kinetic)

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp/5.15.0-1031.38)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-gcp 
(5.15.0-1031.38) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-gcp

[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 packaging 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 2006453] Re: Fix selftests/ftracetests/Meta-selftests

[Po-Hsu Lin]

This is now affecting Bionic

With upstream commit a1d6cd88c "selftests/ftrace: event_triggers: wait
longer for test_event_enable" applied via stable update, ftrace in
Bionic proposed (4.15.0-207.218) is now failing with:

$ sudo ./ftracetest ./test.d/ftrace/func_event_triggers.tc 
[1] ftrace - test for function event triggers   [FAIL]
[2] (instance)  ftrace - test for function event triggers   [FAIL]

With -v added to the command you will see it failing with:
./ftracetest: 52: [: 0: unexpected operator

The "==" operator fix can solve this problem.

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

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

Title:
  Fix selftests/ftracetests/Meta-selftests

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  == Impact ==
  This subtest checks for bashisms in the test scripts of ftracetests. A recent 
stable change added such a case. This is harmless but causes the Meta-selftests 
to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer 
for test_event_enable" which adds:
  +   if [ "$e" == $val ]; then

  == Fix ==
  Replace the test with
  +   if [ "$e" = $val ]; then

  == Testcase ==
  Running the kernel selftests/ftracetest (done in ADT and RT) should no longer 
show "Meta-selftests" as FAILed.

  == Regression Potential ==
  This affects only the selftest suite and only ftrace subtests. Any change 
would only be observable there.

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


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

[Kernel-packages] [Bug 2008118] Re: Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

I just found many similar reports.

1. https://github.com/QubesOS/qubes-issues/issues/6923
2. https://gitlab.freedesktop.org/drm/amd/-/issues/2266
3. https://gitlab.freedesktop.org/drm/amd/-/issues/822

They all have the same amdgpu errors:

```
mar 01 23:01:25 workstation1 kernel: [drm:psp_load_non_psp_fw [amdgpu]] *ERROR* 
Failed to start rlc autoload
mar 01 23:01:25 workstation1 kernel: [drm:psp_resume [amdgpu]] *ERROR* PSP 
resume failed
mar 01 23:01:25 workstation1 kernel: [drm:amdgpu_device_fw_loading [amdgpu]] 
*ERROR* resume of IP block >
mar 01 23:01:25 workstation1 kernel: [drm] Skip scheduling IBs!
mar 01 23:01:25 workstation1 kernel: [drm] Skip scheduling IBs!
mar 01 23:01:25 workstation1 kernel: amdgpu :03:00.0: amdgpu: GPU reset(1) 
failed
mar 01 23:01:25 workstation1 kernel: amdgpu :03:00.0: amdgpu: GPU reset end 
with ret = -22
```

** Bug watch added: github.com/QubesOS/qubes-issues/issues #6923
   https://github.com/QubesOS/qubes-issues/issues/6923

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2266
   https://gitlab.freedesktop.org/drm/amd/-/issues/2266

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #822
   https://gitlab.freedesktop.org/drm/amd/-/issues/822

** Description changed:

  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen; in
  both cases it's completely unresponsive.
  
  The only way out is to force a reboot with the SYSRQ "REISUB" key combo.
  I tried switching VT with Ctrl+Alt+F{1-7}, but it does not respond.
  
  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.
- 
- I didn't have this problem with other flavors (used Xubuntu and Ubuntu,
- 22.04 and 22.10), so I guess it's a Kubuntu bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1217 F pulseaudio
   /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  Freeze on resume from suspend (amdgpu errors)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen;
  in both cases it's completely unresponsive.

  The only way out is to force a reboot with the SYSRQ "REISUB" key
  combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
  respond.

  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Un

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1035.42)

[Ubuntu SRU Bot]

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

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging 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 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)

[Ubuntu SRU Bot]

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

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging 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 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1035.42)

[Ubuntu SRU Bot]

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

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

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

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

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)

[Ubuntu SRU Bot]

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

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

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

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed

[Po-Hsu Lin]

I can see this fcnal-test.sh test failing with 5.15.0-68.75
Thanks

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

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

Title:
  net:fcnal-test.sh didn't return a non-zero value even with some sub-
  tests failed

Status in ubuntu-kernel-tests:
  In Progress
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
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  The net/fcnal-test.sh on F/J won't return a non-zero value even with
  some sub test cases failed, here is an example on Jammy:

   # Tests passed: 857
   # Tests failed: 5
   ok 1 selftests: net: fcnal-test.sh

  Therefore it's marked as PASSED on our report and making it difficult
  to spot these failures:
  # With VRF
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping local, VRF bind - VRF IP [FAIL]
  # TEST: ping local, device bind - ns-A IP [FAIL]
  # SYSCTL: net.ipv4.ping_group_range=0 2147483647
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping local, VRF bind - VRF IP [FAIL]
  # TEST: ping local, device bind - ns-A IP [FAIL]
  # With VRF
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # SYSCTL: net.ipv4.ping_group_range=0 2147483647
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL]

  [Fix]
  * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code

  This patch can be cherry-picked into Focal and Jammy kernel.
  We don't have this test in Bionic, and this patch has already landed
  on Kinetic and OEM-5.17

  [Test]
  Run the patched test, the return value will be 1 whenever the number
  of failed test cases is not 0.

  [Where problems could occur]
  Change limited to testing tools, but we're expected to see new failures
  in Jammy. With bug 2006391 fixed later on, we will see failures
  reported in F/K as well.

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


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

[Kernel-packages] [Bug 2008118] Re: Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

It happened again. Notice the same amdgpu errors near the end.

** Attachment added: "second_freeze.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+attachment/5650838/+files/second_freeze.log

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

Title:
  Freeze on resume from suspend (amdgpu errors)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen;
  in both cases it's completely unresponsive.

  The only way out is to force a reboot with the SYSRQ "REISUB" key
  combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
  respond.

  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.

  I didn't have this problem with other flavors (used Xubuntu and
  Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1217 F pulseaudio
   /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Rear Audio port sometimes has no audio output after reboot(Cirrus
  Logic)

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

Bug description:
  [Impact]
  On the development, we found sometimes there is no audio output device when 
headphone is connected to the rear audio jack.

  [Fix]
  Cirrus Logic provides a patch to fix this
  
https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/

  The patch is included in v6.2-rc1
  9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and 
lock.

  
  [Test]
  Verified by our QA and ODM.

  [Where problems could occur]
  It extends the delay time, should be no harm for existing platforms.

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


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

[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix W6400 hang after resume of S3 stress

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  amdgpu hang when stress S3 on AMD W6400 GPU.

  [Fix]
  Add a WA to manually adjust strobe calculation using FCLK restrict.

  [Test]
  Suspend AMD W6400 for 40 times, it works fine.

  [Where problems could occur]
  Low risk, upstream fix.
  It may cause AMD GPU hang.

  The patch is in 5.16, only Jammy kernel needs it.

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


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

[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  5.15.0-58.64 breaks xen bridge networking (pvh domU)

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

Bug description:
  [Impact]  

   
  Xen guests will not have network access. This fixes a regression due to the 
fix 
 
  for CVE-2022-3643.

   


   
  [Testing] 

   
  This has only been build-tested.  

   


   
  [Potential regression]

   
  Xen guests might not have network access.
  --


  With 5.15.0-58.64-generic, bridge networking on xen is broken :

   no packet (check with tcpdump)  flowing between dom0 and any domUs 
  attached to a network bridge.
   downgrading to  5.15.0-57-generic fix the issue. Thus the patch to the 
netback driver seems the cause.

  relevant network config :

  brtctl show :
  br0   8000.XXXno  eno1
     vif1.0

  relevant domU config :

  kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin'
  type = 'pvh'

  vif = [ 'ip=192.168.10.10 ,bridge=br0' ]

  No message in dmesg, journal, xen logs..

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


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

[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  NFS: client permission error after adding user to permissible group

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

Bug description:
  [Impact]
  The NFS client's access cache becomes stale due to the user's group 
membership changing on the server after the user has already logged in on the 
client.
  The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or 
timeout (without delegation).
  Adding a user to a group in the NFS server will not cause any file attributes 
to change.
  The client will encounter permission errors until other file attributes are 
changed or the memory cache is dropped.

  [Fix]

  The access cache shall be cleared once the user logs out and logs back
  in again.

  0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache 
upon login
  029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's 
timestamp in rcu path
  5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning

  [Test Plan]
  1.[client side] testuser is not part of testgroup
testuser@kinetic:~$ ls -ld /mnt/private/
drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied
  2.[server side] add testuser into testgroup, which has access to folder
root@kinetic:~$ usermod -aG testgroup testuser &&
echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush
  3.[client side] create a file again but still fail
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied

  [Where problems could occur]
  The fix will apply upstream commits, so the regression can be considered as 
low.

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


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

[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a
  while

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

Bug description:
  == SRU Justification ==
  [Impact]
  Audio playback becomes silent on some Intel SoF systems.

  [Fix]
  Revert offending commit.

  [Test]
  The speaker can always play sound after the commit gets reverted.

  [Where problems could occur]
  Audio on linux 5.15 has been working fine without the patch for a long
  time, so this only restore it to where it was.

  == Original Bug Report ==
  [Summary]
  During the kernel SRU testing on focal-hwe, I found the audio output of some 
machines are broken.
  I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and 
haven't seen this happened.

  The volume bars in settings react to what sound is played correctly
  and device is detected as well.

  [Reproduce steps]
  1. install focal
  2. enable -proposed
  3. run apt dist-upgrade.
  4. reboot.
  5. press fn keys to volume up then volume down or play a short youtube video.
  6. after a while can't hear any sound from the speaker.

  [Failure rate]
  10/10

  [Additional info]
  If I run "sudo alsa force-reload" can make audio work again, but after a 
while it breaks again.
  These are machines that impacted by this bug:
  https://certification.canonical.com/hardware/202007-28045/
  https://certification.canonical.com/hardware/201906-27109/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/202007-28047/
  https://certification.canonical.com/hardware/202007-28055/
  https://certification.canonical.com/hardware/202005-27899/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85
  Uname: Linux 5.15.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1303 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Feb 19 21:24:59 2023
  InstallationDate: Installed on 2020-08-03 (930 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: Feb 19 20:53:23 
dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7590
  dmi.product.sku: 0922
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a
  while

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

Bug description:
  == SRU Justification ==
  [Impact]
  Audio playback becomes silent on some Intel SoF systems.

  [Fix]
  Revert offending commit.

  [Test]
  The speaker can always play sound after the commit gets reverted.

  [Where problems could occur]
  Audio on linux 5.15 has been working fine without the patch for a long
  time, so this only restore it to where it was.

  == Original Bug Report ==
  [Summary]
  During the kernel SRU testing on focal-hwe, I found the audio output of some 
machines are broken.
  I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and 
haven't seen this happened.

  The volume bars in settings react to what sound is played correctly
  and device is detected as well.

  [Reproduce steps]
  1. install focal
  2. enable -proposed
  3. run apt dist-upgrade.
  4. reboot.
  5. press fn keys to volume up then volume down or play a short youtube video.
  6. after a while can't hear any sound from the speaker.

  [Failure rate]
  10/10

  [Additional info]
  If I run "sudo alsa force-reload" can make audio work again, but after a 
while it breaks again.
  These are machines that impacted by this bug:
  https://certification.canonical.com/hardware/202007-28045/
  https://certification.canonical.com/hardware/201906-27109/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/202007-28047/
  https://certification.canonical.com/hardware/202007-28055/
  https://certification.canonical.com/hardware/202005-27899/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85
  Uname: Linux 5.15.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1303 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Feb 19 21:24:59 2023
  InstallationDate: Installed on 2020-08-03 (930 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: Feb 19 20:53:23 
dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7590
  dmi.product.sku: 0922
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  rtcpie in timers from ubuntu_kernel_selftests randomly failing

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  Node: Standard_D11_v2
  Kernel: 4.18.0-1008.8~18.04.1

   selftests: timers: rtcpie
   
   Periodic IRQ rate is 1024Hz.
   Counting 20 interrupts at:
   2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   32Hz:1 2 3 4 5 6 7
   PIE delta error: 0.034667 should be close to 0.031250
  181.  01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: 
timers: rtcpie [FAIL]

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


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

[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  ubuntu_kernel_selftests: net:udpgso_bench.sh failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh
  04:41:59 DEBUG| [stdout] # ipv4
  04:41:59 DEBUG| [stdout] # tcp
  04:42:00 DEBUG| [stdout] # tcp tx:   2736 MB/s46415 calls/s  46415 msg/s
  04:42:00 DEBUG| [stdout] # tcp rx:   2737 MB/s46161 calls/s
  04:42:01 DEBUG| [stdout] # tcp tx:   2735 MB/s46392 calls/s  46392 msg/s
  04:42:01 DEBUG| [stdout] # tcp rx:   2739 MB/s46226 calls/s
  04:42:02 DEBUG| [stdout] # tcp tx:   2717 MB/s46092 calls/s  46092 msg/s
  04:42:02 DEBUG| [stdout] # tcp zerocopy
  04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused

  04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1
  04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m
  04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1
  04:42:54 DEBUG| [stdout] make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  04:42:54 ERROR| Exception escaping from test:
  Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
 line 252, in run_once
  raise error.TestError(test_name + ' failed.')
  TestError: net:udpgso_bench.sh failed.

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


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

[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in
  kmalloc-2k slabs

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

Bug description:
  Since updating to kernel 5.15.0-46-generic (package version
  5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel
  memory; our first server with 8 GB of RAM just fatally OOMed, causing
  us to detect this. Inspection of OOM reports, /proc/meminfo, and
  /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k
  slabs:

  Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab 
info:
  Aug 23 12:51:11 cluster kernel: [361299.864757] Name  
Used  Total
  [...]
  Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k   
6676584KB6676596KB

  Most of our machines appear to be leaking slab memory at a rate of
  around 20 to 40 Mbytes/hour, with some machines leaking much faster;
  the champions are leaking kernel memory at 145 Mbytes/hour and 237
  Mbytes/hour.

  We aren't running any proprietary kernel modules and our only unusual
  kernel configuration is that we've disabled AppArmor with 'apparmor=0'
  on the kernel command line.

  /proc/version_signature:
  Ubuntu 5.15.0-46.49-generic 5.15.39

  Full kernel command line from the Dell R240 system that fatally OOMd:
  BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 
console=tty0 apparmor=0

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


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

[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54

Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Released
Status in zfs-linux source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  Fix Committed
Status in zfs-linux source package in Lunar:
  Confirmed

Bug description:
  Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS
  are broken.

  Reproducer steps:

  ```
  sudo snap install lxd
  sudo snap set lxd shiftfs.enable=true
  sudo lxd init --auto
  lxc storage create zfs zfs
  lxc launch images:ubuntu/jammy c1 -s zfs
  lxc exec c1 -- touch /root/foo
  touch: cannot touch '/root/foo': Value too large for defined data type
  ```

  Expected result can be achieved by disabling shiftfs:

  ```
  sudo snap set lxd shiftfs.enable=false
  sudo systemctl reload snap.lxd.daemon
  lxc launch images:ubuntu/jammy c2 -s zfs
  lxc exec c2 -- touch /root/foo
  lxc exec c2 -- ls -la /root/foo
  -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo
  ```

  Kernel 5.15.0-47-generic does not exhibit this issue.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2240 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 14:55:52 2022
  InstallationDate: Installed on 2022-03-04 (205 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  MachineType: LENOVO 20R1000RUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  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
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET40W(1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20R1000RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20R1000RUS
  dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux

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

Title:
  RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror
  mode

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-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The Screen is shaking connected monitor to Onboard HDMI port.

  [Fix]
  The interlaced mode is not supported for Intel Gen 12 onwards.
  Disable interlaced mode for DP&HDMI on Display >= 12.

  Due to schedule, SRU for OEM kernels first.
  After these patches are merged to mainline/drmtip kernel, will SRU for 
generic kernels.

  [Test Case]
  1.Connected two external Monitor to the onboard HDMI/DP port .
  2.Boot OS.
  2.set mirror mode. (onboard HDMI / onboard DP)
  3.check if screen shakes.

  [Where problems could occur]
  Low, Remove interlace support for Display >= 12 so it wouldn't cause a 
regression.

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


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

[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

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

Bug description:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  Included in v6.2-rc1
  d899aa668498 PCI: vmd: Disable MSI remapping after suspend

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

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


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

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

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux

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

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

Status in HWE Next:
  New
Status in HWE Next lunar series:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  New
Status in linux-oem-6.1 source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

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

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

  Add a new keymap for KEY_MUTE.

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

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

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

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


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

[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04
  release

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == SRU Justification ==
  Intel has requested the following patches which enable enable Intel_idle for 
eagle stream.

  Intel has customers that would like to use the intel_idle driver on latest 
SPR (Sapphire Rapids).
  These patches have all landed upstream, but are not in Jammy.

  These patches will enable customers to use Ubuntu 22.04 on new hardware
  from Intel.

  
  == Fixes ==
  9edf3c0ffef0 ("intel_idle: add SPR support")
  da0e58c038e6 ("intel_idle: add 'preferred_cstates' module argument")
  3a9cf77b60dc ("intel_idle: add core C6 optimization for SPR")
  03eb65224e57 ("cpuidle: intel_idle: Drop redundant backslash at line end")
  39c184a6a9a7 ("intel_idle: Fix the 'preferred_cstates' module parameter")
  7eac3bd38d18 ("intel_idle: Fix SPR C6 optimization")
  1548fac47a11 ("intel_idle: make SPR C1 and C1E be independent")

  
  == Regression Potential ==
  Medium. These patches are specific to enable intel_idle support for Sapphire 
Rapids.  Changes
  are specific to Intel and tested by Intel.

  
  == Test Case ==
  A test kernel was built with these patches and tested by Intel.
  Intel tested on SPR-SP machine and see the correct 190us and 600us residency 
for the C6 state.

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


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

[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Regression in ext4 during online resize

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

Bug description:
  Issue

  resize2fs utility is used to resize the filesystem and is idempotent
  in nature. But in the 5.15 kernel, successive execution of resize2fs
  is returning error.

  Reproduction step (on AWS):

  Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 
5.15.0-1022-aws) in us-west-2 region and attach an EBS volume.
  Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p 
/mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0
  Increase the size of EBS volume.
  Run sudo resize2fs /dev/xvdb multiple times.

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  The filesystem is already 5242880 (4k) blocks long.  Nothing to do!

  When you run the same step on the latest image ami-0a1d6d351894df6cc
  (Linux 5.15.0-1026-aws).

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/xvdb
  Couldn't find valid filesystem superblock.


  FIX:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b

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


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

[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix the ACPI _CPC not found error from kernel dmesg on some dynamic
  SSDT table loaded firmwares

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

Bug description:
  [Impact]
  Some machines which have dynamically loaded SSDT tables, will not be loaded 
and get the CPPC not worked.

  [Fix]
  Fix the regression by some load supports for CPPC from an SSDT dynamically 
when _OSC reports CPPC v2. And make the "[\_SB.PR00._CPC], AE_NOT_FOUND" gone.

  [Test]
  Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], 
AE_NOT_FOUND" error exist or not on demesg .

  [Where problems could occur]
  Low risk, It only helps to CPPC support loaded.

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


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

[Kernel-packages] [Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  net:fcnal-test.sh didn't return a non-zero value even with some sub-
  tests failed

Status in ubuntu-kernel-tests:
  In Progress
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
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  The net/fcnal-test.sh on F/J won't return a non-zero value even with
  some sub test cases failed, here is an example on Jammy:

   # Tests passed: 857
   # Tests failed: 5
   ok 1 selftests: net: fcnal-test.sh

  Therefore it's marked as PASSED on our report and making it difficult
  to spot these failures:
  # With VRF
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping local, VRF bind - VRF IP [FAIL]
  # TEST: ping local, device bind - ns-A IP [FAIL]
  # SYSCTL: net.ipv4.ping_group_range=0 2147483647
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping local, VRF bind - VRF IP [FAIL]
  # TEST: ping local, device bind - ns-A IP [FAIL]
  # With VRF
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # SYSCTL: net.ipv4.ping_group_range=0 2147483647
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL]

  [Fix]
  * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code

  This patch can be cherry-picked into Focal and Jammy kernel.
  We don't have this test in Bionic, and this patch has already landed
  on Kinetic and OEM-5.17

  [Test]
  Run the patched test, the return value will be 1 whenever the number
  of failed test cases is not 0.

  [Where problems could occur]
  Change limited to testing tools, but we're expected to see new failures
  in Jammy. With bug 2006391 fixed later on, we will see failures
  reported in F/K as well.

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


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

[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-aws

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

Title:
  Rear Audio port sometimes has no audio output after reboot(Cirrus
  Logic)

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

Bug description:
  [Impact]
  On the development, we found sometimes there is no audio output device when 
headphone is connected to the rear audio jack.

  [Fix]
  Cirrus Logic provides a patch to fix this
  
https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/

  The patch is included in v6.2-rc1
  9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and 
lock.

  
  [Test]
  Verified by our QA and ODM.

  [Where problems could occur]
  It extends the delay time, should be no harm for existing platforms.

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


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

[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress

[Ubuntu Kernel Bot]

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

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

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


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy

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

Title:
  Fix W6400 hang after resume of S3 stress

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  amdgpu hang when stress S3 on AMD W6400 GPU.

  [Fix]
  Add a WA to manually adjust strobe calculation using FCLK restrict.

  [Test]
  Suspend AMD W6400 for 40 times, it works fine.

  [Where problems could occur]
  Low risk, upstream fix.
  It may cause AMD GPU hang.

  The patch is in 5.16, only Jammy kernel needs it.

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


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

[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)

[Ubuntu Kernel Bot]

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

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

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


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy

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

Title:
  5.15.0-58.64 breaks xen bridge networking (pvh domU)

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

Bug description:
  [Impact]  

   
  Xen guests will not have network access. This fixes a regression due to the 
fix 
 
  for CVE-2022-3643.

   


   
  [Testing] 

   
  This has only been build-tested.  

   


   
  [Potential regression]

   
  Xen guests might not have network access.
  --


  With 5.15.0-58.64-generic, bridge networking on xen is broken :

   no packet (check with tcpdump)  flowing between dom0 and any domUs 
  attached to a network bridge.
   downgrading to  5.15.0-57-generic fix the issue. Thus the patch to the 
netback driver seems the cause.

  relevant network config :

  brtctl show :
  br0   8000.XXXno  eno1
     vif1.0

  relevant domU config :

  kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin'
  type = 'pvh'

  vif = [ 'ip=192.168.10.10 ,bridge=br0' ]

  No message in dmesg, journal, xen logs..

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


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

[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group

[Ubuntu Kernel Bot]

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

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

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


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy

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

Title:
  NFS: client permission error after adding user to permissible group

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

Bug description:
  [Impact]
  The NFS client's access cache becomes stale due to the user's group 
membership changing on the server after the user has already logged in on the 
client.
  The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or 
timeout (without delegation).
  Adding a user to a group in the NFS server will not cause any file attributes 
to change.
  The client will encounter permission errors until other file attributes are 
changed or the memory cache is dropped.

  [Fix]

  The access cache shall be cleared once the user logs out and logs back
  in again.

  0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache 
upon login
  029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's 
timestamp in rcu path
  5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning

  [Test Plan]
  1.[client side] testuser is not part of testgroup
testuser@kinetic:~$ ls -ld /mnt/private/
drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied
  2.[server side] add testuser into testgroup, which has access to folder
root@kinetic:~$ usermod -aG testgroup testuser &&
echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush
  3.[client side] create a file again but still fail
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied

  [Where problems could occur]
  The fix will apply upstream commits, so the regression can be considered as 
low.

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


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

[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a
  while

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

Bug description:
  == SRU Justification ==
  [Impact]
  Audio playback becomes silent on some Intel SoF systems.

  [Fix]
  Revert offending commit.

  [Test]
  The speaker can always play sound after the commit gets reverted.

  [Where problems could occur]
  Audio on linux 5.15 has been working fine without the patch for a long
  time, so this only restore it to where it was.

  == Original Bug Report ==
  [Summary]
  During the kernel SRU testing on focal-hwe, I found the audio output of some 
machines are broken.
  I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and 
haven't seen this happened.

  The volume bars in settings react to what sound is played correctly
  and device is detected as well.

  [Reproduce steps]
  1. install focal
  2. enable -proposed
  3. run apt dist-upgrade.
  4. reboot.
  5. press fn keys to volume up then volume down or play a short youtube video.
  6. after a while can't hear any sound from the speaker.

  [Failure rate]
  10/10

  [Additional info]
  If I run "sudo alsa force-reload" can make audio work again, but after a 
while it breaks again.
  These are machines that impacted by this bug:
  https://certification.canonical.com/hardware/202007-28045/
  https://certification.canonical.com/hardware/201906-27109/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/202007-28047/
  https://certification.canonical.com/hardware/202007-28055/
  https://certification.canonical.com/hardware/202005-27899/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85
  Uname: Linux 5.15.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1303 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Feb 19 21:24:59 2023
  InstallationDate: Installed on 2020-08-03 (930 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: Feb 19 20:53:23 
dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7590
  dmi.product.sku: 0922
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep

[Dyson Lu]

Experiencing this as well.

22.04 LTS
Lenovo Lenovo YOGA 720-15IKB
Intel® HD Graphics 630 
External Dell monitor native resolution 2560x1440, connected through USB-C

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

Title:
  [amdgpu] Wrong external screen resolution after wake up from sleep

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
  running KDE) I started experiencing a problem with external screen
  resolution after the wake up from sleep. The monitor resolution is
  small (1280x768) and doesn't respect the setting prior the sleep
  (1920x1200).

  After the wake up from sleep:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  There is an error when trying to change the setting to the highest
  resolution supported by the monitor (which is not included in the
  above list).

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  xrandr: cannot find mode 1920x1200
  ```

  After the turn off and turn on of the external monitor, the resolution
  is somehow added to the xrandr list:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95 +
 # a list of resolutions
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  Now it is possible to change the resolution:

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  # no output, the resolution was successfully changed
  ```   

  After the change, the resolution is successfully changed and xrandr
  gives proper output:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95*+
 # a list of lower resolutions
  ```

  The problem is not present on fresh start. However, it is consistently
  present after the wake up from sleep.

  What can cause the problem and how may I fix it?

  Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
  external monitor is connected via USB-C. There are no problems with
  laptop screen resolution, only external monitor is affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Jun 16 18:12:05 2022
  DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2019-08-21 (1030 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20NE000BMC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
  dmi.bios.date: 01/26/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET44W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NE000BMC
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NE000BMC
  dmi.product.sku: LENOVO_MT_20NE_BU_Th

[Kernel-packages] [Bug 1998938] Re: Add support for CT accounting stats

[Bodong Wang]

Feature is not available yet. Need to verify after
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136

** Tags removed: verification-needed-focal

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

Title:
  Add support for CT accounting stats

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

Bug description:
  * Explain the bug(s)
   
  Add CT accounting stats per flow for TC CT rules. This is only available when 
nf_conn_acct
  is enabled so it won’t affect performance when not enabled.
   
  * Brief explanation of fixes
   
  Cherry-pick. No adaptation. First commit for SW, second commit of HW 
offloaded rules.
   
  * How to test
   
  Enable nf_conn_acct and check ct stats.
   
  * What it could break.
   
  Nothing.

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


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

[Kernel-packages] [Bug 2002361] Re: allow per-net notifier to follow netdev into namespace

[Meriton Tuli]

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

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

Title:
  allow per-net notifier to follow netdev into namespace

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

Bug description:
  
  * Explain the bug(s)
  There is possible deadlock during reload mlxsw into initial netns made 
possible by commit:
  328fbe747ad4 ("net: Close race between {un, }register_netdevice_notifier() 
and setup_net()/cleanup_net()").

  * Brief explanation of fixes
  Introduce dev_net variant that is basically per-net notifier with an
  extension that re-registers the per-net notifier upon netdev namespace
  change. Basically the per-net notifier follows the netdev into
  namespace.

  
  * How to test 
  # chroot /host nsenter -t 1 -n devlink dev reload ${port} netns ${NS}
   
  * What it could break
  none

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


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

[Kernel-packages] [Bug 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu

[Jarkko Korpi]

I got a kernel upgrade from Linux mint 5.15.0-67
I see no change in dmesg.

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

Title:
  5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  from dmesg

   1.313665] UBSAN: shift-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
  [1.313668] shift exponent 64 is too large for 64-bit type 'long long 
unsigned int'

  there is also a crash but i don't know if it's related.

  1.313671] Call Trace:
  [1.313672]  
  [1.313673]  show_stack+0x52/0x5c
  [1.313676]  dump_stack_lvl+0x4a/0x63
  [1.313678]  dump_stack+0x10/0x16
  [1.313679]  ubsan_epilogue+0x9/0x49
  [1.313680]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [1.313682]  initialize_nocpsch.cold+0x15/0x59 [amdgpu]
  [1.313841]  device_queue_manager_init+0x208/0x3b0 [amdgpu]
  [1.313946]  kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
  [1.314079]  amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
  [1.314178]  amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
  [1.314323]  amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
  [1.314463]  ? do_pci_enable_device+0xdb/0x110
  [1.314466]  amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
  [1.314556]  amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
  [1.314642]  local_pci_probe+0x48/0x90
  [1.314644]  pci_device_probe+0x119/0x1f0
  [1.314645]  really_probe+0x21f/0x420
  [1.314647]  __driver_probe_device+0x119/0x190
  [1.314648]  driver_probe_device+0x23/0xc0
  [1.314650]  __driver_attach+0xbd/0x1f0
  [1.314651]  ? __device_attach_driver+0x120/0x120
  [1.314652]  bus_for_each_dev+0x7c/0xd0
  [1.314654]  driver_attach+0x1e/0x30
  [1.314655]  bus_add_driver+0x148/0x220
  [1.314656]  driver_register+0x95/0x100
  [1.314657]  __pci_register_driver+0x68/0x70
  [1.314659]  amdgpu_init+0x7c/0x1000 [amdgpu]
  [1.314747]  ? 0xc0fc
  [1.314748]  do_one_initcall+0x46/0x1e0
  [1.314750]  ? kmem_cache_alloc_trace+0x19e/0x2e0
  [1.314752]  do_init_module+0x52/0x260
  [1.314753]  load_module+0xb2b/0xbc0
  [1.314754]  __do_sys_finit_module+0xbf/0x120
  [1.314756]  __x64_sys_finit_module+0x18/0x20
  [1.314757]  do_syscall_64+0x59/0xc0
  [1.314758]  ? ksys_lseek+0x85/0xc0
  [1.314759]  ? exit_to_user_mode_prepare+0x37/0xb0
  [1.314761]  ? syscall_exit_to_user_mode+0x27/0x50
  [1.314762]  ? __x64_sys_lseek+0x18/0x20
  [1.314763]  ? do_syscall_64+0x69/0xc0
  [1.314764]  entry_SYSCALL_64_after_hwframe+0x61/0xcb
  [1.314766] RIP: 0033:0x7fef87ab8a3d
  [1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
  [1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX: 
0139
  [1.314770] RAX: ffda RBX: 55d1d00078a0 RCX: 
7fef87ab8a3d
  [1.314771] RDX:  RSI: 7fef87c4f441 RDI: 
0018
  [1.314772] RBP: 0002 R08:  R09: 
0002
  [1.314772] R10: 0018 R11: 0246 R12: 
7fef87c4f441
  [1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15: 
55d1d002eb10
  [1.314774]  
  [1.314778] 


  
  gpu is Amd r 380 tonga 4Gb.
  I was adviced to try 6.0 series of kernel and I dont see the ubsan error 
there but I would like to get the fixes backported 5.15 series.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarkko 1322 F pulseaudio
   /dev/snd/controlC1:  jarkko 1322 F pulseaudio
  CasperMD5json: {
  CurrentDesktop: MATE
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2022-09-19 (71 days ago)
  InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem 
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
  ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
  RelatedPackageVersions:
   linux-restricted-modules-6.0.0-1007-oem N/A
   linux-backports-modules-6.0.0-1007-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.7
  Tags:  vanessa
  Uname: Linux 6.0.0-1007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambas

[Kernel-packages] [Bug 1958032] Re: [igb - Intel NIC] Adapter reset due to TX unit hangs

[cardonator]

I am getting this same bug on a 6.0.0 kernel with the igb driver. This
is on a Dell XPS15 2022 on Kubuntu 22.04. If it matters, I have disabled
the MAC address passthrough.

lspci:

:00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH CNVi 
WiFi [8086:51f0] (rev 01)
:05:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network 
Connection [8086:1533] (rev 03)

ethtool -i:

driver: igb
version: 6.0.0-1007-oem
firmware-version: 3.20, 0x85bb
expansion-rom-version: 
bus-info: :05:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

uname -a
Linux xps15 6.0.0-1007-oem #7-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 25 18:05:20 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux


dmesg output
[  995.667074] igb :05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX/TX
[  999.942717] igb :05:00.0: Detected Tx Unit Hang
 Tx Queue <2>
 TDH  <0>
 TDT  <1>
 next_to_use  <1>
 next_to_clean<0>
   buffer_info[next_to_clean]
 time_stamp   <10002a93c>
 next_to_watch<185f352a>
 jiffies  <10002ab60>
 desc.status  <48000>
[ 1001.926595] igb :05:00.0: Detected Tx Unit Hang
 Tx Queue <2>
 TDH  <0>
 TDT  <1>
 next_to_use  <1>
 next_to_clean<0>
   buffer_info[next_to_clean]
 time_stamp   <10002a93c>
 next_to_watch<185f352a>
 jiffies  <10002ad50>
 desc.status  <48000>
[ 1003.942630] igb :05:00.0: Detected Tx Unit Hang
 Tx Queue <2>
 TDH  <0>
 TDT  <1>
 next_to_use  <1>
 next_to_clean<0>
   buffer_info[next_to_clean]
 time_stamp   <10002a93c>
 next_to_watch<185f352a>
 jiffies  <10002af48>
 desc.status  <48000>
[ 1005.926775] igb :05:00.0: Detected Tx Unit Hang
 Tx Queue <2>
 TDH  <0>
 TDT  <1>
 next_to_use  <1>
 next_to_clean<0>
   buffer_info[next_to_clean]
 time_stamp   <10002a93c>
 next_to_watch<185f352a>
 jiffies  <10002b138>
 desc.status  <48000>
[ 1005.958454] igb :05:00.0 enp5s0: Reset adapter

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>

[Kernel-packages] [Bug 2008823] Re: /sys/kernel/boot_params/data leaks random data

[Seth Arnold]

Aha, cool, thanks Mike; I started with xxd myself, and got stuff that
looked enough like ELF objects that I was prepared to trust file's
assessment of them as ELF objects.

My machine with non-zero content at the end:
Linux hunt 4.15.0-201-generic #212-Ubuntu SMP Mon Nov 28 11:29:59 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

My machines with zeros at the end:
Linux millbarge 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
Linux wopr 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux
Linux minis 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 
17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux


** Information type changed from Private Security to Public Security

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

Title:
  /sys/kernel/boot_params/data leaks random data

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

Bug description:
  Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte 
buffer is old kernel data. 
  It really stood out as I saw parts of email contents in there.
  It seems be random RAM contents from what was present before rebooting.   
   
  This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic.
   After rebooting again I 
saw a fragment of yet another email in there.
  A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as 
recognizable.   

  
  Nothing after the entries at the front of e820_table was zeroed out as it 
should be.
  This could leak a substantial amount of data such as encryption keys. 
  

  
  /sys/kernel/boot_params/data is readable by all users.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Feb 28 13:24:06 2023
  InstallationDate: Installed on 2019-10-17 (1229 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago)

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


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

[Kernel-packages] [Bug 2008946] [NEW] Focal update: v5.4.230 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

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

pNFS/filelayout: Fix coalescing test for single DS
net/ethtool/ioctl: return -EOPNOTSUPP if we have no phy stats
RDMA/srp: Move large values to a new enum for gcc13
f2fs: let's avoid panic if extent_tree is not created
wifi: brcmfmac: fix regression for Broadcom PCIe wifi devices
Add exception protection processing for vd in axi_chan_handle_err function
nilfs2: fix general protection fault in nilfs_btree_insert()
efi: fix userspace infinite retry read efivars after EFI runtime services page 
fault
drm/i915/gt: Reset twice
ALSA: hda/realtek - Turn on power early
xhci-pci: set the dma max_seg_size
usb: xhci: Check endpoint is valid before dereferencing it
xhci: Fix null pointer dereference when host dies
xhci: Add update_hub_device override for PCI xHCI hosts
xhci: Add a flag to disable USB3 lpm on a xhci root port level.
usb: acpi: add helper to check port lpm capability using acpi _DSM
xhci: Detect lpm incapable xHC USB3 roothub ports from ACPI tables
prlimit: do_prlimit needs to have a speculation check
USB: serial: option: add Quectel EM05-G (GR) modem
USB: serial: option: add Quectel EM05-G (CS) modem
USB: serial: option: add Quectel EM05-G (RS) modem
USB: serial: option: add Quectel EC200U modem
USB: serial: option: add Quectel EM05CN (SG) modem
USB: serial: option: add Quectel EM05CN modem
USB: misc: iowarrior: fix up header size for USB_DEVICE_ID_CODEMERCS_IOW100
misc: fastrpc: Don't remove map on creater_process and device_release
misc: fastrpc: Fix use-after-free race condition for maps
usb: core: hub: disable autosuspend for TI TUSB8041
comedi: adv_pci1760: Fix PWM instruction handling
mmc: sunxi-mmc: Fix clock refcount imbalance during unbind
btrfs: fix race between quota rescan and disable leading to NULL pointer deref
cifs: do not include page data when checking signature
USB: serial: cp210x: add SCALANCE LPE-9000 device id
usb: host: ehci-fsl: Fix module alias
usb: typec: altmodes/displayport: Add pin assignment helper
usb: typec: altmodes/displayport: Fix pin assignment calculation
usb: gadget: g_webcam: Send color matching descriptor per frame
usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate()
usb-storage: apply IGNORE_UAS only for HIKSEMI MD202 on RTL9210
dt-bindings: phy: g12a-usb3-pcie-phy: fix compatible string documentation
serial: pch_uart: Pass correct sg to dma_unmap_sg()
dmaengine: tegra210-adma: fix global intr clear
serial: atmel: fix incorrect baudrate setup
gsmi: fix null-deref in gsmi_get_variable
drm/i915: re-disable RC6p on Sandy Bridge
drm/amd/display: Fix set scaling doesn's work
drm/amd/display: Fix COLOR_SPACE_YCBCR2020_TYPE matrix
x86/fpu: Use _Alignof to avoid undefined behavior in TYPE_ALIGN
mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma
Linux 5.4.230
UBUNTU: Upstream stable to v5.4.230

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

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

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

** Description changed:

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

[Kernel-packages] [Bug 1914774] Re: Some derivative kernel tools packages don't depend on linux-tools-common

[Launchpad Bug Tracker]

This bug was fixed in the package linux-ibm - 5.19.0-1018.20

---
linux-ibm (5.19.0-1018.20) kinetic; urgency=medium

  * kinetic/linux-ibm: 5.19.0-1018.20 -proposed tracker (LP: #2004288)

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- [Config] Update configs after rebase

  * Some derivative kernel tools packages don't depend on linux-tools-common
(LP: #1914774)
- [Packaging] ibm: linux-tools-common and linux-cloud-tools-common are one 
per
  series

  [ Ubuntu: 5.19.0-35.36 ]

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)
  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

  [ Ubuntu: 5.19.0-34.35 ]

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)
  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container
  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling 

[Kernel-packages] [Bug 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.17 - 5.17.0-1028.29

---
linux-oem-5.17 (5.17.0-1028.29) jammy; urgency=medium

  * jammy/linux-oem-5.17: 5.17.0-1028.29 -proposed tracker (LP:
#2004346)

  * CVE-2023-0045
- x86/bugs: Flush IBP in ib_prctl_set()

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
(LP: #2000110)
- drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
- drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
- drm/amdgpu: make sure to init common IP before gmc
- drm/amdgpu: fix sdma doorbell init ordering on APUs

  * CVE-2022-47520
- wifi: wilc1000: validate pairwise and authentication suite offsets

  * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546)
- selftests: net: return non-zero for failures reported in
  arp_ndisc_evict_nocarrier

  * CVE-2022-43750
- usb: mon: make mmapped memory read only

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2022-3565
- mISDN: fix use-after-free bugs in l1oip timer handlers

  * CVE-2022-36879
- xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in
  xfrm_bundle_lookup()

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on
J-oem-5.17 / K (LP: #1968310)
- selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier

  * CVE-2022-20566
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put

  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates

 -- Timo Aaltonen   Fri, 10 Feb 2023
12:15:41 +0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-20369

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-20566

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3565

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36879

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-43750

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-47520

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0045

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0461

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

Title:
  arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests
  failed on J-oem-5.17 / K

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  In selftests: net: arp_ndisc_evict_nocarrier.sh, even all of the
  sub-tests from this script have passed, the overall test result
  is still a fail.

# selftests: net: arp_ndisc_evict_nocarrier.sh
# run arp_evict_nocarrier=1 test
# ok
# run arp_evict_nocarrier=0 test
# ok
# run all.arp_evict_nocarrier=0 test
# ok
# run ndisc_evict_nocarrier=1 test
# ok
# run ndisc_evict_nocarrier=0 test
# ok
# run all.ndisc_evict_nocarrier=0 test
# ok
not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255

  This is caused by the cleanup() in the script, as it's trying to
  access a non-existing file.

  [Fix]
  * 9c4d7f45d6 selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier

  This patch can be cherry-picked into all affected kernels.

  [Test]
  Run the patched test and the test will pass.

  [Where problems could occur]
  Change limited to testing tools, no impact to real kernel function
  or test performances.

  [Original Bug Report]
  Issue found on Jammy OEM 5.17.0-1003.3

  It looks like all the sub-tests has passed, but the final return value
  is not 0.

   Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/c

[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1012.12

---
linux-oem-6.0 (6.0.0-1012.12) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1012.12 -proposed tracker (LP: #2004348)

  * CVE-2023-0469
- io_uring/filetable: fix file reference underflow

  * LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot (LP: #1987998)
- SAUCE: LSM: Change Landlock from LSMBLOB_NEEDED to LSMBLOB_NOT_NEEDED

  * CVE-2023-0045
- x86/bugs: Flush IBP in ib_prctl_set()

  * CVE-2022-47520
- wifi: wilc1000: validate pairwise and authentication suite offsets

  * CVE-2022-3567
- ipv6: Fix data races around sk->sk_prot.

  * CVE-2022-45934
- Bluetooth: L2CAP: Fix u8 overflow

  * CVE-2022-42896
- Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm

  * CVE-2022-43945
- NFSD: Remove "inline" directives on op_rsize_bop helpers
- NFSD: Cap rsize_bop result based on send buffer size

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates

 -- Timo Aaltonen   Fri, 10 Feb 2023
12:37:27 +0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-20369

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3567

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-42896

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-43945

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-45934

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-47520

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0045

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0461

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0469

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

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

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

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

  [Impact]

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

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

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

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

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

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

  struct lsmblob {
     u32 secid[LSMBLOB_ENTRIES];
  };

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

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

  GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"

  You will receive the following panic:

  LSM: Security Framework initializing
  landlock: Up and running.
  LSM support for eBPF active
  Kernel panic - not syncing: security_add_hooks Too many LSMs registered.
  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
  Call Trace:
   
   show_stack+0x52/0x5c
   dump_stack_lvl+0x

[Kernel-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules

[Launchpad Bug Tracker]

This bug was fixed in the package linux-restricted-modules -
5.19.0-35.36

---
linux-restricted-modules (5.19.0-35.36) kinetic; urgency=medium

  * Master version: 5.19.0-35.36

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to v7.2 autogen form

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

linux-restricted-modules (5.19.0-34.35+3) kinetic; urgency=medium

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (adhoc/2023.01.30)
- update spin to 2023.01.30-2

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to direct ancillaries
- [Packaging] convert to v7.1 autogen form

linux-restricted-modules (5.19.0-34.35) kinetic; urgency=medium

  * Master version: 5.19.0-34.35

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

 -- Luke Nowakowski-Krijger   Fri,
03 Feb 2023 10:19:12 -0800

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules

[Launchpad Bug Tracker]

This bug was fixed in the package linux-restricted-modules -
5.15.0-67.74

---
linux-restricted-modules (5.15.0-67.74) jammy; urgency=medium

  * Master version: 5.15.0-67.74

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

linux-restricted-modules (5.15.0-66.73) jammy; urgency=medium

  * Master version: 5.15.0-66.73

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to v7.2 autogen form

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

linux-restricted-modules (5.15.0-65.72+3) jammy; urgency=medium

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (adhoc/2023.01.30)
- update spin to 2023.01.30-2

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to direct ancillaries
- [Packaging] convert to v7.1 autogen form

linux-restricted-modules (5.15.0-65.72) jammy; urgency=medium

  * Master version: 5.15.0-65.72

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

 -- Stefan Bader   Wed, 22 Feb 2023 15:03:25
+0100

** Changed in: linux-restricted-modules (Ubuntu Jammy)
   Status: In Progress => Fix Released

** Changed in: linux-restricted-modules (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 1999556] Re: commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in kinetic master to remove "hio" reference from Makefile

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.17 - 5.17.0-1028.29

---
linux-oem-5.17 (5.17.0-1028.29) jammy; urgency=medium

  * jammy/linux-oem-5.17: 5.17.0-1028.29 -proposed tracker (LP:
#2004346)

  * CVE-2023-0045
- x86/bugs: Flush IBP in ib_prctl_set()

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
(LP: #2000110)
- drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
- drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
- drm/amdgpu: make sure to init common IP before gmc
- drm/amdgpu: fix sdma doorbell init ordering on APUs

  * CVE-2022-47520
- wifi: wilc1000: validate pairwise and authentication suite offsets

  * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546)
- selftests: net: return non-zero for failures reported in
  arp_ndisc_evict_nocarrier

  * CVE-2022-43750
- usb: mon: make mmapped memory read only

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2022-3565
- mISDN: fix use-after-free bugs in l1oip timer handlers

  * CVE-2022-36879
- xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in
  xfrm_bundle_lookup()

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on
J-oem-5.17 / K (LP: #1968310)
- selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier

  * CVE-2022-20566
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put

  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates

 -- Timo Aaltonen   Fri, 10 Feb 2023
12:15:41 +0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-20369

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-20566

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3565

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36879

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-43750

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-47520

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0045

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0461

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

Title:
  Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards

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-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting 
while entering graphics mode.

  [Fix]
  These 3 commits fix the issue
  a8671493d207 drm/amdgpu: make sure to init common IP before gmc
  e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for 
vega
  dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega

  cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move 
nbio sdma_doorbell_range() into sdma code for vega")
  50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs

  ==
  V1.
  AMD provides a list of commits to fix this issue
  1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
  
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
  2. drm/amdgpu: Don't enable LTR if not supported
  
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6
  3. Patch series: fix PCI AER issues
  drm/amdgpu: make sure to init common IP before gmc
  
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6
  drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
  
https://git.kernel.org/pub/scm/linux/kernel/git/next

[Kernel-packages] [Bug 1999750] Re: Set explicit CC in the headers package

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 2001570] Re: Jammy update: v5.15.79 upstream stable release

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev 

[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

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

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

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

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

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

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

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

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

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

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-67.74 -proposed tracker (LP: #2008074)

  * [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
(LP: #2007798)
- Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"

linux (5.15.0-66.73) jammy; urgency=medium

  * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.15.0-65.72) jammy; urgency=medium

  * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * NFS: client permission error after adding user to permissible group
(LP: #2003053)
- NFS: Clear the file access cache upon login
- NFS: Judge the file access cache's timestamp in rcu path
- NFS: Fix up a sparse warning

  * Fix W6400 hang after resume of S3 stress (LP: #2000299)
- drm/amd/display: Manually adjust strobe for DCN303

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

  * CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()

  * CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP

  * CVE-2023-0179
- netfilter: nft_payload: incorrect arithmetics when fetching VLAN header 
bits

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

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

  * Jammy update: v5.15.83 upstream stable release (LP: #2003134)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- s

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-515-server -
515.86.01-0ubuntu0.22.04.2

---
nvidia-graphics-drivers-515-server (515.86.01-0ubuntu0.22.04.2) jammy; 
urgency=medium

  * debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1 (LP: #2003995).

 -- Alberto Milone   Wed, 01 Feb 2023
10:39:24 +

** Changed in: libnvidia-nscq-525 (Ubuntu Jammy)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-515 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI systems
when using certain dis

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525 -
525.85.05-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-525 (525.85.05-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2003995):
- Improved the reliability of suspend and resume on UEFI systems
  when using certain display panels.
- Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using
  VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT to
  allocate memory.
- Disabled Fixed Rate Link (FRL) when using passive DisplayPort
  to HDMI dongles, which are incompatible  with FRL.
  * debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1.

 -- Alberto Milone   Wed, 01 Feb 2023
11:50:21 +

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Jammy)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-515 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.85.12-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-525-server (525.85.12-0ubuntu0.22.04.1) jammy; 
urgency=medium

  * New upstream release (LP: #2003995).
  * debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1.

 -- Alberto Milone   Wed, 01 Feb 2023
11:05:39 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-515 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI sys

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-515 -
515.86.01-0ubuntu0.22.10.2

---
fabric-manager-515 (515.86.01-0ubuntu0.22.10.2) kinetic; urgency=medium

  * debian/nvidia-fabricmanager{-dev}-510.*:
- Remove leftover files from the 510 series (LP: #2003995).

 -- Alberto Milone   Wed, 01 Feb 2023
15:48:56 +

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-515 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI systems
when using certain display panels.
   

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-525 -
525.85.12-0ubuntu0.22.10.1

---
fabric-manager-525 (525.85.12-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream release (LP: #2003995).

 -- Alberto Milone   Wed, 01 Feb 2023
15:04:50 +

** Changed in: fabric-manager-515 (Ubuntu Kinetic)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-515 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI systems
when using certain display panels.
  - Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using
VK_MEMOR

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-515 -
515.86.01-0ubuntu0.22.10.2

---
libnvidia-nscq-515 (515.86.01-0ubuntu0.22.10.2) kinetic; urgency=medium

  * debian/libnvidia-nscq-510.install:
- Remove leftover install file (LP: #2003995).

 -- Alberto Milone   Wed, 01 Feb 2023
15:22:25 +

** Changed in: fabric-manager-525 (Ubuntu Kinetic)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-515 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI systems
when using certain display panels.
  - Fixed a bug that could cause

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-525 -
525.85.12-0ubuntu0.22.10.1

---
libnvidia-nscq-525 (525.85.12-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream release (LP: #2003995).

 -- Alberto Milone   Wed, 01 Feb 2023
14:48:01 +

** Changed in: libnvidia-nscq-515 (Ubuntu Kinetic)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-515 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI systems
when using certain display panels.
  - Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using
VK_MEMOR

[Kernel-packages] [Bug 2004051] Re: Kinetic update: upstream stable patchset 2023-01-27

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.19.0-35.36

---
linux (5.19.0-35.36) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)

  * CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461

linux (5.19.0-34.35) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-34.35 -proposed tracker (LP: #2004299)

  * LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(LP: #1990849)
- [SAUCE] shiftfs: fix -EOVERFLOW inside the container

  * Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- ASoC: fsl_sai: use local device pointer
- serial: Add rs485_supported to uart_port
- serial: fsl_lpuart: Fill in rs485_supported
- x86/sgx: Create utility to validate user provided offset and length
- x86/sgx: Add overflow check in sgx_validate_offset_length()
- binder: validate alloc->mm in ->mmap() handler
- ceph: Use kcalloc for allocating multiple elements
- ceph: fix NULL pointer dereference for req->r_session
- wifi: mac80211: fix memory free error when registering wiphy fail
- wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
- riscv: dts: sifive unleashed: Add PWM controlled LEDs
- audit: fix undefined behavior in bit shift for AUDIT_BIT
- wifi: airo: do not assign -1 to unsigned char
- wifi: mac80211: Fix ack frame idr leak when mesh has no route
- wifi: ath11k: Fix QCN9074 firmware boot on x86
- spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run
- selftests/bpf: Add verifier test for release_reference()
- Revert "net: macsec: report real_dev features when HW offloading is 
enabled"
- platform/x86: ideapad-laptop: Disable touchpad_switch
- platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1
- platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
- scsi: ibmvfc: Avoid path failures during live migration
- scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
- block, bfq: fix null pointer dereference in bfq_bio_bfqg()
- arm64/syscall: Include asm/ptrace.h in syscall_wrapper header.
- nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
- Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
  properly""
- ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
- RISC-V: vdso: Do not add missing symbols to version section in linker 
script
- MIPS: pic32: treat port as signed integer
- xfrm: fix "disable_policy" on ipv4 early demux
- xfrm: replay: Fix ESN wrap around for GSO
- af_key: Fix send_acquire race with pfkey_register
- ARM: dts: am335x-pcm-953: Define fixed regulators in root node
- ASoC: hdac_hda: fix hda pcm buffer overflow issue
- ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
- ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
- x86/hyperv: Restore VP assist page after cpu offlining/onlining
- scsi: storvsc: Fix handling of srb_status and capacity change events
- ASoC: max98373: Add checks for devm_kcalloc
- regulator: core: fix kobject release warning and memory leak in
  regulator_register()
- spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld()
- regulator: core: fix UAF in destroy_regulator()
- bus: sunxi-rsb: Remove the shutdown callback
- bus: sunxi-rsb: Support atomic transfers
- tee: optee: fix possible memory leak in optee_register_device()
- ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl
- selftests: mptcp: fix mibit vs mbit mix up
- net: liquidio: simplify if expression
- rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-
  CAN-15975]
- net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus
- nfc/nci: fix race with opening and closing
- net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
- 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
- netfilter: conntrack: Fix data-races around ct mark
- netfilter: nf_tables: do not set up extensions for end interval
- iavf: Fix a crash during reset task
- iavf: Do not restart Tx queues after reset task failure
- iavf: Fix race condition between iavf_shutdown and iavf_remove
- ARM: mxs: fix memory leak in mxs_machine_init()
- ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties
- net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
- net/mlx4: Check retval of mlx4_bitmap_init
- net: mvpp2: fix possible invalid pointer dereference
- net/qla3xxx: fix potential memleak in ql3xxx_send()
- octeontx2-af: debugsfs: fix pci device refcount leak
- net: pch_gbe: fix pci device refcount leak while module exiting
- nfp: fill splittable of devlink_port_attrs correctly
- nfp: add port from netdev