[Kernel-packages] [Bug 2064560] Re: kernel panic with linux-intel-iotg 5.15.0.1056.56

[Launchpad Bug Tracker]

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

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

Title:
  kernel panic with linux-intel-iotg 5.15.0.1056.56

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During the SRU testing for linux-intel-iotg 5.15.0.1056.56, Intel ADL-
  PS went into kernel panic. There are no journal logs existed. Please
  check screenshot attached.

  https://certification.canonical.com/hardware/202212-30962/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064560/+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 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.10

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

  * Miscellaneous Ubuntu changes
- [Workflow] Swich to actions/ubuntu-check-commit
  * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283)
- Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
  * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: 
#2053277)
- amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32

 -- Juerg Haefliger   Thu, 21 Mar 2024
08:59:16 +0100

** Changed in: linux-firmware (Ubuntu Mantic)
   Status: Fix Committed => 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/2053277

Title:
  add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy

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

Bug description:
  [SRU Justification]

  [Impact]

  Devices hang up at its desktop (Intel based platform + AMD Navi3.x
  dGPU) during warm boot stress test.

  [Fix]

  AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The
  affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the
  first revision since Jammy is ever released. However, the related
  commits from the upgrade path have also included blob updates to all
  kinds of different, unrelated hardware models.

  This pull request bumps only the affected binary to the target commit
  per online discussion with AMD.

  [Test Case]

  Perform checkbox warmboot stress test:

  $ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  While DCN blob maybe shared with several hardware models, with
  confirmation from IHV, there should be little risk to upgrade it.

  [Other Info]

  Affects both Jammy and Mantic.

  == original bug report ==

  Dell reported sporadically hang up at its desktop (Intel based
  platform + AMD Navi3.x dGPU) during warm boot stress test.

  After updating DMCUB firmware version to 0x07002600, they observed a
  significant improvement in passing rate. And Dell wants to add the
  updated DMCUB firmware (ver 0x7002600) to its OEM image.

  DMCUB firmware (ver 0x7002600) is at
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  
firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.10

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

  * Miscellaneous Ubuntu changes
- [Workflow] Swich to actions/ubuntu-check-commit
  * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283)
- Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
  * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: 
#2053277)
- amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32

 -- Juerg Haefliger   Thu, 21 Mar 2024
08:59:16 +0100

** Changed in: linux-firmware (Ubuntu Mantic)
   Status: Fix Committed => 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/2055283

Title:
  Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

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

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

  [Impact]

  We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image
  and booting up, the bluetooth couldn't work at all. Checking the dmesg,
  the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi,
  but there is no this firmware in the linux-firmware of Jammy, and I
  also checked the Mantic and Noble, Mandic doesn't have this firmware too,
  Noble already has the firmware since the upstream linux-firmware integrated
  the intel/ibt-0180-4150.sfi last year.

  
  [Fix]

  Backport 4 commits from upstream linux-firmware, these 4 commits are all
  on intel/ibt-0180-4150.sfi|ddc

  
  [Test Case]

  Put the firmware into the /lib/firmware/intel/, reboot the machine,
  check dmesg, the bluetooth driver loads the firmware successfully,

  run hciconfig, the hci0 shows up.

  run checkbox testcase, it could pass.
  [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]

  
  [Where problems could occur]

  Probably could make the Intel AX201 BT adapter couldn't work, but the 
possibility
  is very low, we tested the firmware on different lenovo machines with the BT 
adapter
  AX201, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.30

---
linux-firmware (20220329.git681281e4-0ubuntu3.30) jammy; urgency=medium

  * Miscellaneous Ubuntu changes
- [Packaging] rules: Check for git executable
- [Workflow] Swich to actions/ubuntu-check-commit
  * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283)
- Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
  * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: 
#2053277)
- amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32

 -- Juerg Haefliger   Thu, 21 Mar 2024
09:03:22 +0100

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

Title:
  Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Committed

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

  [Impact]

  We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image
  and booting up, the bluetooth couldn't work at all. Checking the dmesg,
  the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi,
  but there is no this firmware in the linux-firmware of Jammy, and I
  also checked the Mantic and Noble, Mandic doesn't have this firmware too,
  Noble already has the firmware since the upstream linux-firmware integrated
  the intel/ibt-0180-4150.sfi last year.

  
  [Fix]

  Backport 4 commits from upstream linux-firmware, these 4 commits are all
  on intel/ibt-0180-4150.sfi|ddc

  
  [Test Case]

  Put the firmware into the /lib/firmware/intel/, reboot the machine,
  check dmesg, the bluetooth driver loads the firmware successfully,

  run hciconfig, the hci0 shows up.

  run checkbox testcase, it could pass.
  [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]

  
  [Where problems could occur]

  Probably could make the Intel AX201 BT adapter couldn't work, but the 
possibility
  is very low, we tested the firmware on different lenovo machines with the BT 
adapter
  AX201, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.30

---
linux-firmware (20220329.git681281e4-0ubuntu3.30) jammy; urgency=medium

  * Miscellaneous Ubuntu changes
- [Packaging] rules: Check for git executable
- [Workflow] Swich to actions/ubuntu-check-commit
  * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283)
- Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
- Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
  * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: 
#2053277)
- amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32

 -- Juerg Haefliger   Thu, 21 Mar 2024
09:03:22 +0100

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

Title:
  add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Devices hang up at its desktop (Intel based platform + AMD Navi3.x
  dGPU) during warm boot stress test.

  [Fix]

  AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The
  affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the
  first revision since Jammy is ever released. However, the related
  commits from the upgrade path have also included blob updates to all
  kinds of different, unrelated hardware models.

  This pull request bumps only the affected binary to the target commit
  per online discussion with AMD.

  [Test Case]

  Perform checkbox warmboot stress test:

  $ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  While DCN blob maybe shared with several hardware models, with
  confirmation from IHV, there should be little risk to upgrade it.

  [Other Info]

  Affects both Jammy and Mantic.

  == original bug report ==

  Dell reported sporadically hang up at its desktop (Intel based
  platform + AMD Navi3.x dGPU) during warm boot stress test.

  After updating DMCUB firmware version to 0x07002600, they observed a
  significant improvement in passing rate. And Dell wants to add the
  updated DMCUB firmware (ver 0x7002600) to its OEM image.

  DMCUB firmware (ver 0x7002600) is at
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  
firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2064354] [NEW] File manager crashes on run

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I 
obtained the following from the command prompt: 
$ nautilus
** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files
libEGL warning: egl: failed to create dri2 screen
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 16:15:29 2024
GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
InstallationDate: Installed on 2024-04-24 (6 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   44.1-1
 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


** Tags: amd64 apport-bug noble wayland-session
-- 
File manager crashes on run
https://bugs.launchpad.net/bugs/2064354
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-535 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 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker
(LP: #2063265)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- [Packaging] Remove renamed out-of-tree sound drivers from blacklist

  [ Ubuntu: 5.15.0-1025.25 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258)
  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume
  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Wed, 24 Apr 2024 08:55:41
-0500

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

Title:
  apply nvidia-tegra patches 2024 Mar 1-7

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+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 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25

---
linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP:
#2063258)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume

  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Tue, 23 Apr 2024 15:45:58
-0500

** Changed in: linux-nvidia-tegra (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  apply nvidia-tegra patches 2024 Feb 6-29

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+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 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker
(LP: #2063265)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- [Packaging] Remove renamed out-of-tree sound drivers from blacklist

  [ Ubuntu: 5.15.0-1025.25 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258)
  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume
  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Wed, 24 Apr 2024 08:55:41
-0500

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

Title:
  apply nvidia-tegra patches 2024 Feb 6-29

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+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 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25

---
linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP:
#2063258)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume

  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Tue, 23 Apr 2024 15:45:58
-0500

** Changed in: linux-nvidia-tegra (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  apply nvidia-tegra patches 2024 Mar 1-7

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+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 2056594] Re: apply nvidia-tegra patches 2024 Mar 8

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker
(LP: #2063265)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- [Packaging] Remove renamed out-of-tree sound drivers from blacklist

  [ Ubuntu: 5.15.0-1025.25 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258)
  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume
  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Wed, 24 Apr 2024 08:55:41
-0500

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

Title:
  apply nvidia-tegra patches 2024 Mar 8

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+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 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25

---
linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP:
#2063258)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume

  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Tue, 23 Apr 2024 15:45:58
-0500

** Changed in: linux-nvidia-tegra (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  apply nvidia-tegra patches 2024 Mar 9-20

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+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 2056594] Re: apply nvidia-tegra patches 2024 Mar 8

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25

---
linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP:
#2063258)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume

  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Tue, 23 Apr 2024 15:45:58
-0500

** Changed in: linux-nvidia-tegra (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  apply nvidia-tegra patches 2024 Mar 8

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+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 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker
(LP: #2063265)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- [Packaging] Remove renamed out-of-tree sound drivers from blacklist

  [ Ubuntu: 5.15.0-1025.25 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258)
  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume
  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Wed, 24 Apr 2024 08:55:41
-0500

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

Title:
  apply nvidia-tegra patches 2024 Mar 9-20

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-
  tegra and linux-nvida-tegra-igx).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+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 2058706] Re: Tegra234 SD card corruption after rebooting some number of times

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker
(LP: #2063265)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- [Packaging] Remove renamed out-of-tree sound drivers from blacklist

  [ Ubuntu: 5.15.0-1025.25 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258)
  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume
  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Wed, 24 Apr 2024 08:55:41
-0500

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: New => Fix Released

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

Title:
  Tegra234 SD card corruption after rebooting some number of times

Status in linux-nvidia-tegra package in Ubuntu:
  New
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  The SD card is being observed to get corrupted after some number of
  reboots, e.g. often in the neighborhood of 10-50 iterations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058706/+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 2059958] Re: Include networking drivers used on Tegra platforms in initrd.img

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed
- 5.15.0-1012.12

---
linux-nvidia-tegra-igx-modules-signed (5.15.0-1012.12) jammy; urgency=medium

  * Master version: 5.15.0-1012.12

 -- Jacob Martin   Wed, 24 Apr 2024 10:31:47
-0500

** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Include networking drivers used on Tegra platforms in initrd.img

Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Committed
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Released

Bug description:
  A race occurs between the probing of network devices and systemd-
  networkd detecting network devices to enable. This can be avoided by
  loading networking drivers earlier in the boot process, which we
  accomplish by including them in the initramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2059958/+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 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx

[Launchpad Bug Tracker]

This bug was fixed in the package linux-meta-nvidia-tegra-igx -
5.15.0.1012.12

---
linux-meta-nvidia-tegra-igx (5.15.0.1012.12) jammy; urgency=medium

  * Bump ABI 5.15.0-1012

  * Add initial r36.3 out-of-tree module meta packages (LP: #2060071)
- [Packaging] Add conflicts against r36.x branch metas

 -- Jacob Martin   Wed, 24 Apr 2024 10:30:22
-0500

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

Title:
  Produce kernel snaps for linux-nvidia-tegra-igx

Status in linux-meta-nvidia-tegra-igx package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Committed
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Released
Status in linux-signed-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  We plan on producing Ubuntu Core images with the linux-nvidia-tegra-
  igx kernel. To support this, add support for producing kernel snaps to
  our kernel source packaging.

  This requires changes to linux-meta-nvidia-tegra-igx, 
linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which 
include:
  * Adding uc meta packages for the -rt and non-rt kernel flavours.
  * Generating signed kernel.efi images.
  * Adding ubuntu-core-initramfs config to include modules unique to Tegra 
platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed
- 5.15.0-1012.12

---
linux-nvidia-tegra-igx-modules-signed (5.15.0-1012.12) jammy; urgency=medium

  * Master version: 5.15.0-1012.12

 -- Jacob Martin   Wed, 24 Apr 2024 10:31:47
-0500

** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Produce kernel snaps for linux-nvidia-tegra-igx

Status in linux-meta-nvidia-tegra-igx package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Committed
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Released
Status in linux-signed-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  We plan on producing Ubuntu Core images with the linux-nvidia-tegra-
  igx kernel. To support this, add support for producing kernel snaps to
  our kernel source packaging.

  This requires changes to linux-meta-nvidia-tegra-igx, 
linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which 
include:
  * Adding uc meta packages for the -rt and non-rt kernel flavours.
  * Generating signed kernel.efi images.
  * Adding ubuntu-core-initramfs config to include modules unique to Tegra 
platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2060071] Re: Add initial r36.3 out-of-tree module meta packages

[Launchpad Bug Tracker]

This bug was fixed in the package linux-meta-nvidia-tegra-igx -
5.15.0.1012.12

---
linux-meta-nvidia-tegra-igx (5.15.0.1012.12) jammy; urgency=medium

  * Bump ABI 5.15.0-1012

  * Add initial r36.3 out-of-tree module meta packages (LP: #2060071)
- [Packaging] Add conflicts against r36.x branch metas

 -- Jacob Martin   Wed, 24 Apr 2024 10:30:22
-0500

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

Title:
  Add initial r36.3 out-of-tree module meta packages

Status in linux-meta-nvidia-tegra-igx package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Released

Bug description:
  We want to enable tracks for different versions of the out-of-tree
  modules. For now we only have R36.3, so create the meta packages for
  that version.

  These meta packages include:
  * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM
  * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2060071/+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 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx

[Launchpad Bug Tracker]

This bug was fixed in the package linux-signed-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-signed-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * Main version: 5.15.0-1012.12

  * Packaging resync (LP: #1786013)
- [Packaging] debian/tracking-bug -- resync from main package

 -- Jacob Martin   Wed, 24 Apr 2024 10:30:12
-0500

** Changed in: linux-signed-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Produce kernel snaps for linux-nvidia-tegra-igx

Status in linux-meta-nvidia-tegra-igx package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Committed
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Released
Status in linux-signed-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  We plan on producing Ubuntu Core images with the linux-nvidia-tegra-
  igx kernel. To support this, add support for producing kernel snaps to
  our kernel source packaging.

  This requires changes to linux-meta-nvidia-tegra-igx, 
linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which 
include:
  * Adding uc meta packages for the -rt and non-rt kernel flavours.
  * Generating signed kernel.efi images.
  * Adding ubuntu-core-initramfs config to include modules unique to Tegra 
platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2060071] Re: Add initial r36.3 out-of-tree module meta packages

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed
- 5.15.0-1012.12

---
linux-nvidia-tegra-igx-modules-signed (5.15.0-1012.12) jammy; urgency=medium

  * Master version: 5.15.0-1012.12

 -- Jacob Martin   Wed, 24 Apr 2024 10:31:47
-0500

** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Add initial r36.3 out-of-tree module meta packages

Status in linux-meta-nvidia-tegra-igx package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Released

Bug description:
  We want to enable tracks for different versions of the out-of-tree
  modules. For now we only have R36.3, so create the meta packages for
  that version.

  These meta packages include:
  * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM
  * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2060071/+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 2060337] Re: apply NVIDIA patches Mar 22 - April 5, 2024

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker
(LP: #2063265)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- [Packaging] Remove renamed out-of-tree sound drivers from blacklist

  [ Ubuntu: 5.15.0-1025.25 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258)
  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume
  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Wed, 24 Apr 2024 08:55:41
-0500

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

Title:
  apply NVIDIA patches Mar 22 - April 5, 2024

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  NVIDIA patches Mar 22 - April 5, 2024.

  NVIDIA tracking details

  soc/tegra: fuse: Remove security_mode fuse from keepout list
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228

  soc/tegra: fuse: Update Tegra234 nvmem keepout list
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227

  arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255

  arm64: defconfig: Enable DMATEST
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125

  PCI: tegra194: Fix probe path for Endpoint mode
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622

  arm64: configs: enable hidraw
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2060337/+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 2060337] Re: apply NVIDIA patches Mar 22 - April 5, 2024

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25

---
linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP:
#2063258)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume

  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Tue, 23 Apr 2024 15:45:58
-0500

** Changed in: linux-nvidia-tegra (Ubuntu)
   Status: New => Fix Released

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: New => Fix Released

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

Title:
  apply NVIDIA patches Mar 22 - April 5, 2024

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  NVIDIA patches Mar 22 - April 5, 2024.

  NVIDIA tracking details

  soc/tegra: fuse: Remove security_mode fuse from keepout list
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228

  soc/tegra: fuse: Update Tegra234 nvmem keepout list
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227

  arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255

  arm64: defconfig: Enable DMATEST
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125

  PCI: tegra194: Fix probe path for Endpoint mode
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622

  arm64: configs: enable hidraw
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2060337/+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 2061900] Re: apply NVIDIA patches April 6-16, 2024

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1012.12

---
linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker
(LP: #2063265)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- [Packaging] Remove renamed out-of-tree sound drivers from blacklist

  [ Ubuntu: 5.15.0-1025.25 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258)
  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume
  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Wed, 24 Apr 2024 08:55:41
-0500

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

Title:
  apply NVIDIA patches April 6-16, 2024

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply NVIDIA patches April 6-16, 2024:

  
  NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016

  NVIDIA: SAUCE: enable handling of macronix block protection
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006

  PCI: dwc: Restore MSI Receiver mask during resume
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2061900/+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 2061900] Re: apply NVIDIA patches April 6-16, 2024

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25

---
linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP:
#2063258)

  * apply NVIDIA patches April 6-16, 2024 (LP: #2061900)
- NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
- NVIDIA: SAUCE: enable handling of macronix block protection
- PCI: dwc: Restore MSI Receiver mask during resume

  * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337)
- NVIDIA: SAUCE: arm64: configs: enable hidraw
- NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode
- NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST
- NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
- NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list
- NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout 
list
- [Config] Enable DMATEST

 -- Jacob Martin   Tue, 23 Apr 2024 15:45:58
-0500

** Changed in: linux-nvidia-tegra (Ubuntu)
   Status: New => Fix Released

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: New => Fix Released

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

Title:
  apply NVIDIA patches April 6-16, 2024

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  Apply NVIDIA patches April 6-16, 2024:

  
  NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016

  NVIDIA: SAUCE: enable handling of macronix block protection
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006

  PCI: dwc: Restore MSI Receiver mask during resume
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2061900/+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 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

[Launchpad Bug Tracker]

This bug was fixed in the package ipu6-drivers -
0~git202404110253.97c94720-0ubuntu1

---
ipu6-drivers (0~git202404110253.97c94720-0ubuntu1) noble; urgency=medium

  [ You-Sheng Yang ]
  * New upstream Release_20240409 release (LP: #2061747)
- drop upstreamed "backport: replace strlcpy with strscpy" patch
- debian: refresh patches
- UBUNTU: SAUCE: firmware: fallback to old firmware path
- UBUNTU: SAUCE: don't fail probing at hwcfg checks

 -- You-Sheng Yang   Thu, 11 Apr 2024 18:38:46 +0800

** Changed in: ipu6-drivers (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  obsolete out-of-tree ivsc dkms in favor of in-tree one

Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-meta-oem-6.8 package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  Fix Committed
Status in linux-meta source package in Noble:
  Fix Committed
Status in linux-meta-oem-6.8 source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
  ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The main fixes are in kernel & dkms packages. This adds ivsc-modules to
  Provides list of linux-image-generic as other built-in linux-modules-foo
  packages do.

  [Test Case]

  The generated meta package linux-image-generic should then provides
  "ivsc-modules".

  [Where problems could occur]

  Meta package changes only. No real effect but in package dependency.

  [Other Info]

  While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
  only be nominated for Unstable/Noble/OEM-6.8.

  == ipu6-drivers, linux, linux-oem-6.8 ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.

  == original bug description ==

  Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel
  demands the use of in-tree IVSC drivers instead of out-of-tree dkms
  from https://github.com/intel/ivsc-driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 2064530] [NEW] Include support for .NET 8 for Ubuntu on Power

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - JAMIE L. DOLAN  - 2024-05-01
12:19:47 ==

This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04

- This has already been added for s390x
- Customer survey showed strong interest in .NET on Linux on Power, having .NET 
on Ubuntu on Power will help in adoption of .NET on Power

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


** Tags: architecture-ppc64le bugnameltc-206154 severity-medium 
targetmilestone-inin2404
-- 
Include support for .NET 8 for Ubuntu on Power
https://bugs.launchpad.net/bugs/2064530
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 2064370] [NEW] Blank screen after boot in raspberry pi 4

[Launchpad Bug Tracker]

You have been subscribed to a public bug:


I just flashed noble arm64+raspi image and booted it in my raspberry pi 4, and 
after initial rainbow screen kernel boots with 4 raspberries on the top and 
boot text appears as normal. But then, before it finishes booting, the screen 
goes blank.

Image is ubuntu-24.04-preinstalled-server-arm64+raspi.img.xz downloaded
at Apr/30.

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 02:29:55 
UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

I know the system booted because I can access it over the network and I
even plugged a usb-serial adapter in the uart GPIOs and from there I can
see the boot does progress to completion and offers me a prompt where I
can use the system normally. But the HDMI screen stays blank.

The funny thing is that I have been trying daily builds for quite some
time now and they used to work well, this is the first one that does
this (the official release).

After testing some config options I found that if I change
"dtoverlay=vc4-kms-v3d" for "dtoverlay=vc4-fkms-v3d" in config.txt then
it boots ok and the screen stays on (note the change from kms to fkms).

I also tried appending ",cma-128" to that line (it is present on other
lines -- like for pi3 and pi0 -- but not on this one), it does not help.

I don't think the issue is with my monitor since it works well for a
long time. Also I checked EDIDs, they are detected when using fkms but
they are blank when using kms:

With KMS:
ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid 
EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty.

With fKMS:
ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid 
edid-decode (hex):

00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00
01 1a 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24
..
(supressed)

I do not use a graphical environment on this unit so I don't know the
consequences of this change (to me it just fixes the issue, but I guess
it was there for a reason).

Let me know if you need any other information from the environment.

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

-- 
Blank screen after boot in raspberry pi 4
https://bugs.launchpad.net/bugs/2064370
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-raspi 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 2064189] Re: Screen flickers after installing Ubuntu 24.04

[Launchpad Bug Tracker]

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

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

Title:
  Screen flickers after installing Ubuntu 24.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been struggling with some random screen flickering after a fresh
  install of Ubuntu 24.04.

  My laptop is running the Mesa Intel(R) HD Graphics 620 (KBL GT2F)
  integrated graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-31-generic 6.8.0-31.31
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:melk   2393 F pipewire
   /dev/snd/controlC0:  melk   2401 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 22:22:53 2024
  InstallationDate: Installed on 2024-04-29 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Dell Inc. Inspiron 3584
  ProcEnviron:
   LANG=pt_BR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=2e0a4d2b-a47f-4fff-8c17-c90f6816b03e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-31-generic N/A
   linux-backports-modules-6.8.0-31-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 05RCHV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd09/12/2023:br1.24:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr:sku08D1:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3584
  dmi.product.sku: 08D1
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064189/+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 2064345] [NEW] Power guest secure boot with key management: userspace portion

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Covering the userspace portion (secvarctl)

Feature:

This feature comprises PowerVM LPAR guest OS kernel verification to
extend the chain of trust from partition firmware to the OS kernel and
includes key management.  GRUB and the host OS kernel are signed with 2
separate public key pairs.  Partition firmware includes the the public
verification key for GRUB in its build and uses it to verify GRUB.  GRUB
includes the public verification key for the OS kernel in its build and
uses it to verify the OS kernel image

Test case:

If secure boot is switched off, any GRUB and kernel boots.
If secure boot is switched on:
  - Properly signed GRUB boots.
  - Improperly signed GRUB does not boot.
  - Tampered signed GRUB does not boot.
  - Properly signed kernels boot.
  - Improperly signed kernels do not boot.
  - Tampered signed kernels do not boot.
TPM PCRs are extended roughly following the TCG PC Client and UEFI specs as 
they apply to POWER.

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


** Tags: architecture-ppc64le bugnameltc-205843 severity-critical 
targetmilestone-inin2404
-- 
Power guest secure boot with key management: userspace portion
https://bugs.launchpad.net/bugs/2064345
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 2064321] [NEW] Power guest secure boot with key management: kernel portion

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Covering the kernel portion

Feature:

This feature comprises PowerVM LPAR guest OS kernel verification using
static keys to extend the chain of trust from partition firmware to the
OS kernel.  GRUB and the host OS kernel are signed with 2 separate
public key pairs.  Partition firmware includes the the public
verification key for GRUB in its build and uses it to verify GRUB.  GRUB
includes the public verification key for the OS kernel in its build and
uses it to verify the OS kernel image

Test case:

If secure boot is switched off, any GRUB and kernel boots.
If secure boot is switched on:
  - Properly signed GRUB boots.
  - Improperly signed GRUB does not boot.
  - Tampered signed GRUB does not boot.
  - Properly signed kernels boot.
  - Improperly signed kernels do not boot.
  - Tampered signed kernels do not boot.
TPM PCRs are extended roughly following the TCG PC Client and UEFI specs as 
they apply to POWER.

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


** Tags: architecture-ppc64le bugnameltc-205842 severity-critical 
targetmilestone-inin2404
-- 
Power guest secure boot with key management: kernel portion
https://bugs.launchpad.net/bugs/2064321
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 2064298] [NEW] Tochupad issue

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have installed windows and ubuntu in my Lenovo think book and using
both of them with dual booting. Unfortunately, I have issues with my
touchpad. It's not working in ubuntu but working in windows. So, I
request you to find a way for me.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-31-generic 6.8.0-31.31
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:falih  2177 F pipewire
 /dev/snd/pcmC0D0p:   falih  2177 F...m pipewire
 /dev/snd/controlC0:  falih  2177 F pipewire
  falih  2181 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 20:16:20 2024
InstallationDate: Installed on 2024-04-28 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: LENOVO 20RV
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=4f984407-48a9-41a7-b36f-10fb247a8235 ro i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop quiet splash psmouse.proto=bare vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-31-generic N/A
 linux-backports-modules-6.8.0-31-generic  N/A
 linux-firmware20240318.git3b128b60-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2023
dmi.bios.release: 1.42
dmi.bios.vendor: LENOVO
dmi.bios.version: CJCN42WW
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.ec.firmware.release: 1.34
dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN42WW:bd06/07/2023:br1.42:efr1.34:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:skuLENOVO_MT_20RV_BU_idea_FM_LenovoThinkBook14-IML:
dmi.product.family: Lenovo ThinkBook 14-IML
dmi.product.name: 20RV
dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
dmi.product.version: Lenovo ThinkBook 14-IML
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug noble wayland-session
-- 
Tochupad issue
https://bugs.launchpad.net/bugs/2064298
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 2064135] [NEW] Thinkpad T510 hangs during installation

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Boot install disk and system freezes when desktop appears.  
Booted with nomodeset kernel option and completed install.
Booted up installed system and after desktop shown complete system hang.
Installed 6.7 kernel and booted with that and everything is fine. 
Appears to be a but in latest kernel and intel drivers

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubiquity (not installed)
Uname: Linux 6.7.0-060700rc8-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Mon Apr 29 10:35:10 2024
InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=5fa53d37-cc0c-4b60-b6b7-d5916b8df332 ro quiet splash vt.handoff=7
InstallationDate: Installed on 2024-04-29 (0 days ago)
InstallationMedia: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Release amd64 
(20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble
-- 
Thinkpad T510 hangs during installation
https://bugs.launchpad.net/bugs/2064135
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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~juergh/ubuntu-seeds/+git/ubuntu/+merge/465215

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~simpoir/livecd-rootfs/+git/livecd-rootfs/+merge/465193

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in livecd-rootfs source package in Jammy:
  Fix Released
Status in util-linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in livecd-rootfs source package in Mantic:
  New
Status in util-linux source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in livecd-rootfs source package in Noble:
  Fix Released
Status in util-linux source package in Noble:
  New

Bug description:
  [impact]
  In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, 
with the expectation that this would give us a reliable, race-free way of 
loop-mounting partitions from a disk image during image build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

    https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

    https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

  The losetup usage has been backported to Jammy, and sees frequent
  failures there.

  [test case]
  The autopkgtests will provide enough confidence that the changes are not 
completely broken. Whether the change helps with the races on riscv can be 
"tested in prod" just as well as any other way.

  [regression potential]
  If the backport has been done incorrectly, image builds can fail (and the 
autopkgtests will fail if it has been completely bungled). This can be quickly 
handled. There is no foreseeable way for this to result in successful builds 
but broken images, which would be a much more difficult failure mode to unpick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

[Launchpad Bug Tracker]

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

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

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857760/+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 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

[Launchpad Bug Tracker]

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

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

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857760/+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 2064017] [NEW] Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:


My machine information is following :
HP EliteBook 840 G3
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520]
xrandr -q active mode on laptop display : 1368x768  60.01

Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped 
kernel 6.8.0-31), same issue.
Rolling back the kernel to 6.7 fixed the problem,maybe there were some video 
driver changes from kernel 6.7 to 6.8 ?

While using the 6.8 kernel I did some experiments:

disabled picom in startup , no effect

Tried changing display resolution, just moves vertical position of band.
(at the above resolution 1368x768 vertical mouse pointer flicker range is 
around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from 
a bash terminal)

Tried moving refresh rate slightly around 60 Hz by creating a new
modeline using cvt tool and adding new mode with xrandr, no effect.

tried connecting external display on laptop VGA port and duplicating
screen and the issue seems to disappear.

tried capturing a video of the desktop  using ffmpeg with x11grab, but
it does not show the issue.

I attached a short video of the laptop display flicker I recorded using
my phone

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: LXQt
Date: Sun Apr 28 09:44:42 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
InstallationDate: Installed on 2024-04-25 (3 days ago)
InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP HD Camera
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP EliteBook 840 G3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2019
dmi.bios.release: 1.42
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.42
dmi.board.name: 8079
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.78
dmi.chassis.asset.tag: 5CG7042V5J
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 133.120
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 840 G3
dmi.product.sku: Z2A57UT#ABA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption noble ubuntu
-- 
Xserver Display flickers when mouse pointer is inside narrow horizontal range 
band (kernel related)
https://bugs.launchpad.net/bugs/2064017
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 2054560] Re: Xorg freeze: i915 flips and commits are timing out

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze: i915 flips and commits are timing out

Status in linux-hwe-6.5 package in Ubuntu:
  Expired

Bug description:
  Random freezes occur since the installation of 6.5.x kernel. 
  Freeze occur several times a day, probably after touching the mouse or 
keyboard, but I'm not sure.
  App continue to work sound is OK, there is just no dispay updated.

  Booting to old 6.2 kernel solves the problem. I have tried all 6.5
  updates since the first released, but each time, I had a freeze after
  a few hours.

  Example of last mesg in dmesg when freeze occur :

  Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out

  or :
  Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), 
lowering kernel.perf_event_max_sample_rate to 79750
  Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
  Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
  Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
  Feb 13 11:36:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed 

[Kernel-packages] [Bug 2055162] Re: linux-headers package not being pulled in with linux-image-generic

[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/2055162

Title:
  linux-headers package not being pulled in with linux-image-generic

Status in linux package in Ubuntu:
  Expired

Bug description:
  linux-image-5.15.0-97-generic definitely exists in Ubuntu and it does
  not pull in the correct linux-header package which is required to
  rebuilt nvidia kernel modules.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136
  Uname: Linux 5.15.0-97-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Feb 27 08:29:48 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2023-06-16 (256 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055162/+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 1902896] Re: Thunderbolt dock no longer works

[Launchpad Bug Tracker]

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

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

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

Title:
  Thunderbolt dock no longer works

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

Bug description:
  I'm using Lubuntu 20.04 on Dell XPS 13 9360. Somehow thunderbolt
  stopped working. I've attached the relevant output from /var/syslog.
  I'm using 5.4.0-52-generic. I've updated all my firmware through
  fwupdmgr.

  Briefly, the kernel complains 
  kernel: pci :01:00.0: BAR 13: no space for [io  size 0x3000]
  kernel: pci :01:00.0: BAR 13: failed to assign [io  size 0x3000]

  then
  kernel: usb 3-1.3: config 1 has no interfaces?

  then

  kernel: xhci_hcd :39:00.0: xHCI host controller not responding, assume 
dead
  kernel: r8152 4-1.4:1.0 enxd481d70b2831: Stop submitting intr, status -108
  kernel: xhci_hcd :39:00.0: HC died; cleaning up

  then 
  kernel: xhci_hcd :39:00.0: Host halt failed, -19
  kernel: xhci_hcd :39:00.0: Host not accessible, reset failed. 

  then

  kernel: pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID) 
  kernel: pcieport :00:1c.0: AER:   device [8086:9d10] error 
status/mask=0001/2000   

  kernel: pcieport :00:1c.0: AER:[ 0] RxErr

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.3
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert  820 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Nov  4 16:07:31 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-05-11 (176 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=95de7ebe-d429-45d7-9548-0d5af627a560 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.14.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 075B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902896/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Launchpad Bug Tracker]

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

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

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

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still
  controlled by simpledrm, while Nvidia uses /dev/dri/card1.

  [ Workaround ]

  1. sudo rm /dev/dri/card0
  2. Log in again.

  [ Test Plan ]

  Open Settings and verify the only monitors shown are your real
  monitors.

  [ Where problems could occur ]

  Removing the simpledrm card is only safe when it's not being used. If
  somehow a machine wasn't using the installed Nvidia driver then there
  could be a risk of deleting the only working display.

  [ Other Info ]

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble
  Uname: Linux 6.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: RNUC12DCMi7
  dmi.product.version: M30143-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

[Launchpad Bug Tracker]

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

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

Title:
  24.04 Upgrade/Fresh Install results in black screen on reboot on
  AMDGPU system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.

  Using xUbuntu.

  I had been daily driving the 24.04 nightly iso since March. About a
  week ago, I took a kernel update via apt and rebooted. The result was
  that the system would hard freeze to a black screen after the initial
  kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
  switching terminals (ctrl-alt-f#) did nothing, had to hard power off
  to regain control of the system.

  I tried various fixes, none of which permanently stuck. This includes
  nomodeset in grub, rebooting into safe mode, checking for proprietary
  drivers. Safe mode allowed me to reboot once more into desktop, but
  then any subsequent reboots would result in a black screen lockup.

  Suspending while able to use the desktop before reboot would cause a
  black screen lockup did not seem to cause any issues.

  3 days before 24.04 was officially released, I reflashed the most
  recent installer iso to my thumbdrive, copied my home folder to my
  RAID and did a full wipe and fresh install.

  First reboot after installation always went to the desktop. Subsequent
  reboots always resulted in a black screen lockup.

  Memtest cleared without errors.

  Again tried various fixes, nomodeset, safe mode, drivers. The only
  consistency was that regardless of what I could do to regain control
  or what I did differently when doing a wipe and reinstall, I would
  always reboot to a black screen.

  Once 24.04 was officially released, I again did a full wipe and
  reinstall and encountered all of the above same issues as before.

  After mentioning this in #ubuntu on libera, someone suggested a kernel
  downgrade.

  24.04 as installed was using 6.8.0-31.31

  Using Mainline, I downgraded to the next minor version below 6.8 that
  was considered stable. 6.7.10

  Problem went away. No more black screen on boot, no more hard power
  offs required to be able to use my system again, no suspend issues.
  Was not necessary for me to do anything else to maintain a consistent
  successful reboot to desktop.

  Did yet another full wipe and fresh install of 24.04, only installing
  Mainline upon first reboot to install 6.7.10, using Grub Customizer to
  edit the default grub option to boot the 6.7.10 kernel instead.

  No issues.

  I apologise that I did not collect logs during this process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+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 2063060] Re: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 4

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  nvidia driver 390

  dkms390

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Apr 21 23:45:13 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
  InstallationDate: Installed on 2024-04-02 (19 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.12
  SourcePackage: dkms
  Title: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2063060/+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 2063983] [NEW] 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.

Using xUbuntu.

I had been daily driving the 24.04 nightly iso since March. About a week
ago, I took a kernel update via apt and rebooted. The result was that
the system would hard freeze to a black screen after the initial kernel
messages cleared from the screen. Ctrl-Alt-Del did nothing, switching
terminals (ctrl-alt-f#) did nothing, had to hard power off to regain
control of the system.

I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but then
any subsequent reboots would result in a black screen lockup.

Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.

3 days before 24.04 was officially released, I reflashed the most recent
installer iso to my thumbdrive, copied my home folder to my RAID and did
a full wipe and fresh install.

First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.

Memtest cleared without errors.

Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control or
what I did differently when doing a wipe and reinstall, I would always
reboot to a black screen.

Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.

After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.

24.04 as installed was using 6.8.0-31.31

Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10

Problem went away. No more black screen on boot, no more hard power offs
required to be able to use my system again, no suspend issues. Was not
necessary for me to do anything else to maintain a consistent successful
reboot to desktop.

Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.

No issues.

I apologise that I did not collect logs during this process.

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

-- 
24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
https://bugs.launchpad.net/bugs/2063983
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 2052637] Re: [i386] please add 550-server to the i386 seed

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-535-server (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [i386] please add 550-server to the i386 seed

Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Expired

Bug description:
  Please add the following packages to i386 seed:

  - nvidia-graphics-drivers-550-server

  The other one:

  - nvidia-graphics-drivers-550 is already included.

  
  such that beta driver can be packaged and built for i386.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2052637/+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 2063893] Re: after last OS uptate system will not boot normaly.

[Launchpad Bug Tracker]

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

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

Title:
  after last OS uptate system will not boot normaly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot
  into Linux 6.5.0-28 generic if forced.   I have never had an issue
  before with OS updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063893/+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 2060984] Re: FFe: New firmware release

[Launchpad Bug Tracker]

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

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

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

Title:
  FFe: New firmware release

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  A new upstream release of linux-firmware was tagged on 2024.04.10,
  this would sync us with that. Changes:

   - imx: sdma: update firmware to v3.6/v4.6
   - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200
   - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B
   - Montage: update firmware for Mont-TSSE
   - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops
   - rtw88: Add RTL8703B firmware v11.0.0
   - rtw89: 8922a: add firmware v0.35.18.0
   - rtw89: 8852c: update fw to v0.27.56.14
   - mekdiatek: Update mt8186 SOF firmware to v2.0.1
   - linux-firmware: update firmware for en8811h 2.5G ethernet phy
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - i915: Add DG2 HuC 7.10.15
   - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
   - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2063893] [NEW] after last OS uptate system will not boot normaly.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot into
Linux 6.5.0-28 generic if forced.   I have never had an issue before
with OS updates.

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


** Tags: bot-comment
-- 
after last OS uptate system will not boot normaly.
https://bugs.launchpad.net/bugs/2063893
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 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics

[Launchpad Bug Tracker]

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

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

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

Title:
  Fix system hang while entering suspend with AMD Navi3x graphics

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

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  The system with AMD W7500/W7600/W7700 graphics will randomly hang when 
entering suspend. The page fault would keep happening and the system can't 
handle other tasks.
  BUG: unable to handle page fault for address: 0a980148 

  [Fix]
  Backport the fix from upstream 
  drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
  drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · 
GitHub
  https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  Improve the error handling when suspend and add the fallback mechanism in MES 
