[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146669.html 
(linux-firmware/jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146670.html 
(linux-firmware/mantic)

** Description changed:

  [SRU Justification]
+ 
+ == linux-firmware ==
+ 
+ [Impact]
+ 
+ Missing firmware for Intel BE200 on Intel Meteor Lake platform.
+ 
+ [Fix]
+ 
+ 2 upstream commits needed, and the iwlwifi firmware one is in the pull request
+ for bug 2037390 (Add firmware for Intel CNVi AX211 on Intel Meteor Lake
+ platform). Rebased the second one onto PR for bug 2037390.
+ 
+ [Test Case]
+ 
+ Boot with firmware blobs installed, and iwlwifi and btintel should probe
+ successfully without error.
+ 
+ [Where problems could occur]
+ 
+ While this introduces support for new hardware on new platforms, expect every
+ possible problem.
+ 
+ [Other Info]
+ 
+ We're to support oem-6.5/jammy, and mantic for best effort. While there is no
+ Noble branch yet, Noble is not nominated.
+ 
+ While this is rebased onto PR for bug 2037390, it makes that PR a prerequisite
+ to this one.
+ 
+ == kernel ==
  
  [Impact]
  
  Missing Intel Gale Peak WiFi/Bluetooth support.
  
  [Fix]
  
  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
   crash") [v6.5-rc2]
  b. firmware (to be released):
-- ES
-      - iwlwifi-gl-b0-fm-b0-83.ucode
-      - iwlwifi-gl-b0-fm-b0.pnvm
-- QS
-      - iwlwifi-gl-c0-fm-c0-83.ucode
-      - iwlwifi-gl-c0-fm-c0.pnvm
+    - ES
+  - iwlwifi-gl-b0-fm-b0-83.ucode
+  - iwlwifi-gl-b0-fm-b0.pnvm
+    - QS
+  - iwlwifi-gl-c0-fm-c0-83.ucode
+  - iwlwifi-gl-c0-fm-c0.pnvm
  
  Bluetooth:
  a. kernel driver:
     - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
     - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
-- ES
-      - intel/ibt-0191-0191.sfi
-      - intel/ibt-0191-0191.ddc
-- QS
-      - intel/ibt-0291-0291.sfi
-      - intel/ibt-0291-0291.ddc
+    - ES
+  - intel/ibt-0191-0191.sfi
+  - intel/ibt-0191-0191.ddc
+    - QS
+  - intel/ibt-0291-0291.sfi
+  - intel/ibt-0291-0291.ddc
  
  [Test Case]
  
  To boot with patched kernel and prereleased firmware blob and check basic
  WiFi/Bluetooth functions.
  
  [Where problems could occur]
  
  New device. Expect incomplete functions and bugs.
  
  [Other Info]
  
  Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.
  
  = original bug report ==
  
  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix 
crash") [v6.5-rc2]
  b. firmware (to be released):
     - iwlwifi-gl-b0-fm-b0-83.ucode
     - iwlwifi-gl-b0-fm-b0.pnvm
  
  Bluetooth:
  a. kernel driver:
     - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
     - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
     - intel/ibt-0191-0191.sfi
     - intel/ibt-0191-0191.ddc

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

Title:
  Support for Intel Discrete Gale Peak2/BE200

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  == linux-firmware ==

  [Impact]

  Missing firmware for Intel BE200 on Intel Meteor Lake platform.

  [Fix]

  2 upstream commits needed, and the iwlwifi firmware one is in the pull request
  for bug 2037390 (Add firmware for Intel CNVi AX211 on Intel Meteor Lake
  platform). Rebased the second one onto PR for bug 2037390.

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort. While there is no
  Noble branch yet, Noble is not nominated.

  While this is rebased onto PR for bug 2037390, it makes that PR a prerequisite
  to this one.

  == kernel ==

  [Impact]

  Missing Intel Gale Peak WiFi/Bluetooth support.

  [Fix]

  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' confi

[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146667.html 
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146668.html 
(mantic)

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

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Triaged => In Progress

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

** Changed in: linux-firmware (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Mantic)
   Status: Triaged => In Progress

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

** Changed in: linux-firmware (Ubuntu Mantic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform.
+ 
+   iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
+   iwlwifi :00:14.3: no suitable firmware found!
+   iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
+   iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
+   iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
+ 
+ And Bluetooth:
+ 
+   Bluetooth: hci0: Failed to load Intel firmware file
+ intel/ibt-0180-0041.sfi (-2)
+ 
+ [Fix]
+ 
+ 3 upstream commits needed.
+ 
+ For the first commit for iwlwifi, it supports both AX211 and BE200 (for bug
+ 2028065).
+ 
+ [Test Case]
+ 
+ Boot with firmware blobs installed, and iwlwifi and btintel should probe
+ successfully without error.
+ 
+ [Where problems could occur]
+ 
+ While this introduces support for new hardware on new platforms, expect every
+ possible problem.
+ 
+ [Other Info]
+ 
+ We're to support oem-6.5/jammy, and mantic for best effort. While there is no
+ Noble branch yet, Noble is not nominated.
+ 
+ == original bug report ==
+ 
  WIFI FW:
-   Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
-   Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
-   Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
-   Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
-   Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
+   Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
+   Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
+   Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
+   Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
+   Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
  
  Bluetooth FW:
-   Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
- --- 
+   Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-jiayi-jammy-amd64-20230706-44
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-06 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-jiayi-jammy-amd64-20230706-44
  MachineType: Intel Corporation Meteor Lake Client Platform
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem 
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linu

[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200

[You-Sheng Yang]

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

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

** Changed in: linux-firmware (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

** Changed in: linux-firmware (Ubuntu Mantic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

Title:
  Support for Intel Discrete Gale Peak2/BE200

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing Intel Gale Peak WiFi/Bluetooth support.

  [Fix]

  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
   crash") [v6.5-rc2]
  b. firmware (to be released):
 - ES
   - iwlwifi-gl-b0-fm-b0-83.ucode
       - iwlwifi-gl-b0-fm-b0.pnvm
 - QS
   - iwlwifi-gl-c0-fm-c0-83.ucode
       - iwlwifi-gl-c0-fm-c0.pnvm

  Bluetooth:
  a. kernel driver:
     - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
     - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
 - ES
   - intel/ibt-0191-0191.sfi
       - intel/ibt-0191-0191.ddc
 - QS
   - intel/ibt-0291-0291.sfi
       - intel/ibt-0291-0291.ddc

  [Test Case]

  To boot with patched kernel and prereleased firmware blob and check basic
  WiFi/Bluetooth functions.

  [Where problems could occur]

  New device. Expect incomplete functions and bugs.

  [Other Info]

  Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.

  = original bug report ==

  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix 
crash") [v6.5-rc2]
  b. firmware (to be released):
     - iwlwifi-gl-b0-fm-b0-83.ucode
     - iwlwifi-gl-b0-fm-b0.pnvm

  Bluetooth:
  a. kernel driver:
     - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
     - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
     - intel/ibt-0191-0191.sfi
     - intel/ibt-0191-0191.ddc

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028065/+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 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

Hi, I'm focusing on resolving all issues caused by structural changes
rather than solely ensuring the crash utility functions across different
kernel versions. The patch set will be extensive and require additional
time for backporting and testing. I'll provide the new patch as soon as
possible.

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
 

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

[Ante Karamatić]

Another +1 on -proposed mutter. It solves the problem for me too.

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

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

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

Bug description:
  [ Impact ]

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

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

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

  [ Where problems could occur ]

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

  [ Original Description ]

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

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

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in ipu6-drivers source package in Mantic:
  New
Status in ivsc-driver source package in Mantic:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  In Progress
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already, and IPU6 ISYS is under upstream review. More components
  to come according to Intel.

  These two fixes are therefore for related components for not-yet fully
  upstreamed IPU6 as needed for out-of-tree dkms drivers.

  [Test Case]

  ```
  $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU"
  $ sudo dmesg | grep 

[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on

[koba]

** Description changed:

  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.
  
  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
  Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.
  
+ [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814
+ 
  [where the issue could happen]
  Medium, may have the regression but the risk is limited in some Dell 
platforms.
  we will ask Realtek's effort once the regression is observed.

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

Title:
  Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle
  screen on

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

Bug description:
  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.

  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
  Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.

  [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814

  [where the issue could happen]
  Medium, may have the regression but the risk is limited in some Dell 
platforms.
  we will ask Realtek's effort once the regression is observed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on

[koba]

** Summary changed:

- Fix CPU C-state alway keep at C3 when system run PHM with idle screen on
+ Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on

** Description changed:

  [Impact]
+ RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.
  
  [Fix]
+ Realtek r8168h/r8111's ASPM is blocked due to users report the regression
  
  [where the issue could happen]
  Medium,

** Description changed:

  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.
  
  [Fix]
- Realtek r8168h/r8111's ASPM is blocked due to users report the regression
+ Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
+ Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.
  
  [where the issue could happen]
- Medium,
+ Medium, may have the regression but the risk is limited in some Dell 
platforms.
+ we will ask Realtek's effort once the regression is observed.

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

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

** Tags added: oem-priority originate-from-2038398 somerville

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

Title:
  Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle
  screen on

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

Bug description:
  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.

  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
  Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.

  [where the issue could happen]
  Medium, may have the regression but the risk is limited in some Dell 
platforms.
  we will ask Realtek's effort once the regression is observed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042385] Re: Fix CPU C-state alway keep at C3 when system run PHM with idle screen on

[koba]

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

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

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

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

Title:
  Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle
  screen on

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.

  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression

  [where the issue could happen]
  Medium,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042385/+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 2042385] [NEW] Fix CPU C-state alway keep at C3 when system run PHM with idle screen on

[koba]

Public bug reported:

[Impact]

[Fix]

[where the issue could happen]
Medium,

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

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

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

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

Title:
  Fix CPU C-state alway keep at C3 when system run PHM with idle screen
  on

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  [Impact]

  [Fix]

  [where the issue could happen]
  Medium,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042385/+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 2028065] Re: Support for Intel Discrete Gale Peak2/BE200

[You-Sheng Yang]

** Description changed:

  [SRU Justification]
  
  [Impact]
  
  Missing Intel Gale Peak WiFi/Bluetooth support.
  
  [Fix]
  
  WIFI:
  a. kernel driver :
-- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
-  crash") [v6.5-rc2]
+    - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
+  crash") [v6.5-rc2]
  b. firmware (to be released):
-- iwlwifi-gl-b0-fm-b0-83.ucode
-- iwlwifi-gl-b0-fm-b0.pnvm
+- ES
+      - iwlwifi-gl-b0-fm-b0-83.ucode
+      - iwlwifi-gl-b0-fm-b0.pnvm
+- QS
+      - iwlwifi-gl-c0-fm-c0-83.ucode
+      - iwlwifi-gl-c0-fm-c0.pnvm
  
  Bluetooth:
  a. kernel driver:
-- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
-- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
+    - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
+    - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
-- intel/ibt-0191-0191.sfi
-- intel/ibt-0191-0191.ddc
+- ES
+      - intel/ibt-0191-0191.sfi
+      - intel/ibt-0191-0191.ddc
+- QS
+      - intel/ibt-0291-0291.sfi
+      - intel/ibt-0291-0291.ddc
  
  [Test Case]
  
  To boot with patched kernel and prereleased firmware blob and check basic
  WiFi/Bluetooth functions.
  
  [Where problems could occur]
  
  New device. Expect incomplete functions and bugs.
  
  [Other Info]
  
  Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.
  
  = original bug report ==
  
  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix 
crash") [v6.5-rc2]
  b. firmware (to be released):
     - iwlwifi-gl-b0-fm-b0-83.ucode
     - iwlwifi-gl-b0-fm-b0.pnvm
  
  Bluetooth:
  a. kernel driver:
     - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
     - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
     - intel/ibt-0191-0191.sfi
     - intel/ibt-0191-0191.ddc

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

Title:
  Support for Intel Discrete Gale Peak2/BE200

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Incomplete
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing Intel Gale Peak WiFi/Bluetooth support.

  [Fix]

  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
   crash") [v6.5-rc2]
  b. firmware (to be released):
 - ES
   - iwlwifi-gl-b0-fm-b0-83.ucode
       - iwlwifi-gl-b0-fm-b0.pnvm
 - QS
   - iwlwifi-gl-c0-fm-c0-83.ucode
       - iwlwifi-gl-c0-fm-c0.pnvm

  Bluetooth:
  a. kernel driver:
     - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
     - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
 - ES
   - intel/ibt-0191-0191.sfi
       - intel/ibt-0191-0191.ddc
 - QS
   - intel/ibt-0291-0291.sfi
       - intel/ibt-0291-0291.ddc

  [Test Case]

  To boot with patched kernel and prereleased firmware blob and check basic
  WiFi/Bluetooth functions.

  [Where problems could occur]

  New device. Expect incomplete functions and bugs.

  [Other Info]

  Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.

  = original bug report ==

  WIFI:
  a. kernel driver :
     - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix 
crash") [v6.5-rc2]
  b. firmware (to be released):
     - iwlwifi-gl-b0-fm-b0-83.ucode
     - iwlwifi-gl-b0-fm-b0.pnvm

  Bluetooth:
  a. kernel driver:
     - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
     - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
  b. firmware (to be released):
     - intel/ibt-0191-0191.sfi
     - intel/ibt-0191-0191.ddc

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028065/+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 2039601] Re: [ kernel 6.5 regression ] nvme not working on some laptops

[Eric Rouleau]

the issue seems fixed with latest kernel 6.5.0.12

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

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

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

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

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

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

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

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


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

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

[Bug Watch Updater]

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

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 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-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2034477]

[ertugruluyar.personal]

I forgot to add a link to the issue. 
https://bugzilla.kernel.org/show_bug.cgi?id=218092

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 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-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2034477]

[ertugruluyar.personal]

(In reply to Mario Limonciello (AMD) from comment #89)
> You have a different issue, please open a separate one.

I opened a different issue, but I was not sure which context should I
choose for this. So I choose Kernel. If anyone help, I appreciate.

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 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-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2034477]

[suroto]

#86.  Fixed.

Thank you very much to Mario, Hans

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 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-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2034477]

[ertugruluyar.personal]

(In reply to Mario Limonciello (AMD) from comment #89)
> You have a different issue, please open a separate one.

Okay, but I have a similar issue that when I suspend my laptop and woke
up the laptop, it is hanging on black screen and I have to force to
shutdown laptop by hold pressed button on keyboard. Unless I add
amd_iommu=off to my grub file. If it is really so different issue, I'am
gonna open a new issue. Could you help me?

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 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-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 1989983] Re: kinetic: apply new apparmor and LSM stacking patch set

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2 
verification-needed-jammy-linux-nvidia-6.5

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

Title:
  kinetic: apply new apparmor and LSM stacking patch set

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

Bug description:
  [Impact]

  Align with the latest apparmor and LSM stacking versions.

  To do so we need to:
   - revert sauce to get back to upstream apparmor, and drop old LSM stacking
   - pull in needed patches from upstream 6.0
   - pull in needed patches from apparmor-next 6.1

  This is required to properly support apparmor in Ubuntu.

  [Test case]

  We test apparmor in our RT suite.

  [Regression potential]

  We may see breakage in the apparmor tests after applying this patch
  set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989983/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2 
verification-needed-jammy-linux-nvidia-6.5

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

Title:
  udev fails to make prctl() syscall with apparmor=0 (as used by maas by
  default)

Status in AppArmor:
  Fix Released
Status in MAAS:
  Fix Released
Status in maas-images:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in apparmor source package in Lunar:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in systemd source package in Lunar:
  Invalid

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
/run/net6
  -*.conf
  :: 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
fsverity
  =yes
  shfs
  :: mount_squash downloading 
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
  wget: can't connect to remote host (10.229.32.21): Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
  done.

  Still gathering logs and info and will update as I go.

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2017903] Re: LSM stacking and AppArmor for 6.2: additional fixes

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2 
verification-needed-jammy-linux-nvidia-6.5

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

Title:
  LSM stacking and AppArmor for 6.2: additional fixes

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

Bug description:
  [Impact]

  We maintain custom LSM stacking and AppArmor SAUCE patches in our
  kernel to provide additional features that are not available in the
  upstream AppArmor.

  We have experienced occasional bugs in the lunar kernel (specifically
  with the environ.sh test) that can lead to system crashes / failures
  (such as potential NULL pointer dereference).

  [Test case]

  Run AppArmor autopkgtest / qa-regression-testing.

  [Fix]

  Apply the following additional fixes provided by AppArmor upstream
  maintainer:

UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa
UBUNTU: SAUCE: apparmor: fix profile verification and enable it
UBUNTU: SAUCE: apparmor: fix: add missing failure check in 
compute_xmatch_perms
UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas

  [Regression potential]

  Additional fixes are touching only AppArmor specific code, so we may
  experience regressions (bugs / behavior change) only in apparmor by
  applying them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+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 2028253] Re: update apparmor and LSM stacking patch set

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2 
verification-needed-jammy-linux-nvidia-6.5

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

Title:
  update apparmor and LSM stacking patch set

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

Bug description:
  [Impact]

  Provide an updated patch set for apparmor / LSM stacking with all the
  custom features that we need in the Ubuntu kernel.

  This patch set is required to provide the proper confinement with
  snaps and other Ubuntu-specific security features.

  [Fix]

  Apply the latest updated patch set from:

   https://gitlab.com/jjohansen/apparmor-kernel

  [Test case]

  Run the apparmor test case suite.

  [Regression potential]

  This patch set introduces significant non-upstream changes to the
  security layer, so we may expect generic regressions in the kernel,
  especially running applications that are stressing the security layer
  (such as systemd, snapd, lxd, etc.).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028253/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2 
verification-needed-jammy-linux-nvidia-6.5

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

Title:
  Disable restricting unprivileged change_profile by default, due to LXD
  latest/stable not yet compatible with this new apparmor feature

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2035373] Re: Move nbd module into modules (from -extra)

[Launchpad Bug Tracker]

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

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

  * jammy/linux-raspi: 5.15.0-1042.45 -proposed tracker (LP: #2038050)

  * Include USB drivers in linux-modules (LP: #2037938)
- [Packaging] raspi: Include most USB modules in linux-modules

  * Exclude DRM drivers from linux-modules (LP: #2037936)
- [Packaging] raspi: Exclude unlikely DRM modules from linux-modules

  * pi-kernel snap is missing modules for microk8s/microceph on UC22
(LP: #2036747)
- [Packaging] raspi: Include rbd and vxlan modules in linux-modules

  * Move nbd module into modules (from -extra) (LP: #2035373)
- [Packaging] raspi: Include nbd module in linux-modules

  [ Ubuntu: 5.15.0-88.98 ]

  * jammy/linux: 5.15.0-88.98 -proposed tracker (LP: #2038055)
  * CVE-2023-4244
- netfilter: nf_tables: don't skip expired elements during walk
- netfilter: nf_tables: adapt set backend to use GC transaction API
- netfilter: nft_set_hash: mark set element as dead when deleting from 
packet
  path
- netfilter: nf_tables: GC transaction API to avoid race with control plane
- netfilter: nf_tables: remove busy mark and gc batch API
- netfilter: nf_tables: don't fail inserts if duplicate has expired
- netfilter: nf_tables: fix kdoc warnings after gc rework
- netfilter: nf_tables: fix GC transaction races with netns and netlink 
event
  exit path
- netfilter: nf_tables: GC transaction race with netns dismantle
- netfilter: nf_tables: GC transaction race with abort path
- netfilter: nf_tables: use correct lock to protect gc_list
- netfilter: nf_tables: defer gc run if previous batch is still pending
- netfilter: nft_dynset: disallow object maps
- netfilter: nft_set_rbtree: skip sync GC for new elements in this 
transaction
  * CVE-2023-42756
- netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
  * CVE-2023-4623
- net/sched: sch_hfsc: Ensure inner classes have fsc curve
  * PCI BARs larger than 128GB are disabled (LP: #2037403)
- PCI: Support BAR sizes up to 8TB
  * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077)
- ALSA: hda/realtek - ALC287 I2S speaker platform support
  * Check for changes relevant for security certifications (LP: #1945989)
- [Packaging] Add a new fips-checks script
  * Jammy update: v5.15.126 upstream stable release (LP: #2037593)
- io_uring: gate iowait schedule on having pending requests
- perf: Fix function pointer case
- net/mlx5: Free irqs only on shutdown callback
- arm64: errata: Add workaround for TSB flush failures
- arm64: errata: Add detection for TRBE write to out-of-range
- [Config] updateconfigs for ARM64_ERRATUM_ and
  ARM64_WORKAROUND_TSB_FLUSH_FAILURE
- iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982
- iommu/arm-smmu-v3: Document MMU-700 erratum 2812531
- iommu/arm-smmu-v3: Add explicit feature for nesting
- iommu/arm-smmu-v3: Document nesting-related errata
- arm64: dts: imx8mn-var-som: add missing pull-up for onboard PHY reset 
pinmux
- word-at-a-time: use the same return type for has_zero regardless of
  endianness
- KVM: s390: fix sthyi error handling
- wifi: cfg80211: Fix return value in scan logic
- net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx
- net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer()
- bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing
- rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length
- net: dsa: fix value check in bcm_sf2_sw_probe()
- perf test uprobe_from_different_cu: Skip if there is no gcc
- net: sched: cls_u32: Fix match key mis-addressing
- mISDN: hfcpci: Fix potential deadlock on &hc->lock
- qed: Fix kernel-doc warnings
- qed: Fix scheduling in a tasklet while getting stats
- net: annotate data-races around sk->sk_max_pacing_rate
- net: add missing READ_ONCE(sk->sk_rcvlowat) annotation
- net: add missing READ_ONCE(sk->sk_sndbuf) annotation
- net: add missing READ_ONCE(sk->sk_rcvbuf) annotation
- net: add missing data-race annotations around sk->sk_peek_off
- net: add missing data-race annotation for sk_ll_usec
- net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
- bpf, cpumap: Handle skb as well when clean up ptr_ring
- bpf: sockmap: Remove preempt_disable in sock_map_sk_acquire
- net: ll_temac: Switch to use dev_err_probe() helper
- net: ll_temac: fix error checking of irq_of_parse_and_map()
- net: korina: handle clk prepare error in korina_probe()
- net: netsec: Ignore 'phy-mode' on SynQuacer in DT mode
- net: dcb: choose correct policy to parse DCB_ATTR_BCN
- s390/qeth: Don't call dev_close/dev_open (DOWN/UP)
- ip6mr: Fix skb_under_panic in ip6mr_cache_report()
- vxlan: Fix nexthop hash size
- net/mlx5: fs_co

[Kernel-packages] [Bug 2036747] Re: pi-kernel snap is missing modules for microk8s/microceph on UC22

[Launchpad Bug Tracker]

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

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

  * jammy/linux-raspi: 5.15.0-1042.45 -proposed tracker (LP: #2038050)

  * Include USB drivers in linux-modules (LP: #2037938)
- [Packaging] raspi: Include most USB modules in linux-modules

  * Exclude DRM drivers from linux-modules (LP: #2037936)
- [Packaging] raspi: Exclude unlikely DRM modules from linux-modules

  * pi-kernel snap is missing modules for microk8s/microceph on UC22
(LP: #2036747)
- [Packaging] raspi: Include rbd and vxlan modules in linux-modules

  * Move nbd module into modules (from -extra) (LP: #2035373)
- [Packaging] raspi: Include nbd module in linux-modules

  [ Ubuntu: 5.15.0-88.98 ]

  * jammy/linux: 5.15.0-88.98 -proposed tracker (LP: #2038055)
  * CVE-2023-4244
- netfilter: nf_tables: don't skip expired elements during walk
- netfilter: nf_tables: adapt set backend to use GC transaction API
- netfilter: nft_set_hash: mark set element as dead when deleting from 
packet
  path
- netfilter: nf_tables: GC transaction API to avoid race with control plane
- netfilter: nf_tables: remove busy mark and gc batch API
- netfilter: nf_tables: don't fail inserts if duplicate has expired
- netfilter: nf_tables: fix kdoc warnings after gc rework
- netfilter: nf_tables: fix GC transaction races with netns and netlink 
event
  exit path
- netfilter: nf_tables: GC transaction race with netns dismantle
- netfilter: nf_tables: GC transaction race with abort path
- netfilter: nf_tables: use correct lock to protect gc_list
- netfilter: nf_tables: defer gc run if previous batch is still pending
- netfilter: nft_dynset: disallow object maps
- netfilter: nft_set_rbtree: skip sync GC for new elements in this 
transaction
  * CVE-2023-42756
- netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
  * CVE-2023-4623
- net/sched: sch_hfsc: Ensure inner classes have fsc curve
  * PCI BARs larger than 128GB are disabled (LP: #2037403)
- PCI: Support BAR sizes up to 8TB
  * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077)
- ALSA: hda/realtek - ALC287 I2S speaker platform support
  * Check for changes relevant for security certifications (LP: #1945989)
- [Packaging] Add a new fips-checks script
  * Jammy update: v5.15.126 upstream stable release (LP: #2037593)
- io_uring: gate iowait schedule on having pending requests
- perf: Fix function pointer case
- net/mlx5: Free irqs only on shutdown callback
- arm64: errata: Add workaround for TSB flush failures
- arm64: errata: Add detection for TRBE write to out-of-range
- [Config] updateconfigs for ARM64_ERRATUM_ and
  ARM64_WORKAROUND_TSB_FLUSH_FAILURE
- iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982
- iommu/arm-smmu-v3: Document MMU-700 erratum 2812531
- iommu/arm-smmu-v3: Add explicit feature for nesting
- iommu/arm-smmu-v3: Document nesting-related errata
- arm64: dts: imx8mn-var-som: add missing pull-up for onboard PHY reset 
pinmux
- word-at-a-time: use the same return type for has_zero regardless of
  endianness
- KVM: s390: fix sthyi error handling
- wifi: cfg80211: Fix return value in scan logic
- net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx
- net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer()
- bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing
- rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length
- net: dsa: fix value check in bcm_sf2_sw_probe()
- perf test uprobe_from_different_cu: Skip if there is no gcc
- net: sched: cls_u32: Fix match key mis-addressing
- mISDN: hfcpci: Fix potential deadlock on &hc->lock
- qed: Fix kernel-doc warnings
- qed: Fix scheduling in a tasklet while getting stats
- net: annotate data-races around sk->sk_max_pacing_rate
- net: add missing READ_ONCE(sk->sk_rcvlowat) annotation
- net: add missing READ_ONCE(sk->sk_sndbuf) annotation
- net: add missing READ_ONCE(sk->sk_rcvbuf) annotation
- net: add missing data-race annotations around sk->sk_peek_off
- net: add missing data-race annotation for sk_ll_usec
- net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
- bpf, cpumap: Handle skb as well when clean up ptr_ring
- bpf: sockmap: Remove preempt_disable in sock_map_sk_acquire
- net: ll_temac: Switch to use dev_err_probe() helper
- net: ll_temac: fix error checking of irq_of_parse_and_map()
- net: korina: handle clk prepare error in korina_probe()
- net: netsec: Ignore 'phy-mode' on SynQuacer in DT mode
- net: dcb: choose correct policy to parse DCB_ATTR_BCN
- s390/qeth: Don't call dev_close/dev_open (DOWN/UP)
- ip6mr: Fix skb_under_panic in ip6mr_cache_report()
- vxlan: Fix nexthop hash size
- net/mlx5: fs_co

[Kernel-packages] [Bug 2037936] Re: Exclude DRM drivers from linux-modules

[Launchpad Bug Tracker]

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

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

  * jammy/linux-raspi: 5.15.0-1042.45 -proposed tracker (LP: #2038050)

  * Include USB drivers in linux-modules (LP: #2037938)
- [Packaging] raspi: Include most USB modules in linux-modules

  * Exclude DRM drivers from linux-modules (LP: #2037936)
- [Packaging] raspi: Exclude unlikely DRM modules from linux-modules

  * pi-kernel snap is missing modules for microk8s/microceph on UC22
(LP: #2036747)
- [Packaging] raspi: Include rbd and vxlan modules in linux-modules

  * Move nbd module into modules (from -extra) (LP: #2035373)
- [Packaging] raspi: Include nbd module in linux-modules

  [ Ubuntu: 5.15.0-88.98 ]

  * jammy/linux: 5.15.0-88.98 -proposed tracker (LP: #2038055)
  * CVE-2023-4244
- netfilter: nf_tables: don't skip expired elements during walk
- netfilter: nf_tables: adapt set backend to use GC transaction API
- netfilter: nft_set_hash: mark set element as dead when deleting from 
packet
  path
- netfilter: nf_tables: GC transaction API to avoid race with control plane
- netfilter: nf_tables: remove busy mark and gc batch API
- netfilter: nf_tables: don't fail inserts if duplicate has expired
- netfilter: nf_tables: fix kdoc warnings after gc rework
- netfilter: nf_tables: fix GC transaction races with netns and netlink 
event
  exit path
- netfilter: nf_tables: GC transaction race with netns dismantle
- netfilter: nf_tables: GC transaction race with abort path
- netfilter: nf_tables: use correct lock to protect gc_list
- netfilter: nf_tables: defer gc run if previous batch is still pending
- netfilter: nft_dynset: disallow object maps
- netfilter: nft_set_rbtree: skip sync GC for new elements in this 
transaction
  * CVE-2023-42756
- netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
  * CVE-2023-4623
- net/sched: sch_hfsc: Ensure inner classes have fsc curve
  * PCI BARs larger than 128GB are disabled (LP: #2037403)
- PCI: Support BAR sizes up to 8TB
  * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077)
- ALSA: hda/realtek - ALC287 I2S speaker platform support
  * Check for changes relevant for security certifications (LP: #1945989)
- [Packaging] Add a new fips-checks script
  * Jammy update: v5.15.126 upstream stable release (LP: #2037593)
- io_uring: gate iowait schedule on having pending requests
- perf: Fix function pointer case
- net/mlx5: Free irqs only on shutdown callback
- arm64: errata: Add workaround for TSB flush failures
- arm64: errata: Add detection for TRBE write to out-of-range
- [Config] updateconfigs for ARM64_ERRATUM_ and
  ARM64_WORKAROUND_TSB_FLUSH_FAILURE
- iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982
- iommu/arm-smmu-v3: Document MMU-700 erratum 2812531
- iommu/arm-smmu-v3: Add explicit feature for nesting
- iommu/arm-smmu-v3: Document nesting-related errata
- arm64: dts: imx8mn-var-som: add missing pull-up for onboard PHY reset 
pinmux
- word-at-a-time: use the same return type for has_zero regardless of
  endianness
- KVM: s390: fix sthyi error handling
- wifi: cfg80211: Fix return value in scan logic
- net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx
- net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer()
- bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing
- rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length
- net: dsa: fix value check in bcm_sf2_sw_probe()
- perf test uprobe_from_different_cu: Skip if there is no gcc
- net: sched: cls_u32: Fix match key mis-addressing
- mISDN: hfcpci: Fix potential deadlock on &hc->lock
- qed: Fix kernel-doc warnings
- qed: Fix scheduling in a tasklet while getting stats
- net: annotate data-races around sk->sk_max_pacing_rate
- net: add missing READ_ONCE(sk->sk_rcvlowat) annotation
- net: add missing READ_ONCE(sk->sk_sndbuf) annotation
- net: add missing READ_ONCE(sk->sk_rcvbuf) annotation
- net: add missing data-race annotations around sk->sk_peek_off
- net: add missing data-race annotation for sk_ll_usec
- net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
- bpf, cpumap: Handle skb as well when clean up ptr_ring
- bpf: sockmap: Remove preempt_disable in sock_map_sk_acquire
- net: ll_temac: Switch to use dev_err_probe() helper
- net: ll_temac: fix error checking of irq_of_parse_and_map()
- net: korina: handle clk prepare error in korina_probe()
- net: netsec: Ignore 'phy-mode' on SynQuacer in DT mode
- net: dcb: choose correct policy to parse DCB_ATTR_BCN
- s390/qeth: Don't call dev_close/dev_open (DOWN/UP)
- ip6mr: Fix skb_under_panic in ip6mr_cache_report()
- vxlan: Fix nexthop hash size
- net/mlx5: fs_co

[Kernel-packages] [Bug 2037938] Re: Include USB drivers in linux-modules

[Launchpad Bug Tracker]

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

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

  * jammy/linux-raspi: 5.15.0-1042.45 -proposed tracker (LP: #2038050)

  * Include USB drivers in linux-modules (LP: #2037938)
- [Packaging] raspi: Include most USB modules in linux-modules

  * Exclude DRM drivers from linux-modules (LP: #2037936)
- [Packaging] raspi: Exclude unlikely DRM modules from linux-modules

  * pi-kernel snap is missing modules for microk8s/microceph on UC22
(LP: #2036747)
- [Packaging] raspi: Include rbd and vxlan modules in linux-modules

  * Move nbd module into modules (from -extra) (LP: #2035373)
- [Packaging] raspi: Include nbd module in linux-modules

  [ Ubuntu: 5.15.0-88.98 ]

  * jammy/linux: 5.15.0-88.98 -proposed tracker (LP: #2038055)
  * CVE-2023-4244
- netfilter: nf_tables: don't skip expired elements during walk
- netfilter: nf_tables: adapt set backend to use GC transaction API
- netfilter: nft_set_hash: mark set element as dead when deleting from 
packet
  path
- netfilter: nf_tables: GC transaction API to avoid race with control plane
- netfilter: nf_tables: remove busy mark and gc batch API
- netfilter: nf_tables: don't fail inserts if duplicate has expired
- netfilter: nf_tables: fix kdoc warnings after gc rework
- netfilter: nf_tables: fix GC transaction races with netns and netlink 
event
  exit path
- netfilter: nf_tables: GC transaction race with netns dismantle
- netfilter: nf_tables: GC transaction race with abort path
- netfilter: nf_tables: use correct lock to protect gc_list
- netfilter: nf_tables: defer gc run if previous batch is still pending
- netfilter: nft_dynset: disallow object maps
- netfilter: nft_set_rbtree: skip sync GC for new elements in this 
transaction
  * CVE-2023-42756
- netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
  * CVE-2023-4623
- net/sched: sch_hfsc: Ensure inner classes have fsc curve
  * PCI BARs larger than 128GB are disabled (LP: #2037403)
- PCI: Support BAR sizes up to 8TB
  * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077)
- ALSA: hda/realtek - ALC287 I2S speaker platform support
  * Check for changes relevant for security certifications (LP: #1945989)
- [Packaging] Add a new fips-checks script
  * Jammy update: v5.15.126 upstream stable release (LP: #2037593)
- io_uring: gate iowait schedule on having pending requests
- perf: Fix function pointer case
- net/mlx5: Free irqs only on shutdown callback
- arm64: errata: Add workaround for TSB flush failures
- arm64: errata: Add detection for TRBE write to out-of-range
- [Config] updateconfigs for ARM64_ERRATUM_ and
  ARM64_WORKAROUND_TSB_FLUSH_FAILURE
- iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982
- iommu/arm-smmu-v3: Document MMU-700 erratum 2812531
- iommu/arm-smmu-v3: Add explicit feature for nesting
- iommu/arm-smmu-v3: Document nesting-related errata
- arm64: dts: imx8mn-var-som: add missing pull-up for onboard PHY reset 
pinmux
- word-at-a-time: use the same return type for has_zero regardless of
  endianness
- KVM: s390: fix sthyi error handling
- wifi: cfg80211: Fix return value in scan logic
- net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx
- net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer()
- bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing
- rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length
- net: dsa: fix value check in bcm_sf2_sw_probe()
- perf test uprobe_from_different_cu: Skip if there is no gcc
- net: sched: cls_u32: Fix match key mis-addressing
- mISDN: hfcpci: Fix potential deadlock on &hc->lock
- qed: Fix kernel-doc warnings
- qed: Fix scheduling in a tasklet while getting stats
- net: annotate data-races around sk->sk_max_pacing_rate
- net: add missing READ_ONCE(sk->sk_rcvlowat) annotation
- net: add missing READ_ONCE(sk->sk_sndbuf) annotation
- net: add missing READ_ONCE(sk->sk_rcvbuf) annotation
- net: add missing data-race annotations around sk->sk_peek_off
- net: add missing data-race annotation for sk_ll_usec
- net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
- bpf, cpumap: Handle skb as well when clean up ptr_ring
- bpf: sockmap: Remove preempt_disable in sock_map_sk_acquire
- net: ll_temac: Switch to use dev_err_probe() helper
- net: ll_temac: fix error checking of irq_of_parse_and_map()
- net: korina: handle clk prepare error in korina_probe()
- net: netsec: Ignore 'phy-mode' on SynQuacer in DT mode
- net: dcb: choose correct policy to parse DCB_ATTR_BCN
- s390/qeth: Don't call dev_close/dev_open (DOWN/UP)
- ip6mr: Fix skb_under_panic in ip6mr_cache_report()
- vxlan: Fix nexthop hash size
- net/mlx5: fs_co

[Kernel-packages] [Bug 2042357] Re: Merge crash 8.0.3 into Noble

[Mauricio Faria de Oliveira]

The package built successfully in a PPA with all supported architectures 
(!riscv64).
Now waiting on the Debian issue with the gdb-10.2.tar.gz tarball to be 
addressed.

Test build in ppa:mfo/noble-crash,

```
crash (8.0.3-1ubuntu1+gdb102targz.2) noble; urgency=medium

  * Merge with Debian unstable. Remaining changes: (LP: #2042357)
- d/t/live: If the "live" autopkgtest fails with a recommendation
  to try /proc/kcore instead of the default, attempt that before
  failing the test. [7.2.6-1ubuntu1]
- d/t/live: Fix logic issue in "live" autopkgtest introduced in
   the last upload. [7.2.6-1ubuntu2]
- d/t/live: Fix test, as if will return 0 when no cases were true.
  [7.2.8-1ubuntu1]
- d/t/control: Add linux-libc-dev dependency for the autopkg test.
  This package gets usually broken with kernel upgrades, so let it
  already show in the autopkg test. [7.2.9-2ubuntu3]
- d/t/control: Run autopkg test with allow-stderr. [8.0.0-1ubuntu1]
  * Dropped changes:
- Build without lto. Fails to build gdb on ppc64el. That should be
  fixed, once gdb is updated to a more recent version (e.g. 10.x).
  [7.2.9-2ubuntu2]
  * Added changes:
- d/p/0002-Fix-compilation-error-due-to-new-strlcpy-function.patch:
  Fix FTBFS due to strlcpy() introduced in glibc 2.38.

crash (8.0.3-1) unstable; urgency=medium

  * New upstream (Closes: #1054805)
  * https://github.com/crash-utility/crash/compare/8.0.2...8.0.3

 -- Mauricio Faria de Oliveira   Tue, 31 Oct 2023 14:09:03 
-0300
```

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

Title:
  Merge crash 8.0.3 into Noble

Status in crash package in Ubuntu:
  In Progress
Status in crash package in Debian:
  New

Bug description:
  Work in progress; testing changes on PPA.

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2042363] [NEW] AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 s

[bugproxy]

Public bug reported:

---Problem Description---
AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl(). NFS server is 
Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not 
appear to affect other combinations of NFS client (including AIX 7.2) with this 
NFS server.

The AIX team have indicated that the cause of the EIO is triggered by the NFS 
server returning a BAD_SEQID error which leads to the AIX NFS client 
incorrectly zeroing the stateid, which then leads to the NFS server returning a 
BAD_STATEID error and the NFS client then returns the EIO error. The AIX team 
would like to understand why the BAD_SEQID has been returned.
 
---uname output---
Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
 
Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 
2.30GHz  

---Steps to Reproduce---
 We cannot offer a simple way to recreate the problem as it involves IBM MQ 
running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 
storage.

However, we can provide any requested trace or dumps from any or all of
the involved machines.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-x8664 bugnameltc-203937 severity-high 
targetmilestone-inin2004

** Tags added: architecture-x8664 bugnameltc-203937 severity-high
targetmilestone-inin2004

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  AIX 7.3 NFS client frequently returns an EIO error to an application
  when reading or writing to a file that has been locked with fcntl() on
  a Ubuntu 20.04 NFSV4 server

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl(). NFS server is 
Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not 
appear to affect other combinations of NFS client (including AIX 7.2) with this 
NFS server.

  The AIX team have indicated that the cause of the EIO is triggered by the NFS 
server returning a BAD_SEQID error which leads to the AIX NFS client 
incorrectly zeroing the stateid, which then leads to the NFS server returning a 
BAD_STATEID error and the NFS client then returns the EIO error. The AIX team 
would like to understand why the BAD_SEQID has been returned.
   
  ---uname output---
  Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
   
  Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 
2.30GHz  

  ---Steps to Reproduce---
   We cannot offer a simple way to recreate the problem as it involves IBM MQ 
running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 
storage.

  However, we can provide any requested trace or dumps from any or all
  of the involved machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+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 2042363] [NEW] AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 s

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---
AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl(). NFS server is 
Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not 
appear to affect other combinations of NFS client (including AIX 7.2) with this 
NFS server.

The AIX team have indicated that the cause of the EIO is triggered by the NFS 
server returning a BAD_SEQID error which leads to the AIX NFS client 
incorrectly zeroing the stateid, which then leads to the NFS server returning a 
BAD_STATEID error and the NFS client then returns the EIO error. The AIX team 
would like to understand why the BAD_SEQID has been returned.
 
---uname output---
Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
 
Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 
2.30GHz  

---Steps to Reproduce---
 We cannot offer a simple way to recreate the problem as it involves IBM MQ 
running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 
storage.

However, we can provide any requested trace or dumps from any or all of
the involved machines.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-x8664 bugnameltc-203937 severity-high 
targetmilestone-inin2004
-- 
AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl() on a Ubuntu 
20.04 NFSV4 server
https://bugs.launchpad.net/bugs/2042363
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Erich Eickmeyer]

Thank you for reporting this and helping make Ubuntu better. Could you
please boot into a Ubuntu kernel (not third party kernel) and execute
the following command only once, as it will automatically gather
debugging information, in a terminal:

apport-collect 2011385

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Erich Eickmeyer]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We need some more information from you before we can
start working on this bug.

Please include the information requested from the "Reporting Sound Bugs"
section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate
attachments.

This information can be gathered for you automatically by using the following 
command only once:
apport-collect -p alsa-base 2011385

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

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2039378] Re: Screen goes blank

[stef]

I have similar problems with a lenovo m625q with Stoney graphics: 
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Stoney 
[Radeon R2/R3/R4/R5 Graphics] (rev d4)
Since 5.15.0-86 (Ubuntu 20.04 HWE):
After entering the password in the dm and mate startup, the machine crashes.
A twin system without graphic login works with out issues.

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

Title:
  Screen goes blank

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Screen goes blank after the desktop environment gets loaded. I use the 
cinnamon desktop. After I type in the user password at the display-manager to 
login, the desktop shows for 1 second and then the screen goes blank. I solved 
the problem through switching the desktop to cinnamon (software rendering) at 
the display-manager and then installed 6.2.0-34-generic instead of 5.15.0-86 to 
be able to use the normal cinnamon desktop again.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1277 F pulseaudio
   /dev/snd/controlC0:  user   1277 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 21.2
  InstallationDate: Installed on 2023-08-07 (71 days ago)
  InstallationMedia: Linux Mint 21.2 "Victoria" - Release amd64 20230711
  MachineType: LENOVO 20KDS01T00
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic 
root=UUID=27a26739-8f56-4f8e-b127-efffca9d526f ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-86-generic N/A
   linux-backports-modules-5.15.0-86-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.21
  Tags:  victoria
  Uname: Linux 5.15.0-86-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/13/2021
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0NET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KDS01T00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0NET46W(1.24):bd04/13/2021:br1.24:efr1.16:svnLENOVO:pn20KDS01T00:pvrThinkPadA275:rvnLENOVO:rn20KDS01T00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KD_BU_Think_FM_ThinkPadA275:
  dmi.product.family: ThinkPad A275
  dmi.product.name: 20KDS01T00
  dmi.product.sku: LENOVO_MT_20KD_BU_Think_FM_ThinkPad A275
  dmi.product.version: ThinkPad A275
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039378/+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 2042361] [NEW] Ubuntu crashes and reboot while using blender

[Thiago Nunes Costa]

Public bug reported:

Ubuntu is frequently crashing while using Blender, UPBGE, Inkscape, or
Gimp. Sometimes I've just opened the software with nothing on the
project screen and the SO crashes.

Other times, I experience problems with interface rendering. Some areas
of the screen turn completely gray or black.

I tried to use nvidia-drivers-525, nvidia-drivers-535, and  nvidia-
drivers-545, all with the same results.

OS info:
Description:Ubuntu 22.04.3 LTS
Release:22.04

Video card:
NVIDIA GeForce RTX 3060 Laptop GPU

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-525 (not installed)
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 31 16:04:21 2023
InstallationDate: Installed on 2022-08-26 (430 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: nvidia-graphics-drivers-525
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Ubuntu crashes and reboot while using blender

Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New

Bug description:
  Ubuntu is frequently crashing while using Blender, UPBGE, Inkscape, or
  Gimp. Sometimes I've just opened the software with nothing on the
  project screen and the SO crashes.

  Other times, I experience problems with interface rendering. Some
  areas of the screen turn completely gray or black.

  I tried to use nvidia-drivers-525, nvidia-drivers-535, and  nvidia-
  drivers-545, all with the same results.

  OS info:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Video card:
  NVIDIA GeForce RTX 3060 Laptop GPU

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-525 (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 16:04:21 2023
  InstallationDate: Installed on 2022-08-26 (430 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: nvidia-graphics-drivers-525
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2042361/+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 2042357] Re: Merge crash 8.0.3 into Noble

[Bug Watch Updater]

** Changed in: crash (Debian)
   Status: Unknown => New

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

Title:
  Merge crash 8.0.3 into Noble

Status in crash package in Ubuntu:
  In Progress
Status in crash package in Debian:
  New

Bug description:
  Work in progress; testing changes on PPA.

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2042357] Re: Merge crash 8.0.3 into Noble

[Mauricio Faria de Oliveira]

** Bug watch added: Debian Bug tracker #1054805
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054805

** Also affects: crash via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054805
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #1055117
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055117

** Also affects: crash (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055117
   Importance: Unknown
   Status: Unknown

** No longer affects: crash

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

Title:
  Merge crash 8.0.3 into Noble

Status in crash package in Ubuntu:
  In Progress
Status in crash package in Debian:
  New

Bug description:
  Work in progress; testing changes on PPA.

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2042357] Re: Merge crash 8.0.3 into Noble

[Mauricio Faria de Oliveira]

** Description changed:

- Work in progress
+ Work in progress; testing changes on PPA.
+ 
+ Debian bugs:
+ 
+ https://bugs.debian.org/1054805
+ Please update crash to 8.0.3
+ 
+ https://bugs.debian.org/1055117
+ FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

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

Title:
  Merge crash 8.0.3 into Noble

Status in crash package in Ubuntu:
  In Progress

Bug description:
  Work in progress; testing changes on PPA.

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2042357] [NEW] Merge crash 8.0.3 into Noble

[Mauricio Faria de Oliveira]

Public bug reported:

Work in progress; testing changes on PPA.

Debian bugs:

https://bugs.debian.org/1054805
Please update crash to 8.0.3

https://bugs.debian.org/1055117
FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

** Affects: crash (Ubuntu)
 Importance: Medium
 Assignee: Mauricio Faria de Oliveira (mfo)
 Status: In Progress

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

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

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

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

Title:
  Merge crash 8.0.3 into Noble

Status in crash package in Ubuntu:
  In Progress

Bug description:
  Work in progress; testing changes on PPA.

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Debian's crash 8.0.3-1 FTBFS, waiting on 8.0.3-2 [1].

[1] https://bugs.debian.org/1055117

** Bug watch added: Debian Bug tracker #1055117
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055117

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unkn

[Kernel-packages] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C

[Andreas Hasenack]

I still get this error in Ubuntu Lunar, with kernel 6.2.0-35-generic.

Sample:
$ sudo dmesg -T|grep Atomic
[qua nov  1 05:52:03 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=78023 end=78024) time 305 us, min 1783, max 1799, 
scanline start 1753, end 1804
[qua nov  1 06:15:56 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=161109 end=161110) time 209 us, min 1783, max 1799, 
scanline start 1775, end 1811
[qua nov  1 22:22:34 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=50827 end=50828) time 270 us, min 1783, max 1799, 
scanline start 1767, end 1812
[qua nov  1 22:32:50 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=90592 end=90593) time 278 us, min 1783, max 1799, 
scanline start 1768, end 1814
[qua nov  1 22:35:42 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=100359 end=100360) time 168 us, min 1783, max 1799, 
scanline start 1779, end 1807
[qua nov  1 23:29:19 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=259865 end=259866) time 276 us, min 1783, max 1799, 
scanline start 1770, end 1817
[qui nov  2 03:54:09 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=317370 end=317371) time 264 us, min 1783, max 1799, 
scanline start 1756, end 1801
[qui nov  2 03:57:36 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=331393 end=331394) time 279 us, min 1783, max 1799, 
scanline start 1769, end 1816
[qui nov  2 04:00:05 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe C (start=317726 end=317727) time 255 us, min 2146, max 2159, 
scanline start 2140, end 2173
[qui nov  2 04:48:44 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe C (start=492825 end=492826) time 272 us, min 2146, max 2159, 
scanline start 2123, end 2159

Hardware is a lenovo x1 10th gen, with intel "alderlake gen12" according
to intel_gpu_top, and I'm running xorg (not wayland).


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

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

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe A/B/C

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

Bug description:
  I have this error and arbitrary freezes on the system

  My System:

  Hardware:
  Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 
0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate 
ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: 
Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 
Gigabit + Intel Device a370

  Software:
  OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, 
Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, 
Screen Resolution: 1920x1980

  dmesg output:

  Dec  2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, 
min 894, max 899, scanline start 845, end 903
  Dec  2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup 
failure, AE_NOT_FOUND (20170831/psargs-364)
  Dec  2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized 
for Method [BRT6]
  Dec  2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method 
[BRT6]:  (2 arguments defined for method invocation)
  Dec  2 16:08:50 G5 kernel: [ 2534.448073]   Arg0:   a83faa08 
   Integer 0001
  Dec  2 16:08:50 G5 kernel: [ 2534.448076]   Arg1:   35246c42 
   Integer 
  Dec  2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution 
failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution 
failed \EV5, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution 
failed \SMEE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution 
failed \SMIE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution 
failed \NEVT, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution 
failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2

[Kernel-packages] [Bug 2042043] Re: system boot freeze while typing crypt password

[Joe Barnett]

** Description changed:

  Rebooted my system and at the luks/crypt password entry screen, I was
  able to type about half my password when the system locked up and became
  unresponsive.  Hard poweroff was the only thing that worked.  Same
  problem in recovery mode at the text prompt for the crypt password.  saw
- the same behavior after multiple reboots.
+ the same behavior after multiple reboots with both 6.5.0-10 and 6.5.0-9
+ kernels.
  
  Eventually was able to boot successfully by waiting a while before
  typing the password, and typing it very slowly.  no idea what triggered
  the succesful password entry though
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  jbarnett   5022 F wireplumber
-  /dev/snd/seq:jbarnett   5015 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jbarnett   5022 F wireplumber
+  /dev/snd/seq:jbarnett   5015 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Oct 30 20:16:01 2023
  InstallationDate: Installed on 2019-08-17 (1536 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
-  Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
-  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
+  Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
+  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-6.5.0-10-generic N/A
-  linux-backports-modules-6.5.0-10-generic  N/A
-  linux-firmware20230919.git3672ccab-0ubuntu2.1
+  linux-restricted-modules-6.5.0-10-generic N/A
+  linux-backports-modules-6.5.0-10-generic  N/A
+  linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-09-26 (34 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

** Description changed:

  Rebooted my system and at the luks/crypt password entry screen, I was
  able to type about half my password when the system locked up and became
  unresponsive.  Hard poweroff was the only thing that worked.  Same
  problem in recovery mode at the text prompt for the crypt password.  saw
  the same behavior after multiple reboots with both 6.5.0-10 and 6.5.0-9
  kernels.
  
  Eventually was able to boot successfully by waiting a while before
  typing the password, and typing it very slowly.  no idea what triggered
- the succesful password entry though
+ the succesful password entry though, or how to even debug the system
+ when its in this state
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   5022 F wireplumber
   /dev/snd/seq:jbarnett   5015 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Oct 30 20:16:01 2023
  InstallationDate: Installed on 2019-08-17 (1536 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
   Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001

[Kernel-packages] [Bug 2041006] Re: 7900XTX support still broken on Jammy after latest update

[Mario Limonciello]

> amd_gpio AMDI0030 0: Invalid config param 0014

This is fixed by this patch:
https://github.com/torvalds/linux/commit/87b549efcb0f7934b0916d2a00607a878b6f1e0f

Canonical needs to backport that to applicable kernels.

> 10/31/23 12:11 PM   WARNING CPU: 2 PID: 3763 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hwseq.c:1197
dcn32_calculate_dccg_k1_k2_values+0xec/0x120 [amdgpu]

I believe that likely Canonical is missing stable backports related to VRR.
You can cross reference a newer mainline kernel to confirm this.

** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu)

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: Incomplete

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

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

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

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

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

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

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

** Summary changed:

- 7900XTX support still broken on Jammy after latest update
+ WARNING CPU: 2 PID: 3763 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hwseq.c:1197 
dcn32_calculate_dccg_k1_k2_values

** No longer affects: linux (Ubuntu Jammy)

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

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

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

** Package changed: linux-hwe (Ubuntu Jammy) => linux-hwe-6.2 (Ubuntu
Jammy)

** Changed in: linux-hwe-6.2 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux-hwe-6.2 (Ubuntu Lunar)
   Status: New => Invalid

** Changed in: linux-hwe-6.2 (Ubuntu Mantic)
   Status: New => Invalid

** Changed in: linux-hwe-6.2 (Ubuntu Noble)
   Status: New => Invalid

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

Title:
  WARNING CPU: 2 PID: 3763 at
  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hwseq.c:1197
  dcn32_calculate_dccg_k1_k2_values

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-hwe-6.2 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-hwe-6.2 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-6.2 source package in Noble:
  Invalid

Bug description:
  darkfoss@Tardis-2:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  Clean install just apt-get update and apt-get dist-upgrade 
  During the installation process when intramfs is run the following error is 
being generated:
  Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu

  darkfoss@Tardis-2:~$ apt-cache policy linux-firmware
  linux-firmware:
Installed: 20220329.git681281e4-0ubuntu3.21
Candidate: 20220329.git681281e4-0ubuntu3.21
Version table:
   *** 20220329.git681281e4-0ubuntu3.21 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20220329.git681281e4-0ubuntu3.14 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   20220329.git681281e4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  All of the above do not work even though the driver is installed
  correctly. The above error prevents radeonsi from loading.

  The good news is when I installed Both 23.04 and 23.10 they had 1 working 
firmware each they are:
  From Lunar Lobster
  20230323.gitbcdcfbcf-0ubuntu1.2 security (main)   2023-07-06
  Publishing details

  Created on 2023-07-06 by Andy Whitcroft
  Published on 2023-07-06

  Changelog

  linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) lunar; urgency=medium

* rtl8761b usb bluetooth doesn't work following reboot until unplug/replug 
(LP: #1968604)
  - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922
  - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922

   -- Ju

[Kernel-packages] [Bug 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

[Heinrich Schuchardt]

File lib/firmware/brcm/brcmfmac43430-sdio.bin.zst is contained in the
24.04 package. Looks ok.

** Changed in: linux-firmware (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [Impact]

  /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
  StarFive VisionFive board which uses the starfive kernel flavor.

  The file was available in Jammy and only recently removed from Mantic.

  File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding
  it cyfmac43430-sdio.clm_blob which file WHENCE links to
  brcmfmac43430-sdio.bin. So this file needs to change.

  [Fix]

  Include cypress/cyfmac firmware files in firmware packages.

  [Test Case]

  Check that wifi is functional.

  [Where Problems Could Occur]

  Potential wifi problems on platforms that are using the brcmfmac
  driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2041006] Re: 7900XTX support still broken on Jammy after latest update

[Lawrence A Fossi]

Second issue is resuming from sleep 1 error on shutdown different error
on resume. I'm attaching the kernel log after resuming.

Sorry for the long delay from my initial post but I wanted to make sure
I was providing clean information from a solid installation.

** Attachment added: "kernel-log sleep errors 10.31.2023"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2041006/+attachment/5714709/+files/kernel-log%20sleep%20errors%2010.31.2023

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

Title:
  7900XTX support still broken on Jammy after latest update

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  darkfoss@Tardis-2:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  Clean install just apt-get update and apt-get dist-upgrade 
  During the installation process when intramfs is run the following error is 
being generated:
  Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu

  darkfoss@Tardis-2:~$ apt-cache policy linux-firmware
  linux-firmware:
Installed: 20220329.git681281e4-0ubuntu3.21
Candidate: 20220329.git681281e4-0ubuntu3.21
Version table:
   *** 20220329.git681281e4-0ubuntu3.21 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20220329.git681281e4-0ubuntu3.14 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   20220329.git681281e4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  All of the above do not work even though the driver is installed
  correctly. The above error prevents radeonsi from loading.

  The good news is when I installed Both 23.04 and 23.10 they had 1 working 
firmware each they are:
  From Lunar Lobster
  20230323.gitbcdcfbcf-0ubuntu1.2 security (main)   2023-07-06
  Publishing details

  Created on 2023-07-06 by Andy Whitcroft
  Published on 2023-07-06

  Changelog

  linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) lunar; urgency=medium

* rtl8761b usb bluetooth doesn't work following reboot until unplug/replug 
(LP: #1968604)
  - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922
  - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922

   -- Juerg Haefliger   Mon, 05 Jun 2023
  09:22:50 +0200

  Available diffs

  diff from 20230323.gitbcdcfbcf-0ubuntu1.1 to
  20230323.gitbcdcfbcf-0ubuntu1.2 (653 bytes)

  Builds

  [FULLYBUILT] amd64

  Built packages

  linux-firmware Firmware for Linux kernel drivers

  Package files

  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.debian.tar.xz (3.4 MiB)
  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.dsc (2.0 KiB)
  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2_all.deb (268.0 MiB)
  linux-firmware_20230323.gitbcdcfbcf.orig.tar.xz (254.0 MiB)


  From The Mantic Minotaur  (current stable release)
  20230919.git3672ccab-0ubuntu2.1  release (main)   2023-10-09
  Publishing details

  Created on 2023-10-09 by Ubuntu Archive Auto-Sync
  Published on 2023-10-09

  Changelog

  linux-firmware (20230919.git3672ccab-0ubuntu2.1) mantic;
  urgency=medium

* /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 (LP: 
#2038546)
  - [Packaging] config: Don't exclude cypress fw link targets

   -- Juerg Haefliger   Mon, 09 Oct 2023
  16:16:20 +0200

  Available diffs

  diff from 20230919.git3672ccab-0ubuntu2 to
  20230919.git3672ccab-0ubuntu2.1 (992 bytes)

  Builds

  [FULLYBUILT] amd64
  [FULLYBUILT] arm64
  [FULLYBUILT] armhf
  [FULLYBUILT] ppc64el
  [FULLYBUILT] riscv64
  [FULLYBUILT] s390x

  Built packages

  linux-firmware Firmware for Linux kernel drivers

  Package files

  linux-firmware_20230919.git3672ccab-0ubuntu2.1.debian.tar.xz (3.3 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1.dsc (2.0 KiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_amd64.deb (389.5 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_arm64.deb (386.5 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_armhf.deb (384.5 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_ppc64el.deb (384.2 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_riscv64.deb (384.3 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_s390x.deb (315.0 MiB)
  linux-firmware_20230919.git3672ccab.orig.tar.xz (292.2 MiB)

  darkfoss@Tardis-2:~$ glxinfo | grep render
  direct rendering: Yes
  GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_MESA_swap_contr

[Kernel-packages] [Bug 2041006] Re: 7900XTX support still broken on Jammy after latest update

[Lawrence A Fossi]

Your comments lead me do some digging and it tuns out I had somehow
broken the secure boot chain. After changing the 2 bios ccp settings
from auto to enabled the psp loads correctly. I downgraded the firmware
with muon then Discover notified me of an upgrade I had made sure that
it was set to update on reboot. Everything appears to have installed in
the correct manner, I now have fully working secure display.

There are 2 remaining issues 1 new 1 old.
The new issue occurred last night after installing the new kernel upgrade:Linux 
Tardis-2 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct  9 
15:34:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I can actually see it during the boot up right after the Ubuntu slash screen 
and before the screen to unlock the drive encryption: 

10/31/23 11:47 AM   amd_gpio AMDI0030   0: Invalid config param
0014

I'm attaching the kernel log error occurs at the top right under init.

** Attachment added: "kernel-log-clean boot 10-31-2023"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2041006/+attachment/5714708/+files/kernel-log-clean%20boot%2010-31-2023

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

Title:
  7900XTX support still broken on Jammy after latest update

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  darkfoss@Tardis-2:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  Clean install just apt-get update and apt-get dist-upgrade 
  During the installation process when intramfs is run the following error is 
being generated:
  Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu

  darkfoss@Tardis-2:~$ apt-cache policy linux-firmware
  linux-firmware:
Installed: 20220329.git681281e4-0ubuntu3.21
Candidate: 20220329.git681281e4-0ubuntu3.21
Version table:
   *** 20220329.git681281e4-0ubuntu3.21 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20220329.git681281e4-0ubuntu3.14 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   20220329.git681281e4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  All of the above do not work even though the driver is installed
  correctly. The above error prevents radeonsi from loading.

  The good news is when I installed Both 23.04 and 23.10 they had 1 working 
firmware each they are:
  From Lunar Lobster
  20230323.gitbcdcfbcf-0ubuntu1.2 security (main)   2023-07-06
  Publishing details

  Created on 2023-07-06 by Andy Whitcroft
  Published on 2023-07-06

  Changelog

  linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) lunar; urgency=medium

* rtl8761b usb bluetooth doesn't work following reboot until unplug/replug 
(LP: #1968604)
  - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922
  - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922

   -- Juerg Haefliger   Mon, 05 Jun 2023
  09:22:50 +0200

  Available diffs

  diff from 20230323.gitbcdcfbcf-0ubuntu1.1 to
  20230323.gitbcdcfbcf-0ubuntu1.2 (653 bytes)

  Builds

  [FULLYBUILT] amd64

  Built packages

  linux-firmware Firmware for Linux kernel drivers

  Package files

  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.debian.tar.xz (3.4 MiB)
  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.dsc (2.0 KiB)
  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2_all.deb (268.0 MiB)
  linux-firmware_20230323.gitbcdcfbcf.orig.tar.xz (254.0 MiB)


  From The Mantic Minotaur  (current stable release)
  20230919.git3672ccab-0ubuntu2.1  release (main)   2023-10-09
  Publishing details

  Created on 2023-10-09 by Ubuntu Archive Auto-Sync
  Published on 2023-10-09

  Changelog

  linux-firmware (20230919.git3672ccab-0ubuntu2.1) mantic;
  urgency=medium

* /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 (LP: 
#2038546)
  - [Packaging] config: Don't exclude cypress fw link targets

   -- Juerg Haefliger   Mon, 09 Oct 2023
  16:16:20 +0200

  Available diffs

  diff from 20230919.git3672ccab-0ubuntu2 to
  20230919.git3672ccab-0ubuntu2.1 (992 bytes)

  Builds

  [FULLYBUILT] amd64
  [FULLYBUILT] arm64
  [FULLYBUILT] armhf
  [FULLYBUILT] ppc64el
  [FULLYBUILT] riscv64
  [FULLYBUILT] s390x

  Built packages

  linux-firmware Firmware for Linux kernel drivers

  Package files

  linux-firmware_20230919.git3672ccab-0ubuntu2.1.debian.tar.xz (3.3 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1.dsc (

[Kernel-packages] [Bug 2042301] Re: Windows are slow to open shortly after login under X11 session

[Dimitrij Mijoski]

** Description changed:

  On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable
  latency of about 10-15 seconds after I click on any application, be it
  Nautilus, Terminal, Firefox. The problem lasts for about one minute.
  More precise steps:
  
  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear
  
  After about one minute opening any of these apps will open immediately,
  as expected. If I logout and login to Wayland the issue is not present.
  If I logout and login into X11 the issue can be reproduced, so it is not
  related to boot but to login. If I uninstall nvidia drivers the issue is
  gone.
  
  It might be an issue with mutter or gnome-shell.
  
  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]
  
  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.
  
  If I write the following command:
  
  $ journalctl --user --unit=xdg-desktop-portal
  
  I get:
  
  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
- Oct 31 18:20:10 my-pc-hostname xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was r>
- Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: Failed to create file 
chooser proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout w>
+ Oct 31 18:20:10 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
+ Oct 31 18:20:35 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create file 
chooser proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
  Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: No skeleton to export
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
start operation timed out. Terminating.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
Failed with result 'timeout'.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: Failed to start 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Started 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopping 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopped 
xdg-desktop-portal.service - Portal service.
  
  So during one login and logout the service fails to start at first, but
  succeeds to start later.

** Description changed:

  On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable
  latency of about 10-15 seconds after I click on any application, be it
  Nautilus, Terminal, Firefox. The problem lasts for about one minute.
  More precise steps:
  
  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear
  
  After about one minute opening any of these apps will open immediately,
  as expected. If I logout and login to Wayland the issue is not present.
  If I logout and login into X11 the issue can be reproduced, so it is not
  related to boot but to login. If I uninstall nvidia drivers the issue is
  gone.
  
  It might be an issue with mutter or gnome-shell.
  
  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]
  
  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.
  
  If I write the following command:
  
  $ journalctl --user --unit=xdg-desktop-portal
  
  I get:
  
  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
- Oct 31 18:20:10 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling StartS

[Kernel-packages] [Bug 2042301] Re: Windows are slow to open shortly after login under X11 session

[Dimitrij Mijoski]

** Also affects: xdg-desktop-portal (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable
  latency of about 10-15 seconds after I click on any application, be it
  Nautilus, Terminal, Firefox. The problem lasts for about one minute.
  More precise steps:
  
  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear
  
  After about one minute opening any of these apps will open immediately,
  as expected. If I logout and login to Wayland the issue is not present.
  If I logout and login into X11 the issue can be reproduced, so it is not
  related to boot but to login. If I uninstall nvidia drivers the issue is
  gone.
  
  It might be an issue with mutter or gnome-shell.
  
  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]
  
  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.
  
  If I write the following command:
  
  $ journalctl --user --unit=xdg-desktop-portal
  
  I get:
  
  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:20:10 my-pc-hostname xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was r>
  Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: Failed to create file 
chooser proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout w>
  Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: No skeleton to export
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
start operation timed out. Terminating.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
Failed with result 'timeout'.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: Failed to start 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Started 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopping 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopped 
xdg-desktop-portal.service - Portal service.
  
  So during one login and logout the service fails to start at first, but
- succeeds to tart later.
+ succeeds to start later.

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

Title:
  Windows are slow to open shortly after login under X11 session

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  On Ubuntu 23.10 after I install the Nvidia driver v535 I get
  noticeable latency of about 10-15 seconds after I click on any
  application, be it Nautilus, Terminal, Firefox. The problem lasts for
  about one minute. More precise steps:

  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear

  After about one minute opening any of these apps will open
  immediately, as expected. If I logout and login to Wayland the issue
  is not present. If I logout and login into X11 the issue can be
  reproduced, so it is not related to boot but to login. If I uninstall
  nvidia drivers the issue is gone.

  It might be an issue with mutter or gnome-shell.

  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]

  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.

  If I write the following command:

  $ journalctl --user --unit=xdg-desktop-portal

  I get:

  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:20:10 my-pc-hostname x

[Kernel-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Utkarsh Gupta]

** Also affects: mesa (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Fix Released

** Also affects: ubuntu-settings (Ubuntu Noble)
   Importance: Undecided
 Assignee: Dave Jones (waveform)
   Status: Fix Released

** Also affects: pipewire (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Invalid

** Also affects: linux-meta-raspi (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Fix Released

** Also affects: linux-raspi (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Fix Released

** Also affects: libcamera (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Triaged

** Also affects: rpi-eeprom (Ubuntu Noble)
   Importance: Undecided
 Assignee: Dave Jones (waveform)
   Status: Fix Released

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

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  Fix Released
Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in libcamera source package in Noble:
  Triaged
Status in linux-meta-raspi source package in Noble:
  Fix Released
Status in linux-raspi source package in Noble:
  Fix Released
Status in mesa source package in Noble:
  Fix Released
Status in pipewire source package in Noble:
  Invalid
Status in rpi-eeprom source package in Noble:
  Fix Released
Status in ubuntu-settings source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

[Utkarsh Gupta]

Can you please adjust the status of Noble, too? Thanks

** Also affects: linux-firmware (Ubuntu Noble)
   Importance: High
   Status: Fix Released

** Changed in: linux-firmware (Ubuntu Noble)
   Status: Fix Released => New

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

Title:
  /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  New

Bug description:
  [Impact]

  /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
  StarFive VisionFive board which uses the starfive kernel flavor.

  The file was available in Jammy and only recently removed from Mantic.

  File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding
  it cyfmac43430-sdio.clm_blob which file WHENCE links to
  brcmfmac43430-sdio.bin. So this file needs to change.

  [Fix]

  Include cypress/cyfmac firmware files in firmware packages.

  [Test Case]

  Check that wifi is functional.

  [Where Problems Could Occur]

  Potential wifi problems on platforms that are using the brcmfmac
  driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor

[Utkarsh Gupta]

** Also affects: linux-raspi (Ubuntu Noble)
   Importance: Undecided
   Status: Confirmed

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

Title:
  [raspi] Ubuntu 22.10 does not turn off monitor

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Noble:
  Confirmed

Bug description:
  I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a
  strange behaviour of the screen saver.

  In settings -> energy -> power saving options I selected Screen Blank
  after 5 minutes. After 5 minutes of inactivity, the screen goes blank,
  the monitor says No Signal and turns off, but a few seconds after it
  turns on again, showing a completely black screen.

  The desired behaviour here is that Ubuntu sends no signal to the
  monitor, so the monitor goes into low-consumption mode. But this is
  not happening, the monitor is on and showing a black screen.

  I wonder how to solve this problem, especially given the current
  energy situation in Europe.

  This bug is related to the Ubuntu 22.04 LTS and 22.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7
  Uname: Linux 5.19.0-1009-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 21:31:27 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  ImageMediaBuild: 20221018.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+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 2042301] [NEW] Windows are slow to open shortly after login under X11 session

[Dimitrij Mijoski]

Public bug reported:

On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable
latency of about 10-15 seconds after I click on any application, be it
Nautilus, Terminal, Firefox. The problem lasts for about one minute.
More precise steps:

1. Install Nvidia drivers (using sudo ubuntu-drivers install)
2. Reboot
3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear

After about one minute opening any of these apps will open immediately,
as expected. If I logout and login to Wayland the issue is not present.
If I logout and login into X11 the issue can be reproduced, so it is not
related to boot but to login. If I uninstall nvidia drivers the issue is
gone.

It might be an issue with mutter or gnome-shell.

$ apt list nvidia-driver-535 mutter gnome-shell
Listing... Done
gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]

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

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

Title:
  Windows are slow to open shortly after login under X11 session

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  On Ubuntu 23.10 after I install the Nvidia driver v535 I get
  noticeable latency of about 10-15 seconds after I click on any
  application, be it Nautilus, Terminal, Firefox. The problem lasts for
  about one minute. More precise steps:

  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear

  After about one minute opening any of these apps will open
  immediately, as expected. If I logout and login to Wayland the issue
  is not present. If I logout and login into X11 the issue can be
  reproduced, so it is not related to boot but to login. If I uninstall
  nvidia drivers the issue is gone.

  It might be an issue with mutter or gnome-shell.

  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2042301/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in Linux:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in mesa source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8
  dmi.product.version: XiaoXinPro 14 APH8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2042054/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

[Mario Limonciello]

It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.

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

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

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

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

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

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

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

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

** Also affects: mesa (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: mesa (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-6.5 (Ubuntu Noble)
   Importance: Undecided
   Status: Invalid

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

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

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in mesa source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  

[Kernel-packages] [Bug 1931432] Re: crash FTBFS on riscv64

[Mauricio Faria de Oliveira]

** Changed in: crash (Ubuntu Groovy)
   Status: Confirmed => Won't Fix

** Changed in: crash (Ubuntu Groovy)
   Importance: Medium => Undecided

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

Title:
  crash FTBFS on riscv64

Status in crash package in Ubuntu:
  Confirmed
Status in crash source package in Focal:
  Confirmed
Status in crash source package in Groovy:
  Won't Fix

Bug description:
  Crash fails to build from source on riscv at least for Focal and
  Groovy, later releases may also be affected but I haven't confirm it.

  Examples of failed builds :

  Groovy : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864
  Focal : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+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 2012060] Re: Crash doesn't open kdumps on Jammy with HWE kernel

[Mauricio Faria de Oliveira]

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

** This bug has been marked a duplicate of bug 2038249
   The dump file parsing issue arises from structural changes in Linux kernel 
6.2

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

Title:
  Crash doesn't open kdumps on Jammy with HWE kernel

Status in crash package in Ubuntu:
  New

Bug description:
  Hi!

  I'm running Ubuntu with HWE kernel 5.19.0-35-generic. The kernel
  contains slab struct changes [1] that break crash 8.0.0. The issue has
  been fixed [3] in commit 14f8c460473c ("memory: Handle struct slab
  changes on Linux 5.17-rc1 and later"). The fix is available in crash
  8.0.1 and above.

  If you wish I can send a merge request to jammy-devel with this single
  patch but for now it seems that Ubuntu's process with regards to this
  package is just bump it to the newer version from debian.

  Please advice how to proceed. For now I just build the latest version
  of crash and I can open kdumps from Jammy with HWE using it.

  1. https://lwn.net/Articles/881039/
  2. https://bugzilla.redhat.com/show_bug.cgi?id=2041702
  3. 
https://github.com/crash-utility/crash/commit/14f8c460473c8613553b5defd174ca2af812ddcb

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

  $ apt-cache policy crash
  crash:
Installed: 8.0.0-1ubuntu1
Candidate: 8.0.0-1ubuntu1
Version table:
   *** 8.0.0-1ubuntu1 500
  500 http://th.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2012060/+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 2039141] Re: linux-tools-raspi is missing at least one module needed by usbip

[Juerg Haefliger]

Closing this as 'Invalid' since it's tracked in 3 separate bugs (comment
12).

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

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

Title:
  linux-tools-raspi is missing at least one module needed by usbip

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  my install command-line was sudo apt install linux-tools-raspi

  if is search for it with apt - I find it. This bug reporting tool told
  me it doesn't exist.

  ~$ apt search linux-tools-raspi
  Sorting... Done
  Full Text Search... Done
  linux-tools-raspi/jammy-updates,jammy-security 5.15.0.1038.36 armhf
Raspberry Pi Linux kernel tools

  linux-tools-raspi-nolpae/jammy-updates,jammy-security 5.15.0.1038.36 armhf
Raspberry Pi no-LPAE Linux kernel tools (dummy transitional package)

  https://manpages.ubuntu.com/manpages/jammy/man1/usbip.8.html

  I believe that for usbip bind --busid=1-1.x to work. 
  sudo modprobe usbip_host must run.
  This module is not installed.

  ~$ usbip list -l
   - busid 1-1.1 (0424:ec00)
 Microchip Technology, Inc. (formerly SMSC) : SMSC9512/9514 Fast Ethernet 
Adapter (0424:ec00)

   - busid 1-1.3 (046d:c52b)
 Logitech, Inc. : Unifying Receiver (046d:c52b)

   - busid 1-1.5 (1a86:55d4)
 QinHeng Electronics : unknown product (1a86:55d4)

  ~$ modprobe usbip_host
  modprobe: FATAL: Module usbip_host not found in directory 
/lib/modules/5.15.0-1038-raspi

  
  ~$ usbip bind --busid=1-1.5
  usbip: error: error unbinding device 1-1.5 from driver
  usbip: error: could not unbind driver from device on busid 1-1.5

  
  It would be good if the man page showed the basic use case of binding a local 
usb device, and connecting from a client.

  I have only installed the linux-tools-raspi package out of the linux-
  tools family.

  Cheers...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-raspi 5.15.0.1038.36
  ProcVersionSignature: Ubuntu 5.15.0-1038.41-raspi 5.15.116
  Uname: Linux 5.15.0-1038-raspi armv7l
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-1038-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: armv7l
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: config-disk (/dev/mmcblk0p1)
  Date: Thu Oct 12 17:14:53 2023
  ImageMediaBuild: 20230807.2
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb:
   Bus 001 Device 005: ID 1a86:55d4 QinHeng Electronics SONOFF Zigbee 3.0 USB 
Dongle Plus V2
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   TERM=xterm-kitty
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M snd_bcm2835.enable_compat_alsa=0 
snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1200 
bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  
console=ttyAMA0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable 
rootfstype=ext4 rootwait fixrtc quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-1038-raspi N/A
   linux-backports-modules-5.15.0-1038-raspi  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-raspi
  StagingDrivers: vc_sm_cma bcm2835_v4l2 bcm2835_isp bcm2835_codec snd_bcm2835 
bcm2835_mmal_vchiq
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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

[Kernel-packages] [Bug 2042107] Re: Focal update: v5.4.258 upstream stable release

[Roxana Nicolescu]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.258 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.258 upstream stable release
-from git://git.kernel.org/
- 
- 
+ NFS/pNFS: Report EINVAL errors from connect() to the server
+ SUNRPC: Mark the cred for revalidation if the server rejects it
+ tracing: Increase trace array ref count on enable and filter files
+ ata: libahci: clear pending interrupt status
+ ext4: remove the 'group' parameter of ext4_trim_extent
+ ext4: add new helper interface ext4_try_to_trim_range()
+ ext4: scope ret locally in ext4_try_to_trim_range()
+ ext4: change s_last_trim_minblks type to unsigned long
+ ext4: mark group as trimmed only if it was fully scanned
+ ext4: replace the traditional ternary conditional operator with with 
max()/min()
+ ext4: move setting of trimmed bit into ext4_try_to_trim_range()
+ ext4: do not let fstrim block system suspend
+ ASoC: meson: spdifin: start hw on dai probe
+ netfilter: nf_tables: disallow element removal on anonymous sets
+ bpf: Avoid deadlock when using queue and stack maps from NMI
+ selftests/tls: Add {} to avoid static checker warning
+ selftests: tls: swap the TX and RX sockets in some tests
+ ASoC: imx-audmix: Fix return error with devm_clk_get()
+ i40e: Fix for persistent lldp support
+ UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: i40e Fix GPF when deleting VMs"
+ i40e: Remove scheduling while atomic possibility
+ i40e: Fix warning message and call stack during rmmod i40e driver
+ i40e: Fix VF VLAN offloading when port VLAN is configured
+ powerpc/perf/hv-24x7: Update domain value check
+ dccp: fix dccp_v4_err()/dccp_v6_err() again
+ net: hns3: add 5ms delay before clear firmware reset irq source
+ net: bridge: use DEV_STATS_INC()
+ team: fix null-ptr-deref when team device type is changed
+ net: rds: Fix possible NULL-pointer dereference
+ gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
+ i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
+ Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
+ scsi: qla2xxx: Fix update_fcport for current_topology
+ scsi: qla2xxx: Fix deletion race condition
+ drm/amd/display: Reinstate LFC optimization
+ drm/amd/display: Fix LFC multiplier changing erratically
+ drm/amd/display: prevent potential division by zero errors
+ ata: libata: disallow dev-initiated LPM transitions to unsupported states
+ MIPS: Alchemy: only build mmc support helpers if au1xmmc is enabled
+ clk: tegra: fix error return case for recalc_rate
+ ARM: dts: ti: omap: motorola-mapphone: Fix abe_clkctrl warning on boot
+ bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart wake-up
+ xtensa: add default definition for XCHAL_HAVE_DIV32
+ xtensa: iss/network: make functions static
+ xtensa: boot: don't add include-dirs
+ xtensa: boot/lib: fix function prototypes
+ gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip
+ parisc: sba: Fix compile warning wrt list of SBA devices
+ parisc: iosapic.c: Fix sparse warnings
+ parisc: drivers: Fix sparse warning
+ parisc: irq: Make irq_stack_union static to avoid sparse warning
+ selftests/ftrace: Correctly enable event in instance-event.tc
+ ring-buffer: Avoid softlockup in ring_buffer_resize()
+ ata: libata-eh: do not clear ATA_PFLAG_EH_PENDING in ata_eh_reset()
+ spi: nxp-fspi: reset the FLSHxCR1 registers
+ bpf: Clarify error expectations from bpf_clone_redirect
+ powerpc/watchpoints: Annotate atomic context in more places
+ ncsi: Propagate carrier gain/loss events to the NCSI controller
+ fbdev/sh7760fb: Depend on FB=y
+ nvme-pci: do not set the NUMA node of device if it has none
+ watchdog: iTCO_wdt: No need to stop the timer in probe
+ watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running
+ i40e: improve locking of mac_filter_hash
+ i40e: always propagate error value in i40e_set_vsi_promisc()
+ i40e: fix return of uninitialized aq_ret in i40e_set_vsi_promisc
+ smack: Record transmuting in smk_transmuted
+ smack: Retrieve transmuting information in smack_inode_getsecurity(

[Kernel-packages] [Bug 2042107] [NEW] Focal update: v5.4.258 upstream stable release

[Roxana Nicolescu]

Public bug reported:


SRU Justification

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

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


Linux 5.4.258
xen/events: replace evtchn_rwlock with RCU
ima: rework CONFIG_IMA dependency block
NFS: Fix a race in __nfs_list_for_each_server()
parisc: Restore __ldcw_align for PA-RISC 2.0 processors
RDMA/mlx5: Fix NULL string error
RDMA/siw: Fix connection failure handling
RDMA/uverbs: Fix typo of sizeof argument
RDMA/cma: Fix truncation compilation warning in make_cma_ports
gpio: pxa: disable pinctrl calls for MMP_GPIO
gpio: aspeed: fix the GPIO number passed to pinctrl_gpio_set_config()
IB/mlx4: Fix the size of a buffer in add_port_entries()
RDMA/core: Require admin capabilities to set system parameters
cpupower: add Makefile dependencies for install targets
sctp: update hb timer immediately after users change hb_interval
sctp: update transport state when processing a dupcook packet
tcp: fix delayed ACKs for MSS boundary condition
tcp: fix quick-ack counting to count actual ACKs of new data
net: stmmac: dwmac-stm32: fix resume on STM32 MCU
netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp
net: nfc: llcp: Add lock when modifying device list
net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg
net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is absent
ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
net: fix possible store tearing in neigh_periodic_work()
modpost: add missing else to the "of" check
NFSv4: Fix a nfs4_state_manager() race
NFS: Add a helper nfs_client_for_each_server()
NFS4: Trace state recovery operation
scsi: target: core: Fix deadlock due to recursive locking
ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig
regmap: rbtree: Fix wrong register marked as in-cache when creating new node
wifi: mt76: mt76x02: fix MT76x0 external LNA gain handling
drivers/net: process the result of hdlc_open() and add call of hdlc_close() in 
uhdlc_close()
wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet
wifi: iwlwifi: dbg_ini: fix structure packing
ubi: Refuse attaching if mtd's erasesize is 0
net: prevent rewrite of msg_name in sock_sendmsg()
net: replace calls to sock->ops->connect() with kernel_connect()
wifi: mwifiex: Fix tlv_buf_left calculation
qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info
scsi: zfcp: Fix a double put in zfcp_port_enqueue()
Revert "PCI: qcom: Disable write access to read only registers for IP v2.3.3"
rbd: take header_rwsem in rbd_dev_refresh() only when updating
rbd: decouple parent info read-in from updating rbd_dev
rbd: decouple header read-in from updating rbd_dev->header
rbd: move rbd_dev_refresh() definition
fs: binfmt_elf_efpic: fix personality for ELF-FDPIC
ata: libata-sata: increase PMP SRST timeout to 10s
ata: libata-core: Do not register PM operations for SAS ports
ata: libata-core: Fix port and device removal
ata: libata-core: Fix ata_port_request_pm() locking
net: thunderbolt: Fix TCPv6 GSO checksum calculation
btrfs: properly report 0 avail for very full file systems
ring-buffer: Update "shortest_full" in polling
i2c: i801: unregister tco_pdev in i801_probe() error path
ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES
ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q
nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
serial: 8250_port: Check IRQ data before use
Smack:- Use overlay inode label in smack_inode_copy_up()
smack: Retrieve transmuting information in smack_inode_getsecurity()
smack: Record transmuting in smk_transmuted
i40e: fix return of uninitialized aq_ret in i40e_set_vsi_promisc
i40e: always propagate error value in i40e_set_vsi_promisc()
i40e: improve locking of mac_filter_hash
watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running
watchdog: iTCO_wdt: No need to stop the timer in probe
nvme-pci: do not set the NUMA node of device if it has none
fbdev/sh7760fb: Depend on FB=y
ncsi: Propagate carrier gain/loss events to the NCSI controller
powerpc/watchpoints: Annotate atomic context in more places
bpf: Clarify error expectations from bpf_clone_redirect
spi: nxp-fspi: reset the FLSHxCR1 registers
ata: libata-eh: do not clear ATA_PFLAG_EH_PENDING in ata_eh_reset()
ring-buffer: Avoid softlockup in ring_buffer_resize()
selftests/ftrace: Correctly enable event in instance-event.tc
parisc: irq: Make irq_stack_union static to avoid sparse warning
parisc: drivers: Fix sparse warning
parisc: iosapic.c: Fix sparse warning

[Kernel-packages] [Bug 2034718] Re: Backport request: drm/amdgpu: fix clearing mappings for BOs that are always valid in VM

[kisak]

The lack of human communication is underwhelming, alas...


Focal HWE 5.15 https://bugs.launchpad.net/kernel-sru-workflow/+bug/2036573
Jammy 5.15 https://bugs.launchpad.net/kernel-sru-workflow/+bug/2036575
Jammy HWE 6.2 https://bugs.launchpad.net/kernel-sru-workflow/+bug/2038075
Lunar 6.2 https://bugs.launchpad.net/kernel-sru-workflow/+bug/2038076
Mantic 6.5 https://bugs.launchpad.net/kernel-sru-workflow/+bug/2034546

These routine updates have bumped the kernel past the baseline.

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

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

Title:
  Backport request: drm/amdgpu: fix clearing mappings for BOs that are
  always valid in VM

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Good day Ubuntu kernel maintainers,

  Please evaluate
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea2c3c08554601b051d91403a241266e1cf490a5
  for backport into all actively maintained Ubuntu flavors of the Linux
  kernel.

  This commit is needed to stabilize Starfield with mesa/RADV. There was
  a stopgap workaround put into mesa 23.1.4, but that workaround harmed
  other games and it needed to be fixed properly in the kernel. The mesa
  workaround is removed in mesa 23.1.7 and mesa git main.

  As far as I can tell, all Ubuntu kernels do not meet the 5.15.121+,
  6.1.40+ or 6.4.5+ baseline noted in
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774

  There's what looks like an automated mailing list message that this
  commit was queued for the upstream 5.4 series at some point near
  5.4.250, but it's not in the linux changelog, so there might be a
  conflict denominating it from that kernel.

  Expected kernels affected: Focal HWE and Jammy (5.15 based), Jammy HWE
  and Lunar (6.2 based), and Mantic (6.3 based)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034718/+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 2042092] Re: CIFS module is not included in 6.2.0-1016

[Kalen Emhof]

I can confirm this:

6.2.0-1015 Kernel
~# uname -a
Linux pi-geosvrd01 6.2.0-1015-azure #15~22.04.1-Ubuntu SMP Fri Oct  6 13:20:44 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

~# lsmod | grep cifs
cifs 1363968  2
cifs_arc4  16384  1 cifs
cifs_md4   16384  1 cifs
fscache   380928  1 cifs

~# ls -lh /lib/modules/6.2.0-1015-azure/kernel/fs/cifs
-rw-r--r-- 1 root root 2.8M Oct  6 07:20 cifs.ko

~# ls -lh /lib/modules/6.2.0-1015-azure/kernel/fs
total 128K
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 9p
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 autofs
-rw-r--r-- 1 root root  38K Oct  6 07:20 binfmt_misc.ko
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 btrfs
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 cachefiles
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 ceph
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 cifs
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 dlm
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 fat
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 fscache
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 fuse
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 isofs
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 lockd
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 netfs
drwxr-xr-x 5 root root 4.0K Oct 31 09:00 nfs
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 nfs_common
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 nfsd
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 nls
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 overlayfs
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 smbfs_common
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 udf
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 ufs
drwxr-xr-x 2 root root 4.0K Oct 31 09:00 xfs


After installing the 6.2.0-1016 kernel and rebooting unable to mount CIFS 
filesystems:
~# uname -a
Linux pi-geosvrd01 6.2.0-1016-azure #16~22.04.1-Ubuntu SMP Tue Oct 10 17:11:51 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

~# modprobe cifs
modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure

~#
mount error: cifs filesystem not supported by the system
mount error(19): No such device

~# ls -lh /lib/modules/6.2.0-1016-azure/kernel/fs/
total 120K
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 9p
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 autofs
-rw-r--r-- 1 root root  38K Oct 10 11:03 binfmt_misc.ko
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 btrfs
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 cachefiles
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 ceph
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 dlm
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 fat
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 fscache
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 fuse
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 isofs
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 lockd
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 netfs
drwxr-xr-x 5 root root 4.0K Oct 31 09:36 nfs
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 nfs_common
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 nfsd
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 nls
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 overlayfs
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 udf
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 ufs
drwxr-xr-x 2 root root 4.0K Oct 31 09:36 xfs

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
  fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
  inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
  was not updated for this change, so the module is not included in the
  linux-modules-6.2.0-1026-azure package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042092/+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 2042092] Re: CIFS module is not included in 6.2.0-1016

[Launchpad Bug Tracker]

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

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

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
  fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
  inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
  was not updated for this change, so the module is not included in the
  linux-modules-6.2.0-1026-azure package.

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


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

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

[Juerg Haefliger]

> I've updated. Using crontab, I start collecting information in case of
a failure. What else should I add?

Nothing. This is 'Fix Released', so all done from our perspective.

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

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

  [Where Problems Could Occur]

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

  [Original Description]

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

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

  another user experienced similar issue

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

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

  I use systemd-networkd

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

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

  dmesg:

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

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

[Kernel-packages] [Bug 2042101] [NEW] "intel_ish_ipc 0000:00:1d.0: enable ose_gpe failed" when suspend/resume over 255 times Edit

[Philip Cox]

Public bug reported:

This is a public version of https://bugs.launchpad.net/bugs/2025310

---

[Summary]
intel_ish_ipc enable ose_gpe failed after suspend/resume over 255 times

[Steps to reproduce]
1. Boot into OS
2. Install checkbox
$ snap install checkbox22 --channel=beta
$ snap install checkbox-iiotg-classic --channel=latest/edge
3. Run suspend stress test
$ sudo checkbox-iiotg-classic.checkbox-cli
4. Select the Suspend (S3) stress test and run the tests
5. run the test over 255 times.

[Expected result]
ish should enable pci pme as required.

[Actual result]
cannot enable pci pme because the reference count overflow.


Upstream patch that was submitted to fix this is:
https://lore.kernel.org/linux-
input/20231003155332.1855569-1-srinivas.pandruv...@linux.intel.com/#r

** Affects: linux-intel-iotg (Ubuntu)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: In Progress

** Affects: linux-intel-iotg (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: In Progress

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

** Changed in: linux-intel-iotg (Ubuntu Jammy)
 Assignee: (unassigned) => Philip Cox (philcox)

** Changed in: linux-intel-iotg (Ubuntu)
   Status: New => Triaged

** Changed in: linux-intel-iotg (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: linux-intel-iotg (Ubuntu)
   Status: Triaged => Confirmed

** Changed in: linux-intel-iotg (Ubuntu Jammy)
   Status: Triaged => Confirmed

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

** Changed in: linux-intel-iotg (Ubuntu Jammy)
   Status: Confirmed => In Progress

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

Title:
  "intel_ish_ipc :00:1d.0: enable ose_gpe failed" when
  suspend/resume over 255 times Edit

Status in linux-intel-iotg package in Ubuntu:
  In Progress
Status in linux-intel-iotg source package in Jammy:
  In Progress

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

  ---

  [Summary]
  intel_ish_ipc enable ose_gpe failed after suspend/resume over 255 times

  [Steps to reproduce]
  1. Boot into OS
  2. Install checkbox
  $ snap install checkbox22 --channel=beta
  $ snap install checkbox-iiotg-classic --channel=latest/edge
  3. Run suspend stress test
  $ sudo checkbox-iiotg-classic.checkbox-cli
  4. Select the Suspend (S3) stress test and run the tests
  5. run the test over 255 times.

  [Expected result]
  ish should enable pci pme as required.

  [Actual result]
  cannot enable pci pme because the reference count overflow.


  Upstream patch that was submitted to fix this is:
  https://lore.kernel.org/linux-
  input/20231003155332.1855569-1-srinivas.pandruv...@linux.intel.com/#r

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2042101/+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 2042078] Re: package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

[Launchpad Bug Tracker]

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

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

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

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

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  during googling face this pop up and send the error.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1644 F wireplumber
   /dev/snd/seq:sunny  1641 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Oct 31 13:33:10 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-04-29 (184 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. X540UV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=f083fc1e-8354-4bb4-b672-973d36f4def2 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540UV.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540UV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540UV.204:bd10/05/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX540UV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: X
  dmi.product.name: X540UV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2042078/+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 2042096] [NEW] Azure: Update TDX with HCL support

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]

Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV VM
support with HCL.

The refreshed patches will fix 2 bugs for future Hyper-V versions:
1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a 
host bug. The guest bug is fixed in the mainline version of the TDX patches.
2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing 
hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the 
Hyper-V while it should pass a private input page; as a result, the hypercall 
always fails and Linux now falls back to the legacy native method of flusing 
TLB. This slows down the flush-TLB operation . The mainline version doesn't 
have the bug.

[Test Plan]

Microsoft tested.

[Regression Potential]

Azure instances with TDX on HCL hypervisors may not work correctly.

[Other Info]

SF: #00364214

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

** Affects: linux-azure (Ubuntu Lunar)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

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

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

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

** Changed in: linux-azure (Ubuntu Lunar)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

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

Title:
  Azure: Update TDX with HCL support

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Lunar:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV
  VM support with HCL.

  The refreshed patches will fix 2 bugs for future Hyper-V versions:
  1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a 
host bug. The guest bug is fixed in the mainline version of the TDX patches.
  2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing 
hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the 
Hyper-V while it should pass a private input page; as a result, the hypercall 
always fails and Linux now falls back to the legacy native method of flusing 
TLB. This slows down the flush-TLB operation . The mainline version doesn't 
have the bug.

  [Test Plan]

  Microsoft tested.

  [Regression Potential]

  Azure instances with TDX on HCL hypervisors may not work correctly.

  [Other Info]

  SF: #00364214

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042096/+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 2042096] Re: Azure: Update TDX with HCL support

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2023-October/146654.html

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

Title:
  Azure: Update TDX with HCL support

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Lunar:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV
  VM support with HCL.

  The refreshed patches will fix 2 bugs for future Hyper-V versions:
  1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a 
host bug. The guest bug is fixed in the mainline version of the TDX patches.
  2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing 
hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the 
Hyper-V while it should pass a private input page; as a result, the hypercall 
always fails and Linux now falls back to the legacy native method of flusing 
TLB. This slows down the flush-TLB operation . The mainline version doesn't 
have the bug.

  [Test Plan]

  Microsoft tested.

  [Regression Potential]

  Azure instances with TDX on HCL hypervisors may not work correctly.

  [Other Info]

  SF: #00364214

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042096/+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 2038960] Re: X11 session crash when resuming from sleed mode

[Alexandre AM MOYRAND]

any help please?

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

Title:
  X11 session crash when resuming from sleed mode

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

Bug description:
  after my laptop has been in sleep mode I try to login.
  After 1 enter my password, it asks me a second time my password and the 
system start a brand new session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 21:22:07 2023
  InstallationDate: Installed on 2023-09-22 (18 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038960/+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 2042092] [NEW] CIFS module is not included in 6.2.0-1016

[Jean-Francois Simoneau]

Public bug reported:

Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
was not updated for this change, so the module is not included in the
linux-modules-6.2.0-1026-azure package.

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

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
  fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
  inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
  was not updated for this change, so the module is not included in the
  linux-modules-6.2.0-1026-azure package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042092/+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 2042088] [NEW] package linux-headers-6.2.0-36-generic 6.2.0-36.37 failed to install/upgrade: installed linux-headers-6.2.0-36-generic package post-installation script subprocess

[pbuzas]

Public bug reported:

Building module:
Cleaning build area...
'make' -j2 KVER=6.2.0-36-generic 
KSRC=/lib/modules/6.2.0-36-generic/build(bad
 exit status: 2)
ERROR (dkms apport): binary package for rtl88x2bu: git not found
Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
Consult /var/lib/dkms/rtl88x2bu/git/build/make.log for more information.
dkms autoinstall on 6.2.0-36-generic/x86_64 failed for rtl88x2bu(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.2.0-36-generic
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: hiba a csomag feldolgozásakor: linux-headers-6.2.0-36-generic 
(--configure):
 installed linux-headers-6.2.0-36-generic package post-installation script 
subprocess returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-36-generic 6.2.0-36.37
ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  judit  1646 F wireplumber
 /dev/snd/controlC1:  judit  1646 F wireplumber
 /dev/snd/seq:judit  1633 F pipewire
CasperMD5CheckResult: unknown
Date: Tue Oct 31 13:22:38 2023
ErrorMessage: installed linux-headers-6.2.0-36-generic package 
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=10cf95da-595a-4987-b599-d61cbfc17ca1
InstallationDate: Installed on 2016-10-16 (2570 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: ASUSTeK Computer INC. VM40B
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=9f5d1bb4-4b33-449e-a155-45aba2c59da2 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.2.0-36-generic 6.2.0-36.37 failed to 
install/upgrade: installed linux-headers-6.2.0-36-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-07-14 (108 days ago)
dmi.bios.date: 12/09/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: VM40B
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd12/09/2014:br4.6:svnASUSTeKComputerINC.:pnVM40B:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnVM40B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: VM40B
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-36-generic 6.2.0-36.37 failed to
  install/upgrade: installed linux-headers-6.2.0-36-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Building module:
  Cleaning build area...
  'make' -j2 KVER=6.2.0-36-generic 
KSRC=/lib/modules/6.2.0-36-generic/build(bad
 exit status: 2)
  ERROR (dkms apport): binary package for rtl88x2bu: git not found
  Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
  Consult /var/lib/dkms/rtl88x2bu/git/build/make.log for more information.
  dkms autoinstall on 6.2.0-36-generic/x86_64 failed for rtl88x2bu(10)
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
   * dkms: autoinstall for kernel 6.2.0-36-generic
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: hiba a csomag feldolgozásakor: linux-headers-6.2.0-36-generic 
(--configure):
   installed linux-headers-6.2.0-36-generic package post-installation script 
subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-36-generic 6.2.0-36.37
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.

[Kernel-packages] [Bug 2042090] [NEW] Orchid Bay MLK2/Maya Bay MLK soundwire support

[You-Sheng Yang]

Public bug reported:

The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23

And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: Undecided
 Status: Triaged


** Tags: oem-priority originate-from-2041774 somerville

** Tags added: oem-priority originate-from-2041774 somerville

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

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: New => Triaged

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux-oem-6.5 source package in Jammy:
  Triaged

Bug description:
  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2041903] Re: Bluetooth stutters because of bug in kernel

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217673.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-07-14T22:29:56+00:00 cydiaimpactor2003 wrote:

Created attachment 304639
The dmesg output after boot for the 6.5 RC1 mainline kernel

I have a Lenovo ThinkPad X1 Yoga Gen 7 running Arch Linux. Linux 6.4 and
higher, cause audio distortion. Sometimes, this occurs to the point that
nearly nothing is discernible. This carries over to wired headphones.
The issue occurs on the entire mainline 6.4.x kernel series and also the
6.4.3 stable and 6.5 RC1 kernel, which are the latest at the time of
writing. The issue occurs on both the Arch distributed kernels, and the
mainline kernels.

Linux kernels 6.3.x are not affected and neither is the 6.1 LTS kernel
series which is what I am temporarily using. On Windows 10/11 too, the
audio works as it should. This indicates that my hardware is not at
fault. Bluetooth audio is not impacted from my testing, either.

The distortion doesn't start immediately. It either occurs automatically
after a random amount of time, or when I increase/decrease the volume,
or when I skip forward/backward to a section. In order to stop the
distortion, I have to either increase/decrease the volume until it
stops, or skip forward/backward until it stops, or restart Pipewire via
systemd, however it starts again due to one of the aforementioned
reasons.

At the time of this report, I am running Pipewire 0.3.74 and Wireplumber
0.4.14. This also doesn't seem like a Pipewire/Wireplumber issue, since
these same versions work fine on the 6.1 LTS kernels without causing any
audio distortion.

I wrote about this on the Arch Linux forums, too, and seems like at
least two other people are facing this issue. Here's the forum post:
https://bbs.archlinux.org/viewtopic.php?id=287068

Furthermore, I filed a bug report on the Arch Linux Bug Reporter, where
they suggested that the issue is a kernel regression and should be
reported upstream, here. Here's the bug report that I filed on the Arch
Linux Bug Reporter for anyone interested:
https://bugs.archlinux.org/task/79081?project=1&pagenum=10

I have attached the dmesg outputs of the mainline 6.5 RC1 kernel.

Here's some audio related hardware information from my device:

inxi -A

Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio
driver: sof-audio-pci-intel-tgl
API: ALSA v: k6.5.0-rc1-1-mainline status: kernel-api


pactl info

Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 138
Tile Size: 65472
User Name: tux
Host Name: NSA-Terminal-4
Server Name: PulseAudio (on PipeWire 0.3.74)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: 
alsa_output.pci-_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink
Default Source: 
alsa_input.pci-_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_6__source
Cookie: f9dc:5e7a


I can't figure out why this is happening. Kindly ask for any more information 
that is necessary. Thank you.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041903/comments/0


On 2023-07-14T22:33:17+00:00 cydiaimpactor2003 wrote:

Created attachment 304640
Pactl detailed sound card information

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041903/comments/1


On 2023-07-14T22:48:27+00:00 cydiaimpactor2003 wrote:

Also, please pardon me if I did something wrong with filing the bug
report. This is my first time filing one.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041903/comments/2


On 2023-07-15T10:46:43+00:00 bagasdotme wrote:

(In reply to Iyer from comment #0)
> Created attachment 304639 [details]
> The dmesg output after boot for the 6.5 RC1 mainline kernel
> 
> I have a Lenovo ThinkPad X1 Yoga Gen 7 running Arch Linux. Linux 6.4 and
> higher, cause audio distortion. Sometimes, this occurs to the point that
> nearly nothing is discernible. This carries over to wired headphones. The
> issue occurs on the entire mainline 6.4.x kernel series and also the 6.4.3
> stable and 6.5 RC1 kernel, which are the latest at the time of writing. The
> issue occurs on both the Arch distributed kernels, and the mainline kernels.
> 
> Linux kernels 6.3.x are not affected and neither is the 6.1 LTS kernel
> series which is what I am temporarily using. On Windows 10/11 too, the audio
> works as it should

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

[Seiwan Khalni]

Public bug reported:

during googling face this pop up and send the error.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-36-generic 6.2.0-36.37
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sunny  1644 F wireplumber
 /dev/snd/seq:sunny  1641 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Oct 31 13:33:10 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2023-04-29 (184 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: ASUSTeK COMPUTER INC. X540UV
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=f083fc1e-8354-4bb4-b672-973d36f4def2 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: dkms
Title: package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X540UV.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X540UV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540UV.204:bd10/05/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX540UV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: X
dmi.product.name: X540UV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package lunar need-duplicate-check

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

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

Status in dkms package in Ubuntu:
  New

Bug description:
  during googling face this pop up and send the error.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1644 F wireplumber
   /dev/snd/seq:sunny  1641 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Oct 31 13:33:10 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-04-29 (184 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. X540UV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=f083fc1e-8354-4bb4-b672-973d36f4def2 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540UV.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540UV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540UV.204:bd10/05/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX540UV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: X
  dmi.product.name: X540UV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2042078/+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.laun

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

[Quinten Van Ginderen]

@timo,

Just for some clarity, when you say no longer affects; does that mean
you can get the kernel from kernel.org, install it and it will work just
like that or does it mean when you install a kernel with a tool say
mainline, it should work?

Or are we now waiting for the patch to be in the apt/dnf/pacman/zypper repos?
I'm a bit of a noob on the patching cycle.
For now i'm running a patched unsigned kernel 6.1.59. unfortunatly Virtualbox 
won't run unless the modules are signed however.
I was looking in how to sign it myself but it seems like certificate hassle.

Kind regards.
Quinten.

Happy patching :)

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 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-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2042075] [NEW] Black screen at login after updating to this kernel

[David Rutherford]

Public bug reported:

Dell Inspiron  AMD A10 Laptop
Linux Mint Mate O/S

After updating the kernel I restarted the laptop. After entering my
password and logging in the screen goes black with occasional flashes
of, I guess i'd call it static.

The same thing happened with the previous kernel I installed, ending
.87, when I was running Zorin OS.

After un-installing the system returns to opening as usual.

System:
  Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working 
correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco
dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy

Machine:
  Type: Portable System: Dell product: Inspiron  v: A12 serial:  Chassis:
type: 8 v: A12 serial: 
  Mobo: Dell model: 0CX84K v: A00 serial:  UEFI: Dell v: A12
date: 08/30/2016

CPU:
  Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 
64 type: MT MCP
arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
  Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 
2673 2: 2680
3: 3053 4: 2700 bogomips: 14374
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: 
kernel ports:
active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874
  Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 
Mobile]
vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 
bus-ID: 03:00.0
chip-ID: 1002:6660
  Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 
2-4:3
chip-ID: 0c45:6712
  Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X:
loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu 
display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96
  Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9")
  OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 
5.15.0-76-generic)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

I don't have a lot of experience with reporting errors so I hope this
helps!

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

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

Title:
  Black screen at login after updating to this kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Dell Inspiron  AMD A10 Laptop
  Linux Mint Mate O/S

  After updating the kernel I restarted the laptop. After entering my
  password and logging in the screen goes black with occasional flashes
  of, I guess i'd call it static.

  The same thing happened with the previous kernel I installed, ending
  .87, when I was running Zorin OS.

  After un-installing the system returns to opening as usual.

  System:
Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working 
correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco
  dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy

  Machine:
Type: Portable System: Dell product: Inspiron  v: A12 serial: 
 Chassis:
  type: 8 v: A12 serial: 
Mobo: Dell model: 0CX84K v: A00 serial:  UEFI: Dell v: 
A12
  date: 08/30/2016

  CPU:
Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 
64 type: MT MCP
  arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 
1: 2673 2: 2680
  3: 3053 4: 2700 bogomips: 14374
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu 
v: kernel ports:
  active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874
Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 
Mobile]
  vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 
bus-ID: 03:00.0
  chip-ID: 1002:6660
Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 
2-4:3
  chip-ID: 0c45:6712
Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: 
X:
  loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu 
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96
Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9")
OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 
5.15.0-76-generic)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  I don't have a lot of experience with reporting errors so I hope this
  helps!

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


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

[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown

[jdt37b]

Same message at launch :"kfd: amdgpu: STONEY not supported in kfd""
Same problems with this system :
Xubuntu 22.04.3 LTS
Kernel: 5.15.0-87-generic
Xfce 4.16.0-1
CPU : AMD A9-9420 RADEON R5 5 COMPUTE CORES 2C+3G
Graphics: AMD Stoney [Radeon R2/R3/R4/R5 Graphics]
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati

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

Title:
  powerlight stays on after shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43,
  5.11.0.44 power-button light fails to switch off, after shutdown.

  shutdown can be triggered from command line or via desktop menu,
  result is the same. After rebooting from 5.11.0.40 normal
  functionality is restored.

  systemd appears to complete shutdown looking at the logs (see
  attached)

  Switching to suspend mode (sleep) functions as expected (power light blinks) 
and stays permanently on after wake-up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christian   1896 F pulseaudio
   /dev/snd/controlC0:  christian   1896 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-06 (609 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81MT
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-40-generic N/A
   linux-backports-modules-5.11.0-40-generic  N/A
   linux-firmware 1.187.24
  Tags:  focal
  Uname: Linux 5.11.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/09/2019
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8ZCN23WW(V2.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V145-15AST
  dmi.ec.firmware.release: 2.23
  dmi.modalias: 
dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST:
  dmi.product.family: V145-15AST
  dmi.product.name: 81MT
  dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST
  dmi.product.version: Lenovo V145-15AST
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956467/+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 1970586] Re: No sound support on Linux AWS/Azure kernels (but supported on GCP)

[Daniel Gibson]

Same for linux-modules-extra-6.2.0-1015-aws, it's missing snd-aloop.ko
as well

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

Title:
  No sound support on Linux AWS/Azure kernels (but supported on GCP)

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

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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


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

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

[Timo Aaltonen]

skipping 5.15, this will be for 6.2 and up (plus oem-6.1)

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

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 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-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2034477]

[mario.limonciello]

You have a different issue, please open a separate one.

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2042074] [NEW] missing mei_vsc firmware for HM2172 and OV02E sensor

[You-Sheng Yang]

Public bug reported:

[ 5.880936] mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
[ 5.880940] mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
[ 5.880958] mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
[ 5.880959] mei_vsc spi-INTC10D0:00: reset failed ret = -19
[ 5.880960] mei_vsc spi-INTC10D0:00: link layer initialization failed.
[ 5.880974] mei_vsc spi-INTC10D0:00: init hw failure.

Upstream commit in https://github.com/intel/ivsc-
firmware/commit/4f15196c0dcb7b71981cfe24015336eefd9a7bc8

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

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

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

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


** Tags: oem-priority originate-from-2042073 somerville

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

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

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

** Tags added: oem-priority originate-from-2042073 somerville

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

Title:
  missing mei_vsc firmware for HM2172 and OV02E sensor

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  New
Status in linux-firmware source package in Noble:
  New

Bug description:
  [ 5.880936] mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
  [ 5.880940] mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
  [ 5.880958] mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
  [ 5.880959] mei_vsc spi-INTC10D0:00: reset failed ret = -19
  [ 5.880960] mei_vsc spi-INTC10D0:00: link layer initialization failed.
  [ 5.880974] mei_vsc spi-INTC10D0:00: init hw failure.

  Upstream commit in https://github.com/intel/ivsc-
  firmware/commit/4f15196c0dcb7b71981cfe24015336eefd9a7bc8

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042074/+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 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181

[Martin Johansen]

We see that that vmlinuz-5.4.0-166-generic was deplyed as an automatic
update a few hours ago, hopefully this resolves the problem :)

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

Title:
  qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a number of Ubuntu 20.04 servers that have recently been
  upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27.

  About 1/1000 boots of qemu results in a failed boot hanging at 100%
  CPU indefinately. A number of our utilities are using qemu for
  processing, so we get a lot of processes spinning at 100% that we need
  to clean up regularly.

  Ubuntu: 20.04
  Linux: 5.4.0-164.181
  Qemu: 4.2-3ubuntu6.27

  This problem was not seen before the release of Linux. 5.4.0-164.181
  on sept. 1.

  What you expected to happen: Qemu boots linux reliably.
  What happened instead: Qemu hangs at 100% indefinately.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-164-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic 
root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 
netcfg/do_not_use_netplan=true
  ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-164-generic N/A
   linux-backports-modules-5.4.0-164-generic  N/A
   linux-firmware 1.187.39
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-164-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+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 1970586] Re: No sound support on Linux AWS/Azure kernels (but supported on GCP)

[Daniel Gibson]

How do I reopen this bug?

The current `linux-aws` package in Jammy is 6.2.0.1014.14~22.04.1, and
snd_aloop (and the modules it depends on: snd, snd_pcm, snd_timer) are
missing from linux-modules-extra-aws (or more specifically, linux-
modules-extra-6.2.0-1012-aws)

@timg-tpi can you look into this? Thanks :)

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

Title:
  No sound support on Linux AWS/Azure kernels (but supported on GCP)

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

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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 2021740] Re: Add modaliases support

[You-Sheng Yang]

** Changed in: ipu6-drivers (Ubuntu Mantic)
   Status: In Progress => Triaged

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

Title:
  Add modaliases support

Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver 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 linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  In Progress
Status in ivsc-driver source package in Jammy:
  In Progress
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in ipu6-drivers source package in Kinetic:
  Won't Fix
Status in ivsc-driver source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux-oem-6.5 source package in Kinetic:
  Invalid
Status in ipu6-drivers source package in Lunar:
  In Progress
Status in ivsc-driver source package in Lunar:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in ipu6-drivers source package in Mantic:
  Triaged
Status in ivsc-driver source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justifications]

  == kernel ==

  [Impact]

  Need modaliases info for ubuntu-drivers integration.

  [Fix]

  This Ubuntu sauced patch copies modaliases info from source dkms deb packages 
to
  standalone `linux-modules---` ones if available.

  [Test Case]

  ```bash
  $ sudo add-apt-repository ppa:canonical-hwe-team/experimental-unstable
  $ apt-cache show linux-modules-ivsc-6.6.0-9005-generic | grep Modaliases
  Modaliases: mei-vsc(acpi*:INTC1009:*, acpi*:INTC1058:*, acpi*:INTC1094:*, 
acpi*:INTC10D0:*)

  $ ubuntu-drivers list
  linux-modules-ipu6-6.5.0-9005-generic
  ...
  ```

  [Where problems could occur]

  With **XB-Modaliases** field added to deb control, `ubuntu-drivers` will then
  give a list of installable `linux-modules---` 
candidates
  on available platforms. So far based on current `debian/dkms-versions`, the 
only
  one will be enabled will be ivsc-driver, and ipu6-drivers to be SRUed soon.

  [Other Info]

  To nominate Unstable/Mantic/Lunar/OEM-6.5/OEM-6.1.

  Note that this adds a build-dep to dh-modaliases from universe pocket.

  == ipu6-drivers, ivsc-driver ==

  [Impact]

  Need modaliases info for ubuntu-drivers integration.

  [Fix]

  Modaliases applied to ivsc-drivers/{mantic,lunar,jammy}, and
  ipu6-drivers/{mantic,lunar,jammy}

  [Test Case]

  ```bash
  $ sudo add-apt-repository ppa:vicamo/ppa-2031412 # noble, mantic
  $ ubuntu-drivers list
  intel-ipu6-dkms, (kernel modules provided by intel-ipu6-dkms)
  ...
  ```

  [Where problems could occur]

  This adds modaliases to built binary dkms packages so that they may
  prompt on systems with Intel IPU6 camera.

  [Other Info]

  == original bug report ==

  To be discovered by ubuntu-drivers, dkms packages should have
  modaliases tag in debian/control as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2021740/+subscriptions


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

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

[Isaac True]

This seems to have been resolved with the beta release of the 3.03
firmware. Thanks @superm1

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

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

Title:
  amdgpu crashing intermittently under high load on Kubuntu 23.10

Status in linux package in Ubuntu:
  Invalid

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

  Relevant part of dmesg seems to be:

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

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

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

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


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

[Kernel-packages] [Bug 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9

[Chris Chiu]

** Tags added: oem-priority originate-from-2018975 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/2042060

Title:
  Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook
  Fury 16 G9

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

Bug description:
  
  [Impact]
  Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume 
from suspend. The audio play and capture functions are not working after resume 
from S3.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/.

  [Test Case]
  1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA .
  2. Perform system suspend/resume at least 3 times.
  3. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA. The impact is restricted.

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


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

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

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 
verification-needed-jammy-linux-oracle-6.2

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

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

  [Where Problems Could Occur]

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

  [Original Description]

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

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

  another user experienced similar issue

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

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

  I use systemd-networkd

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

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

  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Ubuntu Kernel Bot]

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


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


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


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

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in ipu6-drivers source package in Mantic:
  New
Status in ivsc-driver source package in Mantic:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  In Progress
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 pl

[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 
verification-needed-jammy-linux-oracle-6.2

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

Title:
  [regression] Unable to initialize SGX enclaves with XFRM other than 3

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

Bug description:
  SRU Justification

  [Impact]

  In 5.15.0-1045, only loading enclaves with XFRM set to 3 works,
  sgx_encl_init returns EINVAL. The only reason this wouldn't work
  properly is if sgx_drv_init thinks XSAVE isn't enabled. This works
  fine in 5.15.0-1043.

  Likely cause:
  1045 adds this patch: 
https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4
 . This later patch indicates that the former patch introduced some ordering 
problems. 
https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5
 . That later patch isn't applied to 1045.

  [Test Plan]

  User test results pending, but its a fix commit so should likely be
  applied regardless.

  [Regression Potential]

  SGX could continue to fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2027816] Re: Interrupt storm on GPIO controller on AMD platforms

[Mario Limonciello]

These fixes all landed in 6.5-rc2, mantic and noble have them for sure, closing 
those tasks.
I'd expect backporting to be done for Lunar and Jammy if necessary.

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

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

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

** No longer affects: linux-oem-6.1 (Ubuntu Lunar)

** No longer affects: linux-oem-6.1 (Ubuntu Mantic)

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

Title:
  Interrupt storm on GPIO controller on AMD platforms

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

Bug description:
  On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to
  GPIO 7 is causing an interrupt storm.  This issue doesn't happen on
  Windows.

  Comparing the GPIO register configuration between Windows and Linux
  bit 20 has been configured as a pull up on Windows, but not on Linux.
  Checking GPIO declaration from the firmware it is clear it *should* have
  been a pull up on Linux as well.

  ```
  GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x,
    "\\_SB.GPIO", 0x00, ResourceConsumer, ,)
  {   // Pin list
  0x0007
  }
  ```

  On Linux amd_gpio_set_config() is currently only used for programming
  the debounce. Actually the GPIO core calls it with all the arguments
  that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`.

  To solve this issue expand amd_gpio_set_config() to support the other
  arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`,
  `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`.

  Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336

  Related fixes are:
  * v6.4:
* commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and 
wake status")
* commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output")
  * v6.5-rc1:
    * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce 
handling")
  * linux-next:
    * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior 
for GPIO 0")
    * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config 
options")
    * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration")
    * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into 
amd_pinconf_set()")

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


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

[Kernel-packages] [Bug 2034477]

[ertugruluyar.personal]

I have had the same problem for a long time. I have had the same problem for a 
long time. I'am using Lenovo Thinkbook 15 Gen2 ARE 20VG006XTX. 
I only find these solutions worked:
https://lucraymond.net/2021/07/09/fixing-suspend-resume-on-lenovo-thinkbook-15-g2-are-laptop-with-amd-in-linux/
https://lucraymond.net/2022/10/04/linux-fixing-suspend-resume-on-amd-renoir-lenovo-thinkbook-g2-are-on-kernel-5-19-6-0-and-up/
memsleep_default=deep doesn't work. Only the amd_iommu=soft (for older kernels) 
and amd_iommu=off (kernel 6.0+) works. Is this 
(https://www.phoronix.com/news/Linux-6.6-Fixes-9-Lenovo-Laptop) fix this issue 
for my laptop? Please help me, I'am waiting very very long time for get rid of 
this issue.
This is the distro and kernel info that I using now:
OS: TUXEDO OS 2 x86_64
Host: LENOVO LNVNB161216
Kernel: 6.5.0-10006-tuxedo
Uptime: 16 mins
Packages: 2177 (dpkg), 67 (flatpak)
Shell: bash 5.1.16
Resolution: 1920x1080
DE: Plasma 5.27.8 (Wayland)
WM: kwin_wayland_wr
Theme: [Plasma], Breeze [GTK2/3]
Icons: [Plasma], breeze [GTK2/3]
Terminal: konsole
CPU: AMD Ryzen 5 4500U with Radeon Graphics (6) @ 2.375GHz
GPU: AMD ATI Renoir
Memory: 4314MiB / 6790MiB

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 
verification-needed-jammy-linux-oracle-6.2

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

Title:
  allow io_uring to be disabled in runtime

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  io_uring has been an important attack vector in the recent years in local 
privilege escalation attacks. Allowing admins that don't use io_uring to 
disable it in their systems allows them to reduce their attack surface.

  [Test case]
  sysctl -w kernel.io_uring_disabled=1
  then try to use io_uring from an unprivileged user, then try it with 
privileges (CAP_SYS_ADMIN)

  Actually also tried setting kernel.io_uring_disabled=2 and checking that
  neither (privileged or unprivileged worked).

  Then testing setting it back to 0.

  Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and
  that it worked for group 1000, then set it to 1001 and verified that it
  didn't work anymore for group 1000.

  
  [Potential regression]
  Uses can be denied from using io_uring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2035163] Re: Avoid address overwrite in kernel_connect

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 
verification-needed-jammy-linux-oracle-6.2

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

Title:
  Avoid address overwrite in kernel_connect

Status in linux package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-gkeop package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-gke source package in Jammy:
  Fix Released
Status in linux-gkeop source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-gcp source package in Lunar:
  Fix Released
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  This fix is requested to resolve an issue with NFS-backed mounts when
  used with BPF-load-balancing:

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  next.git/commit/?id=0bdf399342c5

  
  Testing:
   - GCP has confirmed the fix works before proposing it upstream. I have 
verified basic network sanity with fix applied.

  
  Regression potenial:
   - The fix modifies kernel_connect() which can have an effect on all kinds of 
network connections. The change itself is very minor though and simply converts 
a pass-by-reference to a pass-by-value - so the risk is considered minimal.

  More information at:
  https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view

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


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

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

[Jarkko Korpi]

0.340638] platform eisa.0: Probing EISA bus 0
[0.340638] platform eisa.0: EISA: Cannot allocate resource for mainboard
[0.340639] platform eisa.0: Cannot allocate resource for EISA slot 1
[0.340640] platform eisa.0: Cannot allocate resource for EISA slot 2
[0.340640] platform eisa.0: Cannot allocate resource for EISA slot 3
[0.340640] platform eisa.0: Cannot allocate resource for EISA slot 4
[0.340641] platform eisa.0: Cannot allocate resource for EISA slot 5
[0.340641] platform eisa.0: Cannot allocate resource for EISA slot 6
[0.340642] platform eisa.0: Cannot allocate resource for EISA slot 7
[0.340642] platform eisa.0: Cannot allocate resource for EISA slot 8
[0.340642] platform eisa.0: EISA: Detected 0 cards


 uname -a
5.15.0-88-generic (Linux Mint 21.2)

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 2032385] Re: [mlx5] Not able to enable switchdev mode on CX-6 DX with OPN MCX623106AN-CDAT and PSID MT_0000000359

[Munish]

Can this also impact Dell R650s with ConnectX-6 LXs?

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

Title:
  [mlx5] Not able to enable switchdev mode on CX-6 DX with OPN
  MCX623106AN-CDAT and PSID MT_000359

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This occurs with default firmware configuration on the following kernels:
  5.15.0
  5.19.0
  6.2.0

  Firmware versions tried:
  22.35.3006
  22.38.1002

  
  The operation is successful when attempting to perform the same operation on 
a CX-6 DX card of a different model.

  Steps to reproduce:
  # ip link
  ...
  4: enp65s0f0np0:  mtu 9000 qdisc mq state UP 
mode DEFAULT group default qlen 1000
  link/ether 10:70:fd:0f:84:2a brd ff:ff:ff:ff:ff:ff
  5: enp65s0f1np1:  mtu 9000 qdisc mq state UP 
mode DEFAULT group default qlen 1000
  link/ether 10:70:fd:0f:84:2b brd ff:ff:ff:ff:ff:ff

  # echo 32 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs 
  # echo 32 > /sys/class/net/enp65s0f1np1/device/sriov_numvfs
  # for addr in $(devlink dev show|tail +3|cut -f2 -d/); do echo $addr > 
/sys/bus/pci/drivers/mlx5_core/unbind;done
  # devlink dev eswitch set pci/:41:00.0 mode switchdev
  Error: mlx5_core: Failed setting eswitch to offloads.
  kernel answers: Cannot allocate memory
  # devlink dev eswitch set pci/:41:00.1 mode switchdev
  Error: mlx5_core: Failed setting eswitch to offloads.
  kernel answers: Cannot allocate memory

  Steps to work around:
  # modprobe -r mlx5_ib
  # echo blacklist mlx5_ib > /etc/modprobe.d/blacklist-mlx5-ib.conf
  # devlink dev eswitch set pci/:41:00.0 mode switchdev
  # devlink dev eswitch set pci/:41:00.1 mode switchdev
  # devlink dev eswitch show pci/:41:00.0
  pci/:41:00.0: mode switchdev inline-mode none encap-mode basic
  # devlink dev eswitch show pci/:41:00.1
  pci/:41:00.1: mode switchdev inline-mode none encap-mode basic

  
  Log excerpts:
  # dmesg -T | tail -40
  [Mon Aug 21 14:50:35 2023] mlx5_core :41:08.1 enp65s0f1v31: renamed from 
eth0
  [Mon Aug 21 14:50:36 2023] infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 19): 
Error -110 while trying to test write-combining support
  [Mon Aug 21 14:50:36 2023] mlx5_ib.rdma: probe of mlx5_core.rdma.65 failed 
with error -12
  [Mon Aug 21 14:53:32 2023] mlx5_core :41:00.0: E-Switch: Disable: 
mode(LEGACY), nvfs(32), active vports(33)
  [Mon Aug 21 14:53:33 2023] mlx5_core :41:00.0: E-Switch: Supported tc 
chains and prios offload
  [Mon Aug 21 14:53:33 2023] mlx5_core :41:00.0: Supported tc offload range 
- chains: 4294967294, prios: 4294967295
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0: MLX5E: StrdRq(1) RqSz(64) 
StrdSz(256) RxCqeCmprss(0)
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0 enp65s0f0np0: Link up
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0 enp65s0f0np0: Dropping 
C-tag vlan stripping offload due to S-tag vlan
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0 enp65s0f0np0: Disabling 
HW_VLAN CTAG FILTERING, not supported in switchdev mode
  [Mon Aug 21 14:53:34 2023] infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 
102770): Error -110 while trying to test write-combining support
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0: MLX5E: StrdRq(1) RqSz(64) 
StrdSz(256) RxCqeCmprss(0)
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0: Supported tc offload range 
- chains: 4294967294, prios: 4294967295
  [Mon Aug 21 14:53:35 2023] mlx5_core :41:00.0 enp65s0f0np0: Link up
  [Mon Aug 21 14:53:36 2023] infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 
102770): Error -110 while trying to test write-combining support
  [Mon Aug 21 14:53:36 2023] mlx5_ib.rdma: probe of mlx5_core.rdma.0 failed 
with error -12
  [Mon Aug 21 14:53:36 2023] mlx5_core :41:00.0: E-Switch: Enable: 
mode(LEGACY), nvfs(32), active vports(33)
  [Mon Aug 21 14:53:39 2023] mlx5_core :41:00.1: E-Switch: Disable: 
mode(LEGACY), nvfs(32), active vports(33)
  [Mon Aug 21 14:53:39 2023] mlx5_core :41:00.1: E-Switch: Supported tc 
chains and prios offload
  [Mon Aug 21 14:53:39 2023] mlx5_core :41:00.1: Supported tc offload range 
- chains: 4294967294, prios: 4294967295
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1: MLX5E: StrdRq(1) RqSz(64) 
StrdSz(256) RxCqeCmprss(0)
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1 enp65s0f1np1: Link up
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1 enp65s0f1np1: Dropping 
C-tag vlan stripping offload due to S-tag vlan
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1 enp65s0f1np1: Disabling 
HW_VLAN CTAG FILTERING, not supported in switchdev mode
  [Mon Aug 21 14:53:40 2023] infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 
102913): Error -110 while trying to test write-combining support
  [Mon Aug 21 14:53:41 2023] mlx5_core :41:00.1: MLX5E: StrdRq(1) RqSz(64) 
StrdSz(256) RxCqeCmprss(0)
  [Mon Aug 21 14:53:41 2023] mlx5_cor

[Kernel-packages] [Bug 2042074] Re: missing mei_vsc firmware for HM2172 and OV02E sensor

[You-Sheng Yang]

Not sure if necessary yet: 
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87
 lib/firmware/intel/ipu6epmtl_fw.bin  | Bin 466944 -> 466944 bytes
 lib/firmware/intel/unsigned/ipu6epmtl_fw.bin | Bin 466944 -> 466944 bytes
 2 files changed, 0 insertions(+), 0 deletions(-)

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

Title:
  missing mei_vsc firmware for HM2172 and OV02E sensor

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  New
Status in linux-firmware source package in Noble:
  New

Bug description:
  [ 5.880936] mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
  [ 5.880940] mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
  [ 5.880958] mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
  [ 5.880959] mei_vsc spi-INTC10D0:00: reset failed ret = -19
  [ 5.880960] mei_vsc spi-INTC10D0:00: link layer initialization failed.
  [ 5.880974] mei_vsc spi-INTC10D0:00: init hw failure.

  Upstream commit in https://github.com/intel/ivsc-
  firmware/commit/4f15196c0dcb7b71981cfe24015336eefd9a7bc8

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042074/+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 2041903] Re: Bluetooth stutters because of bug in kernel

[Paul White]

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

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

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

** Tags added: mantic

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

Title:
  Bluetooth stutters because of bug in kernel

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

Bug description:
  Problems with bluetooth, apparently due to this error.
  https://bugzilla.kernel.org/show_bug.cgi?id=217673
  And for some reason it is present in 6.5.0-10.10 Ubuntu kernel.
  I had to roll back to 6.5.0 using mainline, where there was no problem. Why 
is this fix not available in 6.5.0-10.10? I want to use the kernel from 
canonical

  
  Also only 6.5.0 does not have this problem, 6.5.7 has it

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2041903/+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 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 
verification-needed-jammy-linux-oracle-6.2

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

Title:
  Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
  with CO-RE") from stable update breaks the ubuntu_bpf test build and
  cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
  ubuntu_kernel_selftests stopped working, as they require bpf selftest
  to be built first.

  The following is extracted from the commit message:
  The problem is the new offsetof() does not play nice with static asserts.
  Given that the context is a static assert (and CO-RE relocation is not
  needed at compile time), offsetof() usage can be replaced by restoring
  the original offsetof() definition as __builtin_offsetof().

  [Test Plan]
  Build bpf selftest in tools/testing/selftests with the following command:
  make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
  clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/

  The build can finish successfully with patched kernel source code.

  [Where problems could occur]
  Fix limited to testing tool, if this fix is incorrect the bpf selftest
  build will remain broken.

  
  == Original bug report ==
  Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04

  This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
  is a security cycle, in which the ubuntu_bpf test was not triggered
  there)

  Test build failed with:
    CLNG-BPF [test_maps] test_btf_map_in_map.o
    CLNG-BPF [test_maps] test_btf_newkv.o
    CLNG-BPF [test_maps] test_btf_nokv.o
    CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
    CLNG-BPF [test_maps] test_cgroup_link.o
    CLNG-BPF [test_maps] test_check_mtu.o
    CLNG-BPF [test_maps] test_cls_redirect.o
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
  stderr:
  Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from 
latest version at 'include/uapi/linux/bpf.h'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs 
from latest version at 'include/uapi/linux/netlink.h'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs 
from latest version at 'include/uapi/linux/if_link.h'
  progs/test_cls_redirect.c:90:2: error: static_assert expression is not an 
integral constant expression
  sizeof(flow_ports_t) !=
  ^~~
  progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a 
reinterpret_cast is not allowed in a constant expression
  offsetofend(struct bpf_sock_tuple, ipv4.dport) -
  ^
  progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
  (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
   ^
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
 note: expanded from macro 'offsetof'
  #define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
   ^
  progs/test_cls_redirect.c:95:2: error: static_assert expression is not an 
integral constant expression
  sizeof(flow_ports_t) !=
  ^~~
  progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a 
reinterpret_cast is not allowed in a constant expression
  offsetofend(struct bpf_sock_tuple, ipv6.dport) -
  ^
  progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
  (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
   ^
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/

[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 
verification-needed-jammy-linux-oracle-6.2

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

Title:
  Fix unstable audio at low levels on Thinkpad P1G4

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

Bug description:
  [Impact]
  The audio at low levels is not stable with fluctuating levels.

  [Fix]
  Forcibly assign NID 0x03 to HP while NID 0x02 to SPK.

  [Test]
  Tested on hardware, the audio output is OK at all levels.

  [Where problems could occur]
  It may break audio output on Thinkpad P1G4/5.

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


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

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

[Timo Aaltonen]

** Description changed:

+ [Impact]
+ 
+ Keyboard and touchpad doesn't work on some recent systems, and also
+ s2idle is broken.
+ 
+ [Fix]
+ 
+ Two upstream commits.
+ 
+ 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
+ 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops
+ 
+ [Test case]
+ 
+ boot a fixed kernel and test that input and s2idle works.
+ 
+ [Where problems could occur]
+ 
+ A buggy bios could maybe advertise a system being PCAT compatible when
+ it's not, though in such a case it might have been already caught
+ before.
+ 
+ --
+ 
  Hello.
  
  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are not
  working. The keyboard and touchpad work fine in BIOS setup and till GRUB
  (command line). It was found that when external devices such as
  keyboard, mouse and microphone are connected through USB and 3.5 jack,
  respectively, these work just fine. To confirm these are not hardware
  problems, Microsoft Windows 11  (Home) was installed in another disk
  partition and observed all these working alright. Hence a bug is being
  reported to draw attention of the concerned team and I request them to
  refer this issue and do the needful at the earliest.
  
  Regards,
  Pradip Kumar Das
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_IN
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

** No longer affects: linux-hwe-6.2 (Ubuntu Jammy)

** No longer affects: linux-hwe-6.2 (Ubuntu)

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

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

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

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

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days

[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel

[David Rutherford]

Just in case I should add the kernels that caused the problem for my
laptop are Linux kernel 5.15.0-88.98, and 5.15.0-87

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

Title:
  Black screen at login after updating to this kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Dell Inspiron  AMD A10 Laptop
  Linux Mint Mate O/S

  After updating the kernel I restarted the laptop. After entering my
  password and logging in the screen goes black with occasional flashes
  of, I guess i'd call it static.

  The same thing happened with the previous kernel I installed, ending
  .87, when I was running Zorin OS.

  After un-installing the system returns to opening as usual.

  System:
Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working 
correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco
  dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy

  Machine:
Type: Portable System: Dell product: Inspiron  v: A12 serial: 
 Chassis:
  type: 8 v: A12 serial: 
Mobo: Dell model: 0CX84K v: A00 serial:  UEFI: Dell v: 
A12
  date: 08/30/2016

  CPU:
Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 
64 type: MT MCP
  arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 
1: 2673 2: 2680
  3: 3053 4: 2700 bogomips: 14374
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu 
v: kernel ports:
  active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874
Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 
Mobile]
  vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 
bus-ID: 03:00.0
  chip-ID: 1002:6660
Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 
2-4:3
  chip-ID: 0c45:6712
Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: 
X:
  loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu 
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96
Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9")
OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 
5.15.0-76-generic)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  I don't have a lot of experience with reporting errors so I hope this
  helps!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+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 2035313] Re: Fix non-working I219 after system sleep

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 
verification-needed-jammy-linux-oracle-6.2

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

Title:
  Fix non-working I219 after system sleep

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

Bug description:
  [Impact]
  Intel I219 ethernet stops working after system sleep.

  [Fix]
  Force resume Intel ME to fix I219. It's not surprising because ME/AMT is
  controlled through Intel I219.

  [Test]
  Use `ping 1.1.1.1` to test if I219 is still alive. With the patch
  applied, the ethernet can survive several system sleeps.

  [Where problems could occur] 
  The commit essentially disables direct-complete optimization, so it
  will make system suspend/resume slightly slower.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2035313/+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 2038522] Re: disable shiftfs

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~canonical-kernel-team/+git/overlay-shiftfs-tests/+merge/454842

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

Title:
  disable shiftfs

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Now that all the filesystems that we officially support have the
  idmapped mounts capability we can get rid of shiftfs.

  The benefit of this change is that we don't have to maintain an out-
  of-tree filesystem anymore and we can completely rely on upstream
  features.

  [Test case]

  lxd was the main user of shiftfs to compensate the lack of idmapped
  mounts capability of certain filesystems, such as zfs / ceph, but now
  in mantic also these two filesystem received the support for idmapped
  mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see
  LP: #2032959).

  The lxd team provided a positive feedback, testing the latest 6.5
  Mantic kernel across all the supported filesystems with shiftfs
  disabled.

  [Fix]

  Disable shiftfs in the kernel config and enable unsafe idmapped mounts
  by default (default=on).

  [Regression potential]

  The support for idmapped mounts for the ceph filesystem is not applied
  upstream yet, so we may experience regressions in systems that are
  using this filesystem. Moreover disabling shiftfs may trigger failures
  in our testing (testing shiftfs capabilities will obviously fail) or
  break any other user-space application that is relying on shiftfs
  (however to our knowledge lxd was the only "official" user or shiftfs;
  for this reason we may also see potential regressions in lxd).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+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