[Kernel-packages] [Bug 2015956] Re: selftest: fib_tests: Always cleanup before exit

[Po-Hsu Lin]

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

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

Title:
   selftest: fib_tests: Always cleanup before exit

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Copied from the commit message:
  Usage of `set -e` before executing a command causes immediate exit
  on failure, without cleanup up the resources allocated at setup.
  This can affect the next tests that use the same resources,
  leading to a chain of failures.

  A simple fix is to always call cleanup function when the script exists.
  This approach is already used by other existing tests.

  [Fix]
  * b60417a9f2 selftest: fib_tests: Always cleanup before exit

  This patch can be cherry-picked into affected kernels.

  [Test]
  Run the patched fib_tests.sh on KVM kernels, which is expected to fail 
  due to bug 2007458.
  Check with `ip netns`, the ns1 added during setup() should be removed.

  [Where problems could occur]
  Test robustness improvement, this should not break things.

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


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

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[raj]

@BlindB0 (blindb0)

HI ,
 I Installed fresh Ubuntu  and again camera not working I followed#67
your steps as previous but this time showing me 

warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 
12.2.0
  You are using:   gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0
  CC [M]  /home/raj/uvc/uvc_driver.o
  CC [M]  /home/raj/uvc/uvc_queue.o
  CC [M]  /home/raj/uvc/uvc_v4l2.o
  CC [M]  /home/raj/uvc/uvc_video.o
  CC [M]  /home/raj/uvc/uvc_ctrl.o
  CC [M]  /home/raj/uvc/uvc_status.o
  CC [M]  /home/raj/uvc/uvc_isight.o
  CC [M]  /home/raj/uvc/uvc_debugfs.o
  CC [M]  /home/raj/uvc/uvc_metadata.o
  CC [M]  /home/raj/uvc/uvc_entity.o
  LD [M]  /home/raj/uvc/uvcvideo.o
  MODPOST /home/raj/uvc/Module.symvers
  CC [M]  /home/raj/uvc/uvcvideo.mod.o
  LD [M]  /home/raj/uvc/uvcvideo.ko
  BTF [M] /home/raj/uvc/uvcvideo.ko
Skipping BTF generation for /home/raj/uvc/uvcvideo.ko due to unavailability of 
vmlinux
make[1]: Leaving directory '/usr/src/linux-headers-6.2.0-20-generic'

Then when I run 
sudo rmmod uvcvideo
error is > mmod: ERROR: Module uvcvideo is not currently loaded


Earlier it was working for 4033 Quanta cameras but this time not can you 
provide solutions as before you provided 

Thanks

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy 

[Kernel-packages] [Bug 1976473] Re: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop

[Álvaro Reguly]

Adding acpi_backlight=nvidia_wmi_ec worked for me, on 23.04 using
proprietary nvidia drivers.

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

Title:
  [Dell G15 5515] Unable to change screen brightness in ubuntu desktop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics.

  In /sys/class/backlight directory, there are two directories
  amdgpu_bl0 and nvidia_wmi_ec_backlight.

  When I change the screen brightness via slider then it changes the
  brightness value of nvidia_wmi_ec_backlight but it doesn't work. When
  I manually changed the value of amdgpu_bl0 brightness file then my
  screen brightness changed.

  My BIOS is updated to the latest version and I have NVIDIA Driver with 
version 510.73.05.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  yorozuya   2677 F pulseaudio
   /dev/snd/controlC0:  yorozuya   2677 F pulseaudio
   /dev/snd/controlC1:  yorozuya   2677 F pulseaudio
   /dev/snd/controlC3:  yorozuya   2677 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Dell G15 5515
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2022
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.asset.tag: not specified
  dmi.board.name: 0TGD6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.6.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5515
  dmi.product.sku: 0A6E
  dmi.product.version: 1.6.0
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2023446] Re: Excessive Power drain in sleep mode on XPS 9315

[Kai-Heng Feng]

Can you please boot with kernel parameter
"intel_pmc_core.warn_on_s0ix_failures=1", suspend overnight, resume the
system and attach dmesg here? Thanks!

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

Title:
  Excessive Power drain in sleep mode on XPS 9315

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a new Dell XPS 9315, with Ubuntu 22.04 installed (from vanilla
  image, downloaded from the Ubuntu site). The machine was sold with an
  OEM 20.04 image which I am no longer using.

  From a full charge, I close the lid and the machine enters sleep. Over
  the course of 8Hrs, the battery drops from 100% to 80%.

  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17

  See attached log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noutram2273 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-06-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Dell Inc. XPS 9315
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-43-generic N/A
   linux-backports-modules-5.19.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  Tags:  jammy
  Uname: Linux 5.19.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 04/12/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 02GGG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd04/12/2023:br1.11:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3

[AceLan Kao]

** Description changed:

  [Impact]
  During the S3 stress test, the system sometimes hangs when resuming. This is 
due to the SCSI rescan task being unable to acquire the mutex lock during the 
resumption from S3. The mutex lock has already been acquired by EH and is 
waiting for the device to be ready for a rescan. Unfortunately, the mutex lock 
is never released by either party, leading to a deadlock.
  
  [Fix]
  Kaiheng submitted a patch to fix this issue which defers the rescan if the 
disk is still suspended so the resume process of the disk device can proceed.
  
https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/
  
  Since the patch has not been accepted by the upstream yet, so submit it
  to the OEM kernel for now.
  
+ The similiar patch has been included in v6.4-rc7
+ 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume
+ 
  [Test]
  Verified on the machines by me and ODM.
  
  [Where problems could occur]
  It only defers the rescan task, and should not have any impact to current 
systems.

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

Title:
  A deadlock issue in scsi rescan task while resuming from S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  During the S3 stress test, the system sometimes hangs when resuming. This is 
due to the SCSI rescan task being unable to acquire the mutex lock during the 
resumption from S3. The mutex lock has already been acquired by EH and is 
waiting for the device to be ready for a rescan. Unfortunately, the mutex lock 
is never released by either party, leading to a deadlock.

  [Fix]
  Kaiheng submitted a patch to fix this issue which defers the rescan if the 
disk is still suspended so the resume process of the disk device can proceed.
  
https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/

  Since the patch has not been accepted by the upstream yet, so submit
  it to the OEM kernel for now.

  The similiar patch has been included in v6.4-rc7
  6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume

  [Test]
  Verified on the machines by me and ODM.

  [Where problems could occur]
  It only defers the rescan task, and should not have any impact to current 
systems.

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


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

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

[dog soup]

This doesn't seem to have been mentioned yet, but so far it's got sound
working for me (the SSDT patch answer):
https://askubuntu.com/questions/1467417/no-sound-from-speakers-on-asus-
zenbook-ux3402za-q409za

Direct link to patch:
https://github.com/thor2002ro/asus_zenbook_ux3402za/tree/main/Sound

ASUS Zenbook UX3402ZA_Q409ZA 1.0
Ubuntu 22.04.2 LTS x86_64 (dual boot w/ Windows 11)

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

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

Status in Linux Firmware:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

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

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

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

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

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


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

