I’ve set the configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES to 1 now. Let’s see if it catches the issue earlier.
The system is quite complex and shutting down interrupts altogether would cause the system to halt, because it’s event-driven from the get-go.
But regarding the interrupt priorities, the Ethernet driver interrupt is set to the system’s “default” interrupt priority level, meaning that it shares the same interrupt priority with many others. There are a few timer interrupts with higher priority than that of the Ethernet driver.
I could try increasing the interrupt priority of the Ethernet driver to see if that has any effect for starters.