engine. Only observed on particular AMD models. Need to test w/ more 
combinations

  
=

  SRU Jusitification for linux-firmware

  [Impact]
  The system will randomly hang due to page fault while suspending.

  [Fix]
  Add release FW binary from AMD to linux-firmware
  dcn_3_2_0_dmcub.bin for Navi31 and 32: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47
 [git.kernel.org]
  dcn_3_2_1_dmcub.bin for Navi33: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a
 [git.kernel.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Test with latest linux kernel and linux-firmware
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The 
impact are restricted to particular series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063417/+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 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics

[Launchpad Bug Tracker]

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

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

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

Title:
  Fix system hang while entering suspend with AMD Navi3x graphics

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

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  The system with AMD W7500/W7600/W7700 graphics will randomly hang when 
entering suspend. The page fault would keep happening and the system can't 
handle other tasks.
  BUG: unable to handle page fault for address: 0a980148 

  [Fix]
  Backport the fix from upstream 
  drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
  drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · 
GitHub
  https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  Improve the error handling when suspend and add the fallback mechanism in MES 
engine. Only observed on particular AMD models. Need to test w/ more 
combinations

  
=

  SRU Jusitification for linux-firmware

  [Impact]
  The system will randomly hang due to page fault while suspending.

  [Fix]
  Add release FW binary from AMD to linux-firmware
  dcn_3_2_0_dmcub.bin for Navi31 and 32: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47
 [git.kernel.org]
  dcn_3_2_1_dmcub.bin for Navi33: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a
 [git.kernel.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Test with latest linux kernel and linux-firmware
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The 
impact are restricted to particular series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063417/+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 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics

[Launchpad Bug Tracker]

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

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

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

Title:
  Fix system hang while entering suspend with AMD Navi3x graphics

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

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  The system with AMD W7500/W7600/W7700 graphics will randomly hang when 
entering suspend. The page fault would keep happening and the system can't 
handle other tasks.
  BUG: unable to handle page fault for address: 0a980148 

  [Fix]
  Backport the fix from upstream 
  drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
  drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · 
GitHub
  https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  Improve the error handling when suspend and add the fallback mechanism in MES 
engine. Only observed on particular AMD models. Need to test w/ more 
combinations

  
=

  SRU Jusitification for linux-firmware

  [Impact]
  The system will randomly hang due to page fault while suspending.

  [Fix]
  Add release FW binary from AMD to linux-firmware
  dcn_3_2_0_dmcub.bin for Navi31 and 32: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47
 [git.kernel.org]
  dcn_3_2_1_dmcub.bin for Navi33: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a
 [git.kernel.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Test with latest linux kernel and linux-firmware
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The 
impact are restricted to particular series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063417/+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 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics

[Launchpad Bug Tracker]

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

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

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

Title:
  Fix system hang while entering suspend with AMD Navi3x graphics

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

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  The system with AMD W7500/W7600/W7700 graphics will randomly hang when 
entering suspend. The page fault would keep happening and the system can't 
handle other tasks.
  BUG: unable to handle page fault for address: 0a980148 

  [Fix]
  Backport the fix from upstream 
  drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
  drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · 
GitHub
  https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  Improve the error handling when suspend and add the fallback mechanism in MES 
engine. Only observed on particular AMD models. Need to test w/ more 
combinations

  
=

  SRU Jusitification for linux-firmware

  [Impact]
  The system will randomly hang due to page fault while suspending.

  [Fix]
  Add release FW binary from AMD to linux-firmware
  dcn_3_2_0_dmcub.bin for Navi31 and 32: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47
 [git.kernel.org]
  dcn_3_2_1_dmcub.bin for Navi33: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a
 [git.kernel.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Test with latest linux kernel and linux-firmware
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The 
impact are restricted to particular series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063417/+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 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics

[Launchpad Bug Tracker]

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

** 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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2063417

Title:
  Fix system hang while entering suspend with AMD Navi3x graphics

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

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  The system with AMD W7500/W7600/W7700 graphics will randomly hang when 
entering suspend. The page fault would keep happening and the system can't 
handle other tasks.
  BUG: unable to handle page fault for address: 0a980148 

  [Fix]
  Backport the fix from upstream 
  drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
  drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · 
GitHub
  https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  Improve the error handling when suspend and add the fallback mechanism in MES 
engine. Only observed on particular AMD models. Need to test w/ more 
combinations

  
=

  SRU Jusitification for linux-firmware

  [Impact]
  The system will randomly hang due to page fault while suspending.

  [Fix]
  Add release FW binary from AMD to linux-firmware
  dcn_3_2_0_dmcub.bin for Navi31 and 32: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47
 [git.kernel.org]
  dcn_3_2_1_dmcub.bin for Navi33: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a
 [git.kernel.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Test with latest linux kernel and linux-firmware
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The 
impact are restricted to particular series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063417/+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 2063495] Re: Kernel soft lockup occures in `fib6_select_path` function

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Kernel soft lockup occures in `fib6_select_path` function

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

Bug description:
  We operate a Linux-based cluster of edge routers within a highly
  dynamic setting where BGP-advertised routes constantly evolve due to
  new next hop destinations frequently appearing and disappearing. In
  areas experiencing significant IPv6 traffic, we periodically face
  kernel soft lockups. Upon investigation, these lockups seem to occur
  during the traversal of the multipath circular linked-list, for
  finding the optimal path, in the fib6_select_path function,
  specifically while iterating through the siblings in the multipath
  linked-list. The problem typically arises when the linked list is
  unexpectedly deleted (its list-head reference count equals zero),
  leading to an infinite loop. This results in a soft lockup that
  triggers a system panic due to the watchdog timer.

  It's worth noting that this is a longstanding issue we've been dealing
  with for about a year. Despite switching between different kernel
  versions, the problem persists.

  Attached please find the `.crash` report generated by `apport-cli`.

  Thanks,
  Omid

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr 23 00:00:14 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  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.5/+bug/2063495/+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 2063497] Re: MIPI camera on Lenovo Carbon X1 will not work

[Launchpad Bug Tracker]

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

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

Title:
  MIPI  camera on Lenovo Carbon X1 will not work

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

Bug description:
  I followed the suggestions here for handling the Intel MIPI camera
  replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo

  Perhaps I should have installed 22.04?  Anyway, this is a new laptop
  so I went with the new release.

  I tried both the generic and oem kernel.  Same.  The pertinent message
  seems to be:

  [   18.420012] intel-ipu6 :00:05.0: Direct firmware load for 
intel/ipu6ep_fw.bin failed with error -2
  [   18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed
  [   18.420023] intel-ipu6: probe of :00:05.0 failed with error -2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063497/+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 2063827] [NEW] Gnome Control Center fails to open on Wayland

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome
Control Center does not open on Wayland, but does on Xorg, attempting to
open it will simply open the crash dialog after some time.

When running from the terminal:

$ gnome-control-center 
libEGL warning: egl: failed to create dri2 screen
Segmentation fault (core dumped)

Version installed:

gnome-control-center:
  Installed: 1:46.0.1-1ubuntu7
  Candidate: 1:46.0.1-1ubuntu7

My current installation is very lightweight, and I haven't removed any
packages or changed any system files.

This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB
with the driver version being 535.171.04

If more information is needed, please let me know, however I might be
slow to respond.

Thank you.

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

-- 
Gnome Control Center fails to open on Wayland
https://bugs.launchpad.net/bugs/2063827
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-535 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 2063503] [NEW] NVidia drivers won't install completely

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

ll versions of the nvidia driver fail to install no matter what.
Including the one downloaded from Nvidia. It doesn't matter the version.

:~$ sudo apt install nvidia-driver-550
[sudo] password for jim: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  nvidia-firmware-545-545.29.06
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550
  libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386
  libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550
  libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550
  libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550
  nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550
  nvidia-utils-550 xserver-xorg-video-nvidia-550
The following packages will be REMOVED:
  libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545
  libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386
  libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545
  libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545
  libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545
  nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545
  nvidia-utils-545 xserver-xorg-video-nvidia-545
The following NEW packages will be installed:
  libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550
  libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386
  libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550
  libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550
  libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550
  nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550
  nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550
0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded.
2 not fully installed or removed.
Need to get 360 MB of archives.
After this operation, 14.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 
amd64 550.67-0ubuntu3 [35.8 kB]
Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB]
Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB]
Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB]
Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB]
Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB]
Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB]
Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB]
Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB]
Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB]
Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB]
Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB]
Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB]
Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB]
Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB]
Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB]
Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB]
Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-kernel-common-550 amd64 550.67-0ubuntu3 [120 kB]
Get:19 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-utils-550 amd64 550.67-0ubuntu3 [521 kB]
Get:20 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
xserver-xorg-video-nvidia-550 amd64 550.67-0ubuntu3 [1,616 kB]
Get:21 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-driver-550 amd64 550.67-0ubuntu3 [486 kB]
Fetched 360 MB in 30s (11.8 MB/s)  
(Reading database ... 339762 files and directories currently installed.)
Removing nvidia-driver-545 (545.29.06-0ubuntu0~gpu24.04.1) ...
Removing 

[Kernel-packages] [Bug 2063229] Re: SATA devices on Alder-Lake S not recognized

[Launchpad Bug Tracker]

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

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

Title:
  SATA devices on Alder-Lake S not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Jammy (kernel 5.15.0-94) and Ubuntu Noble (kernel 6.8.0-22)
  installations and Ubuntu Mantic installed hard drive (kernel
  6.5.0-28-generic) are unable to find SATA devices on Alder-Lake S
  Intel SATA controller.

  Ubuntu Focal and Bionic works just fine. Debian 12 (kernel 6.1.0-18)
  and other debian based distros (Mint, Kali, OpenMediaVault, Proxmox)
  works just fine.

  relevant dmesg logs:
  2024-04-19T17:18:50.668222+00:00 ubuntu-server kernel: ahci :00:17.0: 
version 3.0
  2024-04-19T17:18:50.668356+00:00 ubuntu-server kernel: ahci :00:17.0: 
AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf0 impl SATA mode
  2024-04-19T17:18:50.668358+00:00 ubuntu-server kernel: ahci :00:17.0: 
flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds
  2024-04-19T17:18:50.668361+00:00 ubuntu-server kernel: intel-lpss 
:00:15.0: enabling device (0004 -> 0006)
  2024-04-19T17:18:50.668362+00:00 ubuntu-server kernel: idma64 idma64.0: Found 
Intel integrated DMA 64-bit
  2024-04-19T17:18:50.668363+00:00 ubuntu-server kernel: scsi host0: ahci
  2024-04-19T17:18:50.668364+00:00 ubuntu-server kernel: scsi host1: ahci
  2024-04-19T17:18:50.668370+00:00 ubuntu-server kernel: scsi host2: ahci
  2024-04-19T17:18:50.668371+00:00 ubuntu-server kernel: scsi host3: ahci
  2024-04-19T17:18:50.668372+00:00 ubuntu-server kernel: scsi host4: ahci
  2024-04-19T17:18:50.668373+00:00 ubuntu-server kernel: scsi host5: ahci
  2024-04-19T17:18:50.668374+00:00 ubuntu-server kernel: scsi host6: ahci
  2024-04-19T17:18:50.668380+00:00 ubuntu-server kernel: scsi host7: ahci
  2024-04-19T17:18:50.668383+00:00 ubuntu-server kernel: ata1: DUMMY
  2024-04-19T17:18:50.668385+00:00 ubuntu-server kernel: ata2: DUMMY
  2024-04-19T17:18:50.668386+00:00 ubuntu-server kernel: ata3: DUMMY
  2024-04-19T17:18:50.668387+00:00 ubuntu-server kernel: ata4: DUMMY
  2024-04-19T17:18:50.668388+00:00 ubuntu-server kernel: ata5: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8300 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668389+00:00 ubuntu-server kernel: ata6: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8380 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668390+00:00 ubuntu-server kernel: ata7: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8400 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668391+00:00 ubuntu-server kernel: ata8: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8480 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668392+00:00 ubuntu-server kernel: ahci :02:00.0: 
enabling device ( -> 0003)
  2024-04-19T17:18:50.668393+00:00 ubuntu-server kernel: ahci :02:00.0: SSS 
flag set, parallel bus scan disabled
  2024-04-19T17:18:50.668394+00:00 ubuntu-server kernel: ahci :02:00.0: 
AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
  2024-04-19T17:18:50.668395+00:00 ubuntu-server kernel: ahci :02:00.0: 
flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs
  2024-04-19T17:18:50.668396+00:00 ubuntu-server kernel: scsi host8: ahci
  2024-04-19T17:18:50.668397+00:00 ubuntu-server kernel: scsi host9: ahci
  2024-04-19T17:18:50.668398+00:00 ubuntu-server kernel: ata9: SATA max 
UDMA/133 abar m512@0x8211 port 0x82110100 irq 130 lpm-pol 0
  2024-04-19T17:18:50.668399+00:00 ubuntu-server kernel: ata10: SATA max 
UDMA/133 abar m512@0x8211 port 0x82110180 irq 130 lpm-pol 0
  2024-04-19T17:18:50.668400+00:00 ubuntu-server kernel: intel-lpss 
:00:15.1: enabling device (0004 -> 0006)
  2024-04-19T17:18:50.668401+00:00 ubuntu-server kernel: idma64 idma64.1: Found 
Intel integrated DMA 64-bit
  2024-04-19T17:18:50.668407+00:00 ubuntu-server kernel: ata7: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668408+00:00 ubuntu-server kernel: ata9: SATA link down 
