[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

2024-03-23 Thread Launchpad Bug Tracker
[Expired for linux-nvidia (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

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

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

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


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


[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

2024-03-23 Thread 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 linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2033418

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

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

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

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


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


[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

2024-03-23 Thread 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 linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2033418

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

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

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

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


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


[Kernel-packages] [Bug 2050954] Re: consistently fails to resume from suspend

2024-03-23 Thread 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/2050954

Title:
  consistently fails to resume from suspend

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

Bug description:
  consistently fails to resume from suspend

  using integrated intel gpu no nvidia

  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: Tue Jan 23 08:34:38 2024
  DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
  InstallationDate: Installed on 2022-04-28 (634 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. XPS 8940
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 2.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0427JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
  dmi.product.family: XPS
  dmi.product.name: XPS 8940
  dmi.product.sku: 09C5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  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.1
  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.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-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/2050954/+subscriptions


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/6.5.0.27.28.18)

2024-03-23 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta-lowlatency (6.5.0.27.28.18) 
for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

linux-lowlatency/6.5.0-26.26.1 (amd64, arm64)
lxc/1:5.0.1-0ubuntu8~23.10.1 (amd64)
systemd/253.5-1ubuntu6.1 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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


[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

2024-03-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: procps (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/2057792

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in Ubuntu:
  Confirmed
Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

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


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


[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

2024-03-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gamemode (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/2057792

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in Ubuntu:
  Confirmed
Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

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


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


[Kernel-packages] [Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update

2024-03-23 Thread Andrea Agnolin
** Summary changed:

- vp9 hw decode broke on modern AMD apus, needs amdgpu update
+ vp9 hw decode broken on modern AMD apus, needs amdgpu update

** Description changed:

- Current version of amdgpu in linux-firmware shipped with ubuntu 22.04
- (jammy) and ubuntu 23.10 (mantic) create various problems when decoding
- VP9 content with the iGPU on modern AMD mobile processor (rembrant and
- phoenix, i.e. 6xxxU/H, 7x40U/H and 7735U/H processor).
+ Current version of amdgpu binaries in linux-firmware shipped with ubuntu
+ 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when
+ decoding VP9 content with the iGPU on modern AMD mobile processor
+ (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7735U/H processor).
  
  The issue has been reported and solved upstream:
  
  https://gitlab.com/kernel-firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807
  
  Solution dates to the end of February: https://gitlab.com/kernel-
  firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807
  
  Ubuntu 24.04 already ships the updated binaries and should not be
  affected.
  
  Steps to reproduce:
  * on an affected system play a VP9 video with hardware decoding
  
  Additional links:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
  * https://bugzilla.redhat.com/show_bug.cgi?id=2267714
  * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9
  
  Workaround:
  * download the amdgpu folder from upstream linux-firmware repos
  * compress each file with zstd
  * copy into /lib/firmware/amdgpu
  * regenerate the initrd
  
  I'm currently running ubuntu 23.10 (mantic) with binaries from upstream
  and the issue is solved.

** Description changed:

  Current version of amdgpu binaries in linux-firmware shipped with ubuntu
  22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when
  decoding VP9 content with the iGPU on modern AMD mobile processor
- (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7735U/H processor).
+ (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).
  
  The issue has been reported and solved upstream:
  
  https://gitlab.com/kernel-firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807
  
  Solution dates to the end of February: https://gitlab.com/kernel-
  firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807
  
  Ubuntu 24.04 already ships the updated binaries and should not be
  affected.
  
  Steps to reproduce:
  * on an affected system play a VP9 video with hardware decoding
  
  Additional links:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
  * https://bugzilla.redhat.com/show_bug.cgi?id=2267714
  * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9
  
  Workaround:
  * download the amdgpu folder from upstream linux-firmware repos
  * compress each file with zstd
  * copy into /lib/firmware/amdgpu
  * regenerate the initrd
  
  I'm currently running ubuntu 23.10 (mantic) with binaries from upstream
  and the issue is solved.

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

Title:
  vp9 hw decode broken on modern AMD apus, needs amdgpu update

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Current version of amdgpu binaries in linux-firmware shipped with
  ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems
  when decoding VP9 content with the iGPU on modern AMD mobile processor
  (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).

  The issue has been reported and solved upstream:

  https://gitlab.com/kernel-firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807

  Solution dates to the end of February: https://gitlab.com/kernel-
  firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807

  Ubuntu 24.04 already ships the updated binaries and should not be
  affected.

  Steps to reproduce:
  * on an affected system play a VP9 video with hardware decoding

  Additional links:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
  * https://bugzilla.redhat.com/show_bug.cgi?id=2267714
  * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9

  Workaround:
  * download the amdgpu folder from upstream linux-firmware repos
  * compress each file with zstd
  * copy into /lib/firmware/amdgpu
  * regenerate the initrd

  I'm currently running ubuntu 23.10 (mantic) with binaries from
  upstream and the issue is solved.

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


-- 
Mailing list: 

[Kernel-packages] [Bug 2058830] [NEW] vp9 hw decode broken on modern AMD apus, needs amdgpu update

2024-03-23 Thread Andrea Agnolin
Public bug reported:

Current version of amdgpu binaries in linux-firmware shipped with ubuntu
22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when
decoding VP9 content with the iGPU on modern AMD mobile processor
(rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).

The issue has been reported and solved upstream:

https://gitlab.com/kernel-firmware/linux-
firmware/-/commit/977332782302476e1c863b09b840f463d0378807

Solution dates to the end of February: https://gitlab.com/kernel-
firmware/linux-
firmware/-/commit/977332782302476e1c863b09b840f463d0378807

Ubuntu 24.04 already ships the updated binaries and should not be
affected.

Steps to reproduce:
* on an affected system play a VP9 video with hardware decoding

Additional links:
* 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
* https://bugzilla.redhat.com/show_bug.cgi?id=2267714
* https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9

Workaround:
* download the amdgpu folder from upstream linux-firmware repos
* compress each file with zstd
* copy into /lib/firmware/amdgpu
* regenerate the initrd

I'm currently running ubuntu 23.10 (mantic) with binaries from upstream
and the issue is solved.

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

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

Title:
  vp9 hw decode broken on modern AMD apus, needs amdgpu update

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Current version of amdgpu binaries in linux-firmware shipped with
  ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems
  when decoding VP9 content with the iGPU on modern AMD mobile processor
  (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).

  The issue has been reported and solved upstream:

  https://gitlab.com/kernel-firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807

  Solution dates to the end of February: https://gitlab.com/kernel-
  firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807

  Ubuntu 24.04 already ships the updated binaries and should not be
  affected.

  Steps to reproduce:
  * on an affected system play a VP9 video with hardware decoding

  Additional links:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
  * https://bugzilla.redhat.com/show_bug.cgi?id=2267714
  * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9

  Workaround:
  * download the amdgpu folder from upstream linux-firmware repos
  * compress each file with zstd
  * copy into /lib/firmware/amdgpu
  * regenerate the initrd

  I'm currently running ubuntu 23.10 (mantic) with binaries from
  upstream and the issue is solved.

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


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


[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

2024-03-23 Thread Julian Andres Klode
Subscribing Canonical desktop team to get their input.

Basically the ask is to ship this file:

https://src.fedoraproject.org/rpms/systemd/blob/f39/f/10-map-count.conf

I believe if we do it should be shipped in procps; or possibly, gamemode
should set that option?

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

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

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

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in Ubuntu:
  Confirmed
Status in gamemode package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in procps package in Ubuntu:
  New

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

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


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


[Kernel-packages] [Bug 2058824] [NEW] nvidia-driver-545 (and version 550) randomly hangs with compositing manager on VT change

2024-03-23 Thread Mikko Rantalainen
Public bug reported:

This issue doesn't happen with Nnvidia version 525 or 535 but it happens
with 545 and 550.

Steps to reproduce:

- Run window manager or desktop environment without compositor manager.
For example XFCE with Settings – Window Manager Tweaks – Compositor and
disable Enable display compositing. (The problem is visible with this
compositor, too, but getting out of hang with this one is harder.)

- The problem seems to be some kind of race condition because in "only"
happens about 70% of the time for me. I'm using package "linux-tools-
lowlatency-hwe-22.04" to get kernel with PREEMPT_DYNAMIC which may
trigger the race condition easier.

- Run picom as follows to make sure it has no config of any kind that
might avoid the problem:

picom --config /dev/null --show-all-xerrors --log-level=TRACE &
sleep 20; killall picom

  Note that this will emit a lot of log messages and picom will be
killed after 20 seconds (resulting in no compositor X session which
should be usable if not pretty).

- Switch to different virtual terminals with CTRL+ALT+F1, CTRL+ALT+F2,
..., CTRL+ALT+F7 and wait for display to refresh on each terminal.

- Assuming your initial virtual terminal was VT 7 as usual for GUI
desktop, you should now see fully black screen with your usual mouse
cursor only. Wait for the sleep timer above (20 seconds) to go off and
kill picom to restore your screen. If you had compositing enabled in
XFCE Window manager, you would be seeing the same issue but getting out
of this issue is much harder because XFCE window manager implements the
compositing internally and having compositing hang you would have to
kill your window manager to get rid of it!

I'm assuming this also happens with other software, too, that simply
happens to trigger the racy codepath during VT switch but the above is
the best way to reproduce the issue at will. The problem happens pretty
often rapidly changing to VT 1 and back to VT 7, too. It may be faster
way to reproduce the problem.

When picom hangs, the last line it outputs to stderr is as follows:

[ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render start, frame
416

Normally this should be followed by

[ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render end

on the same millisecond or one later but when NVidia driver hangs on VT
switch, this never happens.

As I wrote above, this bug doesn't occur with Nvidia driver version 535
so the bug has been introduced between version 535 and 545. I cannot
debug this further because I don't have the source code.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-545 (not installed)
ProcVersionSignature: Ubuntu 6.5.0-26.26.1~22.04.1-lowlatency 6.5.13
Uname: Linux 6.5.0-26-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat Mar 23 22:08:21 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1904 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: nvidia-graphics-drivers-545
UpgradeStatus: Upgraded to jammy on 2023-08-11 (225 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158

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


** Tags: amd64 apport-bug jammy

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

Title:
  nvidia-driver-545 (and version 550) randomly hangs with compositing
  manager on VT change

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

Bug description:
  This issue doesn't happen with Nnvidia version 525 or 535 but it
  happens with 545 and 550.

  Steps to reproduce:

  - Run window manager or desktop environment without compositor
  manager. For example XFCE with Settings – Window Manager Tweaks –
  Compositor and disable Enable display compositing. (The problem is
  visible with this compositor, too, but getting out of hang with this
  one is harder.)

  - The problem seems to be some kind of race condition because in
  "only" happens about 70% of the time for me. I'm using package "linux-
  tools-lowlatency-hwe-22.04" to get kernel with PREEMPT_DYNAMIC which
  may trigger the race condition easier.

  - Run picom as follows to make sure it has no config of any kind that
  might avoid the problem:

  picom --config /dev/null --show-all-xerrors --log-level=TRACE &
  sleep 20; killall picom

Note that this will emit a lot of log messages and picom will be
  killed after 20 seconds (resulting in no compositor X session which
  should be usable if not pretty).

  - Switch to different virtual terminals with CTRL+ALT+F1, CTRL+ALT+F2,
  ..., CTRL+ALT+F7 and wait for display to refresh on each terminal.

  - 

[Kernel-packages] [Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"

2024-03-23 Thread Eugene San
Update:
Since release of 6.8.0-20.20 real machine (XPS13) seems to be working fine.
VMs are still hanging.

Short testing showed that the issue is caused by RAM starvation.
Booting LiveCD or Desktop should consume ~1.2GB but under 6.8, it starts with 
~2GB usage and keeps going up.
Maybe it is related to filesystem subsystem while using ISO9660/OverlayFS. Once 
the system hangs it keeps reading from optical device.

The issue with LiveCD install can be mitigated by increasing VM's memory
to at least 3GB or more.

P.S.
The issue might have been fixed with 6.8.0-20.20 but we'll have to wait and see 
since ISOs with this kernel are still not available.

-- 
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:
  Confirmed

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 2057693] Re: Activating autotrim results in high load average due to uninterruptible threads

2024-03-23 Thread Bug Watch Updater
** Changed in: zfs
   Status: Unknown => 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/2057693

Title:
  Activating autotrim results in high load average due to
  uninterruptible threads

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When activating the autotrim feature on any ZFS version starting from
  2.2.0 this will lead to a permanent increase of the load average (as
  diplayed in top) due to an uninterruptible vdev_autotrim thread for
  each vdev capable of TRIM.

  This issue has been reported
  (https://github.com/openzfs/zfs/issues/15453) as well as fixed
  (https://github.com/openzfs/zfs/pull/15781) upstream but the fix is
  not yet backported to Ubuntu.

  Since this bug was introduced with version 2.2.0 both mantic as well
  as noble are affected.

  How to reproduce:
  1. Create a pool with at least one TRIM-capable device
  2. run "zpool set autotrim=on "
  3. watch the output of "top" or "runtime" and see how the load average 
increases permanently even when the system is idle by one per vdev
  4. running "ps aux | grep -w D" will show the broken threads:

  [root@test ~]# ps aux | grep -w D\<
  root7193  0.0  0.0  0 0 ?D<   13:07   0:00 
[vdev_autotrim]

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


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


[Kernel-packages] [Bug 2058808] [NEW] iwlwifi disconnect and crash - intel wifi7

2024-03-23 Thread Jacek Kowalski
Public bug reported:

iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.

[ cut here ]
Invalid rxb from HW 0
WARNING: CPU: 14 PID: 896 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher af_alg 
bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds joydev 
ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
 xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
RSP: 0018:b91d803e0e18 EFLAGS: 00010246
RAX:  RBX: 956747353c30 RCX: 
RDX:  RSI:  RDI: 
RBP: b91d803e0e78 R08:  R09: 
R10:  R11:  R12: 1007
R13: 0015 R14:  R15: 956746a30028
FS:  () GS:95768f38() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
PKRU: 5554
Call Trace:
 
 ? show_regs+0x6d/0x80
 ? __warn+0x89/0x160
 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
 ? report_bug+0x17e/0x1b0
 ? handle_bug+0x46/0x90
 ? exc_invalid_op+0x18/0x80
 ? asm_exc_invalid_op+0x1b/0x20
 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
 ? free_unref_page+0x30/0x180
 iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
 ? skb_free_head+0xa8/0xd0
 __napi_poll+0x30/0x1f0
 net_rx_action+0x181/0x2e0
 ? __irq_wake_thread+0x42/0x50
 __do_softirq+0xd9/0x349
 ? __pfx_irq_thread_fn+0x10/0x10
 do_softirq.part.0+0x41/0x80
 
 
 __local_bh_enable_ip+0x72/0x80
 iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
 irq_thread_fn+0x21/0x70
 irq_thread+0xf8/0x1c0
 ? __pfx_irq_thread_dtor+0x10/0x10
 ? __pfx_irq_thread+0x10/0x10
 kthread+0xef/0x120
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x44/0x70
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1b/0x30
 
---[ end trace  ]---
iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
iwlwifi :05:00.0: Start IWL Error Log Dump:
iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN   
iwlwifi :05:00.0: 0x0003 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C280A | branchlink2
iwlwifi :05:00.0: 0x9328 | interruptlink1
iwlwifi :05:00.0: 0x9328 | interruptlink2
iwlwifi :05:00.0: 0xF46C | data1
iwlwifi :05:00.0: 0x0100 | data2
iwlwifi :05:00.0: 0x | data3
iwlwifi :05:00.0: 0xA0005E44 | beacon time
iwlwifi :05:00.0: 0x2806818F | tsf low
iwlwifi :05:00.0: 0x | tsf hi
iwlwifi :05:00.0: 0x | time gp1
iwlwifi :05:00.0: 0x0BB840A7 | time gp2
iwlwifi :05:00.0: 0x0001 | uCode revision type
iwlwifi :05:00.0: 0x0053 | uCode version major
iwlwifi :05:00.0: 0xEC13314B | uCode version minor
iwlwifi :05:00.0: 0x0472 | hw version
iwlwifi :05:00.0: 0x00C80002 | board version
iwlwifi :05:00.0: 0x03B7001C | hcmd
iwlwifi :05:00.0: 0x67F68000 | isr0
iwlwifi :05:00.0: 0x0140 | isr1
iwlwifi :05:00.0: 0x48F0001A | isr2
iwlwifi :05:00.0: 0x00C0040A | isr3
iwlwifi :05:00.0: 0x1000 | isr4
iwlwifi :05:00.0: 0x03B6001C | last cmd Id
iwlwifi :05:00.0: 0xF46C | wait_event
iwlwifi :05:00.0: 0x00304288 | l2p_control
iwlwifi :05:00.0: 0x00019C34 | l2p_duration
iwlwifi :05:00.0: 0x02001A5A | l2p_mhvalid
iwlwifi :05:00.0: 0x01D8 | l2p_addr_match
iwlwifi :05:00.0: 0x0009 | lmpm_pmg_sel
iwlwifi :05:00.0: 0x | timestamp
iwlwifi :05:00.0: 0xC828 | flow_handler
iwlwifi :05:00.0: Start IWL Error Log Dump:
iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0084 | 

[Kernel-packages] [Bug 2057693] Re: Activating autotrim results in high load average due to uninterruptible threads

2024-03-23 Thread trackwitz
** Bug watch added: github.com/openzfs/zfs/issues #15453
   https://github.com/openzfs/zfs/issues/15453

** Also affects: zfs via
   https://github.com/openzfs/zfs/issues/15453
   Importance: Unknown
   Status: Unknown

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

Title:
  Activating autotrim results in high load average due to
  uninterruptible threads

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When activating the autotrim feature on any ZFS version starting from
  2.2.0 this will lead to a permanent increase of the load average (as
  diplayed in top) due to an uninterruptible vdev_autotrim thread for
  each vdev capable of TRIM.

  This issue has been reported
  (https://github.com/openzfs/zfs/issues/15453) as well as fixed
  (https://github.com/openzfs/zfs/pull/15781) upstream but the fix is
  not yet backported to Ubuntu.

  Since this bug was introduced with version 2.2.0 both mantic as well
  as noble are affected.

  How to reproduce:
  1. Create a pool with at least one TRIM-capable device
  2. run "zpool set autotrim=on "
  3. watch the output of "top" or "runtime" and see how the load average 
increases permanently even when the system is idle by one per vdev
  4. running "ps aux | grep -w D" will show the broken threads:

  [root@test ~]# ps aux | grep -w D\<
  root7193  0.0  0.0  0 0 ?D<   13:07   0:00 
[vdev_autotrim]

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


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


[Kernel-packages] [Bug 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application

2024-03-23 Thread Edward
As mentioned above, this turns out to have been a Chrome/Chromium bug
exposed by the new kernel. It has been fixed in Chrome 123, which is now
the stable release. This issue can be closed.

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

Title:
  Linux 6.5 breaks Novation Components web MIDI application

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: 23.10
  Kernel version: 6.5.0-10

  Steps to recreate:
  1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
  2. Navigate to https://components.novationmusic.com/
  3. Connect a Novation Circuit Tracks via USB

  Expected behaviour (demonstrated by 
linux-image-unsigned-6.4.16-060416-generic):
  - Circuit Tracks shows up in UI with a state of "Connected"

  Observed behaviour:
  - Circuit Tracks shows up in UI with a state of "Connecting" and eventually 
"Connection error"

  Notes:
  - Basic MIDI functions are present (sending notes, clocks etc.)
  - loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N 
makes no difference

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ecoffey2236 F wireplumber
   /dev/snd/controlC1:  ecoffey2236 F wireplumber
   /dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 16:25:39 2023
  InstallationDate: Installed on 2022-12-14 (333 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
  dmi.bios.date: 10/14/2022
  dmi.bios.release: 20.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2014
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z690-P WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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