date:20221212

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

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

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


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

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

Title:
  Support Intel IPU6 MIPI camera

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

Bug description:
  [SRU Justfication:linux-firmware]

  [Impact]

  Need new firmware updates for additional camera senesors.

  [Fix]

  Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for
  hi556/ovti02c1.

  [Test Case]

  The driver will prompt for missed firmware blobs for a given platform.

  [Where problems could occur]

  There is still no suspend support for the camera driver, and user sessions
  across system suspend have to be restarted.

  [Other Info]

  New sensors are introduced in Jammy oem kernels only, and kinetic is nominated
  for future hwe migration.

  = original bug report ==

  This is a follow-up for bug 1964983 but on different platforms that
  runs linux-oem-5.17 or newer.

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


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

[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)

This bug is awaiting verification that the linux-oem-6.0/6.0.0-1009.9
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.0 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/1998115

Title:
  Fix iosm: WWAN cannot build the connection (DW5823e)

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

Bug description:
  [Impact]
   WWAN(DW5823e) can't build the connection successfully.

  [Fix]
   With INTEL_IOMMU disable config or by forcing intel_iommu=off from
   grub some of the features of IOSM driver like browsing, flashing &
   coredump collection is not working.
  
   When driver calls DMA API - dma_map_single() for tx transfers. It is
   resulting in dma mapping error.
  
   Set the device DMA addressing capabilities using dma_set_mask() and
   remove the INTEL_IOMMU dependency in kconfig so that driver follows
   the platform config either INTEL_IOMMU enable or disable.
   
   Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY 
   CONFIGs yet on iosm module, the single patch is necessary for Jammy.

  [Test Case]
   1. boot up with kernel applied the FIX.
   2. check the status of wwan by "mmcli -m 0"
   Status| unlock retries: sim-pin (3)
 |  state: ^[32mconnected^[0m
 |power state: on
 |access tech: lte
 | signal quality: 45% (recent)
--
3GPP |   imei: ##
 |  enabled locks: sim, fixed-dialing
 |operator id: 46692
 |  operator name: Chunghwa Telecom
 |   registration: home
 |   packet service state: attached
 |pco:
 | 0: (complete)

  
  [Where problems could occur]
  remove the dependency for intel_iommu, iosm would fit better on other 
platforms not only Intel.

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


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

[Kernel-packages] [Bug 1998419] Re: Gnome doesn't run smooth when performing normal usage with RPL-P CPU

This bug is awaiting verification that the linux-oem-6.0/6.0.0-1009.9
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.0 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/1998419

Title:
  Gnome doesn't run smooth when performing normal usage with RPL-P CPU

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

Bug description:
  [Impact]
  Gnome desktop doesn't run smooth when performing normal usage, the cursor 
usually stops working and stuck, and then becomes back to normal.

  [Fix]
  Can't reproduce this issue with drm-tip kernel, so found below commit after 
bisected
  dc73ac63e63a drm/i915/rpl-p: Add stepping info

  [Test]
  Verified on the RPL-P machine and the cursor/window move smoothly.

  [Where problems could occur]
  Adding info for new RPL-P chipset should be pretty safe.

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


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

[Kernel-packages] [Bug 1998727] Re: Fix System cannot detect bluetooth after running suspend stress test

This bug is awaiting verification that the linux-oem-6.0/6.0.0-1009.9
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.0 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/1998727

Title:
  Fix System cannot detect bluetooth after running suspend stress test

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 source package in Jammy:
  In Progress
Status in linux-oem-6.0 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 source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
   System cannot detect bluetooth after running 
power-management/suspend-30-cycles-with-reboots

  [Fix]
   Enable BT recovery on Realtek 8852CE FW, FW would detect and recover.

  [Test Case]
  1. checkbox-cli run 
com.canonical.certification::power-management/suspend_30_cycles_with_reboots
  2. check settings > bluetooth

  [Where problems could occur]
  just enable a function from kernel and run the code in the fw.
  the main risk would be related to FW.

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


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

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

This bug is awaiting verification that the linux-oem-6.0/6.0.0-1009.9
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.0

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

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

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

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

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

  The patch has been accepted but still not shown in the upstream tree,
  so submit this patch to oem kernels first, and will submit it to other
  generic ubuntu kernels.

  [Test]
  Verified by our QA and ODM.

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

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


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

[Kernel-packages] [Bug 1992467] Re: Screen Tearing

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Screen Tearing

Status in linux package in Ubuntu:
  Expired

Bug description:
  Screen Tearing

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andre  1515 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 11 10:57:49 2022
  InstallationDate: Installed on 2022-10-11 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. Latitude 3490
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=7970276e-6642-48a8-af7d-02e8e109b252 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2022
  dmi.bios.release: 1.21
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.21.0
  dmi.board.name: 04HCMV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd08/15/2022:br1.21:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn04HCMV:rvrA01:cvnDellInc.:ct10:cvr:sku0839:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3490
  dmi.product.sku: 0839
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-6.0/6.0.0.1009.9)

2022-12-12 Thread Ubuntu SRU Bot

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

backport-iwlwifi-dkms/9858-0ubuntu3.1 (amd64)
systemd/249.11-0ubuntu3.6 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-oem-6.0

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-12-12 Thread ybdjkfd

Hi juliank, I understand completely you want me to have insights related
to verification of the update in lunar-proposed and that I am confusing
you with my #131 post.

I was mentioning that to help people who need the triage, since it is
not possible to say locked out nor without updates until lunar is
released.  The reasons for #131 is to note the original issue that
brought out our understanding of this problem, liked in my #45, that
when Raspberry Pi needs changed the compression, we suddenly realized
that for everyone else grub had a memory issue on some systems since we
were not compressing it as much.

One of the triages I shared out of 2 fixed things for some time, but
after the latest kernel update to 5.19.0-26 from 5.19.0-23, the initrd
image grows significantly and both triages--compression and module
dependencies, are necessary on my system.

So in cases of knowing that it is fixed properly, great.  In cases where
we don't have an update that may be backported, we are lost in 2 triages
that people need to find instructions and help on that are here---
therefore my post on #131 you noted was not relevant.

When you install 5.19.0-26, you will need the triages on initrd. On
5.19.0-23, the initrd is much, much smaller.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 /

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

2022-12-12 Thread Hui Wang

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

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

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

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

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

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


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

[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec

2022-12-12 Thread Hui Wang

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

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

Title:
  alsa: soc: the kernel print UBSAN calltrace on the machine with
  cs35l41 codec

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

Bug description:
  The cs35l41 codec driver was backported to Jammy kernel a couple of
  months ago, recently the Jammy kernel was adopted as the hwe kernel
  for OEM machines and with this kernel the UBSAN calltrace was seen,
  need to backport these 2 patches. Kinetic kernel already has the
  patches, so this SRU is only for Jammy kernel.

  [Impact]
  Install the 5.15 hwe kernel on the machines with cs35l41
  codec, after booting and check the dmesg, there is a UBSAN calltrace.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, check the dmesg, there
  is no UBSAN calltrace, and test the audio functions, all input
  and output devices coudl work as well as before.

  
  [Where problems could occur]
  The patch only affects the cirruslogic asoc codec driver, if it
  could introduce the regression, it will be on the machines with
  cs codec, and it will make the audio driver initialization fail
  and make the system lose the audio function. But this possibility
  is very low, we tested the patches on many oem machines, all
  worked well.

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


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

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

2022-12-12 Thread Alex Murray

** Information type changed from Public Security to Public

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

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

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


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

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

2022-12-12 Thread Bram Stolk

@thedoctar Add it to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
file.

$ sudo dmesg  | grep "Command line"
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash intel_pstate=passive 
eisa_bus.disable_dev=1,2,3,4,5,6,7,8 vt.handoff=7

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

2022-12-12 Thread Robert Lippmann

Turns out my issue was a faulty drive, and the system would lock up when
mdadm hit the bad sectors on resync. The issue seemed like it was lower
in the blockdev code causing a deadlock.

I replaced the drive and the problem went away.

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

Title:
  kernel io hangs during mdcheck/resync

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

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]  submit_bio_noacct+0x112/0x4f0
  [921588.559075]  submit_bio+0x51/0x1a0
  [921588.559077]  ? _cond_resched+0x19/0x30
  [921588.559081]  ? kmem_cache_alloc+0x38e/0x440
  [921588.559084]  ? ext4_init_io_end+0x1f/0x50
  [921588.559088]

[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org

2022-12-12 Thread Don Brace

Thanks, Don... sorry to ask but to make this easier on me (I'm the one who has 
to find the time do do this) could you revise the list in the summary with all 
the desired patches (including the ones from the 6.2 MKP tree) in pick order?
DON> Sure.

And just to be sure, they all cleanly pick with no missing prerequisites or 
conflicts?
DON> No conflicts at all. They are now cutting over to 6.2. I have noticed that 
all are now in linux-next, so I can create the list from linux-next...
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
That will make if really easy. And I'll re-pick them just to be sure.


I will have to sort out what to pick for each affected kernel, as I will
have to pull them back from 6.2 -> 5.19.

Also, Gerry said the target was 20.04.2, so that means the 5.19 HWE kernel, yes?
DON> Yes

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

Title:
  smartpqi: Update 22.04 driver to latest kernel.org

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There are some outstanding patches already in Linus's tree that can be 
applied to 22.04.
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  The following patches apply to
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

  f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
  e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
  6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
  2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
  cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
  6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
  69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
  85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
  2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
  44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
  331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
  904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
  297bdc540f0e scsi: smartpqi: Close write read holes
  dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
  1d393227fc76 scsi: smartpqi: Add controller fw version to console log
  4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
  8946ea283808 scsi: smartpqi: Fix typo in comment
  c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
  31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
  62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
  291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
  c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
  5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
  c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
  00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
  5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
  27655e9db479 scsi: smartpqi: Update volume size after expansion
  b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
  42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
  9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
  b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
  94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
  70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
  2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
  c57ee4ccb358 scsi: smartpqi: Add PCI IDs
  c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
  64fc9015fbeb scsi: smartpqi: Switch to attribute groups
  0ca190805784 scsi: smartpqi: Call scsi_done() directly

  I added the above SHA1 IDs to a file called:
  backport_linus_6.1_into_22.04

  git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
  git am -s /tmp/patches/*.diff

  All patches applied without any conflicts.

  [impact]
  This patches correct some bugs and add support for more PCI devices. Also, 
the in-box driver is largely out-of-date with kernel.org.

  [fix]
  Applying these patches (along with the patches noted below) bring smartpqi up 
to date with our OOB driver and kernel.org. Both have been tested.
  [Test Plan] Our OOB driver has undergone extensive testing by our test team.

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


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

[Kernel-packages] [Bug 1998838] Re: Azure: Jammy fio test hangs, swiotlb buffers exhausted

This bug was fixed in the package linux-azure - 5.15.0-1029.36

---
linux-azure (5.15.0-1029.36) jammy; urgency=medium

  * jammy/linux-azure: 5.15.0-1029.36 -proposed tracker (LP: #1998845)

  * Azure: Jammy fio test hangs, swiotlb buffers exhausted (LP: #1998838)
- SAUCE: scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM

linux-azure (5.15.0-1027.33) jammy; urgency=medium

  * jammy/linux-azure: 5.15.0-1027.33 -proposed tracker (LP: #1997044)

  [ Ubuntu: 5.15.0-56.62 ]

  * jammy/linux: 5.15.0-56.62 -proposed tracker (LP: #1997079)
  * CVE-2022-3566
- tcp: Fix data races around icsk->icsk_af_ops.
  * CVE-2022-3567
- ipv6: annotate some data-races around sk->sk_prot
- ipv6: Fix data races around sk->sk_prot.
  * CVE-2022-3621
- nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
  * CVE-2022-3564
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu
  * CVE-2022-3524
- tcp/udp: Fix memory leak in ipv6_renew_options().
  * CVE-2022-3565
- mISDN: fix use-after-free bugs in l1oip timer handlers
  * CVE-2022-3594
- r8152: Rate limit overflow messages
  * CVE-2022-43945
- SUNRPC: Fix svcxdr_init_decode's end-of-buffer calculation
- SUNRPC: Fix svcxdr_init_encode's buflen calculation
- NFSD: Protect against send buffer overflow in NFSv2 READDIR
- NFSD: Protect against send buffer overflow in NFSv3 READDIR
- NFSD: Protect against send buffer overflow in NFSv2 READ
- NFSD: Protect against send buffer overflow in NFSv3 READ
- NFSD: Remove "inline" directives on op_rsize_bop helpers
- NFSD: Cap rsize_bop result based on send buffer size
  * CVE-2022-42703
- mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
  * 5.15.0-53-generic no longer boots (LP: #1996740)
- drm/amd/display: Add helper for blanking all dp displays

linux-azure (5.15.0-1024.30) jammy; urgency=medium

  * jammy/linux-azure: 5.15.0-1024.30 -proposed tracker (LP: #1996817)

  * Azure: Jammy fio test causes panic (LP: #1996806)
- scsi: storvsc: Fix unsigned comparison to zero

 -- Tim Gardner   Mon, 05 Dec 2022 11:54:13
-0700

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

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

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

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

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

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

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

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

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

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

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

Title:
  Azure: Jammy fio test hangs, swiotlb buffers exhausted

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

Bug description:
  SRU Justification

  [Impact]
  Hello Canonical Team,

  This issue was found while doing the validation on CPC's Jammy CVM
  image. We are up against a tight timeline to deliver this to a partner
  on 10/5. Would appreciate prioritizing this.

  While running fio, the command fails to exit after 2 minutes. I
  watched `top` as the command hung and I saw kworkers getting blocked.

  sudo fio --ioengine=libaio --bs=4K
  
--filename=/dev/sdc1:/dev/sdd1:/dev/sde1:/dev/sdf1:/dev/sdg1:/dev/sdh1:/dev/sdi1:/dev/sdj1:/dev/sdk1:/dev/sdl1:/dev/sdm1:/dev/sdn1:/dev/sdo1:/dev/sdp1:/dev/sdq1:/dev/sdr1
  --readwrite=randwrite --runtime=120 --iodepth=1 --numjob=96
  --name=iteration9 --direct=1 --size=8192M --group_reporting
  --overwrite=1

  
  Example system logs:
  
---
  [ 1096.297641] INFO: task kworker/u192:0:8 blocked for more than 120 seconds.
  [ 1096.302785] Tainted: G W 5.15.0-1024-azure #30-Ubuntu
  [ 1096.306312] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1096.310489] INFO: task jbd2/sda1-8:1113 blocked for more than 120 seconds.
  [ 1096.313900] Tainted: G W 5.15.0-1024-azure #30-Ubuntu
  [ 1096.317481] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1096.324117] INFO: task systemd-journal:1191 blocked for more than 120 
seconds.
  [ 1096.331219] Tainted: G W 5.15.0-1024-azure #30-Ubuntu
  [ 1096.335332] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

[Kernel-packages] [Bug 1995749] Re: [i915] Maximum resolution not available after suspend / screen detach

2022-12-12 Thread Peter Dedecker

Hi Daniel,
I replaced the DP cable. After inserting the cable, the full resolution was 
immediately back available. However, the problem/bug still remains: after a 
suspend, the screen only gives a poor resolution and the full resolution is not 
available. After a reboot, the full resolution is back available.

Are you sure about kernel 5.18.19 as it no longer gets security updates
whilst the previous 5.15.0 is the one maintained by the Ubuntu team.

Any other options/possibilities to resolve the issue? 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/1995749

Title:
  [i915] Maximum resolution not available after suspend / screen detach

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my 
laptop which is used at two locations:
  - at work I have my primary built-in 4K display and 2 additional 1920x1080 
monitor connected to a HP DisplayLink docking station using DP, connected to my 
laptop using USB-C
  - at home, I have my primary built-in 4K display and an additional 4x monitor 
directly connected using the mini-DP

  After boot, everything works perfect. However, after working at work,
  putting the laptop into suspend (by closing the lid), attaching to my
  monitor at home and opening the lid again, I get my external display
  at a poor resolution which I cannot change to 4K in the settings menu:
  the 4K resolution is not available. Also in xrandr, the 4K resolution
  is not available. The resolution is however correctly provided by the
  monitor at all times:

  $ sudo get-edid -b 8 | parse-edid
  8
  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  Only trying 8 as per your request.
  256-byte EDID successfully retrieved from i2c bus 8
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "PHL 328P6V"
ModelName "PHL 328P6V"
VendorName "PHL"
# Monitor Manufactured week 30 of 2020
# EDID version 1.4
# Digital Display
DisplaySize 700 400
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-160
VertRefresh 23-80
# Maximum pixel clock is 600MHz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1280x960, 60Hz
#Not giving standard mode: 1440x900, 75Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1280x720, 60Hz

#Extension block found. Parsing...
Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 
2191 +hsync -vsync 
Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168  
+hsync -vsync 
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 
1125 +hsync +vsync interlace
Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 
+hsync +vsync 
Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 
 +hsync -vsync 
Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 
 +hsync -vsync 
Option "PreferredMode" "Mode 12"
  EndSection

  
  Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which 
could easily be solved by unplugging the external monitor and plugging in back 
again, which worked most of the times, sometimes only after a few retries. Now, 
with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this 
situation and logging in again in an Xorg session doesn't help either. Only a 
reboot seems to help.

  Additional debug information at a situation with wrong resolution can
  be provided on Monday, as I just rebooted again :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-12-12 Thread Julian Andres Klode

Hi ybdjkfd I don't really understand what you are doing and how it's
relevant. This issue should be fixed in lunar-proposed 2.06-2ubuntu16,
please only add comments if you have meaningful insights regarding the
verification of that update.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test

[Kernel-packages] [Bug 1999082] Re: linux-modules-nvidia-510-server fails to install

2022-12-12 Thread dann frazier

What happened here is that we dropped the 510 driver in lrm
5.4.0-135.152+1, transitioning it to the 515 driver. It therefore did
not produce a 5.4.0-135.152+1 version of linux-modules-
nvidia-510-server-5.4.0-135-generic. Ubuntu always keeps the latest
version of a binary package in the archive, even if the source that
produced it has been superseded. Because of that, the 5.4.0-135.152
version of linux-modules-nvidia-510-server-5.4.0-135-generic is sticking
around. 5.4.0-135.152 correctly had a strict versioned dep on a matching
linux-signatures package, and that linux-signatures package was
superseded by a new one. Superseded packages *are* dropped from the
archive, so that dependency can no longer be met.

TLDR; this is all normal (though not ideal) behavior, and this one is
particularly confusing because we dropped (and transitioned) the 510
driver during a refresh of the drivers for a kernel that previously had
a 510 driver.

Lesson: Installing modules for anything other than the latest kernel
update is not supported, even if those modules appear to still be
available in the archive.


** Changed in: nvidia-graphics-drivers-510-server (Ubuntu)
   Status: New => Won't Fix

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

Title:
  linux-modules-nvidia-510-server fails to install

Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Won't Fix

Bug description:
  $ sudo apt install linux-modules-nvidia-510-server-$(uname -r)
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-modules-nvidia-510-server-5.4.0-135-generic : Depends: 
linux-signatures-nvidia-5.4.0-135-generic (= 5.4.0-135.152) but 5.4.0-135.152+1 
is to be installed
   Depends: 
nvidia-kernel-common-510-server (<= 510.85.02-1) but it is not going to be 
installed
   Depends: 
nvidia-kernel-common-510-server (>= 510.85.02) but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.5 LTS
  Release:  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510-server/+bug/1999082/+subscriptions


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

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-12-12 Thread ybdjkfd

Bringing one the original triage fixes I posted in #41 and #45 after
gathering some information on changes to grub2 for Raspberry Pi that
exposed this issue (i.e., I know the fix to get things to boot), after
upgrading to 22.10, I now have an updated set of events on a specific
kernel.

I still have the fixes in my system before restarting (after the
upgrade) so that the compression and module dependency setup are triaged
and run with an update grub command as the final stop. Later on, after
an upgrade to the newest kernel 5.19.0-2x-generic, I get on grub:

error: out of memory
Press any key to boot . . .

However, pressing a key will boot forward normally. My
/boot/initrd.img-5.19.0-26-generic size is 131 Mb.  This happens only
with this new kernel.  The previous one did not have this similar error
show.  I thought I would be locked out as before since the triage did
not prevent the error message.  It may be a new cause for the error than
what is originally bothering this bug.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the

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

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1993242] Re: Fix a race condition with AMD PMF and Thinkpad-ACPI

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

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

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1996084] Re: Jammy update: v6.0.7 upstream stable release

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1996083] Re: Jammy update: v6.0.6 upstream stable release

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1996080] Re: Jammy update: v6.0.4 upstream stable release

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1996081] Re: Jammy update: v6.0.5 upstream stable release

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1996783] Re: Jammy update: v6.0.8 upstream stable release

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1996785] Re: Jammy update: v6.0.9 upstream stable release

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
- platform/x86/amd/pmf: Fix undefined reference to platform_profile
- platform/x86/amd/pmf: Fix clang unused variable warning
- platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  *  Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
- net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
- platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
- HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
- drm/i915/gvt: Add missing vfio_unregister_group_dev() call
- m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
- KVM: debugfs: Return retval of simple_attr_open() if it fails
- drm/i915: Allow more varied alternate fixed modes for panels
- drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
- drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
- drm/amd/display: Acquire FCLK DPM levels on DCN32
- drm/amd/display: Limit dcn32 to 1950Mhz display clock
- drm/amd/display: Set memclk levels to be at least 1 for dcn32
- drm/amdkfd: handle CPU fault on COW mapping
- drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
- cxl/region: Recycle region ids
- HID: wacom: Fix logic used for 3rd barrel switch emulation
- hwspinlock: qcom: correct MMIO max register for newer SoCs
- phy: stm32: fix an error code in probe
- wifi: cfg80211: silence a sparse RCU warning
- wifi: cfg80211: fix memory leak in query_regdb_file()
- soundwire: qcom: reinit broadcast completion
- soundwire: qcom: check for outanding writes before doing a read
- ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
  platform_get_irq()
- spi: mediatek: Fix package division error
- bpf, verifier: Fix memory leak in array reallocation for stack state
- bpf, sockmap: Fix the sk->sk_forward_alloc warning of 
sk_stream_kill_queues
- wifi: mac80211: fix general-protection-fault in 
ieee80211_subif_start_xmit()
- wifi: mac80211: Set TWT Information Frame Disabled bit as 1
- bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
  FILE
- HID: hyperv: fix possible memory leak in mousevsc_probe()
- drm/vc4: hdmi: Fix HSM clock too low on Pi4
- bpf, sock_map: Move cancel_work_sync() out of sock lock
- PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
- bpf: Add helper macro bpf_for_each_reg_in_vstate
- bpf: Fix wrong reg type conversion in release_reference()
- net: gso: fix panic on frag_list with mixed head alloc types
- macsec: delete new rxsc when offload fails
- macsec: fix secy->n_rx_sc accounting
- macsec: fix detection of RXSCs when toggling offloading
- macsec: clear encryption keys from the stack after setting up offload
- octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
- net: tun: Fix memory leaks of napi_get_frags
- bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
- bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
- net: fman: Unregister ethernet device on removal
- capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
- phy: ralink: mt7621-pci: add sentinel to quirks table
- KVM: s390: pv: don't allow userspace to set the clock under PV
- KVM: s390: pci: Fix allocation size of aift kzdev elements
- net: lapbether: fix issue of dev reference count leakage in
  lapbeth_device_event()
- hamradio: fix issue of dev reference count leakage in bpq_device_event()
- net: wwan: iosm: fix memory leak in ipc_wwan_dellink
- net: wwan: mhi: fix memory leak in mhi_mbim_dellink
- drm/vc4: Fix missing platform_unregister_drivers() call in
  vc4_drm_register()
- tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
- platform/x86: p2sb: Don't fail if unknown CPU is found
- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
- can: af_can: fix NULL pointer dereference in can_rx_register()
- drm/i915/psr: Send update also on invalidate
- drm/i915: Do not set cache_dirty for DGFX
- net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
- dt-bindings: net: tsnep: Fix typo on generic nvmem property
- net:

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

2022-12-12 Thread Martin Schreiber

** Information type changed from Public to Public Security

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

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

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


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

Re: [Kernel-packages] [Bug 1998673] Re: [amdgpu] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working

2022-12-12 Thread Michael K

No, my BIOS version is K5CN34WW
Do you have exactly the same computer model (Yoga 7 14ARB7)?
Do you have exactly the same Lenovo TB Dock?

12.12.2022 19:05:22 Steven Hong <1998...@bugs.launchpad.net>:

> I have same issue like u. did you update your bios?
> I have same issue after updating my BIOS.
> 
> Used so well until bios updates.
> 
> The bios Code is : JVEC31WW
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1998673
> 
> Title:
>   [amdgpu] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not
>   working
> 
> Status in linux package in Ubuntu:
>   Confirmed
> 
> Bug description:
>   I have a Lenovo Yoga 7 Gen 7 (14ARB7) with AMD Ryzen 7 6800U CPU, with
>   integrated AMD Radeon Graphics and USB4. I know this is quite new
>   hardware, but I am astonished that many things work right out of the
>   box.
> 
>   Ubuntu 22.04 with Mainline Kernel Linux 6.0.9-060009-generic 
> #202211170559-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 17 06:06:21 UTC x86_64 
> x86_64 x86_64 GNU/Linux
>   Did some cross checks with Kernel 5.15.0-56 (stable)
>   Monitor Samsung U32R592CWU UHD 4K (3.840 x 2.160 Pixel, VA-Panel, 16:9 
> Format, 60 Hz, 4ms)
> 
>   What I have issues with (In this issue I'll only report on topic 1):
> 
>   1) External Monitor
>   2) Touchscreen not working after suspend by closing lid; suspend only works 
> once
>   3) Integrated keyboard only works with Kernel 6 (Mainline) (kind of solved)
> 
>   I tested multiple ways connecting external monitors, each of them only 
> working to some extent:
>   i) directly via HDMI port of Notebook
>   ii) via Lenovo Thinkpad Thunderbolt 3 Dock 40AC DisplayPort or HDMI 
> (preferred solution)
>   iii) via an Razer Core X eGPU with Radeon RX570 DisplayPort or HDMI
> 
>   Problems/Observations:
>   1) DP/HDMI via Dock mostly not working (exception see point 3). USB via 
> Dock works however.
>   2) Booting with HDMI connected to Dock on Kernel 6 stalls. When unplugging 
> the monitor the boot process immediately resumes successfully.
>   3) Booting with HDMI connected to Dock on Kernel 5 brings up the screen, 
> after that Hot Plug is also working, even DP
>   4) Booting with DP connected to Dock on Kernel 5 does not bring up the 
> screen, neither after Hot-Plug of HDMI or DP
>   5) Booting without Monitor connected on Kernel 5 does not bring up the 
> screen on Hot Plug, neither HDMI nor DP
>   6) Hot Plugging the monitors (way i and iii) sometimes freezes the system, 
> needs hard reset.
>   7) Turning off or disconnecting TB cable of eGPU may also cause a freeze 
> (as this also disconnects the monitor it may have the same cause as 2)
> 
>   So to sum it up: External Screens via this Docking Stations is only
>   working on Kernel 5 when the monitor is connected via HDMI during
>   boot, but not in any other case.
> 
>   Side observations:
>   1) The USB devices connected to the TB3 Dock come up very slowly after hot 
> plugging the TB3 connector to the Notebook.
>   2) Mouse cursor (external mouse connected to Dock) hangs from time to time 
> on Kernel 5.
> 
>   Please notify me if you need further logs. The automatically collected
>   logs were captured in situation 2 above. You'll see the gap in the
>   timestamps of th DMESG output.
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: xorg 1:7.7+23ubuntu2
>   Uname: Linux 6.0.9-060009-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.2
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
>   CasperMD5CheckResult: pass
>   CompositorRunning: None
>   CurrentDesktop: MATE
>   Date: Sat Dec  3 18:10:13 2022
>   DistUpgraded: Fresh install
>   DistroCodename: jammy
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>    Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev c1) 
> (prog-if 00 [VGA controller])
>  Subsystem: Lenovo Device [17aa:3801]
>   InstallationDate: Installed on 2022-11-23 (9 days ago)
>   InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release 
> amd64 (20220809.1)
>   MachineType: LENOVO 82QF
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.9-060009-generic 
> root=UUID=3031ba9e-0a88-4dc4-8cb6-65fab38e8fda ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/19/2022
>   dmi.bios.release: 1.34
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: K5CN34WW
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: LNVNB161216
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0T76461 WIN
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 31
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Yoga 7 14ARB7
>   dmi.ec.firmware.release: 1.34
>   dmi.modalias: 
>

[Kernel-packages] [Bug 1998673] Re: [amdgpu] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working

2022-12-12 Thread Steven Hong

I have same issue like u. did you update your bios? 
I have same issue after updating my BIOS.

Used so well until bios updates.

The bios Code is : JVEC31WW

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

Title:
  [amdgpu] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo Yoga 7 Gen 7 (14ARB7) with AMD Ryzen 7 6800U CPU, with
  integrated AMD Radeon Graphics and USB4. I know this is quite new
  hardware, but I am astonished that many things work right out of the
  box.

  Ubuntu 22.04 with Mainline Kernel Linux 6.0.9-060009-generic 
#202211170559-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 17 06:06:21 UTC x86_64 x86_64 
x86_64 GNU/Linux
  Did some cross checks with Kernel 5.15.0-56 (stable)
  Monitor Samsung U32R592CWU UHD 4K (3.840 x 2.160 Pixel, VA-Panel, 16:9 
Format, 60 Hz, 4ms)

  What I have issues with (In this issue I'll only report on topic 1):

  1) External Monitor
  2) Touchscreen not working after suspend by closing lid; suspend only works 
once
  3) Integrated keyboard only works with Kernel 6 (Mainline) (kind of solved)

  I tested multiple ways connecting external monitors, each of them only 
working to some extent:
  i) directly via HDMI port of Notebook
  ii) via Lenovo Thinkpad Thunderbolt 3 Dock 40AC DisplayPort or HDMI 
(preferred solution)
  iii) via an Razer Core X eGPU with Radeon RX570 DisplayPort or HDMI

  Problems/Observations:
  1) DP/HDMI via Dock mostly not working (exception see point 3). USB via Dock 
works however.
  2) Booting with HDMI connected to Dock on Kernel 6 stalls. When unplugging 
the monitor the boot process immediately resumes successfully.
  3) Booting with HDMI connected to Dock on Kernel 5 brings up the screen, 
after that Hot Plug is also working, even DP
  4) Booting with DP connected to Dock on Kernel 5 does not bring up the 
screen, neither after Hot-Plug of HDMI or DP
  5) Booting without Monitor connected on Kernel 5 does not bring up the screen 
on Hot Plug, neither HDMI nor DP
  6) Hot Plugging the monitors (way i and iii) sometimes freezes the system, 
needs hard reset.
  7) Turning off or disconnecting TB cable of eGPU may also cause a freeze (as 
this also disconnects the monitor it may have the same cause as 2)

  So to sum it up: External Screens via this Docking Stations is only
  working on Kernel 5 when the monitor is connected via HDMI during
  boot, but not in any other case.

  Side observations:
  1) The USB devices connected to the TB3 Dock come up very slowly after hot 
plugging the TB3 connector to the Notebook.
  2) Mouse cursor (external mouse connected to Dock) hangs from time to time on 
Kernel 5.

  Please notify me if you need further logs. The automatically collected
  logs were captured in situation 2 above. You'll see the gap in the
  timestamps of th DMESG output.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  Uname: Linux 6.0.9-060009-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sat Dec  3 18:10:13 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev c1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2022-11-23 (9 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 82QF
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.9-060009-generic 
root=UUID=3031ba9e-0a88-4dc4-8cb6-65fab38e8fda ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2022
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: K5CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 7 14ARB7
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrK5CN34WW:bd08/19/2022:br1.34:efr1.34:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7:
  dmi.product.family: Yoga 7 14ARB7
  dmi.product.name: 82QF
  dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7
  dmi.product.version: Yoga 7 14ARB7
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1

[Kernel-packages] [Bug 1758942] Re: [i915_bpo] écran noir au démarrage

2022-12-12 Thread Paul White

Thank you for your reply to my comment #3. Your English is good enough
foe me.

Unfortunately Ubuntu has never had enough users, volunteers or
developers that have had the time to respond to bug reports in a timely
manner.

I'm closing this as 'Invalid' which doesn't mean that your initial
report is irrelevant but that there is insufficient information to keep
this bug report open.

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [i915_bpo] écran noir au démarrage

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

Bug description:
  écran noir, impossible de rentrer mon mot de passe au démarrage,
  lecteur video ne fonctionne pas, impossible de supprimer des
  logiciels, plantage en cours de session

  Google translation:
  black screen, impossible to enter my password at startup, video player does 
not work, impossible to delete software, crash during the session

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 26 16:53:16 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
     Subsystem: Dell Skylake Integrated Graphics [1028:078c]
  InstallationDate: Installed on 2018-03-15 (11 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 15-3567
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=fbcd4cac-8cb9-4527-af8f-a07d69322204 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Mar 26 16:32:28 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5574
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

2022-12-12 Thread Ubuntu SRU Bot

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

linux-nvidia/5.15.0-1011.11 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-nvidia

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

Re: [Kernel-packages] [Bug 1758942] Re: [i915_bpo] écran noir au démarrage

2022-12-12 Thread pieniazek lionel

I don't use Ubuntu anymore, i did not have no answer and helping solution
at this moment, too Bad cause i like using Ubuntu but so disapointed !
Thanks for this answer anyway, a little bit late.(Hope my english is
correct)
Cordialement

Le lun. 12 déc. 2022 à 15:16, Paul White <1758...@bugs.launchpad.net> a
écrit :

> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
>
> Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
>
> Do you still see a problem related to the one that you reported when
> using a currently supported version of Ubuntu? Please let us know if you
> do otherwise this report can be left to expire in approximately 60 days
> time.
>
> Thank you for helping make Ubuntu better.
>
>
> ** Description changed:
>
>   écran noir, impossible de rentrer mon mot de passe au démarrage, lecteur
>   video ne fonctionne pas, impossible de supprimer des logiciels, plantage
>   en cours de session
> +
> + Google translation:
> + black screen, impossible to enter my password at startup, video player
> does not work, impossible to delete software, crash during the session
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
>   Uname: Linux 4.4.0-116-generic x86_64
>   .tmp.unity_support_test.0:
> -
> +
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Mon Mar 26 16:53:16 2018
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
> -  # This is a distribution channel descriptor
> -  # For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
> -  canonical-oem-somerville-xenial-amd64-20160624-2
> +  # This is a distribution channel descriptor
> +  # For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
> +  canonical-oem-somerville-xenial-amd64-20160624-2
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
> -  Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)
> (prog-if 00 [VGA controller])
> -Subsystem: Dell Skylake Integrated Graphics [1028:078c]
> +  Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)
> (prog-if 00 [VGA controller])
> +Subsystem: Dell Skylake Integrated Graphics [1028:078c]
>   InstallationDate: Installed on 2018-03-15 (11 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
> 20160624-10:47
>   MachineType: Dell Inc. Inspiron 15-3567
>   ProcEnviron:
> -  LANGUAGE=fr_FR
> -  PATH=(custom, no user)
> -  LANG=fr_FR.UTF-8
> -  SHELL=/bin/bash
> +  LANGUAGE=fr_FR
> +  PATH=(custom, no user)
> +  LANG=fr_FR.UTF-8
> +  SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed
> root=UUID=fbcd4cac-8cb9-4527-af8f-a07d69322204 ro quiet splash
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/25/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 2.0.3
>   dmi.board.name: 0FGN4M
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 15-3567
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.83-1~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Mon Mar 26 16:32:28 2018
>   xserver.configfile: default
>   xserver.errors:
> -
> +
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
> -  product id5574
> -  vendor CMN
> +  product id5574
> +  vendor CMN
>   xserver.version: 2:1.18.4-0ubuntu0.7
>
> ** Changed in: linux

[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org

2022-12-12 Thread Jeff Lane 

Thanks, Don... sorry to ask but to make this easier on me (I'm the one
who has to find the time do do this) could you revise the list in the
summary with all the desired patches (including the ones from the 6.2
MKP tree) in pick order?

And just to be sure, they all cleanly pick with no missing prerequisites
or conflicts?

I will have to sort out what to pick for each affected kernel, as I will
have to pull them back from 6.2 -> 5.19.

Also, Gerry said the target was 20.04.2, so that means the 5.19 HWE
kernel, yes?

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

Title:
  smartpqi: Update 22.04 driver to latest kernel.org

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There are some outstanding patches already in Linus's tree that can be 
applied to 22.04.
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  The following patches apply to
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

  f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
  e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
  6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
  2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
  cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
  6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
  69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
  85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
  2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
  44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
  331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
  904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
  297bdc540f0e scsi: smartpqi: Close write read holes
  dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
  1d393227fc76 scsi: smartpqi: Add controller fw version to console log
  4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
  8946ea283808 scsi: smartpqi: Fix typo in comment
  c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
  31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
  62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
  291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
  c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
  5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
  c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
  00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
  5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
  27655e9db479 scsi: smartpqi: Update volume size after expansion
  b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
  42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
  9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
  b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
  94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
  70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
  2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
  c57ee4ccb358 scsi: smartpqi: Add PCI IDs
  c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
  64fc9015fbeb scsi: smartpqi: Switch to attribute groups
  0ca190805784 scsi: smartpqi: Call scsi_done() directly

  I added the above SHA1 IDs to a file called:
  backport_linus_6.1_into_22.04

  git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
  git am -s /tmp/patches/*.diff

  All patches applied without any conflicts.

  [impact]
  This patches correct some bugs and add support for more PCI devices. Also, 
the in-box driver is largely out-of-date with kernel.org.

  [fix]
  Applying these patches (along with the patches noted below) bring smartpqi up 
to date with our OOB driver and kernel.org. Both have been tested.
  [Test Plan] Our OOB driver has undergone extensive testing by our test team.

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


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

[Kernel-packages] [Bug 1993539] Re: Nvidia GeForce GTX 560 M not recognized as an OpenCL platform with 5.15.0-50 kernel

2022-12-12 Thread Michel NALLINO

Hi,

I found a workaround to this problem. I solved the problem by installing new 
packages:
"sudo apt install linux-modules-nvidia-390-5.15.0-56-generic"
where:
- "390" is the main version of the Nvidia driver (390.157);
- "5.15.0-56-generic" is the name of the kernel ("uname -r" output).

This induced the installation of the following packages: “linux-modules-
nvidia-390-5.15.0-56-generic”, “linux-objects-
nvidia-390-5.15.0-56-generic”, “linux-signatures-
nvidia-390-5.15.0-56-generic”.

LibreOffice now detects OpenCL; and clinfo output with 5.15.0-56 kernel shows 
GTX 560 M is detected as an OpenCL platform:
"clinfo
Number of platforms   1
  Platform Name   NVIDIA CUDA
  Platform Vendor NVIDIA Corporation
  Platform VersionOpenCL 1.2 CUDA 9.1.84
  Platform ProfileFULL_PROFILE
  Platform Extensions 
cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics 
cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 
cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing 
cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll 
cl_nv_copy_opts cl_nv_create_buffer
  Platform Extensions function suffix NV

  Platform Name   NVIDIA CUDA
Number of devices 1
  Device Name GeForce GTX 560M
[...]"

See discussion on Linux Mint forum: 
https://forums.linuxmint.com/viewtopic.php?f=59=383809=2268764#p2268764
and on Nvidia developers forum: 
https://forums.developer.nvidia.com/t/nvidia-geforce-gtx-560-m-not-recognized-as-an-opencl-platform-with-ubuntu-hwe-5-15/236672

Regards,

MN

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

Title:
  Nvidia GeForce GTX 560 M not recognized as an OpenCL platform with
  5.15.0-50 kernel

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

Bug description:
  Hi,

  Before to update to Linux Mint 21, based on Ubuntu 22.04 LTS, I have
  tried 5.15.0-50 kernel with HWE. This was intended as a test of my
  hardware compatibility with the hardware stack of Ubuntu 22.04, before
  a possible update.

  At a first glance, all seemed OK; nut I noticed that LibreOffice was
  unable to use OpenCL. A simple "clinfo" command confirmed this:

    $ clinfo
    Number of platforms   0

  I went back from 5.15.0-50 kernel to 5.4.0-128 one. Now, "clinfo"
  output is:

    $ clinfo
    Number of platforms   1
  Platform Name   NVIDIA CUDA
  Platform Vendor NVIDIA Corporation
  Platform VersionOpenCL 1.2 CUDA 9.1.84
  Platform ProfileFULL_PROFILE
  Platform Extensions 
cl_khr_global_int32_base_atomics
    cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics
    cl_khr_local_int32_extended_atomics cl_khr_fp64 
cl_khr_byte_addressable_store cl_khr_icd
    cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query 
cl_nv_pragma_unroll
    cl_nv_copy_opts cl_nv_create_buffer
  Platform Extensions function suffix NV
  Platform Name   NVIDIA CUDA
    Number of devices 1
  Device Name GeForce GTX 560M
  Device Vendor   NVIDIA Corporation
  Device Vendor ID0x10de
  Device Version  OpenCL 1.1 CUDA
  Driver Version  390.154
  Device OpenCL C Version OpenCL C 1.1
  Device Type GPU
  Device Topology (NV)PCI-E, 01:00.0
  Device Profile  FULL_PROFILE
  Device AvailableYes
  Compiler Available  Yes
  Max compute units   4
  Max clock frequency 1550MHz
  Compute Capability (NV) 2.1
  Max work item dimensions3
  Max work item sizes 1024x1024x64
  Max work group size 1024
  Preferred work group size multiple  32
  Warp size (NV)  32
  Preferred / native vector sizes
    char 1 / 1
    short1 / 1

[Kernel-packages] [Bug 1999387] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635411/+files/ProcModules.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon

[Kernel-packages] [Bug 1999387] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635415/+files/WifiSyslog.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease:

[Kernel-packages] [Bug 1999387] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1999387/+attachment/5635413/+files/RfKill.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux

[Kernel-packages] [Bug 1999387] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635416/+files/acpidump.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease:

[Kernel-packages] [Bug 1999387] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635412/+files/PulseList.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease:

[Kernel-packages] [Bug 1999387] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1999387/+attachment/5635414/+files/UdevDb.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux

[Kernel-packages] [Bug 1999387] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635410/+files/ProcInterrupts.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon

[Kernel-packages] [Bug 1999387] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon

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

apport information

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

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon

[Kernel-packages] [Bug 1999387] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635407/+files/ProcCpuinfo.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon

[Kernel-packages] [Bug 1999387] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635406/+files/Lsusb-v.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux

[Kernel-packages] [Bug 1999387] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1999387/+attachment/5635404/+files/Lsusb.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint

[Kernel-packages] [Bug 1999387] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635405/+files/Lsusb-t.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux

[Kernel-packages] [Bug 1999387] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635403/+files/Lspci-vt.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease:

[Kernel-packages] [Bug 1999387] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635401/+files/IwConfig.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease:

[Kernel-packages] [Bug 1999387] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1999387/+attachment/5635402/+files/Lspci.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint

[Kernel-packages] [Bug 1999387] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1999387/+attachment/5635400/+files/CurrentDmesg.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon

[Kernel-packages] [Bug 1999387] Re: Bluetooth crashes on kernel 5.4.0-135

apport information

** Tags added: apport-collected una

** Description changed:

  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.25
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dennis 6105 F pulseaudio
+  /dev/snd/controlC1:  dennis 6105 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 20.3
+ InstallationDate: Installed on 2022-03-17 (269 days ago)
+ InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
+ MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
+ ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-135-generic N/A
+  linux-backports-modules-5.4.0-135-generic  N/A
+  linux-firmware 1.187.35
+ Tags:  una
+ Uname: Linux 5.4.0-135-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/12/2022
+ dmi.bios.vendor: American Megatrends International, LLC.
+ dmi.bios.version: F36c
+ dmi.board.asset.tag: Default string
+ dmi.board.name: X570 AORUS ULTRA
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: Default string
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: X570 MB
+ dmi.product.name: X570 AORUS ULTRA
+ dmi.product.sku: Default string
+ dmi.product.version: -CF
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Description changed:

  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.25
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dennis 6105 F pulseaudio
+  /dev/snd/controlC1:  dennis 6105 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 20.3
+ InstallationDate: Installed on 2022-03-17 (269 days ago)
+ InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
+ MachineType: Gigabyte

[Kernel-packages] [Bug 1999387] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1999387/+attachment/5635399/+files/CRDA.txt

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-03-17 (269 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-135-generic 
root=UUID=6bf95fbe-10a5-4660-84fb-b83fbdeb0ba0 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-135-generic N/A
   linux-backports-modules-5.4.0-135-generic  N/A
   linux-firmware 1.187.35
  Tags:  una
  Uname: Linux 5.4.0-135-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2022
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 6105 F pulseaudio
   /dev/snd/controlC1:  dennis 6105 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint

[Kernel-packages] [Bug 1999406] [NEW] Update firmware for hwe kernel migration

2022-12-12 Thread You-Sheng Yang

Public bug reported:

TBD.

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

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

Title:
  Update firmware for hwe kernel migration

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  TBD.

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


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

[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855

2022-12-12 Thread AaronMa

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

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

Title:
  Fix ath11k deadlock on WCN6855

Status in HWE Next:
  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 source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  ath11k is in deadlock when stress reboot or suspend on WCN6855.
  sometimes kernel hang.

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

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


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

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

2022-12-12 Thread AaronMa

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

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

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

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

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

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

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

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

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

  On 5.17 kernel, revert it by upstream commit.

  Unstable kernel already got it.

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

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

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

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

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


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

[Kernel-packages] [Bug 1999387] Re: Bluetooth crashes on kernel 5.4.0-135

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

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

Title:
  Bluetooth  crashes on kernel 5.4.0-135

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth-app crashes when i try to active bluetooth inside the application.
  Using app: "blueman-manager".
  Last kernel working: 5.4.0-132

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


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

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

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

apport-collect 1999396

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

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

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

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

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

Title:
  pnvm firmware files undeclared

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At the moment fallback pnvm firmware files exists, but are undeclared.

  Ensure that if ucode for such devices is copied, that pnvm files are
  copied too.

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


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

[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32

2022-12-12 Thread Ghadi Rahme

** Changed in: zfs-linux (Ubuntu Focal)
 Assignee: Heitor Alves de Siqueira (halves) => Ghadi Rahme (ghadi-rahme)

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

Title:
  ZFS ignores ARC sizes below allmem/32

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. 
This prevents users from properly restraining ARC sizes, and can cause 
increased memory contention in some systems.

  [Test Plan]
  1. Deploy test system with ZFS storage and 32GB RAM
  2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf
     # cat /etc/modprobe.d/99-zfs-arc.conf
     options zfs zfs_arc_min=536870912
     options zfs zfs_arc_max=966367641
  3. Reboot system
  4. Verify ARC sizes through "arc_summary"
     # arc_summary | grep -A3 "ARC size"
     ARC size (current):   < 0.1 %1.3 MiB
     Target size (adaptive):   100.0 %   15.7 GiB
     Min size (hard limit):  3.2 %  512.0 MiB
     Max size (high water):   31:1   15.7 GiB

  For a 32GB test system, we should be able to set max ARC sizes below
  1GB.

  [Fix]
  This has been fixed by upstream commit:
   - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32"

  The commit has been introduced in upstream zfs-2.0.0, so it's needed
  for Bionic and Focal. Releases starting with Impish already have this
  commit by default:

  $ git describe --contains 36a6e2335c45
  zfs-2.0.0-rc1~332
  $ rmadison zfs-linux
   zfs-linux | 0.7.5-1ubuntu15| bionic  | source
   zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates  | source
   zfs-linux | 0.8.3-1ubuntu12| focal   | source
   zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
   zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates   | source
   zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed  | source
   zfs-linux | 2.0.6-1ubuntu2 | impish  | source
   zfs-linux | 2.0.6-1ubuntu2.1   | impish-updates  | source
   zfs-linux | 2.1.2-1ubuntu3 | jammy   | source

  [Regression Potential]
  The introduced commit essentially removes the limitation of setting ARC 
tunables below allmem/32, and re-arranges the order of how some of the tunables 
are parsed. Regressions would possibly show up as other tunables being ignored 
or not being set correctly due to parsing errors. We should validate whether 
other ARC related tunables are still being set correctly, and whether ZFS is 
using the set values for the ARC memory thresholds.

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


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

[Kernel-packages] [Bug 1758942] Re: [i915_bpo] écran noir au démarrage

2022-12-12 Thread Paul White

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** Description changed:

  écran noir, impossible de rentrer mon mot de passe au démarrage, lecteur
  video ne fonctionne pas, impossible de supprimer des logiciels, plantage
  en cours de session
+ 
+ Google translation:
+ black screen, impossible to enter my password at startup, video player does 
not work, impossible to delete software, crash during the session
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 26 16:53:16 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-xenial-amd64-20160624-2
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
-Subsystem: Dell Skylake Integrated Graphics [1028:078c]
+  Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
+    Subsystem: Dell Skylake Integrated Graphics [1028:078c]
  InstallationDate: Installed on 2018-03-15 (11 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 15-3567
  ProcEnviron:
-  LANGUAGE=fr_FR
-  PATH=(custom, no user)
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=fr_FR
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=fbcd4cac-8cb9-4527-af8f-a07d69322204 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Mar 26 16:32:28 2018
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5574 
-  vendor CMN
+  product id5574
+  vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.7

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  [i915_bpo] écran noir au démarrage

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

Bug description:
  écran noir, impossible de rentrer mon mot de passe au démarrage,

[Kernel-packages] [Bug 1997472] Re: Touchpad problem detecting working area on Dell XPS

2022-12-12 Thread florin

Here it is:

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product= Version=
N: Name="Intel HID events"
P: Phys=
S: Sysfs=/devices/platform/INTC1070:00/input/input11
U: Uniq=
H: Handlers=rfkill kbd event9 
B: PROP=0
B: EV=13
B: KEY=810003 504000 1e29400020 0
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="Intel HID 5 button array"
P: Phys=
S: Sysfs=/devices/platform/INTC1070:00/input/input12
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=13
B: KEY=2 0 0 0 0 1 0 201c 0
B: MSC=10

I: Bus=0018 Vendor=04f3 Product=2a15 Version=0100
N: Name="ELAN2097:00 04F3:2A15"
P: Phys=i2c-ELAN2097:00
S: 
Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN2097:00/0018:04F3:2A15.0001/input/input13
U: Uniq=
H: Handlers=mouse0 event4 
B: PROP=2
B: EV=1b
B: KEY=400 0 0 0 0 0
B: ABS=32738003
B: MSC=20

I: Bus=0018 Vendor=04f3 Product=2a15 Version=0100
N: Name="ELAN2097:00 04F3:2A15 UNKNOWN"
P: Phys=i2c-ELAN2097:00
S: 
Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN2097:00/0018:04F3:2A15.0001/input/input14
U: Uniq=
H: Handlers=event5 
B: PROP=0
B: EV=9
B: ABS=100

I: Bus=0018 Vendor=04f3 Product=2a15 Version=0100
N: Name="ELAN2097:00 04F3:2A15 UNKNOWN"
P: Phys=i2c-ELAN2097:00
S: 
Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN2097:00/0018:04F3:2A15.0001/input/input15
U: Uniq=
H: Handlers=event6 
B: PROP=0
B: EV=11

I: Bus=0019 Vendor= Product= Version=
N: Name="Dell Privacy Driver"
P: Phys=
S: 
Sysfs=/devices/platform/PNP0C14:02/wmi_bus/wmi_bus-PNP0C14:02/6932965F-1671-4CEB-B988-D3AB0A901919/input/input17
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=33
B: KEY=101 0 0 0
B: MSC=10
B: SW=200

I: Bus=0003 Vendor=0c45 Product=6732 Version=1461
N: Name="Integrated_Webcam_HD: Integrate"
P: Phys=usb-:00:14.0-6/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/input/input18
U: Uniq=
H: Handlers=kbd event8 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0019 Vendor= Product= Version=
N: Name="Dell WMI hotkeys"
P: Phys=
S: 
Sysfs=/devices/platform/PNP0C14:02/wmi_bus/wmi_bus-PNP0C14:02/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input19
U: Uniq=
H: Handlers=rfkill kbd event11 
B: PROP=0
B: EV=13
B: KEY=8000 0 0 1500b0c00 40020030 e 0
B: MSC=10

I: Bus=0003 Vendor=0c45 Product=6732 Version=1461
N: Name="Integrated_Webcam_HD: Integrate"
P: Phys=usb-:00:14.0-6/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.2/input/input20
U: Uniq=
H: Handlers=kbd event12 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0018 Vendor=06cb Product=ce7e Version=0100
N: Name="VEN_06CB:00 06CB:CE7E Mouse"
P: Phys=i2c-VEN_06CB:00
S: 
Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-VEN_06CB:00/0018:06CB:CE7E.0002/input/input21
U: Uniq=
H: Handlers=mouse1 event13 
B: PROP=0
B: EV=17
B: KEY=3 0 0 0 0
B: REL=3
B: MSC=10

I: Bus=0018 Vendor=06cb Product=ce7e Version=0100
N: Name="VEN_06CB:00 06CB:CE7E Touchpad"
P: Phys=i2c-VEN_06CB:00
S: 
Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-VEN_06CB:00/0018:06CB:CE7E.0002/input/input22
U: Uniq=
H: Handlers=mouse2 event14 
B: PROP=5
B: EV=1b
B: KEY=e520 1 0 0 0 0
B: ABS=2e08003
B: MSC=20

I: Bus= Vendor= Product= Version=
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input24
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA NVidia HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input25
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S:

[Kernel-packages] [Bug 1999396] [NEW] pnvm firmware files undeclared

2022-12-12 Thread Dimitri John Ledkov

Public bug reported:

At the moment fallback pnvm firmware files exists, but are undeclared.

Ensure that if ucode for such devices is copied, that pnvm files are
copied too.

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

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

Title:
  pnvm firmware files undeclared

Status in linux package in Ubuntu:
  New

Bug description:
  At the moment fallback pnvm firmware files exists, but are undeclared.

  Ensure that if ucode for such devices is copied, that pnvm files are
  copied too.

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


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

[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

2022-12-12 Thread mobi

The "Kinetic Ubuntu 22.10" version is also affected.

Backport from fix from comment #33 above? (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/comments/33
)

Please someone who has permission could you please add Kinect as
affected and backport the fix? (google translated)


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.10
Release:22.10
Codename:   kinetic


$ dmesg
[0.00] Linux version 5.19.0-26-generic (buildd@lcy02-amd64-064) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-3ubuntu1) 12.2.0, GNU ld (GNU Binutils 
for Ubuntu) 2.39) #27-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 23 20:44:15 UTC 2022 
(Ubuntu 5.19.0-26.27-generic 5.19.7)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=UUID=5e0045ff-af35-44d7-9627-375f9c38f04b ro debug verbose zswap.enabled=1 
kernel.dmesg_restrict=0
[0.00] KERNEL supported cpus:

[...]

[1.970929] forcedeth: Reverse Engineered nForce ethernet driver. Version 
0.64.
[1.974948] ACPI: \_SB_.LMAC: Enabled at IRQ 23
[1.980418] scsi host0: pata_amd
[1.984037] ahci :00:09.0: version 3.0
[1.987817] ACPI: \_SB_.LSA0: Enabled at IRQ 22
[1.993080] ahci :00:09.0: controller can't do PMP, turning off CAP_PMP
[1.997510] scsi host1: pata_amd
[2.001022] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[2.004572] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[2.008363] ahci :00:09.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0xf 
impl IDE mode
[2.011924] ahci :00:09.0: flags: 64bit ncq sntf led clo pio boh 
[2.020446] scsi host2: ahci
[2.028066] scsi host3: ahci
[2.031849] scsi host4: ahci
[2.036045] scsi host5: ahci
[2.039550] scsi host6: ahci
[2.042923] scsi host7: ahci
[2.046161] ata3: SATA max UDMA/133 abar m8192@0xfbd76000 port 0xfbd76100 
irq 25
[2.049439] ata4: SATA max UDMA/133 abar m8192@0xfbd76000 port 0xfbd76180 
irq 25
[2.052707] ata5: SATA max UDMA/133 abar m8192@0xfbd76000 port 0xfbd76200 
irq 25
[2.055964] ata6: SATA max UDMA/133 abar m8192@0xfbd76000 port 0xfbd76280 
irq 25
[2.059214] ata7: DUMMY
[2.062446] ata8: DUMMY
[2.066781] forcedeth :00:0a.0: ifname eth0, PHY OUI 0x732 @ 3, addr 
90:e6:ba:7c:6e:0b
[2.070154] forcedeth :00:0a.0: highdma csum pwrctl mgmt gbit lnktim msi 
desc-v3
[2.073884] ahci :03:00.0: SSS flag set, parallel bus scan disabled
[2.077385] ahci :03:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 
impl IDE mode
[2.080820] ahci :03:00.0: flags: 64bit ncq sntf stag led clo pmp pio 
slum part ccc sxs 
[2.084840] scsi host8: ahci
[2.088504] scsi host9: ahci
[2.092002] ata9: SATA max UDMA/133 abar m512@0xfbfffc00 port 0xfbfffd00 irq 
26
[2.095432] ata10: SATA max UDMA/133 abar m512@0xfbfffc00 port 0xfbfffd80 
irq 26
[2.131689] usb 3-1: New USB device found, idVendor=03f0, idProduct=034a, 
bcdDevice= 1.21
[2.135300] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[2.138833] usb 3-1: Product: HP Elite USB Keyboard
[2.139693] usb 4-1: New USB device found, idVendor=03f0, idProduct=1198, 
bcdDevice= 7.04
[2.142341] usb 3-1: Manufacturer: Chicony
[2.149360] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[2.152946] usb 4-1: Product: HP USB 1000dpi Laser Mouse
[2.156475] usb 4-1: Manufacturer: HP
[2.161666] hid: raw HID events driver (C) Jiri Kosina
[2.215911] usbcore: registered new interface driver usbhid
[2.219667] usbhid: USB HID core driver
[2.381945] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[2.390289] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[2.399061] ata5: SATA link down (SStatus 0 SControl 300)
[2.407325] ata3: SATA link down (SStatus 0 SControl 300)
[2.415502] ata4.00: ATA-9: SATA3 240GB SSD, T0707B0, max UDMA/133
[2.424371] ata4.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32)
[2.434698] ata6.00: ATA-9: KingDian S400 120GB, Q1115A0, max UDMA/133
[2.443235] ata6.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 32)
[2.452933] ata4.00: configured for UDMA/133
[2.462504] scsi 3:0:0:0: Direct-Access ATA  SATA3 240GB SSD  7B0  
PQ: 0 ANSI: 5
[2.466643] ata6.00: configured for UDMA/133
[2.471984] scsi 3:0:0:0: Attached scsi generic sg0 type 0
[2.472586] sd 3:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/224 
GiB)
[2.472630] sd 3:0:0:0: [sda] Write Protect is off
[2.472638] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
[2.472696] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[2.472731] sd 3:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[2.526709] scsi 5:0:0:0: Direct-Access ATA  KingDian S400 12 5A0  
PQ: 0 ANSI: 5
[2.530967] sd 5:0:0:0: Attached scsi generic sg1 type 0
[2.531321] sd 5:0:0:0: [sdb] 234441648

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

2022-12-12 Thread bugproxy

--- Comment From sig...@de.ibm.com 2022-12-12 08:36 EDT---
still fine with latest updates:

# uname -a
Linux a83lp78.lnxne.boe 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:57:26 
UTC 2022 s390x s390x s390x GNU/Linux
# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii  | wc -l
0
# ethtool encbd00 | grep Duplex
Duplex: Full
# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii  | wc -l
0

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

Title:
  [UBUNTU 22.04] s390/qeth: cache link_info for ethtool

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  == SRU Justification ==
  Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is 
offline") there was a timing window during recovery, that qeth_query_card_info 
could be   sent to the card, even before it was ready for it, leading to a 
failing cardrecovery. There is evidence that this window was hit, as not 
all callers of get_link_ksettings() check for netif_device_present.

  This patch (Mainline commit 7a07a29e4f67) fixes the regression caused
  by commit e6e771b3d897.

  Commit 7a07a29e4f67 is in mainline as of v6.0-rc1.

  This patch is being requested in Jammy 5.15 and Kinetic 5.19.

  == Fix ==
  7a07a29e4f67 ("s390/qeth: cache link_info for ethtool")

  == Regression Potential ==
  Low.  This patch has been accepted in upstream stable and is limited to
  the s390/qeth card.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  == Comment: #0 - J?rn Siglen  - 2022-08-09 07:38:27 ==
  +++ This bug was initially created as a clone of Bug #199319 +++

  Description:   s390/qeth: cache link_info for ethtool
  Symptom:   lost of IP connection and log entries in journalctl:
    kernel: qeth 0.0.0365: The qeth device driver failed to
    recover an error on the device
  Problem:   Since commit e6e771b3d897
   ("s390/qeth: detach netdevice while card is offline")
     there was a timing window during recovery, that
     qeth_query_card_info could be sent to the card, even before it
     was ready for it, leading to a failing card recovery. There is
     evidence that this window was hit, as not all callers of
     get_link_ksettings() check for netif_device_present.
  Solution:  Use cached values in qeth_get_link_ksettings(), instead of
     calling qeth_query_card_info() and falling back to default
     values in case it fails. Link info is already updated when the
     card goes online, e.g. after STARTLAN (physical link up). Set
     the link info to default values, when the card goes offline or
     at STOPLAN (physical link down). A follow-on patch will improve
     values reported for link down.
     Fixes: e6e771b3d897
     ("s390/qeth: detach netdevice while card is offline")
  Reproduction:  enforce a eth device recvoery, while running ethtool multiple
     times in parallel and using iperf to get load on the interface.
  Upstream-ID:   7a07a29e4f6713b224f3bcde5f835e777301bdb8

  
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

  applicable for most kernel > 3.14

  == Comment: #3 - J?rn Siglen  - 2022-08-09 07:54:41 ==
  the inital update came in with kernel 5.1 upstream, but we found it 
backported in many older kernel versions

  == Comment: #4 - J?rn Siglen  - 2022-08-09 08:03:09 ==
  the acceptance info of the patch can be found here:
  
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

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


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

[Kernel-packages] [Bug 1998841] Re: firmware blob in missing pc-kernel 22/stable of Ubuntu Core22

2022-12-12 Thread Dimitri John Ledkov

2022-12-12 13:37:30.762 :: 2022-12-12 13:36:02.048 :: + 
/root/parts/kernel/src/trim-firmware /root/parts/kernel/install/lib
2022-12-12 13:37:30.762 :: 2022-12-12 13:36:13.710 :: Overriding 
iwlwifi-so-a0-gf-a0-66.ucode with iwlwifi-so-a0-gf-a0-64.ucode
2022-12-12 13:37:30.762 :: 2022-12-12 13:36:13.716 :: Overriding 
iwlwifi-so-a0-hr-b0-66.ucode with iwlwifi-so-a0-hr-b0-64.ucode
2022-12-12 13:37:30.762 :: 2022-12-12 13:36:13.723 :: Overriding 
iwlwifi-so-a0-jf-b0-66.ucode with iwlwifi-so-a0-jf-b0-64.ucode

Having some progress to fix this.

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  firmware blob in missing pc-kernel 22/stable of Ubuntu Core22

Status in linux package in Ubuntu:
  In Progress

Bug description:
We are building an application in our private brand store.  While trying to 
use
  the pc-kernel 22/stable our wifi networking does not work.  The same hardware 
(a Dell 5570) works well on Desktop 22.04.

Thee issue seems to be a missing firmware blob to enable the wifi
  networking.  Ubuntu desktop 22.04 loads the following firmware blob.

  lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode

  
  Please add this firmware blob to pc-kernel 22/stable.

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


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

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

2022-12-12 Thread Tim Gardner

** Tags added: verification-done-jammy

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

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

Title:
  md: Replace snprintf with scnprintf

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

Bug description:
  SRU Justification

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

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

  [Fix]

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

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool

2022-12-12 Thread Frank Heimes

This bug was not opened against linux-nvidia/5.15.0-1011.11 and is also not 
relevant for this kernel.
However, I'm setting the tag to done to unblock the process.

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

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

Title:
  [UBUNTU 22.04] s390/qeth: cache link_info for ethtool

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  == SRU Justification ==
  Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is 
offline") there was a timing window during recovery, that qeth_query_card_info 
could be   sent to the card, even before it was ready for it, leading to a 
failing cardrecovery. There is evidence that this window was hit, as not 
all callers of get_link_ksettings() check for netif_device_present.

  This patch (Mainline commit 7a07a29e4f67) fixes the regression caused
  by commit e6e771b3d897.

  Commit 7a07a29e4f67 is in mainline as of v6.0-rc1.

  This patch is being requested in Jammy 5.15 and Kinetic 5.19.

  == Fix ==
  7a07a29e4f67 ("s390/qeth: cache link_info for ethtool")

  == Regression Potential ==
  Low.  This patch has been accepted in upstream stable and is limited to
  the s390/qeth card.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  == Comment: #0 - J?rn Siglen  - 2022-08-09 07:38:27 ==
  +++ This bug was initially created as a clone of Bug #199319 +++

  Description:   s390/qeth: cache link_info for ethtool
  Symptom:   lost of IP connection and log entries in journalctl:
    kernel: qeth 0.0.0365: The qeth device driver failed to
    recover an error on the device
  Problem:   Since commit e6e771b3d897
   ("s390/qeth: detach netdevice while card is offline")
     there was a timing window during recovery, that
     qeth_query_card_info could be sent to the card, even before it
     was ready for it, leading to a failing card recovery. There is
     evidence that this window was hit, as not all callers of
     get_link_ksettings() check for netif_device_present.
  Solution:  Use cached values in qeth_get_link_ksettings(), instead of
     calling qeth_query_card_info() and falling back to default
     values in case it fails. Link info is already updated when the
     card goes online, e.g. after STARTLAN (physical link up). Set
     the link info to default values, when the card goes offline or
     at STOPLAN (physical link down). A follow-on patch will improve
     values reported for link down.
     Fixes: e6e771b3d897
     ("s390/qeth: detach netdevice while card is offline")
  Reproduction:  enforce a eth device recvoery, while running ethtool multiple
     times in parallel and using iperf to get load on the interface.
  Upstream-ID:   7a07a29e4f6713b224f3bcde5f835e777301bdb8

  
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

  applicable for most kernel > 3.14

  == Comment: #3 - J?rn Siglen  - 2022-08-09 07:54:41 ==
  the inital update came in with kernel 5.1 upstream, but we found it 
backported in many older kernel versions

  == Comment: #4 - J?rn Siglen  - 2022-08-09 08:03:09 ==
  the acceptance info of the patch can be found here:
  
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

2022-12-12 Thread Frank Heimes

This bug was not opened against linux-nvidia/5.15.0-1011.11 and is also not 
relevant for this kernel.
However, I'm setting the tag to done to unblock the process.

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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1999309] Re: mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC

2022-12-12 Thread Tim Gardner

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

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

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

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => Liming Sun (lsun)

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

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

Title:
  mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC

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

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to for eMMC host setting on BlueField-3 SoC to be 
consistent with UEFI setting and also for stability reason.

  [Fix]
  The fix calls sdhci_enable_v4_mode() for BlueField-3 SoC.

  [Test Case]
  Same functionality as on BlueField-1/2.

  [Regression Potential]
  Can be considered minimum since similar functionality was already included in 
the focal branch for BlueField-1/2. The driver is different, but functionality 
and eMMC device files will be the same.

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


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

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

2022-12-12 Thread Taihsiang Ho

Kernel panic message snippet from the log attachment
papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log:

[  835.504178] [ cut here ]
[  835.504183] kernel BUG at kernel/irq_work.c:235!
[  835.504184] Internal error: Oops - BUG: 0 [#1] SMP
[  835.504186] Modules linked in:
[  835.504187] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GWL 
6.0.9-060009-generic #202211161102
[  835.504189] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[  835.504190] pc : irq_work_run_list+0x98/0xa0
[  835.504194] lr : irq_work_run+0x2c/0x60
[  835.504196] sp : 8883bc60
[  835.504197] x29: 8883bc60 x28: 403e40bca798 x27: 
[  835.504200] x26: 78e12694f000 x25:  x24: 
[  835.504202] x23: c75d180f48d4 x22: 02e9 x21: c75d1a27b798
[  835.504205] x20: 0095 x19: c75d1a287ff0 x18: 8881b050
[  835.504207] x17:  x16:  x15: 6765722030303030
[  835.504209] x14: 0001 x13: 3a296c61746f7420 x12: 302820736b736174
[  835.504212] x11:  x10:  x9 : c75d180f48f4
[  835.504214] x8 :  x7 :  x6 : 
[  835.504217] x5 :  x4 :  x3 : 
[  835.504219] x2 :  x1 :  x0 : 083e7f10eff8
[  835.504221] Call trace:
[  835.504222]  irq_work_run_list+0x98/0xa0
[  835.504224]  smpcfd_dying_cpu+0x24/0x40
[  835.504227]  cpuhp_invoke_callback+0x230/0x610
[  835.504229]  cpuhp_invoke_callback_range+0xe4/0x11c
[  835.504231]  _cpu_up+0x1f4/0x294
[  835.504233]  cpu_up+0xd0/0x13c
[  835.504234]  bringup_nonboot_cpus+0x98/0xdc
[  835.504236]  smp_init+0x40/0xb8
[  835.504237]  kernel_init_freeable+0x144/0x1c8
[  835.504240]  kernel_init+0x3c/0x180
[  835.504241]  ret_from_fork+0x10/0x20
[  835.504244] Code: d282 d2800010 d2800011 d65f03c0 (d421) 
[  835.504249] ---[ end trace  ]---
[  835.504250] note: swapper/0[1] exited with preempt_count 1
[  835.504435] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[  835.504437] SMP: stopping secondary CPUs
[  835.506210]  x6 : 
[  835.506213] x5 :  x4 :  x3 : 
[  835.506216] x2 :  x1 :  x0 : 00e0
[  835.506218] Call trace:
[  835.506219]  arch_cpu_idle+0x1c/0x60
[  835.506221]  default_idle_call+0x78/0x1f0
[  835.506223]  cpuidle_idle_call+0x198/0x200
[  835.506225]  do_idle+0xb8/0x120
[  835.506227]  cpu_startup_entry+0x30/0x40
[  835.506229]  secondary_start_kernel+0xf4/0x14c
[  835.506231]  __secondary_switched+0xb4/0xb8
[  835.514617] Call trace:
[  835.518072]  arch_cpu_idle+0x1c/0x60
[  835.525418]  default_idle_call+0x78/0x1f0
[  835.528518]  cpuidle_idle_call+0x198/0x200
[  835.538432]  do_idle+0xb8/0x120
[  835.545516]  cpu_startup_entry+0x30/0x40
[  835.549499]  secondary_start_kernel+0xf4/0x14c
[  835.553486]  __secondary_switched+0xb4/0xb8
[  836.948113] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b ]---

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

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

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

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

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

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


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

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

2022-12-12 Thread Taihsiang Ho

I rebooted the system with mainline kernel v6.0.9, and I can similar
kernel panic at 302th reboot. See the log attachment
papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log for
the kernel panic message.


** Attachment added: 
"papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log"
   
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+attachment/5635393/+files/papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log

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

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

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

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

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

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


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

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

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

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

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


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

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

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

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

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

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

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

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

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

  On 5.17 kernel, revert it by upstream commit.

  Unstable kernel already got it.

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

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

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

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

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


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

[Kernel-packages] [Bug 1981883] Re: amdgpu module crash after 5.15 kernel update

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

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

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


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

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

Title:
  amdgpu module crash after 5.15 kernel update

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

Bug description:
  [SRU Justification]

  Impact: The 5.15 kernel series introduced a regression compared to
  5.13 related to virtual display code on AMD GPUs. This causes crashes
  for cloud/VM users back to Focal (using rolling cloud or HWE kernels).

  Fix: Upstream stable 5.15.61 contains a fix for this which is only
  needed there since later kernel version have that code rewritten
  again. This change would get picked up normally in the next stable
  cycle after 2022.09.19. But given the impact we would apply the
  following patch from 5.15.61 ahead of time:

commit 27f8f5219fe4658537ba28fd01657e1062ac3960 linux-5.15.y
"drm/amdgpu: fix check in fbdev init"

  Test case: Booting the affected kernel on a VM which passes through
  AMD GPU hardware.

  Regression potential: Worst case some driver functions will not get
  disabled where they did before.

  --- original description ---

  The kernel 5.15 amdgpu module crashes on load with a “BUG: kernel NULL
  pointer dereference” on Amazon EC2 G4ad hardware (custom AMD Radeon
  V520 Pro datacenter GPU) on focal (HWE) and jammy with kernel
  5.15.0-1011 and possibly earlier, up through latest (revision
  1015.19). This crash bug did not exist in any of the focal HWE 5.13
  kernels.

  This is probably an upstream kernel bug, but I am also filing it here
  because existing focal users on EC2 will suddenly stop having access
  to their AMD GPUs after a reboot once the new 5.15 HWE kernel is
  installed.

  The full backtrace from dmesg is below. The offending function call
  which crashes in the 5.15 kernel corresponds to this source (sorry,
  not the right source tree, but the same driver)
  
https://github.com/torvalds/linux/blob/8bb7eca972ad531c9b149c0a51ab43a417385813/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c#L345

  A workaround that I have discovered is adding “options amdgpu
  virtual_display=;” to a new modprobe.d configuration file - something
  which shouldn’t be required, but is at least harmless.

  Here is the relevant BUG message and backtrace from dmesg:

  [  318.111721] BUG: kernel NULL pointer dereference, address: 
  [  318.115443] #PF: supervisor instruction fetch in kernel mode
  [  318.118443] #PF: error_code(0x0010) - not-present page
  [  318.121177] PGD 0 P4D 0
  [  318.122688] Oops: 0010 [#1] SMP NOPTI
  [  318.124592] CPU: 6 PID: 13667 Comm: modprobe Tainted: GW 
5.15.0-1015-aws #19~20.04.1-Ubuntu
  [  318.129711] Hardware name: Amazon EC2 g4ad.2xlarge/, BIOS 1.0 10/16/2017
  [  318.133167] RIP: 0010:0x0
  [  318.134704] Code: Unable to access opcode bytes at RIP 0xffd6.
  [  318.138291] RSP: 0018:9841828d78e0 EFLAGS: 00010246
  [  318.140938] RAX:  RBX: 8a4f16ae8000 RCX: 
0001
  [  318.144604] RDX:  RSI: 0003 RDI: 
8a4f16ae8000
  [  318.148319] RBP: 9841828d7908 R08: 8a4f02460278 R09: 
8a4f06422c40
  [  318.152151] R10: c01c42494f8a R11: 8a4f01dcb5b8 R12: 
8a4f024602e8
  [  318.155929] R13: c107e4a0 R14:  R15: 
8a4f02460010
  [  318.159685] FS:  7f8afdc1c740() GS:8a55f098() 
knlGS:
  [  318.163897] CS:  0010 DS:  ES:  CR0: 80050033
  [  318.167038] CR2: ffd6 CR3: 00011817e000 CR4: 
003506e0
  [  318.170758] Call Trace:
  [  318.173964]  
  [  318.176822]  __drm_helper_disable_unused_functions+0xe7/0x100 
[drm_kms_helper]
  [  318.184230]  drm_helper_disable_unused_functions+0x44/0x50 [drm_kms_helper]
  [  318.189761]  amdgpu_fbdev_init+0x104/0x110 [amdgpu]
  [  318.194264]  amdgpu_device_init.cold+0x7cc/0xc48 [amdgpu]
  [  318.199061]  ? pci_read_config_byte+0x27/0x40
  [  318.203206]  amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
  [  318.207901]  amdgpu_pci_probe+0x1ea/0x290 [amdgpu]
  [  318.212445]  local_pci_probe+0x4b/0x90
  [  318.216386]  pci_device_probe+0x182/0x1f0
  [  318.220407]

[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32

2022-12-12 Thread Heitor Alves de Siqueira

No worries, thank you for the patience, Robie!

With further testing, we've found out that there's an additional upstream
patch required for Focal, which fixes the "inversion" when setting the ARC
limits.

I'll amend the description and re-spin this SRU to include the proper
fixes. I'll then re-upload, after running the regression tests on the new 
version.

** Changed in: zfs-linux (Ubuntu Focal)
   Status: Triaged => In Progress

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

Title:
  ZFS ignores ARC sizes below allmem/32

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. 
This prevents users from properly restraining ARC sizes, and can cause 
increased memory contention in some systems.

  [Test Plan]
  1. Deploy test system with ZFS storage and 32GB RAM
  2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf
     # cat /etc/modprobe.d/99-zfs-arc.conf
     options zfs zfs_arc_min=536870912
     options zfs zfs_arc_max=966367641
  3. Reboot system
  4. Verify ARC sizes through "arc_summary"
     # arc_summary | grep -A3 "ARC size"
     ARC size (current):   < 0.1 %1.3 MiB
     Target size (adaptive):   100.0 %   15.7 GiB
     Min size (hard limit):  3.2 %  512.0 MiB
     Max size (high water):   31:1   15.7 GiB

  For a 32GB test system, we should be able to set max ARC sizes below
  1GB.

  [Fix]
  This has been fixed by upstream commit:
   - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32"

  The commit has been introduced in upstream zfs-2.0.0, so it's needed
  for Bionic and Focal. Releases starting with Impish already have this
  commit by default:

  $ git describe --contains 36a6e2335c45
  zfs-2.0.0-rc1~332
  $ rmadison zfs-linux
   zfs-linux | 0.7.5-1ubuntu15| bionic  | source
   zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates  | source
   zfs-linux | 0.8.3-1ubuntu12| focal   | source
   zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
   zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates   | source
   zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed  | source
   zfs-linux | 2.0.6-1ubuntu2 | impish  | source
   zfs-linux | 2.0.6-1ubuntu2.1   | impish-updates  | source
   zfs-linux | 2.1.2-1ubuntu3 | jammy   | source

  [Regression Potential]
  The introduced commit essentially removes the limitation of setting ARC 
tunables below allmem/32, and re-arranges the order of how some of the tunables 
are parsed. Regressions would possibly show up as other tunables being ignored 
or not being set correctly due to parsing errors. We should validate whether 
other ARC related tunables are still being set correctly, and whether ZFS is 
using the set values for the ARC memory thresholds.

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


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

[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed

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

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

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


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-nvidia 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/1982070

Title:
  scsi: hisi_sas: Increase debugfs_dump_index after dump is  completed

Status in kunpeng920:
  Fix Released
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Trigger dump on hisi_sas in debugfs will cause kernel oops.

  [Test Plan]
  1) modprobe hisi_sas_main with "debugfs_enable=1"
  2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump
  3) dmesg | grep Oops

  [Regression Risk]
  Only touch code in hisi_sas. Need to run full test on hisi_sas. Other 
drivers/platforms are not affected.

  
  [Bug Description]
   When the hisi_sas_main driver is loaded, the DFX function is enabled. When 
the dump is triggered or the SAS controller is reset, call_trace is displayed. 
In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled.

  [Steps to Reproduce]
  1)dmesg -C
  2)dmesg
  3)lsblk
  4)lsscsi -p
  5)lsmod | grep hisi_sas_v3
  6)rmmod hisi_sas_v3_hw
  7)rmmod hisi_sas_main
  8)modprobe hisi_sas_main debugfs_enable=1
  9)modprobe hisi_sas_v3_hw
  10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/
  11)ll
  12)echo 1 > trigger_dump
  13)echo 1 > trigger_dump
  14)dmesg

  [Actual Results]
  [ 1005.899976] sas: broadcast received: 0
  [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.901793] sas: broadcast received: 0
  [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.903586] sas: broadcast received: 0
  [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.905404] sas: broadcast received: 0
  [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.907182] sas: broadcast received: 0
  [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.909025] sas: broadcast received: 0
  [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.910947] sas: broadcast received: 0
  [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.912877] sas: broadcast received: 0
  [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.915221] sas: broadcast received: 0
  [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170
  [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0
  [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk
  [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk
  [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues
  [ 1008.112712] scsi host6: hisi_sas_v3_hw
  [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues
  [ 1010.433120] scsi host7: hisi_sas_v3_hw
  root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0#

  [Expected Results]
  Recurrence Logs：
  [ 360.441633] SET = 0, FnV = 0
  [ 360.444689] EA = 0, S1PTW = 0
  [ 360.447863] Data abort info:
  [ 360.450783] ISV = 0, ISS = 0x0044
  [ 360.454663]

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

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

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

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

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

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

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

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

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

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

[Fix]
Below is the summary of each of the above bug fix commits,

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

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

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

Please let me if I have missed to add any data.

[Test Plan]

1. All drives attached to the controller are Enumerated in OS
2. IO stress for 5Hrs
3. Created a filesystem and done some IO transitions
4. Controller reset and TMs and while IOs are running
5. driver load and unload
6. Reboot loop
7. Verified that the diag trigger settings are persistent across the reboots.

[Where problems could occur]

The regression risk is low.

[Other Info]

https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

  FIX:

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

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

  TESTCASE:

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


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

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

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

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

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


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

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

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

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

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

  [Impact]

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

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

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

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

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

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

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

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

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

  [Fix]

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

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

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

  This has been fixed by the following commits:

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

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

  A test kernel is available in the following ppa:

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

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

  [Test Plan]

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

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

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

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

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

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

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

  
    
  
    
   
  
    
  

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

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following ip parameters

  $ sudo ip a a 192.168.1.7/24 dev enp7s0
  $ sudo

[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool

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

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

** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-nvidia 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/1984103

Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool

Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released

Bug description:
== SRU Justification ==
Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is
offline") there was a timing window during recovery, that qeth_query_card_info
could be sent to the card, even before it was ready for it, leading to a
failing cardrecovery. There is evidence that this window was hit, as not
all callers of get_link_ksettings() check for netif_device_present.

This patch (Mainline commit 7a07a29e4f67) fixes the regression caused
by commit e6e771b3d897.

Commit 7a07a29e4f67 is in mainline as of v6.0-rc1.

This patch is being requested in Jammy 5.15 and Kinetic 5.19.

== Fix ==
7a07a29e4f67 ("s390/qeth: cache link_info for ethtool")

== Regression Potential ==
Low. This patch has been accepted in upstream stable and is limited to
the s390/qeth card.

== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.

== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++

Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8

https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

applicable for most kernel > 3.14

== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions

== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:

https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

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

[Kernel-packages] [Bug 1987232] Re: WARN in trace_event_dyn_put_ref

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

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

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


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

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

Title:
  WARN in trace_event_dyn_put_ref

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

Bug description:
  [SRU Justification]

  Impact: Some imbalanced ref-counting produces kernel warnings
  regularly. Since it is a warning level, this triggers system
  monitoring on servers which in turn causes unnecessary work for
  inspecting the logs.

  Fix: There is a fix upstream and also backported to the upstream
  stable branch. However we are still a bit behind catching up with the
  latest versions. Since this is having quite an impact and the fix is
  rather straight forward, we pull this in from upstream stable ahead of
  time.

  Test case: tbd

  Regression potential: Regressions would manifest as different errors
  related to ref-counting.

  ---

  I have systems that are regularly hitting a WARN in
  trace_event_dyn_put_ref.

  The exact message is:

  WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46
  +trace_event_dyn_put_ref+0x15/0x20

  With the following stacktrace:

   perf_trace_init+0x8f/0xd0
   perf_tp_event_init+0x1f/0x40
   perf_try_init_event+0x4a/0x130
   perf_event_alloc+0x497/0xf40
   __do_sys_perf_event_open+0x1d4/0xf70
   __x64_sys_perf_event_open+0x20/0x30
   do_syscall_64+0x5c/0xc0
   entry_SYSCALL_64_after_hwframe+0x44/0xae

  I've debugged this and worked with upstream to get a fix into Linux.
  It was recently merged in 6.0-rc2.  See here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d

  The problem started appearing as soon as our systems picked up the 
linux-aws-5.15 branch for Focal.  (That was 5.15.0-1015-aws, if memory serves). 
 Could you please cherry pick this fix and pull it back to the the linux and 
linux-aws kernels for Focal?  There's test here: 
https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that 
reproduces the problem very reliably for me.  With the patch applied, I no 
longer get the WARNs.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 22 17:32 seq
   crw-rw 1 root audio 116, 33 Aug 22 17:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Amazon EC2 c5d.12xlarge
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws 
root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-1015-aws N/A
   linux-backports-modules-5.15.0-1015-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.15.0-1015-aws 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: 10/16/2017
  dmi.bios.release: 1.0
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-03f5d8581c7ad94aa
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias:

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

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

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

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


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

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

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

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

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

  [Impact]

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

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

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

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

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

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

  struct lsmblob {
     u32 secid[LSMBLOB_ENTRIES];
  };

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

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

  GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"

  You will receive the following panic:

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

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

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

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

  [Fix]

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

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

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

  I verified this with:

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

[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

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

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

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


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

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

Title:
  Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

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

Bug description:
  [Impact]
  turbostat doesn't show the correct fields for RPL-S.
  This's a wrong column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI

  [Fix]
  Add RPL-S support in turbostat

  [Test Case]
  1. run "turbostat --list"
  2. check the output, this is a correct column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_%

  [Where problems could occur]
  Low, just add a devcie id to support RPL-S.

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


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

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

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

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

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


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

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Fix Committed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
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 source package in Kinetic:
  Fix Committed
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

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:

[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop

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

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

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


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

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

Title:
  ip/nexthop: fix default address selection for connected nexthop

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

Bug description:
  [Impact]

  Packets sent by userland apps are rejected/dropped if the source
  address is not specified and the corresponding route is using a
  connected nexthop object.

  This bug exists since linux v5.3 and has been fixed in v5.19 by the following 
upstream commits:
   - 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
   - cd72e61bad14 ("selftests/net: test nexthop without gw")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
   - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd

  The last commit (v6.0) fixes a regression introduced by the first
  commit.

  [Test Case]

  A detailed test case is explained in the first commit and a self-test
  is added in the second commit.

  [Regression Potential]

  The patch modifies some internal routing states. It has been living in the 
upstream trees for 2 months and the reported regression about icmp redirects 
has been fixed.
  The risk of regression should be contained.

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


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

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

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

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

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


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

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

Title:
  Add HDMI codec ID for Intel Raptor Lake

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

Bug description:
  [SRU Justification]

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

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

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

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

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


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

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

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

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

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


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

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

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

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

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

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

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

  Test log:
  ###
  Legacy routing
  ###

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

  ###
  Legacy routing with VRF
  ###

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

  ###
  Routing with nexthop objects
  ###

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl