[Kernel-packages] [Bug 2002206] Re: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg

[rustyx]

Way to go...

Mark a ticket incomplete, then expired...

While the problem is still there.

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

Title:
  Periodic freezing after unplugging USB-C monitor - "Enabling HDA
  controller" in dmesg

Status in linux package in Ubuntu:
  Expired

Bug description:
  After disconnecting an external monitor from a Thunderbolt 4 (USB-C) port
  *while the system is asleep*, after wake-up the system keeps on randomly 
freezing for 1-2 seconds.

  Every freeze is accompanied by an "Enabling HDA controller" kernel
  message:

  [54984.259832] nvidia :01:00.0: Enabling HDA controller
  [55008.355784] nvidia :01:00.0: Enabling HDA controller
  [55044.771722] nvidia :01:00.0: Enabling HDA controller
  [55069.859682] nvidia :01:00.0: Enabling HDA controller
  [55096.547622] nvidia :01:00.0: Enabling HDA controller
  [55122.243581] nvidia :01:00.0: Enabling HDA controller
  [55146.339543] nvidia :01:00.0: Enabling HDA controller
  [55168.579505] nvidia :01:00.0: Enabling HDA controller
  [55199.491437] nvidia :01:00.0: Enabling HDA controller

  Rebooting or restarting Xorg "fixes" the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-56-generic 5.15.0-56.62
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: socwatch2_15 vtsspp sep5 socperf3 pax nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  me 2469 F pulseaudio
   /dev/snd/controlC0:  me 2469 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Jan  7 12:19:39 2023
  InstallationDate: Installed on 2022-08-31 (128 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 04f2:b74f Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 003: ID 06cb:00f9 Synaptics, Inc.
   Bus 001 Device 007: ID 8087:0033 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 21DE001QMH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro pci=nommconf
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2022
  dmi.bios.release: 1.12
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3JET28W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21DE001QMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3JET28W(1.12):bd10/18/2022:br1.12:efr1.8:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5:
  dmi.product.family: ThinkPad X1 Extreme Gen 5
  dmi.product.name: 21DE001QMH
  dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5
  dmi.product.version: ThinkPad X1 Extreme Gen 5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002206/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

[koba]

** Tags removed: verification-done-kinetic verification-done-lunar
** Tags added: verification-needed-kinetic verification-needed-lunar

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2015972/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

[Roemer Claasen]

Testing 6.4-rc2 now, it seems the S/G mode issue is indeed resolved.
It's been 2 days only, but the new kernel seems really stable.

I'm now running without the "amdgpu.sg_display=0" kernel param.

It seems the tearing issue is still there though, the
"amdgpu.dcdebugmask=0x10" is still needed.

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

Title:
  [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

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

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[Daniel van Vugt]

Thanks Tolga. It looks like the root cause of the issue on your machine
is a lack of display bandwidth when trying to drive 2 screens through
the same cable:

May 11 21:08:51 messier32 kernel: i915 :00:02.0: 
[drm:intel_dp_mst_compute_config [i915]] Trying to find VCPI slots in DSC mode
May 11 21:08:51 messier32 kernel: i915 :00:02.0: 
[drm:intel_dp_mst_compute_config [i915]] DSC Source supported min bpp 18 max 
bpp 24
May 11 21:08:51 messier32 kernel: i915 :00:02.0: 
[drm:intel_dp_mst_compute_config [i915]] DSC Sink supported min bpp 0 max bpp 0
May 11 21:08:51 messier32 kernel: i915 :00:02.0: 
[drm:intel_dp_mst_find_vcpi_slots_for_bpp.constprop.0.isra.0 [i915]] failed 
finding vcpi slots:-22
May 11 21:08:51 messier32 kernel: i915 :00:02.0: [drm:intel_atomic_check 
[i915]] [ENCODER:106:DP-MST C] config failure: -22

I'm not sure if that's an "expected" or "normal" error which we should
expect to see on some setups forever, or if it's a kernel bug. If it's
"expected" then ideally mutter/gnome-shell should fail more gracefully
but I don't know how that's possible given how limited the atomic API
is. You can never find out _what_ failed, only that something failed. I
hate atomic KMS.

Did the workaround work for you?

  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
  MUTTER_DEBUG_FORCE_KMS_MODE=simple

in /etc/environment

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[Daniel van Vugt]

Comment #86 does not appear to be related to this bug so doesn't need to
be discussed here.

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2013088] Re: kernel: fix __clear_user() inline assembly constraints

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2023-05-16 05:24 EDT---
Fix has been successfully verified and released to bionic, focal, jammy, 
kinetic and lunar.
With that, we can close this bug.

@Carsten, Frank and the teams: thanks for your work!

==> Changing status to: CLOSED

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1804

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

Title:
  kernel: fix __clear_user() inline assembly constraints

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

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * In case clear_user() crosses two pages and faults on the second page
 the kernel may write lowcore contents to the first page, instead of
     clearing it.

   * The __clear_user() inline assembly misses earlyclobber constraint
     modifiers. Depending on compiler and compiler options this may lead to
     incorrect code which copies kernel lowcore contents to user space 
 instead of clearing memory, in case clear_user() faults.

  [Fix]

   * For Kinetic and Jammy cherrypick of
 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3
 "s390/uaccess: add missing earlyclobber annotations to __clear_user()"

   * For Focal and Bionic a backport of the above commit is needed:
 https://launchpadlibrarian.net/659551648/s390-uaccess.patch

  [ Test Plan ]

   * A test program in C is needed and used for testing.

   * The test will be done by IBM.

  [ Where problems could occur ]

   * The modification is limited to function 'long __clear_user'.

   * And there, just to one inline assembly constraints line.

   * This is usually difficult to trace.

   * A erroneous modification may lead to a wrong behavior in
     'long __clear_user',

   * and maybe returning a wrong size (in uaccess.c).

  [ Other Info ]

   * This affects all Ubuntu releases in service, down to 18.04.

   * Since we are close to 23.04 kernel freeze, I submit a patch request for
     23.04 separately, and submit the SRU request for the all other
     Ubuntu releases later.

  __

  Description:   kernel: fix __clear_user() inline assembly constraints

  Symptom:   In case clear_user() crosses two pages and faults on the
     second page the kernel may write lowcore contents to the
     first page, instead of clearing it.

  Problem:   The __clear_user() inline assembly misses earlyclobber
     constraint modifiers. Depending on compiler and compiler
     options this may lead to incorrect code which copies kernel
     lowcore contents to user space instead of clearing memory,
     in case clear_user() faults.

  Solution:  Add missing earlyclobber constraint modifiers.
  Preventive:yes

  Upstream-ID:   89aba4c26fae4e459f755a18912845c348ee48f3

  Affected Releases:
     18.04
     20.04
     22.04
     22.10
     23.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 2009142] Re: nvidia-dkms-390 FTBS with linux 6.2

[Andrea Righi]

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-390 FTBS with linux 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  New
Status in nvidia-graphics-drivers-390 source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  nvidia-dkms-390 fails to build with linux 6.2:

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: 
‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^

  [Fix]

  Change the driver to support also the 6.2 kernel ABI.

  [Test case]

  With linux 6.2 installed, run:

  $ sudo apt install nvidia-dkms-390

  [Regression potential]

  We may experience regressions in newer kernels (>= 6.2) that are using
  nvidia-dkms-390 (source code for previous kernels remain unchanged).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+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 2019131] Re: Add PPIN support for Intel EMR cpu

[Roxana Nicolescu]

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

Title:
  Add  PPIN support for Intel EMR cpu

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

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU.
  It was backported to Jammy in #lp2015372 and in #lp2015855.

  The remaining feature needed to fully support EMR is PPIN (the Protected 
Processor Inventory/Identification Number).
  This was recently pushed to upstream in 6.4 in commit 
36168bc061b4368ad19e82b06a6463c95d3bb9a7.
  The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X 
in the cpuids table where cpus that support ppin are listed. The table is then 
used in `ppin_init`.

  In Jammy, this implementation is missing. Both Amd and Intel have their own 
implementation which is doing pretty much the same. Instead of a list of cpus 
supported, a switch case is used instead in their init functions 
(amd_detect_ppin and intel_ppin_init).
  To reduce duplication of code and to help backport smoothly the new addition 
of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918
  “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too.

  Thus commits: 
  - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD 
ppin_init() functions"
  - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids 
to list of CPUs that support PPIN"
  are needed to support PPIN for EMR.

  [Testing]
   Kernel was built on cbd and boot tested on a VM.

  [Regression potential]
   Very low, it is a small refactor that removes duplication and it should not 
affect the functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+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 2019746] Re: package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez package pre-removal script subprocess returned error exit status 1

[Sebastien Bacher]

Thank you for your bug report. Could you give some details on your
system?

The error is
>   Failed to stop bluetooth.service: Unit bluetooth.service not loaded.

it seems bluetooth isn't active. It also look from the report that you
have the bluez snap installed? Did you disable the bluetooth deb service
yourself?

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

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

Title:
  package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez
  package pre-removal script subprocess returned error exit status 1

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  adding import of OBD with these packages as requirements, but are in
  constrast to each other.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  AptOrdering:
   pulseaudio-module-bluetooth:amd64: Remove
   gnome-bluetooth:amd64: Remove
   bluez:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon May 15 13:30:12 2023
  DpkgTerminalLog:
   Removing pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu2.1) ...
   Removing gnome-bluetooth (3.34.5-8) ...
   Removing bluez (5.64-0ubuntu1) ...
   Failed to stop bluetooth.service: Unit bluetooth.service not loaded.
   invoke-rc.d: initscript bluetooth, action "stop" failed.
  ErrorMessage: installed bluez package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2023-01-23 (112 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: bluetooth
  MachineType: Gateway NE56R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.9
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   27   Done2023-05-14T20:11:56-04:00  2023-05-14T20:13:10-04:00  Install 
"bluez" snap
  SourcePackage: bluez
  Title: package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez 
package pre-removal script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.release: 2.7
  dmi.bios.vendor: Gateway
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V2.07
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnGateway:bvrV2.07:bd10/15/2012:br2.7:efr0.0:svnGateway:pnNE56R:pvrV2.07:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV2.07:skuNE56R_0649_V2.07:
  dmi.product.family: Type1Family
  dmi.product.name: NE56R
  dmi.product.sku: NE56R_0649_V2.07
  dmi.product.version: V2.07
  dmi.sys.vendor: Gateway
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2019746/+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 2019450] Re: zfs-linux FTBFS with v6.2.8 stable updates

