date:20231007

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

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

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

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

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

Title:
  NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
  driver installed

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Confirmed
Status in linux-firmware source package in Lunar:
  Confirmed
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  [Impact]


  NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
  latest Ubuntu 22.04.3 kernel and firmware


  Not repro with NV21 XL or W6800



  [Fix]
  Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin



  [Other Info]


  The IMU FW included in Linux firmware package needs to be paired with
  the latest PMFW smu_13_0_0.bin for Navi31

  Jammy firmware updates only include latest IMU firmware.


  https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
  firmware


  20220329.git681281e4-0ubuntu3.19


  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
  (Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2030775] Re: [HP Slim Desktop S01-aF2xxx] Intermitant display blinks off then back on

2023-10-07 Thread Launchpad Bug Tracker

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

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

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

Title:
  [HP Slim Desktop S01-aF2xxx] Intermitant display blinks off then back
  on

Status in linux package in Ubuntu:
  Expired

Bug description:
  Every now and then my display goes black. Then after about 2-3 seconds
  comes back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  8 10:26:30 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 06) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GeminiLake [UHD Graphics 605] 
[103c:8648]
  InstallationDate: Installed on 2023-06-12 (57 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: HP HP Slim Desktop S01-aF2xxx
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=7b1bf46f-ad8b-4b84-b8a4-a7455f0a4e82 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2023
  dmi.bios.release: 15.85
  dmi.bios.vendor: AMI
  dmi.bios.version: F.55
  dmi.board.name: 8648
  dmi.board.vendor: HP
  dmi.board.version: 1.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 55.34
  dmi.modalias: 
dmi:bvnAMI:bvrF.55:bd02/07/2023:br15.85:efr55.34:svnHP:pnHPSlimDesktopS01-aF2xxx:pvr:rvnHP:rn8648:rvr1.00:cvnHP:ct3:cvr:sku318L7AA#ABA:
  dmi.product.family: 103C_53311M HP Desktop
  dmi.product.name: HP Slim Desktop S01-aF2xxx
  dmi.product.sku: 318L7AA#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/ubuntu/+source/linux/+bug/2030775/+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 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33

Let's track the regression in
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Triaged => 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/2024427

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

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

Bug description:
  [SRU Justification]

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

  [Impact]

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

  [Fix]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

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

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

  == original bug report ==

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

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

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

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


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

[Kernel-packages] [Bug 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed

I believe the same thing should be done for Navi33 at same time, it
upgraded IMU as well.  So these two commits are needed in Jammy and
Lunar:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/smu_13_0_0.bin?id=39d6fcc73100ae4aeeec0194bbf102c672673edd

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/smu_13_0_7.bin?id=a7fe4aa13128ce8139e339f2ea61449cf27cdac5

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

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

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

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

** Tags added: regression-update

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

Title:
  NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
  driver installed

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

Bug description:
  [Impact]


  NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
  latest Ubuntu 22.04.3 kernel and firmware


  Not repro with NV21 XL or W6800



  [Fix]
  Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin



  [Other Info]


  The IMU FW included in Linux firmware package needs to be paired with
  the latest PMFW smu_13_0_0.bin for Navi31

  Jammy firmware updates only include latest IMU firmware.


  https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
  firmware


  20220329.git681281e4-0ubuntu3.19


  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
  (Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33

2023-10-07 Thread Alvin Huan

Please help fix this issue asap. Thanks!

https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745


[Impact]

NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
latest Ubuntu 22.04.3 kernel and firmware

Not repro with NV21 XL or W6800

[Fix]
Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

[Other Info]

The IMU FW included in Linux firmware package needs to be paired with
the latest PMFW smu_13_0_0.bin for Navi31

Jammy firmware updates only include latest IMU firmware.

https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
firmware

20220329.git681281e4-0ubuntu3.19

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
(Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

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

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

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

Bug description:
  [SRU Justification]

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

  [Impact]

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

  [Fix]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

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

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

  == original bug report ==

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

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

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

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


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

[Kernel-packages] [Bug 2038745] [NEW] NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed

2023-10-07 Thread Alvin Huan

Public bug reported:

[Impact]


NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
latest Ubuntu 22.04.3 kernel and firmware


Not repro with NV21 XL or W6800


[Fix]
Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin


[Other Info]


The IMU FW included in Linux firmware package needs to be paired with
the latest PMFW smu_13_0_0.bin for Navi31

Jammy firmware updates only include latest IMU firmware.


https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
firmware


20220329.git681281e4-0ubuntu3.19


https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
(Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

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

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

Title:
  NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
  driver installed

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  [Impact]


  NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
  latest Ubuntu 22.04.3 kernel and firmware


  Not repro with NV21 XL or W6800



  [Fix]
  Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin



  [Other Info]


  The IMU FW included in Linux firmware package needs to be paired with
  the latest PMFW smu_13_0_0.bin for Navi31

  Jammy firmware updates only include latest IMU firmware.


  https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
  firmware


  20220329.git681281e4-0ubuntu3.19


  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
  (Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2033416] Re: change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y

2023-10-07 Thread Zixian Cai

Yes, perf events are often used in performance analysis. Without loading
the module, uncore events, such as `amd_l3`, are missing from perf list.

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

Title:
  change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro
  kernels.

  However, unlike plug and play devices, there is no way to load uncore module 
when user tries to use uncore event.
  Also, a primary motivation to add module support in uncore driver was to ease 
development (https://git.kernel.org/torvalds/c/05485745ad482).

  So, ask ubuntu to switch to CONFIG_PERF_EVENTS_AMD_UNCORE=y.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033416/+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 2038743] [NEW] No sound from ALC236 upon warm boot

2023-10-07 Thread Joseph Sible

Public bug reported:

On an HP 15z-fc000 laptop with Realtek ALC236 audio, on Ubuntu 22.04.3
with HWE kernel 6.2.0-34-generic, after doing a warm boot (i.e.,
"Restart" from the menu" or "sudo reboot"), no sound will be able to
play. Doing a cold boot (i.e., "Power Off" or "sudo poweroff" and then
pressing the power button to turn it back on) will make it start working
again.

This bug is a regression caused by commit 5aec98913095 ("ALSA:
hda/realtek - ALC236 headset MIC recording issue").

I've already worked with upstream to get a fix for this bug into the
mainline kernel, which has since landed as commit 69ea4c9d02b7 ("ALSA:
hda/realtek - remove 3k pull low procedure"), with commit 46cdff2369cb
("ALSA: hda/realtek - Remodified 3k pull low procedure") as a follow-up.
To fix this bug, those two commits just need to be cherry-picked into
Ubuntu's kernel.

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
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  7 21:12:27 2023
InstallationDate: Installed on 2023-10-08 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  No sound from ALC236 upon warm boot

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

Bug description:
  On an HP 15z-fc000 laptop with Realtek ALC236 audio, on Ubuntu 22.04.3
  with HWE kernel 6.2.0-34-generic, after doing a warm boot (i.e.,
  "Restart" from the menu" or "sudo reboot"), no sound will be able to
  play. Doing a cold boot (i.e., "Power Off" or "sudo poweroff" and then
  pressing the power button to turn it back on) will make it start
  working again.

  This bug is a regression caused by commit 5aec98913095 ("ALSA:
  hda/realtek - ALC236 headset MIC recording issue").

  I've already worked with upstream to get a fix for this bug into the
  mainline kernel, which has since landed as commit 69ea4c9d02b7 ("ALSA:
  hda/realtek - remove 3k pull low procedure"), with commit 46cdff2369cb
  ("ALSA: hda/realtek - Remodified 3k pull low procedure") as a follow-
  up. To fix this bug, those two commits just need to be cherry-picked
  into Ubuntu's kernel.

  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
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 21:12:27 2023
  InstallationDate: Installed on 2023-10-08 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038743/+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 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1

(The package built correctly in a PPA on all architectures.)

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

Title:
  Slab page exclusion issue on Linux 6.2-rc1

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Jammy:
  Incomplete
Status in makedumpfile source package in Lunar:
  In Progress

Bug description:
  [Impact]
  The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to 
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions, 
introduced a change that aligns the offset of slab.slabs with that of 
page.mapping.
  However, this modification unintentionally causes the makedumpfile command 
with the -d 8 option, meant to exclude user data, to incorrectly exclude 
certain slab pages.
  Consequently, when utilizing dumpfiles generated in this manner, the "crash" 
utility may encounter an error when attempting to initiate a session:

  crash: page excluded: kernel virtual address: e269d428  type:
  "xa_node shift"

  [Fix]
  An upstream fix is available.
  ==
  commit 5f17bdd2128998a3eeeb4521d136a19fadb6
  Author: Kazuhito Hagio 
  Date:   Wed Dec 21 11:06:39 2022 +0900

  [PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
  ==

  [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 dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r) 
/dump.
  crash 8.0.3++
  Copyright (C) 2002-2022  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-2022  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.
   
  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-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  please wait... (gathering task table data)  
  crash: page excluded: kernel virtual address: e269d428  type: 
"xa_node shift"

  [Where problems could occur]
  The patch has altered the method for excluding slab pages, aligning with the 
structural changes introduced in Linux 6.2-rc1.
  This modification is essential for Linux kernel 6.2.
  However, it's crucial to note that this change may impact the content of the 
dump file, potentially leading to a situation where the "crash" utility is 
unable to parse it in the worst-case scenario.

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


-- 
Mailing list:

[Kernel-packages] [Bug 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1

Hi Chengen,

The fix is included in 1.7.3 in mantic, so only lunar needs the fix.

We probably would like jammy as well, for compatibility with the 6.2+
HWE kernel (without regression to the 5.15 GA kernel).

Could you please check jammy for that too? (I'll add a task as
Incomplete.)

$ git describe --contains 5f17bdd2128998a3eeeb4521d136a19fadb6
1.7.3~6

$ rmadison -a source makedumpfile
 makedumpfile | 1.5.5-2ubuntu1   | trusty   | source
 makedumpfile | 1.5.5-2ubuntu1.6 | trusty-updates   | source
 makedumpfile | 1:1.5.9-5~ubuntu14.04.1  | trusty-backports | source
 makedumpfile | 1:1.5.9-5| xenial   | source
 makedumpfile | 1:1.6.3-2~16.04.3| xenial-updates   | source
 makedumpfile | 1:1.6.3-2| bionic   | source
 makedumpfile | 1:1.6.5-1ubuntu1~18.04.7 | bionic-updates   | source
 makedumpfile | 1:1.6.7-1ubuntu2 | focal| source
 makedumpfile | 1:1.6.7-1ubuntu2.4   | focal-updates| source
 makedumpfile | 1:1.7.0-1build1  | jammy| source
 makedumpfile | 1:1.7.2-1| lunar| source
 makedumpfile | 1:1.7.3-1| mantic   | source

Packages verified with LXD VM and upstream crash for now (before bug
2038248). All good!

Uploaded to Lunar.

Thanks!

Details:
---

Setup:

$ lxc launch --vm --config limits.memory=2GiB ubuntu:lunar mdf-l
$ lxc shell mdf-l

# apt update && apt install -y linux-image-generic linux-crashdump crash
# apt remove -y $(dpkg -l | awk '$2 ~ /linux-.*kvm/ { print $2 }')

# sed 's/crashkernel=[^ "]\+/crashkernel=512M/' -i 
/etc/default/grub.d/kdump-tools.cfg
# update-grub
# reboot
# kdump-config show | grep state:
current state:ready to kdump
# echo c >/proc/sysrq-trigger

Debug symbols:

# wget 
https://launchpad.net/ubuntu/+archive/primary/+files/linux-image-unsigned-6.2.0-34-generic-dbgsym_6.2.0-34.34_amd64.ddeb
# ar x 
linux-image-unsigned-6.2.0-34-generic-dbgsym_6.2.0-34.34_amd64.ddeb data.tar.xz
# tar xvf data.tar.xz ./usr/lib/debug/boot/vmlinux-6.2.0-34-generic
./usr/lib/debug/boot/vmlinux-6.2.0-34-generic

Upstream crash (for now):

# apt build-dep -y crash
# git clone https://github.com/crash-utility/crash.git
# cd crash
# make

Original package:
---

# ./crash /var/crash/202310072357/dump.202310072357 
./usr/lib/debug/boot/vmlinux-6.2.0-34-generic
...
please wait... (gathering task table data)
crash: page excluded: kernel virtual address: 9b13c2b826c8  type: 
"xa_node shift"

Patched package:
---

# wget 
https://launchpad.net/~mfo/+archive/ubuntu/test/+build/26759821/+files/makedumpfile_1.7.2-1ubuntu0.1_amd64.deb
# apt install ./makedumpfile_1.7.2-1ubuntu0.1_amd64.deb

# kdump-config reload
# kdump-config show | grep state:
current state:ready to kdump
# echo c >/proc/sysrq-trigger

# ./crash /var/crash/202310080054/dump.202310080054 
./usr/lib/debug/boot/vmlinux-6.2.0-34-generic
...
  KERNEL: ./usr/lib/debug/boot/vmlinux-6.2.0-34-generic
DUMPFILE: /var/crash/202310080054/dump.202310080054  [PARTIAL DUMP]
...
crash>


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

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

** Changed in: makedumpfile (Ubuntu Jammy)
 Assignee: (unassigned) => Chengen Du (chengendu)

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

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

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

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

Title:
  Slab page exclusion issue on Linux 6.2-rc1

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Jammy:
  Incomplete
Status in makedumpfile source package in Lunar:
  In Progress

Bug description:
  [Impact]
  The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to 
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions, 
introduced a change that aligns the offset of slab.slabs with that of 
page.mapping.
  However, this modification unintentionally causes the makedumpfile command 
with the -d 8 option, meant to exclude user data, to incorrectly exclude 
certain slab pages.
  Consequently, when utilizing dumpfiles generated in this manner, the "crash" 
utility may encounter an error when attempting to initiate a session:

[Kernel-packages] [Bug 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1

** Patch added: "lp2038248-makedumpfile-lunar-v2.debdiff"

https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248/+attachment/5707762/+files/lp2038248-makedumpfile-lunar-v2.debdiff

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

Title:
Slab page exclusion issue on Linux 6.2-rc1

Status in makedumpfile package in Ubuntu:
New
Status in makedumpfile source package in Lunar:
In Progress

Bug description:
[Impact]
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions,
introduced a change that aligns the offset of slab.slabs with that of
page.mapping.
However, this modification unintentionally causes the makedumpfile command
with the -d 8 option, meant to exclude user data, to incorrectly exclude
certain slab pages.
Consequently, when utilizing dumpfiles generated in this manner, the "crash"
utility may encounter an error when attempting to initiate a session:

crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"

[Fix]
An upstream fix is available.
==
commit 5f17bdd2128998a3eeeb4521d136a19fadb6
Author: Kazuhito Hagio
Date: Wed Dec 21 11:06:39 2022 +0900

[PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
==

[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 dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r)
/dump.
crash 8.0.3++
Copyright (C) 2002-2022 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-2022 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.

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-unknown-linux-gnu".
Type "show configuration" for configuration details.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...

please wait... (gathering task table data)
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"

[Where problems could occur]
The patch has altered the method for excluding slab pages, aligning with the
structural changes introduced in Linux 6.2-rc1.
This modification is essential for Linux kernel 6.2.
However, it's crucial to note that this change may impact the content of the
dump file, potentially leading to a situation where the "crash" utility is
unable to parse it in the worst-case scenario.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1

Hi Chengen,

Thanks for the detailed SRU template and debdiff!

I have only 2 minor fixes, which I already performed:
- Version: s/ubuntu1/ubuntu0.1/ (see doc [1])
- Maintainer: this is the first 'ubuntu' version, so run `update-maintainer` 
(see `debian/control` hunk).

The updated debdiff is attached for reference,
and I'll continue the work on sponsoring this.

cheers

[1]
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging

** Tags added: se-sponsor-mfo

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

Title:
  Slab page exclusion issue on Linux 6.2-rc1

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Lunar:
  In Progress

Bug description:
  [Impact]
  The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to 
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions, 
introduced a change that aligns the offset of slab.slabs with that of 
page.mapping.
  However, this modification unintentionally causes the makedumpfile command 
with the -d 8 option, meant to exclude user data, to incorrectly exclude 
certain slab pages.
  Consequently, when utilizing dumpfiles generated in this manner, the "crash" 
utility may encounter an error when attempting to initiate a session:

  crash: page excluded: kernel virtual address: e269d428  type:
  "xa_node shift"

  [Fix]
  An upstream fix is available.
  ==
  commit 5f17bdd2128998a3eeeb4521d136a19fadb6
  Author: Kazuhito Hagio 
  Date:   Wed Dec 21 11:06:39 2022 +0900

  [PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
  ==

  [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 dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r) 
/dump.
  crash 8.0.3++
  Copyright (C) 2002-2022  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-2022  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.
   
  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-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  please wait... (gathering task table data)  
  crash: page excluded: kernel virtual address: e269d428  type: 
"xa_node shift"

  [Where problems could occur]
  The patch has altered the method for excluding slab pages, aligning with the 
structural changes introduced in Linux 6.2-rc1.
  This modification is essential for Linux kernel 6.2.

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

2023-10-07 Thread Dimitri John Ledkov

Possibly have to remove NBS first https://ubuntu-archive-
team.ubuntu.com/nbs.html

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+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 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

2023-10-07 Thread Dimitri John Ledkov

418-server & 440-server ready to remove from mantic

$ reverse-depends -b src:nvidia-graphics-drivers-418-server
No reverse dependencies found

$ reverse-depends src:nvidia-graphics-drivers-418-server
No reverse dependencies found

$ reverse-depends -b src:nvidia-graphics-drivers-440-server
No reverse dependencies found

$ reverse-depends src:nvidia-graphics-drivers-440-server
No reverse dependencies found


** Changed in: nvidia-graphics-drivers-418-server (Ubuntu)
   Status: New => Confirmed

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+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 2030978] Re: kernel 6.5 changes cause UBSAN errors (patch included)

2023-10-07 Thread Boris Gjenero

I applied the patch to files in /usr/src/broadcom-sta-6.30.223.271/ and then 
reinstalled linux-image-6.5.0-7-generic to make DKMS rebuild the module. It 
made this error go away:
UBSAN: array-index-out-of-bounds in 
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:2394:26
But this error remains:
UBSAN: array-index-out-of-bounds in 
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:1935:4

I did verify that in /usr/src/broadcom-sta-6.30.223.271/src/include/wlioctl.h, 
the relevant struct has been changed:
struct maclist {
uint count; 
struct ether_addr ea[]; 
};

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

Title:
  kernel 6.5 changes cause UBSAN errors (patch included)

Status in broadcom-sta package in Ubuntu:
  New

Bug description:
  "On Linux 6.5, due to commit 2d47c6956ab3 ("ubsan: Tighten UBSAN_BOUNDS
  on GCC"), flexible trailing arrays declared like `whatever_t foo[1];`
  will generate warnings when CONFIG_UBSAN & co. is enabled."

  Due to changes in kernel 6.5, we get this error in dmesg:

  [   28.818756] 

  [   28.822952] UBSAN: array-index-out-of-bounds in 
/var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
  [   28.82] index 2 is out of range for type 'ether_addr [1]'
  [   28.832900] CPU: 1 PID: 1232 Comm: avahi-daemon Tainted: P   OE
  6.5.0-rc4 #1
  [   28.836452] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663, 
BIOS 432.60.3.0.0 10/27/2021
  [   28.839806] Call Trace:
  [   28.843091]  
  [   28.846387]  dump_stack_lvl+0x48/0x60
  [   28.849692]  dump_stack+0x10/0x20
  [   28.852965]  __ubsan_handle_out_of_bounds+0xc6/0x100
  [   28.856251]  _wl_set_multicast_list+0x1fd/0x220 [wl]
  [   28.859191]  wl_set_multicast_list+0x3a/0x80 [wl]
  [   28.861879]  __dev_set_rx_mode+0x6a/0xc0
  [   28.864237]  __dev_mc_add+0x82/0x90
  [   28.866587]  dev_mc_add+0x10/0x20
  [   28.868920]  igmp_group_added+0x198/0x1d0
  [   28.871102]  ip_mc_inc_group+0x185/0x2b0
  [   28.873231]  __ip_mc_join_group+0x108/0x170
  [   28.875170]  ip_mc_join_group+0x10/0x20
  [   28.877111]  do_ip_setsockopt+0x104d/0x1160
  [   28.878894]  ? __sys_setsockopt+0xeb/0x1c0
  [   28.880657]  ip_setsockopt+0x30/0xb0
  [   28.882326]  udp_setsockopt+0x22/0x40
  [   28.883949]  sock_common_setsockopt+0x14/0x20
  [   28.885554]  __sys_setsockopt+0xde/0x1c0
  [   28.887063]  __x64_sys_setsockopt+0x1f/0x30
  [   28.888564]  do_syscall_64+0x55/0x80
  [   28.889952]  ? syscall_exit_to_user_mode+0x26/0x40
  [   28.891226]  ? __x64_sys_recvmsg+0x1d/0x20
  [   28.892450]  ? do_syscall_64+0x61/0x80
  [   28.893651]  ? do_syscall_64+0x61/0x80
  [   28.894796]  entry_SYSCALL_64_after_hwframe+0x46/0xb0
  [   28.895942] RIP: 0033:0x7f0a97a7ddae
  [   28.897100] Code: 0f 1f 40 00 48 8b 15 69 60 0d 00 f7 d8 64 89 02 48 c7 c0 
ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 31
  [   28.898270] RSP: 002b:7fffb7b1b3f8 EFLAGS: 0246 ORIG_RAX: 
0036
  [   28.899449] RAX: ffda RBX: 000c RCX: 
7f0a97a7ddae
  [   28.900623] RDX: 0023 RSI:  RDI: 
000c
  [   28.901784] RBP: 0001 R08: 000c R09: 
0004
  [   28.902895] R10: 7fffb7b1b404 R11: 0246 R12: 
7fffb7b1b404
  [   28.904011] R13: 0014 R14: 55cc506ee078 R15: 
55cc506eaf60
  [   28.905149]  
  [   28.906228] 


  A patch is however available for this issue:

  https://gist.github.com/joanbm/9cd5fda1dcfab9a67b42cc6195b7b269

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: bcmwl-kernel-source (not installed)
  Uname: Linux 6.5.0-rc4 x86_64
  NonfreeKernelModules: wl zfs
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Aug 10 10:40:27 2023
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: broadcom-sta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2030978/+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 2038410] Missing required logs.

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

apport-collect 2038410

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

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

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

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

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

Title:
  after kernel upgrade today to 6.2.0-33 network and bluetooth stopped
  waorking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  had to go back to 6.2.0-33

  i have amd ryzen 5700g machine with a ASUS Prime B550 motherboard

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:14275453:2023-10-01 12:57:00.819613695 +0200:2023-10-01 
12:57:01.819613695 +0200:/var/crash/_usr_bin_nautilus.1000.crash
   640:1000:124:5824531:2023-10-03 16:49:20.932747125 +0200:2023-10-03 
16:49:21.932747125 +0200:/var/crash/_usr_bin_gnome-panel.1000.crash
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Oct  4 09:08:31 2023
  InstallationDate: Installed on 2023-09-19 (14 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038410/+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 2038410] Re: after kernel upgrade today to 6.2.0-33 network and bluetooth stopped waorking

2023-10-07 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

Your install media was 22.04.3, the ubuntu-release-upgrader tool is used
to release-upgrade to a later release; but you're still using Ubuntu
22.04 thus haven't used the tool. You've likely filed the issue against
an incorrect package (the kernel is changed, not upgraded; as 22.04
system would be upgraded to 23.04 & thus the kernel changed to the 23.04
kernel).

If you have issues with a linux kernel, I suggest filing against that
kernel.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

** Package changed: ubuntu-release-upgrader (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/2038410

Title:
  after kernel upgrade today to 6.2.0-33 network and bluetooth stopped
  waorking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  had to go back to 6.2.0-33

  i have amd ryzen 5700g machine with a ASUS Prime B550 motherboard

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:14275453:2023-10-01 12:57:00.819613695 +0200:2023-10-01 
12:57:01.819613695 +0200:/var/crash/_usr_bin_nautilus.1000.crash
   640:1000:124:5824531:2023-10-03 16:49:20.932747125 +0200:2023-10-03 
16:49:21.932747125 +0200:/var/crash/_usr_bin_gnome-panel.1000.crash
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Oct  4 09:08:31 2023
  InstallationDate: Installed on 2023-09-19 (14 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038410/+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 2038410] [NEW] after kernel upgrade today to 6.2.0-33 network and bluetooth stopped waorking

2023-10-07 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

had to go back to 6.2.0-33

i have amd ryzen 5700g machine with a ASUS Prime B550 motherboard

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.17
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports:
 640:1000:124:14275453:2023-10-01 12:57:00.819613695 +0200:2023-10-01 
12:57:01.819613695 +0200:/var/crash/_usr_bin_nautilus.1000.crash
 640:1000:124:5824531:2023-10-03 16:49:20.932747125 +0200:2023-10-03 
16:49:21.932747125 +0200:/var/crash/_usr_bin_gnome-panel.1000.crash
CurrentDesktop: GNOME-Flashback:GNOME
Date: Wed Oct  4 09:08:31 2023
InstallationDate: Installed on 2023-09-19 (14 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade jammy
-- 
after kernel upgrade today to 6.2.0-33 network and bluetooth stopped waorking
https://bugs.launchpad.net/bugs/2038410
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 2038737] [NEW] nvidia-kernel-source-535 535.113.01-0ubuntu0.23.04.1: nvidia kernel module failed to build

2023-10-07 Thread rodrigomorante

Public bug reported:

There seems to be some incompatibility between the Nvidia driver and
kernel linux-image-6.2.0-34-generic. As a matter of fact, I get a kernel
panic when rebooting so I have to use 6.2.0-33.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: nvidia-kernel-source-535 535.113.01-0ubuntu0.23.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
DKMSKernelVersion: 6.2.0-33-generic
Date: Thu Oct  5 06:35:33 2023
Dependencies:
 
DuplicateSignature: 
dkms:nvidia-kernel-source-535:535.113.01-0ubuntu0.23.04.1:cc: error: 
unrecognized command line option ‘-mharden-sls=all’
InstallationDate: Installed on 2023-08-07 (61 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageVersion: 535.113.01-0ubuntu0.23.04.1
Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0ubuntu0.1
SourcePackage: nvidia-graphics-drivers-535
Title: nvidia-kernel-source-535 535.113.01-0ubuntu0.23.04.1: nvidia kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (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 nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2038737

Title:
  nvidia-kernel-source-535 535.113.01-0ubuntu0.23.04.1: nvidia kernel
  module failed to build

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

Bug description:
  There seems to be some incompatibility between the Nvidia driver and
  kernel linux-image-6.2.0-34-generic. As a matter of fact, I get a
  kernel panic when rebooting so I have to use 6.2.0-33.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: nvidia-kernel-source-535 535.113.01-0ubuntu0.23.04.1
  ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  DKMSKernelVersion: 6.2.0-33-generic
  Date: Thu Oct  5 06:35:33 2023
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-535:535.113.01-0ubuntu0.23.04.1:cc: error: 
unrecognized command line option ‘-mharden-sls=all’
  InstallationDate: Installed on 2023-08-07 (61 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageVersion: 535.113.01-0ubuntu0.23.04.1
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-535
  Title: nvidia-kernel-source-535 535.113.01-0ubuntu0.23.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2038737/+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 2024479] Re: kdump fails on big arm64 systems when offset is not specified

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

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

Title:
  kdump fails on big arm64 systems when offset is not specified

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in kexec-tools source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Fix Released
Status in kexec-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in kexec-tools source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
  Invalid
Status in kexec-tools source package in Lunar:
  Fix Released
Status in kexec-tools source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  kdump fails on arm64, on machines with a lot of memory when offset is not 
specified,
  e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"

  If kdump-tools.cfg specifies the offset e.g.:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
  it works ok.

  The reason for this is that the kernel needs to allocate memory for the 
crashkernel both
  in low and high memory.
  This is addressed in kernel 6.2.
  In addition kexec-tools needs to support more than one crash kernel region.

  [Fix]

  To address this issue the following upstream commits are needed:

  - From the kernel side:

  commit a9ae89df737756d92f0e14873339cf393f7f7eb0
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:44 2022 +0800

  arm64: kdump: Support crashkernel=X fall back to reserve region
  above DMA zones

  commit a149cf00b158e1793a8dd89ca492379c366300d2
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:43 2022 +0800

  arm64: kdump: Provide default size when crashkernel=Y,low is not
  specified

  - From kexec-tools:

  commit b5a34a20984c4ad27cc5054d9957af8130b42a50
  Author: Chen Zhou 
  Date: Mon Jan 10 18:20:08 2022 +0800

  arm64: support more than one crash kernel regions

  Affected releases:
  Jammy, Focal, Bionic

  For Bionic we won't fix it as we need to backport a lot of code and the 
regression potential is too high.
  The same applies for the Focal 5.4 kernel.
  Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.

  [Test Plan]

  You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
  Install linux-crashdump, configure the crash kernel size, and trigger a crash.

  1) Failing scenario (crashkernel >= 4G, without offset "@"):

  It won't work unless the offset is specified because the memory
  crashkernel cannot be allocated.

  With the patches applied it works as expected without having to
  specify the offset.

  2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')

  This must continue to work with the new patches (ie, no regressions),
  including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
  Focal).

  [Regression Potential]

  KERNEL 5.15 - Jammy (and Focal via the HWE kernel):

  To address this problem in the 5.15 kernel we need to pull in 7 commits (see 
[Other] section for details.
  All the commits are changing code only for arm64 architecture and only the 
code related to reserving the crashkernel.
  This means that any regression potential will affect only the arm64 
architecture and in particular the crash/kdump functionality.
  However, since the reservation of the crashkernel occurs at boot up, 
potentially things could go wrong there as well.

  kexec-tools - FOCAL:

  To fix the kexec_tools in focal we need to pull in 6 commits (see [Other 
section for details]). They all cherry pick.
  Four out of six commits touch only arm64 code. Any regression potential 
because of these commits  would regard either crashdump or kexec functionality.
  Commit cf977b1af9ec67fab adds code without altering current functionality.
  Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive 
it moves the code from vmcore-dmesg.c  to elf_info.c so it can be used by other 
features.

  kexec-tools - JAMMY, LUNAR, MANTIC:

  Commit b5a34a20984c is pulled in, it cherry-picks. It changes only
  arm64 code. It enables kexec to recognise that the reserved kernel may
  use more than one kernel region. Things could go worng when gatherinng
  a crashdump.

  [Other]

  Commits to backport

  - MANTIC:

  kernel 6.3: not affected

  kexec-tools:
  b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one 
crash kernel regions

  - LUNAR:

[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

2023-10-07 Thread Launchpad Bug Tracker

This bug was fixed in the package util-linux - 2.39.1-4ubuntu2

---
util-linux (2.39.1-4ubuntu2) mantic; urgency=medium

  * Disable brand new feature with --disable-libmount-mountfd-support that
causes inability to deploy MAAS LP: #2037417

 -- Dimitri John Ledkov   Thu, 05 Oct 2023
22:27:31 +0100

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

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in cloud-images:
  New
Status in maas-images:
  Confirmed
Status in The Ubuntu-power-systems project:
  Invalid
Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Invalid
Status in systemd source package in Mantic:
  Invalid
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2037417/+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 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33

Instead of reverting the IMU binary can you please upgrade the SMU
binary from the same 5.5 release ?

Navi31:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/smu_13_0_0.bin?id=39d6fcc73100ae4aeeec0194bbf102c672673edd

Navi33:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/smu_13_0_7.bin?id=a7fe4aa13128ce8139e339f2ea61449cf27cdac5

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

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

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

Bug description:
  [SRU Justification]

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

  [Impact]

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

  [Fix]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

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

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

  == original bug report ==

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

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

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

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


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

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

2023-10-07 Thread torel

cc. Same issue with 6.2.0-34-generic on an old i5 machine and Logitech
K400 kbd w/integrated mousepad.

# dmesg |grep -i logitech
[5.648913] usb 2-1.1: Manufacturer: Logitech
[   13.148210] input: Logitech USB Receiver as 
/devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:046D:C52B.0001/input/input3
[   13.208627] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 
Keyboard [Logitech USB Receiver] on usb-:00:1a.0-1.1/input0
[   13.208971] input: Logitech USB Receiver Mouse as 
/devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:046D:C52B.0002/input/input4
[   13.209214] input: Logitech USB Receiver Consumer Control as 
/devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:046D:C52B.0002/input/input5
[   13.268569] input: Logitech USB Receiver System Control as 
/devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:046D:C52B.0002/input/input6
[   13.269157] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID 
v1.11 Mouse [Logitech USB Receiver] on usb-:00:1a.0-1.1/input1
[   13.269713] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 
Device [Logitech USB Receiver] on usb-:00:1a.0-1.1/input2

When it was working

# cat /var/log/Xorg.1.log.old | grep -i Logi
[110891.923] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_3438
[110891.925] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 15 paused 0
[110891.927] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 16 paused 0
[110891.940] (II) systemd-logind: releasing fd for 226:1
[110892.180] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 42 
paused 0
[110892.213] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 45 
paused 0
[110892.220] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 46 
paused 0
[110892.228] (II) config/udev: Adding input device Logitech K400 Plus 
(/dev/input/event3)
[110892.228] (**) Logitech K400 Plus: Applying InputClass "evdev pointer 
catchall"
[110892.228] (**) Logitech K400 Plus: Applying InputClass "evdev keyboard 
catchall"
[110892.228] (**) Logitech K400 Plus: Applying InputClass "libinput pointer 
catchall"
[110892.228] (**) Logitech K400 Plus: Applying InputClass "libinput keyboard 
catchall"
[110892.228] (II) Using input driver 'libinput' for 'Logitech K400 Plus'
[110892.229] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 47 
paused 0
[110892.229] (**) Logitech K400 Plus: always reports core events
[110892.232] (II) event3  - Logitech K400 Plus: is tagged by udev as: Keyboard 
Mouse
[110892.232] (II) event3  - Logitech K400 Plus: device is a pointer
[110892.232] (II) event3  - Logitech K400 Plus: device is a keyboard
[110892.233] (II) event3  - Logitech K400 Plus: device removed
[110892.233] (II) libinput: Logitech K400 Plus: needs a virtual subdevice
[110892.233] (II) XINPUT: Adding extended input device "Logitech K400 Plus" 
(type: MOUSE, id 9)
[110892.233] (**) Logitech K400 Plus: (accel) selected scheme none/0
[110892.233] (**) Logitech K400 Plus: (accel) acceleration factor: 2.000
[110892.233] (**) Logitech K400 Plus: (accel) acceleration threshold: 4
[110892.235] (II) event3  - Logitech K400 Plus: is tagged by udev as: Keyboard 
Mouse
[110892.236] (II) event3  - Logitech K400 Plus: device is a pointer
[110892.236] (II) event3  - Logitech K400 Plus: device is a keyboard
[110892.237] (II) config/udev: Adding input device Logitech K400 Plus 
(/dev/input/mouse0)
[110892.247] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 48 
paused 0
[110892.263] (**) Logitech K400 Plus: Applying InputClass "evdev pointer 
catchall"
[110892.263] (**) Logitech K400 Plus: Applying InputClass "evdev keyboard 
catchall"
[110892.263] (**) Logitech K400 Plus: Applying InputClass "libinput pointer 
catchall"
[110892.263] (**) Logitech K400 Plus: Applying InputClass "libinput keyboard 
catchall"
[110892.263] (II) Using input driver 'libinput' for 'Logitech K400 Plus'
[110892.263] (II) systemd-logind: returning pre-existing fd for 
/dev/input/event3 13:67
[110892.263] (**) Logitech K400 Plus: always reports core events
[110892.263] (II) libinput: Logitech K400 Plus: is a virtual subdevice
[110892.263] (II) XINPUT: Adding extended input device "Logitech K400 Plus" 
(type: KEYBOARD, id 11)
[110892.263] (II) systemd-logind: returning pre-existing fd for 
/dev/input/event4 13:68
[110938.912] (EE) event3  - Logitech K400 Plus: client bug: event processing 
lagging behind by 29ms, your system is too slow
[466904.557] (EE) event3  - Logitech K400 Plus: client bug: event processing 
lagging behind by 26ms, your system is too slow
[467200.761] (EE) event3  - Logitech K400 Plus: client bug: event processing 
lagging behind by 30ms, your system is too slow
[467202.027] (EE) event3  - Logitech K400 Plus: client bug: event processing 
lagging behind by 24ms, your system is too slow
[467596.881] (EE) event3  - Logitech K400 Plus: client bug: event processing 
lagging behind

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

This change was made by a bot.

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

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

Title:
  ACL236 Mute Button LED

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ACL236 Sound Card is not fully supported, as the "F6" mute mutton LED
  does not work and is not recognized as existing. The key does work for
  mute. Caps lock LED works. It is also showing that i have numblock and
  scroll lock LED's but I do not, and nothing happens when I try to
  force them to light.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tweak 230923 F wireplumber
   /dev/snd/controlC0:  tweak 230923 F wireplumber
   /dev/snd/seq:tweak 230920 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Oct  7 13:16:33 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=22004860-e498-4071-a8d2-eccadc51c251 ro quiet 
splash zswap.enabled=1 vt.handoff=7 initrd=boot\initrd.img-6.5.0-5-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2023
  dmi.bios.release: 15.68
  dmi.bios.vendor: AMI
  dmi.bios.version: F.68
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.43
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 99.43
  dmi.modalias: 
dmi:bvnAMI:bvrF.68:bd04/21/2023:br15.68:efr99.43:svnHP:pnHPLaptop15-ef0xxx:pvr:rvnHP:rn86FD:rvr99.43:cvnHP:ct10:cvrChassisVersion:sku12C25UA#ABL:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ef0xxx
  dmi.product.sku: 12C25UA#ABL
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038729/+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 2038729] [NEW] ACL236 Mute Button LED

2023-10-07 Thread Tweaker420666

Public bug reported:

ACL236 Sound Card is not fully supported, as the "F6" mute mutton LED
does not work and is not recognized as existing. The key does work for
mute. Caps lock LED works. It is also showing that i have numblock and
scroll lock LED's but I do not, and nothing happens when I try to force
them to light.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tweak 230923 F wireplumber
 /dev/snd/controlC0:  tweak 230923 F wireplumber
 /dev/snd/seq:tweak 230920 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Oct  7 13:16:33 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=UUID=22004860-e498-4071-a8d2-eccadc51c251 ro quiet 
splash zswap.enabled=1 vt.handoff=7 initrd=boot\initrd.img-6.5.0-5-generic
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-5-generic N/A
 linux-backports-modules-6.5.0-5-generic  N/A
 linux-firmware   20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2023
dmi.bios.release: 15.68
dmi.bios.vendor: AMI
dmi.bios.version: F.68
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86FD
dmi.board.vendor: HP
dmi.board.version: 99.43
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 99.43
dmi.modalias: 
dmi:bvnAMI:bvrF.68:bd04/21/2023:br15.68:efr99.43:svnHP:pnHPLaptop15-ef0xxx:pvr:rvnHP:rn86FD:rvr99.43:cvnHP:ct10:cvrChassisVersion:sku12C25UA#ABL:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-ef0xxx
dmi.product.sku: 12C25UA#ABL
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug mantic

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

Title:
  ACL236 Mute Button LED

Status in linux package in Ubuntu:
  New

Bug description:
  ACL236 Sound Card is not fully supported, as the "F6" mute mutton LED
  does not work and is not recognized as existing. The key does work for
  mute. Caps lock LED works. It is also showing that i have numblock and
  scroll lock LED's but I do not, and nothing happens when I try to
  force them to light.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tweak 230923 F wireplumber
   /dev/snd/controlC0:  tweak 230923 F wireplumber
   /dev/snd/seq:tweak 230920 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Oct  7 13:16:33 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=22004860-e498-4071-a8d2-eccadc51c251 ro quiet 
splash zswap.enabled=1 vt.handoff=7 initrd=boot\initrd.img-6.5.0-5-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2023
  dmi.bios.release: 15.68
  dmi.bios.vendor: AMI
  dmi.bios.version: F.68
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.43
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 99.43
  dmi.modalias: 
dmi:bvnAMI:bvrF.68:bd04/21/2023:br15.68:efr99.43:svnHP:pnHPLaptop15-ef0xxx:pvr:rvnHP:rn86FD:rvr99.43:cvnHP:ct10:cvrChassisVersion:sku12C25UA#ABL:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ef0xxx
  dmi.product.sku: 12C25UA#ABL
  dmi.sys.vendor: HP

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


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

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

Thanks, let me check with others on Monday if that's the right action
for your issue.

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

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

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

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

Bug description:
  [SRU Justification]

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

  [Impact]

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

  [Fix]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

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

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

  == original bug report ==

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

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

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

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


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

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

2023-10-07 Thread Jeroen Webb

My computer booted just fine with that file in /lib/firmware/amdgpu. I
downloaded it again after booting, just to make sure that it was the
right file version.

% ls -l /lib/firmware/amdgpu/gc_11_0_0_imu.bin 
-rw-r--r-- 1 root root 132352 Oct  7 09:36 
/lib/firmware/amdgpu/gc_11_0_0_imu.bin

% sha1sum /lib/firmware/amdgpu/gc_11_0_0_imu.bin
2587fa941d4645e5e38ce4067f630a5c6d51bc23  /lib/firmware/amdgpu/gc_11_0_0_imu.bin

% sha1sum Downloads/gc_11_0_0_imu\(1\).bin Downloads/gc_11_0_0_imu.bin 
2587fa941d4645e5e38ce4067f630a5c6d51bc23  Downloads/gc_11_0_0_imu(1).bin
2587fa941d4645e5e38ce4067f630a5c6d51bc23  Downloads/gc_11_0_0_imu.bin

% dpkg -l | grep firmware 
ii  amd64-microcode  
3.20191218.1ubuntu2.2 amd64 
   Processor microcode firmware for AMD CPUs
ii  firmware-sof-signed  2.0-1ubuntu4.1 
   all  Intel SOF 
firmware - signed
ii  intel-microcode  
3.20230808.0ubuntu0.22.04.1   amd64 
   Processor microcode firmware for Intel CPUs
ii  linux-firmware   
20220329.git681281e4-0ubuntu3.19  all   
   Firmware for Linux kernel drivers

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

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

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

Bug description:
  [SRU Justification]

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

  [Impact]

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

  [Fix]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

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

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

  == original bug report ==

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

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

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

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


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

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

2023-10-07 Thread Jeroen Webb

I believe this is the right journal. It has a couple of amdgpu call
stacks.

I had a lot of restarts trying to get stuff working.

I'll try out that specific file later today.

** Attachment added: "6db523c73ff64c62a3703c38cd11bad9.journal"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2024427/+attachment/5707633/+files/6db523c73ff64c62a3703c38cd11bad9.journal

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

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

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

Bug description:
  [SRU Justification]

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

  [Impact]

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

  [Fix]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

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

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

  == original bug report ==

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

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

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

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


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

[Kernel-packages] [Bug 2038719] Re: Monitor Issues

2023-10-07 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make Ubuntu 
better.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 2038719

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided
with Ubuntu by default, many require manual addition for some releases
of downstream OSes based on Ubuntu (eg. Linux Mint). You should check
with your distribution first.

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

Title:
  Monitor Issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Originally on Kernel 5.13 my GPU is not detected and only one monitor
  out of my three functions. I originally fixed this by moving to the
  latest (6.2) which came with its own issues, of which all were
  resolved.

  Yesterday I updated firmware, and this morning after reboot only one
  monitor works again, and the monitor is all stripey and there are 4 of
  a corner of the screen displayed in strips. The operation is fine but
  the display is broken.

  Hopefully this describes the issue enough, if you need an image just
  tell me how to upload it -  I am on the mint distro, I am a newbie to
  this so I hope this is still the right place.

  CPU: Ryzen 7 3700X
  GPU: Radeon 7900XTX
  Boot: Clean linux only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038719/+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 1949359] Re: crash-utility segfault in ubuntu20.04

2023-10-07 Thread jianpingzhao

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

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

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 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 "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  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  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, 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.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 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 "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.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
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package:

[Kernel-packages] [Bug 2036377] Re: Fix RCU warning on AMD laptops

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1005.5
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.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2036377

Title:
  Fix RCU warning on AMD laptops

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

Bug description:
  [Impact]
  Scary kernel splat about RCU can be observed everytime laptop resumes
  from suspend.

  [Fix]
  Use non-atomic notifier for power supply change to relax the constraint.

  [Test]
  Once the fix is applied, no more RCU warning can be found after several
  suspend/resume cycle.

  [Where problems could occur]
  Essentially no regression potential. Atomic notifier should be used by
  core kernel, and things like power supply doesn't need to be atomic
  anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036377/+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 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1005.5
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 in Ubuntu.
https://bugs.launchpad.net/bugs/2036968

Title:
  Mantic minimized/minimal cloud images do not receive IP address during
  provisioning; systemd regression with wait-online

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Following a recent change from linux-kvm kernel to linux-generic
  kernel in the mantic minimized images, there is a reproducable bug
  where a guest VM does not have an IP address assigned as part of
  cloud-init provisioning.

  This is easiest to reproduce when emulating arm64 on amd64 host. The
  bug is a race condition, so there could exist fast enough
  virtualisation on fast enough hardware where this bug is not present
  but in all my testing I have been able to reproduce.

  The latest mantic minimized images from http://cloud-
  images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and
  no initrd to fallback to.

  This but is not present in the non minimized/base images @
  http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with
  the required drivers present for virtio-net.

  Reproducer

  ```
  wget -O "launch-qcow2-image-qemu-arm64.sh" 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh

  chmod +x ./launch-qcow2-image-qemu-arm64.sh
  wget 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img
  ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image 
./livecd.ubuntu-cpc.img
  ```

  You will then be able to log in with user `ubuntu` and password
  `passw0rd`.

  You can run `ip a` and see that there is a network interface present
  (separate to `lo`) but no IP address has been assigned.

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff

  ```

  This is because when cloud-init is trying to configure network
  interfaces it doesn't find any so it doesn't configure any. But by the
  time boot is complete the network interface is present but cloud-init
  provisioning has already completed.

  You can verify this by running `sudo cloud-init clean && sudo cloud-
  init init`

  You can then see a successfully configured network interface

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
  inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1
     valid_lft 86391sec preferred_lft 86391sec
  inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr 
noprefixroute
     valid_lft 86393sec preferred_lft 14393sec
  inet6 fe80::5054:ff:fe12:3456/64 scope link
     valid_lft forever preferred_lft forever

  ```

  The bug is also reproducible with amd64 guest on adm64 host on
  older/slower hardware.

  The suggested fixes while debugging this issue are:

  * to include `virtio-net` as a built-in in the mantic generic kernel
  * understand what needs to change in cloud-init so that it can react to late 
additions of network interfaces

  I will file a separate bug against cloud-init to address the race
  condition on emulated guest/older hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions


-- 
Mailing list:

[Kernel-packages] [Bug 2037398] Re: kexec enable to load/kdump zstd compressed zimg

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1005.5
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 kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2037398

Title:
  kexec enable to load/kdump zstd compressed zimg

Status in kdump-tools package in Ubuntu:
  Invalid
Status in kexec-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  While testing the 6.5.0-6-generic proposed arm64 generic kernel I
  encountered issues being able to use kdump.

  After enabling -proposed and installing the -proposed 6.5.0-6 kernel
  and rebooting I encountered the following:

  `kdump-config show` shows `current state:Not ready to kdump` and
  looking at the status of the kdump-tools services I see `Cannot
  determine the file type of /var/lib/kdump/vmlinuz`

  Full output:

  ```
  ubuntu@cloudimg:~$ sudo kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0xde00
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.5.0-6-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.5.0-6-generic
  current state:Not ready to kdump

  kexec command:
no kexec command recorded
  ubuntu@cloudimg:~$ sudo service kdump-tools status
  ● kdump-tools.service - Kernel crash dump capture service
   Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; 
preset: enabled)
   Active: active (exited) since Tue 2023-09-26 09:21:44 UTC; 5min ago
  Process: 515 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
 Main PID: 515 (code=exited, status=0/SUCCESS)
  CPU: 4min 21.329s

  Sep 26 09:16:14 cloudimg systemd[1]: Starting kdump-tools.service - Kernel 
crash dump capture service...
  Sep 26 09:16:24 cloudimg kdump-tools[515]: Starting kdump-tools:
  Sep 26 09:16:24 cloudimg kdump-tools[537]:  * Creating symlink 
/var/lib/kdump/vmlinuz
  Sep 26 09:16:32 cloudimg kdump-tools[580]: kdump-tools: Generating 
/var/lib/kdump/initrd.img-6.5.0-6-generic
  Sep 26 09:21:42 cloudimg kdump-tools[537]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Sep 26 09:21:43 cloudimg kdump-tools[5538]: Cannot determine the file type of 
/var/lib/kdump/vmlinuz
  Sep 26 09:21:44 cloudimg kdump-tools[537]:  * failed to load kdump kernel
  Sep 26 09:21:44 cloudimg kdump-tools[5539]: failed to load kdump kernel
  Sep 26 09:21:44 cloudimg systemd[1]: Finished kdump-tools.service - Kernel 
crash dump capture service.

  ubuntu@cloudimg:~$ ls -al /var/lib/kdump/vmlinuz
  lrwxrwxrwx 1 root root 29 Sep 26 09:16 /var/lib/kdump/vmlinuz -> 
/boot/vmlinuz-6.5.0-6-generic
  ubuntu@cloudimg:~$ file /var/lib/kdump/vmlinuz
  /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.5.0-6-generic
  ubuntu@cloudimg:~$ sudo file /boot/vmlinuz-6.5.0-6-generic
  /boot/vmlinuz-6.5.0-6-generic: PE32+ executable (EFI application) Aarch64 
(stripped to external PDB), for MS Windows, 2 sections
  ```

  The reboot with 6.5.0-6 was successful and the reboot after linux-crashdump 
install was successful too. 
  I used https://ubuntu.com/server/docs/kernel-crash-dump guide for installing 
linux-crashdump and attempting to trigger a dump.

  I used arm64 qcow cloud image from http://cloud-
  images.ubuntu.com/mantic/20230925/mantic-server-cloudimg-arm64.img to
  test the above emulated on amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2037398/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1005.5
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.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2037493

Title:
  Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in 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 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:
  [Impact]
  System can't enter suspend on AHCI mode,
  the CPU FAN and System FAN is running, PSU LED is on.
  When fail to enter suspend, remove ODD, the system can successfully enter 
suspend again.

  [Fix]
  Enable LPM on Alder Lake-P AHCI.

  [Test Cases]
  1. enabled AHCI on target machine.
  2. boot with kernel applied fix.
  3. suspend then check slp_s0_residency_usec_cstate_show
  ~~~
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  4951200
  Package C2 : 63571033
  Package C3 : 6212
  Package C6 : 5633477
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 5255561
  u@ubuntu:~$ sudo rtcwake -m mem -s 10
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  12965280
  Package C2 : 75052691
  Package C3 : 46989
  Package C6 : 8108332
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 13628111
  ~~~

  [where the issue could happen]
  Medium, Intel promise there's no issue of ADL AHCI and
  they will take responsibility after regression.
  Intel also take LPM as POR so they will fix any issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037493/+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 2037273] Re: Realtek 8852CE WiFi 6E country code udpates

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1005.5
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 in Ubuntu.
https://bugs.launchpad.net/bugs/2037273

Title:
  Realtek 8852CE WiFi 6E country code udpates

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing WiFi 6G band for interested countries.

  [Fix]

  Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update
  regulatory map to R64-R43").

  [Test Case]

  Use `iw list` to check if 6G bands are then enabled.

  [Where problems could occur]

  This enables corresponding 6G bands for rtw89 driven devices. There
  should be no other side effects.

  [Other Info]

  Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable
  is skipped.

  = original bug report ==

  Proposed fix: 
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
  Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update 
regulatory map to R64-R43") and is in v6.6-rc1 now.

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


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

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

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1005.5
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.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2038263

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

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

Bug description:
  SRU Jusitification for firmware-sof

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

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

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

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

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

  

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

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

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

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

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


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

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

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

apport-collect 2038719

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

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

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

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

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

Title:
  Monitor Issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Originally on Kernel 5.13 my GPU is not detected and only one monitor
  out of my three functions. I originally fixed this by moving to the
  latest (6.2) which came with its own issues, of which all were
  resolved.

  Yesterday I updated firmware, and this morning after reboot only one
  monitor works again, and the monitor is all stripey and there are 4 of
  a corner of the screen displayed in strips. The operation is fine but
  the display is broken.

  Hopefully this describes the issue enough, if you need an image just
  tell me how to upload it -  I am on the mint distro, I am a newbie to
  this so I hope this is still the right place.

  CPU: Ryzen 7 3700X
  GPU: Radeon 7900XTX
  Boot: Clean linux only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038719/+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 2038719] [NEW] Monitor Issues

2023-10-07 Thread Walter Pimax

Public bug reported:

Originally on Kernel 5.13 my GPU is not detected and only one monitor
out of my three functions. I originally fixed this by moving to the
latest (6.2) which came with its own issues, of which all were resolved.

Yesterday I updated firmware, and this morning after reboot only one
monitor works again, and the monitor is all stripey and there are 4 of a
corner of the screen displayed in strips. The operation is fine but the
display is broken.

Hopefully this describes the issue enough, if you need an image just
tell me how to upload it -  I am on the mint distro, I am a newbie to
this so I hope this is still the right place.

CPU: Ryzen 7 3700X
GPU: Radeon 7900XTX
Boot: Clean linux only

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

Title:
  Monitor Issues

Status in linux package in Ubuntu:
  New

Bug description:
  Originally on Kernel 5.13 my GPU is not detected and only one monitor
  out of my three functions. I originally fixed this by moving to the
  latest (6.2) which came with its own issues, of which all were
  resolved.

  Yesterday I updated firmware, and this morning after reboot only one
  monitor works again, and the monitor is all stripey and there are 4 of
  a corner of the screen displayed in strips. The operation is fine but
  the display is broken.

  Hopefully this describes the issue enough, if you need an image just
  tell me how to upload it -  I am on the mint distro, I am a newbie to
  this so I hope this is still the right place.

  CPU: Ryzen 7 3700X
  GPU: Radeon 7900XTX
  Boot: Clean linux only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038719/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen

2023-10-07 Thread Johon Doee

Yes, it still happens with mesa 23.2.1-1ubuntu2. Additionally, it is not
only with video fullscreen. Same happens if I start synaptic for
example. Sometimes it hangs for 10 seconds too. Seems to affect multiple
applications and is triggered by multiple ways.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/9905

** Changed in: mesa (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/2037672

Title:
  amdgpu: [gfxhub] page fault when switching a video to or from
  fullscreen

Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Switching a video to or from fullscreen freezes the screen for around
  10 seconds. This happens with Totem as well as VLC so its not related
  to a specific app.

  Additional observations:

  - The issue seems to be connected to the video's bitrate. With low
  bitrate videos I cannot trigger the freeze. However, videos with high
  bandwidth trigger the freeze reliably.

  Specs:
  Ubuntu 23.10 up to date as of 28.09.2023
  AMD Ryzen 7 PRO 6850U
  Kernel 6.5.0-5-generic
  Grub configured with: amdgpu.vm_update_mode=3

  Syslog shows:

  2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu
  :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2
  pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid
  2311)

  2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772]
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but
  soft recovered

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