BattleTech freeze - Xid 13 Illegal Instruction Encoding

Graphics / Linux Linux
,
1

The game BattleTech (2018) runs fine until a mission is started and then rendering freezes but audio and input work for a while. Eventually the GPU problem slows the system until a reboot is required.

There are many lines in /var/log/messages like the following:

Jan  2 11:52:26 fedora kernel: NVRM: Xid (PCI:0000:1c:00): 13, Graphics Exception: ESR 0x5197b0=0x2d0009 0x5197b4=0x4 0x5197a8=0x1c813b60 0x5197ac=0x1174 
Jan  2 11:52:26 fedora kernel: NVRM: Xid (PCI:0000:1c:00): 13, pid=2915, name=BattleTech, Graphics Exception: channel 0x0000000a, Class 0000ce97, Offset 00000000, Data 00000000 
Jan  2 11:52:26 fedora kernel: NVRM: Xid (PCI:0000:1c:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 0, SM 0): Illegal Instruction Encoding 
Jan  2 11:52:26 fedora kernel: NVRM: Xid (PCI:0000:1c:00): 13, Graphics SM Global Exception on (GPC 0, TPC 0, SM 0): Multiple Warp Errors

Attached is the debug report. The basic system info. is an RTX 5050, driver 580.105.08, running X11 on Linux kernel fedora 6.17.10.

nvidia-bug-report.log.gz (883.6 KB)

2

I attempted to upgrade the driver to 580.119.02, but the install for that failed. After verifying the .run archive the video output gets shutoff and I have to reboot. This is while in the systemctl
multi-user.target (no X11).

3

After upgrading to driver 580.126.09 there are no more “NVRM: Xid” errors output to /var/log/messages. The game still crashes in the same way however.

Note that installation of the driver failed in the same way as 580.119.02 (video signal to monitors gets cut off), but I was able to do it via ssh.

4

Hi @WickedSmoke , thanks for reporting this issue.
Could you kindly help to upload a bug report taken when you see the crash with the latest driver installed ? Thanks.

5

Here’s the report for running the game today. This time the same “NVRM: Xid” errors are back in the messages file.

nvidia-bug-report.log.gz (771.1 KB)

6

Thanks @WickedSmoke for sharing bug report.

I have filed a bug 5843578 internally for tracking purpose.

I will try to reproduce issue internally and will get back to you if required any additional information.