[Timo Aaltonen]

Hello Dimitri, or anyone else affected,

Accepted zfs-linux into lunar-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.1.9-2ubuntu1.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: zfs-linux (Ubuntu Lunar)
   Status: New => Fix Committed

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

Title:
  zfs-linux FTBFS with v6.2.8 stable updates

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Jammy:
  New
Status in zfs-linux source package in Lunar:
  Fix Committed
Status in zfs-linux source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * Stable kernel updates changed signature of a function call, thus
  zfs-linux needs adapting. Otherwise it fallsback to older symbols,
  which are GPL only.

  [ Test Plan ]

   * linux 6.2 with 6.2.8 stable updates builds with zfs, without this
  fix build fails with

MODPOST <>/build/zfs/2.1.9/build/module/Module.symvers
  ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 
'bio_start_io_acct'
  ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 
'bio_end_io_acct_remapped'
  make[5]: *** [scripts/Makefile.modpost:138: 
<>/build/zfs/2.1.9/build/module/Module.symvers] Error 1

  as the signature of the non-gpl function call has changed, zfs
  configure scripts fail to detect it as available, fallback on a gpl
  symbol, which we then prohibit from using.

  [ Where problems could occur ]

   * This is a cherry-pick of build-compat only, without any other
  changes

  [ Other Info ]

   * Upstream commit

  
https://github.com/openzfs/zfs/pull/14677/commits/1a951502f0b4200a13f23f0d2f5759ef60188c17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2019450/+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 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1

[Stefan Bader]

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

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

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

Title:
  Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Impact]
  A regression caused by incomplete stable backports

  [Fix]

  commit 8273b4048664fff356fd10059033f0e2f5a422a1
  Author: Arunpravin Paneer Selvam 
  Date:   Tue Oct 18 07:08:38 2022 -0700

  drm/amdgpu: Fix for BO move issue

  [Test case]

  Install the update, check that display works again on amdgpu

  --

  The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to
  stick on Linux 5.15 because 5.19 was not working with my computer. The
  last two days I spent time to find a way to run Linux 5.19, and found
  one version working: 5.19.0-23.

  Here are the versions I tested:

  - 5.19.0-23
  - 5.19.0-29
  - 5.19.0-31
  - 5.19.0-42

  In that list, only Linux 5.19.0-23 is working with that computer.

  There may be other versions that work I have not tested, but basically
  the breakages occurred after 5.19.0-23.

  I face two problems, let's talk about the first one, the graphic one
  still present in 5.19.0-42. It starts to occurs with 5.19.0-31
  (5.19.0-29 is not affected): graphic breaks at the moment it should
  switch from low resolution display to high resolution display at the
  very beginning of startup. The computer is not completely broken, but
  the graphic is dead. X11 cannot start, trying to use the framebuffer,
  meaning the amdgpu driver is not functional).

  The second bug is the one I get with the 5.19.0-29 version. Linux
  5.19.0-29 doesn't experience the graphic bug but has another issue
  that makes the computer unusable: some CPU got locked, and some btrfs
  process runs at 100% CPU, syncing never ends, even preventing to
  reboot. This bug is less important because I don't reproduce it on
  version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine.

  I have not updated to Ubuntu 23.04 yet because I'm afraid of newer
  kernels from it would leave my computer totally unusable, I have run
  Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of
  that fear.

  It actually took me two work days to test various combinations to boot
  the computer so I'm sticking on 5.19.0-29 for now, and I have limited
  time to test other options. I also tried various BIOS options, and
  also upgraded the BIOS…, and since that ThreadRipper PRO computer has
  very slow booting BIOS, trying various configurations or software
  versions that requires a reboot quickly eats-up whole hours.

  The attached logs may have traces of dkim modules like amdgpu-pro, but
  the first time I experienced the bug I had none of them. I reproduced
  the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply
  opening the ticket from my working environment, and I decided to not
  spend one more hour just to uninstall amdgpu-pro and reboot only to do
  that ticket.

  Here are some details on the hardware:

  - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named 
WRX80PRO-F1 in dmidecode, dated 08/04/2022) 
https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10
  - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 
KSM32ED8/32ME 16Gbit Micron E
  - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2)
  - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver)
  - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver)
  - GPU: ASPEED graphic Family rev 41

  The ASPEED graphic is a small card integrated in the motherboard and
  part of the BMC, I cannot remove it. This may participate in the
  trouble.

  When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is
  displayed on all AMD and ASPEED graphic output, then at the moment the
  graphic switches from low resolution to high resolution, the ASPEED
  graphic goes off and the display continue on AMD cards.

  When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is
  displayed on all AMD and ASPEED graphic output, then at the moment the
  graphic switches from low resolution to high resolution, the AMD cards
  display garbage but the display continue on the ASPEED card. The
  ASPEED card is a very basic integrated card without hardware
  acceleration and featuring only one VGA output so that's unusable. As
  an additional information I know X11 never start on the ASPEED if
  there are discrete cards plugged in (tested last year).

  So right now that computer is sticking on Linux 5.19.0-23 which
  doesn't doesn't the graphic and btrfs bugs.

  The last 

[Kernel-packages] [Bug 2009142] Re: nvidia-dkms-390 FTBS with linux 6.2

[Andrea Righi]

Moving jammy to the same version of the driver used in lunar allows to
use nvidia-dkms-390 both with the stock 5.15 kernel and the new hwe 6.2
(verified in a VM doing a simple test build).

** Patch added: "nvidia-dkms-390-jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+attachment/5673318/+files/nvidia-dkms-390-jammy.debdiff

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

Title:
  nvidia-dkms-390 FTBS with linux 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  New
Status in nvidia-graphics-drivers-390 source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  nvidia-dkms-390 fails to build with linux 6.2:

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: 
‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^

  [Fix]

  Change the driver to support also the 6.2 kernel ABI.

  [Test case]

  With linux 6.2 installed, run:

  $ sudo apt install nvidia-dkms-390

  [Regression potential]

  We may experience regressions in newer kernels (>= 6.2) that are using
  nvidia-dkms-390 (source code for previous kernels remain unchanged).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+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 2009142] Re: nvidia-dkms-390 FTBS with linux 6.2

[Andrea Righi]

Better debdiff to backport only the patch required to support linux 6.2
(that is much better from an SRU perspective). Tested with positive
result in a VM both with 5.15 and the new hwe 6.2 kernels. So, please
ignore my previous comment.

** Patch added: "nvidia-dkms-390-jammy-support-linux-6.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+attachment/5673321/+files/nvidia-dkms-390-jammy-support-linux-6.2.debdiff

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

Title:
  nvidia-dkms-390 FTBS with linux 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  New
Status in nvidia-graphics-drivers-390 source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  nvidia-dkms-390 fails to build with linux 6.2:

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: 
‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^

  [Fix]

  Change the driver to support also the 6.2 kernel ABI.

  [Test case]

  With linux 6.2 installed, run:

  $ sudo apt install nvidia-dkms-390

  [Regression potential]

  We may experience regressions in newer kernels (>= 6.2) that are using
  nvidia-dkms-390 (source code for previous kernels remain unchanged).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+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 2019855] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-

[Sven Broemer]

Public bug reported:

This bug occured while upgrade to lunar lobster. 
parallels@ubuntu-linux-20-04-desktop:~$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04
parallels@ubuntu-linux-20-04-desktop:~$ cat version.log 
Ubuntu 5.19.0-42.43-generic 5.19.17

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
Uname: Linux 5.19.0-42-generic aarch64
NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg
ApportVersion: 2.26.1-0ubuntu2
Architecture: arm64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  parallels   2242 F wireplumber
 /dev/snd/seq:parallels   2235 F pipewire
