amdgpu: Secure display: Generic Failure

Bug #2102188 reported by andrei

This bug report will be marked for expiration in 51 days if no further activity occurs. (find out why)

8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-amdgpu (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Sometimes after `sudo reboot` my PC can't finish off stage because
```
Mar 13 05:50:34 gs kernel: amdgpu 0000:27:00.0: amdgpu: RAS: optional ras ta ucode is not available
Mar 13 05:50:34 gs kernel: amdgpu 0000:27:00.0: amdgpu: RAP: optional rap ta ucode is not available
Mar 13 05:50:34 gs kernel: amdgpu 0000:27:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
Mar 13 05:50:34 gs kernel: amdgpu 0000:27:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
Mar 13 05:50:34 gs kernel: amdgpu 0000:27:00.0: amdgpu: Secure display: Generic Failure.
Mar 13 05:50:34 gs kernel: amdgpu 0000:27:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
```

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: xserver-xorg-video-amdgpu 23.0.0-1build1
ProcVersionSignature: Ubuntu 6.11.0-19.19-generic 6.11.11
Uname: Linux 6.11.0-19-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 13 06:49:45 2025
DistUpgraded: Fresh install
DistroCodename: oracular
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c9) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b89]
InstallationDate: Installed on 2025-03-12 (1 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=e9bdd5bf-1af5-4c5a-8b51-00d088b63c2b ro spectre_v2=off nopti crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: xserver-xorg-video-amdgpu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.60
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd12/30/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.122-1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.8-1ubuntu1~24.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1.2
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-3ubuntu1

Revision history for this message
andrei (andrewternity) wrote :
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

When you reported this bug, was it a successful boot or did you have to drop to a terminal (like Ctrl+Alt+F1) to report this? I ask because the same error messages appear in your current system log, so it seems unlikely they're causing the failure.

I also note that you have a fairly old BIOS and it would be a good idea to update, for security if nothing else: https://www.msi.com/Motherboard/B450M-MORTAR-MAX/support
(Remember, the updated BIOS enables SecureBoot, so you need to sign 3rd party kernel modules or disable SecureBoot.)

Revision history for this message
andrei (andrewternity) wrote (last edit ):

It was no way to off my Linux using CLI so I made hard reset.. After successfully upload system again several times, I have sent bugrepo.
I have updated BIOS, I will inform if I met such problem again. Anyway for now this is ghost bug.

Revision history for this message
andrei (andrewternity) wrote :
Download full text (3.7 KiB)

I still don't met my problem but every start-up time I see warnings:
```
$ sudo dmesg | grep amdgpu
[ 7.468128] [drm] amdgpu kernel modesetting enabled.
[ 7.476150] amdgpu: Virtual CRAT table created for CPU
[ 7.476165] amdgpu: Topology: Add CPU node
[ 7.506451] amdgpu 0000:27:00.0: amdgpu: Fetched VBIOS from ROM BAR
[ 7.506455] amdgpu: ATOM BIOS: 113-PICASSO-118
[ 7.539664] amdgpu 0000:27:00.0: vgaarb: deactivate vga console
[ 7.539672] amdgpu 0000:27:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
[ 7.539732] amdgpu 0000:27:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[ 7.539737] amdgpu 0000:27:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[ 7.541525] [drm] amdgpu: 2048M of VRAM memory ready
[ 7.541531] [drm] amdgpu: 14618M of GTT memory ready.
[ 7.542739] amdgpu: hwmgr_sw_init smu backed is smu10_smu
[ 7.565455] amdgpu 0000:27:00.0: amdgpu: reserve 0x400000 from 0xf47fc00000 for PSP TMR
[ 7.638544] amdgpu 0000:27:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 7.645260] amdgpu 0000:27:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 7.649238] amdgpu 0000:27:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
[ 7.649357] amdgpu 0000:27:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
[ 7.649360] amdgpu 0000:27:00.0: amdgpu: Secure display: Generic Failure.
[ 7.649366] amdgpu 0000:27:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
[ 7.714378] snd_hda_intel 0000:27:00.1: bound 0000:27:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 7.762725] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[ 7.762741] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[ 7.762878] amdgpu: Virtual CRAT table created for GPU
[ 7.762925] amdgpu: Topology: Add dGPU node [0x15d8:0x1002]
[ 7.762927] kfd kfd: amdgpu: added device 1002:15d8
[ 7.762940] amdgpu 0000:27:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 11, active_cu_number 8
[ 7.762945] amdgpu 0000:27:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 7.762946] amdgpu 0000:27:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 7.762948] amdgpu 0000:27:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 7.762949] amdgpu 0000:27:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 7.762951] amdgpu 0000:27:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 7.762952] amdgpu 0000:27:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 7.762953] amdgpu 0000:27:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 7.762955] amdgpu 0000:27:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 7.762956] amdgpu 0000:27:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 7.762957] amdgpu 0000:27:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ 7.762958] amdgpu 0000:27:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[ 7.762959] amdgpu 0000:27:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[ 7.762961] amdgpu 0000:27:00.0: amdgpu: ring vcn_enc0 uses VM inv...

Read more...

Revision history for this message
Daniel Letzeisen (dtl131) wrote :

Again, none of the SecureDisplay/TA warnings are an issue. If you google them, you'll find they are common. I have them on my system too.

What might help is to look at log from a failed boot. After you have a failed boot and then boot successfully, get the log from the previous boot with:
sudo journalctl -b -1 > prevboot.txt

Attach file here.

Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.