Re: [edk2] [PATCH 1/2] OvmfPkg/SMBIOS: Reuse handles supplied by underlying VM

2014-05-16 Thread Jordan Justen
On Thu, May 15, 2014 at 4:30 AM, Wei Liu wrote: > On Wed, May 14, 2014 at 12:34:14PM -0400, Gabriel L. Somlo wrote: >> On Wed, May 14, 2014 at 02:55:15PM +0100, Wei Liu wrote: >> > On Wed, May 14, 2014 at 03:31:48PM +0200, Laszlo Ersek wrote: >> > > On 05/14/14 00:13, Gabriel L. Somlo wrote: >> >

Re: [edk2] Crash in qemu + OVMF after a call to DEBUG()

2014-05-16 Thread Laszlo Ersek
On 05/16/14 16:59, Nigel Croxon wrote: > This patch breaks compiling on new GCC. > https://sourceforge.net/p/gnu-efi/bugs/7/ 1. My earlier analysis and patch was wrong, so it's good that Nigel reverted it. I had missed the fact that on __GNUC__, "efistdarg.h" includes the system-wide . The open-c

Re: [edk2] Crash in qemu + OVMF after a call to DEBUG()

2014-05-16 Thread Jordan Justen
On Fri, May 16, 2014 at 2:44 AM, Ludovic Rousseau wrote: > 2014-05-13 17:56 GMT+02:00 Laszlo Ersek : >> In addition, if you can reproduce this crash with a OVMF binary that you >> build yourself (preferably from a fresh checkout), then you'll have the >> "ConSplitterDxe.dll" file available (refere

[edk2] HotkeyBoot() only called after normal boot fails?

2014-05-16 Thread Tim Lewis
In examining how the current tianocore BDS works, it seems that the UEFI-defined hot keys are ignored except after a boot failure for normal boot options. It appears there is a missing call to HotkeyBoot() in BdsEntry.c inside the loop. Currently, the only calls to this function are in FrontPage

Re: [edk2] Crash in qemu + OVMF after a call to DEBUG()

2014-05-16 Thread Bill Paul
Of all the gin joints in all the towns in all the world, Ludovic Rousseau had to walk into mine at 02:44:33 on Friday 16 May 2014 and say: > 2014-05-13 17:56 GMT+02:00 Laszlo Ersek : > > In addition, if you can reproduce this crash with a OVMF binary that you > > build yourself (preferably from a

Re: [edk2] Howto get level EFI_D_INFO logs in the console using qemu + OVMF?

2014-05-16 Thread Andrew Fish
On May 16, 2014, at 7:52 AM, Ludovic Rousseau wrote: > Hello, > > I can use DEBUG() when I build my test application using edk2. Great. > No more crash. > > In my application I used: > #include > >DEBUG((EFI_D_INFO, "EFI_D_INFO\n")); >DEBUG((EFI_D_ERROR, "EFI_D_ERROR\n")); > > I st

Re: [edk2] Unloading Ram Disk Driver

2014-05-16 Thread Andrew Fish
On May 16, 2014, at 6:56 AM, André Dantas wrote: > Anybody can help me? > > > On Tue, May 13, 2014 at 5:05 PM, André Dantas > wrote: > Hi guys, > > I'm working with the mkramdisk.efi application of Efi Toolkit 2.0. However I > can't see a way to free > the resources used by the ram disk af

[edk2] Howto get level EFI_D_INFO logs in the console using qemu + OVMF?

2014-05-16 Thread Ludovic Rousseau
Hello, I can use DEBUG() when I build my test application using edk2. Great. No more crash. In my application I used: #include DEBUG((EFI_D_INFO, "EFI_D_INFO\n")); DEBUG((EFI_D_ERROR, "EFI_D_ERROR\n")); I start qemu using: qemu-system-x86_64 -bios $OVMF \ -boot c -m 128 -hda 'disk.

Re: [edk2] Crash in qemu + OVMF after a call to DEBUG()

2014-05-16 Thread Ludovic Rousseau
2014-05-13 17:56 GMT+02:00 Laszlo Ersek : > On 05/13/14 16:55, Ludovic Rousseau wrote: >> 2014-05-13 16:24 GMT+02:00 Laszlo Ersek : > >>> Please rebuild your gnu-efi installation with the attached patch, and >>> retest your app. >> >> I still get a crash but with a different message in serial.log >

Re: [edk2] Unloading Ram Disk Driver

2014-05-16 Thread André Dantas
Anybody can help me? On Tue, May 13, 2014 at 5:05 PM, André Dantas wrote: > Hi guys, > > I'm working with the mkramdisk.efi application of Efi Toolkit 2.0. However > I can't see a way to free > the resources used by the ram disk after I don't need it anymore. I took a > look into the source code

Re: [edk2] Crash in qemu + OVMF after a call to DEBUG()

2014-05-16 Thread Laszlo Ersek
On 05/16/14 11:44, Ludovic Rousseau wrote: > 2014-05-13 17:56 GMT+02:00 Laszlo Ersek : >> In addition, if you can reproduce this crash with a OVMF binary that you >> build yourself (preferably from a fresh checkout), then you'll have the >> "ConSplitterDxe.dll" file available (referenced above). >

Re: [edk2] Crash in qemu + OVMF after a call to DEBUG()

2014-05-16 Thread Ludovic Rousseau
2014-05-13 17:56 GMT+02:00 Laszlo Ersek : > In addition, if you can reproduce this crash with a OVMF binary that you > build yourself (preferably from a fresh checkout), then you'll have the > "ConSplitterDxe.dll" file available (referenced above). I do not yet have a working edk2 build environmen