From: "Figo.zhang" <figo1802@gmail.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Dick Hollenbeck <dick@softplc.com>,
netdev@vger.kernel.org, zealcook@gmail.com
Subject: Re: KS8695: possible NAPI issue
Date: Fri, 05 Mar 2010 21:52:17 +0800 [thread overview]
Message-ID: <1267797137.2576.11.camel@myhost> (raw)
In-Reply-To: <f69abfc31003050206h4f9ffe65s2b90e6acea014ec2@mail.gmail.com>
>
> and even if the fourth test succeeds, if I then send a file from other
> host the next ping or any other communication fails. I just tried to
> make some SSH sessions. It goes without a problem till I issue a ping
> after that.
>
> If I test the system with nuttcp I have no problem.
the network driver seems work well for system. the "netcat" application
is build in busybox? you can check busybox configure.
>
> Do you have any idea how to debug this? If I remove the NAPI support I
> have no problem with the same kernel and environment. I'd really like
> to get the whole stuff working.
>
> Regards,
> Yegor
next prev parent reply other threads:[~2010-03-05 13:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 12:04 KS8695: possible NAPI issue Yegor Yefremov
2010-03-02 14:09 ` Dick Hollenbeck
2010-03-03 1:46 ` figo zhang
2010-03-03 5:01 ` Dick Hollenbeck
2010-03-03 8:28 ` Yegor Yefremov
2010-03-04 10:10 ` Yegor Yefremov
2010-03-05 6:54 ` figo zhang
2010-03-05 10:06 ` Yegor Yefremov
2010-03-05 13:52 ` Figo.zhang [this message]
2010-03-05 15:03 ` Yegor Yefremov
2010-03-05 14:07 ` Figo.zhang
2010-03-05 15:00 ` Yegor Yefremov
2010-03-05 16:22 ` Stephen Hemminger
2010-03-06 2:40 ` Figo.zhang
2010-03-08 9:04 ` figo zhang
2010-03-08 14:10 ` Yegor Yefremov
2010-03-08 14:11 ` Yegor Yefremov
2010-03-09 1:50 ` figo zhang
2010-03-15 9:19 ` Yegor Yefremov
2010-08-04 14:40 ` Yegor Yefremov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1267797137.2576.11.camel@myhost \
--to=figo1802@gmail.com \
--cc=dick@softplc.com \
--cc=netdev@vger.kernel.org \
--cc=yegorslists@googlemail.com \
--cc=zealcook@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.