netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Tuttle <ethan@ethantuttle.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "Willy Tarreau" <w@1wt.eu>, "Andrew Lunn" <andrew@lunn.ch>,
	"Jason Cooper" <jason@lakedaemon.net>,
	netdev@vger.kernel.org,
	"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>,
	"Gregory Clément" <gregory.clement@free-electrons.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: mvneta: oops in __rcu_read_lock on mirabox
Date: Mon, 16 Sep 2013 09:35:16 -0700	[thread overview]
Message-ID: <CACzLR4twTNjzU8hK3L1cYUXnEH1ydwY6jnYoOG+9vLB3-4uQ4w@mail.gmail.com> (raw)
In-Reply-To: <20130916175152.4e013457@skate>

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

> Maybe Globalscale is
> shipping Mirabox with a different version of the bootloader, or some
> hardware difference, that is causing problems? (I'm just speculating
> here, but another user already reported having issues with his Mirabox,
> and Russell King analyzed the oops as very likely being hardware
> problems).
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com

  parent reply	other threads:[~2013-09-16 16:35 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 [this message]
2013-09-16 16:39         ` Willy Tarreau
2013-09-16 16:44           ` Willy Tarreau
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=CACzLR4twTNjzU8hK3L1cYUXnEH1ydwY6jnYoOG+9vLB3-4uQ4w@mail.gmail.com \
    --to=ethan@ethantuttle.com \
    --cc=andrew@lunn.ch \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=w@1wt.eu \
    /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).