#Crashing error related to GPU, but I don't really understand it.

15 messages · Page 1 of 1 (latest)

indigo ermine
#

I've got an error log of the time it happened, but it says "illegal opcode in command stream"? This has happened once or twice.

Also my kernel. title Arch Linux (linux)-ZEN linux /vmlinuz-linux-zen initrd /amd-ucode.img initrd /initramfs-linux-zen.img options root=PARTUUID=4d76ca7f-5b26-4ed6-8564-42d1b64ce727 zswap.enabled=1 rw rd.udev.debug=0 rd.udev.timeout=0 systemd.debug_level=0 rootfstype=ext4 amdgpu.ppfeaturemask=0xffffffff

I've also tried with the non-zen kernel with no more success.

pale storm
#

both using a forbidden CPU opcode and whatever is happening here with the GPU

indigo ermine
#

It's definitely something weird. It crashed my whole active session, recovered, but with most things relying on the GPU crashing in the process

pale storm
#

this says it’s repeatedly trying to access memory it shouldn’t be accessing https://en.wikipedia.org/wiki/Page_fault

In computing, a page fault is an exception that the memory management unit (MMU) raises when a process accesses a memory page without proper preparations. Accessing the page requires a mapping to be added to the process's virtual address space. Furthermore, the actual page contents may need to be loaded from a back-up, e.g. a disk. The MMU detec...

#

this feels like an overwatch issue at this point

#

or the compatibility layer

indigo ermine
#

Hmm... GE proton, or gamescope seem more likely of the two?

pale storm
#

gamescope is a simple compositor, so it’d have to be proton

#

either that or the overwatch devs are just bad

indigo ermine
#

I mean, they ARE a small indi company... But this does help narrow down the screw up to 'not explicitly something I did' Which is a good sign

pale storm
#

yea I doubt you could do anything to make a program very memory-unsafe

indigo ermine
#

I haven't done much in the way of programming myself lately. All I've done as of late is uhh.... messed with satty because flameshot sucks, and trying a new launcher or two in place of fuzzel

#

And neither of those are specifically invasive