(SStatus 0 SControl 300)
  2024-04-19T17:18:50.668409+00:00 ubuntu-server kernel: ata5: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668410+00:00 ubuntu-server kernel: ata6: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668411+00:00 ubuntu-server kernel: ata8: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668435+00:00 ubuntu-server kernel: ata10: SATA link down 
(SStatus 0 SControl 300)
  2024-04-19T17:18:50.668466+00:00 ubuntu-server kernel: raid6: avx2x4   gen() 
37283 MB/s
  2024-04-19T17:18:50.668467+00:00 ubuntu-server kernel: raid6: avx2x2   gen() 
39645 MB/s
  2024-04-19T17:18:50.668468+00:00 ubuntu-server kernel: raid6: avx2x1   gen() 
35756 MB/s
  2024-04-19T17:18:50.668469+00:00 ubuntu-server kernel: raid6: using algorithm 
avx2x2 gen() 39645 MB/s
  

[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

[Launchpad Bug Tracker]

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

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

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

Title:
  No input through internal microphone (Ryzen 6000)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after
  updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This
  is a known problem and a patch may be included in kernel 6.8.3.

  Is it possible to backport this patch? Or is the plan to wait for a
  kernel update? It would be good use the microphone in 24.04.

  The symptoms are exactly as described in
  https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297

  Reportedly the patch is included in
  
https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2063150] Re: No sound after upgrade to 24.04

[Launchpad Bug Tracker]

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

** Changed in: pipewire (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/2063150

Title:
  No sound after upgrade to 24.04

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 23.10 to 24.04, it does not work on the
  computer.

  Work with:
  1) Bluetooth
  2) Jack 3.5

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pipewire 1.0.5-1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 15:52:58 2024
  InstallationDate: Installed on 2024-03-25 (28 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+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 2037335] Re: kernel leaking TCP_MEM

[Launchpad Bug Tracker]

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

** Changed in: linux-meta-aws-6.2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  kernel leaking TCP_MEM

Status in linux-meta-aws-6.2 package in Ubuntu:
  Confirmed

Bug description:
  We are running our Kafka brokers on Jammy on ARM64. Previous they were
  on kernel version 5.15.0-1028-aws, but a few weeks ago we built a new
  AMI and it picked up 6.2.0-1009-aws, and we have also upgraded to
  6.2.0-1012-aws and found the same problem.

  What we expected to happen:
  TCP memory (TCP_MEM) to fluctuate but stay relatively low (on a busy 
production broker running 5.15.0-1028-aws, we average 1900 pages over a 24 hour 
period)

  What happened instead:
  TCP memory (TCP_MEM) continues to rise until hitting the limit (1.5 million 
pages as configured currently). At this point, the broker is no longer able to 
properly create new connections and we start seeing "kernel: TCP: out of memory 
-- consider tuning tcp_mem" in dmesg output. If allowed to continue, the broker 
will eventually isolate itself from the rest of the cluster since it can't talk 
to the other brokers.

  Attached is a graph of the average TCP memory usage per kernel version
  for our production environment over the past 24 hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-aws 6.2.0.1012.12~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-1012.12~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1012-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-east-1
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Sep 25 20:56:02 2023
  Ec2AMI: ami-0b9c5aafc5b2a4725
  Ec2AMIManifest: (unknown)
  Ec2Architecture: arm64
  Ec2AvailabilityZone: us-east-1b
  Ec2Imageid: ami-0b9c5aafc5b2a4725
  Ec2InstanceType: im4gn.4xlarge
  Ec2Instancetype: im4gn.4xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-east-1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-aws-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-meta-aws-6.2/+bug/2037335/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

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

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

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

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

** Changed in: protection-domain-mapper (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2056387] Re: [T14 Gen 3 AMD] Fail to suspend/resume for the second time

[Launchpad Bug Tracker]

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

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

Title:
  [T14 Gen 3 AMD] Fail to suspend/resume for the second time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had a similar issue before:
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
  However, I haven't seen the issue with later kernels until getting 
6.8.0-11.11+1 recently.

  * 6.8.0-11 - fails to suspend/resume for the second time although the first 
suspend/resume works
  * 6.6.0-14 - no issue in terms of suspend/resume

  One thing worth noting is that connecting an external monitor or not
  might be a key to trigger this issue. I cannot reproduce it when an
  external monitor (through USB-C to HDMI) is not connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-11-generic 6.8.0-11.11
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 11:17:31 2024
  InstallationDate: Installed on 2024-01-08 (59 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  MachineType: LENOVO 21CFCTO1WW
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2023
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET73W (1.49 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CFCTO1WW
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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 2063143] [NEW] Frequent boot to black display

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hardware: AMD Framework 13
OS: Ubuntu Noble 24.04
DE: Plasma Wayland
BIOS: version 3.03 and 3.05 (latest new release)
Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 
2024 x86_64 x86_64 x86_64 GNU/Linux

This issue started about 2-3 weeks ago I believe around the time that
Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
This issue may not be a kernel regression but instead a wayland
regression but I am not certain and looking for help.

The issue is that on boot the (internal laptop and external displays if
connected) are black but backlight is lit. I am able to boot into
recovery mode without issue since the graphics drivers are not loaded in
that case (only amd framebuffer driver and userspace mesa llvmpipe).
Cold boot from OFF seems to be the most common case for this issue and
it happens about 50-75% of the time from there. I have to force power
the device off and try again in this case. I don't know how to get
proper bootlogs from the previous boot when this is the case since
/var/log only seems to contain logs from the current boot.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Apr 22 13:35:21 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 
00 [VGA controller])
   Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
InstallationDate: Installed on 2023-11-16 (159 days ago)
InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP05
dmi.board.vendor: Framework
dmi.board.version: A5
dmi.chassis.asset.tag: FRANDGCPA5342400SJ
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A5
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP05
dmi.product.version: A5
dmi.sys.vendor: Framework
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 amdgpu apport-bug freeze kubuntu noble ubuntu wayland-session
-- 
Frequent boot to black display
https://bugs.launchpad.net/bugs/2063143
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 2061986] Re: Mount CIFS fails with Permission denied

[Launchpad Bug Tracker]

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

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+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 2061986] Re: Mount CIFS fails with Permission denied

[Launchpad Bug Tracker]

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

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+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 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)

[Launchpad Bug Tracker]

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

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

Title:
  Keyboard does not work after waking up from suspend with 5.15.0-105
  (but works with 5.15.0-101)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear Ubuntu maintainers, I think I found a regression in linux
  5.15.0-105.

  In the past few days, my keyboard stopped working after waking up from
  suspend (sleep), so I couldn't unlock my laptop. Various workarounds
  found on the internet helped, but I wanted to investigate if it was a
  gdm issue, grub, or a hardware failure. I managed to narrow it down to
  the kernel, which is why I'm filing this bug report.

  AFAICT the only keys that work are the keyboard lights and the
  brightness knobs (in the Fn functions). I can confirm that 5.15.0-105
  has the issue, and I can consistently reproduce it with the following
  steps:

  1. boot fresh with 5.15.0-105
  2. login to my account
  3. choose suspend from the power menu
  4. wake up

  
  Following the same steps above with the last kernel available does not cause 
the issue (package version 5.15.0-101.111). I'll keep using that one for the 
time being.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-105-generic 5.15.0-105.115
  ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148
  Uname: Linux 5.15.0-105-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philsf 5465 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 02:58:26 2024
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc
  InstallationDate: Installed on 2018-06-07 (2145 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic 
root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-105-generic N/A
   linux-backports-modules-5.15.0-105-generic  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.29
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2023
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 0TXW78
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+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 2063228] [NEW] screen sometimes blinking

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
I notice this with Firefox because I use it a lot, I don't know if this happens 
with other software.
I'm under wayland (xwayland?)

Description:Ubuntu 24.04 LTS
Release:24.04

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 18:57:50 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
InstallationDate: Installed on 2024-04-07 (16 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
 Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 
4.2 Adapter
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP Pavilion Laptop 14-ce2xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2022
dmi.bios.release: 15.27
dmi.bios.vendor: Insyde
dmi.bios.version: F.27
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84BB
dmi.board.vendor: HP
dmi.board.version: 15.32
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 15.32
dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 14-ce2xxx
dmi.product.sku: 8KZ34EA#ABF
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble ubuntu wayland-session
-- 
screen sometimes blinking
https://bugs.launchpad.net/bugs/2063228
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 2063222] [NEW] Ghost "unknown display" since upgrading to 24.04 beta

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

X11
GNOME
NVIDIA 4080 with their driver

->

GNOME settings has a "ghost" display called "Unknown Display", its
resolution is 1024 x 768

I only have one display attached - a 4K 27" DELL plugged into the NVIDIA

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.171.04  Tue Mar 19 
20:30:00 UTC 2024
 GCC version:  gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4)
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 08:55:55 2024
DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus:
 nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed
 nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25]
 NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] 
[1462:5111]
InstallationDate: Installed on 2022-04-30 (724 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Micro-Star International Co., Ltd. MS-7D25
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet 
splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago)
dmi.bios.date: 11/13/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.F0
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D25
dmi.product.sku: Default string
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble ubuntu
-- 
Ghost "unknown display" since upgrading to 24.04 beta
https://bugs.launchpad.net/bugs/2063222
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-535 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 2063259] [NEW] sudden issues with monitors and sleep mode with 6.5.0-28-generic kernel

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have Kubuntu 22.04 and KDE 5.24.7 on my desktop. On 4/19/24 it
downloaded and installed kernel 6.5.0-28-generic. After restarting, I
suddenly had 2 issues:

1. I have 2 monitors. One of the monitors would not turn on while in the 
KDE desktop. However, while booting and also after getting into KDE and 
pressing CTRL-ALT-F2 to switch to the terminal the monitor worked, so I knew 
there wasn't a hardware problem with the monitor.
2. I could no longer put the computer into sleep mode. When I clicked on 
"sleep", it appeared to go into sleep mode (the working monitor would turn 
off), but the CPU fan never turned off and it was still "awake".

I was able to revert back to 6.5.0-27-generic from the grub menu and the
above issues went away, but they are concerning and I can't use
6.5.0-28-generic.

Start-Date: 2024-04-19  19:39:32
Commandline: /usr/bin/unattended-upgrade
Install: linux-modules-extra-6.5.0-28-generic:amd64 (6.5.0-28.29~22.04.1, 
automatic), linux-hwe-6.5-headers-6.5.0-28:amd64 (6.5.0-28.29~22.04.1, 
automatic), linux-modules-6.5.0-28-generic:amd64 (6.5.0-28.29~22.04.1, 
automatic), linux-image-6.5.0-28-generic:amd64 (6.5.0-28.29~22.04.1, 
automatic), linux-headers-6.5.0-28-generic:amd64 (6.5.0-28.29~22.04.1, 
automatic)
Upgrade: linux-image-generic-hwe-22.04:amd64 (6.5.0.27.28~22.04.1, 
6.5.0.28.29~22.04.1), linux-headers-generic-hwe-22.04:amd64 
(6.5.0.27.28~22.04.1, 6.5.0.28.29~22.04.1), linux-generic-hwe-22.04:amd64 
(6.5.0.27.28~22.04.1, 6.5.0.28.29~22.04.1)
End-Date: 2024-04-19  19:40:36


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

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

-- 
sudden issues with monitors and sleep mode with 6.5.0-28-generic kernel
https://bugs.launchpad.net/bugs/2063259
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 2062951] Re: Random flickering with i915 on Linux 6.8

[Launchpad Bug Tracker]

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

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

Title:
  Random flickering with i915 on Linux 6.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+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 2062950] [NEW] RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504

I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
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

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


** Tags: amd64 apport-bug flicker mantic multimonitor ubuntu wayland-session
-- 
RE: Flickering problems on external monitor with HDMI after installing Ubuntu 
23.10 
https://bugs.launchpad.net/bugs/2062950
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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 255.4-1ubuntu8