CasperMD5CheckResult: pass
Date: Tue May 16 13:14:14 2023
ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2021-03-13 (794 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release arm64 
(20210201.2)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lspci-vt:
 -[:00]-+-01.0  Intel Corporation 82801I (ICH9 Family) HD Audio Controller
+-02.0  Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 
EHCI Controller
+-03.0  NEC Corporation uPD720200 USB 3.0 Host Controller
+-09.0  Parallels, Inc. Virtual Machine Communication Interface
\-0a.0  Red Hat, Inc. Virtio GPU
MachineType: Parallels International GmbH. Parallels ARM Virtual Machine
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=732910d6-ddae-4a95-ab9e-9f5c9edc555a ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to lunar on 2023-05-16 (0 days ago)
acpidump:
 
dmi.bios.date: Fri, 10 Feb 2023 10:16:42
dmi.bios.release: 0.1
dmi.bios.vendor: Parallels International GmbH.
dmi.bios.version: 18.2.0 (53488)
dmi.board.asset.tag: None
dmi.board.name: Parallels ARM Virtual Platform
dmi.board.vendor: Parallels ARM Virtual Machine
dmi.board.version: 0.1
dmi.chassis.type: 2
dmi.chassis.vendor: Parallels International GmbH.
dmi.modalias: 
dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM:
dmi.product.family: Parallels VM
dmi.product.name: Parallels ARM Virtual Machine
dmi.product.sku: Parallels_ARM_VM
dmi.product.version: 0.1
dmi.sys.vendor: Parallels International GmbH.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: apport-package arm64 lunar

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/2019855/+attachment/5673325/+files/lspci-vnvn.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/2019855

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: »installiertes post-installation-Skript des Paketes
  linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1
  zurück

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug occured while upgrade to lunar lobster. 
  parallels@ubuntu-linux-20-04-desktop:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  parallels@ubuntu-linux-20-04-desktop:~$ cat version.log 
  Ubuntu 5.19.0-42.43-generic 5.19.17

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic aarch64
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parallels   2242 F wireplumber
   /dev/snd/seq:parallels   2235 F pipewire
  CasperMD5CheckResult: pass
  Date: Tue May 16 13:14:14 2023
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  

[Kernel-packages] [Bug 2000798] Re: cannot connect to K380 bluetooth keyboard

[Launchpad Bug Tracker]

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

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

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

Title:
  cannot connect to K380 bluetooth keyboard

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Had trouble connecting my K380 keyboard with the laptop (previously
  used it without issues), unpaired and now I can no longer pair it.

  Other bluetooth devices work with this particular laptop (mouse,
  earbuds), the keyboard works flawlessly with a different laptop
  (running the same Ubuntu 20.04 OS) and an Android phone.

  Used bluetoothctl to peek under the hood and got nowhere after turning scan 
on on the controller and activating the keyboard:
  [NEW] Device [...mac address of the keyboard...] Keyboard K380
  [CHG] Device [...mac address of the keyboard...] Connected: no
  [DEL] Device [...mac address of the keyboard...] Keyboard K380

  After this action, I get:

  # connect [...mac address of the keyboard...]
  Device [...mac address of the keyboard...] not available

  When I activate the keyboard (by pressing any key on it while it's
  turned on), in the bluetooth settings GUI tool I see the keyboard
  appear for a fraction of a second in the list of unpaired devices and
  then it disappears.

  Help?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 19:41:41 2022
  InstallationDate: Installed on 2022-11-03 (57 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems LAPKC71E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCTGL357.0037.2021.0712.0948
  dmi.board.name: LAPKC71E
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M1-402
  dmi.chassis.type: 10
  dmi.chassis.vendor: Intel(R) Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000:
  dmi.product.family: KC
  dmi.product.name: LAPKC71E
  dmi.product.sku: BKC71EBFB6000
  dmi.product.version: M38559-402
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 20:1E:88:3C:4C:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:221779 acl:5063 sco:0 events:6018 errors:0
TX bytes:785416 acl:104 sco:0 commands:4168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 1935719] Re: broadcom-sta-dkms 6.30.223.271-12: broadcom-sta kernel module failed to build

[Launchpad Bug Tracker]

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

** Changed in: broadcom-sta (Ubuntu)
   Status: New => Confirmed

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

Title:
  broadcom-sta-dkms 6.30.223.271-12: broadcom-sta kernel module failed
  to build

Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu does not find the WiFi adapter after update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: broadcom-sta-dkms 6.30.223.271-12
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-22-generic
  Date: Fri Jul  9 20:42:08 2021
  DuplicateSignature: 
dkms:broadcom-sta-dkms:6.30.223.271-12:/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:1666:6:
 error: implicit declaration of function ‘segment_eq’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2021-06-10 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  PackageVersion: 6.30.223.271-12
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: broadcom-sta
  Title: broadcom-sta-dkms 6.30.223.271-12: broadcom-sta kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1935719/+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 2019855] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: »installiertes post-installation-Skript des Paketes
  linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1
  zurück

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug occured while upgrade to lunar lobster. 
  parallels@ubuntu-linux-20-04-desktop:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  parallels@ubuntu-linux-20-04-desktop:~$ cat version.log 
  Ubuntu 5.19.0-42.43-generic 5.19.17

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic aarch64
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parallels   2242 F wireplumber
   /dev/snd/seq:parallels   2235 F pipewire
  CasperMD5CheckResult: pass
  Date: Tue May 16 13:14:14 2023
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2021-03-13 (794 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release arm64 
(20210201.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci-vt:
   -[:00]-+-01.0  Intel Corporation 82801I (ICH9 Family) HD Audio Controller
  +-02.0  Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller
  +-03.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  +-09.0  Parallels, Inc. Virtual Machine Communication Interface
  \-0a.0  Red Hat, Inc. Virtio GPU
  MachineType: Parallels International GmbH. Parallels ARM Virtual Machine
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=732910d6-ddae-4a95-ab9e-9f5c9edc555a ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to lunar on 2023-05-16 (0 days ago)
  acpidump:
   
  dmi.bios.date: Fri, 10 Feb 2023 10:16:42
  dmi.bios.release: 0.1
  dmi.bios.vendor: Parallels International GmbH.
  dmi.bios.version: 18.2.0 (53488)
  dmi.board.asset.tag: None
  dmi.board.name: Parallels ARM Virtual Platform
  dmi.board.vendor: Parallels ARM Virtual Machine
  dmi.board.version: 0.1
  dmi.chassis.type: 2
  dmi.chassis.vendor: Parallels International GmbH.
  dmi.modalias: 
dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM:
  dmi.product.family: Parallels VM
  dmi.product.name: Parallels ARM Virtual Machine
  dmi.product.sku: Parallels_ARM_VM
  dmi.product.version: 0.1
  dmi.sys.vendor: Parallels International GmbH.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019855/+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 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages

[Marcus Uneson]

Same issue here, very similar to the above:

System-manufacturer : LENOVO
System-product-name : 20STCTO1WW 
System-version : ThinkPad P15 Gen 1
Bios-release-date : 10/07/2022
Bios-version : N30ET48W (1.31 )

5.19.0-41-generic

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

Title:
  [i915] Intermittent freezing and LSPCON init failed kernel messages

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-oem-5.14 package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Lenovo ThinkPad model 20ST0055AU

  Boot messages show:
  [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on 
minor 0

  During normal operation there will intermittently be a freeze for a
  second or two and then more of these messages display in the kernel
  logs:

  [  505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D
  [  506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  The system will then become operational again.

  The system is still usable, but it is annoying.

  I've switched onto this OEM kernel from the generic kernel (5.13), as
  I had other problems with 5.13 regarding external displays not coming
  back after idle timeouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40
  ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21
  Uname: Linux 5.14.0-1036-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 10:29:31 2022
  InstallationDate: Installed on 2021-05-05 (371 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[Tolga Gonul]

Hey Daniel. Your comment made me look closer at what was happening and I
found the culprit in my case.

I have 2x 1440p screens connected through the dock, that support up to
165hz, and the dock supports enough bandwidth to run them at 1440px60hz.
But when it wakes up from suspend it for some reason puts the screen
settings at 1440px144hz. The same doesn't occur in xorg which is why the
issue was isolated to Wayland for me.

After I woke my laptop from suspend, changed the display settings to
60hz, everything worked again. After changing it once it also seems to
persist for now.

One other observation though, in xorg I can't even set my screen hz
higher than 60 while Wayland gives me the option to crank it up to
144hz. When even trying to set it to 144hz, my monitors OSD tell me it
still runs 60hz while gnome settings thinks it's 144hz.

Either way, I apologize if I wasted your time but I hope that it was
helpful for others who might end up here trying to find a similar
solution.

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2019450] Re: zfs-linux FTBFS with v6.2.8 stable updates

[Dimitri John Ledkov]

** Merge proposal linked:
   https://code.launchpad.net/~xnox/+git/kernel-versions/+merge/442998

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

Title:
  zfs-linux FTBFS with v6.2.8 stable updates

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Jammy:
  New
Status in zfs-linux source package in Lunar:
  Fix Committed
Status in zfs-linux source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * Stable kernel updates changed signature of a function call, thus
  zfs-linux needs adapting. Otherwise it fallsback to older symbols,
  which are GPL only.

  [ Test Plan ]

   * linux 6.2 with 6.2.8 stable updates builds with zfs, without this
  fix build fails with

MODPOST <>/build/zfs/2.1.9/build/module/Module.symvers
  ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 
'bio_start_io_acct'
  ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 
'bio_end_io_acct_remapped'
  make[5]: *** [scripts/Makefile.modpost:138: 
<>/build/zfs/2.1.9/build/module/Module.symvers] Error 1

  as the signature of the non-gpl function call has changed, zfs
  configure scripts fail to detect it as available, fallback on a gpl
  symbol, which we then prohibit from using.

  [ Where problems could occur ]

   * This is a cherry-pick of build-compat only, without any other
  changes

  [ Other Info ]

   * Upstream commit

  
https://github.com/openzfs/zfs/pull/14677/commits/1a951502f0b4200a13f23f0d2f5759ef60188c17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2019450/+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 2013758] Re: Add support for 200G/400G speed to bond

[Khoa Vo]

There is no 200/400Gb for BlueField2.  It is only applicable for
BlueField 3 therefore I remove tag verifcation-needed-focal

** Tags removed: verification-needed-focal

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

Title:
  Add support for 200G/400G speed to bond

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

Bug description:
  SRU Justification:

  [Impact]

  * 5.4 kernel can't work with bond for 200G/400G NIC

  [Fix]

  * cherry pick the commits to support 200G/400G

  [Test Plan]

  * Test on 200G/400G bond

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013758/+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 2018687] Re: rm -r dir on USB disk locks up hdparm on different disk

[Ian! D. Allen]

Unfortunately, an unacceptable side-effect of "sysctl -w
vm.dirty_ratio=0" is that disk operations that move a lot of data are
taking much too long. An rsync that normally takes less than an hour of
real time was still running over 12 hours later (and hasn't finished
yet).  I'm reverting the vm.dirty_ratio back up to 20 to see if that
clears out all the unfinished disk I/O.

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

Title:
  rm -r dir on USB disk locks up hdparm on different disk

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

Bug description:
  Description:Ubuntu 20.04.6 LTS
  Linux 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023 
x86_64 GNU/Linux
  Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz

  Running a "rm -r dir" on a directory with millions of files that resides
  on a disk in an external USB-3 hard drive dock locks up an unrelated
  hdparm processes running on an internal disk such that the kernel says:

  May  7 04:24:02 kernel: [163606.041862] INFO: task hdparm:1391162 blocked 
for more than 120 seconds.
  [...]
  May  7 04:26:03 kernel: [163726.876357] INFO: task hdparm:1391162 blocked 
for more than 241 seconds.
  [...]
  May  7 04:28:04 kernel: [163847.702980] INFO: task hdparm:1391162 blocked 
for more than 362 seconds.

  First a normal run of "hdparm -t /dev/sda" with the offending "rm -r" 
SIGSTOPped so that
  it doesn't affect anything:

  # \time hdparm -t /dev/sda
  /dev/sda:
   Timing buffered disk reads: 1128 MB in  3.00 seconds = 375.50 MB/sec
  0.01user 0.67system 0:06.21elapsed 11%CPU (0avgtext+0avgdata 
4584maxresident)k
  2312704inputs+8outputs (0major+664minor)pagefaults 0swaps

  Elapsed time is about six seconds, as expected.  /dev/sda is an
  internal SSD drive.

  I now run this loop to show the timings and process states below:

  # while sleep 1 ; do  date ; ps laxww | grep '[ ]D' | grep -v
  refrig ; done

  (I have some processes stopped in a freezer cgroup ("refrig") that I
  don't want to see in the grep output.)  I SIGCONT the offending "rm -r"
  running on the drive in the USB3 drive dock and you see the rm appear
  in uninterruptible sleep along with a couple of kernel processes:

  Sun May  7 05:01:07 EDT 2023
  Sun May  7 05:01:08 EDT 2023
  Sun May  7 05:01:09 EDT 2023
  Sun May  7 05:01:10 EDT 2023
  Sun May  7 05:01:11 EDT 2023
  1 0 447   2  20   0  0 0 usb_sg D?  3:17 
[usb-storage]
  4 0 1423283   11939  20   0  10648   580 wait_o D+   pts/28 0:00 
rm -rf 15tb3
  Sun May  7 05:01:12 EDT 2023
  1 0 447   2  20   0  0 0 usb_sg D?  3:17 
[usb-storage]
  1 04016   1  20   0 161136  1900 usbhid Dsl  ?  1:39 
/sbin/apcupsd
  4 0 1423283   11939  20   0  10648   580 wait_o D+   pts/28 0:00 
rm -rf 15tb3
  Sun May  7 05:01:13 EDT 2023

  The above lines showing those processes in uninterruptible sleep repeat
  over and over each second as the "rm -r" continues.  I then start up
  "hdparm -t /dev/sda" on the internal SSD disk, and it also appears in
  uninterruptible sleep and doesn't finish even after minutes of waiting:

  Sun May  7 05:01:25 EDT 2023
  1 0 368   2  20   0  0 0 md_sup D?  2:57 
[md0_raid5]
  1 0 1366783   2  20   0  0 0 blk_mq D?  0:02 
[kworker/u16:2+flush-8:144]
  4 0 1423283   11939  20   0  11260  2544 wait_o D+   pts/28 0:00 
rm -rf 15tb3
  4 0 14235019975  20   0   4680  4584 wb_wai DL+  pts/4  0:00 
hdparm -t /dev/sda
  Sun May  7 05:01:26 EDT 2023
  1 0 447   2  20   0  0 0 usb_sg D?  3:17 
[usb-storage]
  1 0 1366783   2  20   0  0 0 blk_mq D?  0:02 
[kworker/u16:2+flush-8:144]
  4 0 1423283   11939  20   0  11260  2544 wait_o D+   pts/28 0:00 
rm -rf 15tb3
  4 0 14235019975  20   0   4680  4584 wb_wai DL+  pts/4  0:00 
hdparm -t /dev/sda
  Sun May  7 05:01:27 EDT 2023
  [...]
  4 0 14235019975  20   0   4680  4584 wb_wai DL+  pts/4  0:00 
hdparm -t /dev/sda
  Sun May  7 05:01:35 EDT 2023
  1 0 447   2  20   0  0 0 usb_sg D?  3:17 
[usb-storage]
  4 0 1423283   11939  20   0  11260  2544 blk_mq D+   pts/28 0:00 
rm -rf 15tb3
  4 0 14235019975  20   0   4680  4584 wb_wai DL+  pts/4  0:00 
hdparm -t /dev/sda
  Sun May  7 05:01:36 EDT 2023
  1 0 447   2  20   0  0 0 usb_sg D?  3:17 
[usb-storage]
  1 04985   2  20   0  0 0 rq_qos D?  0:24 
[jbd2/sdj1-8]
  1 0 1366783   2  20   0  0 0 blk_mq D?  0:02 

[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2

[Andrea Righi]

** Patch added: "nvidia-dkms-390-mantic-better-support-for-linux-6.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5673352/+files/nvidia-dkms-390-mantic-better-support-for-linux-6.2.debdiff

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Jammy:
  New
Status in nvidia-graphics-drivers-390 source package in Lunar:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+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 2013383] Re: mlxbf-bootctl: support SMC call for setting ARM boot state

[Meriton Tuli]

Using 5.15.0-1015-bluefield, the following file exists:
# ll /sys/devices/platform/MLNXBF04\:00/driver/os_up
--w--- 1 root root 4096 May 11 21:02 
/sys/devices/platform/MLNXBF04:00/driver/os_up

** 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2013383

Title:
  mlxbf-bootctl: support SMC call for setting ARM boot state

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

Bug description:
  SRU Justification:

  [Impact]

  Add a new SMC call which allows setting the ARM boot progress state to
  "OS is up".

  [Fix]

  * Add a new SMC call in mlxbf-bootctl which allows setting the ARM
  boot progress state to "OS is up".

  [Test Case]

  * Check that /sys/devices/platform/MLNXBF04:00/driver/os_up exists

  [Regression Potential]

  * No known regression because it is just adding a sysfs entry. It is
  backward compatible with older TAF images. If the SMC call is not
  supported by ATF, it is ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013383/+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 2012649] Re: mlxbf_gige: need to replace SAUCE patches with upstream commits

[Meriton Tuli]

** 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2012649

Title:
  mlxbf_gige: need to replace SAUCE patches with upstream commits

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

Bug description:
  SRU Justification:

  [Impact]

  The GIGE driver ("mlxbf_gige") in the Jammy repo contains SAUCE
  patches that enable BlueField-3 support.  This same functionality
  is contained in upstream commits and Jammy repo should utilize them.

  [Fix]
  The BlueField-3 support will be provided in the form of a set
  of upstream patches, to be sent in as a pull request.

  [Test Case]
  Should test on both BlueField-2 & BlueField-3: 
 Boot platform and bring up "oob_net0" interface properly
 Test that network traffic works properly

  [Regression Potential]
  The upstream commits have been reviewed and tested well,
  so there should be low risk of regression.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012649/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[Daniel van Vugt]

If anyone would like to help more, please reproduce the bug and while
the screen is stuck in the off state, log in by ssh and run:

  sudo apt install drm-info
  sudo drm_info > drminfo.txt

Then attach the resulting text file here.

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2015670] Re: [r8169] Kernel loop PCIe Bus Error on RTL810xE

[corrado venturini]

Same problem in Ubuntu 23.10 with kernel 6.4.0-060400rc2-generic

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

Title:
  [r8169] Kernel loop PCIe Bus Error on RTL810xE

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel loop after login
  This happens with both kernels 6.2.0-18 and 6.2.0-19 on 2 different 
partitions of same PC:
  Partition installed from beta and partition from ISO dated 04/02.
  No problem on same PC different partitions of same disk with Ubuntu Focal, 
Jammy and Kinetic
  Problem does not occur with kernel 5.19.17-051917-generic installed from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/
  Adding journalctl -b related to the problem

  note: I opened another bug for this problem blaming gnome-shell but it's wrong
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-19-generic 6.2.0-19.19
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1511 F wireplumber
   /dev/snd/seq:corrado1508 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  9 09:33:06 2023
  InstallationDate: Installed on 2023-04-07 (1 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic 
root=UUID=78239576-b8af-4c66-bf15-8d5ee9a63d35 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:sku097A:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015670/+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 2019869] [NEW] nvidia-dkms-390: better support for kernel 6.2

[Andrea Righi]

Public bug reported:

[Impact]

Instead of disabling acpi support completely with nvidia-dkms-390, we
should try instead to see if it's possible to support it somehow.

[Fix]

This patch looks promising (even if it says huge hack in the comments...):
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

Apply this patch and drop any 6.0 and 6.2 related patches.

[Regression potential]

With this patch nvidia-dkms-390 should build against 6.2 kernels without
disabling any feature, but users of this driver may experience kernel
bugs / crashes. However, the nvidia 390 driver is unmaintained so we
should start to consider phasing it out.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-390 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** No longer affects: nvidia-graphics-drivers-390 (Ubuntu Kinetic)

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Jammy:
  New
Status in nvidia-graphics-drivers-390 source package in Lunar:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+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 2016269] Re: conntrack mark is not advertised via netlink

[Nicolas Dichtel]

Tests are ok.

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

Title:
  conntrack mark is not advertised via netlink

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

Bug description:
  SRU justification sent to ML:

  [Impact]
  There was a commit 95fcb42e5f20
  ("netfilter: ctnetlink: fix compilation warning after data race fixes in ct 
mark")
  that introduces a regression where the "mark" variable is no longer
  dumped in netlink netfilter conntrack messages, which userspace tools use
  to mark and track connections.

  [Fix]
  Introduce the upstream fix 9f7dd42f0db1
  ("netfilter: ctnetlink: revert to dumping mark regardless of event type")
  that always dumps the 'mark' variable for conntrack entries.
  This fix has also landed in 5.15 upstream stable.

  [Test]
  Run 'conntrack -E' and check the output of connection entries.

  The 'mark' variable should now be present in connection entries after
  the fix.

  before fix:
  > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345 
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
  after fix:
  > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345 
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1

  [Where problems could occur]
  The fixes are pretty straight forward so regression potential should be
  minimal. 


  
  

  [Impact]

  The last merge of the v5.15 stable (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
  introduced a bug on netlink netfilter conntrack messages.

  The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix 
compilation warning after data race fixes in ct mark"):
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20

  This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter: 
ctnetlink: revert to dumping mark regardless of event type"):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1

  which has been backported in v5.15.103:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c

  [Test Case]

  Run 'conntrack -E' and check the output.

  Before the problematic commit:
  > tcp  6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] 
mark=0 use=1

  'mark=' is seen on connrtack event

  after:
  > tcp  6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1

  => 'mark=' is not seen.

  [Regression Potential]

  The patch is quite simple. It has been backported in the official 5.15
  stable. The risk of regression should be contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+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 2019869] Re: nvidia-dkms-390: better support for kernel 6.2

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Jammy:
  New
Status in nvidia-graphics-drivers-390 source package in Lunar:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+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 2013758] Re: Add support for 200G/400G speed to bond

[Bartlomiej Zolnierkiewicz]

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

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

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

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

Title:
  Add support for 200G/400G speed to bond

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

Bug description:
  SRU Justification:

  [Impact]

  * 5.4 kernel can't work with bond for 200G/400G NIC

  [Fix]

  * cherry pick the commits to support 200G/400G

  [Test Plan]

  * Test on 200G/400G bond

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013758/+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 2015293] Re: netfilter: ctnetlink: Support offloaded conntrack entry deletion

