We might want to switch to error!() from println() or make this configurable in our panic_handler (uefi crate feature)? often when things go wrong? At least in one of my examples, I didn't actually get printed messages at all. Using error!() helped me at least to get log o the debugcon device.