---
systemd (255.4-1ubuntu8) noble; urgency=medium

  * copy: ignore -EOPNOTSUPP from copy_file_range() (LP: #2058179)
File: 
debian/patches/lp2058179-copy-ignore-EOPNOTSUPP-from-copy_file_range.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fc81bb680f5d5c8c5995fcf6ed7f55f739dcd6a7

 -- Nick Rosbrook   Fri, 19 Apr 2024 10:24:36 -0400

** Changed in: systemd (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in systemd source package in Noble:
  Fix Released
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages (s390x)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 6.8.0-31.31

---
linux (6.8.0-31.31) noble; urgency=medium

  * noble/linux: 6.8.0-31.31 -proposed tracker (LP: #2062933)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)

 -- Andrea Righi   Fri, 19 Apr 2024 23:46:38
+0200

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

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

Title:
  [24.04 FEAT] Memory hotplug vmem pages (s390x)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  The current s390 specific memory hotplug backend allocates 'struct page' 
management structures for all standby memory regions, when those standby 
regions are detected at ipl time.
  The reason for this is, that setting standby online memory is supposed to 
succeed especially in memory constrained environments, since lack of free 
memory is likely the reason why additional memory is brought online.
  If in such cases 'struct pages' would have to be allocated before memory 
could be brought up, this would likely fail, and contradict the whole rationale 
of memory hotplug.

  However pre-allocating memory for 'struct pages' comes with the
  downside that for highly unbalanced ratios of online/standby memory a
  system might even fail to ipl, because there is not enough memory
  available for all possible struct pages which are required for standby
  memory.

  The idea is to improve the situation: when standby memory is brought
  online, the memory for struct pages (and maybe other management
  structures) required for this new memory area should be taken from the
  online memory, instead of pre-allocating them.

  This would solve the problems with unbalanced ratios as described
  above.

  Note: there are intentions to tell customers that they should always
  define the maximum size of standby memory for their LPAR activation
  profiles. This would allow for maximum flexibility for all LPARs
  during runtime, given that the amount of standby memory cannot be
  changed during runtime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051835/+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 2050019] Re: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 6.8.0-31.31

---
linux (6.8.0-31.31) noble; urgency=medium

  * noble/linux: 6.8.0-31.31 -proposed tracker (LP: #2062933)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)

 -- Andrea Righi   Fri, 19 Apr 2024 23:46:38
+0200

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

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

Title:
  [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with
  device scans

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

Bug description:
  The error recovery of a crypto request currently fails if a device is not 
available or the device is not completely setup and bound if the device has 
been discovered due to a bus scan.
  If, during request handling, a device is lost and a bus scan is triggered the 
DD must wait for the bus scan (including the device binding) to complete before 
giving up on reties.

  This item is important to support life guest relocation where the APQN
  sets on the source and target guests differ.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050019/+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 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 6.8.0-31.31

---
linux (6.8.0-31.31) noble; urgency=medium

  * noble/linux: 6.8.0-31.31 -proposed tracker (LP: #2062933)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)

 -- Andrea Righi   Fri, 19 Apr 2024 23:46:38
+0200

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/2056706

Title:
  System unstable, kernel ring buffer flooded with "BUG: Bad page state
  in process swapper/0"

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After upgrading a homelab 24.04 test machine from 6.6 to 6.8 kernel
  that was recently introduced, the test machine started flooding the
  terminal with following messages:

  [ 1877.712068] BUG: Bad page state in process swapper/0  pfn:58919

  The process name varies and appears to be whatever is currently doing
  something. I installed a fresh up to date copy to see if this could be
  replicated elsewhere and the outcome is the same. Both of the machines
  are VMs running under Xen with XCP-ng, although unsure if it's
  related.

  The issue produces a notable amount of syslog entries. If left
  running, the system will eventually go into a state where processes
  get stuck and do not react to systemd control, even when there's no
  notable load, no memory pressure nor is the disk space low.

  Booted back to 6.6 kernel the issue no longer happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-11-generic 6.8.0-11.11
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 11 00:31 seq
   crw-rw+ 1 root audio 116, 33 Mar 11 00:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Mar 11 00:36:24 2024
  InstallationDate: Installed on 2024-03-11 (0 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20240222)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 002: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_US.UTF-8
   LC_CTYPE=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=97002c6c-ab61-49d5-b937-891e4e8da514 ro
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2024
  dmi.bios.release: 4.13
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.13
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.13:bd01/31/2024:br4.13:svnXen:pnHVMdomU:pvr4.13:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.13
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+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 2063013] [NEW] Facing display issue (Display distortion and shows distorted lines) on booting after upgrading to new kernel.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Facing display issue (Display distortion and shows distorted lines) on
booting after upgrading to new kernel. It is working good till version
linux-image-5.15.0-84-generic (currently using). after this version able
to boot system only in recovery mode. (currently installed: linux-
image-5.15.0-105)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-terminal 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148
Uname: Linux 5.15.0-105-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 21 10:11:19 2024
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2021-10-10 (923 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy
-- 
Facing display issue (Display distortion and shows distorted lines) on booting 
after upgrading to new kernel.
https://bugs.launchpad.net/bugs/2063013
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 2062576] Re: Keyboard stops working after suspend 5.15.0-105

[Launchpad Bug Tracker]

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

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

Title:
  Keyboard stops working after suspend 5.15.0-105

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel updates on Apr 8 '24 started the issue of keyboard not working after 
sleep/suspend.
  Kernel 5.15.0-97 works, other kernels after 97 need grub modified to make 
them work.  
  Changed:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 
i8042.noaux=1"

  Only negative side effect of the i8042.dumbkbd entry is that the caps-
  lock light does not work. Otherwise on suspend and wake the keyboard
  works.

  I even tried the 6.6.0-26 kernel with same issue.

  version.log: Ubuntu 5.15.0-105.115-generic 5.15.148

  alan: ~ $ lsb_release -rd
  Description:  Linux Mint 21.3
  Release:  21.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062576/+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 2053019] Re: [nvidia] Second (external) monitor not active after screen lock in Xorg

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] Second (external) monitor not active after screen lock in
  Xorg

Status in mutter package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Expired

Bug description:
  After switching back to Xorg, I have encountered the issue with the
  second (external) monitor - after the screen is locked and I unlock
  it, the second monitor either shows a blank black screen or is not
  even active in Display settings. It's like the configuration is lost
  during lock/unclock process.

  I am using USB-C to HDMI cable with the second screen and Xorg as
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 12:53:24 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
  InstallationDate: Installed on 2024-01-12 (32 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash 
amd_pstate=guided vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2023
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN64WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.64
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  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/mutter/+bug/2053019/+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 2053019] Re: [nvidia] Second (external) monitor not active after screen lock in Xorg

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-535 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Second (external) monitor not active after screen lock in
  Xorg

Status in mutter package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Expired

Bug description:
  After switching back to Xorg, I have encountered the issue with the
  second (external) monitor - after the screen is locked and I unlock
  it, the second monitor either shows a blank black screen or is not
  even active in Display settings. It's like the configuration is lost
  during lock/unclock process.

  I am using USB-C to HDMI cable with the second screen and Xorg as
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 12:53:24 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
  InstallationDate: Installed on 2024-01-12 (32 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash 
amd_pstate=guided vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2023
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN64WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.64
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  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/mutter/+bug/2053019/+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 2054181] Re: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu

[Launchpad Bug Tracker]

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

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

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

Title:
  Monitor Not Detected when Connected to Belkin Docking Station via
  DisplayPort on Ubuntu

Status in linux-hwe-6.5 package in Ubuntu:
  Expired

Bug description:
  Dear Ubuntu Bug Tracking Team,

  I hope this message finds you well. I am writing to report an issue I
  have encountered while using Ubuntu.

  Issue Description:
  When connecting my BenQ monitor to a Belkin docking station via DisplayPort, 
Ubuntu fails to detect the monitor. Other monitor connected to same docking 
station via hdmi is working

  
  Thank you for your attention to this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 12:33:13 2024
  DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac]
  InstallationDate: Installed on 2020-06-01 (1355 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago)
  dmi.bios.date: 07/17/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2SET31W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390:
  dmi.product.family: ThinkPad X390
  dmi.product.name: 20SDCTO1WW
  dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390
  dmi.product.version: ThinkPad X390
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2054181/+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 1991130] Re: Add lrm autogenerated transitional independent of variants

[Launchpad Bug Tracker]

This bug was fixed in the package linux-restricted-modules - 6.8.0-28.28

---
linux-restricted-modules (6.8.0-28.28) noble; urgency=medium

  * Main version: 6.8.0-28.28

  * Packaging resync (LP: #1786013)
- [Packaging] debian/tracking-bug -- resync from main package

 -- Paolo Pisati   Tue, 16 Apr 2024 19:03:14
+0200

** Changed in: linux-restricted-modules (Ubuntu)
   Status: New => Fix Released

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

Title:
  Add lrm autogenerated transitional independent of variants

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux-restricted-modules-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux-restricted-modules source package in Focal:
  Invalid
Status in linux-restricted-modules-hwe-5.15 source package in Focal:
  Fix Released
Status in linux-restricted-modules-hwe-5.19 source package in Focal:
  Invalid
Status in linux-restricted-modules source package in Jammy:
  Invalid
Status in linux-restricted-modules-hwe-5.15 source package in Jammy:
  Invalid
Status in linux-restricted-modules-hwe-5.19 source package in Jammy:
  In Progress
Status in linux-restricted-modules source package in Lunar:
  Invalid
Status in linux-restricted-modules-hwe-5.15 source package in Lunar:
  Invalid
Status in linux-restricted-modules-hwe-5.19 source package in Lunar:
  Invalid
Status in linux-restricted-modules source package in Mantic:
  New
Status in linux-restricted-modules-hwe-5.15 source package in Mantic:
  Invalid
Status in linux-restricted-modules-hwe-5.19 source package in Mantic:
  Invalid

Bug description:
  [Impact]

  The kernel lrm packages have a mechanism to auto-generate transitional
  packages by adding a line to 'debian/package.config' in the following
  format

  transitional   

  Example:

  transitional 450-oem-20.04 450-generic amd64

  When being processed by 'debian/scripts/gen-rules.lrm' the
  autogenerated contents are added to 'debian/control.d/transitionals-
  local'. However, this file is not included in the final
  'debian/control' for packages which does not contain the default
  variant '--' (see debian/rules.in). This is intentional to prevent
  unwanted transitionals.

  However, there are some cases where we want to transition packages to
  kernels which are not the default variant in a series (e.g. hwe
  kernels).

  [Fix]

  The proposed fix is to add a new command "migrate", which does exactly
  what "transitional" does but adding the content to
  'debian/control.d/migrate-local' which would get added to the final
  'debian/control' independently of the source's variants.

  [Test Case]

  Add "migrate" entries to 'debian/package.config' and check whether
  they get added to 'debian/control' even for non default variant
  packages.

  [Where problems could occur]

  If not used correctly, unwanted transitionals could be generated
  causing issues to the archive. However, this is a new command and
  should not impact any of the previously set transitionals and it needs
  to be explicitly used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1991130/+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 2046315] Re: panel flickering after the i915.psr2 is enabled

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.8 - 6.8.0-1004.4

---
linux-oem-6.8 (6.8.0-1004.4) noble; urgency=medium

  * noble/linux-oem-6.8: 6.8.0-1004.4 -proposed tracker (LP: #2062020)

  * panel flickering after the i915.psr2 is enabled (LP: #2046315)
- drm/i915/alpm: Add ALPM register definitions
- drm/i915/psr: Add alpm_parameters struct
- drm/i915/alpm: Calculate ALPM Entry check
- drm/i915/alpm: Alpm aux wake configuration for lnl
- drm/i915/display: Make intel_dp_aux_fw_sync_len available for PSR code
- drm/i915/psr: Improve fast and IO wake lines calculation
- drm/i915/psr: Calculate IO wake and fast wake lines for DISPLAY_VER < 12
- drm/i915/display: Increase number of fast wake precharge pulses

  * Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update update.conf
- debian.oem/dkms-versions -- update from kernel-versions (main/d2024.04.04)

  * intel_rapl_common: Add support for ARL and LNL (LP: #2061953)
- powercap: intel_rapl: Add support for Lunar Lake-M paltform
- powercap: intel_rapl: Add support for Arrow Lake

  [ Ubuntu: 6.8.0-28.28 ]

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

  [ Ubuntu: 6.8.0-25.25 ]

  * noble/linux: 6.8.0-25.25 -proposed tracker (LP: #2061083)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)
  * Apply mitigations for the native BHI hardware vulnerabilty (LP: #2060909)
- x86/cpufeatures: Add new word for scattered features
- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
- x86/syscall: Don't force use of indirect calls for system calls
- x86/bhi: Add support for clearing branch history at syscall entry
- x86/bhi: Define SPEC_CTRL_BHI_DIS_S
- x86/bhi: Enumerate Branch History Injection (BHI) bug
- x86/bhi: Add BHI mitigation knob
- x86/bhi: Mitigate KVM by default
- KVM: x86: Add BHI_NO
- x86: set SPECTRE_BHI_ON as default
- [Config] enable spectre_bhi=auto by default
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/90]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/90]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/90]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/90]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/90]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/90]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/90]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/90]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/90]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/90]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/90]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/90]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/90]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/90]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/90]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/90]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/90]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/90]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/90]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/90]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/90]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
   

[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 6.8.0-28.28

---
linux (6.8.0-28.28) noble; urgency=medium

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)

  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

 -- Paolo Pisati   Tue, 16 Apr 2024 18:29:17
+0200

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

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

Title:
  [MTL] x86: Fix Cache info sysfs is not populated

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  The interface /sys/devices/system/cpu/cpuX/cache is broken (not populated) if
  CPUs have different numbers of subleaves in CPUID 4. This is the case of Intel
  Meteor Lake.

  [Fix]

  
https://lore.kernel.org/all/2023121519.12834-1-ricardo.neri-calde...@linux.intel.com/
  Reviewed, but probably will only land in v6.9.

  [Test Case]

  Check existence of cpu cache info:

$ ls /sys/devices/system/cpu/cpu0/cache/
index0 index1 index2 index3 uevent

  [Where problems could occur]

  This populates sysfs entries that should have been available, not
  something new or alters existing interface.

  [Other Info]

  While this is targets v6.8 for Intel LPMD (Low Power Model Daemon)'s
  use, only Noble and Unstable will be nominated for fix.

  == original bug report ==

  [Description]
    The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, 
