Hi Siyuan,

Here is the log again. Looks like NOT_FOUND is being returned by DispatchDpc.
Thanx.


Shell> ping -n 1 172.25.17.100
Ping StartsAPing 172.25.17.100 16 data bytes
NicVfTransmit                                                     (ARP request)
NicVfGetPacket                                                   (ARP reply)
NicVfTransmit                                                      (Ping 
request)
NicVfGetPacket                                                    (Ping reply)
Ip4AccpetFrame EFI_IP_PROTO_ICMP
Ip4IcmpHandle ICMP_QUERY_MESSAGE
Ip4ProcessIcmpQuery Ip4Demultiplex
Ip4Demultiplex Ip4InterfaceEnquePacket
Ip4Demultiplex Ip4InterfaceEnquePacket
Ip4Demultiplex Ip4InterfaceDeliverPacket
Ip4InstanceDeliverPacket: Before SignalEvent
Ip4InstanceDeliverPacket: After SignalEvent 0x0
Ip4Demultiplex Ip4InterfaceDeliverPacket
Ip4AccpetFrame: Before DispatchDpc
Ip4AccpetFrame: After DispatchDpc 0x800000000000000E

1 packets transmitted, 0 received, 100% packet loss, time 0ms

From: siyuan...@intel.com
To: edk2-devel@lists.sourceforge.net; nd6...@hotmail.com
Subject: RE: [edk2] Missing Ping Reply
Date: Mon, 18 Aug 2014 06:14:08 +0000









Hi, Chris
 
Could you please help to check the return status of the gBS->SignalEvent and 
DispatchDpc (see attached patch file)?  Ping’s call back function
 should be invoked when IP4 driver calling SignalEvent or DispatchDpc (mostly 
after SingalEvent if you execute the ping command in EFI shell).
 
Best Regards,
Siyuan
 


From: Chris Cuthbert [mailto:nd6...@hotmail.com]


Sent: Sunday, August 17, 2014 11:14 AM

To: Edk2 Devel

Subject: [edk2] Missing Ping Reply


 

Hi All,

 


I am implementing a UEFI driver for a network controller and I am producing 
Simple Network Protocol(SNP). To test this, I am using the 'ping' shell 
command. The problem is that
 I never get the first ping reply. I have debugged this all the way up the IPv4 
stack and I can see that reply packet is being passed up but the first packet 
never reaches the 'ping' command. Logs below. From the ping source code it 
looks like it is creating
 an event to get a call back on reply packet and as part of the call back, it 
registers for event again if more replies are expected. But the first reply 
never kicks the call back function.


Any suggestions ?


Thanx.


 



Shell> ping -n 1 172.25.17.100


Ping StartsAPing 172.25.17.100 16 data bytes


NicVfTransmit                                                          (ARP 
request)


NicVfGetPacket                                                        (ARP 
reply)


NicVfTransmit                                                          (Ping 
packet)


NicVfGetPacket                                                        (Ping 
reply)


Ip4AccpetFrame EFI_IP_PROTO_ICMP                    (ICMP recognized)


Ip4IcmpHandle ICMP_QUERY_MESSAGE


Ip4ProcessIcmpQuery Ip4Demultiplex                    (Ip4Demultiplex function 
call)


Ip4Demultiplex Ip4InterfaceEnquePacket


Ip4Demultiplex Ip4InterfaceEnquePacket


Ip4Demultiplex Ip4InterfaceDeliverPacket


Ip4Demultiplex Ip4InterfaceDeliverPacket


 


1 packets transmitted, 0 received, 100% packet loss, time 0ms


 



                                          
------------------------------------------------------------------------------
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to