Josh,
I reloaded the eeprom with the reference image from Intel. Now it
appears we get a little further.
Loading driver at 0x352CD000 EntryPoint=0x352D72D8
RIP - 00000000352CD1F4, CS - 0000000000000038, RFLAGS - 0000000000010213
$ addr2line -fe bin-x86_64-efi/e1000e.efi.tmp 0x11f4
e1000e_get_cfg_done_80003es2lan
e1000e_80003es2lan.c:0
Have a good weekend.
Thanks,
Mike
Mike Bishton wrote:
Josh,
$ addr2line -fe bin-x86_64-efi/e1000e.efi.tmp 0x1241
e1000e_init_nvm_params_80003es2lan
e1000e_80003es2lan.c:0
Now that I think about it, I'm working with a proto board so I'm not
entirely sure that the eeprom is programmed correctly. I do know that
the controller works with the Intel PXE ROM and with the Linux e1000e
driver though. I'll try to verify that the contents are sane.
Thanks,
Mike
Joshua Oreman wrote:
On Fri, Apr 2, 2010 at 4:17 PM, Mike Bishton <[email protected]> wrote:
Josh,
The output of the `nm bin-x86_64-efi/e1000e.efi.tmp` is attached.
addr2line returned an error as written. Switching -ef to -fe resulted in
??
??:0
00000000000011f9 t e1000e_init_nvm_params_80003es2lan
0000000000001315 t e1000e_init_mac_params_80003es2lan
It looks like you're crashing somewhere in
e1000e_init_nvm_params_80003es2lan. Could you try `addr2line -fe
bin-x86_64-efi/e1000e.efi.tmp 0x1241'? Sorry about the incorrect
syntax in my earlier suggestion.
Thanks,
-- Josh
------------------------------------------------------------------------
_______________________________________________
gPXE mailing list
[email protected]
http://etherboot.org/mailman/listinfo/gpxe
_______________________________________________
gPXE mailing list
[email protected]
http://etherboot.org/mailman/listinfo/gpxe