not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute 
die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem 
happens because Linux assumes that all CPUs have the same number of subleaves.

  [Hardware Information]
    Architecture:
  Intel / AMD (x86_64)
    Platform(s):
  Meteor Lake
    Date HW is expected at Canonical:

    Component(s):
  x86

  [Software Information]
    Target Version:
  24.04
    Target Kernel:
  6.8
    Commit IDs:
  TBD
    External Links:
  
https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/

  [Business Justification]

  [Testing guidance]

  [External ID]
    LFE-6901

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2049793/+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 2059147] Re: New upstream relase 535.171.04

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.171.04-0ubuntu2

---
nvidia-graphics-drivers-535 (535.171.04-0ubuntu2) noble; urgency=medium

  * remove 
debian/dkms_nvidia/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch
  * remove debian/dkms_nvidia/patches/buildfix_kernel_6.8-gpl-pfn_valid.patch
  * remove 
debian/open-kernel/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch
  * remove debian/open-kernel/patches/buildfix_kernel_6.8-gpl-pfn_valid.patch

 -- Bartlomiej Zolnierkiewicz 
Wed, 27 Mar 2024 14:45:04 +0100

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.171.04

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2059147/+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 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 6.8.0-1006.6

---
linux-aws (6.8.0-1006.6) noble; urgency=medium

  * noble/linux-aws: 6.8.0-1006.6 -proposed tracker (LP: #2061868)

  * Rebase on 6.8.0-28.28

 -- Andrea Righi   Tue, 16 Apr 2024 19:26:16
+0200

** Changed in: linux-aws (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  aws: Backport latest ENA driver in upstream Linux to enable IRQ
  moderation

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux-aws source package in Mantic:
  Fix Released
Status in linux-aws source package in Noble:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard
  Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our
  latest generation instances with networking heavy workloads is up to a
  25% performance regression (i.e. NGINX in a load-balancing
  configuration).

  
  [Fix]

  
  The mainline Linux kernel will now support IRQ moderation by default for ENA 
in the 6.9 kernel release via this patch: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b

  [Test Plan]

  AWS tested

  [Where problems could occur]

  By enabling adaptive coalescing, the default interrupt behaviour will
  by changed to be more adaptive, which shows improvements on heavy
  network workloads, but my change the behaviour and performance on
  other network workloads differently.   Rather than handling the
  interrupts based off of a fixed amount of time elapsed, it will change
  to an adaptive based approach.   There should be no negative impact on
  light workloads, and a positive impact on heavy work loads.  If there
  is an impact though, this option can be disabled via the ethtool
  command.

  [Other Info]

  SF: 00380449

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+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 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oracle - 6.8.0-1004.4

---
linux-oracle (6.8.0-1004.4) noble; urgency=medium

  * noble/linux-oracle: 6.8.0-1004.4 -proposed tracker (LP: #2061873)

  * Rebase on Ubuntu-6.8.0-28.28

 -- Paolo Pisati   Tue, 16 Apr 2024 19:36:13
+0200

** Changed in: linux-oracle (Ubuntu Noble)
   Status: In Progress => Fix Released

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

Title:
  Provide an arm64 linux-oracle 64k kernel variant

Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle-6.5 package in Ubuntu:
  Invalid
Status in linux-oracle source package in Jammy:
  Invalid
Status in linux-oracle-6.5 source package in Jammy:
  Fix Released
Status in linux-oracle source package in Mantic:
  Fix Released
Status in linux-oracle-6.5 source package in Mantic:
  Invalid
Status in linux-oracle source package in Noble:
  Fix Released
Status in linux-oracle-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]

  * Oracle requested 64k page size flavour.

  [Fix]

  * Add flavour and configs for 64k flavour

  [Test Case]

  * Compile tested
  * Boot tested

  [Where things could go wrong]

  * Low chance of regression. Isolated logic fix.

  [Other Info]

  * SF #00377602

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+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 2060909] Re: Apply mitigations for the native BHI hardware vulnerabilty

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 6.8.0-28.28

---
linux (6.8.0-28.28) noble; urgency=medium

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)

  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

 -- Paolo Pisati   Tue, 16 Apr 2024 18:29:17
+0200

** Changed in: linux (Ubuntu Noble)
   Status: Fix Committed => 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/2060909

Title:
  Apply mitigations for the native BHI hardware vulnerabilty

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

Bug description:
  [Impact]

  Branch History Injection (BHI) attacks may allow a malicious
  application to influence indirect branch prediction in kernel by
  poisoning the branch history. eIBRS isolates indirect branch targets
  in ring0.

  The BHB can still influence the choice of indirect branch predictor
  entry, and although branch predictor entries are isolated between
  modes when eIBRS is enabled, the BHB itself is not isolated between
  modes.

  Previously the only known real-world BHB attack vector was via
  unprivileged eBPF. Further research has found attacks that don't
  require unprivileged eBPF.

  See also:
  https://www.phoronix.com/news/Linux-BHI-Branch-History-Inject

  [Test case]

  https://www.vusec.net/projects/native-bhi/

  [Fix]

  Backport from upstream the merge that introduces spectre_bhi= boot
  option to control BHI mitigation:

   2bb69f5fc721 ("Merge tag 'nativebhi' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
   ed2e8d49b54d ("KVM: x86: Add BHI_NO")
   95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
   ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
   be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
   0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
   7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall 
entry")
   1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system 
calls")
   0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs 
file")

  Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
  hardware control if it's available on the system CPUs, otherwise a
  proper software sequence will be executed at VMexit.

  NOTE: we may get these changes via stable update in 6.8, when that
  happens we can drop this backport and apply the patch set like any
  other regular stable update.

  [Regression potential]

  We may experience performance regressions with this new mitigation
  enabled, especially in VMs and CPUs that don't have the BHI hardware
  support capability (due to the extra software sequence executed at
  VMexit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+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 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 6.8.0-28.28

---
linux (6.8.0-28.28) noble; urgency=medium

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)

  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

 -- Paolo Pisati   Tue, 16 Apr 2024 18:29:17
+0200

** Changed in: linux (Ubuntu Noble)
   Status: New => 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/2061851

Title:
  linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new
  apparmor profiles/features

Status in chrony package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-ibm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New
Status in chrony source package in Noble:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-aws source package in Noble:
  New
Status in linux-azure source package in Noble:
  New
Status in linux-gcp source package in Noble:
  New
Status in linux-ibm source package in Noble:
  New
Status in linux-oracle source package in Noble:
  New
Status in snapd source package in Noble:
  New

Bug description:
  * Canonical Public Cloud discovered that `chronyc -c sources` now fails with 
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in 
linux-azure and linux-gcp kernels (6.8.0-1005.5)
  * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in 
no regression and `chronyc -c sources` returns as expected
  * Disabling the apparmor profile for `chronyd` only results in no regression 
and `chronyc -c sources` returns as expected
  * There are zero entries in dmesg when this occurs
  * There are zero entries in dmesg when this occurs if the  apparmor profile 
for `chronyd` is placed in complain mode instead of enforce mode
  * We changed the time server from the internal GCP metadata.google.internal 
to the ubuntu time server ntp.ubuntu.com with no change in behaviour

  
  We also noted issues with DNS resolution in snaps like `google-cloud-cli` in 
GCE images. 

  * Disabling apparmor completely for snaps too (`sudo systemctl stop
  snapd.apparmor`) results in no regression and calling the snaps
  returns as expected.

  
  The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and 
the -proposed `6.8.0-25.25` generic kernel. 

  This is a release blocker for Noble release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2061953] Re: intel_rapl_common: Add support for ARL and LNL

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.8 - 6.8.0-1004.4

---
linux-oem-6.8 (6.8.0-1004.4) noble; urgency=medium

  * noble/linux-oem-6.8: 6.8.0-1004.4 -proposed tracker (LP: #2062020)

  * panel flickering after the i915.psr2 is enabled (LP: #2046315)
- drm/i915/alpm: Add ALPM register definitions
- drm/i915/psr: Add alpm_parameters struct
- drm/i915/alpm: Calculate ALPM Entry check
- drm/i915/alpm: Alpm aux wake configuration for lnl
- drm/i915/display: Make intel_dp_aux_fw_sync_len available for PSR code
- drm/i915/psr: Improve fast and IO wake lines calculation
- drm/i915/psr: Calculate IO wake and fast wake lines for DISPLAY_VER < 12
- drm/i915/display: Increase number of fast wake precharge pulses

  * Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update update.conf
- debian.oem/dkms-versions -- update from kernel-versions (main/d2024.04.04)

  * intel_rapl_common: Add support for ARL and LNL (LP: #2061953)
- powercap: intel_rapl: Add support for Lunar Lake-M paltform
- powercap: intel_rapl: Add support for Arrow Lake

  [ Ubuntu: 6.8.0-28.28 ]

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

  [ Ubuntu: 6.8.0-25.25 ]

  * noble/linux: 6.8.0-25.25 -proposed tracker (LP: #2061083)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)
  * Apply mitigations for the native BHI hardware vulnerabilty (LP: #2060909)
- x86/cpufeatures: Add new word for scattered features
- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
- x86/syscall: Don't force use of indirect calls for system calls
- x86/bhi: Add support for clearing branch history at syscall entry
- x86/bhi: Define SPEC_CTRL_BHI_DIS_S
- x86/bhi: Enumerate Branch History Injection (BHI) bug
- x86/bhi: Add BHI mitigation knob
- x86/bhi: Mitigate KVM by default
- KVM: x86: Add BHI_NO
- x86: set SPECTRE_BHI_ON as default
- [Config] enable spectre_bhi=auto by default
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/90]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/90]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/90]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/90]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/90]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/90]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/90]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/90]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/90]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/90]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/90]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/90]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/90]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/90]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/90]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/90]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/90]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/90]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/90]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/90]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/90]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
   

[Kernel-packages] [Bug 2062545] Re: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

[Launchpad Bug Tracker]

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

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

Title:
  Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
  Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
  This combination gives still a not working keyboard after booting.

  Today the system has upgraded the kernel to Linux version
  6.5.0-1020-oem this should solves the keyboard problem introduced in
  kernel 6.5.0-1019-oem and already reported in:

  - https://bugs.launchpad.net/bugs/2060727
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

  This bug fix does not work, I still have no internal keyboard.

  For the moment I am using kernel 6.5.0-1018-oem which workes fine.

  Who can/will help?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062545/+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 2061897] Re: Enable Milk-V Mars board

[Launchpad Bug Tracker]

This bug was fixed in the package linux-riscv - 6.8.0-28.28.1

---
linux-riscv (6.8.0-28.28.1) noble; urgency=medium

  * noble/linux-riscv: 6.8.0-28.28.1 -proposed tracker (LP: #2061974)

  * Packaging resync (LP: #1786013)
- [Packaging] drop getabis data
- [Packaging] debian.riscv/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)

  * Enable Milk-V Mars board (LP: #2061897)
- SAUCE: riscv: dts: starfive: add 'cpus' label to jh7110 and jh7100 soc 
dtsi
- SAUCE: dt-bindings: riscv: starfive: add Milkv Mars board
- SAUCE: riscv: dts: starfive: visionfive 2: update sound and codec dt node
  name
- SAUCE: riscv: dts: starfive: visionfive 2: use cpus label for timebase 
freq
- SAUCE: riscv: dts: starfive: introduce a common board dtsi for jh7110 
based
  boards
- SAUCE: riscv: dts: starfive: add Milkv Mars board device tree

  * Enable StarFive VisionFive 2 board (LP: #2013232)
- SAUCE: riscv: dts: starfive: visionfive 2: Remove non-existing TDM 
hardware
- SAUCE: riscv: dts: starfive: visionfive 2: Remove non-existing I2S 
hardware

  [ Ubuntu: 6.8.0-28.28 ]

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

  [ Ubuntu: 6.8.0-25.25 ]

  * noble/linux: 6.8.0-25.25 -proposed tracker (LP: #2061083)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)
  * Apply mitigations for the native BHI hardware vulnerabilty (LP: #2060909)
- x86/cpufeatures: Add new word for scattered features
- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
- x86/syscall: Don't force use of indirect calls for system calls
- x86/bhi: Add support for clearing branch history at syscall entry
- x86/bhi: Define SPEC_CTRL_BHI_DIS_S
- x86/bhi: Enumerate Branch History Injection (BHI) bug
- x86/bhi: Add BHI mitigation knob
- x86/bhi: Mitigate KVM by default
- KVM: x86: Add BHI_NO
- x86: set SPECTRE_BHI_ON as default
- [Config] enable spectre_bhi=auto by default
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/90]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/90]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/90]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/90]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/90]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/90]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/90]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/90]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/90]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/90]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/90]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/90]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/90]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/90]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/90]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/90]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/90]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/90]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/90]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/90]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/90]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
- SAUCE: 

