On 29 мая 2012 22:24:32 Adam Lackorzynski wrote:
Hi,
On Tue May 22, 2012 at 21:16:39 +0400, Timur wrote:
I had fixed the l4ankh driver and after that it started to work properly. Now only thread is used to receive packets. In lines 158-162 we clear the rcv buffer: that is necessary to be done as after opening a session we start to receive packets that should not be served; otherwise the response time will be quite slow. This is not the best solution, but I do not have time to make it better.
It's polling now, right?
Now I face the following problem: the driver in ankh (I use 8139cp) stops receiving packets after some time (for me it is usually 3-4 minutes). This situation occurs when the interrupt handler was called and the device register IntrStatus already equals "zero". An interrupt doesn't work after that.
Hm, just some quite generic hint, when you poll in this situation, are there any packets?
Adam
1) yes 2) at some moment (for me it's ~120 pings) i receive this message:
ankh | <6>NETDEV WATCHDOG: eth0 (8139cp): transmit timed out ankh | WARN():/l4re- snapshot-2011081207/src/l4/pkg/dde/linux26/lib/src/net/sched/sch_generic.c:230<4>eth0: Transmit timeout, status d 2b 15 80ff
and after that tcpdump shows that no packets passes through the device