NVIDIA / NVIDIA/open-gpu-kernel-modules

GSP-FMC Failure Lenovo Legion RTX 5080 - Ubuntu24.04

Open
#1,120 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

tried: nvidia-driver-590-open, nvidia-driver-570-open and nvidia-driver-595-open (.run)

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
  • I confirm that this does not happen with the proprietary driver package.
Operating System and Version

Ubunto 24.04

Kernel Release

6.17.0-22-generic but tried also on 6.8.0-110

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Hardware: GPU

RTX 5080

Describe the bug

GPU stopped working so lost also HDMI see logs:
sudo dmesg | grep -i "gsp|nvrm" | tail -20
[ 43.077796] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x62:0x55:1861)
[ 43.078323] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0
[ 43.139237] NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
[ 43.337565] NVRM: kgspBootstrap_GH100: GSP-FMC reported an error while attempting to boot GSP: 0xb
[ 43.337600] NVRM: RmInitAdapter: Cannot initialize GSP firmware RM
[ 43.339275] NVRM: iovaspaceDestruct_IMPL: 1 left-over mappings in IOVAS 0x200
[ 43.339290] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x62:0x55:1861)
[ 43.339794] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0
[ 43.374999] NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
[ 43.573777] NVRM: kgspBootstrap_GH100: GSP-FMC reported an error while attempting to boot GSP: 0xb
[ 43.573821] NVRM: RmInitAdapter: Cannot initialize GSP firmware RM
[ 43.575052] NVRM: iovaspaceDestruct_IMPL: 1 left-over mappings in IOVAS 0x200
[ 43.575066] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x62:0x55:1861)
[ 43.575472] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0
[ 43.630381] NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
[ 43.825092] NVRM: kgspBootstrap_GH100: GSP-FMC reported an error while attempting to boot GSP: 0xb
[ 43.825241] NVRM: RmInitAdapter: Cannot initialize GSP firmware RM
[ 43.826947] NVRM: iovaspaceDestruct_IMPL: 1 left-over mappings in IOVAS 0x200
[ 43.826959] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x62:0x55:1861)
[ 43.827468] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0

To Reproduce

Just use lenovo legio i7 Pro eith rtx 5080 on ubuntu 24.04

Bug Incidence

Once

nvidia-bug-report.log.gz

amirma@rdwrlnx-Amirma:~$ sudo nvidia-bug-report.sh
[sudo] password for amirma:

nvidia-bug-report.sh will now collect information about your
system and create the file 'nvidia-bug-report.log.gz' in the current
directory. It may take several seconds to run. In some
cases, it may hang trying to capture data generated dynamically
by the Linux kernel and/or the NVIDIA kernel module. While
the bug report log file will be incomplete if this happens, it
may still contain enough data to diagnose your problem.

If nvidia-bug-report.sh hangs, consider running with the --safe-mode
and --extra-system-data command line arguments.

Please include the 'nvidia-bug-report.log.gz' log file when reporting
your bug via the NVIDIA Linux forum (see forums.developer.nvidia.com)
or by sending email to 'linux-bugs@nvidia.com'.

By delivering 'nvidia-bug-report.log.gz' to NVIDIA, you acknowledge
and agree that personal information may inadvertently be included in
the output. Notwithstanding the foregoing, NVIDIA will use the
output only for the purpose of investigating your reported issue.

Running nvidia-bug-report.sh...
complete.

Summary of Skipped Sections:

Skipped Component | Details

ldd output | glxinfo not found

vulkaninfo output | vulkaninfo not found

ibstat output | ibstat not found

acpidump output | acpidump not found

mst output | mst not found

nvlsm-bug-report.sh output | nvlsm-bug-report.sh not found

Summary of Errors:

Error Component | Details | Resolution

amirma@rdwrlnx-Amirma:~$

More Info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported dmesg command and the repeated RmInitAdapter and kgspBootstrap_GH100 errors. Reproduce on the Lenovo Legion with the RTX 5080 across the listed Ubuntu kernels and driver versions, then inspect the output from nvidia-bug-report.sh. Done means the GSP-FMC failure is characterized with complete logs and a confirmed driver-specific result.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux, ubuntu
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.