search for: spontani

...: Try to download ldlinux.e64 4 - *CRASH* Now it is: 1 - HP ROM FW: Download syslinux.efi 2 - HP ROM FW: Run syslinux.efi 3 - Syslinux: Try to download ldlinux.e64 4 - Syslinux: Invoke ldlinux.e64 [...] 5 - Syslinux: Try to run vesamenu.c32 6 - *CRASH* In both cases *CRASH* can either be a spontanious reboot or one of a selection of Exceptions reported in red on black. Due to the randomness of the crashes my bet would be on an overwritten return address or longjmp address somewhere. In both cases there should be some error message or an exit back to the firmware bootloader indicating a f...

...device /dev/dsk - failed, Linux boots all installation clicks can been made, installation starts and then suddenly I/O stopped, domU still listet in VirtManager but domU frozen, no more I/O on the system in the middle we also faced a ''black-screen of death'' ie. system spontaniously rebooted without notice or dump I believe during some steps in 5) So to sump-up, it seems that everytime an installation attempted to start I/O to the pseudo-domU disk of whatever nature, I/O just stopped and the domU''s gone out to luch while the dom0 is up (apart from the panic and...

On 04-08-15 17:38, Oscar Roozen wrote: > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. I was busy adding some code to dprintf.h