date:20231019

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

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

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

Title:
  USB-C 3.x port running at 2.0 speeds

Status in linux-signed-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  I noticed that every device I plugged in to the USB-C port on my
  computer (which is USB 3.1 or, should I say, 3.2 Gen. 2 - WTF those
  names), it only runs at 2.0 speeds (480Mbps). After doing some
  troubleshooting, here's what I discovered:

  If I shut down my machine, plug my USB 3 device in to the USB-C port,
  power it on and let the OS boots... it works at 3.x speeds just fine
  until I unplug it; The moment I plug it back in, the exact same USB 3
  device at the exact same USB-C port at the exact same orientation, it
  starts to run at 2.0 speeds.

  
  Logs:

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ apt-cache policy linux-image-5.15.0-48-lowlatency
  linux-image-5.15.0-48-lowlatency:
Installed: 5.15.0-48.54
Candidate: 5.15.0-48.54
Version table:
   *** 5.15.0-48.54 500
  500 https://ubuntu.itsbrasil.net/ubuntu jammy-updates/main amd64 
Packages
  500 https://ubuntu.itsbrasil.net/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  $ lsmod | grep xhci
  xhci_pci   24576  0
  xhci_pci_renesas   20480  1 xhci_pci

  $ lsusb -tvv (Device Plugged at Boot)
  /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M
  ID 1d6b:0003 Linux Foundation 3.0 root hub
  /sys/bus/usb/devices/usb4  /dev/bus/usb/004/001
  |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
  ID 0bc2:ab24 Seagate RSS LLC Backup Plus Portable Drive
  /sys/bus/usb/devices/4-2  /dev/bus/usb/004/002
  /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
  ID 1d6b:0002 Linux Foundation 2.0 root hub
  /sys/bus/usb/devices/usb3  /dev/bus/usb/003/001
  |__ Port 4: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 12M
  ID 0d8c:0267 C-Media Electronics, Inc. 
  /sys/bus/usb/devices/3-4  /dev/bus/usb/003/002
  |__ Port 4: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 12M
  ID 0d8c:0267 C-Media Electronics, Inc. 
  /sys/bus/usb/devices/3-4  /dev/bus/usb/003/002
  |__ Port 4: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 12M
  ID 0d8c:0267 C-Media Electronics, Inc. 
  /sys/bus/usb/devices/3-4  /dev/bus/usb/003/002
  |__ Port 4: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 12M
  ID 0d8c:0267 C-Media Electronics, Inc. 
  /sys/bus/usb/devices/3-4  /dev/bus/usb/003/002
  |__ Port 7: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
  ID 04f2:b729 Chicony Electronics Co., Ltd 
  /sys/bus/usb/devices/3-7  /dev/bus/usb/003/003
  |__ Port 7: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
  ID 04f2:b729 Chicony Electronics Co., Ltd 
  /sys/bus/usb/devices/3-7  /dev/bus/usb/003/003
  |__ Port 7: Dev 3, If 2, Class=Application Specific Interface, Driver=, 
480M
  ID 04f2:b729 Chicony Electronics Co., Ltd 
  /sys/bus/usb/devices/3-7  /dev/bus/usb/003/003
  |__ Port 10: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
  ID 8087:0029 Intel Corp. AX200 Bluetooth
  /sys/bus/usb/devices/3-10  /dev/bus/usb/003/004
  |__ Port 10: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
  ID 8087:0029 Intel Corp. AX200 Bluetooth
  /sys/bus/usb/devices/3-10  /dev/bus/usb/003/004
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M
  ID 1d6b:0003 Linux Foundation 3.0 root hub
  /sys/bus/usb/devices/usb2  /dev/bus/usb/002/001
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
  ID 1d6b:0002 Linux Foundation 2.0 root hub
  /sys/bus/usb/devices/usb1  /dev/bus/usb/001/001

  $ lsusb -tvv (Device Plugged After)
  /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M
  ID 1d6b:0003 Linux Foundation 3.0 root hub
  /sys/bus/usb/devices/usb4  /dev/bus/usb/004/001
  /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
  ID 1d6b:0002 Linux Foundation 2.0 root hub
  /sys/bus/usb/devices/usb3  /dev/bus/usb/003/001
  |__ Port 2: Dev 5, If 0, Class=Mass Storage, Driver=uas, 480M
  ID 0bc2:ab24 Seagate RSS LLC Backup Plus Portable Drive
  /sys/bus/usb/devices/3-2  /dev/bus/usb/003/005
  |__ Port 4: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 12M
  ID 0d8c:0267 C-Media Electronics, Inc. 
  /sys/bus/usb/devices/3-4  /dev/bus/usb/003/002
  |__ Port 4: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 12M
  ID

[Kernel-packages] [Bug 2039894] [NEW] USB-C 3.2 port registering as USB 2.0

2023-10-19 Thread Michael Black

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

Public bug reported:

When I plug in USB 3.0/3.1/3.2 devices into system, it is always
registering at USB 2.0 speeds.

mblack@pro:~$ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 7: Dev 4, If 0, Class=Mass Storage, Driver=uas, 480M
|__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

Port 7: Dev 4 is a SanDisk Extreme Pro Portable SSD which is a USB 3.2
2x2 drive.  This is connected via USB-C port.   When same drive is
connected via USB-A cable, device connect at 1M speed. This is
consistent with all USB 3.x devices.

mblack@pro:~$ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
|__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=uas, 1M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M


mblack@pro:~$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-35-generic 6.2.0-35.35~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:17:22 2023
InstallationDate: Installed on 2023-08-13 (67 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** This bug has been marked a duplicate of bug 1991028
   USB-C 3.x port running at 2.0 speeds

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

Title:
  USB-C 3.2 port registering as USB 2.0

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

Bug description:
  When I plug in USB 3.0/3.1/3.2 devices into system, it is always
  registering at USB 2.0 speeds.

  mblack@pro:~$ lsusb -t
  /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
  /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 7: Dev 4, If 0, Class=Mass Storage, Driver=uas, 480M
  |__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  |__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

  Port 7: Dev 4 is a SanDisk Extreme Pro Portable SSD which is a USB 3.2
  2x2 drive.  This is connected via USB-C port.   When same drive is
  connected via USB-A cable, device connect at 1M speed. This is
  consistent with all USB 3.x devices.

  mblack@pro:~$ lsusb -t
  /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
  /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
  |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=uas, 1M
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  |__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

  
  mblack@pro:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-35-generic 6.2.0-35.35~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:17:22 2023
  InstallationDate: Installed on 2023-08-13 (67 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2

[Kernel-packages] [Bug 2039601] Re: [ kernel 6.5 regression ] nvme not working on some laptops

2023-10-19 Thread Luis Alberto Pabón

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

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

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

Title:
  [ kernel 6.5 regression ] nvme not working on some laptops

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

Bug description:
  With the update to Ubuntu 23.10 my nvme drive ceased to function.
  Booting the old 6.2 kernel from 23.04 works, but not the newer
  6.5.0-9.

  This is a kernel bug that's been fixed in 6.5.6, any chance it could
  possibly be backported?

  More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luis   3036 F wireplumber
   /dev/snd/controlC1:  luis   3036 F wireplumber
   /dev/snd/seq:luis   3029 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:05:29 2023
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-19 Thread Devis

Same problem with Lenovo IdeaPad Slim 3 15AMN8 with Ryzen 5 7520U

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in linux-signed package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2039877] Re: System crash dialogue when opening flatpak

2023-10-19 Thread Erich Eickmeyer

This bug report was filed against the Linux kernel but seems to have
been intended for the flatpak package touchegg. Please contact the
developer of touchegg for support. Contact information for the developer
seems to be at https://github.com/JoseExposito/touchegg.

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

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

Title:
  System crash dialogue when opening flatpak

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Occurred when trying to open flatpak from
  https://flathub.org/apps/com.github.joseexposito.touche in-between
  opening .flatpakref with Discover  store and the Discover store fully
  loading.

  Have encountered previously with other flatpaks - usually but doesn't
  always crash and have installed other flatpaks from flathub after
  trying a few times.

  Everything up to date in apt.

  Hope this report helps in some small way!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-35-generic 6.2.0-35.35
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rich   3967 F wireplumber
   /dev/snd/seq:rich   3960 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 19 19:16:57 2023
  InstallationDate: Installed on 2023-07-20 (91 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: Apple Inc. MacBookPro14,3
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet 
splash vt.handoff=7 initrd=\initrd.img-6.2.0-35-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2023
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 515.0.0.0.0
  dmi.board.name: Mac-551B86E5744E2388
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,3
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-551B86E5744E2388
  dmi.modalias: 
dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 2039884] [NEW] Lunar update: upstream stable patchset 2023-10-19

2023-10-19 Thread 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:

   upstream stable patchset 2023-10-19

Ported from the following upstream stable releases:
v6.1.51, v6.4.14
v6.1.52, v6.4.15

   from git://git.kernel.org/

ACPI: thermal: Drop nocrt parameter
module: Expose module_init_layout_section()
arm64: module-plts: inline linux/moduleloader.h
arm64: module: Use module_init_layout_section() to spot init sections
ARM: module: Use module_init_layout_section() to spot init sections
lockdep: fix static memory detection even more
parisc: Cleanup mmap implementation regarding color alignment
parisc: sys_parisc: parisc_personality() is called from asm code
io_uring/parisc: Adjust pgoff in io_uring mmap() for parisc
kallsyms: Fix kallsyms_selftest failure
module/decompress: use vmalloc() for zstd decompression workspace
UBUNTU: Upstream stable to v6.1.51, v6.4.14
erofs: ensure that the post-EOF tails are all zeroed
ksmbd: fix wrong DataOffset validation of create context
ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob()
ksmbd: replace one-element array with flex-array member in struct smb2_ea_info
ksmbd: reduce descriptor size if remaining bytes is less than request size
ARM: pxa: remove use of symbol_get()
mmc: au1xmmc: force non-modular build and remove symbol_get usage
net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
USB: serial: option: add Quectel EM05G variant (0x030e)
USB: serial: option: add FOXCONN T99W368/T99W373 product
ALSA: usb-audio: Fix init call orders for UAC1
usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
HID: wacom: remove the battery when the EKR is off
staging: rtl8712: fix race condition
Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race condition
wifi: mt76: mt7921: do not support one stream on secondary antenna only
wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU
serial: qcom-geni: fix opp vote on shutdown
serial: sc16is7xx: fix broken port 0 uart init
serial: sc16is7xx: fix bug when first setting GPIO direction
firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
fsi: master-ast-cf: Add MODULE_FIRMWARE macro
tcpm: Avoid soft reset when partner does not support get_status
dt-bindings: sc16is7xx: Add property to change GPIO function
nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
usb: typec: tcpci: clear the fault status bit
pinctrl: amd: Don't show `Invalid config param` errors
wifi: rtw88: usb: kill and free rx urbs on probe failure
UBUNTU: Upstream stable to v6.1.52, v6.4.15

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

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

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

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

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

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

** Description changed:

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

[Kernel-packages] [Bug 2036450] Re: Azure: Update CIFS to v6.5

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


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-v2 
verification-needed-jammy-linux-azure

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

Title:
  Azure: Update CIFS to v6.5

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

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested this patch set to update CIFS and smbfs to the
  Linux kernel version 6.5.

  [Test Plan]

  Microsoft has tested with positive results.

  [Regression Potential]

  This is a huge patch set. The potential exists for corruption,
  connection instabilities, or other cifs related maladies.

  [Other Info]

  SF: #00365185

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


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

[Kernel-packages] [Bug 2039882] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2039882/+attachment/5711423/+files/ProcEnviron.txt

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

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

Title:
  Kernels 6.x have a regression for Audio via HDMI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Dell Inspiron 16 7610]

  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19

  before and including kernel 5.15 there was a bug that after locking
  the screen and logging back audio via HDMI was disappearing. Later the
  bug was fixed and definitely not present in 5.19

  However, this bug is present in 6.x kernels included in Lunar and
  Mantic as well as in 6.5.7-060507.202310102154

  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.

  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```

  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```

  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP

  ```
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2022-06-19 (487 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags: mantic
  Uname: Linux 5.19.17-051917-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to mantic on 2023-10-19 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 2039882] Re: Kernels 6.x have a regression for Audio via HDMI

apport information

** Tags added: apport-collected mantic

** Description changed:

  [Dell Inspiron 16 7610]
  
  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19
  
  before and including kernel 5.15 there was a bug that after locking the
  screen and logging back audio via HDMI was disappearing. Later the bug
  was fixed and definitely not present in 5.19
  
  However, this bug is present in 6.x kernels included in Lunar and Mantic
  as well as in 6.5.7-060507.202310102154
  
  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.
  
  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```
  
  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```
  
  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP
  
  ```
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2022-06-19 (487 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ Tags: mantic
+ Uname: Linux 5.19.17-051917-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to mantic on 2023-10-19 (0 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd microk8s plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2039882/+attachment/5711422/+files/ProcCpuinfoMinimal.txt

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

Title:
  Kernels 6.x have a regression for Audio via HDMI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Dell Inspiron 16 7610]

  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19

  before and including kernel 5.15 there was a bug that after locking
  the screen and logging back audio via HDMI was disappearing. Later the
  bug was fixed and definitely not present in 5.19

  However, this bug is present in 6.x kernels included in Lunar and
  Mantic as well as in 6.5.7-060507.202310102154

  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.

  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```

  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```

  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP

  ```
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2022-06-19 (487 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags: mantic
  Uname: Linux 5.19.17-051917-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to mantic on 2023-10-19 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:

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

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

apport-collect 2039882

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

Title:
  Kernels 6.x have a regression for Audio via HDMI

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Dell Inspiron 16 7610]

  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19

  before and including kernel 5.15 there was a bug that after locking
  the screen and logging back audio via HDMI was disappearing. Later the
  bug was fixed and definitely not present in 5.19

  However, this bug is present in 6.x kernels included in Lunar and
  Mantic as well as in 6.5.7-060507.202310102154

  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.

  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```

  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```

  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP

  ```

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


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

[Kernel-packages] [Bug 2039730] Re: apply nvidia igx patches for Sep 30 - Oct 18

2023-10-19 Thread Jacob Martin

** Description changed:

  Need to update the latest kernel patches for IGX.  There are 4 new
  patches.
+ 
+ 
+ Ankur Pawar (1):
+   NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234
+  
+ Fabrice Gasnier (1):
+   usb: typec: ucsi: don't print PPM init deferred errors
+  
+ Gautham Srinivasan (1):
+   NVIDIA: SAUCE: arm64: configs: enable cifs
+ 
+ Jim Lin (1):
+   NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control

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

Title:
  apply nvidia igx patches for Sep 30 - Oct 18

Status in linux-nvidia-tegra-igx package in Ubuntu:
  New

Bug description:
  Need to update the latest kernel patches for IGX.  There are 4 new
  patches.

  
  Ankur Pawar (1):
NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234
   
  Fabrice Gasnier (1):
usb: typec: ucsi: don't print PPM init deferred errors
   
  Gautham Srinivasan (1):
NVIDIA: SAUCE: arm64: configs: enable cifs

  Jim Lin (1):
NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2039730/+subscriptions


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

[Kernel-packages] [Bug 2039882] Re: Kernels 6.x have a regression for Audio via HDMI

** Description changed:

+ [Dell Inspiron 16 7610]
+ 
  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19
  
  before and including kernel 5.15 there was a bug that after locking the
  screen and logging back audio via HDMI was disappearing. Later the bug
  was fixed and definitely not present in 5.19
  
  However, this bug is present in 6.x kernels included in Lunar and Mantic
  as well as in 6.5.7-060507.202310102154
  
  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.
  
- 
  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```
  
  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```
  
- 
  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP
  
  ```

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

Title:
  Kernels 6.x have a regression for Audio via HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  [Dell Inspiron 16 7610]

  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19

  before and including kernel 5.15 there was a bug that after locking
  the screen and logging back audio via HDMI was disappearing. Later the
  bug was fixed and definitely not present in 5.19

  However, this bug is present in 6.x kernels included in Lunar and
  Mantic as well as in 6.5.7-060507.202310102154

  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.

  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```

  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```

  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP

  ```

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


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

[Kernel-packages] [Bug 2039882] Re: Kernels 6.x have a regression for Audio via HDMI

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039882/+attachment/5711421/+files/lspci-vvnn.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/2039882

Title:
  Kernels 6.x have a regression for Audio via HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19

  before and including kernel 5.15 there was a bug that after locking
  the screen and logging back audio via HDMI was disappearing. Later the
  bug was fixed and definitely not present in 5.19

  However, this bug is present in 6.x kernels included in Lunar and
  Mantic as well as in 6.5.7-060507.202310102154

  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.

  
  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```

  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```

  
  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP

  ```

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


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

[Kernel-packages] [Bug 2039882] [NEW] Kernels 6.x have a regression for Audio via HDMI

Public bug reported:

All kernels of 6.x looks to be missing some port of the bug fix from
5.19

before and including kernel 5.15 there was a bug that after locking the
screen and logging back audio via HDMI was disappearing. Later the bug
was fixed and definitely not present in 5.19

However, this bug is present in 6.x kernels included in Lunar and Mantic
as well as in 6.5.7-060507.202310102154

Currently I rolled back to 5.19 to confirm that this issue is fixed in
this kernel.


```
cat /proc/version_signature > version.log
cat: /proc/version_signature: No such file or directory
```

```
lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
```


```
$ dpkg -l | grep linux-image
ii  linux-image-6.5.0-9-generic   6.5.0-9.9 
  amd64Signed kernel image generic
pi  linux-image-generic   6.5.0.9.11
  amd64Generic Linux kernel image
pi  linux-image-generic-hwe-22.04 6.5.0.9.11
  amd64Generic Linux kernel image
ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939   
  amd64Linux kernel image for version 5.19.17 on 64 bit x86 SMP
ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154 
  amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP

```

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

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/bugs/2039882/+attachment/5711420/+files/uname-a.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/2039882

Title:
  Kernels 6.x have a regression for Audio via HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  All kernels of 6.x looks to be missing some port of the bug fix from
  5.19

  before and including kernel 5.15 there was a bug that after locking
  the screen and logging back audio via HDMI was disappearing. Later the
  bug was fixed and definitely not present in 5.19

  However, this bug is present in 6.x kernels included in Lunar and
  Mantic as well as in 6.5.7-060507.202310102154

  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.

  
  ```
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  ```

  ```
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10
  ```

  
  ```
  $ dpkg -l | grep linux-image
  ii  linux-image-6.5.0-9-generic   6.5.0-9.9   
amd64Signed kernel image generic
  pi  linux-image-generic   6.5.0.9.11  
amd64Generic Linux kernel image
  pi  linux-image-generic-hwe-22.04 6.5.0.9.11  
amd64Generic Linux kernel image
  ii  linux-image-unsigned-5.19.17-051917-generic   5.19.17-051917.202210240939 
amd64Linux kernel image for version 5.19.17 on 64 bit x86 
SMP
  ii  linux-image-unsigned-6.5.7-060507-generic 6.5.7-060507.202310102154   
amd64Linux kernel image for version 6.5.7 on 64 bit x86 SMP

  ```

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


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

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-19 Thread Kyrylo Budnyk

Endre, i can't say exactly when it will be available on Ubuntu
repositories but you always can build the kernel with patch by yourself.

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in linux-signed package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11

2023-10-19 Thread Sergio Durigan Junior

Hi Chris,

Thanks for the patch.  As Timo asked on comment #6, we need to SRU this
into Mantic and Lunar as well, otherwise we break the upgrade path
(Jammy will have the fix, but Mantic/Lunar won't).  Could you please
provide MPs or debdiffs for both releases, too?

Thank you.

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

Title:
  Add SoF topology support on Intel RaptorLake DELL SKU 0C11

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  New

Bug description:
  SRU Jusitification for firmware-sof

  [Impact]
  To support audio functions on RPL Dell SKU 0C11, it requires the topology 
file from sof-tplg-v2.2.7

  [Fix]
  Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from 
https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  [Test Case]
  Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the 
audio function.
  1. Install the firmware-sof on platform(RPL) Dell SKU 0C11
  2. Make sure the audio output/input devices are not dummy in audio settings.

  [Where problems could occur]
  New firmware is only for the RPL platforms which requires the specific 
topology file.

  [Misc]
  https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  

  [Impact]
  Audio play/capture are not functional on specific Dell machines of Intel RPL 
platforms

  [Fix]
  Backport the fix from Intel in https://github.com/thesofproject/linux

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy` shown on the Audio output/input option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

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


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

[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64

2023-10-19 Thread Thadeu Lima de Souza Cascardo

aslr32 libs regressed because of upstream commit 1854bc6e2420
("mm/readahead: Align file mappings for non-DAX").

Some filesystems mmap will try to align the address by the size and when
glibc loaded maps the ELF file, a randomized address will be chosen but
then aligned to the PMD size (21 bits on x86). Given we default to
randomizing 8 bits of the address on 32-bit programs on x86 and the page
size of 4096, we end up clearing the random bits when that alignment is
done.

There are a couple of paths here:

1) revert that upstream commit, losing optimization on transparent huge pages 
due to the PMD aligment for every file mapped by either 32-bit of 64-bit 
programs;
2) do not align for 32-bit programs. I don't expect code to be maintainable 
here.
3) increase the default random bits for 32-bit programs to 16 (the x86 maximum) 
and other sensible values on other platforms (arm64 and ppc64el), which has the 
potential of breaking a few programs, specially ones that require "too much 
memory", but those should be using 64-bit if that is really needed;
4) ignore the issue and leave 32-bit programs vulnerable to attacks.