[Kernel-packages] [Bug 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0

[Launchpad Bug Tracker]

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

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

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

Title:
  GDM3 autologin might be racy on GCP resulting in inconsistent state of
  the wayland setup of seat0

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed

Bug description:
  This might not be a bug really about linux-gcp, but this is following
  the work on bug 2039732 and so far I could not reproduce that locally.

  Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
  attached thus relying on vkms. I have reproduced locally a similar
  setup but on a KVM host.

  We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
   - create a new task_XXX user
   - make it autologin in gdm3 config
   - generic-worker has code to probe for existence of the GNOME Wayland 
session before launching the task

  We relied on wl-clipboard package installed for verifying the status
  of wayland

  On top of that setup, here is the issue.

  We issue a TC task with payload:
  > export WAYLAND_DISPLAY=wayland-0
  > export XDG_RUNTIME_DIR=/run/user/$(id -u)
  > wl-paste -l -p

  We expect that payload to report "No selection", but on GCP instances
  we mostly always end up with "This seat has no keyboard". There were
  also cases were the session would not be Wayland at all but rather
  X11. I think this suggests something around the availability of
  /dev/dri/card0, but forcing the gdm3 service to wait for its
  availability and adding extra waiting time after card0 is present
  would still not get us somewhere.

  We enabled gdm3 as well as mutter debugging but never found anything
  that would be a good lead on why it was not yet ready.

  At some point, the seat0 session of our user was shown as inactive and
  the active one was tied to gdm so we suspected this was the reason,
  but both forcing the session to be active and terminating the gdm
  session would still not unblock us.

  We also suspected the desktop to be locking itself so we disabled locking 
with the following, but iit did not help much:
  > cat > /etc/dconf/profile/user << EOF
  > user-db:user
  > system-db:local
  > EOF
  > 
  > mkdir /etc/dconf/db/local.d/
  > # dconf user settings
  > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF
  > # /org/gnome/desktop/session/idle-delay
  > [org/gnome/desktop/session]
  > idle-delay=uint32 0
  > # /org/gnome/desktop/lockdown/disable-lock-screen
  > [org/gnome/desktop/lockdown]
  > disable-lock-screen=true
  > EOF
  > 
  > sudo dconf update

  
  In the end, the only viable and reliable (verified over hundreds of runs now) 
fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup:
  > mkdir -p /etc/systemd/system/gdm.service.d/
  > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF
  > [Unit]
  > Description=Extra 30s wait
  > [Service]
  > ExecStartPre=/bin/sleep 30
  > EOF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2062534/+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 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0

[Launchpad Bug Tracker]

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

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

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

Title:
  GDM3 autologin might be racy on GCP resulting in inconsistent state of
  the wayland setup of seat0

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed

Bug description:
  This might not be a bug really about linux-gcp, but this is following
  the work on bug 2039732 and so far I could not reproduce that locally.

  Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
  attached thus relying on vkms. I have reproduced locally a similar
  setup but on a KVM host.

  We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
   - create a new task_XXX user
   - make it autologin in gdm3 config
   - generic-worker has code to probe for existence of the GNOME Wayland 
session before launching the task

  We relied on wl-clipboard package installed for verifying the status
  of wayland

  On top of that setup, here is the issue.

  We issue a TC task with payload:
  > export WAYLAND_DISPLAY=wayland-0
  > export XDG_RUNTIME_DIR=/run/user/$(id -u)
  > wl-paste -l -p

  We expect that payload to report "No selection", but on GCP instances
  we mostly always end up with "This seat has no keyboard". There were
  also cases were the session would not be Wayland at all but rather
  X11. I think this suggests something around the availability of
  /dev/dri/card0, but forcing the gdm3 service to wait for its
  availability and adding extra waiting time after card0 is present
  would still not get us somewhere.

  We enabled gdm3 as well as mutter debugging but never found anything
  that would be a good lead on why it was not yet ready.

  At some point, the seat0 session of our user was shown as inactive and
  the active one was tied to gdm so we suspected this was the reason,
  but both forcing the session to be active and terminating the gdm
  session would still not unblock us.

  We also suspected the desktop to be locking itself so we disabled locking 
with the following, but iit did not help much:
  > cat > /etc/dconf/profile/user << EOF
  > user-db:user
  > system-db:local
  > EOF
  > 
  > mkdir /etc/dconf/db/local.d/
  > # dconf user settings
  > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF
  > # /org/gnome/desktop/session/idle-delay
  > [org/gnome/desktop/session]
  > idle-delay=uint32 0
  > # /org/gnome/desktop/lockdown/disable-lock-screen
  > [org/gnome/desktop/lockdown]
  > disable-lock-screen=true
  > EOF
  > 
  > sudo dconf update

  
  In the end, the only viable and reliable (verified over hundreds of runs now) 
fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup:
  > mkdir -p /etc/systemd/system/gdm.service.d/
  > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF
  > [Unit]
  > Description=Extra 30s wait
  > [Service]
  > ExecStartPre=/bin/sleep 30
  > EOF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2062534/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 2.2.2-0ubuntu9

---
zfs-linux (2.2.2-0ubuntu9) noble; urgency=medium

  * 
debian/patches/0007-Linux-6.8-compat-use-splice_copy_file_range-for-fallback.patch
- Linux 6.8 support(LP: #2058179)
  * debian/control:
- add libtirpc-dev as build dependency

 -- John Cabaj   Thu, 18 Apr 2024 23:00:06
-0500

** Changed in: zfs-linux (Ubuntu Noble)
   Status: In Progress => Fix Released

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in systemd source package in Noble:
  Fix Committed
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2062556] [NEW] [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---

Hugepages memory is not getting released even after destroying the guest
 
Machine Type = P10 Denali LPAR 
 
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr  4 22:47:57 UTC 
2024 ppc64le ppc64le ppc64le GNU/Linux

 
---Steps to Reproduce---
1. Create a guest which is backed by hugepages.
2. Destroy the guest
3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is 
still getting held.
 
 
HugePages_Total:   20480
HugePages_Free:20419
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
Hugetlb:41943040 kB
DirectMap4k:   0 kB
DirectMap64k:52428800 kB
DirectMap2M:   0 kB
DirectMap1G:   0 kB
root@ubuntu2404lp3:~# virsh list --all
 Id   Name   State
---
 -ramlp2g1   shut off
 -ramlp2g2   shut off
 -ramlp2g3   shut off
 -ramlp3g3   shut off

root@ubuntu2404lp3:~# free -h
   totalusedfree  shared  buff/cache   available
Mem:48Gi43Gi   4.6Gi   2.6Mi   277Mi   4.6Gi
Swap:  8.0Gi   243Mi   7.8Gi
root@ubuntu2404lp3:~#


This is an issue created by commit 1b151e2435fc ("block: Remove special-casing 
of compound pages") that moved the direct-io hugetlb handling from compound 
pages to folios.

Following commit has been proposed and merged into 6.9-rc1 which fixes this 
issue.
38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for 
unaligned buffers in __bio_release_pages()")

So the same needs to be backported to the Ubuntu24.04 kernel as well.

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


** Tags: architecture-ppc64le bugnameltc-206058 severity-high 
targetmilestone-inin2404
-- 
[Ubuntu-24.04] Hugepage memory is not getting released even after destroying 
the guest!
https://bugs.launchpad.net/bugs/2062556
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 2062426] [NEW] simple-framebuffer: swiotlb buffer is full

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[   29.548909] [ cut here ]
[   29.548912] simple-framebuffer simple-framebuffer.0: 
drm_WARN_ON(map->is_iomem)
[   29.548924] WARNING: CPU: 7 PID: 2700 at 
drivers/gpu/drm/drm_gem_shmem_helper.c:319 drm_gem_shmem_vmap+0x1a5/0x1e0
[   29.548932] Modules linked in: nf_tables libcrc32c snd_seq_dummy snd_hrtimer 
ccm qrtr binfmt_misc nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) 
nls_iso8859_1 nvidia(POE) intel_rapl_msr intel_rapl_common snd_hda_codec_hdmi 
snd_hda_intel rtl8192ee snd_intel_dspcfg snd_intel_sdw_acpi btcoexist 
snd_hda_codec snd_usb_audio rtl_pci snd_hda_core snd_usbmidi_lib rtlwifi 
snd_hwdep snd_ump snd_seq_midi edac_mce_amd snd_seq_midi_event snd_rawmidi 
mac80211 mc kvm_amd snd_seq snd_pcm snd_seq_device kvm joydev snd_timer 
input_leds cfg80211 snd irqbypass soundcore libarc4 rapl video wmi_bmof ccp 
k10temp i2c_piix4 gpio_amdpt mac_hid msr parport_pc ppdev lp parport efi_pstore 
nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid 
crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic r8169 
ghash_clmulni_intel sha256_ssse3 sha1_ssse3 ahci xhci_pci realtek libahci 
xhci_pci_renesas wmi aesni_intel crypto_simd cryptd
[   29.549044] CPU: 7 PID: 2700 Comm: Xorg Tainted: P   OE  
6.8.0-22-generic #22-Ubuntu
[   29.549047] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./A320M-DVS R4.0, BIOS P4.00 07/16/2020
[   29.549049] RIP: 0010:drm_gem_shmem_vmap+0x1a5/0x1e0
[   29.549054] Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 44 a6 ec ff 48 c7 
c1 73 62 82 9f 4c 89 ea 48 c7 c7 b2 3d 82 9f 48 89 c6 e8 4b 3f 44 ff <0f> 0b 48 
8b 83 f0 00 00 00 4c 89 e6 48 8b 38 e8 f7 48 f5 ff b8 fb
[   29.549056] RSP: 0018:b6da8304ba08 EFLAGS: 00010246
[   29.549060] RAX:  RBX: a0778c558a00 RCX: 
[   29.549062] RDX:  RSI:  RDI: 
[   29.549063] RBP: b6da8304ba28 R08:  R09: 
[   29.549065] R10:  R11:  R12: a0778cdaa6c8
[   29.549067] R13: a07781d2efc0 R14: a0778cdaa6c8 R15: a0778cdaa6c8
[   29.549069] FS:  7e8343530ac0() GS:a07a8e58() 
knlGS:
[   29.549071] CS:  0010 DS:  ES:  CR0: 80050033
[   29.549073] CR2: 567a82464778 CR3: 00014044e000 CR4: 003506f0
[   29.549075] Call Trace:
[   29.549078]  
[   29.549082]  ? show_regs+0x6d/0x80
[   29.549087]  ? __warn+0x89/0x160
[   29.549092]  ? drm_gem_shmem_vmap+0x1a5/0x1e0
[   29.549096]  ? report_bug+0x17e/0x1b0
[   29.549103]  ? handle_bug+0x51/0xa0
[   29.549108]  ? exc_invalid_op+0x18/0x80
[   29.549112]  ? asm_exc_invalid_op+0x1b/0x20
[   29.549121]  ? drm_gem_shmem_vmap+0x1a5/0x1e0
[   29.549125]  ? drm_gem_shmem_vmap+0x1a5/0x1e0
[   29.549130]  drm_gem_shmem_object_vmap+0x9/0x20
[   29.549133]  drm_gem_vmap+0x26/0x80
[   29.549138]  drm_gem_vmap_unlocked+0x2b/0x50
[   29.549142]  drm_gem_fb_vmap+0x40/0x150
[   29.549147]  drm_gem_begin_shadow_fb_access+0x25/0x40
[   29.549150]  drm_atomic_helper_prepare_planes.part.0+0x142/0x1e0
[   29.549155]  drm_atomic_helper_prepare_planes+0x5d/0x70
[   29.549160]  drm_atomic_helper_commit+0x84/0x160
[   29.549164]  drm_atomic_commit+0x99/0xd0
[   29.549167]  ? __pfx___drm_printfn_info+0x10/0x10
[   29.549173]  drm_atomic_helper_set_config+0x82/0xd0
[   29.549176]  drm_mode_setcrtc+0x535/0x8b0
[   29.549187]  ? __pfx_drm_mode_setcrtc+0x10/0x10
[   29.549191]  drm_ioctl_kernel+0xbc/0x120
[   29.549194]  ? srso_return_thunk+0x5/0x5f
[   29.549200]  drm_ioctl+0x2d4/0x550
[   29.549204]  ? __pfx_drm_mode_setcrtc+0x10/0x10
[   29.549214]  __x64_sys_ioctl+0xa3/0xf0
[   29.549220]  do_syscall_64+0x85/0x180
[   29.549223]  ? srso_return_thunk+0x5/0x5f
[   29.549226]  ? count_memcg_events.constprop.0+0x2a/0x50
[   29.549231]  ? srso_return_thunk+0x5/0x5f
[   29.549234]  ? handle_mm_fault+0xad/0x380
[   29.549238]  ? srso_return_thunk+0x5/0x5f
[   29.549241]  ? do_user_addr_fault+0x338/0x6b0
[   29.549245]  ? srso_return_thunk+0x5/0x5f
[   29.549248]  ? irqentry_exit_to_user_mode+0x7b/0x260
[   29.549252]  ? srso_return_thunk+0x5/0x5f
[   29.549255]  ? irqentry_exit+0x43/0x50
[   29.549258]  ? srso_return_thunk+0x5/0x5f
[   29.549261]  ? exc_page_fault+0x94/0x1b0
[   29.549265]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[   29.549269] RIP: 0033:0x7e8343924ded
[   29.549283] Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 
10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 
00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
[   29.549285] RSP: 002b:7ffeea092ae0 EFLAGS: 0246 ORIG_RAX: 
0010
[   29.549288] RAX: ffda RBX: 567a826da2f0 RCX: 7e8343924ded
[   29.549290] RDX: 7ffeea092b70 RSI: c06864a2 RDI: 0013
[   29.549292] RBP: 7ffeea092b30 R08: