From: Claudiu Manoil <claudiu.manoil@freescale.com>
To: "Thomas Hühn" <Thomas.Huehn@dai-labor.de>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Gianfar driver crashes in Kernel v3.10
Date: Fri, 4 Oct 2013 16:45:47 +0300 [thread overview]
Message-ID: <524EC68B.3090402@freescale.com> (raw)
In-Reply-To: <8EF35D6A-A132-458C-A3B4-80D4D2C5BA4C@dai-labor.de>
On 10/4/2013 3:03 PM, Thomas H=FChn wrote:
> Hi all,
>
> We are several Openwrt users based on the TPlink 4900 device and suffer=
from a crashing gianfar driver.
> We troubleshooted the problem down to the fact, that a 3.8er Linux kern=
el is working, and a v3.10 crashes, but there is
> no reproducable case yet.
I'll have some low traffic tests with the upstream 3.10 kernel on a
p1010rdb, but since you say there's no "reproducibility case" the crash
may not be easy to spot on my side. I wouldn't jump to conclusions
too fast, the fact that it manifests now doesn't neccesarily mean
that a bug was introduced between v3.8 and v3.10.
I'll let you know should I find something. Meanwhile, if you have
additional information about how to reproduce it, please share.
Thanks,
Claudiu
next prev parent reply other threads:[~2013-10-04 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 12:03 Gianfar driver crashes in Kernel v3.10 Thomas Hühn
2013-10-04 13:45 ` Claudiu Manoil [this message]
2013-10-08 22:09 ` Scott Wood
2013-10-11 9:17 ` Thomas Hühn
2013-10-11 17:49 ` Scott Wood
2013-10-11 17:49 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2013-10-04 12:28 Thomas Hühn
2013-10-10 11:07 ` Claudiu Manoil
2013-10-10 21:41 ` Scott Wood
2013-10-11 7:49 ` Claudiu Manoil
[not found] <90BE8C5D-E23B-41B5-BB52-8A0C0758931D@net.t-labs.tu-berlin.de>
2013-10-11 8:59 ` Fwd: " Thomas Hühn
2013-10-16 7:10 ` Claudiu Manoil
2013-10-16 12:44 ` Thomas Hühn
2013-10-31 11:51 ` Thomas Hühn
2013-11-01 11:51 ` Claudiu Manoil
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=524EC68B.3090402@freescale.com \
--to=claudiu.manoil@freescale.com \
--cc=Thomas.Huehn@dai-labor.de \
--cc=linuxppc-dev@lists.ozlabs.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 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).