Given the alternative of leaving programs vulnerable, I would rather
experimenting with changing the default (option 3). The option is
tunable anyway and users should be able to change the setting if
necessary. We could also consider making the behavior tunable and we
actually have THP as a setting, so could as well use it.

Cascardo.

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

Title:
  test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
  K-5.19 / J-OEM-6.1 / J-6.2 AMD64

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  New
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-6.1 source package in Kinetic:
  Invalid

Bug description:
  Issue found on 5.19.0-9.9 Kinetic AMD64 systems

  Test log:
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: 
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs ... (default libs native) (default libs native rekey) (default 
libs COMPAT) FAIL
   
   ==
   FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
   self._test_aslr('libs', expected)
 File "./test-kernel-security.py", line 1727, in _test_aslr
   self._test_aslr_all(area, expected, "default %s" % area)
 File "./test-kernel-security.py", line 1720, in _test_aslr_all
   self._test_aslr_exec(area, expected, target, name)
 File "./test-kernel-security.py", line 1703, in _test_aslr_exec
   self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1203, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: default libs COMPAT:
   Got exit code 1, expected 0
   Command: './aslr32', 'libs', '--verbose'
   Output:
   Checking ASLR of libs:
   0xf7c81790
   0xf7c81790
   0xf7c81790
   FAIL: ASLR not functional (libs always at 0xf7c81790)
   
   
   --
   Ran 1 test in 0.144s
   
   FAILED (failures=1)

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


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

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

This change was made by a bot.

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

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

