From: Caglar Akyuz <caglarakyuz@gmail.com>
To: cyril@ti.com
Cc: Michael Williamson <michael.williamson@criticallink.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 00/10] split out emac cpdma and mdio for reuse
Date: Mon, 13 Sep 2010 20:51:46 +0300 [thread overview]
Message-ID: <201009132051.46042.caglarakyuz@gmail.com> (raw)
In-Reply-To: <4C8E308B.7020003@ti.com>
On Monday 13 September 2010 05:09:15 pm Cyril Chemparathy wrote:
> Hi Caglar,
>
> [...]
>
> > Unfortunately emac driver is not stable after this series. I face
> > lock-ups time to time, followed by attached kernel trace.
>
> Could you elaborate on your test scenario so that I can try and
> reproduce the problem at my end? Also, did you have the contents of my
> commit stack in this particular kernel build?
>
Ooops! I didn't noticed your commits till you noted, I was working with
DaVinci head. Applying patches in your tree solves all my problems and all my
use cases are working now. However, I just barely tested them.
To make myself forgiven here are my 'netperf' numbers before and after your
patches applied:
TCP_STREAM : 54.64 Mbit vs 52.84 Mbit
UDP_STREAM : 96.27 Mbit vs 96.22 Mbit
Regards,
Caglar
> Assuming that the DMA got stuck at some point leading up to the transmit
> timeout, any ideas as to why a host error was not thrown? To help
> debug, I'll post out a set of patches that dump out the MAC (and DMA)
> registers on timeout. That should give us some visibility into the
> problem.
>
> > [ 1651.440000] nfs: server 192.168.2.34 not responding, still trying
> > [ 1859.010000] ------------[ cut here ]------------
> > [ 1859.010000] WARNING: at net/sched/sch_generic.c:258
> > dev_watchdog+0x184/0x294()
> > [ 1859.020000] NETDEV WATCHDOG: eth0 (davinci_emac): transmit queue 0
> > timed out
>
> [...]
>
> Regards
> Cyril.
>
next prev parent reply other threads:[~2010-09-13 17:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 20:25 [PATCH v3 00/10] split out emac cpdma and mdio for reuse Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 01/10] net: davinci_emac: separate out davinci mdio Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 02/10] davinci: add mdio platform devices Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 03/10] omap: " Cyril Chemparathy
2010-09-08 1:00 ` Tony Lindgren
2010-09-07 20:25 ` [PATCH v3 04/10] net: davinci_emac: switch to new mdio Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 05/10] davinci: cleanup unused davinci mdio arch code Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 06/10] omap: " Cyril Chemparathy
2010-09-08 1:00 ` Tony Lindgren
2010-09-07 20:25 ` [PATCH v3 07/10] net: davinci_emac: cleanup unused mdio emac code Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 08/10] net: davinci_emac: separate out cpdma code Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 09/10] net: davinci_emac: switch to new cpdma layer Cyril Chemparathy
2010-09-07 20:25 ` [PATCH v3 10/10] net: davinci_emac: cleanup unused cpdma code Cyril Chemparathy
2010-09-08 1:18 ` [PATCH v3 00/10] split out emac cpdma and mdio for reuse Kevin Hilman
2010-09-08 2:22 ` Michael Williamson
2010-09-08 21:59 ` Cyril Chemparathy
2010-09-09 0:47 ` Michael Williamson
2010-09-09 18:43 ` Michael Williamson
2010-09-09 19:51 ` Cyril Chemparathy
2010-09-09 21:24 ` Cyril Chemparathy
2010-09-09 21:45 ` Michael Williamson
2010-09-09 21:25 ` Michael Williamson
2010-09-10 15:23 ` Caglar Akyuz
2010-09-11 8:54 ` Caglar Akyuz
2010-09-13 14:09 ` Cyril Chemparathy
2010-09-13 15:46 ` Cyril Chemparathy
2010-09-13 17:51 ` Caglar Akyuz [this message]
2010-09-10 22:59 ` Cyril Chemparathy
2010-09-11 13:14 ` Michael Williamson
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=201009132051.46042.caglarakyuz@gmail.com \
--to=caglarakyuz@gmail.com \
--cc=cyril@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=michael.williamson@criticallink.com \
--cc=netdev@vger.kernel.org \
/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.