Re: [Etherboot-developers] UNDI driver

[H. P. A. <hp...@zy...>]

Michael Brown wrote:
> 
> The only thing I can think of that could cause this is a corrupted 
> interrupt handler.  I've taken a look at pxeprefix.S.  It performs the PXE 
> API calls PXENV_UNDI_SHUTDOWN, PXENV_STOP_UNDI and PXENV_UNLOAD_STACK.  It 
> doesn't check the return status of any of these calls and it then proceeds 
> to forcibly free base memory, even if the API calls returned "No, you 
> can't free base memory because I've got an interrupt handler installed 
> that I can't unhook for some reason".
> 

Ouch!

I'd recommend looking at the unloading code in PXELINUX.  Getting 
unloading to work (semi-)reliably was the single hardest thing I had to 
deal with in PXELINUX, believe it or not.

PXELINUX is quite conservative; if it detects any errors it assumes 
memory is not freeable; Linux doesn't care anyway.

	-hpa