[gPXE-devel] [PATCH] [sky2] Disable interrupts by default

[Stefan Hajnoczi]

On Tue, Aug 3, 2010 at 4:53 PM, Gilles Martin <gilles.martin at psi.ch> wrote:
> ...
>> >>
>> >> 3. Build with debug messages: make DEBUG=sky2:10.  The output during
>> >> the first dhcp would be interesting.
>> >
>> > I don't know how to capture debug messages, that's my problem...
>>
>> When there is a lot of debug output the serial console can be used to
>> send debug output to another machine over a serial cable.  Add #define
>> CONSOLE_SERIAL to config/local/console.h and rebuild to enable serial.
>>
>> Alternatively, a patch to send the console log over TCP was posted but
>> is not yet in mainline gPXE:
>> http://www.mail-archive.com/gpxe@etherboot.org/msg01115.html
>>
>> Stefan
>
> So, here is the output of the console. I am just able to type "dhcp
> net0" and then the debug output never ends.
>
> ftp://ftp.psi.ch/PSI_outgoing/mg07/capture_sky2.txt

Thanks for running the test.  The debug output will continue because
gPXE will always check the network device for new packets.  While you
are at the gPXE shell the network device is being polled in the
background and this causes debug messages to be generated.

The critical log information is what happens when the undionly.kpxe
DHCP hangs.  You can either keep typing as debug messages are
displayed or you can let it autoboot if your DHCP server is configured
to hand out the undionly.kpxe boot filename.

Stefan