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 19:47:08 +0200 [thread overview]
Message-ID: <20130916174708.GG3188@1wt.eu> (raw)
In-Reply-To: <CACzLR4ssOPsmYaEh2ohe4HL5j+67keDYnmR4YezNB=aO7Pj5kA@mail.gmail.com>
On Mon, Sep 16, 2013 at 10:24:05AM -0700, Ethan Tuttle wrote:
> I have not opened my mirabox - but sure, I'll open it up and try those
> other settings when I get a chance.
OK
> Also, you mentioned that you have SMP disabled in your kernel. It
> looks like it's on in my .config. Should I run a test with SMP
> disabled?
You may want to try but I wouldn't bet on this.
> I'm surprised that nobody else sees this crash given how easy it is
> for me to reproduce. BTW, the 3.11 kernel I made with 702821f
> reverted has been humming along for days without issue.
I'll have to rebuild with your config and exact 3.11 to test again.
Can you check the packet rate of your ping flood to give an order of
magnitude so that we're sure to be in the same conditions ?
Willy
next prev parent reply other threads:[~2013-09-16 17:47 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
2013-09-16 17:24 ` Ethan Tuttle
2013-09-16 17:47 ` Willy Tarreau [this message]
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=20130916174708.GG3188@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).