Title:
  System crash dialogue when opening flatpak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occurred when trying to open flatpak from
  https://flathub.org/apps/com.github.joseexposito.touche in-between
  opening .flatpakref with Discover  store and the Discover store fully
  loading.

  Have encountered previously with other flatpaks - usually but doesn't
  always crash and have installed other flatpaks from flathub after
  trying a few times.

  Everything up to date in apt.

  Hope this report helps in some small way!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-35-generic 6.2.0-35.35
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rich   3967 F wireplumber
   /dev/snd/seq:rich   3960 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 19 19:16:57 2023
  InstallationDate: Installed on 2023-07-20 (91 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: Apple Inc. MacBookPro14,3
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet 
splash vt.handoff=7 initrd=\initrd.img-6.2.0-35-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2023
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 515.0.0.0.0
  dmi.board.name: Mac-551B86E5744E2388
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,3
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-551B86E5744E2388
  dmi.modalias: 
dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

2023-10-19 Thread Juerg Haefliger

Please do not change the status of the ticket manually. It's
automatically updated by automation.

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

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2
  resulting in frequent transmit queue timeouts. Related to ASPM. See
  'original description' below.

  [Test Case]

  Just regular usage for an extended period of time. No transmit queue
  timeouts with RTL8168h/8111h NICs.

  [Where Problems Could Occur]

  Modification are isolated to the r8169 driver so only machine where
  that driver is loaded are affected. Issues could show up as kernel
  crashes, stack traces, non-fnuctional wired network.

  [Original Description]

  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09:

[Kernel-packages] [Bug 2039877] [NEW] System crash dialogue when opening flatpak

2023-10-19 Thread Rade0nfighter

Public bug reported:

Occurred when trying to open flatpak from
https://flathub.org/apps/com.github.joseexposito.touche in-between
opening .flatpakref with Discover  store and the Discover store fully
loading.

Have encountered previously with other flatpaks - usually but doesn't
always crash and have installed other flatpaks from flathub after trying
a few times.

Everything up to date in apt.

Hope this report helps in some small way!

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-35-generic 6.2.0-35.35
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rich   3967 F wireplumber
 /dev/snd/seq:rich   3960 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Oct 19 19:16:57 2023
InstallationDate: Installed on 2023-07-20 (91 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: Apple Inc. MacBookPro14,3
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet 
splash vt.handoff=7 initrd=\initrd.img-6.2.0-35-generic
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-35-generic N/A
 linux-backports-modules-6.2.0-35-generic  N/A
 linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2023
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 515.0.0.0.0
dmi.board.name: Mac-551B86E5744E2388
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,3
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-551B86E5744E2388
dmi.modalias: 
dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug lunar

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

Title:
  System crash dialogue when opening flatpak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occurred when trying to open flatpak from
  https://flathub.org/apps/com.github.joseexposito.touche in-between
  opening .flatpakref with Discover  store and the Discover store fully
  loading.

  Have encountered previously with other flatpaks - usually but doesn't
  always crash and have installed other flatpaks from flathub after
  trying a few times.

  Everything up to date in apt.

  Hope this report helps in some small way!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-35-generic 6.2.0-35.35
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rich   3967 F wireplumber
   /dev/snd/seq:rich   3960 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 19 19:16:57 2023
  InstallationDate: Installed on 2023-07-20 (91 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: Apple Inc. MacBookPro14,3
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet 
splash vt.handoff=7 initrd=\initrd.img-6.2.0-35-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2023
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 515.0.0.0.0
  dmi.board.name: Mac-551B86E5744E2388
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,3
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-551B86E5744E2388
  dmi.modalias: 
dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,3
  dmi.product.version: 1.0

[Kernel-packages] [Bug 2036672] Re: apply nvidia igx patches for Aug 29 - Sep 19

This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1005.5

---
linux-nvidia-tegra-igx (5.15.0-1005.5) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1005.5 -proposed tracker (LP:
#2038956)

  * NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22 (LP: #2031567)
- [Config] updateconfigs for removal of imx219

  * Split iGPU out-of-tree modules into a separate binary package (LP: #2038953)
- [Packaging] linux-nvidia-tegra-igx: update dkms-versions for tegra-oot-igx
  1.0.4-1
- [Packaging] Break out iGPU drivers into a standalone package
- [Config] linux-nvidia-tegra-igx: updateconfigs for iGPU module changes

  * Jammy update: v5.15.117 upstream stable release (LP: #2030107)
- [Config] updateconfigs for BLK_DEV_SX8

  * Jammy update: v5.15.118 upstream stable release (LP: #2030239)
- [Config] updateconfigs for DECNET

  * Please enable Renesas RZ platform serial installer (LP: #2022361)
- [Config] Mark sh-sci as built-in

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- debian/dkms-versions -- update from kernel-versions (main/d2023.08.28)

  * apply nvidia igx patches for Sep 20-29 (LP: #2038165)
- NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla
- NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234
- NVIDIA: SAUCE: memory: tegra: Fix SID override
- dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap()
- dma-buf-map: Rename to iosys-map
- of: Move simple-framebuffer device handling from simplefb to of
- iosys-map: Add offset to iosys_map_memcpy_to()
- iosys-map: Add a few more helpers
- NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points
- drm/format-helper: Add drm_fb_xrgb_to_rgb332()
- drm/format-helper: Add drm_fb_xrgb_to_rgb888()
- drm/gud: Add GUD_PIXEL_FORMAT_R8
- drm/gud: Add GUD_PIXEL_FORMAT_RGB332
- drm/gud: Add GUD_PIXEL_FORMAT_RGB888
- drm/format-helper: Export drm_fb_clip_offset()
- drm/format-helper: Rework format-helper memcpy functions
- drm/format-helper: Add destination-buffer pitch to drm_fb_swab()
- drm/format-helper: Rework format-helper conversion functions
- drm/format-helper: Streamline blit-helper interface
- drm/simpledrm: Enable FB_DAMAGE_CLIPS property
- drm/simpledrm: Support virtual screen sizes
- drm/format-helper: Add drm_fb_xrgb_to_xrgb2101010_toio()
- drm/simpledrm: Add [AX]RGB2101010 formats
- drm/simpledrm: Request memory region in driver
- drm/format-helper: Add drm_fb_xrgb_to_gray8_line()
- drm/format-helper: Add drm_fb_xrgb_to_mono_reversed()
- drm/repaper: Use format helper for xrgb to monochrome conversion
- drm/simpledrm: Use fbdev defaults for shadow buffering
- drm/format-helper: Rename drm_fb_xrgb_to_mono_reversed()
- drm/format-helper: Fix XRGB888 to monochrome conversion
- drm/format_helper: fix a kernel-doc typo
- drm/format-helper: Print warning on missing format conversion
- drm/format-helper: Add RGB888-to-XRGB conversion
- drm/format-helper: Add RGB565-to-XRGB conversion
- drm/format-helper: Implement drm_fb_swab() with per-line helpers
- drm/format-helper: Remove optional byte-swap from line convertion
- drm/format-helper: Unify the parameters of all per-line conversion helpers
- drm/format-helper: Share implementation among conversion helpers
- drm/atomic-helper: Add helper drm_atomic_helper_check_crtc_state()
- drm/fourcc: Add drm_format_info_bpp() helper
- drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers
- drm/simpledrm: Remove mem field from device structure
- drm/simpledrm: Inline device-init helpers
- drm/simpledrm: Remove pdev field from device structure
- drm/simpledrm: Compute framebuffer stride if not set
- drm/simpledrm: Convert to atomic helpers
- drm/format-helper: Provide drm_fb_blit()
- drm/format-helper: Add drm_fb_build_fourcc_list() helper
- drm/simpledrm: Compute linestride with drm_format_info_min_pitch()
- drm/simpledrm: Use drm_atomic_get_new_plane_state()
- drm/simpledrm: Remove !fb check from atomic_update
- drm/simpledrm: Iterate over damage clips
- drm/simpledrm: Synchronize access to GEM BOs
- drm/simpledrm: Set preferred depth from format of scanout buffer
- drm/simpledrm: Use struct iosys_map consistently
- drm/simpledrm: Add support for system memory framebuffers
- drm/simpledrm: Fix an NULL vs IS_ERR() bug
- drm/vgem: use shmem helpers

  * Create modprobe configuration for the IGX kernel (LP: #2037760)
- [Packaging] linux-nvidia-tegra-igx: Update modprobe configuration

  * apply nvidia igx patches for Aug 29 - Sep 19 (LP: #2036672)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT
- NVIDIA: SAUCE:

[Kernel-packages] [Bug 2037760] Re: Create modprobe configuration for the IGX kernel

This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1005.5

---
linux-nvidia-tegra-igx (5.15.0-1005.5) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1005.5 -proposed tracker (LP:
#2038956)

  * NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22 (LP: #2031567)
- [Config] updateconfigs for removal of imx219

  * Split iGPU out-of-tree modules into a separate binary package (LP: #2038953)
- [Packaging] linux-nvidia-tegra-igx: update dkms-versions for tegra-oot-igx
  1.0.4-1
- [Packaging] Break out iGPU drivers into a standalone package
- [Config] linux-nvidia-tegra-igx: updateconfigs for iGPU module changes

  * Jammy update: v5.15.117 upstream stable release (LP: #2030107)
- [Config] updateconfigs for BLK_DEV_SX8

  * Jammy update: v5.15.118 upstream stable release (LP: #2030239)
- [Config] updateconfigs for DECNET

  * Please enable Renesas RZ platform serial installer (LP: #2022361)
- [Config] Mark sh-sci as built-in

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- debian/dkms-versions -- update from kernel-versions (main/d2023.08.28)

  * apply nvidia igx patches for Sep 20-29 (LP: #2038165)
- NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla
- NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234
- NVIDIA: SAUCE: memory: tegra: Fix SID override
- dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap()
- dma-buf-map: Rename to iosys-map
- of: Move simple-framebuffer device handling from simplefb to of
- iosys-map: Add offset to iosys_map_memcpy_to()
- iosys-map: Add a few more helpers
- NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points
- drm/format-helper: Add drm_fb_xrgb_to_rgb332()
- drm/format-helper: Add drm_fb_xrgb_to_rgb888()
- drm/gud: Add GUD_PIXEL_FORMAT_R8
- drm/gud: Add GUD_PIXEL_FORMAT_RGB332
- drm/gud: Add GUD_PIXEL_FORMAT_RGB888
- drm/format-helper: Export drm_fb_clip_offset()
- drm/format-helper: Rework format-helper memcpy functions
- drm/format-helper: Add destination-buffer pitch to drm_fb_swab()
- drm/format-helper: Rework format-helper conversion functions
- drm/format-helper: Streamline blit-helper interface
- drm/simpledrm: Enable FB_DAMAGE_CLIPS property
- drm/simpledrm: Support virtual screen sizes
- drm/format-helper: Add drm_fb_xrgb_to_xrgb2101010_toio()
- drm/simpledrm: Add [AX]RGB2101010 formats
- drm/simpledrm: Request memory region in driver
- drm/format-helper: Add drm_fb_xrgb_to_gray8_line()
- drm/format-helper: Add drm_fb_xrgb_to_mono_reversed()
- drm/repaper: Use format helper for xrgb to monochrome conversion
- drm/simpledrm: Use fbdev defaults for shadow buffering
- drm/format-helper: Rename drm_fb_xrgb_to_mono_reversed()
- drm/format-helper: Fix XRGB888 to monochrome conversion
- drm/format_helper: fix a kernel-doc typo
- drm/format-helper: Print warning on missing format conversion
- drm/format-helper: Add RGB888-to-XRGB conversion
- drm/format-helper: Add RGB565-to-XRGB conversion
- drm/format-helper: Implement drm_fb_swab() with per-line helpers
- drm/format-helper: Remove optional byte-swap from line convertion
- drm/format-helper: Unify the parameters of all per-line conversion helpers
- drm/format-helper: Share implementation among conversion helpers
- drm/atomic-helper: Add helper drm_atomic_helper_check_crtc_state()
- drm/fourcc: Add drm_format_info_bpp() helper
- drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers
- drm/simpledrm: Remove mem field from device structure
- drm/simpledrm: Inline device-init helpers
- drm/simpledrm: Remove pdev field from device structure
- drm/simpledrm: Compute framebuffer stride if not set
- drm/simpledrm: Convert to atomic helpers
- drm/format-helper: Provide drm_fb_blit()
- drm/format-helper: Add drm_fb_build_fourcc_list() helper
- drm/simpledrm: Compute linestride with drm_format_info_min_pitch()
- drm/simpledrm: Use drm_atomic_get_new_plane_state()
- drm/simpledrm: Remove !fb check from atomic_update
- drm/simpledrm: Iterate over damage clips
- drm/simpledrm: Synchronize access to GEM BOs
- drm/simpledrm: Set preferred depth from format of scanout buffer
- drm/simpledrm: Use struct iosys_map consistently
- drm/simpledrm: Add support for system memory framebuffers
- drm/simpledrm: Fix an NULL vs IS_ERR() bug
- drm/vgem: use shmem helpers

  * Create modprobe configuration for the IGX kernel (LP: #2037760)
- [Packaging] linux-nvidia-tegra-igx: Update modprobe configuration

  * apply nvidia igx patches for Aug 29 - Sep 19 (LP: #2036672)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT
- NVIDIA: SAUCE:

[Kernel-packages] [Bug 2038165] Re: apply nvidia igx patches for Sep 20-29

This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1005.5

---
linux-nvidia-tegra-igx (5.15.0-1005.5) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1005.5 -proposed tracker (LP:
#2038956)

  * NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22 (LP: #2031567)
- [Config] updateconfigs for removal of imx219

  * Split iGPU out-of-tree modules into a separate binary package (LP: #2038953)
- [Packaging] linux-nvidia-tegra-igx: update dkms-versions for tegra-oot-igx
  1.0.4-1
- [Packaging] Break out iGPU drivers into a standalone package
- [Config] linux-nvidia-tegra-igx: updateconfigs for iGPU module changes

  * Jammy update: v5.15.117 upstream stable release (LP: #2030107)
- [Config] updateconfigs for BLK_DEV_SX8

  * Jammy update: v5.15.118 upstream stable release (LP: #2030239)
- [Config] updateconfigs for DECNET

  * Please enable Renesas RZ platform serial installer (LP: #2022361)
- [Config] Mark sh-sci as built-in

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- debian/dkms-versions -- update from kernel-versions (main/d2023.08.28)

  * apply nvidia igx patches for Sep 20-29 (LP: #2038165)
- NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla
- NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234
- NVIDIA: SAUCE: memory: tegra: Fix SID override
- dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap()
- dma-buf-map: Rename to iosys-map
- of: Move simple-framebuffer device handling from simplefb to of
- iosys-map: Add offset to iosys_map_memcpy_to()
- iosys-map: Add a few more helpers
- NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points
- drm/format-helper: Add drm_fb_xrgb_to_rgb332()
- drm/format-helper: Add drm_fb_xrgb_to_rgb888()
- drm/gud: Add GUD_PIXEL_FORMAT_R8
- drm/gud: Add GUD_PIXEL_FORMAT_RGB332
- drm/gud: Add GUD_PIXEL_FORMAT_RGB888
- drm/format-helper: Export drm_fb_clip_offset()
- drm/format-helper: Rework format-helper memcpy functions
- drm/format-helper: Add destination-buffer pitch to drm_fb_swab()
- drm/format-helper: Rework format-helper conversion functions
- drm/format-helper: Streamline blit-helper interface
- drm/simpledrm: Enable FB_DAMAGE_CLIPS property
- drm/simpledrm: Support virtual screen sizes
- drm/format-helper: Add drm_fb_xrgb_to_xrgb2101010_toio()
- drm/simpledrm: Add [AX]RGB2101010 formats
- drm/simpledrm: Request memory region in driver
- drm/format-helper: Add drm_fb_xrgb_to_gray8_line()
- drm/format-helper: Add drm_fb_xrgb_to_mono_reversed()
- drm/repaper: Use format helper for xrgb to monochrome conversion
- drm/simpledrm: Use fbdev defaults for shadow buffering
- drm/format-helper: Rename drm_fb_xrgb_to_mono_reversed()
- drm/format-helper: Fix XRGB888 to monochrome conversion
- drm/format_helper: fix a kernel-doc typo
- drm/format-helper: Print warning on missing format conversion
- drm/format-helper: Add RGB888-to-XRGB conversion
- drm/format-helper: Add RGB565-to-XRGB conversion
- drm/format-helper: Implement drm_fb_swab() with per-line helpers
- drm/format-helper: Remove optional byte-swap from line convertion
- drm/format-helper: Unify the parameters of all per-line conversion helpers
- drm/format-helper: Share implementation among conversion helpers
- drm/atomic-helper: Add helper drm_atomic_helper_check_crtc_state()
- drm/fourcc: Add drm_format_info_bpp() helper
- drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers
- drm/simpledrm: Remove mem field from device structure
- drm/simpledrm: Inline device-init helpers
- drm/simpledrm: Remove pdev field from device structure
- drm/simpledrm: Compute framebuffer stride if not set
- drm/simpledrm: Convert to atomic helpers
- drm/format-helper: Provide drm_fb_blit()
- drm/format-helper: Add drm_fb_build_fourcc_list() helper
- drm/simpledrm: Compute linestride with drm_format_info_min_pitch()
- drm/simpledrm: Use drm_atomic_get_new_plane_state()
- drm/simpledrm: Remove !fb check from atomic_update
- drm/simpledrm: Iterate over damage clips
- drm/simpledrm: Synchronize access to GEM BOs
- drm/simpledrm: Set preferred depth from format of scanout buffer
- drm/simpledrm: Use struct iosys_map consistently
- drm/simpledrm: Add support for system memory framebuffers
- drm/simpledrm: Fix an NULL vs IS_ERR() bug
- drm/vgem: use shmem helpers

  * Create modprobe configuration for the IGX kernel (LP: #2037760)
- [Packaging] linux-nvidia-tegra-igx: Update modprobe configuration

  * apply nvidia igx patches for Aug 29 - Sep 19 (LP: #2036672)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT
- NVIDIA: SAUCE:

[Kernel-packages] [Bug 2038953] Re: Split iGPU out-of-tree modules into a separate binary package

This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1005.5

---
linux-nvidia-tegra-igx (5.15.0-1005.5) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1005.5 -proposed tracker (LP:
#2038956)

  * NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22 (LP: #2031567)
- [Config] updateconfigs for removal of imx219

  * Split iGPU out-of-tree modules into a separate binary package (LP: #2038953)
- [Packaging] linux-nvidia-tegra-igx: update dkms-versions for tegra-oot-igx
  1.0.4-1
- [Packaging] Break out iGPU drivers into a standalone package
- [Config] linux-nvidia-tegra-igx: updateconfigs for iGPU module changes

  * Jammy update: v5.15.117 upstream stable release (LP: #2030107)
- [Config] updateconfigs for BLK_DEV_SX8

  * Jammy update: v5.15.118 upstream stable release (LP: #2030239)
- [Config] updateconfigs for DECNET

  * Please enable Renesas RZ platform serial installer (LP: #2022361)
- [Config] Mark sh-sci as built-in

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- debian/dkms-versions -- update from kernel-versions (main/d2023.08.28)

  * apply nvidia igx patches for Sep 20-29 (LP: #2038165)
- NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla
- NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234
- NVIDIA: SAUCE: memory: tegra: Fix SID override
- dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap()
- dma-buf-map: Rename to iosys-map
- of: Move simple-framebuffer device handling from simplefb to of
- iosys-map: Add offset to iosys_map_memcpy_to()
- iosys-map: Add a few more helpers
- NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points
- drm/format-helper: Add drm_fb_xrgb_to_rgb332()
- drm/format-helper: Add drm_fb_xrgb_to_rgb888()
- drm/gud: Add GUD_PIXEL_FORMAT_R8
- drm/gud: Add GUD_PIXEL_FORMAT_RGB332
- drm/gud: Add GUD_PIXEL_FORMAT_RGB888
- drm/format-helper: Export drm_fb_clip_offset()
- drm/format-helper: Rework format-helper memcpy functions
- drm/format-helper: Add destination-buffer pitch to drm_fb_swab()
- drm/format-helper: Rework format-helper conversion functions
- drm/format-helper: Streamline blit-helper interface
- drm/simpledrm: Enable FB_DAMAGE_CLIPS property
- drm/simpledrm: Support virtual screen sizes
- drm/format-helper: Add drm_fb_xrgb_to_xrgb2101010_toio()
- drm/simpledrm: Add [AX]RGB2101010 formats
- drm/simpledrm: Request memory region in driver
- drm/format-helper: Add drm_fb_xrgb_to_gray8_line()
- drm/format-helper: Add drm_fb_xrgb_to_mono_reversed()
- drm/repaper: Use format helper for xrgb to monochrome conversion
- drm/simpledrm: Use fbdev defaults for shadow buffering
- drm/format-helper: Rename drm_fb_xrgb_to_mono_reversed()
- drm/format-helper: Fix XRGB888 to monochrome conversion
- drm/format_helper: fix a kernel-doc typo
- drm/format-helper: Print warning on missing format conversion
- drm/format-helper: Add RGB888-to-XRGB conversion
- drm/format-helper: Add RGB565-to-XRGB conversion
- drm/format-helper: Implement drm_fb_swab() with per-line helpers
- drm/format-helper: Remove optional byte-swap from line convertion
- drm/format-helper: Unify the parameters of all per-line conversion helpers
- drm/format-helper: Share implementation among conversion helpers
- drm/atomic-helper: Add helper drm_atomic_helper_check_crtc_state()
- drm/fourcc: Add drm_format_info_bpp() helper
- drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers
- drm/simpledrm: Remove mem field from device structure
- drm/simpledrm: Inline device-init helpers
- drm/simpledrm: Remove pdev field from device structure
- drm/simpledrm: Compute framebuffer stride if not set
- drm/simpledrm: Convert to atomic helpers
- drm/format-helper: Provide drm_fb_blit()
- drm/format-helper: Add drm_fb_build_fourcc_list() helper
- drm/simpledrm: Compute linestride with drm_format_info_min_pitch()
- drm/simpledrm: Use drm_atomic_get_new_plane_state()
- drm/simpledrm: Remove !fb check from atomic_update
- drm/simpledrm: Iterate over damage clips
- drm/simpledrm: Synchronize access to GEM BOs
- drm/simpledrm: Set preferred depth from format of scanout buffer
- drm/simpledrm: Use struct iosys_map consistently
- drm/simpledrm: Add support for system memory framebuffers
- drm/simpledrm: Fix an NULL vs IS_ERR() bug
- drm/vgem: use shmem helpers

  * Create modprobe configuration for the IGX kernel (LP: #2037760)
- [Packaging] linux-nvidia-tegra-igx: Update modprobe configuration

  * apply nvidia igx patches for Aug 29 - Sep 19 (LP: #2036672)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT
- NVIDIA: SAUCE:

[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

2023-10-19 Thread Mario Limonciello

This is the upstream fix for this issue:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324

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

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Kernel-packages] [Bug 2039731] Re: After upgrade 20.04 LTS -> 23.10, closing laptop lid causes all GUI apps to be quit

2023-10-19 Thread Mario Limonciello

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

I was just checking a Lenovo X13 for another issue and reproduced the
same thing.  This is a duplicate of that other bug.

** This bug has been marked a duplicate of bug 2034619
   [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in 
Wayland

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

Title:
  After upgrade 20.04 LTS -> 23.10, closing laptop lid causes all GUI
  apps to be quit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a brand new Lenovo ThinkPad T14 (AMD) Gen 3 with touchscreen. I
  was told this is a good laptop for Linux and Lenovo says it is
  "certified" on Ubuntu 20.04.

  Yesterday I installed Ubuntu 22.04 LTS off a USB stick. It worked
  pretty well. Later in the day I decided to upgrade to a newer Ubuntu
  and installed Ubuntu 23.10 off a USB stick (I did not upgrade, I told
  it to delete the partition and create a new one). This has had a
  couple new, serious problems (see also
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
  daemon/+bug/2039722 ).

  With 23.10 I am seeing a behavior where if I close the lid, wait for
  the red light on the Thinkpad logo to begin blinking to indicate it is
  in sleep, then open the lid, it asks me to log in, and when I log in I
  am looking at a new, blank desktop session. All my apps have been
  quit. I see this behavior both when I am plugged into power and when I
  am not plugged into power. I am 95% certain I did not see this
  yesterday in 22.04 LTS. I closed and reopened the laptop multiple
  times.

  I have made fumbling attempts to fix this myself but because this is a
  common laptop, Lenovo-certified with Ubuntu, with default settings,
  and I *THINK* it is a regression (seemed to work with 22.04 LTS?) I
  think it should work out of the box.

  MY FUMBLING ATTEMPTS TO FIX THIS MYSELF

  I learned Linux on servers and before the systemd era. I do not
  currently know how to find out: - Where is there a log of which
  applications have crashed, and when? - Where is there a log of
  reboots? On Windows there is an "event viewer" which tells you the
  last reboot (and whether it was caused by a power event, the OS or
  user requesting the reboot, or what). At the moment I don't know in
  Linux if it is trying to hibernate and failing, intentionally powering
  down, or if it is correctly hibernating and waking but at some step a
  critical software (like the wayland server) is dying. I am happy to
  gather any information needed.

  The Arch wiki, which in my experience is often a good source of
  general Linux information, has a page on this device
  https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14_(AMD)_Gen_3
  containing the suspicious line:

  "According to Lenovo staff the CPU generation in this device only
  supports s2idle and not S3 sleep."

  They recommend running: $ cat /sys/power/mem_sleep to see what suspend
  methods are "advertised". This file contains only the line "[s2idle]".
  The arch wiki says that "shallow" or "deep" should be next to s2idle
  and I want to pick one of them. But I don't see either of those so I
  don't know how to proceed. Google searching seems to imply that this
  is about hibernating vs going into some special mode. Arch wiki also
  says:

  "If you run system firmware version 0.1.17 do not set the suspend mode
  in UEFI setup to Linux (S3). This sleep mode is not supported by the
  CPU. If you set S3 mode and upgrade the system firmware you need to do
  a downgrade to 0.1.17 to change it back, because the option is removed
  in newer firmware. If you set S3 mode nevertheless and try to suspend
  to mem/S3 mode the system will crash and you need to reset it by
  holding the power button for a few seconds."

  I have not yet explored this in the pre-OS UEFI settings but will try
  that after filing this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 15:08:29 2023
  InstallationDate: Installed on 2023-10-18 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=ecb1730b-cbe1-457c-a4f8-23e2eaf89020 ro

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

2023-10-19 Thread Garry

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

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2
  resulting in frequent transmit queue timeouts. Related to ASPM. See
  'original description' below.

  [Test Case]

  Just regular usage for an extended period of time. No transmit queue
  timeouts with RTL8168h/8111h NICs.

  [Where Problems Could Occur]

  Modification are isolated to the r8169 driver so only machine where
  that driver is loaded are affected. Issues could show up as kernel
  crashes, stack traces, non-fnuctional wired network.

  [Original Description]

  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09: 

  [Mon Aug 7 12:39:19 2023] R10:  R11:  R12: 
9979968684c8

[Kernel-packages] [Bug 2039869] Re: Devlink reload hangs: fix race and lock issue

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

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

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: Fix Committed => In Progress

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

Title:
  Devlink reload hangs: fix race and lock issue

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

Bug description:
  Summary:
  Machine hangs when doing devlink reload

  How to reproduce:
  Host:
  [root@bu-lab24v ~]# echo '2' > /sys/class/net/ens2f0np0/device/sriov_numvfs  

  Arm:
  root@bu-lab24v-oob:~# uname -r
  5.15.0-1027-bluefield
  root@bu-lab24v-oob:~# devlink dev eswitch set pci/:03:00.0 mode switchdev
  root@bu-lab24v-oob:~# devlink dev reload pci/:03:00.0
  *Hangs*

  Arm dmesg:
  [ 1089.747409] INFO: task devlink:8753 blocked for more than 120 seconds.
  [ 1089.760560]   Tainted: G   OE 5.15.0-1027-bluefield 
#29-Ubuntu
  [ 1089.775086] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1089.790829] task:devlink state:D stack:0 pid: 8753 ppid:  5090 
flags:0x0004
  [ 1089.790838] Call trace:
  [ 1089.790840]  __switch_to+0xf8/0x150
  [ 1089.790857]  __schedule+0x2b8/0x790
  [ 1089.790865]  schedule+0x64/0x140
  [ 1089.790870]  schedule_preempt_disabled+0x18/0x24
  [ 1089.790874]  __mutex_lock.constprop.0+0x1a0/0x680
  [ 1089.790878]  __mutex_lock_slowpath+0x40/0x90
  [ 1089.790883]  mutex_lock+0x64/0x70
  [ 1089.790887]  devl_lock+0x1c/0x30
  [ 1089.790893]  mlx5_detach_device+0x58/0x190 [mlx5_core]
  [ 1089.791055]  mlx5_unload_one+0x40/0xe4 [mlx5_core]
  [ 1089.791177]  mlx5_devlink_reload_down+0x184/0x270 [mlx5_core]
  [ 1089.791318]  devlink_reload+0x214/0x290

  Fixes:
  Checking the OFED source code, we found this missing devl trap group
  also need to be backported to avoid deadlock.

  void mlx5_detach_device(struct mlx5_core_dev *dev, bool suspend)
  {
  ...
  #ifdef HAVE_DEVL_PORT_REGISTER
  #ifdef HAVE_DEVL_TRAP_GROUPS_REGISTER
  devl_assert_locked(priv_to_devlink(dev));
  #else
  devl_lock(devlink);
  #endif /* HAVE_DEVL_TRAP_GROUPS_REGISTER */
  #endif /* HAVE_DEVL_PORT_REGISTER */
  mutex_lock(_intf_mutex);
  #ifdef HAVE_DEVL_PORT_REGISTER

  Related issue:
  #2032378 Devlink backport: fix race and lock issue

  So cherry-pick the patch below
  commit 852e85a704c2e11c050bdea286bc438aba4f4a22
  Author: Jiri Pirko 
  Date:   Sat Jul 16 13:02:34 2022 +0200

  net: devlink: add unlocked variants of devling_trap*() functions

  Add unlocked variants of devl_trap*() functions to be used in drivers
  called-in with devlink->lock held.

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


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

[Kernel-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

2023-10-19 Thread Erich Eickmeyer

Working with Pirouette on IRC, we determined this may be related to
https://bugzilla.kernel.org/show_bug.cgi?id=201957#c94 in which the
solution, sadly, was to add amdgpu.mcbp=0 to the kernel boot parameters.
Per that bug report, it does appear as though this might be the result
of a regression in the 6.5 kernel as they did not experience this issue
in prior kernels or Ubuntu 23.04.

They also found mentions of
https://gitlab.freedesktop.org/drm/amd/-/issues/2848 where Kernel 6.6
has a fix which we could pull a patch from, and we might have a patch
for mesa at
https://gitlab.freedesktop.org/drm/amd/-/issues/2848#note_2095536.

** Also affects: mesa (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/2039868

Title:
  amdgpu reset during usage of firefox

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

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  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:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

2023-10-19 Thread Pirouette Cacahuète

https://gitlab.freedesktop.org/drm/amd/-/issues/2848#note_2108686

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

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

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

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

Title:
  amdgpu reset during usage of firefox

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

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  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:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2039869] [NEW] Devlink reload hangs: fix race and lock issue

2023-10-19 Thread William Tu

Public bug reported:

Summary:
Machine hangs when doing devlink reload

How to reproduce:
Host:
[root@bu-lab24v ~]# echo '2' > /sys/class/net/ens2f0np0/device/sriov_numvfs  

Arm:
root@bu-lab24v-oob:~# uname -r
5.15.0-1027-bluefield
root@bu-lab24v-oob:~# devlink dev eswitch set pci/:03:00.0 mode switchdev
root@bu-lab24v-oob:~# devlink dev reload pci/:03:00.0
*Hangs*

Arm dmesg:
[ 1089.747409] INFO: task devlink:8753 blocked for more than 120 seconds.
[ 1089.760560]   Tainted: G   OE 5.15.0-1027-bluefield 
#29-Ubuntu
[ 1089.775086] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1089.790829] task:devlink state:D stack:0 pid: 8753 ppid:  5090 
flags:0x0004
[ 1089.790838] Call trace:
[ 1089.790840]  __switch_to+0xf8/0x150
[ 1089.790857]  __schedule+0x2b8/0x790
[ 1089.790865]  schedule+0x64/0x140
[ 1089.790870]  schedule_preempt_disabled+0x18/0x24
[ 1089.790874]  __mutex_lock.constprop.0+0x1a0/0x680
[ 1089.790878]  __mutex_lock_slowpath+0x40/0x90
[ 1089.790883]  mutex_lock+0x64/0x70
[ 1089.790887]  devl_lock+0x1c/0x30
[ 1089.790893]  mlx5_detach_device+0x58/0x190 [mlx5_core]
[ 1089.791055]  mlx5_unload_one+0x40/0xe4 [mlx5_core]
[ 1089.791177]  mlx5_devlink_reload_down+0x184/0x270 [mlx5_core]
[ 1089.791318]  devlink_reload+0x214/0x290

Fixes:
Checking the OFED source code, we found this missing devl trap group
also need to be backported to avoid deadlock.

void mlx5_detach_device(struct mlx5_core_dev *dev, bool suspend)
{
...
#ifdef HAVE_DEVL_PORT_REGISTER
#ifdef HAVE_DEVL_TRAP_GROUPS_REGISTER
devl_assert_locked(priv_to_devlink(dev));
#else
devl_lock(devlink);
#endif /* HAVE_DEVL_TRAP_GROUPS_REGISTER */
#endif /* HAVE_DEVL_PORT_REGISTER */
mutex_lock(_intf_mutex);
#ifdef HAVE_DEVL_PORT_REGISTER

Related issue:
#2032378 Devlink backport: fix race and lock issue

So cherry-pick the patch below
commit 852e85a704c2e11c050bdea286bc438aba4f4a22
Author: Jiri Pirko 
Date:   Sat Jul 16 13:02:34 2022 +0200

net: devlink: add unlocked variants of devling_trap*() functions

Add unlocked variants of devl_trap*() functions to be used in drivers
called-in with devlink->lock held.

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

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

Title:
  Devlink reload hangs: fix race and lock issue

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  Summary:
  Machine hangs when doing devlink reload

  How to reproduce:
  Host:
  [root@bu-lab24v ~]# echo '2' > /sys/class/net/ens2f0np0/device/sriov_numvfs  

  Arm:
  root@bu-lab24v-oob:~# uname -r
  5.15.0-1027-bluefield
  root@bu-lab24v-oob:~# devlink dev eswitch set pci/:03:00.0 mode switchdev
  root@bu-lab24v-oob:~# devlink dev reload pci/:03:00.0
  *Hangs*

  Arm dmesg:
  [ 1089.747409] INFO: task devlink:8753 blocked for more than 120 seconds.
  [ 1089.760560]   Tainted: G   OE 5.15.0-1027-bluefield 
#29-Ubuntu
  [ 1089.775086] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1089.790829] task:devlink state:D stack:0 pid: 8753 ppid:  5090 
flags:0x0004
  [ 1089.790838] Call trace:
  [ 1089.790840]  __switch_to+0xf8/0x150
  [ 1089.790857]  __schedule+0x2b8/0x790
  [ 1089.790865]  schedule+0x64/0x140
  [ 1089.790870]  schedule_preempt_disabled+0x18/0x24
  [ 1089.790874]  __mutex_lock.constprop.0+0x1a0/0x680
  [ 1089.790878]  __mutex_lock_slowpath+0x40/0x90
  [ 1089.790883]  mutex_lock+0x64/0x70
  [ 1089.790887]  devl_lock+0x1c/0x30
  [ 1089.790893]  mlx5_detach_device+0x58/0x190 [mlx5_core]
  [ 1089.791055]  mlx5_unload_one+0x40/0xe4 [mlx5_core]
  [ 1089.791177]  mlx5_devlink_reload_down+0x184/0x270 [mlx5_core]
  [ 1089.791318]  devlink_reload+0x214/0x290

  Fixes:
  Checking the OFED source code, we found this missing devl trap group
  also need to be backported to avoid deadlock.

  void mlx5_detach_device(struct mlx5_core_dev *dev, bool suspend)
  {
  ...
  #ifdef HAVE_DEVL_PORT_REGISTER
  #ifdef HAVE_DEVL_TRAP_GROUPS_REGISTER
  devl_assert_locked(priv_to_devlink(dev));
  #else
  devl_lock(devlink);
  #endif /* HAVE_DEVL_TRAP_GROUPS_REGISTER */
  #endif /* HAVE_DEVL_PORT_REGISTER */
  mutex_lock(_intf_mutex);
  #ifdef HAVE_DEVL_PORT_REGISTER

  Related issue:
  #2032378 Devlink backport: fix race and lock issue

  So cherry-pick the patch below
  commit 852e85a704c2e11c050bdea286bc438aba4f4a22
  Author: Jiri Pirko 
  Date:   Sat Jul 16 13:02:34 2022 +0200

  net: devlink: add unlocked variants of devling_trap*() functions

  Add unlocked variants of devl_trap*() functions to be used in drivers
  called-in with devlink->lock held.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2039868] [NEW] amdgpu reset during usage of firefox

2023-10-19 Thread Pirouette Cacahuète

Public bug reported:

Running nightly on 23.10 (since monday), I have been experiencing a few
amdgpu resets in the past hours

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-9-generic N/A
 linux-backports-modules-6.5.0-9-generic  N/A
 linux-firmware   20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
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:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug mantic

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

Title:
  amdgpu reset during usage of firefox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  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:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

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

This change was made by a bot.

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

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

Title:
  amdgpu reset during usage of firefox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  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:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2039773] Re: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-10-19 Thread Hans Joachim Desserud

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

** This bug has been marked a duplicate of bug 2039772
   package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

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

Title:
  package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-31-generic 6.2.0-31.31
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  beyagu 1865 F pulseaudio
   /dev/snd/pcmC0D0p:   beyagu 1865 F...m pulseaudio
   /dev/snd/controlC1:  beyagu 1865 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Oct 18 06:39:04 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-06-28 (112 days ago)
  InstallationMedia: Ubuntu-Unity 23.04 "Lunar Lobster" - Release amd64 
(20230419)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=603facbe-a5f3-4d8a-b62d-bd59c2ddf5c4 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   
  SourcePackage: dkms
  Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/19/2017:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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

[Kernel-packages] [Bug 2035123] Re: scripts/pahole-flags.sh change return to exit 0

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  scripts/pahole-flags.sh change return to exit 0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-bluefield package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  In Progress
Status in linux-bluefield source package in Jammy:
  Fix Committed

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

  [Impact]

  When building the Jammy linux-bluefield kernel tree on a system
  without pahole installed, the following warning is emitted:

  ./scripts/pahole-flags.sh: line 7: return: can only `return' from a
  function or sourced script

  scripts/pahole-flags.sh attempts to return from an if statement that
  is not within a function, and generates a warning.

  The fix is straightforward, changing return to an exit 0.

  --- a/scripts/pahole-flags.sh
  +++ b/scripts/pahole-flags.sh
  @@ -4,7 +4,7 @@
   extra_paholeopt=

   if ! [ -x "$(command -v ${PAHOLE})" ]; then
  -   return
  +   exit 0
   fi

  [Testcase]

  Clone the linux-bluefield kernel tree and build it on a arm64 system without
  pahole installed.

  A test kernel is available with the fix applied in:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test

  Both linux-bluefield and ubuntu-jammy build correctly.

  [Fix]

  This was fixed by Linus Torvalds in the following merge commit:

  commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
  Merge: bfc484fe6abb 84882cf72cd7
  Author: Linus Torvalds 
  Date:   Tue Nov 2 06:20:58 2021 -0700
  Subject: Merge tag 'net-next-for-5.16' of 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4

  Note, the original commit does not have the fix included:

  commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
  Author: Jiri Olsa 
  Date:   Fri Oct 29 14:57:29 2021 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8

  The Ubuntu kernel cherry-picked the original commit and did not pick up the
  silent fix made in the merge commit. Submitting the silent fix as a SAUCE 
patch
  with changelog describing the change.

  Note: I know SAUCE patches are bad, but in this scenario, to revert
  the initial commit and re-apply the fixed version would require us to
  revert two additional dependency commits, making six patches to
  review, vs, a one line change in a SAUCE commit that has a real
  changelog entry.

  [Where problems could occur]

  The Ubuntu kernel is built with pahole enabled, and requires pahole to
  be installed as a build dependency. It is extremely unlikely that any
  users are disabling pahole at build time, apart from linux-bluefield
  engineers.

  If a regression were to occur, engineers would see errors during build
  time about scripts/pahole-flags.sh not executing properly.

  [Other info]

  Linus remarked about the issue in the following lkml discussion:

  
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
  
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/

  This was silently Incorporated into the linux-stable commit:

  commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
  From: Jiri Olsa 
  Date: Sun, 4 Sep 2022 15:19:00 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7

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


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

[Kernel-packages] [Bug 2038868] Re: gpio-mlxbf3: support valid mask

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  gpio-mlxbf3: support valid mask

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

Bug description:
  SRU Justification:

  [Impact]

  After syncing up the gpio-mlxbf3.c driver with the upstreamed version, we 
dropped the use of the valid_mask variable because kernels greater or equal to 
6.2.0 dont need it.
  This is no longer needed in kernel versions >= 6.2.0 because valid_mask is 
populated by core gpio code.
  5.15 kernel doesnt support that feature so we still need to explicitly define 
valid_mask like we did before. 
  This doesnt impact the functionality of the GPIO driver but it is a security 
breach as it doesnt restrict the access to only gpios defined in the acpi table 
by valid_mask.

  [Fix]

  * define valid_mask and init_valid_mask

  [Test Case]

  * Make sure that the user (libgpiod) cannot access any other gpio
  besides 0->4 (gpiochip0) and 22-23 in gpiochip1.

  [Regression Potential]

  no known regression.

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


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

[Kernel-packages] [Bug 2039561] Re: mlxbf_pmc: Replace sauce patches with upstream commits

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  mlxbf_pmc: Replace sauce patches with upstream commits

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

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_pmc BlueField platform driver in the Jammy repo
  consists of some SAUCE patches. These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality. 2 patches are from
  upstream linux, while the 3rd is from linux-next.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Test sysfs interface exposed by driver for programming various
  counters and events.

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been
  well-tested and the functionality is the same.

  [Other]
  n/a

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


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

[Kernel-packages] [Bug 2039325] Re: mmc: sdhci-of-dwcmshc: Intermittent data error under stress test

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  mmc: sdhci-of-dwcmshc: Intermittent data error under stress test

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

Bug description:
  sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110

  SRU Justification:

  [Impact]
  This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: 
__mmc_blk_ioctl_cmd: data error -110" error under stress test

  [Fix]
  The fix added a quirk for the BF3 sdhci driver to avoid such data error.

  [Test Case]
  1. Same functionality and testing as on BlueField-1/2.
  2. Install OS on NVME, and run the FIO test on EMMC.
  fio --name=mmcblk0_randrw_stress_round_1 \
--ioengine=libaio --direct=1  --time_based=1 \
--end_fsync=1 --ramp_time=5 --norandommap=1 \
--randrepeat=0 --group_reporting=1 --numjobs=8 \
--iodepth=128 --rw=randrw --overwrite=1 \
--runtime=3600 --bs=4K --filename=/dev/mmcblk0 &

  
  [Regression Potential]
  Same behavior from user perspective.

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


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

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

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

apport-collect 2039816

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

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

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

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

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

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

Title:
  Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node
  scobee-kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  Issue found on ARM64 node scobee-kernel with:
   * J-5.15.0-86.95 lowlatency
   * 5.15.0-85.95~20.04.2 generic
   * F-5.15.0-86.95~20.04.1 lowlatency
   * F-5.15.0-87.96~20.04.1 lowlatency-64k

  Test failed with:
  $ sudo ./vrf-xfrm-tests.sh

  No qdisc on VRF device
  TEST: IPv4 no xfrm policy   [ OK ]
  TEST: IPv6 no xfrm policy   [ OK ]
  TEST: IPv4 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy with VRF in selector [ OK ]
  TEST: IPv4 xfrm policy with xfrm device [FAIL]
  TEST: IPv6 xfrm policy with xfrm device [FAIL]

  netem qdisc on VRF device
  TEST: IPv4 no xfrm policy   [ OK ]
  TEST: IPv6 no xfrm policy   [ OK ]
  TEST: IPv4 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy with VRF in selector [ OK ]
  TEST: IPv4 xfrm policy with xfrm device [FAIL]
  TEST: IPv6 xfrm policy with xfrm device [FAIL]

  Tests passed:   6
  Tests failed:   8

  And this issue does not exist with the following combination:
  * F-generic-5.15.0-86.96~20.04.1 howzit-kernel
  * F-generic-5.15.0-86.96~20.04.1 wright-kernel
  * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel
  * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel
  * F-lowlatency-5.15.0-85.94 starmie-kernel
  * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel
  * J-lowlatency-64k-5.15.0-85.94 starmie-kernel
  * J-lowlatency-64k-5.15.0-86.95 howzit-kernel

  So it looks like this is hardware related.

  And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: 
change authentication and encryption algos"), which lands on the Jammy tree 
since:
   * Ubuntu-5.15.0-85.95
   * Ubuntu-lowlatency-5.15.0-85.94

  With this commit reverted, this test can pass on node scobee-kernel
  with 5.15.0-87-lowlatency-64k

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2023-10-19 Thread Lukas Märdian

** Changed in: systemd (Ubuntu)
   Status: Invalid => 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/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2036742] Re: amdgpu crash on Mantic

2023-10-19 Thread Mario Limonciello

> the firmware on mantic is zstd compressed, so mainline builds from the
past can't load the firmware..

As a hack then maybe just clone https://gitlab.com/kernel-
firmware/linux-firmware and put everything (uncompressed) in
/lib/firmware/updates/ to get by that.

Or run the check on Jammy instead.

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

Title:
  amdgpu crash on Mantic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Booting from USB the latest Mantic Desktop daily image (2023-09-20),
  just after the initial logs, nothing is displayed on screen. The
  system is still alive since _autoinstall_ works as intended. Once
  provisioned, the problem is still present.

  It seems related to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/2029396 .

  dmesg attached.

  [Test Case]

  Live boot Ubuntu Mantic Desktop canary (2023-09-19)

  [Where Problems Could Occur]

  Dell Optiplex 5090
  - Intel Core(TM) i7-11700
  - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f

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


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

[Kernel-packages] [Bug 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel

2023-10-19 Thread Po-Hsu Lin

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

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

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

Title:
  Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node
  scobee-kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New

Bug description:
  Issue found on ARM64 node scobee-kernel with:
   * J-5.15.0-86.95 lowlatency
   * 5.15.0-85.95~20.04.2 generic
   * F-5.15.0-86.95~20.04.1 lowlatency
   * F-5.15.0-87.96~20.04.1 lowlatency-64k

  Test failed with:
  $ sudo ./vrf-xfrm-tests.sh

  No qdisc on VRF device
  TEST: IPv4 no xfrm policy   [ OK ]
  TEST: IPv6 no xfrm policy   [ OK ]
  TEST: IPv4 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy with VRF in selector [ OK ]
  TEST: IPv4 xfrm policy with xfrm device [FAIL]
  TEST: IPv6 xfrm policy with xfrm device [FAIL]

  netem qdisc on VRF device
  TEST: IPv4 no xfrm policy   [ OK ]
  TEST: IPv6 no xfrm policy   [ OK ]
  TEST: IPv4 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy based on address [FAIL]
  TEST: IPv6 xfrm policy with VRF in selector [ OK ]
  TEST: IPv4 xfrm policy with xfrm device [FAIL]
  TEST: IPv6 xfrm policy with xfrm device [FAIL]

  Tests passed:   6
  Tests failed:   8

  And this issue does not exist with the following combination:
  * F-generic-5.15.0-86.96~20.04.1 howzit-kernel
  * F-generic-5.15.0-86.96~20.04.1 wright-kernel
  * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel
  * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel
  * F-lowlatency-5.15.0-85.94 starmie-kernel
  * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel
  * J-lowlatency-64k-5.15.0-85.94 starmie-kernel
  * J-lowlatency-64k-5.15.0-86.95 howzit-kernel

  So it looks like this is hardware related.

  And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: 
change authentication and encryption algos"), which lands on the Jammy tree 
since:
   * Ubuntu-5.15.0-85.95
   * Ubuntu-lowlatency-5.15.0-85.94

  With this commit reverted, this test can pass on node scobee-kernel
  with 5.15.0-87-lowlatency-64k

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


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

[Kernel-packages] [Bug 2039858] [NEW] Wireless not working on Dell XPS 9320 1360P (Intel 6E AX211 Wireless card) with kernel version 6.1.0-1023-oem on Ubuntu 22.04

2023-10-19 Thread Ory Band

Public bug reported:

Posting here since there are barely any reports on this issue except
this Intel community forum ticket.
https://community.intel.com/t5/Wireless/Wifi-is-not-working-on-
ubuntu/m-p/1532192/thread-id/50189

In recent days (Oct 16 2023) wireless suddenly stopped working and the
"wireless adapter not found" message is printed in Ubuntu's Wireless
settings. The above ticket has most of the technical details, but it
looks like it's an issue with the recent kernel version 6.1.0-1023-oem
and happens on Dell XPS 9320 with Intel 6E AX211 Wireless Card.

Note Intel have returned to the issue submitter and ask him to turn the
issue back to Dell. Beats me why can't these two corporations figure the
issue on their own and ask the user to act as a proxy.

The current temporary solution until this issue is investigated and
resolved is to downgrade the kernel version. The second most recent
version I had available was 6.0.0-1021-oem and it resolved the issue. I
followed this guide and it resolved it for me.
https://www.groovypost.com/howto/how-to-downgrade-the-kernel-in-ubuntu/

Note that running Ubuntu updates can re-update your kernel version back.

Link to "Ask Ubuntu" question since this issue took a considerable
amount of my time to pinpoint. Hoping to save others the trouble:
https://askubuntu.com/questions/1489313/wireless-not-working-on-dell-
xps-9320-1360p-intel-6e-ax211-wireless-card-with

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

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

Title:
Wireless not working on Dell XPS 9320 1360P (Intel 6E AX211 Wireless
card) with kernel version 6.1.0-1023-oem on Ubuntu 22.04

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

Bug description:
Posting here since there are barely any reports on this issue except
this Intel community forum ticket.
https://community.intel.com/t5/Wireless/Wifi-is-not-working-on-
ubuntu/m-p/1532192/thread-id/50189

Note Intel have returned to the issue submitter and ask him to turn
the issue back to Dell. Beats me why can't these two corporations
figure the issue on their own and ask the user to act as a proxy.

The current temporary solution until this issue is investigated and
resolved is to downgrade the kernel version. The second most recent
version I had available was 6.0.0-1021-oem and it resolved the issue.
I followed this guide and it resolved it for me.
https://www.groovypost.com/howto/how-to-downgrade-the-kernel-in-
ubuntu/

Note that running Ubuntu updates can re-update your kernel version
back.

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

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

[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard

2023-10-19 Thread Jarkko Korpi

still an issue, latest 5.15 series kernel that Linux Mint 21.2 currently
provides. 5.15.0-87-generic (available today)

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

Title:
  platform eisa.0: EISA: Cannot allocate resource for mainboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard
  [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1
  [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2
  [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3
  [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4
  [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5
  [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6
  [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7
  [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3028 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   3028 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 21 12:16:07 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (230 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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

2023-10-19 Thread Jarkko Korpi

there was upgrade today, 5.15.0-87-generic. I sm not able to see the out
of bounds or crash anymore so I am going to close this as fixed.

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

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

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

Status in linux package in Ubuntu:
  Fix Committed

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:

[Kernel-packages] [Bug 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video output cuts out

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.113.01-0ubuntu0.20.04.3

---
nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.20.04.3) focal; urgency=medium

  * debian/rules:
- Add override_dh_installsystemd.
- Pass in dh_installsystemd --no-restart-after-upgrade.

nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.20.04.2) focal;
urgency=medium

  * debian/rules:
   - Pass in --no-stop-on-upgrade to dh_installsystemd.
 Prevent dh_installsystemd from stopping services (LP: #2025640).

 -- Alberto Milone   Fri, 29 Sep 2023
18:03:34 +

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to
  535.54.03 video output cuts out

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  The current version nvidia-graphics-drivers-535 and nvidia-graphics-
  drivers-535-server, from Focal on, use the default values (from the
  debian compat 10) for dh_installsystemd which cause all the systemd
  services to be restarted on upgrade. This will cause the screen to go
  blank and never wake up.

  [Test Case]

  Install the nvidia-driver:
  sudo ubuntu-drivers install nvidia:535

  Try re-installing nvidia-kernel-common-535 and nvidia-compute-
  utils-535:

  sudo apt --reinstall nvidia-kernel-common-535 nvidia-compute-utils-535

  The screen will go black.

  [Where problems could occur]

  On servers with no display server in use, if, for some reason,
  restarting services such as nvidia-persistenced on upgrade is a
  desired feature, this will not take place any more.

  _
  
https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588

  https://forums.linuxmint.com/viewtopic.php?p=2344294

  timeline 10:36 - 10:39
  switch to TTY not helped-no video output, SSH not tested

  After emergency sync, reboot (by sysrq), is all fine.

  Jul  3 10:37:14 Panter nvidia-persistenced: Received signal 15
  Jul  3 10:37:14 Panter systemd[1]: Stopping NVIDIA Persistence Daemon...
  Jul  3 10:37:14 Panter nvidia-persistenced: Socket closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file unlocked.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced
  Jul  3 10:37:14 Panter nvidia-persistenced: Shutdown (1085)
  Jul  3 10:37:14 Panter systemd[1]: nvidia-persistenced.service: Deactivated 
successfully.
  Jul  3 10:37:14 Panter systemd[1]: Stopped NVIDIA Persistence Daemon.
  Jul  3 10:37:19 Panter systemd[1]: Reloading.
  Jul  3 10:37:19 Panter systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Jul  3 10:37:19 Panter systemd[1]: Starting NVIDIA system hibernate actions...
  Jul  3 10:37:19 Panter hibernate: nvidia-hibernate.service
  Jul  3 10:37:19 Panter logger[9260]: <13>Jul  3 10:37:19 hibernate: 
nvidia-hibernate.service
  Jul  3 10:37:19 Panter kernel: [  424.892353] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 16
  Jul  3 10:37:19 Panter systemd[1]: nvidia-hibernate.service: Deactivated 
successfully.
  Jul  3 10:37:19 Panter systemd[1]: Finished NVIDIA system hibernate actions.
  Jul  3 10:37:20 Panter systemd[1]: Reloading.
  Jul  3 10:37:20 Panter systemd[1]: Starting NVIDIA system resume actions...
  Jul  3 10:37:20 Panter suspend: nvidia-resume.service
  Jul  3 10:37:20 Panter logger[9305]: <13>Jul  3 10:37:20 suspend: 
nvidia-resume.service
  Jul  3 10:37:20 Panter systemd[1]: nvidia-resume.service: Deactivated 
successfully.
  Jul  3 10:37:20 Panter systemd[1]: Finished NVIDIA system resume actions.
  Jul  3 10:37:20 Panter acpid: client 1346[0:0] has disconnected
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Supervising 7 threads of 3 
processes of 1 users.
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Successfully made thread 9312 of 
process 1530 owned by '1000' RT at priority 5.
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Supervising 8 threads of 3

[Kernel-packages] [Bug 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video output cuts out

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.113.01-0ubuntu0.22.04.3

---
nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.22.04.3) jammy; urgency=medium

  * debian/rules:
- Add override_dh_installsystemd.
- Pass in dh_installsystemd --no-restart-after-upgrade.

nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.22.04.2) jammy;
urgency=medium

  * debian/rules:
   - Pass in --no-stop-on-upgrade to dh_installsystemd.
 Prevent dh_installsystemd from stopping services (LP: #2025640).

 -- Alberto Milone   Fri, 29 Sep 2023
18:11:41 +

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy)
   Status: In Progress => Fix Released

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to
  535.54.03 video output cuts out

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  The current version nvidia-graphics-drivers-535 and nvidia-graphics-
  drivers-535-server, from Focal on, use the default values (from the
  debian compat 10) for dh_installsystemd which cause all the systemd
  services to be restarted on upgrade. This will cause the screen to go
  blank and never wake up.

  [Test Case]

  Install the nvidia-driver:
  sudo ubuntu-drivers install nvidia:535

  Try re-installing nvidia-kernel-common-535 and nvidia-compute-
  utils-535:

  sudo apt --reinstall nvidia-kernel-common-535 nvidia-compute-utils-535

  The screen will go black.

  [Where problems could occur]

  On servers with no display server in use, if, for some reason,
  restarting services such as nvidia-persistenced on upgrade is a
  desired feature, this will not take place any more.

  _
  
https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588

  https://forums.linuxmint.com/viewtopic.php?p=2344294

  timeline 10:36 - 10:39
  switch to TTY not helped-no video output, SSH not tested

  After emergency sync, reboot (by sysrq), is all fine.

  Jul  3 10:37:14 Panter nvidia-persistenced: Received signal 15
  Jul  3 10:37:14 Panter systemd[1]: Stopping NVIDIA Persistence Daemon...
  Jul  3 10:37:14 Panter nvidia-persistenced: Socket closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file unlocked.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced
  Jul  3 10:37:14 Panter nvidia-persistenced: Shutdown (1085)
  Jul  3 10:37:14 Panter systemd[1]: nvidia-persistenced.service: Deactivated 
successfully.
  Jul  3 10:37:14 Panter systemd[1]: Stopped NVIDIA Persistence Daemon.
  Jul  3 10:37:19 Panter systemd[1]: Reloading.
  Jul  3 10:37:19 Panter systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Jul  3 10:37:19 Panter systemd[1]: Starting NVIDIA system hibernate actions...
  Jul  3 10:37:19 Panter hibernate: nvidia-hibernate.service
  Jul  3 10:37:19 Panter logger[9260]: <13>Jul  3 10:37:19 hibernate: 
nvidia-hibernate.service
  Jul  3 10:37:19 Panter kernel: [  424.892353] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 16
  Jul  3 10:37:19 Panter systemd[1]: nvidia-hibernate.service: Deactivated 
successfully.
  Jul  3 10:37:19 Panter systemd[1]: Finished NVIDIA system hibernate actions.
  Jul  3 10:37:20 Panter systemd[1]: Reloading.
  Jul  3 10:37:20 Panter systemd[1]: Starting NVIDIA system resume actions...
  Jul  3 10:37:20 Panter suspend: nvidia-resume.service
  Jul  3 10:37:20 Panter logger[9305]: <13>Jul  3 10:37:20 suspend: 
nvidia-resume.service
  Jul  3 10:37:20 Panter systemd[1]: nvidia-resume.service: Deactivated 
successfully.
  Jul  3 10:37:20 Panter systemd[1]: Finished NVIDIA system resume actions.
  Jul  3 10:37:20 Panter acpid: client 1346[0:0] has disconnected
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Supervising 7 threads of 3 
processes of 1 users.
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Successfully made thread 9312 of 
process 1530 owned by

[Kernel-packages] [Bug 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video output cuts out

This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.104.12-0ubuntu0.22.04.2

---
nvidia-graphics-drivers-535-server (535.104.12-0ubuntu0.22.04.2) jammy; 
urgency=medium

  * debian/rules:
- Add override_dh_installsystemd.
- Pass in --no-stop-on-upgrade --no-restart-after-upgrade to
  dh_installsystemd (LP: #2025640).

 -- Alberto Milone   Fri, 29 Sep 2023
19:17:05 +

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to
  535.54.03 video output cuts out

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  The current version nvidia-graphics-drivers-535 and nvidia-graphics-
  drivers-535-server, from Focal on, use the default values (from the
  debian compat 10) for dh_installsystemd which cause all the systemd
  services to be restarted on upgrade. This will cause the screen to go
  blank and never wake up.

  [Test Case]

  Install the nvidia-driver:
  sudo ubuntu-drivers install nvidia:535

  Try re-installing nvidia-kernel-common-535 and nvidia-compute-
  utils-535:

  sudo apt --reinstall nvidia-kernel-common-535 nvidia-compute-utils-535

  The screen will go black.

  [Where problems could occur]

  On servers with no display server in use, if, for some reason,
  restarting services such as nvidia-persistenced on upgrade is a
  desired feature, this will not take place any more.

  _
  
https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588

  https://forums.linuxmint.com/viewtopic.php?p=2344294

  timeline 10:36 - 10:39
  switch to TTY not helped-no video output, SSH not tested

  After emergency sync, reboot (by sysrq), is all fine.

  Jul  3 10:37:14 Panter nvidia-persistenced: Received signal 15
  Jul  3 10:37:14 Panter systemd[1]: Stopping NVIDIA Persistence Daemon...
  Jul  3 10:37:14 Panter nvidia-persistenced: Socket closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file unlocked.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced
  Jul  3 10:37:14 Panter nvidia-persistenced: Shutdown (1085)
  Jul  3 10:37:14 Panter systemd[1]: nvidia-persistenced.service: Deactivated 
successfully.
  Jul  3 10:37:14 Panter systemd[1]: Stopped NVIDIA Persistence Daemon.
  Jul  3 10:37:19 Panter systemd[1]: Reloading.
  Jul  3 10:37:19 Panter systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Jul  3 10:37:19 Panter systemd[1]: Starting NVIDIA system hibernate actions...
  Jul  3 10:37:19 Panter hibernate: nvidia-hibernate.service
  Jul  3 10:37:19 Panter logger[9260]: <13>Jul  3 10:37:19 hibernate: 
nvidia-hibernate.service
  Jul  3 10:37:19 Panter kernel: [  424.892353] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 16
  Jul  3 10:37:19 Panter systemd[1]: nvidia-hibernate.service: Deactivated 
successfully.
  Jul  3 10:37:19 Panter systemd[1]: Finished NVIDIA system hibernate actions.
  Jul  3 10:37:20 Panter systemd[1]: Reloading.
  Jul  3 10:37:20 Panter systemd[1]: Starting NVIDIA system resume actions...
  Jul  3 10:37:20 Panter suspend: nvidia-resume.service
  Jul  3 10:37:20 Panter logger[9305]: <13>Jul  3 10:37:20 suspend: 
nvidia-resume.service
  Jul  3 10:37:20 Panter systemd[1]: nvidia-resume.service: Deactivated 
successfully.
  Jul  3 10:37:20 Panter systemd[1]: Finished NVIDIA system resume actions.
  Jul  3 10:37:20 Panter acpid: client 1346[0:0] has disconnected
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Supervising 7 threads of 3 
processes of 1 users.
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Successfully made thread 9312 of 
process 1530 owned by '1000' RT at priority 5.
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Supervising 8 threads of 3 
processes of 1 users.
  Jul  3 10:37:20 Panter acpid: client connected from 1346[0:0]
  Jul  3 10:37:20 Panter acpid: 1 client rule loaded
  Jul  3 10:37:20 Panter

[Kernel-packages] [Bug 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video output cuts out

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.113.01-0ubuntu0.23.04.3

---
nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.23.04.3) lunar; urgency=medium

  * debian/rules:
- Add override_dh_installsystemd.
- Pass in dh_installsystemd --no-restart-after-upgrade.

nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.23.04.2) lunar;
urgency=medium

  * debian/rules:
   - Pass in --no-stop-on-upgrade to dh_installsystemd.
 Prevent dh_installsystemd from stopping services (LP: #2025640).

 -- Alberto Milone   Fri, 29 Sep 2023
18:09:19 +

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar)
   Status: In Progress => Fix Released

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to
  535.54.03 video output cuts out

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  The current version nvidia-graphics-drivers-535 and nvidia-graphics-
  drivers-535-server, from Focal on, use the default values (from the
  debian compat 10) for dh_installsystemd which cause all the systemd
  services to be restarted on upgrade. This will cause the screen to go
  blank and never wake up.

  [Test Case]

  Install the nvidia-driver:
  sudo ubuntu-drivers install nvidia:535

  Try re-installing nvidia-kernel-common-535 and nvidia-compute-
  utils-535:

  sudo apt --reinstall nvidia-kernel-common-535 nvidia-compute-utils-535

  The screen will go black.

  [Where problems could occur]

  On servers with no display server in use, if, for some reason,
  restarting services such as nvidia-persistenced on upgrade is a
  desired feature, this will not take place any more.

  _
  
https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588

  https://forums.linuxmint.com/viewtopic.php?p=2344294

  timeline 10:36 - 10:39
  switch to TTY not helped-no video output, SSH not tested

  After emergency sync, reboot (by sysrq), is all fine.

  Jul  3 10:37:14 Panter nvidia-persistenced: Received signal 15
  Jul  3 10:37:14 Panter systemd[1]: Stopping NVIDIA Persistence Daemon...
  Jul  3 10:37:14 Panter nvidia-persistenced: Socket closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file unlocked.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced
  Jul  3 10:37:14 Panter nvidia-persistenced: Shutdown (1085)
  Jul  3 10:37:14 Panter systemd[1]: nvidia-persistenced.service: Deactivated 
successfully.
  Jul  3 10:37:14 Panter systemd[1]: Stopped NVIDIA Persistence Daemon.
  Jul  3 10:37:19 Panter systemd[1]: Reloading.
  Jul  3 10:37:19 Panter systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Jul  3 10:37:19 Panter systemd[1]: Starting NVIDIA system hibernate actions...
  Jul  3 10:37:19 Panter hibernate: nvidia-hibernate.service
  Jul  3 10:37:19 Panter logger[9260]: <13>Jul  3 10:37:19 hibernate: 
nvidia-hibernate.service
  Jul  3 10:37:19 Panter kernel: [  424.892353] snd_hda_codec_hdmi hdaudioC0D0: 
HDMI: invalid ELD data byte 16
  Jul  3 10:37:19 Panter systemd[1]: nvidia-hibernate.service: Deactivated 
successfully.
  Jul  3 10:37:19 Panter systemd[1]: Finished NVIDIA system hibernate actions.
  Jul  3 10:37:20 Panter systemd[1]: Reloading.
  Jul  3 10:37:20 Panter systemd[1]: Starting NVIDIA system resume actions...
  Jul  3 10:37:20 Panter suspend: nvidia-resume.service
  Jul  3 10:37:20 Panter logger[9305]: <13>Jul  3 10:37:20 suspend: 
nvidia-resume.service
  Jul  3 10:37:20 Panter systemd[1]: nvidia-resume.service: Deactivated 
successfully.
  Jul  3 10:37:20 Panter systemd[1]: Finished NVIDIA system resume actions.
  Jul  3 10:37:20 Panter acpid: client 1346[0:0] has disconnected
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Supervising 7 threads of 3 
processes of 1 users.
  Jul  3 10:37:20 Panter rtkit-daemon[1537]: Successfully made thread 9312 of 
process 1530 owned by

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

This change was made by a bot.

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

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

Title:
  amdgpu crashing intermittently under high load on Kubuntu 23.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While the system is under very high load (in this case downloading a
  game on Steam, maxing out all CPU cores) on my Framework AMD Ryzen
  7840U running Kubuntu 23.10 with linux-image-6.5.0-9-generic, amdgpu
  sometimes crashes and Kwin reports that it needed to restart graphic
  effects.

  Relevant part of dmesg seems to be:

  [ 1171.439662] amdgpu :c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:40 vmid:8 pasid:32799, for process  pid 0 thread  pid 0)
  [ 1171.439669] amdgpu :c1:00.0: amdgpu:   in page starting at address 
0x800100209000 from client 10
  [ 1171.439672] amdgpu :c1:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00840C50
  [ 1171.439674] amdgpu :c1:00.0: amdgpu:  Faulty UTCL2 client ID: CPG 
(0x6)
  [ 1171.439676] amdgpu :c1:00.0: amdgpu:  MORE_FAULTS: 0x0
  [ 1171.439678] amdgpu :c1:00.0: amdgpu:  WALKER_ERROR: 0x0
  [ 1171.439680] amdgpu :c1:00.0: amdgpu:  PERMISSION_FAULTS: 0x5
  [ 1171.439682] amdgpu :c1:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [ 1171.439683] amdgpu :c1:00.0: amdgpu:  RW: 0x1
  [ 1171.439730] [drm] ring gfx_32799.1.1 ib test pass
  [ 1171.439769] [drm] ring compute_32799.2.2 ib test pass
  [ 1171.440060] [drm] ring sdma_32799.3.3 ib test pass
  [ 1171.441628] amdgpu :c1:00.0: amdgpu: GPU reset(1) succeeded!

  I'm using linux-firmware 20230919.git3672ccab-0ubuntu2.1.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  itrue 12359 F wireplumber
   /dev/snd/controlC0:  itrue 12359 F wireplumber
   /dev/snd/seq:itrue 12353 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 19 15:30:33 2023
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-02-16 (610 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_teyrij@/vmlinuz-6.5.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_teyrij ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-19 (0 days ago)
  dmi.bios.date: 09/27/2023
  dmi.bios.release: 3.2
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.02
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANMDCPA7337200HR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.02:bd09/27/2023:br3.2:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANMDCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANMDCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

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


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

[Kernel-packages] [Bug 2036742] Re: amdgpu crash on Mantic

2023-10-19 Thread Timo Aaltonen

the firmware on mantic is zstd compressed, so mainline builds from the
past can't load the firmware..

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

Title:
  amdgpu crash on Mantic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Booting from USB the latest Mantic Desktop daily image (2023-09-20),
  just after the initial logs, nothing is displayed on screen. The
  system is still alive since _autoinstall_ works as intended. Once
  provisioned, the problem is still present.

  It seems related to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/2029396 .

  dmesg attached.

  [Test Case]

  Live boot Ubuntu Mantic Desktop canary (2023-09-19)

  [Where Problems Could Occur]

  Dell Optiplex 5090
  - Intel Core(TM) i7-11700
  - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f

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


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

[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances

2023-10-19 Thread John Cabaj

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

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

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

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

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

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

** Changed in: linux-gcp (Ubuntu Jammy)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

** Changed in: linux-gcp (Ubuntu Lunar)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

** Changed in: linux-gcp (Ubuntu Mantic)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

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

Title:
  No graphic desktop environment on Google GCP instances

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Jammy:
  In Progress
Status in linux-gcp source package in Lunar:
  In Progress
Status in linux-gcp source package in Mantic:
  In Progress

Bug description:
  [Impact]

  * Google reports not being able to display graphic desktop
  environment.

  [Fix]

  * CONFIG_SYSFB_SIMPLEFB was initially enabled in
  https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently
  disabled for amd64 in https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not
  reflected in the GCP kernel config.

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression. Simple config change that was not taken
  from generic.

  [Other Info]

  * SF #00366439

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


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

[Kernel-packages] [Bug 2039819] [NEW] amdgpu crashing intermittently under high load on Kubuntu 23.10

2023-10-19 Thread Isaac True

Public bug reported:

While the system is under very high load (in this case downloading a
game on Steam, maxing out all CPU cores) on my Framework AMD Ryzen 7840U
running Kubuntu 23.10 with linux-image-6.5.0-9-generic, amdgpu sometimes
crashes and Kwin reports that it needed to restart graphic effects.

Relevant part of dmesg seems to be:

[ 1171.439662] amdgpu :c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:40 vmid:8 pasid:32799, for process  pid 0 thread  pid 0)
[ 1171.439669] amdgpu :c1:00.0: amdgpu:   in page starting at address 
0x800100209000 from client 10
[ 1171.439672] amdgpu :c1:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00840C50
[ 1171.439674] amdgpu :c1:00.0: amdgpu:  Faulty UTCL2 client ID: CPG 
(0x6)
[ 1171.439676] amdgpu :c1:00.0: amdgpu:  MORE_FAULTS: 0x0
[ 1171.439678] amdgpu :c1:00.0: amdgpu:  WALKER_ERROR: 0x0
[ 1171.439680] amdgpu :c1:00.0: amdgpu:  PERMISSION_FAULTS: 0x5
[ 1171.439682] amdgpu :c1:00.0: amdgpu:  MAPPING_ERROR: 0x0
[ 1171.439683] amdgpu :c1:00.0: amdgpu:  RW: 0x1
[ 1171.439730] [drm] ring gfx_32799.1.1 ib test pass
[ 1171.439769] [drm] ring compute_32799.2.2 ib test pass
[ 1171.440060] [drm] ring sdma_32799.3.3 ib test pass
[ 1171.441628] amdgpu :c1:00.0: amdgpu: GPU reset(1) succeeded!

I'm using linux-firmware 20230919.git3672ccab-0ubuntu2.1.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  itrue 12359 F wireplumber
 /dev/snd/controlC0:  itrue 12359 F wireplumber
 /dev/snd/seq:itrue 12353 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Oct 19 15:30:33 2023
HibernationDevice: RESUME=none
InstallationDate: Installed on 2022-02-16 (610 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_teyrij@/vmlinuz-6.5.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_teyrij ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-9-generic N/A
 linux-backports-modules-6.5.0-9-generic  N/A
 linux-firmware   20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-19 (0 days ago)
dmi.bios.date: 09/27/2023
dmi.bios.release: 3.2
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.02
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANMDCPA7337200HR
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.02:bd09/27/2023:br3.2:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANMDCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANMDCP07
dmi.product.version: A7
dmi.sys.vendor: Framework

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


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

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

Title:
  amdgpu crashing intermittently under high load on Kubuntu 23.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While the system is under very high load (in this case downloading a
  game on Steam, maxing out all CPU cores) on my Framework AMD Ryzen
  7840U running Kubuntu 23.10 with linux-image-6.5.0-9-generic, amdgpu
  sometimes crashes and Kwin reports that it needed to restart graphic
  effects.

  Relevant part of dmesg seems to be:

  [ 1171.439662] amdgpu :c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:40 vmid:8 pasid:32799, for process  pid 0 thread  pid 0)
  [ 1171.439669] amdgpu :c1:00.0: amdgpu:   in page starting at address 
0x800100209000 from client 10
  [ 1171.439672] amdgpu :c1:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00840C50
  [ 1171.439674] amdgpu :c1:00.0: amdgpu:  Faulty UTCL2 client ID: CPG 
(0x6)
  [ 1171.439676] amdgpu :c1:00.0: amdgpu:  MORE_FAULTS: 0x0
  [ 1171.439678] amdgpu :c1:00.0: amdgpu:  WALKER_ERROR: 0x0
  [ 1171.439680] amdgpu :c1:00.0: amdgpu:  PERMISSION_FAULTS: 0x5
  [ 1171.439682] amdgpu :c1:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [ 1171.439683] amdgpu :c1:00.0: amdgpu:  RW: 0x1
  [ 1171.439730] [drm] ring gfx_32799.1.1 ib test pass
  [

[Kernel-packages] [Bug 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33

2023-10-19 Thread You-Sheng Yang

** Tags added: originate-from-2033369

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

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2024427

  [Impact]

  Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms
  will sometimes fail to wake from S3.

  [Fix]

  kernel patches:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  firmware patches:
  * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release
  * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release

  [Test Case]

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Little we know about the firmware fixes. However, while with these commits 
have
  been pulled via stable kernel fixes, the driver begins to request new firmware
  blobs of a different filename.

  [Other Info]

  The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and
  partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has 
to
  be fixed.

  For the firmware parts, they have been included in linux-firmware/mantic,
  leaving linux-firmware/lunar and linux-firmware/jammy to be fixed.

  == original bug report ==

  amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue.

  amdgpu:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  Navi31:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc
  Navi33:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac

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


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

[Kernel-packages] [Bug 2019222] Re: [IOTG][RPL] Integrated TSN controller (stmmac) driver enabling

This bug was fixed in the package linux-intel-iotg - 5.15.0-1043.49

---
linux-intel-iotg (5.15.0-1043.49) jammy; urgency=medium

  * jammy/linux-intel-iotg: 5.15.0-1043.49 -proposed tracker (LP:
#2038196)

  * CVE-2023-42755
- [Config] remove NET_CLS_RSVP and NET_CLS_RSVP6

  [ Ubuntu: 5.15.0-87.97 ]

  * jammy/linux: 5.15.0-87.97 -proposed tracker (LP: #2038209)
  * CVE-2023-4623
- net/sched: sch_hfsc: Ensure inner classes have fsc curve
  * CVE-2023-42755
- net/sched: Retire rsvp classifier
- [Config] remove NET_CLS_RSVP and NET_CLS_RSVP6
  * CVE-2023-34319
- xen/netback: Fix buffer overrun triggered by unusual packet
  * CVE-2023-4921
- net: sched: sch_qfq: Fix UAF in qfq_dequeue()
  * CVE-2023-42752
- igmp: limit igmpv3_newpack() packet size to IP_MAX_MTU
  * CVE-2023-4622
- af_unix: Fix null-ptr-deref in unix_stream_sendpage().
  * CVE-2023-4244
- netfilter: nft_set_rbtree: fix overlap expiration walk
- netfilter: nf_tables: don't skip expired elements during walk
- netfilter: nf_tables: adapt set backend to use GC transaction API
- netfilter: nft_set_hash: mark set element as dead when deleting from 
packet
  path
- netfilter: nf_tables: GC transaction API to avoid race with control plane
- netfilter: nf_tables: remove busy mark and gc batch API
- netfilter: nf_tables: don't fail inserts if duplicate has expired
- netfilter: nf_tables: fix kdoc warnings after gc rework
- netfilter: nf_tables: fix GC transaction races with netns and netlink 
event
  exit path
- netfilter: nf_tables: GC transaction race with netns dismantle
- netfilter: nf_tables: GC transaction race with abort path
- netfilter: nf_tables: use correct lock to protect gc_list
- netfilter: nf_tables: defer gc run if previous batch is still pending
- netfilter: nft_dynset: disallow object maps
- netfilter: nft_set_rbtree: skip sync GC for new elements in this 
transaction
  * CVE-2023-42756
- netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
  * CVE-2023-42753
- netfilter: ipset: add the missing IP_SET_HASH_WITH_NET0 macro for
  ip_set_hash_netportnet.c
  * CVE-2023-5197
- netfilter: nf_tables: skip bound chain in netns release path
- netfilter: nf_tables: disallow rule removal from chain binding
  * CVE-2023-4881
- netfilter: nftables: exthdr: fix 4-byte stack OOB write

 -- Philip Cox   Wed, 11 Oct 2023 12:24:56
-0400

** Changed in: linux-intel-iotg (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-34319

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42752

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42753

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42755

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42756

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4622

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4623

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4881

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4921

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5197

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

Title:
  [IOTG][RPL] Integrated TSN controller (stmmac) driver enabling

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

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/1996592

  -

  Description
  Enable Integrated TSN controller (stmmac) driver

  Hardware: Raptor Lake

  Target Release: 22.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.19-linux-221019T120731Z

  0001-igc-Disable-PTM-sequences-when-interface-goes-down.tsn
  0001-taprio-Add-support-for-frame-preemption-offload.tsn
  0002-xsk-add-txtime-field-in-xdp_desc-struct.tsn
  0003-tc-Add-index-of-FPE-QMASK.tsn
  0004-net-pcs-xpcs-enable-xpcs-reset-skipping.tsn
  0007-net-stmmac-add-FPE-preempt-setting-for-TxQ-preemptible.tsn
  0008-net-stmmac-support-recalculating-of-CBS-idle-slope-und.tsn
  0009-net-stmmac-Add-module-param-to-del-keep-est-hw-conf.tsn
  0011-net-stmmac-restructure-Rx-Tx-hardware-timestamping-fun.tsn
  0013-net-stmmac-introduce-AF_XDP-ZC-TX-HW-timestamps.tsn
  0018-net-stmmac-skip-runtime-handling-in-mdio-read-write.tsn
  0019-net-stmmac-Add-support-for-HW-accelerated-VLAN-strippi.tsn
  0025-net-phy-add-wrapper-function-for-setup-master-slave-se.tsn
  0027-net-stmmac-Adjust-mac_capabilities-for-Intel-mGbE-2.5G.tsn

[Kernel-packages] [Bug 2039809] Re: selftests:memory-hotplug:mem-on-off-test.sh: Timeout when offlining memory as a VM guest

As additional info, this is the ending of a previous case which
succeeded:

8875s 14:02:46 DEBUG| [stdout] # online->offline memory38
8965s 14:04:16 DEBUG| [stdout] # -> Success
8965s 14:04:16 DEBUG| [stdout] # online all hot-pluggable memory in 
offline state:
8965s 14:04:16 DEBUG| [stdout] # offline->online memory1
8965s 14:04:16 DEBUG| [stdout] # offline->online memory38
8965s 14:04:16 DEBUG| [stdout] # Test with memory notifier error 
injection
8966s 14:04:17 DEBUG| [stdout] ok 1 selftests: memory-hotplug: 
mem-on-off-test.sh

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

Title:
  selftests:memory-hotplug:mem-on-off-test.sh: Timeout when offlining
  memory as a VM guest

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This was observed first checking the ADT results for the 2023.10.02
  Lunar kernel (6.2.0-36.37) on amd64. But it seems also present for at
  least the Jammy (5.15) kernel. Also seen doing internal regression
  testing on OpenStack. However NOT reproducible on a local KVM VM. Also
  bare-metal appears ok.

  There were already issues before on Arm and public clouds (AWS, Azure)
  getting this test disabled there. Running as ADT (which is OpenStack
  like the internal RT tests) we saw multiple failed attempts before but
  the attempt which now results in the timeout did succeed before. So
  memory 38 could be offlined before and now somehow gets stuck. But not
  bad enough that the script cannot be terminated and the rest of the
  tests completing more or less normally.

  3143s 13:33:40 DEBUG| [stdout] TAP version 13
  3143s 13:33:40 DEBUG| [stdout] 1..1
  3143s 13:33:40 DEBUG| [stdout] # selftests: memory-hotplug: mem-on-off-test.sh
  3143s 13:33:40 DEBUG| [stdout] # Test scope: 2% hotplug memory
  3143s 13:33:40 DEBUG| [stdout] #   online all hot-pluggable memory in 
offline state:
  3143s 13:33:40 DEBUG| [stdout] #   SKIPPED - no hot-pluggable 
memory in offline state
  3144s 13:33:41 DEBUG| [stdout] #   offline 2% hot-pluggable memory in 
online state
  3144s 13:33:41 DEBUG| [stdout] #   trying to offline 2 out of 64 memory 
block(s):
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory0
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory1
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory10
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory11
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory12
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory13
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory14
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory15
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory16
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory17
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory18
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory19
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory2
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory20
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory21
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory22
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory23
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory3
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory32
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory33
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory34
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory35
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory36
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory37
  3144s 13:33:41 DEBUG| [stdout] # -> Failure
  3144s 13:33:41 DEBUG| [stdout] # online->offline memory38
  3743s 13:43:40 DEBUG| [stdout] #
  3743s 13:43:40 DEBUG| [stdout] not ok 1 selftests: memory-hotplug: 
mem-on-off-test.sh #

[Kernel-packages] [Bug 2039809] [NEW] selftests:memory-hotplug:mem-on-off-test.sh: Timeout when offlining memory as a VM guest

Public bug reported:

This was observed first checking the ADT results for the 2023.10.02
Lunar kernel (6.2.0-36.37) on amd64. But it seems also present for at
least the Jammy (5.15) kernel. Also seen doing internal regression
testing on OpenStack. However NOT reproducible on a local KVM VM. Also
bare-metal appears ok.

There were already issues before on Arm and public clouds (AWS, Azure)
getting this test disabled there. Running as ADT (which is OpenStack
like the internal RT tests) we saw multiple failed attempts before but
the attempt which now results in the timeout did succeed before. So
memory 38 could be offlined before and now somehow gets stuck. But not
bad enough that the script cannot be terminated and the rest of the
tests completing more or less normally.

3143s 13:33:40 DEBUG| [stdout] TAP version 13
3143s 13:33:40 DEBUG| [stdout] 1..1
3143s 13:33:40 DEBUG| [stdout] # selftests: memory-hotplug: mem-on-off-test.sh
3143s 13:33:40 DEBUG| [stdout] # Test scope: 2% hotplug memory
3143s 13:33:40 DEBUG| [stdout] # online all hot-pluggable memory in 
offline state:
3143s 13:33:40 DEBUG| [stdout] # SKIPPED - no hot-pluggable 
memory in offline state
3144s 13:33:41 DEBUG| [stdout] # offline 2% hot-pluggable memory in 
online state
3144s 13:33:41 DEBUG| [stdout] # trying to offline 2 out of 64 memory 
block(s):
3144s 13:33:41 DEBUG| [stdout] # online->offline memory0
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory1
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory10
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory11
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory12
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory13
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory14
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory15
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory16
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory17
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory18
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory19
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory2
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory20
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory21
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory22
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory23
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory3
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory32
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory33
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory34
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory35
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory36
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory37
3144s 13:33:41 DEBUG| [stdout] # -> Failure
3144s 13:33:41 DEBUG| [stdout] # online->offline memory38
3743s 13:43:40 DEBUG| [stdout] #
3743s 13:43:40 DEBUG| [stdout] not ok 1 selftests: memory-hotplug: 
mem-on-off-test.sh # TIMEOUT 600 seconds

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


** Tags: kernel-adt-failure

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

Title:
  selftests:memory-hotplug:mem-on-off-test.sh: Timeout when offlining
  memory as a VM guest

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This was observed first checking the ADT results for the 2023.10.02
  Lunar kernel (6.2.0-36.37) on amd64. But it seems also present for at
  least the Jammy (5.15) kernel. Also seen doing internal regression
  testing on OpenStack. However NOT reproducible on a local KVM VM. Also
  bare-metal appears ok.

  There were already issues before on Arm and public clouds (AWS, Azure)
  getting this test disabled there. Running as ADT (which is OpenStack
  like the internal RT tests) we saw multiple failed attempts before but
  the attempt

[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init

This bug was fixed in the package linux-gcp - 6.2.0-1017.19

---
linux-gcp (6.2.0-1017.19) lunar; urgency=medium

  * lunar/linux-gcp: 6.2.0-1017.19 -proposed tracker (LP: #2038064)

  * CVE-2023-42755
- [Config] remove NET_CLS_RSVP and NET_CLS_RSVP6

  * SEV_SNP failure to init (LP: #2037316)
- x86/sev-es: Allow copy_from_kernel_nofault in earlier boot
- x86/sev-es: Only set x86_virt_bits to correct value

  [ Ubuntu: 6.2.0-35.35 ]

  * lunar/linux: 6.2.0-35.35 -proposed tracker (LP: #2038229)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CVE-2023-4244
- netfilter: nf_tables: don't skip expired elements during walk
- netfilter: nf_tables: integrate pipapo into commit protocol
- netfilter: nft_set_rbtree: fix overlap expiration walk
- netfilter: nf_tables: adapt set backend to use GC transaction API
- netfilter: nft_set_hash: mark set element as dead when deleting from 
packet
  path
- netfilter: nf_tables: drop map element references from preparation phase
- netfilter: nf_tables: GC transaction API to avoid race with control plane
- netfilter: nf_tables: remove busy mark and gc batch API
- netfilter: nf_tables: don't fail inserts if duplicate has expired
- netfilter: nf_tables: fix kdoc warnings after gc rework
- netfilter: nf_tables: fix GC transaction races with netns and netlink 
event
  exit path
- netfilter: nf_tables: GC transaction race with netns dismantle
- netfilter: nf_tables: GC transaction race with abort path
- netfilter: nf_tables: use correct lock to protect gc_list
- netfilter: nf_tables: defer gc run if previous batch is still pending
- netfilter: nft_dynset: disallow object maps
- netfilter: nft_set_rbtree: skip sync GC for new elements in this 
transaction
  * CVE-2023-5197
- netfilter: nf_tables: skip bound chain in netns release path
- netfilter: nf_tables: disallow rule removal from chain binding
  * CVE-2023-4921
- net: sched: sch_qfq: Fix UAF in qfq_dequeue()
  * CVE-2023-4881
- netfilter: nftables: exthdr: fix 4-byte stack OOB write
  * CVE-2023-4623
- net/sched: sch_hfsc: Ensure inner classes have fsc curve
  * CVE-2023-4622
- af_unix: Fix null-ptr-deref in unix_stream_sendpage().
  * CVE-2023-42756
- netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
  * CVE-2023-42755
- net/sched: Retire rsvp classifier
- [Config] remove NET_CLS_RSVP and NET_CLS_RSVP6
  * CVE-2023-42753
- netfilter: ipset: add the missing IP_SET_HASH_WITH_NET0 macro for
  ip_set_hash_netportnet.c
  * CVE-2023-42752
- igmp: limit igmpv3_newpack() packet size to IP_MAX_MTU
- net: add SKB_HEAD_ALIGN() helper
- net: remove osize variable in __alloc_skb()
- net: factorize code in kmalloc_reserve()
- net: deal with integer overflows in kmalloc_reserve()
  * CVE-2023-34319
- xen/netback: Fix buffer overrun triggered by unusual packet

 -- John Cabaj   Thu, 05 Oct 2023 21:59:43
-0500

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-34319

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42752

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42753

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42755

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42756

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4622

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4623

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4881

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4921

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5197

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

Title:
  SEV_SNP failure to init

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

Bug description:
  [Impact]

  * Kernel fails to boot on SEV-SNP instances when compiled with GCC
  12.3.0

  [Fix]

  *
  https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested by Google

  [Where things could go wrong]

  * Patches relatively isolated and maintain similar checking
  functionality, just earlier in

[Kernel-packages] [Bug 2039802] [NEW] [IOTG][ADL-P] TGPIO enabling

2023-10-19 Thread Ionut Nechita

Public bug reported:

Hello Ubuntu Team,

I notice today using default iot and proposed iot kernel, missing TGPIO
and GPIO support.

IOT: 5.15.0-1040-intel-iotg
Proposed IOT: 5.15.0-1042-intel-iotg

With TGPIO support in kernel, i have this in dmesg:

dmesg | grep -i gpio
[1.954807] acpi MSFT0101:00: GPIO: looking up 0 in _CRS
[2.153305] i2c_designware i2c_designware.0: GPIO lookup for consumer scl
[2.153307] i2c_designware i2c_designware.0: using ACPI for GPIO lookup
[2.153309] acpi device:6b: GPIO: looking up scl-gpios
[2.153310] acpi device:6b: GPIO: looking up scl-gpio
[2.153312] i2c_designware i2c_designware.0: using lookup tables for GPIO 
lookup
[2.153313] i2c_designware i2c_designware.0: No GPIO consumer scl found
[2.189085] i2c_designware i2c_designware.1: GPIO lookup for consumer scl
[2.189087] i2c_designware i2c_designware.1: using ACPI for GPIO lookup
[2.189088] acpi device:6c: GPIO: looking up scl-gpios
[2.189090] acpi device:6c: GPIO: looking up scl-gpio
[2.189091] i2c_designware i2c_designware.1: using lookup tables for GPIO 
lookup
[2.189092] i2c_designware i2c_designware.1: No GPIO consumer scl found
[2.197541] mdio_bus fixed-0: GPIO lookup for consumer reset
[2.197542] mdio_bus fixed-0: using lookup tables for GPIO lookup
[2.197543] mdio_bus fixed-0: No GPIO consumer reset found
[2.209058] rtc_cmos rtc_cmos: GPIO lookup for consumer wp
[2.209059] rtc_cmos rtc_cmos: using lookup tables for GPIO lookup
[2.209060] rtc_cmos rtc_cmos: No GPIO consumer wp found
[2.626844] gpiochip_find_base: found new base at 664
[2.633323] gpio gpiochip0: (INTC1055:00): created GPIO range 0->25 ==> 
INTC1055:00 PIN 0->25
[2.633327] gpio gpiochip0: (INTC1055:00): created GPIO range 32->47 ==> 
INTC1055:00 PIN 26->41
[2.633328] gpio gpiochip0: (INTC1055:00): created GPIO range 64->88 ==> 
INTC1055:00 PIN 42->66
[2.633329] gpio gpiochip0: (INTC1055:00): created GPIO range 96->103 ==> 
INTC1055:00 PIN 67->74
[2.61] gpio gpiochip0: (INTC1055:00): created GPIO range 128->151 ==> 
INTC1055:00 PIN 75->98
[2.62] gpio gpiochip0: (INTC1055:00): created GPIO range 160->180 ==> 
INTC1055:00 PIN 99->119
[2.63] gpio gpiochip0: (INTC1055:00): created GPIO range 192->215 ==> 
INTC1055:00 PIN 120->143
[2.64] gpio gpiochip0: (INTC1055:00): created GPIO range 224->252 ==> 
INTC1055:00 PIN 144->172
[2.65] gpio gpiochip0: (INTC1055:00): created GPIO range 256->279 ==> 
INTC1055:00 PIN 173->196
[2.67] gpio gpiochip0: (INTC1055:00): created GPIO range 288->312 ==> 
INTC1055:00 PIN 197->221
[2.68] gpio gpiochip0: (INTC1055:00): created GPIO range 320->344 ==> 
INTC1055:00 PIN 228->252
[2.69] gpio gpiochip0: (INTC1055:00): created GPIO range 352->359 ==> 
INTC1055:00 PIN 262->269
[2.633397] gpio gpiochip0: (INTC1055:00): added GPIO chardev (254:0)
[2.633412] gpio gpiochip0: registered GPIOs 664 to 1023 on INTC1055:00
[4.144080] usb 3-10: GPIO lookup for consumer reset
[4.144084] usb 3-10: using ACPI for GPIO lookup
[4.144086] acpi device:5f: GPIO: looking up reset-gpios
[4.144088] acpi device:5f: GPIO: looking up reset-gpio
[4.144089] usb 3-10: using lookup tables for GPIO lookup
[4.144090] usb 3-10: No GPIO consumer reset found
[4.184939] usb 4-1: GPIO lookup for consumer privacy
[4.184941] usb 4-1: using ACPI for GPIO lookup
[4.184943] acpi device:62: GPIO: looking up privacy-gpios
[4.184945] acpi device:62: GPIO: looking up privacy-gpio
[4.184945] usb 4-1: using lookup tables for GPIO lookup
[4.184946] usb 4-1: No GPIO consumer privacy found
[4.186515] usb 4-1: GPIO lookup for consumer privacy
[4.186516] usb 4-1: using ACPI for GPIO lookup
[4.186517] acpi device:62: GPIO: looking up privacy-gpios
[4.186518] acpi device:62: GPIO: looking up privacy-gpio
[4.186519] usb 4-1: using lookup tables for GPIO lookup
[4.186519] usb 4-1: No GPIO consumer privacy found

But the support in the IOT kernel does not exist.

 # dmesg | grep -i gpio
 # uname -a
Linux 5.15.0-1042-intel-iotg #48-Ubuntu SMP Wed Sep 20 15:09:23 UTC 2023 x86_64 
x86_64 x86_64 GNU/Linux

Is it possible that in the next version we will have support for GPIO
and TGPIO?

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


** Tags: gpio

** Description changed:

  Hello Ubuntu Team,
  
  I notice today using default iot and proposed iot kernel, missing TGPIO
  and GPIO support.
  
  IOT: 5.15.0-1040-intel-iotg
  Proposed IOT: 5.15.0-1042-intel-iotg
- 
  
  With TGPIO support in kernel, i have this in dmesg:
  
  dmesg | grep -i gpio
  [1.954807] acpi MSFT0101:00: GPIO: looking up 0 in _CRS
  [2.153305] i2c_designware i2c_designware.0: GPIO lookup for consumer scl
  [2.153307] i2c_designware i2c_designware.0: using ACPI for GPIO lookup
  [2.153309] acpi device:6b: GPIO: looking up scl-gpios

[Kernel-packages] [Bug 2039783] Re: [UBUNTU 23.10] Opencryptoki package instalation not creating /run/opencryptoki directory

2023-10-19 Thread Frank Heimes

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

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

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

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

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

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

Title:
  [UBUNTU 23.10] Opencryptoki package instalation not creating
  /run/opencryptoki directory

Status in Ubuntu on IBM z Systems:
  New
Status in opencryptoki package in Ubuntu:
  New

Bug description:
  ---Problem Description  (by Grgo Mariani) ---
  Opencryptoki post-installation script fails due to a non-existing directory.
  Although the package is shown as installed the missing directory is critical 
for service running.
   
  Contact Information = grgo.mari...@ibm.com christian.r...@de.ibm.com 
   
  ---uname output---
  Linux SYSTEM 6.5.0-9-generic #9-Ubuntu SMP Fri Oct  6 19:43:35 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  Machine Type = Manufacturer: IBM Type: 3931  Model:   
 704  A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install the opencryptoki package and check if the service is running.

  root@SYSTEM:~# apt install opencryptoki
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
opencryptoki
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 228 kB of archives.
  After this operation, 834 kB of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports mantic/universe s390x opencryptoki 
s390x 3.21.0+dfsg-0ubuntu1 [228 kB]
  Fetched 228 kB in 0s (1,130 kB/s)
  Selecting previously unselected package opencryptoki.
  (Reading database ... 68397 files and directories currently installed.)
  Preparing to unpack .../opencryptoki_3.21.0+dfsg-0ubuntu1_s390x.deb ...
  Unpacking opencryptoki (3.21.0+dfsg-0ubuntu1) ...
  Setting up opencryptoki (3.21.0+dfsg-0ubuntu1) ...
  info: The group `pkcs11' already exists as a system group. Exiting.
  info: The system user `pkcsslotd' already exists. Exiting.

  info: Adding user `root' to group `pkcs11' ...
  chown: cannot access '/run/opencryptoki': No such file or directory
  dpkg: error processing package opencryptoki (--configure):
   installed opencryptoki package post-installation script subprocess returned 
error exit status 1
  Processing triggers for man-db (2.11.2-3) ...
  Errors were encountered while processing:
   opencryptoki
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@SYSTEM:~# systemctl status pkcsslotd

  
   
  Userspace tool common name: opencryptoki 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace rpm: opencryptoki v3.21.0

  Userspace tool obtained from project website:  na

  == Comment: #1 - Ingo Franzki - 2023-10-18 09:26:50 ==
  /run/opencryptoki should be created by the package install, but is also 
created by tmpfiles.d service after every boot, because /run is usually in 
tempfs, so its not persistent across boots. OCK installs a tempfiles.d config 
script (/usr/lib/tmpfiles.d/opencryptoki.conf), too.

  == Comment: #3 - Ingo Franzki - 2023-10-18 10:13:30 ==
  It also seems that Ubuntu's /usr/lib/tmpfiles.d/opencryptoki.conf file has 
incorrect (outdated?) contents.
  It must be ensured that the file as produced by building Opencryptoki (via 
'make install') is installed, and not something else/older.

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


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

[Kernel-packages] [Bug 2032378] Re: Devlink backport: fix race and lock issue

Mark the verification as already done using the new tag.

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

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

Title:
  Devlink backport: fix race and lock issue

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

Bug description:
  Summary:
  machine get stuck if try to switch to switchdev mode while toggling ns over 
BF kernel.
  This is due to missing lock refactor series devlink and driver from kernel 6.0

  How to test:
  1. Configure SRIOV
  2. Enable switchdev mode
  3. Devlink reload
  4. Add/Del network namespace

  Note: Need to run the test multiple times to reproduce the issue.

  How to fix:
  Need to backport a series of devlink patches into BlueField 5.15 kernel, from 
6.0 upstream kernel.
  Patches needed for 5.4/5.15 kernel:

  First series: 367dfa121205^..f0680ef0f949

  second series: 5502e8712c9b^..c90005b5f75c

  Also needed: 644a66c60f02

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


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

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

This change was made by a bot.

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

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

Title:
  package hostname-image-6.2.0-34-generic 6.2.0-34.34 failed to
  install/upgrade: installed hostname-image-6.2.0-34-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Happens affter update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Oct 17 11:22:32 2023
  Df:
   Filesystem1K-blocks Used Available Use% Mounted 
on
   /dev/mapper/ubuntu--vg-ubuntu--lv 241851868 40466920 189026704  18% /
  ErrorMessage: installed linux-image-6.2.0-34-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-08-10 (70 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: MSI MS-7883
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-34-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package hostname-image-6.2.0-34-generic 6.2.0-34.34 failed to 
install/upgrade: installed hostname-image-6.2.0-34-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Default string
  dmi.board.name: X99A GODLIKE GAMING (MS-7883)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd08/25/2016:br5.11:svnMSI:pnMS-7883:pvr1.0:rvnMSI:rnX99AGODLIKEGAMING(MS-7883):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7883
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Kernel-packages] [Bug 2039325] Re: mmc: sdhci-of-dwcmshc: Intermittent data error under stress test

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

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

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

Title:
  mmc: sdhci-of-dwcmshc: Intermittent data error under stress test

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110

  SRU Justification:

  [Impact]
  This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: 
__mmc_blk_ioctl_cmd: data error -110" error under stress test

  [Fix]
  The fix added a quirk for the BF3 sdhci driver to avoid such data error.

  [Test Case]
  1. Same functionality and testing as on BlueField-1/2.
  2. Install OS on NVME, and run the FIO test on EMMC.
  fio --name=mmcblk0_randrw_stress_round_1 \
--ioengine=libaio --direct=1  --time_based=1 \
--end_fsync=1 --ramp_time=5 --norandommap=1 \
--randrepeat=0 --group_reporting=1 --numjobs=8 \
--iodepth=128 --rw=randrw --overwrite=1 \
--runtime=3600 --bs=4K --filename=/dev/mmcblk0 &

  
  [Regression Potential]
  Same behavior from user perspective.

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


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

[Kernel-packages] [Bug 2039788] [NEW] package hostname-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed hostname-image-6.2.0-34-generic package post-installation script subproce

2023-10-19 Thread RNDLab

Public bug reported:

Happens affter update.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-34-generic 6.2.0-34.34
ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Oct 17 11:22:32 2023
Df:
 Filesystem1K-blocks Used Available Use% Mounted on
 /dev/mapper/ubuntu--vg-ubuntu--lv 241851868 40466920 189026704  18% /
ErrorMessage: installed linux-image-6.2.0-34-generic package post-installation 
script subprocess returned error exit status 1
InstallationDate: Installed on 2023-08-10 (70 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: MSI MS-7883
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-34-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package hostname-image-6.2.0-34-generic 6.2.0-34.34 failed to 
install/upgrade: installed hostname-image-6.2.0-34-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: X99A GODLIKE GAMING (MS-7883)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd08/25/2016:br5.11:svnMSI:pnMS-7883:pvr1.0:rvnMSI:rnX99AGODLIKEGAMING(MS-7883):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7883
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-package lunar

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

Title:
  package hostname-image-6.2.0-34-generic 6.2.0-34.34 failed to
  install/upgrade: installed hostname-image-6.2.0-34-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Happens affter update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Oct 17 11:22:32 2023
  Df:
   Filesystem1K-blocks Used Available Use% Mounted 
on
   /dev/mapper/ubuntu--vg-ubuntu--lv 241851868 40466920 189026704  18% /
  ErrorMessage: installed linux-image-6.2.0-34-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-08-10 (70 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: MSI MS-7883
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-34-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package hostname-image-6.2.0-34-generic 6.2.0-34.34 failed to 
install/upgrade: installed hostname-image-6.2.0-34-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Default string
  dmi.board.name: X99A GODLIKE GAMING (MS-7883)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd08/25/2016:br5.11:svnMSI:pnMS-7883:pvr1.0:rvnMSI:rnX99AGODLIKEGAMING(MS-7883):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7883
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Kernel-packages] [Bug 2039783] [NEW] [UBUNTU 23.10] Opencryptoki package instalation not creating /run/opencryptoki directory

2023-10-19 Thread bugproxy

Public bug reported:

---Problem Description  (by Grgo Mariani) ---
Opencryptoki post-installation script fails due to a non-existing directory.
Although the package is shown as installed the missing directory is critical 
for service running.
 
Contact Information = grgo.mari...@ibm.com christian.r...@de.ibm.com 
 
---uname output---
Linux SYSTEM 6.5.0-9-generic #9-Ubuntu SMP Fri Oct  6 19:43:35 UTC 2023 s390x 
s390x s390x GNU/Linux
 
Machine Type = Manufacturer: IBM Type: 3931  Model: 
   704  A01 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
Install the opencryptoki package and check if the service is running.

root@SYSTEM:~# apt install opencryptoki
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  opencryptoki
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 228 kB of archives.
After this operation, 834 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports mantic/universe s390x opencryptoki 
s390x 3.21.0+dfsg-0ubuntu1 [228 kB]
Fetched 228 kB in 0s (1,130 kB/s)
Selecting previously unselected package opencryptoki.
(Reading database ... 68397 files and directories currently installed.)
Preparing to unpack .../opencryptoki_3.21.0+dfsg-0ubuntu1_s390x.deb ...
Unpacking opencryptoki (3.21.0+dfsg-0ubuntu1) ...
Setting up opencryptoki (3.21.0+dfsg-0ubuntu1) ...
info: The group `pkcs11' already exists as a system group. Exiting.
info: The system user `pkcsslotd' already exists. Exiting.

info: Adding user `root' to group `pkcs11' ...
chown: cannot access '/run/opencryptoki': No such file or directory
dpkg: error processing package opencryptoki (--configure):
 installed opencryptoki package post-installation script subprocess returned 
error exit status 1
Processing triggers for man-db (2.11.2-3) ...
Errors were encountered while processing:
 opencryptoki
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@SYSTEM:~# systemctl status pkcsslotd


 
Userspace tool common name: opencryptoki 
 
The userspace tool has the following bit modes: 64bit 

Userspace rpm: opencryptoki v3.21.0

Userspace tool obtained from project website:  na

== Comment: #1 - Ingo Franzki - 2023-10-18 09:26:50 ==
/run/opencryptoki should be created by the package install, but is also created 
by tmpfiles.d service after every boot, because /run is usually in tempfs, so 
its not persistent across boots. OCK installs a tempfiles.d config script 
(/usr/lib/tmpfiles.d/opencryptoki.conf), too.

== Comment: #3 - Ingo Franzki - 2023-10-18 10:13:30 ==
It also seems that Ubuntu's /usr/lib/tmpfiles.d/opencryptoki.conf file has 
incorrect (outdated?) contents.
It must be ensured that the file as produced by building Opencryptoki (via 
'make install') is installed, and not something else/older.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-203873 severity-high 
targetmilestone-inin2310

** Tags added: architecture-s39064 bugnameltc-203873 severity-high
targetmilestone-inin2310

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

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

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

Title:
  [UBUNTU 23.10] Opencryptoki package instalation not creating
  /run/opencryptoki directory

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description  (by Grgo Mariani) ---
  Opencryptoki post-installation script fails due to a non-existing directory.
  Although the package is shown as installed the missing directory is critical 
for service running.
   
  Contact Information = grgo.mari...@ibm.com christian.r...@de.ibm.com 
   
  ---uname output---
  Linux SYSTEM 6.5.0-9-generic #9-Ubuntu SMP Fri Oct  6 19:43:35 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  Machine Type = Manufacturer: IBM Type: 3931  Model:   
 704  A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install the opencryptoki package and check if the service is running.

  root@SYSTEM:~# apt install opencryptoki
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
opencryptoki
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 228 kB of archives.
  After this operation, 834 kB of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports mantic/universe s390x opencryptoki 
s390x 3.21.0+dfsg-0ubuntu1 [228 kB]
  Fetched 228 kB in

[Kernel-packages] [Bug 2039782] [NEW] Stalls on CPUs/tasks on VisionFive 2 with external GPU

2023-10-19 Thread Heinrich Schuchardt

Public bug reported:

I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
board using
https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
server-riscv64.img.gz

I have connected an Nvidia GT710 graphics card to the NVMe connector and
see rcu_sched stalls. I have not  observed this behavior on StarFive
VisionFive 2 1.3B boards without an external GPU.

The U-Boot installed on SPI flash is
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

[   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
[   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 ncpus=4)
[   93.140996] Task dump for CPU 0:
[   93.149549] task:swapper/0   state:R  running task stack:0 pid:0 
ppid:0  flags:0x
[   93.164907] Call Trace:
[   93.172715] [] __schedule+0x27a/0x82e
[   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
[   93.200202] rcu: Possible timer handling issue on cpu=0 timer-softirq=890
[   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
[   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM 
is now expected behavior.
[   93.243573] rcu: RCU grace-period kthread stack dump:
[   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
[   93.268895] Call Trace:
[   93.277340] [] __schedule+0x27a/0x82e
[   93.288646] [] schedule+0x4e/0xde
[   93.299623] [] schedule_timeout+0x8c/0x15e
[   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
[   93.323170] [] rcu_gp_kthread+0x11a/0x142
[   93.334901] [] kthread+0xc4/0xe4
[   93.345833] [] ret_from_fork+0xe/0x20

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

** Attachment added: "boot.log.txt"
   
https://bugs.launchpad.net/bugs/2039782/+attachment/5711125/+files/boot.log.txt

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

Title:
  Stalls on CPUs/tasks on VisionFive 2 with external GPU

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
  board using
  https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
  server-riscv64.img.gz

  I have connected an Nvidia GT710 graphics card to the NVMe connector
  and see rcu_sched stalls. I have not  observed this behavior on
  StarFive VisionFive 2 1.3B boards without an external GPU.

  The U-Boot installed on SPI flash is
  
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

  [   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
  [   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
  [   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 
ncpus=4)
  [   93.140996] Task dump for CPU 0:
  [   93.149549] task:swapper/0   state:R  running task stack:0 
pid:0 ppid:0  flags:0x
  [   93.164907] Call Trace:
  [   93.172715] [] __schedule+0x27a/0x82e
  [   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
  [   93.200202] rcu: Possible timer handling issue on cpu=0 
timer-softirq=890
  [   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
  [   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, 
OOM is now expected behavior.
  [   93.243573] rcu: RCU grace-period kthread stack dump:
  [   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
  [   93.268895] Call Trace:
  [   93.277340] [] __schedule+0x27a/0x82e
  [   93.288646] [] schedule+0x4e/0xde
  [   93.299623] [] schedule_timeout+0x8c/0x15e
  [   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
  [   93.323170] [] rcu_gp_kthread+0x11a/0x142
  [   93.334901] [] kthread+0xc4/0xe4
  [   93.345833] [] ret_from_fork+0xe/0x20

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


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

[Kernel-packages] [Bug 2039783] [NEW] [UBUNTU 23.10] Opencryptoki package instalation not creating /run/opencryptoki directory

You have been subscribed to a public bug:

---Problem Description  (by Grgo Mariani) ---
Opencryptoki post-installation script fails due to a non-existing directory.
Although the package is shown as installed the missing directory is critical 
for service running.
 
Contact Information = grgo.mari...@ibm.com christian.r...@de.ibm.com 
 
---uname output---
Linux SYSTEM 6.5.0-9-generic #9-Ubuntu SMP Fri Oct  6 19:43:35 UTC 2023 s390x 
s390x s390x GNU/Linux
 
Machine Type = Manufacturer: IBM Type: 3931  Model: 
   704  A01 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
Install the opencryptoki package and check if the service is running.

root@SYSTEM:~# apt install opencryptoki
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  opencryptoki
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 228 kB of archives.
After this operation, 834 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports mantic/universe s390x opencryptoki 
s390x 3.21.0+dfsg-0ubuntu1 [228 kB]
Fetched 228 kB in 0s (1,130 kB/s)
Selecting previously unselected package opencryptoki.
(Reading database ... 68397 files and directories currently installed.)
Preparing to unpack .../opencryptoki_3.21.0+dfsg-0ubuntu1_s390x.deb ...
Unpacking opencryptoki (3.21.0+dfsg-0ubuntu1) ...
Setting up opencryptoki (3.21.0+dfsg-0ubuntu1) ...
info: The group `pkcs11' already exists as a system group. Exiting.
info: The system user `pkcsslotd' already exists. Exiting.

info: Adding user `root' to group `pkcs11' ...
chown: cannot access '/run/opencryptoki': No such file or directory
dpkg: error processing package opencryptoki (--configure):
 installed opencryptoki package post-installation script subprocess returned 
error exit status 1
Processing triggers for man-db (2.11.2-3) ...
Errors were encountered while processing:
 opencryptoki
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@SYSTEM:~# systemctl status pkcsslotd


 
Userspace tool common name: opencryptoki 
 
The userspace tool has the following bit modes: 64bit 

Userspace rpm: opencryptoki v3.21.0

Userspace tool obtained from project website:  na

== Comment: #1 - Ingo Franzki - 2023-10-18 09:26:50 ==
/run/opencryptoki should be created by the package install, but is also created 
by tmpfiles.d service after every boot, because /run is usually in tempfs, so 
its not persistent across boots. OCK installs a tempfiles.d config script 
(/usr/lib/tmpfiles.d/opencryptoki.conf), too.

== Comment: #3 - Ingo Franzki - 2023-10-18 10:13:30 ==
It also seems that Ubuntu's /usr/lib/tmpfiles.d/opencryptoki.conf file has 
incorrect (outdated?) contents.
It must be ensured that the file as produced by building Opencryptoki (via 
'make install') is installed, and not something else/older.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-203873 severity-high 
targetmilestone-inin2310
-- 
[UBUNTU 23.10] Opencryptoki package instalation not creating /run/opencryptoki 
directory
https://bugs.launchpad.net/bugs/2039783
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2039601] Re: [ kernel 6.5 regression ] nvme not working on some laptops

2023-10-19 Thread Luis Alberto Pabón

** Summary changed:

- [ kernel regression ] nvme not working on some laptops
+ [ kernel 6.5 regression ] nvme not working on some laptops

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

Title:
  [ kernel 6.5 regression ] nvme not working on some laptops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the update to Ubuntu 23.10 my nvme drive ceased to function.
  Booting the old 6.2 kernel from 23.04 works, but not the newer
  6.5.0-9.

  This is a kernel bug that's been fixed in 6.5.6, any chance it could
  possibly be backported?

  More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luis   3036 F wireplumber
   /dev/snd/controlC1:  luis   3036 F wireplumber
   /dev/snd/seq:luis   3029 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:05:29 2023
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2038832] Re: Jammy update: v6.1.56 upstream stable release

2023-10-19 Thread Atlas Yu

** Tags added: oem-priority originate-from-2039774 sutton

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

Title:
  Jammy update: v6.1.56 upstream stable release

Status in OEM Priority Project:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  
  SRU Justification

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

 v6.1.56 upstream stable release
 from git://git.kernel.org/

  
  Linux 6.1.56
  ASoC: amd: yc: Fix a non-functional mic on Lenovo 82TL
  mm, memcg: reconsider kmem.limit_in_bytes deprecation
  memcg: drop kmem.limit_in_bytes
  drm/meson: fix memory leak on ->hpd_notify callback
  drm/amdkfd: Use gpu_offset for user queue's wptr
  fs: binfmt_elf_efpic: fix personality for ELF-FDPIC
  power: supply: ab8500: Set typing and props
  power: supply: rk817: Add missing module alias
  drm/i915/gt: Fix reservation address in ggtt_reserve_guc_top
  ata: libata-sata: increase PMP SRST timeout to 10s
  ata: libata-core: Do not register PM operations for SAS ports
  ata: libata-core: Fix port and device removal
  ata: libata-core: Fix ata_port_request_pm() locking
  fs/smb/client: Reset password pointer to NULL
  net: thunderbolt: Fix TCPv6 GSO checksum calculation
  bpf: Fix BTF_ID symbol generation collision in tools/
  bpf: Fix BTF_ID symbol generation collision
  bpf: Add override check to kprobe multi link attach
  media: uvcvideo: Fix OOB read
  btrfs: properly report 0 avail for very full file systems
  ring-buffer: Update "shortest_full" in polling
  mm: memcontrol: fix GFP_NOFS recursion in memory.high enforcement
  mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()
  mm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions()
  arm64: defconfig: remove CONFIG_COMMON_CLK_NPCM8XX=y
  drm/tests: Fix incorrect argument in drm_test_mm_insert_range
  timers: Tag (hr)timer softirq as hotplug safe
  Revert "SUNRPC dont update timeout value on connection reset"
  netfilter: nf_tables: fix kdoc warnings after gc rework
  sched/rt: Fix live lock between select_fallback_rq() and RT push
  kernel/sched: Modify initial boot task idle setup
  ASoC: amd: yc: Fix non-functional mic on Lenovo 82QF and 82UG
  i2c: i801: unregister tco_pdev in i801_probe() error path
  io_uring/fs: remove sqe->rw_flags checking from LINKAT
  ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES
  ata: libata-scsi: link ata port and scsi device
  LoongArch: numa: Fix high_memory calculation
  LoongArch: Define relocation types for ABI v2.10
  ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q
  netfilter: nf_tables: disallow rule removal from chain binding
  nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
  serial: 8250_port: Check IRQ data before use
  Revert "tty: n_gsm: fix UAF in gsm_cleanup_mux"
  misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to 
probe
  mptcp: fix bogus receive window shrinkage with multiple subflows
  KVM: x86/mmu: Do not filter address spaces in 
for_each_tdp_mmu_root_yield_safe()
  KVM: x86/mmu: Open code leaf invalidation from mmu_notifier
  KVM: SVM: Fix TSC_AUX virtualization setup
  KVM: SVM: INTERCEPT_RDTSCP is never intercepted anyway
  x86/srso: Add SRSO mitigation for Hygon processors
  x86/sgx: Resolves SECS reclaim vs. page fault for EAUG race
  iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range
  smack: Retrieve transmuting information in smack_inode_getsecurity()
  smack: Record transmuting in smk_transmuted
  nvme-pci: always return an ERR_PTR from nvme_pci_alloc_dev
  scsi: qla2xxx: Fix NULL pointer dereference in target mode
  wifi: ath11k: Don't drop tx_status when peer cannot be found
  nvme-pci: do not set the NUMA node of device if it has none
  nvme-pci: factor out a nvme_pci_alloc_dev helper
  nvme-pci: factor the iod mempool creation into a helper
  perf build: Define YYNOMEM as YYNOABORT for bison < 3.81
  fbdev/sh7760fb: Depend on FB=y
  LoongArch: Set all reserved memblocks on Node#0 at initialization
  tsnep: Fix NAPI polling with budget 0
  tsnep: Fix NAPI scheduling
  net: hsr: Add __packed to struct hsr_sup_tlv.
  ncsi: Propagate carrier gain/loss events to the NCSI controller
  powerpc/watchpoints: Annotate atomic context in more places
  powerpc/watchpoint: Disable pagefaults when getting

[Kernel-packages] [Bug 2039405] Re: Unable to power off the system with MTL CPU

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

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

Title:
  Unable to power off the system with MTL CPU

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

Bug description:
  [Impact]
  The commit introduced from v6.4 leads to the power off issue
  45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible

  [Fix]
  The problematic commit has been reverted since v6.6
  fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible"

  [Test case]
  1. Power up the MTL system
  2. Power off the system and make sure it shutdown correctly

  [Where problems could occur]
  From the origin commit log, revert the commit may have a protential security 
issue.

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


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

[Kernel-packages] [Bug 2039440] Re: Focal update: v5.4.255 upstream stable release

2023-10-19 Thread Roxana Nicolescu

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

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

Title:
  Focal update: v5.4.255 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mmc: sdhci_f_sdh30: convert to devm_platform_ioremap_resource
  mmc: sdhci-f-sdh30: Replace with sdhci_pltfm
  selftests: forwarding: tc_flower: Relax success criterion
  macsec: Fix traffic counters/statistics
  macsec: use DEV_STATS_INC()
  drm/radeon: Fix integer overflow in radeon_cs_parser_init
  ALSA: emu10k1: roll up loops in DSP setup code for Audigy
  quota: Properly disable quotas when add_dquot_ref() fails
  quota: fix warning in dqgrab()
  HID: add quirk for 03f0:464a HP Elite Presenter Mouse
  ovl: check type and offset of struct vfsmount in ovl_entry
  udf: Fix uninitialized array access for some pathnames
  fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev
  MIPS: dec: prom: Address -Warray-bounds warning
  FS: JFS: Fix null-ptr-deref Read in txBegin
  FS: JFS: Check for read-only mounted filesystem in txBegin
  media: v4l2-mem2mem: add lock to protect parameter num_rdy
  media: platform: mediatek: vpu: fix NULL ptr dereference
  usb: chipidea: imx: don't request QoS for imx8ulp
  gfs2: Fix possible data races in gfs2_show_options()
  pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()
  Bluetooth: L2CAP: Fix use-after-free
  drm/amdgpu: Fix potential fence use-after-free v2
  ALSA: hda/realtek: Add quirks for Unis H3C Desktop B760 & Q760
  ALSA: hda: fix a possible null-pointer dereference due to data race in 
snd_hdac_regmap_sync()
  powerpc/kasan: Disable KCOV in KASAN code
  IMA: allow/fix UML builds
  iio: add addac subdirectory
  iio: adc: stx104: Utilize iomap interface
  iio: adc: stx104: Implement and utilize register structures
  iio: stx104: Move to addac subdirectory
  iio: addac: stx104: Fix race condition for stx104_write_raw()
  iio: addac: stx104: Fix race condition when converting analog-to-digital
  iommu/amd: Fix "Guest Virtual APIC Table Root Pointer" configuration in IRTE
  PM-runtime: add tracepoints for usage_count changes
  PM: runtime: Add pm_runtime_get_if_active()
  ALSA: hda: Fix unhandled register update during auto-suspend period
  irqchip/mips-gic: Get rid of the reliance on irq_cpu_online()
  irqchip/mips-gic: Use raw spinlock for gic_lock
  interconnect: Move internal structs into a separate file
  interconnect: Add helpers for enabling/disabling a path
  usb: dwc3: qcom: Add helper functions to enable,disable wake irqs
  USB: dwc3: qcom: fix NULL-deref on suspend
  mmc: bcm2835: fix deferred probing
  mmc: sunxi: fix deferred probing
  leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename
  tracing/probes: Have process_fetch_insn() take a void * instead of pt_regs
  tracing/probes: Fix to update dynamic data counter if fetcharg uses it
  net/ncsi: Fix gma flag setting after response
  nfsd4: kill warnings on testing stateids with mismatched clientids
  nfsd: Remove incorrect check in nfsd4_validate_stateid
  virtio-mmio: convert to devm_platform_ioremap_resource
  virtio-mmio: Use to_virtio_mmio_device() to simply code
  virtio-mmio: don't break lifecycle of vm_dev
  i2c: bcm-iproc: Fix bcm_iproc_i2c_isr deadlock issue
  fbdev: mmp: fix value check in mmphw_probe()
  powerpc/rtas_flash: allow user copy to flash block cache objects
  tty: serial: fsl_lpuart: Clear the error flags by writing 1 for lpuart32 
platforms
  btrfs: fix BUG_ON condition in btrfs_cancel_balance
  net: xfrm: Fix xfrm_address_filter OOB read
  net: af_key: fix sadb_x_filter validation
  xfrm: interface: rename xfrm_interface.c to xfrm_interface_core.c
  xfrm: fix slab-use-after-free in decode_session6
  ip6_vti: fix slab-use-after-free in decode_session6
  ip_vti: fix potential slab-use-after-free in decode_session6
  selftests: mirror_gre_changes: Tighten up the TTL test match
  ipvs: fix racy memcpy in proc_do_sync_threshold
  netfilter: nft_dynset: disallow object maps
  team: Fix incorrect deletion of ETH_P_8021AD protocol vid from slaves
  i40e: fix misleading debug logs
  net: dsa: mv88e6xxx: Wait for EEPROM done before HW reset
  sock: Fix misuse of sk_under_memory_pressure()

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids