| 22 Mar 2025 |
 Sean | just read the stuff above. should I use mesa 24? | 00:19:34 |
| Sean | it doesn't start at all in mesa 24 | 00:43:24 |
 olivia | the gpu disappears and re-appears over and over again
what do you mean by this? | 00:56:18 |
| Sean | I mean in the proton logs I can see the vulkan device lost, over and over | 00:56:54 |
| olivia | https://gitlab.freedesktop.org/mesa/mesa/-/issues/12809 (which I think is the issue that the previous conversation was about, from skimming) seems unlikely to be related | 00:57:22 |
| olivia | ah, that makes sense | 00:57:29 |
| olivia | is there anything in the kernel logs? | 00:57:34 |
| olivia | I'm assuming this is amd? | 00:57:39 |
| Sean | oh I have this issue but yeah unrelated | 00:57:41 |
| Sean | let me check | 00:57:50 |
| olivia | * I'm assuming this is amd/radv? | 00:57:54 |
| Sean | no nothing just this before it even starts happening
Mar 21 21:01:08 nixos-desktop kernel: umip: MonsterHunterWi[79400] ip:1569dbf11 sp:8280eee8: SGDT instruction cannot be used by applications.
Mar 21 21:01:08 nixos-desktop kernel: umip: MonsterHunterWi[79400] ip:1569dbf11 sp:8280eee8: For now, expensive software emulation returns the result.
Mar 21 21:01:08 nixos-desktop kernel: umip: MonsterHunterWi[79400] ip:1569dbf11 sp:8280eee8: SGDT instruction cannot be used by applications.
Mar 21 21:01:08 nixos-desktop kernel: umip: MonsterHunterWi[79400] ip:1569dbf11 sp:8280eee8: For now, expensive software emulation returns the result.
Mar 21 21:01:10 nixos-desktop kernel: umip: MonsterHunterWi[79400] ip:7fc2c65b sp:8280fc30: SGDT instruction cannot be used by applications.
| 01:01:40 |
| olivia | that's probably unrelated | 01:02:17 |
| Sean | I got this after
Mar 21 21:01:31 nixos-desktop kernel: mce: [Hardware Error]: Machine check events logged
Mar 21 21:01:31 nixos-desktop kernel: [Hardware Error]: Corrected error, no action required.
Mar 21 21:01:31 nixos-desktop kernel: [Hardware Error]: CPU:0 (19:21:2) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
Mar 21 21:01:31 nixos-desktop kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
Mar 21 21:01:31 nixos-desktop kernel:
Mar 21 21:01:31 nixos-desktop kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2
Mar 21 21:01:31 nixos-desktop kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
| 01:02:37 |
| Sean | let me try running my RAM at 2666 | 01:03:00 |
| olivia | I'm kinda surprised that proton even attempts to recover from VK_ERROR_DEVICE_LOST lol. That sounds like an enormous pain | 01:03:35 |
| olivia | oh, possible they don't have any special handling to quit the program on device loss, and so they're just getting the same error over and over again with every api call. That seems more likely | 01:04:02 |
| Sean | In reply to @olivia:computer.surgery
oh, possible they don't have any special handling to quit the program on device loss, and so they're just getting the same error over and over again with every api call. That seems more likely well it must recover somehow. since the game continues running | 01:08:16 |
| olivia | ah, yeah | 01:08:46 |
| olivia | * ah, if it continues running, then yeah | 01:08:54 |
| olivia | can you send some of the VKERRORDEVICE_LOST messages, plus the surrounding lines | 01:10:40 |
| olivia | can you send some of the VK_ERROR_DEVICE_LOST messages, plus the surrounding lines | 01:10:50 |
| Sean | sure but it’s kinda spammy because I have libunwrap or whatever | 01:12:00 |
| olivia | it looks like in all places I found in radv where it signals device loss, it should include some additional info, assuming the application has configured the debug callbacks | 01:12:19 |
| olivia | that's fine | 01:12:26 |
| Sean | https://p.seanbehan.ca/e096a
here's the last 2000 lines of the log | 01:17:20 |
| Sean | or 5000 lines https://p.seanbehan.ca/82dd0 | 01:19:13 |
| olivia | thanks! | 01:19:58 |
| Sean | it's just all EXCEPTION_ACCESS_VIOLATION | 01:20:00 |
| olivia | oh | 01:20:40 |
