From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: mvneta: oops in __rcu_read_lock on mirabox
Date: Mon, 16 Sep 2013 18:44:12 +0200 [thread overview]
Message-ID: <20130916164412.GD3188@1wt.eu> (raw)
In-Reply-To: <20130916163937.GC3188@1wt.eu>
On Mon, Sep 16, 2013 at 06:39:37PM +0200, Willy Tarreau wrote:
> On Mon, Sep 16, 2013 at 09:35:16AM -0700, Ethan Tuttle wrote:
> > On Mon, Sep 16, 2013 at 8:51 AM, Thomas Petazzoni
> > <thomas.petazzoni@free-electrons.com> wrote:
> > > Willy, Ethan,
> > >
> > > On Mon, 16 Sep 2013 08:50:47 +0200, Willy Tarreau wrote:
> > >
> > >> I'm currently testing on 3.11.1 (which I had here) and am not getting
> > >> any issue after 50M packets. My kernel is running in thumb mode and
> > >> without SMP.
> > >>
> > >> Ethan, we'll need your config I guess.
> > >
> > > Can both of you also report the U-Boot version you're using, and the
> > > SoC revision (it's visible in the U-Boot output).
> >
> > Mine says:
> >
> > U-Boot 2009.08 (Sep 16 2012 - 22:50:06)Marvell version: 1.1.2 NQ
> > SoC: MV6710 A1
>
> I just checked on my old captures and I have the same here, with more
> details such as the CPU's revision (Rev 1) :
>
> http://1wt.eu/articles/mirabox-vs-guruplug/
BTW Ethan, I don't know if you have already opened your mirabox, but on the
link above you'll find settings for trying other frequencies for the CPU. It
could be nice to try 1 GHz with L2/DDR @500 instead of 1200/600 to see if the
issue remains or not. If it disappears, there's also a working setting with
CPU at 1.2G, L2 at 800M and DDR at 400M to help find if CPU, L2 or DDR is the culprit.
Willy
next prev parent reply other threads:[~2013-09-16 16:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 1:05 mvneta: oops in __rcu_read_lock on mirabox Ethan Tuttle
2013-09-15 18:57 ` Thomas Petazzoni
2013-09-16 6:50 ` Willy Tarreau
2013-09-16 8:56 ` Ethan Tuttle
2013-09-16 15:51 ` Thomas Petazzoni
2013-09-16 16:22 ` Russell King - ARM Linux
2013-09-16 16:24 ` Thomas Petazzoni
2013-09-16 17:14 ` Russell King - ARM Linux
2013-09-16 17:45 ` Willy Tarreau
2013-09-16 18:25 ` Russell King - ARM Linux
2013-09-16 16:35 ` Ethan Tuttle
2013-09-16 16:39 ` Willy Tarreau
2013-09-16 16:44 ` Willy Tarreau [this message]
2013-09-16 17:24 ` Ethan Tuttle
2013-09-16 17:47 ` Willy Tarreau
2013-09-16 18:28 ` Russell King - ARM Linux
2013-09-17 3:43 ` Ethan Tuttle
2013-09-17 6:01 ` Willy Tarreau
2013-09-18 6:30 ` Ethan Tuttle
2013-09-18 16:35 ` Thomas Petazzoni
2013-09-18 16:49 ` Willy Tarreau
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=20130916164412.GD3188@1wt.eu \
--to=w@1wt.eu \
--cc=linux-arm-kernel@lists.infradead.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).