[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage

[otiskujawa]

Remote Debian server on 5.10.0-23-amd64 x86_64 kernel after running 
memory-hungry job.
Swap enabled, 16GB of ram, Intel Xeon W3550.
System hangs without any warning.

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

Title:
  When DMA is disabled system freeze on high memory usage

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

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  all i know is what is in the summary above
  BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dorna  1303 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 26'
 Mixer name : 'IDT 92HD71B7X'
 Components : 'HDA:111d76b2,102802aa,00100302'
 Controls  : 38
 Simple ctrls  : 16
  Date: Mon Jun 19 10:40:21 2023
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: release_task+0x19/0x460 SS:ESP: 0068:f3e1fe00
  Failure: oops
  HibernationDevice: RESUME=UUID=354b21c5-900f-474a-ab37-d22df3793d83
  InstallationDate: Installed on 2017-10-20 (2067 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: Dell Inc. Inspiron 1545
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=056991b6-6d2d-447c-8407-d498b760c2ef ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd06/03/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2024395] Re: BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

Status in linux package in Ubuntu:
  New

Bug description:
  all i know is what is in the summary above
  BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dorna  1303 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 26'
 Mixer name : 'IDT 92HD71B7X'
 Components : 'HDA:111d76b2,102802aa,00100302'
 Controls  : 38
 Simple ctrls  : 16
  Date: Mon Jun 19 10:40:21 2023
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: release_task+0x19/0x460 SS:ESP: 0068:f3e1fe00
  Failure: oops
  HibernationDevice: RESUME=UUID=354b21c5-900f-474a-ab37-d22df3793d83
  InstallationDate: Installed on 2017-10-20 (2067 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: Dell Inc. Inspiron 1545
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=056991b6-6d2d-447c-8407-d498b760c2ef ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd06/03/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2024395] [NEW] BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

[Dorna Kightlinger]

Public bug reported:

all i know is what is in the summary above
BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dorna  1303 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 26'
   Mixer name   : 'IDT 92HD71B7X'
   Components   : 'HDA:111d76b2,102802aa,00100302'
   Controls  : 38
   Simple ctrls  : 16
Date: Mon Jun 19 10:40:21 2023
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: release_task+0x19/0x460 SS:ESP: 0068:f3e1fe00
Failure: oops
HibernationDevice: RESUME=UUID=354b21c5-900f-474a-ab37-d22df3793d83
InstallationDate: Installed on 2017-10-20 (2067 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
MachineType: Dell Inc. Inspiron 1545
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=056991b6-6d2d-447c-8407-d498b760c2ef ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd06/03/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-kerneloops artful i386 kernel-oops

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

Title:
  BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

Status in linux package in Ubuntu:
  New

Bug description:
  all i know is what is in the summary above
  BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dorna  1303 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 26'
 Mixer name : 'IDT 92HD71B7X'
 Components : 'HDA:111d76b2,102802aa,00100302'
 Controls  : 38
 Simple ctrls  : 16
  Date: Mon Jun 19 10:40:21 2023
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: release_task+0x19/0x460 SS:ESP: 0068:f3e1fe00
  Failure: oops
  HibernationDevice: RESUME=UUID=354b21c5-900f-474a-ab37-d22df3793d83
  InstallationDate: Installed on 2017-10-20 (2067 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: Dell Inc. Inspiron 1545
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=056991b6-6d2d-447c-8407-d498b760c2ef ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd06/03/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest

[Fabio Augusto Miranda Martins]

Verified a Focal guest as follows:

1. Reproduced the problem with kernel 5.4.0-152-generic:

https://pastebin.ubuntu.com/p/Cgj6j4Prbc/

2. As a workaround removed:

  
0x0003
  
  
3. Installed kernel from -proposed:

root@ubuntu:~# apt-cache policy linux-image-virtual linux-virtual
linux-image-virtual:
  Installed: 5.4.0.154.151
  Candidate: 5.4.0.154.151
  Version table:
 *** 5.4.0.154.151 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 5.4.0.152.149 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 5.4.0.26.32 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
linux-virtual:
  Installed: 5.4.0.154.151
  Candidate: 5.4.0.154.151
  Version table:
 *** 5.4.0.154.151 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 5.4.0.152.149 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 5.4.0.26.32 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages


4. Added back:

  
0x0003
  
  

5. Instance booted fine:

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.4.0-154-generic #171-Ubuntu SMP Fri Jun 16 16:29:04 UTC 2023 x86_
64 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ sudo dmesg | grep -i sev
[0.172491] AMD Secure Encrypted Virtualization (SEV) active
[5.318658] SVM: KVM is unsupported when running as an SEV guest

6. Full dmesg: https://paste.ubuntu.com/p/dP4Zp8pKfm/

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

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

Title:
  Encountering an issue with memcpy_fromio causing failed boot of SEV-
  enabled guest

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

Bug description:
  [Impact]
  When launching a SEV-enabled guest, the guest kernel panics with the 
following call trace,
  indicating a critical error in the system.

  ==
  [1.090638] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers
  [1.092105] Linux agpgart interface v0.103
  [1.092716] BUG: unable to handle page fault for address: 9b820003d068
  [1.093445] #PF: supervisor read access in kernel mode
  [1.093966] #PF: error_code(0x) - not-present page
  [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 
8001001da067 PTE 8000fed40173
  [1.094629] Oops:  [#1] SMP NOPTI
  [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic 
#49-Ubuntu
  [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 
02/06/2015
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 
0002
  [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 
9b820001ba90
  [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 
0f80
  [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 
8cc7068eca48
  [1.094629] R13: 8cc700a64288 R14:  R15: 
fed40080
  [1.094629] FS:  () GS:8cc77bd0() 
knlGS:
  [1.094629] CS:  0010 DS:  ES:  CR0: 80050033
  [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 
00350ee0
  [1.094629] Call Trace:
  [1.094629]  
  [1.094629]  crb_map_io+0x315/0x870
  [1.094629]  ? radix_tree_iter_tag_clear+0x12/0x20
  [1.094629]  ? _raw_spin_unlock_irqrestore+0xe/0x30
  [1.094629]  crb_acpi_add+0xc2/0x140
  [1.094629]  acpi_device_probe+0x4c/0x170
  [1.094629]  really_probe+0x222/0x420
  [1.094629]  __driver_probe_device+0x119/0x190
  [1.094629]  driver_probe_device+0x23/0xc0
  [1.094629]  __driver_attach+0xbd/0x1e0
  [1.094629]  ? __device_attach_driver+0x120/0x120
  [1.094629]  bus_for_each_dev+0x7e/0xd0
  [1.094629]  driver_attach+0x1e/0x30
  [1.094629]  bus_add_driver+0x139/0x200
  [1.094629]  driver_register+0x95/0x100
  [1.094629]  ? init_tis+0xfd/0xfd
  [1.094629]  acpi_bus_register_driver+0x39/0x50

[Kernel-packages] [Bug 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest

[Fabio Augusto Miranda Martins]

I've verified a Jammy guest as follows:

1. Reproduced the problem with kernel 5.15.0-75-generic:

https://pastebin.ubuntu.com/p/844W5SzjR8/


2. As a workaround removed:

  
0x0003
  
  
  
3. Installed kernel from -proposed:

root@ubuntu:~# apt-cache policy linux-image-virtual linux-virtual
linux-image-virtual:
  Installed: 5.15.0.77.75
  Candidate: 5.15.0.77.75
  Version table:
 *** 5.15.0.77.75 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 5.15.0.75.73 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 5.15.0.25.27 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
linux-virtual:
  Installed: 5.15.0.77.75
  Candidate: 5.15.0.77.75
  Version table:
 *** 5.15.0.77.75 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 5.15.0.75.73 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 5.15.0.25.27 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages


4. Added back:

  
0x0003
  
  
5. Instance booted fine:

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.15.0-77-generic #84-Ubuntu SMP Fri Jun 16 16:16:44 UTC 2023 x86_6
4 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ sudo dmesg | grep -i sev
[0.217323] AMD Memory Encryption Features active: SEV
[5.296555] SVM: KVM is unsupported when running as an SEV guest


6. Full dmesg: https://paste.ubuntu.com/p/5MDcKbVzPv/

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

Title:
  Encountering an issue with memcpy_fromio causing failed boot of SEV-
  enabled guest

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

Bug description:
  [Impact]
  When launching a SEV-enabled guest, the guest kernel panics with the 
following call trace,
  indicating a critical error in the system.

  ==
  [1.090638] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers
  [1.092105] Linux agpgart interface v0.103
  [1.092716] BUG: unable to handle page fault for address: 9b820003d068
  [1.093445] #PF: supervisor read access in kernel mode
  [1.093966] #PF: error_code(0x) - not-present page
  [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 
8001001da067 PTE 8000fed40173
  [1.094629] Oops:  [#1] SMP NOPTI
  [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic 
#49-Ubuntu
  [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 
02/06/2015
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 
0002
  [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 
9b820001ba90
  [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 
0f80
  [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 
8cc7068eca48
  [1.094629] R13: 8cc700a64288 R14:  R15: 
fed40080
  [1.094629] FS:  () GS:8cc77bd0() 
knlGS:
  [1.094629] CS:  0010 DS:  ES:  CR0: 80050033
  [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 
00350ee0
  [1.094629] Call Trace:
  [1.094629]  
  [1.094629]  crb_map_io+0x315/0x870
  [1.094629]  ? radix_tree_iter_tag_clear+0x12/0x20
  [1.094629]  ? _raw_spin_unlock_irqrestore+0xe/0x30
  [1.094629]  crb_acpi_add+0xc2/0x140
  [1.094629]  acpi_device_probe+0x4c/0x170
  [1.094629]  really_probe+0x222/0x420
  [1.094629]  __driver_probe_device+0x119/0x190
  [1.094629]  driver_probe_device+0x23/0xc0
  [1.094629]  __driver_attach+0xbd/0x1e0
  [1.094629]  ? __device_attach_driver+0x120/0x120
  [1.094629]  bus_for_each_dev+0x7e/0xd0
  [1.094629]  driver_attach+0x1e/0x30
  [1.094629]  bus_add_driver+0x139/0x200
  [1.094629]  driver_register+0x95/0x100
  [1.094629]  ? init_tis+0xfd/0xfd
  [1.094629]  acpi_bus_register_driver+0x39/0x50
  [1.094629]  crb_acpi_driver_init+0x15/0x1b
  [1.094629]  do_one_initcall+0x48/0x1e0
  [1.094629]  do_initcalls+0x12f/0x159
  [1.094629]  

[Kernel-packages] [Bug 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  Fix only reach PC3 when ethernet is plugged r8169

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Triaged
Status in linux-oem-5.13 source package in Kinetic:
  Invalid
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-5.13 source package in Lunar:
  Invalid
Status in linux-oem-5.14 source package in Lunar:
  Invalid
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-5.13 source package in Mantic:
  Invalid
Status in linux-oem-5.14 source package in Mantic:
  Invalid
Status in linux-oem-5.17 source package in Mantic:
  Invalid
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  System only can reach PC3, and it affects power consumption alot.

  [Fix]
  Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state 
issue, but also fixes network speed issue.
  V7:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/
  V6:
  
https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/

  
  [Test]
  Verified on 2 different systems which has PC state issue and has network 
speed issue, these patches fix both issues.

  [Where problems could occur]
  It toggles ASPM on and off depends on the network traffic during runtime, I 
don't think it'll lead to any regressions. Some potential issues have been 
addressed during the patch submitting. It's v6 now and accepted by upstream.

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


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

[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-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/1977827

Title:
  ftrace in ubuntu_kernel_selftests failed with "check if duplicate
  events are caught" on J-5.15 P9 / J-kvm / L-kvm

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

Bug description:
  Issue found on Jammy 5.15.0-36.37 with Power9 node baltar

  Test failed with:
  # [15] Generic dynamic event - check if duplicate events are caught [FAIL]

  Test Log:
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
   TAP version 13
   1..1
   # selftests: ftrace: ftracetest
   # === Ftrace unit tests ===
   # [1] Basic trace file check [PASS]
   # [2] Basic test for tracers [PASS]
   # [3] Basic trace clock test [PASS]
   # [4] Basic event tracing check  [PASS]
   # [5] Change the ringbuffer size [PASS]
   # [6] Snapshot and tracing setting   [PASS]
   # [7] trace_pipe and trace_marker[PASS]
   # [8] Test ftrace direct functions against tracers   [UNRESOLVED]
   # [9] Test ftrace direct functions against kprobes   [UNRESOLVED]
   # [10] Generic dynamic event - add/remove eprobe events  [PASS]
   # [11] Generic dynamic event - add/remove kprobe events  [PASS]
   # [12] Generic dynamic event - add/remove synthetic events   [PASS]
   # [13] Generic dynamic event - selective clear (compatibility)   [PASS]
   # [14] Generic dynamic event - generic clear event   [PASS]
   # [15] Generic dynamic event - check if duplicate events are caught  [FAIL]
   # [16] event tracing - enable/disable with event level files [PASS]
   # [17] event tracing - restricts events based on pid notrace filtering   
[PASS]
   # [18] event tracing - restricts events based on pid [PASS]
   # [19] event tracing - enable/disable with subsystem level files [PASS]
   # [20] event tracing - enable/disable with top level files   [PASS]
   # [21] Test trace_printk from module [PASS]
   # [22] ftrace - function graph filters with stack tracer [PASS]
   # [23] ftrace - function graph filters   [PASS]
   # [24] ftrace - function pid notrace filters [PASS]
   # [25] ftrace - function pid filters [PASS]
   # [26] ftrace - stacktrace filter command[PASS]
   # [27] ftrace - function trace with cpumask  [PASS]
   # [28] ftrace - test for function event triggers [PASS]
   # [29] ftrace - function trace on module [PASS]
   # [30] ftrace - function profiling   [PASS]
   # [31] ftrace - function profiler with function tracing  [PASS]
   # [32] ftrace - test reading of set_ftrace_filter[PASS]
   # [33] ftrace - test for function traceon/off triggers   [PASS]
   # [34] ftrace - test tracing error log support   [PASS]
   # [35] Test creation and deletion of trace instances while setting an event  
[PASS]
   # [36] Test creation and deletion of trace instances [PASS]
   # [37] Kprobe dynamic event - adding and removing[PASS]
   # [38] Kprobe dynamic event - busy event check   [PASS]
   # [39] Kprobe dynamic event with arguments   [PASS]
   # [40] Kprobe event with comm arguments  [PASS]
   # [41] Kprobe event string type argument [PASS]
   # [42] Kprobe event symbol argument  [PASS]
   # [43] Kprobe event argument syntax  [PASS]
   # [44] Kprobes event arguments with types[PASS]
   # [45] Kprobe event user-memory access   [UNSUPPORTED]
   # [46] Kprobe event auto/manual naming   [PASS]
   # [47] Kprobe dynamic event with function tracer [PASS]
   # [48] Create/delete multiprobe on kprobe event  [PASS]
   # [49] Kprobe event parser error log check   [PASS]
   # [50] Kretprobe dynamic event with arguments[PASS]
   # [51] Kretprobe dynamic event with maxactive[PASS]
   # [52] Kretprobe %return suffix test [PASS]
   # [53] Register/unregister many kprobe events[PASS]
   # [54] Kprobe profile[PASS]
   # [55] Uprobe event parser error log check   [PASS]
   # [56] test for the preemptirqsoff tracer[UNSUPPORTED]
   # 

[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  ftrace in ubuntu_kernel_selftests failed with "check if duplicate
  events are caught" on J-5.15 P9 / J-kvm / L-kvm

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

Bug description:
  Issue found on Jammy 5.15.0-36.37 with Power9 node baltar

  Test failed with:
  # [15] Generic dynamic event - check if duplicate events are caught [FAIL]

  Test Log:
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
   TAP version 13
   1..1
   # selftests: ftrace: ftracetest
   # === Ftrace unit tests ===
   # [1] Basic trace file check [PASS]
   # [2] Basic test for tracers [PASS]
   # [3] Basic trace clock test [PASS]
   # [4] Basic event tracing check  [PASS]
   # [5] Change the ringbuffer size [PASS]
   # [6] Snapshot and tracing setting   [PASS]
   # [7] trace_pipe and trace_marker[PASS]
   # [8] Test ftrace direct functions against tracers   [UNRESOLVED]
   # [9] Test ftrace direct functions against kprobes   [UNRESOLVED]
   # [10] Generic dynamic event - add/remove eprobe events  [PASS]
   # [11] Generic dynamic event - add/remove kprobe events  [PASS]
   # [12] Generic dynamic event - add/remove synthetic events   [PASS]
   # [13] Generic dynamic event - selective clear (compatibility)   [PASS]
   # [14] Generic dynamic event - generic clear event   [PASS]
   # [15] Generic dynamic event - check if duplicate events are caught  [FAIL]
   # [16] event tracing - enable/disable with event level files [PASS]
   # [17] event tracing - restricts events based on pid notrace filtering   
[PASS]
   # [18] event tracing - restricts events based on pid [PASS]
   # [19] event tracing - enable/disable with subsystem level files [PASS]
   # [20] event tracing - enable/disable with top level files   [PASS]
   # [21] Test trace_printk from module [PASS]
   # [22] ftrace - function graph filters with stack tracer [PASS]
   # [23] ftrace - function graph filters   [PASS]
   # [24] ftrace - function pid notrace filters [PASS]
   # [25] ftrace - function pid filters [PASS]
   # [26] ftrace - stacktrace filter command[PASS]
   # [27] ftrace - function trace with cpumask  [PASS]
   # [28] ftrace - test for function event triggers [PASS]
   # [29] ftrace - function trace on module [PASS]
   # [30] ftrace - function profiling   [PASS]
   # [31] ftrace - function profiler with function tracing  [PASS]
   # [32] ftrace - test reading of set_ftrace_filter[PASS]
   # [33] ftrace - test for function traceon/off triggers   [PASS]
   # [34] ftrace - test tracing error log support   [PASS]
   # [35] Test creation and deletion of trace instances while setting an event  
[PASS]
   # [36] Test creation and deletion of trace instances [PASS]
   # [37] Kprobe dynamic event - adding and removing[PASS]
   # [38] Kprobe dynamic event - busy event check   [PASS]
   # [39] Kprobe dynamic event with arguments   [PASS]
   # [40] Kprobe event with comm arguments  [PASS]
   # [41] Kprobe event string type argument [PASS]
   # [42] Kprobe event symbol argument  [PASS]
   # [43] Kprobe event argument syntax  [PASS]
   # [44] Kprobes event arguments with types[PASS]
   # [45] Kprobe event user-memory access   [UNSUPPORTED]
   # [46] Kprobe event auto/manual naming   [PASS]
   # [47] Kprobe dynamic event with function tracer [PASS]
   # [48] Create/delete multiprobe on kprobe event  [PASS]
   # [49] Kprobe event parser error log check   [PASS]
   # [50] Kretprobe dynamic event with arguments[PASS]
   # [51] Kretprobe dynamic event with maxactive[PASS]
   # [52] Kretprobe %return suffix test [PASS]
   # [53] Register/unregister many kprobe events[PASS]
   # [54] Kprobe profile[PASS]
   # [55] Uprobe event parser error log check   [PASS]
   # [56] test for the preemptirqsoff tracer[UNSUPPORTED]
   # 

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

[Ubuntu Kernel Bot]

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

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

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


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

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

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

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid

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

  [Impact]

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

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

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

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

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

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

  struct lsmblob {
     u32 secid[LSMBLOB_ENTRIES];
  };

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

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

  GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"

  You will receive the following panic:

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

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

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

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

  [Fix]

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

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

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

[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-5.19 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-hwe-5.19 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-hwe-5.19 source package in Mantic:
  Invalid

Bug description:
  With below commit in 5.16 upstream kernel, support for
  mdev_set_iommu_device() kABI was removed from kernel as there were no
  in-tree drivers making use of the kABI.

  fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")

  This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
  (SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
  kABI to pin all guest memory during VM boot.

  As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
  it will not include this kABI and as a result will break SRIOV based
  Nvidia vGPU. So, filing this bug to request to have a custom patch in
  HWE kernel which doesn't remove the support for
  mdev_set_iommu_device() kABI.

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


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

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[Giuliano Lotta]

@andrianovigor

Hi Igor !
the 
https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/blob/main/uvc_driver.c
 at line  2687 has ALREADY supported the 0408:4033 Quanta model.

Which uvc_drriver.c did you download ?

Did you launch the bash file ? It directly download all the necessary
files, compile and install them...

The script is to be launched each time the kernel get updated (you need
to recompile the driver to follow the new kernel version...)

By
Giuliano

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably 

[Kernel-packages] [Bug 2015440] Re: fib_tests.sh in ubuntu_kernel_selftests was skipped silently on Focal

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Status: In Progress => 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/2015440

Title:
  fib_tests.sh in ubuntu_kernel_selftests was skipped silently on Focal

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

Bug description:
  [Impact]
  When applying the following commit via stable update (bug 2011625):
Revert "ipv4: Fix incorrect route flushing when source address is
deleted"

  The executable bit of this script was dropped. And this test will be
  skipped on 5.4:
   # selftests: net: fib_tests.sh
   # Warning: file fib_tests.sh is missing!
   not ok 1 selftests: net: fib_tests.sh

  [Fix]
  * f0c95f229a ("selftests: Fix the executable permissions for fib_tests.sh")

  This can be cherry-picked to Focal from linux-5.4.y of the stable
  tree.

  [Test]
  Run the test with the patched kernel. This test will not be skipped.

  [Where problems could occur]
  This change just allow the script to get tested, however we will see
  failures reported from this test.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-kvm source package in Jammy:
  In Progress
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  In Progress
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Committed
Status in linux-kvm source package in Lunar:
  In Progress
Status in linux-meta-azure source package in Lunar:
  New
Status in linux-meta-kvm source package in Lunar:
  New
Status in linux source package in Mantic:
  In Progress
Status in linux-kvm source package in Mantic:
  In Progress
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_IMA_ARCH_POLICY

  (The latter is needed to ensure that MoK keys can be used to verify
  dm-verity images too, via the machine keyring linked to the secondary
  keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-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/2018591

Title:
  Enable Tracing Configs for OSNOISE and TIMERLAT

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  == SRU Justification ==
  These config changes will allow tracing with the OSNOISE and TIMERLAT tracing 
tools.

  These tracers can be enabled at run-time and should not affect
  performance or add any additional overhead.

  == Fix ==
  UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs

  == Regression Potential ==
  Low.  These config changes will just allow the use of tracing tools.

  == Test Case ==
  Test build.

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


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

[Kernel-packages] [Bug 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Enable Tracing Configs for OSNOISE and TIMERLAT

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  == SRU Justification ==
  These config changes will allow tracing with the OSNOISE and TIMERLAT tracing 
tools.

  These tracers can be enabled at run-time and should not affect
  performance or add any additional overhead.

  == Fix ==
  UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs

  == Regression Potential ==
  Low.  These config changes will just allow the use of tracing tools.

  == Test Case ==
  Test build.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-kvm source package in Jammy:
  In Progress
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  In Progress
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Committed
Status in linux-kvm source package in Lunar:
  In Progress
Status in linux-meta-azure source package in Lunar:
  New
Status in linux-meta-kvm source package in Lunar:
  New
Status in linux source package in Mantic:
  In Progress
Status in linux-kvm source package in Mantic:
  In Progress
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_IMA_ARCH_POLICY

  (The latter is needed to ensure that MoK keys can be used to verify
  dm-verity images too, via the machine keyring linked to the secondary
  keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2019915] Re: Enable audio LEDs on HP laptops

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  Enable audio LEDs on HP laptops

Status in HWE Next:
  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:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Audio LEDs are not working on some new HP laptops.

  [Fix]
  Use Realtek codec specific method, VREF, to enable audio LEDs.

  [Test]
  With the fix applied, audio LEDs function correctly.

  [Where problems could occur]
  The fix only applies to two hardwares, so other hardwares are
  unaffected.

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


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

[Kernel-packages] [Bug 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  No  HDMI/DP audio output on dock(Nvidia GPU)

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

Bug description:
  [Impact]
  When the machine is docked with an external monitor, it is able to output 
display, but the HDMI/DP audio output option is lost in DGFF Hybrid 
Discrete/Discrete mode(Nvidia GPU).

  [Fix]
  Nvidia provides a patch to fix it
  
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/

  in 6.4-rc3
  dc4f2ccaeddd ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table

  [Test]
  Verified on the target machine.

  {Where problems could occur]
  The patch just adds IDs, and won't lead to any regression.

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


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

[Kernel-packages] [Bug 2020295] Re: Include the MAC address pass through function on RTL8153DD-CG

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Include the MAC address pass through function on RTL8153DD-CG

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

Bug description:
  [Impact]
  When user connect network cable on the RJ45 port of RTL8153DD-CG on dock, it 
should show pass through MAC address set in BIOS. But the LAN MAC address pass 
through doesn't function on RTL8153DD-CG sku.

  [Fix]
  Commit in v6.3-rc1 fixes the issue.
  ec51fbd1b8a2 r8152: add USB device driver for config selection

  [Test]
  Verified by OEM.

  [Where problems could occur]
  It won't affect the old behavior if there is no preferred cfg is configured 
and will select the preferred one while probing.

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


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

[Kernel-packages] [Bug 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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-focal-linux verification-needed-focal

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

Title:
  Encountering an issue with memcpy_fromio causing failed boot of SEV-
  enabled guest

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

Bug description:
  [Impact]
  When launching a SEV-enabled guest, the guest kernel panics with the 
following call trace,
  indicating a critical error in the system.

  ==
  [1.090638] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers
  [1.092105] Linux agpgart interface v0.103
  [1.092716] BUG: unable to handle page fault for address: 9b820003d068
  [1.093445] #PF: supervisor read access in kernel mode
  [1.093966] #PF: error_code(0x) - not-present page
  [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 
8001001da067 PTE 8000fed40173
  [1.094629] Oops:  [#1] SMP NOPTI
  [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic 
#49-Ubuntu
  [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 
02/06/2015
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 
0002
  [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 
9b820001ba90
  [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 
0f80
  [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 
8cc7068eca48
  [1.094629] R13: 8cc700a64288 R14:  R15: 
fed40080
  [1.094629] FS:  () GS:8cc77bd0() 
knlGS:
  [1.094629] CS:  0010 DS:  ES:  CR0: 80050033
  [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 
00350ee0
  [1.094629] Call Trace:
  [1.094629]  
  [1.094629]  crb_map_io+0x315/0x870
  [1.094629]  ? radix_tree_iter_tag_clear+0x12/0x20
  [1.094629]  ? _raw_spin_unlock_irqrestore+0xe/0x30
  [1.094629]  crb_acpi_add+0xc2/0x140
  [1.094629]  acpi_device_probe+0x4c/0x170
  [1.094629]  really_probe+0x222/0x420
  [1.094629]  __driver_probe_device+0x119/0x190
  [1.094629]  driver_probe_device+0x23/0xc0
  [1.094629]  __driver_attach+0xbd/0x1e0
  [1.094629]  ? __device_attach_driver+0x120/0x120
  [1.094629]  bus_for_each_dev+0x7e/0xd0
  [1.094629]  driver_attach+0x1e/0x30
  [1.094629]  bus_add_driver+0x139/0x200
  [1.094629]  driver_register+0x95/0x100
  [1.094629]  ? init_tis+0xfd/0xfd
  [1.094629]  acpi_bus_register_driver+0x39/0x50
  [1.094629]  crb_acpi_driver_init+0x15/0x1b
  [1.094629]  do_one_initcall+0x48/0x1e0
  [1.094629]  do_initcalls+0x12f/0x159
  [1.094629]  kernel_init_freeable+0x162/0x1b5
  [1.094629]  ? rest_init+0x100/0x100
  [1.094629]  kernel_init+0x1b/0x150
  [1.094629]  ? rest_init+0x100/0x100
  [1.094629]  ret_from_fork+0x22/0x30
  [1.094629]  
  [1.094629] Modules linked in:
  [1.094629] CR2: 9b820003d068
  [1.094629] ---[ end trace 3d6d81c42a3c2030 ]---
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 
0002
  [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 
9b820001ba90
  [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 
0f80
  [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 
8cc7068eca48
  [

[Kernel-packages] [Bug 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Encountering an issue with memcpy_fromio causing failed boot of SEV-
  enabled guest

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

Bug description:
  [Impact]
  When launching a SEV-enabled guest, the guest kernel panics with the 
following call trace,
  indicating a critical error in the system.

  ==
  [1.090638] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers
  [1.092105] Linux agpgart interface v0.103
  [1.092716] BUG: unable to handle page fault for address: 9b820003d068
  [1.093445] #PF: supervisor read access in kernel mode
  [1.093966] #PF: error_code(0x) - not-present page
  [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 
8001001da067 PTE 8000fed40173
  [1.094629] Oops:  [#1] SMP NOPTI
  [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic 
#49-Ubuntu
  [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 
02/06/2015
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 
0002
  [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 
9b820001ba90
  [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 
0f80
  [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 
8cc7068eca48
  [1.094629] R13: 8cc700a64288 R14:  R15: 
fed40080
  [1.094629] FS:  () GS:8cc77bd0() 
knlGS:
  [1.094629] CS:  0010 DS:  ES:  CR0: 80050033
  [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 
00350ee0
  [1.094629] Call Trace:
  [1.094629]  
  [1.094629]  crb_map_io+0x315/0x870
  [1.094629]  ? radix_tree_iter_tag_clear+0x12/0x20
  [1.094629]  ? _raw_spin_unlock_irqrestore+0xe/0x30
  [1.094629]  crb_acpi_add+0xc2/0x140
  [1.094629]  acpi_device_probe+0x4c/0x170
  [1.094629]  really_probe+0x222/0x420
  [1.094629]  __driver_probe_device+0x119/0x190
  [1.094629]  driver_probe_device+0x23/0xc0
  [1.094629]  __driver_attach+0xbd/0x1e0
  [1.094629]  ? __device_attach_driver+0x120/0x120
  [1.094629]  bus_for_each_dev+0x7e/0xd0
  [1.094629]  driver_attach+0x1e/0x30
  [1.094629]  bus_add_driver+0x139/0x200
  [1.094629]  driver_register+0x95/0x100
  [1.094629]  ? init_tis+0xfd/0xfd
  [1.094629]  acpi_bus_register_driver+0x39/0x50
  [1.094629]  crb_acpi_driver_init+0x15/0x1b
  [1.094629]  do_one_initcall+0x48/0x1e0
  [1.094629]  do_initcalls+0x12f/0x159
  [1.094629]  kernel_init_freeable+0x162/0x1b5
  [1.094629]  ? rest_init+0x100/0x100
  [1.094629]  kernel_init+0x1b/0x150
  [1.094629]  ? rest_init+0x100/0x100
  [1.094629]  ret_from_fork+0x22/0x30
  [1.094629]  
  [1.094629] Modules linked in:
  [1.094629] CR2: 9b820003d068
  [1.094629] ---[ end trace 3d6d81c42a3c2030 ]---
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 
0002
  [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 
9b820001ba90
  [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 
0f80
  [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 
8cc7068eca48
  [1.094629] 

[Kernel-packages] [Bug 2020356] Re: generate linux-lib-rust only on amd64

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-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/2020356

Title:
  generate linux-lib-rust only on amd64

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Incomplete

Bug description:
  [Impact]

  Rust is only supported by amd64 at the moment, so there is no reason
  to generate linux-lib-rust packages on the other architectures.

  [Test case]

  Simply build the kernel, generating all the deb packages.

  [Fix]

  Produce linux-lib-rust only on amd64.

  [Regression potential]

  If Rust will be enabled on other architectures we need to remember to
  undo this change, or selectively enable the packaging on the
  architectures that will get the Rust support.

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


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

[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-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/2020531

Title:
  support python < 3.9 with annotations

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

Bug description:
  [Impact]

  At the moment we can't use the annotations scripts in focal, because
  we are using the'|=' update operator for merging dicts, that has been
  introduced with python 3.9.

  Rewrite the code that is using this operator in a more portable way
  and apply this change everywhere, so that annotations will work on any
  backport/derivative kernels.

  [Test case]

  Run `fakeroot debian/rules updateconfigs` in focal (using the new
  annotations model).

  [Fix]

  Try to use the '|=' operator in a try/except block, if it fails
  fallback to a more portable way.

  [Regression potential]

  With this change applied we may experience regressions during the
  updateconfigs phase.

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


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

[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  System either hang with black screen or rebooted on entering suspend
  on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justfication]

  [Impact]

  On AMD Phoenix platforms, system may hang, or reboot while resuming from
  suspend.

  [Fix]

  Two patches in v6.4-rc3 for amdgpu. The first one is pulled for
  dependency.

  [Test Case]

  $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto
  $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30
  $ checkbox-cli run 
com.canonical.certification::power-management/suspend_30_cycles_with_reboots

  [Where problems could occur]

  The fix is to safely guard register access as it should be. No potential
  problem identified so far.

  [Other Info]

  This should affects v6.1 or above as which AMD Phoenix are supported,
  and has been included in mantic-6.3 through stable-6.3.4 and in oem-6.1
  through stable-6.1.30, leaving lunar-6.2 unfixed only.

  == original bug report ==

  To reproduce:

  ```
  $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto
  # or
  $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30
  ```

  Proposed fixes from AMD:
  * 
https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b
  * 
https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1277 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1277 F pulseaudio
  CasperMD5CheckMismatches: ./preseed/project.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-jammy-amd64-20230421-366
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-04-21 (38 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-stella-jammy-amd64-20230421-366
  MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem 
root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29
  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.1.0-1014-oem N/A
   linux-backports-modules-6.1.0-1014-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.13
  Tags:  jammy
  Uname: Linux 6.1.0-1014-oem x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 05/08/2023
  dmi.bios.release: 30.1
  dmi.bios.vendor: HP
  dmi.bios.version: V85 Ver. 00.30.01
  dmi.board.name: 8B95
  dmi.board.vendor: HP
  

[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
  type-C dongle

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

Bug description:
  [Impact]
  Enabling CL1 (Controller Low Power) states during discovery of existing 
tunnels established by the system firmware can interfere with the operation of 
those tunnels.
  The DisplayPort tunnel establishment timeout of 1.5 seconds can be 
insufficient for some docking stations, leading to blank displays.

  [Fix]
  CL1 states are now not enabled during discovery of existing tunnels. The TMU 
settings also remain unchanged.
  The timeout is increased to 3 seconds to allow more time for the DisplayPort 
connection manager handshake, fixing the issue of displays remaining blank.

  [Test Cases]
  1. plug docking station on the host
  2. bring up the host and get into desktop.
  3. flip docking station's cable.
  4. check if the external monitor works well

  [Where problems could occur]
  Low, If the handshake actually requires even more than 3 seconds in some 
cases, the timeout may still need to be increased further.

  [Misc]
  Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a 
huge,  
  so skip Jammy.

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


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

[Kernel-packages] [Bug 2020743] Re: FM350(mtk_t7xx) failed to suspend, or early wake while suspending

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  FM350(mtk_t7xx) failed to suspend, or early wake while suspending

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  FM350(mtk_t7xx) can't suspend sometimes.

  kernel: [ 12.917396] mtk_t7xx :57:00.0: [PM] Exiting suspend, modem in 
invalid state
  kernel: [ 12.917406] mtk_t7xx :57:00.0: PM: pci_pm_suspend(): 
t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -14
  kernel: [ 12.917446] mtk_t7xx :57:00.0: PM: dpm_run_callback(): 
pci_pm_suspend+0x0/0x1b0 returns -14
  kernel: [ 12.917462] mtk_t7xx :57:00.0: PM: failed to suspend async: 
error -14

  [Fix]
  The commit in v6.4-rc3 waits for the device to be ready before suspending.
  ab87603b2511 net: wwan: t7xx: Ensure init is completed before system sleep

  [Test]
  Verified on the machine with FM350 wwan module.

  [Where problems could occur]
  If the wwan is not ready before the time is up, it results in -ETIMEDOUT. 
However, in this scenario, we will encounter the same issue where the system 
fails to enter suspend mode. Therefore, it will not introduce regressions or 
new issues.

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


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

[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  System either hang with black screen or rebooted on entering suspend
  on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justfication]

  [Impact]

  On AMD Phoenix platforms, system may hang, or reboot while resuming from
  suspend.

  [Fix]

  Two patches in v6.4-rc3 for amdgpu. The first one is pulled for
  dependency.

  [Test Case]

  $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto
  $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30
  $ checkbox-cli run 
com.canonical.certification::power-management/suspend_30_cycles_with_reboots

  [Where problems could occur]

  The fix is to safely guard register access as it should be. No potential
  problem identified so far.

  [Other Info]

  This should affects v6.1 or above as which AMD Phoenix are supported,
  and has been included in mantic-6.3 through stable-6.3.4 and in oem-6.1
  through stable-6.1.30, leaving lunar-6.2 unfixed only.

  == original bug report ==

  To reproduce:

  ```
  $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto
  # or
  $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30
  ```

  Proposed fixes from AMD:
  * 
https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b
  * 
https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1277 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1277 F pulseaudio
  CasperMD5CheckMismatches: ./preseed/project.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-jammy-amd64-20230421-366
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-04-21 (38 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-stella-jammy-amd64-20230421-366
  MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem 
root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29
  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.1.0-1014-oem N/A
   linux-backports-modules-6.1.0-1014-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.13
  Tags:  jammy
  Uname: Linux 6.1.0-1014-oem x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 05/08/2023
  dmi.bios.release: 30.1
  dmi.bios.vendor: HP
  dmi.bios.version: V85 Ver. 00.30.01
  dmi.board.name: 8B95
  

[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Severe NFS performance degradation after LP #2003053

Status in linux package in Ubuntu:
  Incomplete
Status in linux-gke package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-gke source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-gke source package in Jammy:
  Fix Released

Bug description:
  The fix to LP #2003053 has caused massively increased NFS server
  access in some use-cases, which caused severe performance degradation
  to the point of being unusable in some cases.

  The solution to this issue, at least temporarily and at least for
  linux-gke, is to make the new behaviour optional using the
  "nfs_fasc=1" module parameter. Without this parameter specified, (or
  specified as =0) will keep the old behaviour.

  
  Regresion potential:
   - Regression potential is considered low considering the scope of the change 
and is limited to NFS only.

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


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

[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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

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


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

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

Title:
  introduce do_lib_rust=true|false to enable/disable linux-lib-rust
  package

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Lunar:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Incomplete
Status in linux-aws source package in Mantic:
  New

Bug description:
  [Impact]

  Provide a variable do_lib_rust=true|false in the kernel build system
  to selectively enable the Rust packaging (linux-lib-rust) with
  specific kernels and specific architectures.

  Right now Rust should be enabled only in lunar and mantic and only on
  amd64.

  [Test case]

  Build the kernel producing all the debs.

  [Fix]

  Introduce a do_lib_rust=true variable that will be defined only in
  debian.master/rules.d/amd64.mk for now.

  [Regression potential]

  Kernels may need to set this variables if they want to enable the Rust
  support.

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


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

[Kernel-packages] [Bug 2021449] Re: ALSA: hda/realtek: Enable headset onLenovo M70/M90

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  ALSA: hda/realtek: Enable headset onLenovo M70/M90

Status in OEM Priority Project:
  Triaged
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:
  Fix Committed

Bug description:
  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.

  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f

  [Test]
  After applying the patch, the os works fine with the headset mic on 6.1.0-oem.

  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2021449/+subscriptions


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

[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
  type-C dongle

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

Bug description:
  [Impact]
  Enabling CL1 (Controller Low Power) states during discovery of existing 
tunnels established by the system firmware can interfere with the operation of 
those tunnels.
  The DisplayPort tunnel establishment timeout of 1.5 seconds can be 
insufficient for some docking stations, leading to blank displays.

  [Fix]
  CL1 states are now not enabled during discovery of existing tunnels. The TMU 
settings also remain unchanged.
  The timeout is increased to 3 seconds to allow more time for the DisplayPort 
connection manager handshake, fixing the issue of displays remaining blank.

  [Test Cases]
  1. plug docking station on the host
  2. bring up the host and get into desktop.
  3. flip docking station's cable.
  4. check if the external monitor works well

  [Where problems could occur]
  Low, If the handshake actually requires even more than 3 seconds in some 
cases, the timeout may still need to be increased further.

  [Misc]
  Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a 
huge,  
  so skip Jammy.

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


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

[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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-focal-linux

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

Title:
  Severe NFS performance degradation after LP #2003053

Status in linux package in Ubuntu:
  Incomplete
Status in linux-gke package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-gke source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-gke source package in Jammy:
  Fix Released

Bug description:
  The fix to LP #2003053 has caused massively increased NFS server
  access in some use-cases, which caused severe performance degradation
  to the point of being unusable in some cases.

  The solution to this issue, at least temporarily and at least for
  linux-gke, is to make the new behaviour optional using the
  "nfs_fasc=1" module parameter. Without this parameter specified, (or
  specified as =0) will keep the old behaviour.

  
  Regresion potential:
   - Regression potential is considered low considering the scope of the change 
and is limited to NFS only.

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


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

[Kernel-packages] [Bug 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix Disable thunderbolt clx make edp-monitor garbage while moving the
  touchpad

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

Bug description:
  [impact]
  The default sync pulse length for fast wake AUX transactions was changed from 
18 to 10, which was causing issues with some eDP panels.

  [fix]
  Revert the sync pulse length for fast wake AUX transactions back to the 
hardware default of 18 (10 precharge + 8 preamble).

  [test cases]
  1. configure with thunderbolt.clx=0.
  2. check edp's behavior and it should work well and there's no garbage.

  [where the issue could happen]
  low, By reverting this setting back to the default, this commit restores 
stability for configurations using fast wake AUX transactions, especially those 
involving eDP panels that were incompatible with the shorter sync pulse length. 
The longer, hardware-default sync pulse length is compatible with more use 
cases.

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


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

[Kernel-packages] [Bug 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  Fix Disable thunderbolt clx make edp-monitor garbage while moving the
  touchpad

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

Bug description:
  [impact]
  The default sync pulse length for fast wake AUX transactions was changed from 
18 to 10, which was causing issues with some eDP panels.

  [fix]
  Revert the sync pulse length for fast wake AUX transactions back to the 
hardware default of 18 (10 precharge + 8 preamble).

  [test cases]
  1. configure with thunderbolt.clx=0.
  2. check edp's behavior and it should work well and there's no garbage.

  [where the issue could happen]
  low, By reverting this setting back to the default, this commit restores 
stability for configurations using fast wake AUX transactions, especially those 
involving eDP panels that were incompatible with the shorter sync pulse length. 
The longer, hardware-default sync pulse length is compatible with more use 
cases.

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


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

[Kernel-packages] [Bug 2023197] Re: Fix speaker volume too low on HP G10 laptops

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix speaker volume too low on HP G10 laptops

Status in HWE Next:
  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:
  Incomplete
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]
  HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to 
enable all amplifiers to output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The quirk is for Cirrus codec on particular HP series laptops.
   * The risk of regression should only impact particular models

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


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

[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Add support of Smart Amplifier IC ALC1319D  on Intel platforms

Status in HWE Next:
  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:
  Incomplete
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Speaker is not functional on some Dell machines of Intel RPL platforms

  [Fix]
  Here's the patch submitted by Intel.
  
https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy Output` shown on the Audio output 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/2023201/+subscriptions


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

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

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


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

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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-focal-linux verification-needed-focal

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

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


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

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

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


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

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

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


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

[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-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/2023539

Title:
  Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2

  [Fix]
  Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2.

  [Test]
  Tested with alsa audio, audio works fine.

  [Where problems could occur]
  Risk low due to specific hardware.

  These 2 patches are already in Unstable and OEM-6.1 already got them
  via stable updates.

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


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

[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2

  [Fix]
  Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2.

  [Test]
  Tested with alsa audio, audio works fine.

  [Where problems could occur]
  Risk low due to specific hardware.

  These 2 patches are already in Unstable and OEM-6.1 already got them
  via stable updates.

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


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

[Kernel-packages] [Bug 2023307] Re: System hang at reading amdgpu sysfs attribute psp_vbflash

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  System hang at reading amdgpu sysfs attribute psp_vbflash

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Summary]
  1. System hang on starting checkbox test.
  2. Hang on collecting device information during start Auto and Stress test.
  3. This issue exist on GPU with W7500 & W7600.

  [Steps to reproduce]
  1. Boot into OS
  2. Start Auto test or Stress test(checkbox-cli run 
com.canonical.certification::sysfs_attachment)

  AMD proposed fix in 
https://lore.kernel.org/amd-gfx/20230607065259.48516-1-mario.limoncie...@amd.com/T/#mc5c38f31129f23e498d669734cafe96474a8f8ba
 .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1442 F pulseaudio
   /dev/snd/controlC0:  u  1442 F pulseaudio
  CasperMD5CheckResult: pass
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-tynamo+X81
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-05-16 (23 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  IwConfig:
   lono wireless extensions.
   
   enp5s0f0  no wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Dell Inc. Precision 7875 Tower
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem 
root=UUID=e9463c30-0a89-4838-a9fa-3296791ccd2a ro log_buf_len=64M quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29
  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.1.0-1014-oem N/A
   linux-backports-modules-6.1.0-1014-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.13
  RfKill:
   
  Tags:  jammy
  Uname: Linux 6.1.0-1014-oem x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 05/10/2023
  dmi.bios.release: 0.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.28
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 0.18
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.28:bd05/10/2023:br0.4:efr0.18:svnDellInc.:pnPrecision7875Tower:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0C61:
  dmi.product.family: Precision
  dmi.product.name: Precision 7875 Tower
  dmi.product.sku: 0C61
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2023311] Re: Resolve synchronous exception on arm64

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Resolve synchronous exception on arm64

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

Bug description:
  SRU Justification

  [Impact]

  MSFT has requested the inclusion of commit
  e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64: efi: Recover from
  synchronous exceptions occurring in firmware'). It looks generic
  enough to apply to the master kernel.

  Unlike x86, which has machinery to deal with page faults that occur
  during the execution of EFI runtime services, arm64 has nothing like
  that, and a synchronous exception raised by firmware code brings down
  the whole system.

  [Test Plan]

  This looks like a hard one to reproduce. Boot and regression testing
  should be sufficient.

  [Regression Potential]

  Firmware exceptions could still take down the system.

  [Other Info]

  SF: #00362062

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


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

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

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

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

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


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

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-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/2023577

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

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

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

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


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

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

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

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

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


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

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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-focal-linux verification-needed-focal

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

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

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

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

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


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

[Kernel-packages] [Bug 2023650] Re: Add microphone support of the front headphone port on P3 Tower

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Add microphone support of the front headphone port on P3 Tower

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The 3.5mm headphone port in front panel cannot detect the microphone. 

  [Fix]
  Add quirk for headset mic pin on P3 Tower.

  [Test]
  Tested with alsa audio, mic works fine.

  [Where problems could occur]
  Low risk to add specific hardware ID.

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


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

[Kernel-packages] [Bug 2023650] Re: Add microphone support of the front headphone port on P3 Tower

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Add microphone support of the front headphone port on P3 Tower

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The 3.5mm headphone port in front panel cannot detect the microphone. 

  [Fix]
  Add quirk for headset mic pin on P3 Tower.

  [Test]
  Tested with alsa audio, mic works fine.

  [Where problems could occur]
  Low risk to add specific hardware ID.

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


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

[Kernel-packages] [Bug 2023650] Re: Add microphone support of the front headphone port on P3 Tower

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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-lunar-linux verification-needed-lunar

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

Title:
  Add microphone support of the front headphone port on P3 Tower

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The 3.5mm headphone port in front panel cannot detect the microphone. 

  [Fix]
  Add quirk for headset mic pin on P3 Tower.

  [Test]
  Tested with alsa audio, mic works fine.

  [Where problems could occur]
  Low risk to add specific hardware ID.

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


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

[Kernel-packages] [Bug 1639924] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2023-06-19 06:27 EDT---
Big thank you to everybody who has contributed and helped to make this 
important feature available for s390x.

With this being released to Jammy, we can close the bug / LP entry.

Changing the status to CLOSED.

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

Title:
  Kernel livepatch support for for s390x

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in kpatch package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in gcc-11 source package in Jammy:
  Fix Released
Status in kpatch source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in gcc-11 source package in Kinetic:
  Fix Released
Status in kpatch source package in Kinetic:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * kpatch upstream has gained support for more architectures which we
  would like to enable on LTS release. Since building livepatches using
  the kpatch tooling makes the most sense on LTS kernels.

   * This SRU is to enable s390x builds of kpatch on kinetic & jammy.

   * Separately linux kernel patches for s390x will also be backported
  to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to
  support livepatches.

  [ Test Plan ]

   * Attempt to run and load sample integration livepatches from the
  kpatch integration source code, against v5.15 & v5.19 kernels. These
  should succeed on:

   - amd64 jammy v5.15
   - amd64 & s390x jammy v5.19
   - amd64 & s390x kinetic v5.19

  [ Where problems could occur ]

   * The newly generated livepatches produced by this kpatch may have
  different content (more or less sections/sybmols/relocations/etc), but
  remain compatible with all prior kernels and tool-chains.

   * This is a fairly large upstream update to the tooling.

   * One command line option to kpatch-build is no longer supported
  '-e', instead long form command line option must be used '--oot-
  module'. And '--ott-module-src' becomes mandatory in such cases,
  previously '--sourcedire' was required.

  Additional command line options added '--oot-module-src, -R|--non-
  replace'.

  '--skip-gcc-check' is still supported but prints warnings, it is
  deprecated in favour of '--skip-compiler-check'.

  kpatch-cc utility is added, which is a toolchain wrapper.

  Thus adjustments might be needed to scripts used to invoke and create
  kpatch modules.

   * Majority of non-test/non-doc changes are to do with:
     - add support for s390x and 32bit powerpc
     - add support for newer kernels and compilers (support & bugfixes to 
various sections and symbols)
     - more strict checking and bugfixes w.r.t. livepatch generation
     - refactoring and better build support for cross-compiled modules, 
compilation for various linux distributions, and code cleanups.

  * Some of the fixes from these new upstream releases have already been
  cherry-picked in the kpatch, but others might soon be needed on x84,
  i.e. to support gcc-12 built kernels.

  $ git log  --no-merges  --oneline v0.8.0..v0.9.7 -- kmod/ kpatch-
  build/ > shortlog.txt

  d46fea98ef kpatch-build: strengthen conditions for changed sections
  9fac261ed0 kpatch-build: rela section could disappear after patched
  fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules
  8cc0fedefb kpatch-build: use err.h instead of error.h for musl support
  07433e98c0 kpatch-cc: fix stripping of source tree prefix
  33368a88cd create-diff-object: add support for .return_sites section (x86)
  e921c557f9 macros: tweak syscall patching macros
  a1171b112e create-diff-object: Create missing section symbol
  0308d52bcd kpatch/s390: Enable kpatch build support
  b0330ab18e kpatch/s390: Add additional bundled symbols.
  eb4a85f778 kpatch/s390: Add exclusion lists
  f0d00a9290 kpatch/s390: Add initial support for kpatch
  10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch
  c6d0b5450b lookup: fix symtab parsing
  52863dace0 create-diff-object: fix endianness in 
kpatch_no_sibling_calls_ppc64le()
  017015a725 create-diff-object: make kpatch_check_relocations() more precise
  f0e3da336c create-diff-object: fix string extraction
  86d5208b46 create-diff-object: error on symbol conversion failure
  325bccd89d create-diff-object: skip conversion for sections which never have 
symbols
  8508abd3b1 create-diff-object: allow converstion of empty symbols
  8d5a628bde create-diff-object: add extra check for symbol conversion edge case
  01427d50a1 create-diff-object: move addend math to a new function
  bec6488af6 create-diff-object: add rela_insn() error check
  6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec'
  bf212f7750 create-diff-object: error on unsupported rela 

[Kernel-packages] [Bug 2024126] Re: eDP power on flow enhancement to speed up kernel boot time

[AceLan Kao]

** Description changed:

  [Impact]
- eDP power on flow enhancement to speed up kernel boot time
+ eDP power on flow enhancement to speed up kernel boot time.
+ This commit is recommended by Intel.
  
  [Fix]
- The commit from 6.2-rc1 is recommended by Intel
+ The commit below is from 6.2-rc1
  36d357169891 drm/i915/edp: wait power off delay at driver remove to optimize 
probe
  
  [Test]
  No
  
  [Where problems could occur]
+ The assumption of the patch should be always correct, we don't have to wait 
the panel to be powered off when boots up, the panel power should has been 
switched off right before boots up. And the panel_power_off_time value will be 
set to the desired value in wait_panel_power_cycle(). So, should be pretty safe 
to include this patch.

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

Title:
  eDP power on flow enhancement to speed up kernel boot time

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

Bug description:
  [Impact]
  eDP power on flow enhancement to speed up kernel boot time.
  This commit is recommended by Intel.

  [Fix]
  The commit below is from 6.2-rc1
  36d357169891 drm/i915/edp: wait power off delay at driver remove to optimize 
probe

  [Test]
  No

  [Where problems could occur]
  The assumption of the patch should be always correct, we don't have to wait 
the panel to be powered off when boots up, the panel power should has been 
switched off right before boots up. And the panel_power_off_time value will be 
set to the desired value in wait_panel_power_cycle(). So, should be pretty safe 
to include this patch.

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


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

[Kernel-packages] [Bug 2024126] Re: For runtime s0ix to work with few eDP panel models

[AceLan Kao]

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

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

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

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

** No longer affects: linux (Ubuntu Jammy)

** No longer affects: linux (Ubuntu)

** Description changed:

  [Impact]
- For runtime s0ix to work with few eDP panel models
+ eDP power on flow enhancement to speed up kernel boot time
  
  [Fix]
- 6.2-rc1
+ The commit from 6.2-rc1 is recommended by Intel
  36d357169891 drm/i915/edp: wait power off delay at driver remove to optimize 
probe
  
  [Test]
+ No
  
  [Where problems could occur]

** Summary changed:

- For runtime s0ix to work with few eDP panel models
+ eDP power on flow enhancement to speed up kernel boot time

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

Title:
  eDP power on flow enhancement to speed up kernel boot time

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

Bug description:
  [Impact]
  eDP power on flow enhancement to speed up kernel boot time

  [Fix]
  The commit from 6.2-rc1 is recommended by Intel
  36d357169891 drm/i915/edp: wait power off delay at driver remove to optimize 
probe

  [Test]
  No

  [Where problems could occur]

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


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

[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms

[AceLan Kao]

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
 Assignee: AceLan Kao (acelankao)
   Status: In Progress

** Also affects: linux-oem-6.1 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

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

Title:
  Remove all other acpi_video backlight interface on Dell AIO platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
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:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  There are acpi_video* sysfs backlight interface in the system which are not 
working.
  For Dell AIO platforms, we use dell_uart_backlight to control the display 
brightness.
  The old way to fix this is to unregister acpi backlight interfaces in the 
backlight driver, but it may lead to some issues and the unregister function 
has been removed since v6.1-rc1
  77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")

  [Fix]
  The new way to do this is to collect all the quirk and auto detection method 
in video_detect.c
  I added an audo detection for the Dell AIO platoform to the driver which 
should do the same thing as the old way.

  [Test]
  Verified on the Dell AIO platform and confirmed there is only on 
dell_uart_backlight in the sysfs, and no acpi_video* interface.

  [Where problems could occur]
  There should be no regression potential, it uses different way to do the same 
thing, should be pretty safe.

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


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

[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0

[Richard Laager]

My experience so far lines up with the above: 148 good, 150 bad, 152
good.

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

Title:
  linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212
  sk_stream_kill_queues+0xcf/0xe0

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

Bug description:
  After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu
  Focal), I noticed that it was suddenly getting a bunch of kernel log
  (dmesg) reports like:

  WARNING: CPU: 4 PID: 0 at net/core/stream.c:212
  sk_stream_kill_queues+0xcf/0xe0

  while investigating I determined that it is currently running the
  focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns
  out was enabled for this server (clearly it seemed like a good idea at
  the time).

  I'm not expecting focal-proposed to be fixed as if it were a release
  package, but since I couldn't find any reports on Launchpad I figured
  I should let y'all know this focal-proposed package could do with some
  additional work before it's actually released :-)

  There have been at least 80 such reports in the last 5 hours since the
  server was rebooted, differing only by the CPU core and the process
  reported, although it seems the last one was a couple of hours ago, so
  I guess it's traffic dependent/timing dependent.

  ewen@naosr620:~$ uptime
   16:27:32 up  5:19,  1 user,  load average: 0.08, 0.14, 0.06
  ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: 
[0-9]*/PID: N/;' | uniq -c
   88 WARNING: CPU: N PID: N at net/core/stream.c:212 
sk_stream_kill_queues+0xcf/0xe0
  ewen@naosr620:~$ 

  Ubuntu Release:

  ewen@naosr620:~$ lsb_release -rd
  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04
  ewen@naosr620:~$ 

  
  Kernel/package version affected:

  ewen@naosr620:~$ uname -a
  Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149
  ii  linux-image-5.4.0-149-generic  5.4.0-149.166  
   amd64Signed kernel image generic
  ii  linux-image-generic5.4.0.149.147  
   amd64Generic Linux kernel image
  ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic 
  linux-image-5.4.0-149-generic:
Installed: 5.4.0-149.166
Candidate: 5.4.0-149.166
Version table:
   *** 5.4.0-149.166 500
  500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  ewen@naosr620:~$ apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 5.4.0.149.147
Candidate: 5.4.0.149.147
Version table:
   *** 5.4.0.149.147 500
  500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.4.0.148.146 500
  500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 
Packages
  500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 
Packages
   5.4.0.26.32 500
  500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages
  ewen@naosr620:~$ 
  ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source:
  Source: linux-signed
  ewen@naosr620:~$ 

  
  Full example dmesg, including stack trace (they all seem to be WARNINGs, and 
other than filling dmesg / system logs the system "appears to be running okay", 
so I'm not going to rush another reboot now -- near end of business day):

  ewen@naosr620:~$ date
  Tue 09 May 2023 16:34:56 NZST
  ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 
"cut here"
  [Tue May  9 14:21:18 2023] [ cut here ]
  [Tue May  9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 
sk_stream_kill_queues+0xcf/0xe0
  [Tue May  9 14:21:18 2023] Modules linked in: mpt3sas raid_class 
scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT 
nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent 
ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment 
xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp 
iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp 
nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc 
ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp 
ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink 
nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter dell_rbu nls_iso8859_1 

[Kernel-packages] [Bug 2002968] Re: Fix flicker display problem on some panels which support PSR2

[Timo Aaltonen]

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

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

Title:
  Fix flicker display problem on some panels which support PSR2

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  On some PSR2 supported panels, which connects to Intel Graphics has flicker 
symptom. It gets normal after booting the kernel with parameter `i915. 
enable_psr=0`

  [Fix]
  Backport one patch from upstream. 
https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_psr.c?id=084aab04cc60e5eab32287d0483c33e12c92da87

  [Test]
  Booting the patched kernel with problematic panel (LGD LCD_VD78M), check if 
the display has abnormal flickering problem on graphics interfaces.

  [Where problems could occur]
  The risk of regression is low. It only fixes problem on panels which support 
PSR2.

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


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

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-23-generic 6.2.0-23.23 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:
  I plugged in external monitor and set the settings to external
  display. But even after removing HDMI cable, it not showing content in
  laptop screen (black screen). I have restarted system twice.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ashish-prabhakar   2339 F wireplumber
   /dev/snd/controlC2:  ashish-prabhakar   2339 F wireplumber
   /dev/snd/controlC1:  ashish-prabhakar   2339 F wireplumber
   /dev/snd/seq:ashish-prabhakar   2336 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Fri Jun 16 18:16:00 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-05-24 (25 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G531GV_G531GV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=b6a95648-2d38-4582-b8b1-d629e81dbc99 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-23-generic 6.2.0-23.23 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: 02/01/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G531GV.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G531GV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG531GV.308:bd02/01/2021:br5.13:svnASUSTeKCOMPUTERINC.:pnROGStrixG531GV_G531GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G531GV_G531GV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 2024346] [NEW] package linux-image-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

[Ashish Prabhakar]

Public bug reported:

I plugged in external monitor and set the settings to external display.
But even after removing HDMI cable, it not showing content in laptop
screen (black screen). I have restarted system twice.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-23-generic 6.2.0-23.23
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ashish-prabhakar   2339 F wireplumber
 /dev/snd/controlC2:  ashish-prabhakar   2339 F wireplumber
 /dev/snd/controlC1:  ashish-prabhakar   2339 F wireplumber
 /dev/snd/seq:ashish-prabhakar   2336 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Fri Jun 16 18:16:00 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2023-05-24 (25 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G531GV_G531GV
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=b6a95648-2d38-4582-b8b1-d629e81dbc99 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: dkms
Title: package linux-image-6.2.0-23-generic 6.2.0-23.23 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: 02/01/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G531GV.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G531GV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG531GV.308:bd02/01/2021:br5.13:svnASUSTeKCOMPUTERINC.:pnROGStrixG531GV_G531GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G531GV_G531GV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: dkms (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 dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2024346

Title:
  package linux-image-6.2.0-23-generic 6.2.0-23.23 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:
  I plugged in external monitor and set the settings to external
  display. But even after removing HDMI cable, it not showing content in
  laptop screen (black screen). I have restarted system twice.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ashish-prabhakar   2339 F wireplumber
   /dev/snd/controlC2:  ashish-prabhakar   2339 F wireplumber
   /dev/snd/controlC1:  ashish-prabhakar   2339 F wireplumber
   /dev/snd/seq:ashish-prabhakar   2336 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Fri Jun 16 18:16:00 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-05-24 (25 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G531GV_G531GV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=b6a95648-2d38-4582-b8b1-d629e81dbc99 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-23-generic 6.2.0-23.23 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: 02/01/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G531GV.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G531GV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
 

[Kernel-packages] [Bug 2024183] Re: package linux-headers-generic 6.2.0.20.20 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato

[Juerg Haefliger]

You have an unsupported DKMS modules installed. Remove it and retry the
upgrade:

$ dkms remove nvidia/520.61.05 --all


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

Title:
  package linux-headers-generic 6.2.0.20.20 failed to install/upgrade:
  problemi con le dipendenze - lasciato non configurato

Status in linux package in Ubuntu:
  Invalid

Bug description:
  my pc comes with this error. I can't use new version of ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-generic 6.2.0.20.20
  ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  AptOrdering:
   linux-headers-5.19.0-42-generic:amd64: Remove
   linux-headers-5.19.0-42:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarinaleggy   1527 F wireplumber
   /dev/snd/seq:sarinaleggy   1524 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Jun 16 14:08:49 2023
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  InstallationDate: Installed on 2022-10-22 (236 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5220 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G6 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=ac43499b-4533-4383-94f3-a886a9aabd42 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-generic 6.2.0.20.20 failed to install/upgrade: 
problemi con le dipendenze - lasciato non configurato
  UpgradeStatus: Upgraded to lunar on 2023-06-10 (5 days ago)
  dmi.bios.date: 08/10/2022
  dmi.bios.release: 15.70
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.70
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832A
  dmi.board.vendor: HP
  dmi.board.version: 23.77
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 23.77
  dmi.modalias: 
dmi:bvnInsyde:bvrF.70:bd08/10/2022:br15.70:efr23.77:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.77:cvnHP:ct10:cvrChassisVersion:sku1WY24EA#ABZ:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.sku: 1WY24EA#ABZ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2024292] Re: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess r

[Juerg Haefliger]

You have an unsupported DKMS module installed. Remove it and retry the
upgrade:

# dkms remove anbox-binder/1 --all


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

Title:
  package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to
  install/upgrade: installed linux-headers-6.2.0-23-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
dkms libppd2 libppd2-common
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  6 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up linux-headers-6.2.0-23-generic (6.2.0-23.23) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-23-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j8 KERNELRELEASE=6.2.0-23-generic all 
KERNEL_SRC=/lib/modules/6.2.0-23-generic/build...(bad exit status: 2)
  ERROR (dkms apport): binary package for anbox-binder: 1 not found
  Error! Bad return status for module build on kernel: 6.2.0-23-generic (x86_64)
  Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-23-generic (--configure):
   installed linux-headers-6.2.0-23-generic package post-installation script 
subpr
  ocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-23-generic; however:
Package linux-headers-6.2.0-23-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-image-6.2.0-23-generic (6.2.0-23.23) ...
  No apport report written because the error message indicates its a followup 
erro
  r from a previous failure.
dpkg: dependency problems prevent configuration of 
lin
  ux-headers-generic-hwe-22.04:
   linux-headers-generic-hwe-22.04 depends on linux-headers-6.2.0-23-generic; 
howe
  ver:
Package linux-headers-6.2.0-23-generic is not configured yet.

  dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
6.2.0.23.
  23); however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.23.23); however:
Package linux-headers-generic is not configured yet.

  No apport report written because the error message indicates its a followup 
erro
  r from a previous failure.
No apport report written because MaxReports is 
reached
   already
  No apport report written because MaxReports is reached already
dpkg: 
erro
  r processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for linux-image-6.2.0-23-generic (6.2.0-23.23) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-23-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j8 KERNELRELEASE=6.2.0-23-generic all 
KERNEL_SRC=/lib/modules/6.2.0-23-gen
  eric/build...(bad exit status: 2)
  ERROR (dkms apport): binary package for anbox-binder: 1 not found
  Error! Bad return status for module build on kernel: 6.2.0-23-generic (x86_64)
  Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: 

[Kernel-packages] [Bug 2024292] Re: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess r

[Juerg Haefliger]

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.2.0-23-generic all 
KERNEL_SRC=/lib/modules/6.2.0-23-generic/build...(bad exit status: 2)
ERROR (dkms apport): binary package for anbox-binder: 1 not found
Error! Bad return status for module build on kernel: 6.2.0-23-generic (x86_64)
Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!

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

Title:
  package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to
  install/upgrade: installed linux-headers-6.2.0-23-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
dkms libppd2 libppd2-common
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  6 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up linux-headers-6.2.0-23-generic (6.2.0-23.23) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-23-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j8 KERNELRELEASE=6.2.0-23-generic all 
KERNEL_SRC=/lib/modules/6.2.0-23-generic/build...(bad exit status: 2)
  ERROR (dkms apport): binary package for anbox-binder: 1 not found
  Error! Bad return status for module build on kernel: 6.2.0-23-generic (x86_64)
  Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-23-generic (--configure):
   installed linux-headers-6.2.0-23-generic package post-installation script 
subpr
  ocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-23-generic; however:
Package linux-headers-6.2.0-23-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-image-6.2.0-23-generic (6.2.0-23.23) ...
  No apport report written because the error message indicates its a followup 
erro
  r from a previous failure.
dpkg: dependency problems prevent configuration of 
lin
  ux-headers-generic-hwe-22.04:
   linux-headers-generic-hwe-22.04 depends on linux-headers-6.2.0-23-generic; 
howe
  ver:
Package linux-headers-6.2.0-23-generic is not configured yet.

  dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
6.2.0.23.
  23); however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.23.23); however:
Package linux-headers-generic is not configured yet.

  No apport report written because the error message indicates its a followup 
erro
  r from a previous failure.
No apport report written because MaxReports is 
reached
   already
  No apport report written because MaxReports is reached already
dpkg: 
erro
  r processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for linux-image-6.2.0-23-generic (6.2.0-23.23) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-23-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j8 KERNELRELEASE=6.2.0-23-generic all 
KERNEL_SRC=/lib/modules/6.2.0-23-gen
  eric/build...(bad exit status: 2)
  ERROR (dkms apport): binary package for anbox-binder: 1 not found
  Error! Bad return status for module build on 

[Kernel-packages] [Bug 2024183] Re: package linux-headers-generic 6.2.0.20.20 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato

[Juerg Haefliger]

Building module:
Cleaning build area...
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 
'make' -j4 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.2.0-20-generic 
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/lib/modules/6.2.0-20-generic/build LD=/usr/bin/ld.bfd 
modules...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/nvidia-dkms-520.0.crash'
Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
Consult /var/lib/dkms/nvidia/520.61.05/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!

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

Title:
  package linux-headers-generic 6.2.0.20.20 failed to install/upgrade:
  problemi con le dipendenze - lasciato non configurato

Status in linux package in Ubuntu:
  Invalid

Bug description:
  my pc comes with this error. I can't use new version of ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-generic 6.2.0.20.20
  ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  AptOrdering:
   linux-headers-5.19.0-42-generic:amd64: Remove
   linux-headers-5.19.0-42:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarinaleggy   1527 F wireplumber
   /dev/snd/seq:sarinaleggy   1524 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Jun 16 14:08:49 2023
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  InstallationDate: Installed on 2022-10-22 (236 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5220 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G6 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=ac43499b-4533-4383-94f3-a886a9aabd42 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-generic 6.2.0.20.20 failed to install/upgrade: 
problemi con le dipendenze - lasciato non configurato
  UpgradeStatus: Upgraded to lunar on 2023-06-10 (5 days ago)
  dmi.bios.date: 08/10/2022
  dmi.bios.release: 15.70
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.70
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832A
  dmi.board.vendor: HP
  dmi.board.version: 23.77
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 23.77
  dmi.modalias: 
dmi:bvnInsyde:bvrF.70:bd08/10/2022:br15.70:efr23.77:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.77:cvnHP:ct10:cvrChassisVersion:sku1WY24EA#ABZ:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.sku: 1WY24EA#ABZ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2016355] Re: Cannot change to proprietary driver

[Launchpad Bug Tracker]

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

** Changed in: linux-restricted-modules-hwe-5.19 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Cannot change to proprietary driver

Status in linux-restricted-modules-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  Whenever I change to a proprietary driver for my Nvidia 1660 super
  card, I get a pk-client-error-quark error while installing package.
  Running dpkg --configure -a gives errors while processing these driver
  files.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-525-server-5.19.0-38-generic 
5.19.0-38.39~22.04.1+1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Apr 14 23:01:37 2023
  DuplicateSignature:
   
package:linux-modules-nvidia-525-server-5.19.0-38-generic:5.19.0-38.39~22.04.1+1
   Setting up linux-modules-nvidia-525-server-5.19.0-38-generic 
(5.19.0-38.39~22.04.1+1) ...
   /var/lib/dpkg/info/linux-modules-nvidia-525-server-5.19.0-38-generic.config: 
6: /etc/default/linux-modules-nvidia: 
linux-modules-nvidia-525-open-generic-hwe-22.04: not found
   dpkg: error processing package 
linux-modules-nvidia-525-server-5.19.0-38-generic (--configure):
installed linux-modules-nvidia-525-server-5.19.0-38-generic package 
post-installation script subprocess returned error exit status 127
  ErrorMessage: installed linux-modules-nvidia-525-server-5.19.0-38-generic 
package post-installation script subprocess returned error exit status 127
  InstallationDate: Installed on 2023-04-15 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: linux-restricted-modules-hwe-5.19
  Title: package linux-modules-nvidia-525-server-5.19.0-38-generic 
5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed 
linux-modules-nvidia-525-server-5.19.0-38-generic package post-installation 
script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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