Rot127

Second freeze ``` Jul 23 10:10:48 dom0 systemd-coredump[21057]: Process 13415 (xss-lock) of user 1000 dumped core. Stack trace of thread 13415: #0 0x00007d3cab8cbfc2 g_logv (libglib-2.0.so.0 + 0x59fc2) #1 0x00007d3cab8cc233 g_log...

Yes, this looks very much like it.

> As suggested in https://github.com/QubesOS/updates-status/issues/2982 I tried downgrading the firmware: Works well for me currently. No freezes for a long time.

Unfortunately I now experience the same crashes with the downgrade firmware. ``` > sudo dnf info linux-firmware Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00 Installed Packages...

It stays up the first and mostly the second time (can work for a few hours usually before the first freeze happens). The next crash it hangs up (no reboot,...

**Not** turning of the turbo mode of the processor (via `sudo xenpm disable-turbo-mode `) resolves the issue for me. Enabled turbo mode is the default though. Just mention it in...

I can disable turbo mode after some time (maybe around 30m) without running in those crashes. Which is nice since enabled turbo draws a lot of power.

The crashes occur when the turbo mode is off. So if the machine is not getting hot.

Can you provide an example of bytes, the output you get and the output you expect? Printing bytes instead of exiting the disassembly shouldn't be hard to implement.

This is possibly an issue with the Python binding then. If I run `cstool` it disassembles fine: ``` ./cstool -s cortexm "0x01,0x25,0x94,0xe7,0x0,0x0,0x3f,0xff,0xf0,0x6,0x1,0xff,0x90,0xf8,0x24,0x30,0x1,0x2b,0x2,0xd1,0x2,0x23,0x18,0x46,0x70,0x47,0x10,0xb5,0x4,0x46,0x1,0x23,0x80,0xf8,0x24,0x30,0xff,0xf7,0xc6,0xfe,0x3,0x46,0x38,0xb9,0xa2,0x6a,0x22,0xf4,0x88,0x52,0x22,0xf0,0x1,0x2,0x42,0xf0,0x1,0x2,0xa2,0x62,0x0,0x22,0x84,0xf8" 0 01 25 movs r5, #1 2 94...