> I don't understand what you mean. Pure64 leaves all interrupts disabled
> once it is finished.
Not quit. You make a "cli", but the rtc still fires. As soon as the loaded
SW enables interrupts, the RTC interrupt fires and (in the case of my
RTOS) an unhandled interrupt occurs because no user handler has been
> The RTC interrupt increments a clock counter, displaying the system status
> bar (enabled by default), and also restarting the CLI once a program has
> finished running. So it is useful but can be disabled.
Thats for BM. I disabled the RTC code in pure64, and now I have no
problems with the interrupt.
To bad, my attempt to disable the RTC again, did not work, maybe because
it is still pending.