[Bug 2085541] Re: [SRU] [nano] [agx] [nx] No video output after suspend

Loïc Minier 2085541 at bugs.launchpad.net
Wed Nov 13 17:28:16 UTC 2024


** Description changed:

  [ Impact ]
  
-  * On nvidia Jetson Orin platforms installed with Ubuntu for Jetson
- classic server image, a connected monitor will not light up again after
- a suspend-resume cycle
+  * On NVIDIA Jetson Orin platforms installed with candidate Ubuntu for
+ Jetson images (https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-
+ server/jammy/daily-preinstalled/), a monitor connected to the
+ DisplayPort will not light up again after a suspend-resume cycle
  
-  * On these platforms, a monitor will not display any output if it is
- connected after the system boots or when being disconnected and
+  * In the same configuration, a monitor will not display any output if
+ it is connected after the system boots or when being disconnected and
  reconnected while the system is running
  
-  * This will be fixed by adding the file /etc/modules-load.d/nvidia-
+  * These issues affect Ubuntu 22.04 certification on Jetson Orin
+ platforms.
+ 
+  * This will be fixed by adding the file /etc/modules-load.d/nvidia-
  drm.conf that force-loads the nvidia-drm module.
  
-  *The module will also need to be loaded with the appropriate parameters
- modeset=1 and fbdev=1 which will be the default starting with the tegra-
- igx kernel 1019
+  * The module will also need to be loaded with the appropriate
+ parameters modeset=1 and fbdev=1 which will be the default starting with
+ the tegra-igx kernel 1019
  
  [ Test Plan ]
-  * Install an Ubuntu for Jetson image on a Tegra platform and make sure to install a kernel version >= 1019 from jammy-proposed if it's not already the case. Connect a monitor to the Displayport and boot up the system. Then disconnect and reconnect the monitor to observe that the terminal is showing up on the monitor again.
  
-  * With the monitor connected, run the following command and observe the
- terminal showing up on the monitor again after a suspend-resume cycle:
+  * Install the candidate Ubuntu for Jetson image (https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-server/jammy/daily-preinstalled/manual/ – build 20240919) on a Jetson AGX Orin
+  * Upgrade to latest packages, making particularly sure to install the latest jetson meta-package (apt install linux-nvidia-tegra-igx-jetson) and kernel package (1019 ABI or later) from jammy-updates
+  * Reboot the system without a monitor connected, connect a monitor, see that it doesn't show any video output
+  * Reboot the system with a monitor connected, see that it shows console output, trigger a suspend-resume cycle with the command below and see that video output is not coming back (you can connect over e.g. serial or SSH to confirm the system is truly back from suspend):
+    $ sudo rtcwake -m no -s 30 && sudo systemctl suspend
  
-    $ sudo rtcwake -m no -s 30 && sudo systemctl suspend
+  * Install nvidia-tegra-defaults from -proposed; NB: there are no noble
+ images, but it's fine to install the noble-proposed build on top of the
+ jammy image to confirm it will work properly after an upgrade
+ 
+  * Rerun the above monitor testing instructions rebooting between tests
+ and confirm that console output works even when the monitor is plugged
+ after boot, or after a suspend-resume cycle
  
  [ Where problems could occur ]
  
   * No additional problems should happen as the nvidia-drm kernel module
  is usually automatically loaded with these parameters when it is pulled
  in by an X11 dependency. Nvidia releases 2 desktop images using that
  mechanism (Jetpack and BaseOS). This intends to fix the behavior on a
  Ubuntu server image.
  
-  * If a user installs this package on a different platform, running a
+  * If a user installs this package on a different platform, running a
  different kernel, the nvidia-drm kernel module will not be present and
  subsequently not loaded and therefore does not impact such systems.
  
  [ Other Info ]
  
-  * This is related to two internal bugs being discussed between
- Canonical and Nvidia
+  * This is related to two private bugs being discussed between Canonical
+ and NVIDIA; because NVIDIA uses the kernel packages in their own Ubuntu-
+ based images, it's not possible to include this fix in the kernel
+ package itself as NVIDIA doesn't want nvidia-drm to be force loaded for
+ their usage
  
- ProblemType: Bug
- DistroRelease: Ubuntu 22.04
- Package: nvidia-tegra-defaults 1.3~22.04.2
- ProcVersionSignature: User Name 5.15.0-1019.19-nvidia-tegra-igx 5.15.163
- Uname: Linux 5.15.0-1019-nvidia-tegra-igx aarch64
- ApportVersion: 2.20.11-0ubuntu82.6
- Architecture: arm64
- CasperMD5CheckResult: unknown
- CloudArchitecture: aarch64
- CloudID: nocloud
- CloudName: unknown
- CloudPlatform: nocloud
- CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
- Date: Thu Oct 24 13:14:55 2024
- Dependencies:
- 
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=C.UTF-8
-  SHELL=/bin/bash
- SourcePackage: nvidia-tegra-defaults
- UpgradeStatus: No upgrade log present (probably fresh install)
+  * See also https://discourse.ubuntu.com/t/changes-to-ubuntu-for-tegra-
+ kernel-metapackages-on-jetson-and-igx/48807 for current changes
+ affecting jetson kernel metapackages

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2085541

Title:
  [SRU] [nano] [agx] [nx] No video output after suspend

Status in nvidia-tegra-defaults package in Ubuntu:
  Fix Released
Status in nvidia-tegra-defaults source package in Jammy:
  In Progress
Status in nvidia-tegra-defaults source package in Noble:
  In Progress

Bug description:
  [ Impact ]

   * On NVIDIA Jetson Orin platforms installed with candidate Ubuntu for
  Jetson images (https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-
  server/jammy/daily-preinstalled/), a monitor connected to the
  DisplayPort will not light up again after a suspend-resume cycle

   * In the same configuration, a monitor will not display any output if
  it is connected after the system boots or when being disconnected and
  reconnected while the system is running

   * These issues affect Ubuntu 22.04 certification on Jetson Orin
  platforms.

   * This will be fixed by adding the file /etc/modules-load.d/nvidia-
  drm.conf that force-loads the nvidia-drm module.

   * The module will also need to be loaded with the appropriate
  parameters modeset=1 and fbdev=1 which will be the default starting
  with the tegra-igx kernel 1019

  [ Test Plan ]

   * Install the candidate Ubuntu for Jetson image (https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-server/jammy/daily-preinstalled/manual/ – build 20240919) on a Jetson AGX Orin
   * Upgrade to latest packages, making particularly sure to install the latest jetson meta-package (apt install linux-nvidia-tegra-igx-jetson) and kernel package (1019 ABI or later) from jammy-updates
   * Reboot the system without a monitor connected, connect a monitor, see that it doesn't show any video output
   * Reboot the system with a monitor connected, see that it shows console output, trigger a suspend-resume cycle with the command below and see that video output is not coming back (you can connect over e.g. serial or SSH to confirm the system is truly back from suspend):
     $ sudo rtcwake -m no -s 30 && sudo systemctl suspend

   * Install nvidia-tegra-defaults from -proposed; NB: there are no
  noble images, but it's fine to install the noble-proposed build on top
  of the jammy image to confirm it will work properly after an upgrade

   * Rerun the above monitor testing instructions rebooting between
  tests and confirm that console output works even when the monitor is
  plugged after boot, or after a suspend-resume cycle

  [ Where problems could occur ]

   * No additional problems should happen as the nvidia-drm kernel
  module is usually automatically loaded with these parameters when it
  is pulled in by an X11 dependency. Nvidia releases 2 desktop images
  using that mechanism (Jetpack and BaseOS). This intends to fix the
  behavior on a Ubuntu server image.

   * If a user installs this package on a different platform, running a
  different kernel, the nvidia-drm kernel module will not be present and
  subsequently not loaded and therefore does not impact such systems.

  [ Other Info ]

   * This is related to two private bugs being discussed between
  Canonical and NVIDIA; because NVIDIA uses the kernel packages in their
  own Ubuntu-based images, it's not possible to include this fix in the
  kernel package itself as NVIDIA doesn't want nvidia-drm to be force
  loaded for their usage

   * See also https://discourse.ubuntu.com/t/changes-to-ubuntu-for-
  tegra-kernel-metapackages-on-jetson-and-igx/48807 for current changes
  affecting jetson kernel metapackages

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




More information about the Ubuntu-sponsors mailing list