[Bartlomiej Zolnierkiewicz]

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

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

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

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

Title:
  netfilter: ctnetlink: Support offloaded conntrack entry deletion

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

Bug description:
  * Explain the bug(s)
   
  conntrack -D or conntrack -F doesn't delete offloaded tuples.
   
  * brief explanation of fixes
   
  Add support for to delete offloaded tuples via netlink interface and
  userspace conntrack utility.
   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.

  Enable HW offload and configure regular connection tracking OpenFlow
  rules:


  e.g:

  ovs-ofctl del-flows br-ovs

  ovs-ofctl add-flow br-ovs arp,actions=normal

  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk
  actions=ct(table=1)"

  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new
  actions=ct(commit),normal"

  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est,
  actions=normal"


  Run a UDP connection, e.g:
  on mlx5 VF1 iperf -s -u
  on mlx5 VF2 iperf -c  -u -t 10 
   

  Optional: In different terminal, while traffic is running, check for
  offload:

  tcpdump -nnepi  udp
  and see no iperf udp packets.
   

  Dump conntrack with relevant ip:

  cat /proc/net/nf_conntrack | grep -i 
   

  See tuples were offloaded:
  ipv4 2 udp 17 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 
bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3
   
  Flush the tuples:
  conntrack -F
   
  Verify tuples are deleted:
  cat /proc/net/nf_conntrack | grep -i 


  Before fix, the above tuple shows again,

  after fix, it's deleted, and shows nothing.

   
  * What it could break.


  Conntrack -F / -D not working on offloaded tuples.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015293/+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 2016700] Re: Add support for X13s wifi

