Public bug reported: [Summary] stress-ng procfs cause kernel call trace error with the Ubuntu 24.04 server image on Jetson AGX Thor
[Steps to reproduce] 1. flash the https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-server/noble/daily-preinstalled/manual/noble-preinstalled-server-arm64+tegra-jetson.img.xz image 2. Boot in OS 3. sudo add-apt-repository ppa:colin-king/ppa 4. sudo apt install stress-ng 5. stress-ng --procfs 0 --timeout 30 --oom-avoid-bytes 10% --skip-silent --verbose [Expected result] Pass. [Actual result] Cause kernel call trace error. [Failure rate] 3/3 [Affected test cases] N/A [Description] Tested with the kernel 6.8.0-1013-nvidia-tegra. The test immediately triggers a lot of kernel traces, showing up on the serial console, continuously until the end of the test. After a few minutes, it ends with a final kernel panic, until the board eventually reboots ubuntu@ubuntu:~$ stress-ng --procfs 0 --timeout 30 --oom-avoid-bytes 10% --skip-silent --verbose stress-ng: debug: [3698] invoked with 'stress-ng --procfs 0 --timeout 30 --oom-avoid-bytes 10% --skip-silent --verbose' by user 1000 'ubuntu' stress-ng: debug: [3698] stress-ng 0.20.01 stress-ng: debug: [3698] system: Linux ubuntu 6.8.0-1013-nvidia-tegra #13-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 13 19:09:54 UTC 2025 aarch64, gcc 13.3.0, glibc 2.39, little endian stress-ng: debug: [3698] RAM total: 122.6G, RAM free: 120.5G, swap free: 0.0 stress-ng: debug: [3698] temporary file path: '/home/ubuntu', filesystem type: ext4 (235472515 blocks available, WD PC SN5000S SDEPNSJ-1T00) stress-ng: debug: [3698] CPUs have 3 idle states: BUSY, WFI, cc7 stress-ng: debug: [3698] 14 processors online, 14 processors configured stress-ng: info: [3698] setting to a 30 secs run per stressor stress-ng: debug: [3698] shared cache allocate: using cache maximum level L2 stress-ng: debug: [3698] CPU data cache: L1: 64K, L2: 1024K stress-ng: debug: [3698] shared cache allocate: shared cache buffer size: 1024K stress-ng: info: [3698] dispatching hogs: 14 procfs stress-ng: debug: [3698] starting stressor stress-ng: debug: [3699] procfs: [3699] started (instance 0 on CPU 13) stress-ng: debug: [3700] procfs: [3700] started (instance 1 on CPU 0) stress-ng: debug: [3701] procfs: [3701] started (instance 2 on CPU 1) stress-ng: debug: [3698] 14 stressors started stress-ng: debug: [3709] procfs: [3709] started (instance 10 on CPU 10) stress-ng: debug: [3711] procfs: [3711] started (instance 12 on CPU 11) stress-ng: debug: [3716] procfs: [3716] started (instance 13 on CPU 12) stress-ng: debug: [3708] procfs: [3708] started (instance 9 on CPU 8) stress-ng: debug: [3710] procfs: [3710] started (instance 11 on CPU 9) stress-ng: debug: [3705] procfs: [3705] started (instance 6 on CPU 5) stress-ng: debug: [3704] procfs: [3704] started (instance 5 on CPU 4) stress-ng: debug: [3702] procfs: [3702] started (instance 3 on CPU 2) stress-ng: debug: [3703] procfs: [3703] started (instance 4 on CPU 3) stress-ng: debug: [3707] procfs: [3707] started (instance 8 on CPU 7) stress-ng: debug: [3706] procfs: [3706] started (instance 7 on CPU 6) stress-ng: debug: [3698] procfs: [3699] terminated on signal 11 'SIGSEGV' stress-ng: debug: [3698] procfs: [3699] aborted via a termination signal stress-ng: debug: [3698] procfs: [3699] terminated (killed by signal) stress-ng: debug: [3700] procfs: [3700] exited (instance 1 on CPU 7) stress-ng: debug: [3701] procfs: [3701] exited (instance 2 on CPU 12) stress-ng: debug: [3698] procfs: [3701] terminated (success) stress-ng: debug: [3698] procfs: [3700] terminated (success) stress-ng: debug: [3704] procfs: [3704] exited (instance 5 on CPU 9) stress-ng: debug: [3698] procfs: [3704] terminated (success) stress-ng: debug: [3709] procfs: [3709] exited (instance 10 on CPU 1) stress-ng: debug: [3698] procfs: [3709] terminated (success) stress-ng: debug: [3705] procfs: [3705] exited (instance 6 on CPU 1) stress-ng: debug: [3698] procfs: [3705] terminated (success) stress-ng: debug: [3698] procfs: [3707] terminated on signal 11 'SIGSEGV' stress-ng: debug: [3698] procfs: [3707] aborted via a termination signal stress-ng: debug: [3698] procfs: [3707] terminated (killed by signal) stress-ng: debug: [3698] procfs: [3703] terminated on signal 11 'SIGSEGV' stress-ng: debug: [3698] procfs: [3703] aborted via a termination signal stress-ng: debug: [3698] procfs: [3703] terminated (killed by signal) stress-ng: debug: [3702] procfs: [3702] exited (instance 3 on CPU 7) stress-ng: debug: [3698] procfs: [3702] terminated (success) stress-ng: debug: [3716] procfs: [3716] exited (instance 13 on CPU 1) stress-ng: debug: [3698] procfs: [3716] terminated (success) stress-ng: debug: [3711] procfs: [3711] exited (instance 12 on CPU 11) stress-ng: debug: [3698] procfs: [3711] terminated (success) stress-ng: debug: [3710] procfs: [3710] exited (instance 11 on CPU 7) stress-ng: debug: [3698] procfs: [3710] terminated (success) stress-ng: debug: [3706] procfs: [3706] exited (instance 7 on CPU 6) stress-ng: debug: [3698] procfs: [3706] terminated (success) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-nvidia-tegra-jetson 6.8.0-1013.13+2 ProcVersionSignature: User Name 6.8.0-1013.13-nvidia-tegra 6.8.12 Uname: Linux 6.8.0-1013-nvidia-tegra aarch64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) Date: Tue Feb 24 14:42:36 2026 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color XDG_RUNTIME_DIR=<set> SourcePackage: linux-nvidia-tegra-modules-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-nvidia-tegra-modules-signed (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 jetson noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2142602 Title: stress-ng procfs cause kernel call trace error (linux-nvidia-tegra- jetson on Jetson AGX Thor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-modules-signed/+bug/2142602/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
