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, 5 Mar 2010 14:54:44 +0800 [thread overview]
Message-ID: <c6ed1ac51003042254g27f65f9dhd9bd731e05a9518@mail.gmail.com> (raw)
In-Reply-To: <f69abfc31003040210i7e8a136am4b4a97306ba770cf@mail.gmail.com>
2010/3/4 Yegor Yefremov <yegorslists@googlemail.com>:
>>>> I'm using 2.6.33 kernel and I noticed such a strange behavior:
>>>>
>>>> after system start I transfer one file via netcat from my development
>>>> host, after this transfer the network is not functioning i.e. no pings
>>>> possible etc.
>>>>
>>>> To narrow down the problem I checked out this commit
>>>>
>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=451f14439847db302e5104c44458b2dbb4b1829d.
>>>> Till here the network driver is functioning as intended, but after
>>>> NAPI introduction I have this issue. With latest git-pull of "Linus'
>>>> kernel tree" I can't even ping right after the systems start.
>>>>
>>>> Any Ideas? What am I missing?
>>>>
>>>
>>> No idea, although I am using the same ARM chip, my kernel is at 2.6.30.5,
>>> and except for this occasional loss of connection I get, the ethernet driver
>>> seems to work better than what you are reporting.
>>
>> from linux-2.6.32, this ethernet driver have add NAPI support, would
>> you like to
>> try using this version?
>
> Figo, I just looked at the 2.6.32 kernel and found out that it
> doesn't' contain NAPI support (see the history
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=history;f=drivers/net/arm/ks8695net.c;h=2a7b7745cc55b54cefada690b0ea47865b54b6b9;hb=HEAD).
> So 2.6.33 is the first stable kernel to support NAPI.
>
> I made some further tests but I can't find the reason for network
> failures: the interrupts are coming and the packets will be received
> and sent so that rx/tx counters would be increased, but none of them
> seem to reach the IP stack. I don't know where and why the things get
> desynchronized.
>
> Could you try the 2.6.33 or Linus tree? Thank you in advance.
yes, i have test it on linux-2.6.33, it is work well.
next prev parent reply other threads:[~2010-03-05 6:54 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 [this message]
2010-03-05 10:06 ` Yegor Yefremov
2010-03-05 13:52 ` Figo.zhang
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=c6ed1ac51003042254g27f65f9dhd9bd731e05a9518@mail.gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).