[Juerg Haefliger]

Verified that the updated binary is provided by the lunar package.


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

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

Title:
  Add support for X13s wifi

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  Wifi on a Lenovo X13s is not coming up. The board ID is unknown.

  [Fix]

  Uptream commit d1dc30480fef ("ath11k: WCN6855 hw2.0: update
  board-2.bin")

  [Test Case]

  Check that wifi comes up.

  [Where Problems Could Occur]

  ath11k based machines could experince Wifi issues if that upstream
  binary is broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2016700/+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 2012743] Re: Support Nvidia BlueField-3 GPIO driver and pin controller

[Meriton Tuli]

** 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2012743

Title:
  Support Nvidia BlueField-3 GPIO driver and pin controller

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

Bug description:
  SRU Justification:

  [Impact]

  Support the BlueField-3 SoC GPIO driver for handling interrupts and providing 
the option to change the direction and value of a GPIO.
  Support the BlueField-3 SoC pin controller driver for allowing a select 
number of GPIO pins to be manipulated from userspace or the kernel.

  All these changes have been accepted for upstream but most of them are
  not yet in the tree/branches.

  PLEASE NOTE: This change is dependent on changes done in the ACPI
  tables. So the UEFI image needs to be updated accordingly.

  [Fix]

  * Add support for the BlueField-3 SoC GPIO driver.
  This driver configures and handles GPIO interrupts. It also enables a user to 
manipulate certain GPIO pins via libgpiod tools or other kernel drivers.
  The usable pins are defined via the "gpio-reserved-ranges" property.

  * NVIDIA BlueField-3 SoC has a few pins that can be used as GPIOs or
  take the default hardware functionality. Add a driver for the pin
  muxing.

  * The following gpiolib commits are bug fixes and are required for the gpio 
driver to work:
  443a0a0f0cf4f432c7af6654b7f2f920d411d379

  Although the following have been accepted by maintainers, they are not 
present in any tree/branch yet so
  these will be pushed as SAUCE for now:
  [PATCH v4] gpio: mmio: handle "ngpios" properly in bgpio_init()
  [PATCH v1] gpio: mmio: fix calculation of bgpio_bits

  [Test Case]

  * Check if the gpio-mlxbf3 driver is loaded
  * Check if the pinctrl-mlxbf3 driver is loaded
  * check if the mlxbf-gige driver is loaded
  * check if the pwr-mlxbf driver is loaded
  * Check that the oob_net0 interface is up and operational
  * Do reset and powercycle and check the oob_net0 interface again
  * Test power GPIO interrupt on BF3.

  [Regression Potential]

  * The Mellanox drivers could fail to be loaded.
  * The mlxbf-gige PHY interrupt or pwr-mlxbf interrupt could fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012743/+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 2012571] Re: net/sched: cls_api: Support hardware miss to tc action

[Bartlomiej Zolnierkiewicz]

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

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

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

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

Title:
  net/sched: cls_api: Support hardware miss to tc action

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

Bug description:
  * Explain the bug(s)
   
  Currently tc miss interface only supports resuming from a specific tc chain.
  If a packet modification is done before a missable action such as CT and
  there is a miss in CT after it, this may cause a miss match when resuming
  re-executing the same chain in software, and wrong packet count.
  This use case for example is a stateless (static) nat.
   
  * brief explanation of fixes
   
  Add support for missing to a specific action instance, and support
  of per action hardware stats to update what was actually done in hardware.
   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.
  Enable HW offload and configure regular connection tracking OpenFlow rules
  with packet modification before the CT action (such as statless nat):

   
  e.g:

  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
 ovs-ofctl add-flow br-ovs "in_port=1,table=0, ip,ct_state=-trk 
actions=mod_nw_dst=1.1.1.2,ct(table=1)"
  ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+new 
actions=ct(commit),output:2"
  ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+est, 
actions=output:2"
  ovs-ofctl add-flow br-ovs "in_port=2,table=0, ip,ct_state=-trk 
actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "in_port=2,table=1, ip,ct_state=+trk+est, 
actions=mod_nw_src=1.1.1.2,output:1"

   
  Config VF1 ip 1.1.1.1, VF2 ip 1.1.1.2

  For VF2, add route and static neighbour to floating (router) ip
  5.5.5.5

  
  Then run a TCP connection, e.g:

  on mlx5 VF1 iperf -s   #(which will listen on 1.1.1.2)
  on mlx5 VF2 iperf -c 5.5.5.5 -t 10#(this creates a packet from 1.1.1.1 -> 
5.5.5.5, and nat will change this to 1.1.1.1->1.1.1.2)

  
  Optional: In different terminal, while traffic is running, check for offload:
  tcpdump -nnepi  tcp
  and see no iperf tcp packets.

  Dump conntrack with relevant ip:
  cat /proc/net/nf_conntrack | grep -i  1.1.1.1

  See tuples were offloaded:
  ipv4 2 tcp  6 src= 1.1.1.1 dst=1.1.1.2 sport=56394 dport=5001 
packets=2 bytes=112 src=1.1.1.2 dst=1.1.1.1 sport=5001 dport=56394 packets=1777 
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3

  
  * What it could break.
  offload for modifications + ct and tc packet count.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012571/+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 2003547] Re: [23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2)

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2304

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

Title:
  [23.04] net/smc: Alibaba patches about tunable buffer sizes may cause
  errors and need to be removed (kernel 6.2)

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

Bug description:
  There are two patches about tunable buffer sizes that are changing the
  conventional behavior in our SMC code.

  This change of behavior might not be expected by our clients, which could 
lead to problems.
  Therefore, we need to remove these two patches from v6.2 / lunar, until we 
can provide an appropriate solution.

  The two patches to be removed depend on each other, but don't have any
  further dependencies to other code/commits.

  Please remove / revert the following two patches:

  0227f058aa29 net/smc: Unbind r/w buffer size from clcsock and make them 
tunable
  77eee3251431 net/smc: Introduce a specific sysctl for TEST_LINK time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003547/+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 2012571] Re: net/sched: cls_api: Support hardware miss to tc action

[Bartlomiej Zolnierkiewicz]

Patches to revert this functionality have been submitted using the same
BugLink and applied in linux-bluefield/5.4.0-1062.68 to fix the
regression.

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

Title:
  net/sched: cls_api: Support hardware miss to tc action

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

Bug description:
  * Explain the bug(s)
   
  Currently tc miss interface only supports resuming from a specific tc chain.
  If a packet modification is done before a missable action such as CT and
  there is a miss in CT after it, this may cause a miss match when resuming
  re-executing the same chain in software, and wrong packet count.
  This use case for example is a stateless (static) nat.
   
  * brief explanation of fixes
   
  Add support for missing to a specific action instance, and support
  of per action hardware stats to update what was actually done in hardware.
   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.
  Enable HW offload and configure regular connection tracking OpenFlow rules
  with packet modification before the CT action (such as statless nat):

   
  e.g:

  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
 ovs-ofctl add-flow br-ovs "in_port=1,table=0, ip,ct_state=-trk 
actions=mod_nw_dst=1.1.1.2,ct(table=1)"
  ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+new 
actions=ct(commit),output:2"
  ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+est, 
actions=output:2"
  ovs-ofctl add-flow br-ovs "in_port=2,table=0, ip,ct_state=-trk 
actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "in_port=2,table=1, ip,ct_state=+trk+est, 
actions=mod_nw_src=1.1.1.2,output:1"

   
  Config VF1 ip 1.1.1.1, VF2 ip 1.1.1.2

  For VF2, add route and static neighbour to floating (router) ip
  5.5.5.5

  
  Then run a TCP connection, e.g:

  on mlx5 VF1 iperf -s   #(which will listen on 1.1.1.2)
  on mlx5 VF2 iperf -c 5.5.5.5 -t 10#(this creates a packet from 1.1.1.1 -> 
5.5.5.5, and nat will change this to 1.1.1.1->1.1.1.2)

  
  Optional: In different terminal, while traffic is running, check for offload:
  tcpdump -nnepi  tcp
  and see no iperf tcp packets.

  Dump conntrack with relevant ip:
  cat /proc/net/nf_conntrack | grep -i  1.1.1.1

  See tuples were offloaded:
  ipv4 2 tcp  6 src= 1.1.1.1 dst=1.1.1.2 sport=56394 dport=5001 
packets=2 bytes=112 src=1.1.1.2 dst=1.1.1.1 sport=5001 dport=56394 packets=1777 
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3

  
  * What it could break.
  offload for modifications + ct and tc packet count.

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


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

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

[Samer Attrah]

Hello,

I have the same problem and I followed the instructions in #19 and rebooted but 
the camera still not working.
I have: acer aspire A715-51G and the camera is: 0408:4033 Quanta Computer, Inc. 
ACER HD User Facing

and what I get on the following commands are:

sudo dmesg | grep uvc
# nothing


sudo rmmod uvcvideo && sudo modprobe uvcvideo -vv 
rmmod: ERROR: Module uvcvideo is not currently loaded


uname -r
5.19.0-42-generic

Please help, I need my camera so much and will be happy to provide more
details if needed

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

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


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


  -kindly ASK

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

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

  
  BR
  Giuliano

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

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

[Kernel-packages] [Bug 1970603] Re: DSI touchscreen not working with KMS under 5.15

[Launchpad Bug Tracker]

This bug was fixed in the package linux-raspi - 5.15.0-1029.31

---
linux-raspi (5.15.0-1029.31) jammy; urgency=medium

  * jammy/linux-raspi: 5.15.0-1029.31 -proposed tracker (LP: #2016543)

  * DSI touchscreen not working with KMS under 5.15 (LP: #1970603)
- [Packaging] raspi: Include rpi-panel-attiny-regulator module in linux-
  modules

  [ Ubuntu: 5.15.0-72.79 ]

  * jammy/linux: 5.15.0-72.79 -proposed tracker (LP: #2016548)
  * Add split lock detection for EMR (LP: #2015855)
- x86/split_lock: Enumerate architectural split lock disable bit
  *  selftest: fib_tests: Always cleanup before exit  (LP: #2015956)
- selftest: fib_tests: Always cleanup before exit
  * Add support for intel EMR cpu (LP: #2015372)
- platform/x86: intel-uncore-freq: add Emerald Rapids support
- perf/x86/intel/cstate: Add Emerald Rapids
- perf/x86/rapl: Add support for Intel Emerald Rapids
- intel_idle: add Emerald Rapids Xeon support
- tools/power/x86/intel-speed-select: Add Emerald Rapid quirk
- tools/power turbostat: Introduce support for EMR
- powercap: intel_rapl: add support for Emerald Rapids
- EDAC/i10nm: Add Intel Emerald Rapids server support
  * Kernel livepatch ftrace graph fix (LP: #2013603)
- kprobes: treewide: Remove trampoline_address from
  kretprobe_trampoline_handler()
- kprobes: treewide: Make it harder to refer kretprobe_trampoline directly
- kprobes: Add kretprobe_find_ret_addr() for searching return address
- s390/unwind: recover kretprobe modified return address in stacktrace
- s390/unwind: fix fgraph return address recovery
  * Jammy update: v5.15.98 upstream stable release (LP: #2015600)
- Linux 5.15.98
  * Jammy update: v5.15.97 upstream stable release (LP: #2015599)
- ionic: refactor use of ionic_rx_fill()
- Fix XFRM-I support for nested ESP tunnels
- arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc
- ARM: dts: rockchip: add power-domains property to dp node on rk3288
- HID: elecom: add support for TrackBall 056E:011C
- ACPI: NFIT: fix a potential deadlock during NFIT teardown
- btrfs: send: limit number of clones and allocated memory size
- ASoC: rt715-sdca: fix clock stop prepare timeout issue
- IB/hfi1: Assign npages earlier
- neigh: make sure used and confirmed times are valid
- HID: core: Fix deadloop in hid_apply_multiplier.
- x86/cpu: Add Lunar Lake M
- staging: mt7621-dts: change palmbus address to lower case
- bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state
- net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from 
sk_stream_kill_queues().
- vc_screen: don't clobber return value in vcs_read
- scripts/tags.sh: Invoke 'realpath' via 'xargs'
- scripts/tags.sh: fix incompatibility with PCRE2
- usb: dwc3: pci: add support for the Intel Meteor Lake-M
- USB: serial: option: add support for VW/Skoda "Carstick LTE"
- usb: gadget: u_serial: Add null pointer check in gserial_resume
- USB: core: Don't hold device lock while reading the "descriptors" sysfs 
file
- Linux 5.15.97
  * Jammy update: v5.15.96 upstream stable release (LP: #2015595)
- drm/etnaviv: don't truncate physical page address
- wifi: rtl8xxxu: gen2: Turn on the rate control
- drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink
- clk: mxl: Switch from direct readl/writel based IO to regmap based IO
- clk: mxl: Remove redundant spinlocks
- clk: mxl: Add option to override gate clks
- clk: mxl: Fix a clk entry by adding relevant flags
- powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G
- clk: mxl: syscon_node_to_regmap() returns error pointers
- random: always mix cycle counter in add_latent_entropy()
- KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception
- KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid
- can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len
- powerpc: dts: t208x: Disable 10G on MAC1 and MAC2
- powerpc: use generic version of arch_is_kernel_initmem_freed()
- powerpc/vmlinux.lds: Ensure STRICT_ALIGN_SIZE is at least page aligned
- powerpc/vmlinux.lds: Add an explicit symbol for the SRWX boundary
- powerpc/64s/radix: Fix crash with unaligned relocated kernel
- powerpc/64s/radix: Fix RWX mapping with relocated kernel
- drm/i915/gvt: fix double free bug in split_2MB_gtt_entry
- uaccess: Add speculation barrier to copy_from_user()
- binder: read pre-translated fds from sender buffer
- binder: defer copies of pre-patched txn data
- binder: fix pointer cast warning
- binder: Address corner cases in deferred copy and fixup
- binder: Gracefully handle BINDER_TYPE_FDA objects with num_fds=0
- nbd: fix possible overflow on 'first_minor' in nbd_dev_add()
- wifi: mwifiex: Add missing compatible string for SD8787
- audit: update the mailing list in MAINTAINERS
- ext4: Fix 

[Kernel-packages] [Bug 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability

[Steve Beattie]

This issue was introduced in fce96cf04430 ("virt: Add SEV-SNP guest
driver") and thus affects 5.19 kernels and newer.

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

Title:
  Fix (+follow-up) needed for SEV-SNP vulnerability

Status in linux package in Ubuntu:
  Incomplete
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  From email discussions with Dionna Glazee from Google:

  
  > This email details a critical vulnerability in SEV-SNP attestation
  > report integrity protection that must be patched in SEV-SNP-enabled
  > kernels.
  >
  > I'm reaching out since I've been tracking our progress towards a
  > stable offering of customer access to SEV-SNP "guest requests". I'd
  > like to know how or if y'all test the /dev/sev-guest driver.
  >
  > The reason I ask is because our host KVM injects failures into the
  > guest if requests come too frequently. Test suites that request
  > attestation reports in quick succession will fail without very recent
  > patches or workaround code in user space.
  >
  > Technical details, tl;dr
  > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa
  > that will cause attestation to fail frequently (in GCE). Peter found
  > and patched this vulnerability.
  >
  > Details of security patch 47894e0fa:
  > This patch to sev-guest causes more fail-closed situations. All VMM
  > errors other than INVALID_LEN will wipe out the VMPCK and close the
  > guest's ability to communicate with the security processor.
  > Ratelimit failures will also cause a fail-closed situation.
  >
  > As you may know, guest requests are encrypted by the guest with
  > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory
  > to the host's KVM. KVM forwards that to the crypto/ccp driver to
  > deliver to the AMD secure processor to respond to. When the VMM
  > returns an error instead of forwarding a request to the secure
  > processor, then the guest driver *does not* increment its IV. It can
  > therefore reuse an IV on multiple messages with different contents.
  > This breaks AES_GCM's security guarantees.
  >
  > Ratelimiting looks to the guest not as a stalled vCPU, but rather a
  > special error response that AMD will include in their next published
  > version of the GHCB protocol (I believe v2.02). This allows the guest
  > VM to schedule other threads and remain productive while waiting up to
  > 2 seconds for a request to be serviced. The special error code to an
  > unpatched kernel is just forwarded to the guest as an EIO. User space
  > may continue to issue requests, even if it is unsafe to do so.

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


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

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

[Giuliano Lotta]

@Samer
please download the script at
https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/blob/main/compile_module.sh

give it right permission and run it.
I use it for every kernel update and it works.

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

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


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


  -kindly ASK

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

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

  
  BR
  Giuliano

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

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

[Kernel-packages] [Bug 2015293] Re: netfilter: ctnetlink: Support offloaded conntrack entry deletion

[Feysel Mohammed]

Hello,

Using 5.4.0-1062-bluefield, conntrack -F properly flushes the tuples.

Thanks,

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

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

Title:
  netfilter: ctnetlink: Support offloaded conntrack entry deletion

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

Bug description:
  * Explain the bug(s)
   
  conntrack -D or conntrack -F doesn't delete offloaded tuples.
   
  * brief explanation of fixes
   
  Add support for to delete offloaded tuples via netlink interface and
  userspace conntrack utility.
   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.

  Enable HW offload and configure regular connection tracking OpenFlow
  rules:


  e.g:

  ovs-ofctl del-flows br-ovs

  ovs-ofctl add-flow br-ovs arp,actions=normal

  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk
  actions=ct(table=1)"

  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new
  actions=ct(commit),normal"

  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est,
  actions=normal"


  Run a UDP connection, e.g:
  on mlx5 VF1 iperf -s -u
  on mlx5 VF2 iperf -c  -u -t 10 
   

  Optional: In different terminal, while traffic is running, check for
  offload:

  tcpdump -nnepi  udp
  and see no iperf udp packets.
   

  Dump conntrack with relevant ip:

  cat /proc/net/nf_conntrack | grep -i 
   

  See tuples were offloaded:
  ipv4 2 udp 17 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 
bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3
   
  Flush the tuples:
  conntrack -F
   
  Verify tuples are deleted:
  cat /proc/net/nf_conntrack | grep -i 


  Before fix, the above tuple shows again,

  after fix, it's deleted, and shows nothing.

   
  * What it could break.


  Conntrack -F / -D not working on offloaded tuples.

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


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

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

[Samer Attrah]

@Giuliano

thanks, but I just did and the camera still not working after reboot.

Any other ideas, or what to do now?

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

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


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


  -kindly ASK

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

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

  
  BR
  Giuliano

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

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  

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

[Ivan Hu]

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

Title:
  Add some ACPI device IDs for Intel HID device

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:
  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 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:
  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]
  Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake

  [Fix]
  ACPI devices IDs are add the the related Intel HID devices on these platforms 
can work.

  [Test]
  Verified the Intel HID events can work such as power button for suspend and 
wake.
   
  [Where problems could occur]
  Add the ACPI device IDs for support Intel HID devices, so chance of problems 
should be low.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 2019915

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-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2019915

Title:
  Enable audio LEDs on HP laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

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

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

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

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

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


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

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

[Ubuntu SRU Bot]

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

adv-17v35x/unknown (arm64)
backport-iwlwifi-dkms/unknown (arm64)
bbswitch/0.8-14ubuntu1 (arm64)
ddcci-driver-linux/unknown (arm64)
digimend-dkms/unknown (arm64)
dm-writeboost/unknown (arm64)
dpdk-kmods/unknown (arm64)
evdi/unknown (arm64)
falcosecurity-libs/unknown (arm64)
glibc/unknown (arm64)
iptables-netflow/unknown (arm64)
jool/unknown (arm64)
langford/unknown (arm64)
librem-ec-acpi/unknown (arm64)
nvidia-graphics-drivers-515-server/unknown (arm64)
openafs/unknown (arm64)
openvpn-dco-dkms/unknown (arm64)
r8125/unknown (arm64)
r8168/unknown (arm64)
rapiddisk/unknown (arm64)
systemd/unknown (arm64)
west-chamber/unknown (arm64)
xilinx-runtime/unknown (arm64)


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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

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

[AceLan Kao]

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

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

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

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

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

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

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

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

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

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

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


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

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

[Kai-Heng Feng]

Public bug reported:

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

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

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

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

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

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

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux-oem-6.1 (Ubuntu Jammy)
 Importance: Undecided
 Status: Confirmed

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => Won't Fix

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

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

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

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

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

Title:
  Enable audio LEDs on HP laptops

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

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

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

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

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

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


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

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

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-2015730 stella

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

Title:
  Enable audio LEDs on HP laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

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

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

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

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

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


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

[Kernel-packages] [Bug 2019450] Re: zfs-linux FTBFS with v6.2.8 stable updates

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 2.1.9-2ubuntu2

---
zfs-linux (2.1.9-2ubuntu2) mantic; urgency=medium

  * Cherry-pick upstream fix to address FTBFS with v6.2.8+. LP: #2019450

 -- Dimitri John Ledkov   Sat, 13 May 2023
00:49:15 +0100

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

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

Title:
  zfs-linux FTBFS with v6.2.8 stable updates

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

Bug description:
  [ Impact ]

   * Stable kernel updates changed signature of a function call, thus
  zfs-linux needs adapting. Otherwise it fallsback to older symbols,
  which are GPL only.

  [ Test Plan ]

   * linux 6.2 with 6.2.8 stable updates builds with zfs, without this
  fix build fails with

MODPOST <>/build/zfs/2.1.9/build/module/Module.symvers
  ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 
'bio_start_io_acct'
  ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 
'bio_end_io_acct_remapped'
  make[5]: *** [scripts/Makefile.modpost:138: 
<>/build/zfs/2.1.9/build/module/Module.symvers] Error 1

  as the signature of the non-gpl function call has changed, zfs
  configure scripts fail to detect it as available, fallback on a gpl
  symbol, which we then prohibit from using.

  [ Where problems could occur ]

   * This is a cherry-pick of build-compat only, without any other
  changes

  [ Other Info ]

   * Upstream commit

  
https://github.com/openzfs/zfs/pull/14677/commits/1a951502f0b4200a13f23f0d2f5759ef60188c17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2019450/+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 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19

[Po-Hsu Lin]

No PowerPC for linux-nvidia-5.19/5.19.0-1009.9

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

Title:
  powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  When trying to build powerpc tests from ubuntu_kernel_selftests, it 
  will fail with:
  inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3:
  /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may 
be used uninitialized [-Werror=maybe-uninitialized]
     86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack 
());
    | ^~~
  cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’:
  cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here
     25 | uint64_t val, expected[2], actual;
    | ^~
  cc1: all warnings being treated as errors

  [Fix]
  * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning"
  This patch can be cherry-picked into Kinetic kernel.

  [Test]
  Apply this patch to the kernel tree and build it with:
  sudo make -C linux/tools/testing/selftests TARGETS=powerpc

  With this error fixed, test compliation can finish without any issue.

  [Where problems could occur]
  Change for test case, no impact to acutal function.

  [Original Bug Report]
  Issue found with K-5.19.0-28-generic on P9 node baltar

  This should not be considered as a regression since
  ubuntu_kernel_selftests will be blocked by the net test crash before
  this powerpc tests can be started. This was found by manually running
  the test.

  Test build failed with:
  gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
  -m64   -no-pie  cycles_with_mmcr2_test.c ../../harness.c ../../utils.c 
../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test
  In file included from /usr/include/stdio.h:906,
   from cycles_with_mmcr2_test.c:6:
  In function ‘printf’,
  inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3:
  /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may 
be used uninitialized [-Werror=maybe-uninitialized]
     86 |   return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack 
());
    |  
^~~
  cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’:
  cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here
     25 | uint64_t val, expected[2], actual;
    |^~
  cc1: all warnings being treated as errors
  make[3]: *** [../../../lib.mk:173: 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test]
 Error 1

  Please find attachment for the complete build log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+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 2000709] Re: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19

[Po-Hsu Lin]

Verified with linux-azure/5.19.0-1023.24 and linux-aws/5.19.0-1023.24,
this cmsg_ipv6.sh has passed without any issue.

** Tags removed: verification-needed-kinetic
** Tags added: 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/2000709

Title:
  net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  Issue found with 5.19.0-28.29

  Running 'make run_tests -C net TEST_PROGS=cmsg_ipv6.sh TEST_GEN_PROGS='' 
TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
 INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: cmsg_ipv6.sh
   #   Case TCLASS UDP setsock - packet data returned 1, expected 0
   #   Case TCLASS ICMP setsock - packet data returned 1, expected 0
   #   Case TCLASS RAW setsock - packet data returned 1, expected 0
   #   Case TCLASS UDP cmsg - packet data returned 1, expected 0 
   #   Case TCLASS ICMP cmsg - packet data returned 1, expected 0
   #   Case TCLASS RAW cmsg - packet data returned 1, expected 0 
   #   Case TCLASS UDP both - packet data returned 1, expected 0 
   #   Case TCLASS ICMP both - packet data returned 1, expected 0
   #   Case TCLASS RAW both - packet data returned 1, expected 0 
   #   Case TCLASS UDP diff - packet data returned 1, expected 0 
   #   Case TCLASS ICMP diff - packet data returned 1, expected 0
   #   Case TCLASS RAW diff - packet data returned 1, expected 0 
   #   Case HOPLIMIT UDP setsock - packet data returned 1, expected 0
   #   Case HOPLIMIT ICMP setsock - packet data returned 1, expected 0
   #   Case HOPLIMIT RAW setsock - packet data returned 1, expected 0
   #   Case HOPLIMIT UDP cmsg - packet data returned 1, expected 0 
   #   Case HOPLIMIT ICMP cmsg - packet data returned 1, expected 0
   #   Case HOPLIMIT RAW cmsg - packet data returned 1, expected 0 
   #   Case HOPLIMIT UDP both - packet data returned 1, expected 0 
   #   Case HOPLIMIT ICMP both - packet data returned 1, expected 0
   #   Case HOPLIMIT RAW both - packet data returned 1, expected 0 
   #   Case HOPLIMIT UDP diff - packet data returned 1, expected 0 
   #   Case HOPLIMIT ICMP diff - packet data returned 1, expected 0
   #   Case HOPLIMIT RAW diff - packet data returned 1, expected 0 
   # FAIL - 24/93 cases failed
   not ok 1 selftests: net: cmsg_ipv6.sh # exit=1

  
  This is not a regression as the net test build was blocked with bug 1993155

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000709/+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 1983180]

[temporalcoldwar24]

Hi, got this again after a Ubuntu update that overwrote my "acpi=off"
grub kernel parameter. For anyone that can't boot into the login screen
then adding this is the fix.

CPU: Q9650

MB: G41MT-S2PT

BTW the last half of the reports below are after I hit the power button
to initiate what would normally be an ACPI shut down. I had to keep the
power button held down to force power off.

Cheers.

[
0.333629] ACPI Error: Aborting method _PR.CPU1..
_PDC due to previous error
(AE ALREADY EXISTS) (20221020/psparse-529)
[
0.3336291 ACPI Error: AE_ALREADY_EXISTS, SSDT Ox910E80D15200 Table is a 
ready loaded (20221020/tbdata-548)
[
0.333629] ACPI Error: Aborting method _PR. CPUZ._PDC due to previous error
(AE _ALREADY _EXISTS) (20221020/psparse-529)
[
0.3336291 ACPI Error: AF
ALREADY_EXISTS, SSDT Ox910E80D14600 Table is a
ready loaded (20221020/tbdata-548)
г
0.3336291 ACPI Error: Aborting method _PR.CPU3..
_PDC due to previous error
(AE_ALREADY _EXISTS) (20221020/psparse-529)

60.8740511 ru: INFO: ru_preempt detected
stalls on CPUs/tasks:
[
60.8743431 rcu: 01-..
1: (0 ticks this GP) idle=4a60/0/0x0 softirq=15/15 fqs
=0 (false positive?)
60.875?361 rcu: rcu_preempt kthread timer wakeup didn't happen for 15001 jif 
fies! g-1031 f0x0 RU_GP_WAIT_FQS(5) -›state=0x402
[
60.876242] ru: oFossible timer handling issue on cpu-1 timer-softirg-5
г
60.8765361 rcu: rcu_preempt kthread stared for 15002 jiffies g-1031 fOx0 R
CU_GP_WAIT_FQS(5) -›state=0x402 ->cpu=1
[
60.8769991 rcu: Unless ru_preempt kthread gets sufficient CPU time, 00M is now 
expected behauior.
[
60.8773991 ru: RCU grace-period kthread stack dump:
[
60.8780471 rcu: Stack dump where RCU GP kthread last ran:

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

Title:
  ACPI Error _CPC not found

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

Bug description:
  just recently (I guess since the last update) I get a few ACPI error
  messages during start up. Those are also visible with dmesg:

  ...
  [0.713907] ACPI: AC: AC Adapter [AC] (on-line)
  [0.713978] input: Sleep Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
  [0.714011] ACPI: button: Sleep Button [SLPB]
  [0.714040] input: Lid Switch as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  [0.714061] ACPI: button: Lid Switch [LID]
  [0.714087] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  [0.714105] ACPI: button: Power Button [PWRF]
  [0.714187] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.714199] No Local Variables are initialized for Method [_CPC]
  [0.714201] No Arguments are initialized for method [_CPC]
  [0.714203] ACPI Error: Aborting method \_SB.PR01._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.714395] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.714404] No Local Variables are initialized for Method [_CPC]
  [0.714405] No Arguments are initialized for method [_CPC]
  [0.714407] ACPI Error: Aborting method \_SB.PR02._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.714480] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.714488] No Local Variables are initialized for Method [_CPC]
  [0.714490] No Arguments are initialized for method [_CPC]
  [0.714492] ACPI Error: Aborting method \_SB.PR03._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.714640] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.714651] No Local Variables are initialized for Method [_CPC]
  [0.714653] No Arguments are initialized for method [_CPC]
  [0.714655] ACPI Error: Aborting method \_SB.PR04._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.714940] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.714952] No Local Variables are initialized for Method [_CPC]
  [0.714953] No Arguments are initialized for method [_CPC]
  [0.714955] ACPI Error: Aborting method \_SB.PR05._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.715106] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.715118] No Local Variables are initialized for Method [_CPC]
  [0.715119] No Arguments are initialized for method [_CPC]
  [0.715121] ACPI Error: Aborting method \_SB.PR06._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.715309] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.715321] No Local 

[Kernel-packages] [Bug 1981783]

[temporalcoldwar24]

Hi, got this again after a Ubuntu update that overwrote my "acpi=off"
grub kernel parameter. For anyone that can't boot into the login screen
then adding this is the fix.

CPU: Q9650

MB: G41MT-S2PT

BTW the last half of the reports below are after I hit the power button
to initiate what would normally be an ACPI shut down. I had to keep the
power button held down to force power off.

Cheers.

[
0.333629] ACPI Error: Aborting method _PR.CPU1..
_PDC due to previous error
(AE ALREADY EXISTS) (20221020/psparse-529)
[
0.3336291 ACPI Error: AE_ALREADY_EXISTS, SSDT Ox910E80D15200 Table is a 
ready loaded (20221020/tbdata-548)
[
0.333629] ACPI Error: Aborting method _PR. CPUZ._PDC due to previous error
(AE _ALREADY _EXISTS) (20221020/psparse-529)
[
0.3336291 ACPI Error: AF
ALREADY_EXISTS, SSDT Ox910E80D14600 Table is a
ready loaded (20221020/tbdata-548)
г
0.3336291 ACPI Error: Aborting method _PR.CPU3..
_PDC due to previous error
(AE_ALREADY _EXISTS) (20221020/psparse-529)

60.8740511 ru: INFO: ru_preempt detected
stalls on CPUs/tasks:
[
60.8743431 rcu: 01-..
1: (0 ticks this GP) idle=4a60/0/0x0 softirq=15/15 fqs
=0 (false positive?)
60.875?361 rcu: rcu_preempt kthread timer wakeup didn't happen for 15001 jif 
fies! g-1031 f0x0 RU_GP_WAIT_FQS(5) -›state=0x402
[
60.876242] ru: oFossible timer handling issue on cpu-1 timer-softirg-5
г
60.8765361 rcu: rcu_preempt kthread stared for 15002 jiffies g-1031 fOx0 R
CU_GP_WAIT_FQS(5) -›state=0x402 ->cpu=1
[
60.8769991 rcu: Unless ru_preempt kthread gets sufficient CPU time, 00M is now 
expected behauior.
[
60.8773991 ru: RCU grace-period kthread stack dump:
[
60.8780471 rcu: Stack dump where RCU GP kthread last ran:

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

Title:
  there is an ACPI error message every time it booting

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

Bug description:
  there is the following message every time it boots

  [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol
  [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529)

  [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous
  error (AE_NOT_FOUND (20210730/psargs-529)

  [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol
  [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529)

  [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous
  error (AE_NOT_FOUND (20210730/psargs-529)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.38
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 15 11:15:30 2022
  InstallationDate: Installed on 2022-04-21 (85 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Giuliano Lotta]

@Samer
I see you have camera 0408:4033 (mine is 0408:4035)

I've now included also your model in the .c source file.


Please download again the *.c file from github and recompile it using the bash 
script *.sh (I also updated the script yesterday)

BR
Giuliano

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

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


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


  -kindly ASK

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

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

  
  BR
  Giuliano

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

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

[Kernel-packages] [Bug 2018335] Re: Regression - battery drain on suspend

[Kishore]

I think I am facing the same issue with my Asus Vivibook S3402. This
laptop had a keyboard detection issue with stock kernel in kubuntu 22.10
which was fixed using a patched kernel. It still had this battery drain
issue then. Later the signed kernel (5.19.0-27) that came in through the
proposed repositories fixed both issues. Now, upgrading the kubuntu
23.04 with kernel 6.2.0-20, the battery drain on suspend has come back.

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

Title:
  Regression - battery drain on suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is a regression in the kernel somewhere between: linux-
  image-5.19.0-21-generic and linux-image-5.19.0-41-generic that is
  causing battery drain on an HP Spectre x360 Convertible 14-ea1xxx.

  
  I am attaching the logs from running this tool: 
https://github.com/intel/S0ixSelftestTool on both kernels.

  I have tested this with the kernel from Ubuntu 23.04 (version 6.2) and
  the mainline kernel 6.3 and the results are the same as linux-
  image-5.19.0-41-generic - zero s0ix residence.

  I am also attaching the output from:

  sudo cat /sys/kernel/debug/pmc_core/pch_ip_power_gating_status

  I think the key line is:

  PCH IP: 6  - SPCState: On

  This never turns to Off on the newer kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-41-generic 5.19.0-41.42
  ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kstoilov   1848 F pipewire
kstoilov   1852 F wireplumber
   /dev/snd/seq:kstoilov   1848 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  2 22:41:42 2023
  InstallationDate: Installed on 2023-04-30 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: HP HP Spectre x360 Convertible 14-ea1xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-41-generic N/A
   linux-backports-modules-5.19.0-41-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2023
  dmi.bios.release: 15.29
  dmi.bios.vendor: AMI
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89DB
  dmi.board.vendor: HP
  dmi.board.version: 40.65
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 40.65
  dmi.modalias: 
dmi:bvnAMI:bvrF.29:bd03/17/2023:br15.29:efr40.65:svnHP:pnHPSpectrex360Convertible14-ea1xxx:pvr:rvnHP:rn89DB:rvr40.65:cvnHP:ct31:cvrChassisVersion:sku457Q6AVT#ABA:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 14-ea1xxx
  dmi.product.sku: 457Q6AVT#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018335/+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 2015440] Re: fib_tests.sh in ubuntu_kernel_selftests was skipped silently on Focal

[Po-Hsu Lin]

This issue is still visible on:
* f/aws-fips 5.4.0-1102.110+fips1
* f/azure-fips 5.4.0-1108.114+fips1

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

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

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

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

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

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

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

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

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

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


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