From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: mvneta: oops in __rcu_read_lock on mirabox
Date: Wed, 18 Sep 2013 18:35:49 +0200 [thread overview]
Message-ID: <20130918183549.3e7b8f4c@skate> (raw)
In-Reply-To: <CACzLR4t2ABZdRk40VUhLtDKXX2PQiSVoQZQ4coQkNkvETnY6Rw@mail.gmail.com>
Dear Ethan Tuttle,
On Tue, 17 Sep 2013 23:30:56 -0700, Ethan Tuttle wrote:
> On Mon, Sep 16, 2013 at 11:01 PM, Willy Tarreau <w@1wt.eu> wrote:
> > Next step should be that you test both kernels to be sure.
>
> Thanks for the kernel images, Willy. I'm still experimenting but
> initial results are strange: I haven't seen a crash from the -ethan
> image you provided, nor by a kernel with that config that I built
> myself. The config is only different from my crashing config by a few
> options. So perhaps some combination of options prevents the crash.
> I'll see if I can narrow it down.
A toolchain generating some crappy code maybe? Ethan, Willy, comparing
your toolchain (compiler version, origin of the toolchain) could be
interesting.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Ethan Tuttle <ethan@ethantuttle.com>
Cc: "Willy Tarreau" <w@1wt.eu>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"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: Wed, 18 Sep 2013 18:35:49 +0200 [thread overview]
Message-ID: <20130918183549.3e7b8f4c@skate> (raw)
In-Reply-To: <CACzLR4t2ABZdRk40VUhLtDKXX2PQiSVoQZQ4coQkNkvETnY6Rw@mail.gmail.com>
Dear Ethan Tuttle,
On Tue, 17 Sep 2013 23:30:56 -0700, Ethan Tuttle wrote:
> On Mon, Sep 16, 2013 at 11:01 PM, Willy Tarreau <w@1wt.eu> wrote:
> > Next step should be that you test both kernels to be sure.
>
> Thanks for the kernel images, Willy. I'm still experimenting but
> initial results are strange: I haven't seen a crash from the -ethan
> image you provided, nor by a kernel with that config that I built
> myself. The config is only different from my crashing config by a few
> options. So perhaps some combination of options prevents the crash.
> I'll see if I can narrow it down.
A toolchain generating some crappy code maybe? Ethan, Willy, comparing
your toolchain (compiler version, origin of the toolchain) could be
interesting.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-18 16:35 UTC|newest]
Thread overview: 42+ 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 1:05 ` Ethan Tuttle
2013-09-15 18:57 ` Thomas Petazzoni
2013-09-15 18:57 ` Thomas Petazzoni
2013-09-16 6:50 ` Willy Tarreau
2013-09-16 6:50 ` Willy Tarreau
2013-09-16 8:56 ` Ethan Tuttle
2013-09-16 8:56 ` Ethan Tuttle
2013-09-16 15:51 ` Thomas Petazzoni
2013-09-16 15:51 ` Thomas Petazzoni
2013-09-16 16:22 ` Russell King - ARM Linux
2013-09-16 16:22 ` Russell King - ARM Linux
2013-09-16 16:24 ` Thomas Petazzoni
2013-09-16 16:24 ` Thomas Petazzoni
2013-09-16 17:14 ` Russell King - ARM Linux
2013-09-16 17:14 ` Russell King - ARM Linux
2013-09-16 17:45 ` Willy Tarreau
2013-09-16 17:45 ` Willy Tarreau
2013-09-16 18:25 ` Russell King - ARM Linux
2013-09-16 18:25 ` Russell King - ARM Linux
2013-09-16 16:35 ` Ethan Tuttle
2013-09-16 16:35 ` Ethan Tuttle
2013-09-16 16:39 ` Willy Tarreau
2013-09-16 16:39 ` Willy Tarreau
2013-09-16 16:44 ` Willy Tarreau
2013-09-16 16:44 ` Willy Tarreau
2013-09-16 17:24 ` Ethan Tuttle
2013-09-16 17:24 ` Ethan Tuttle
2013-09-16 17:47 ` Willy Tarreau
2013-09-16 17:47 ` Willy Tarreau
2013-09-16 18:28 ` Russell King - ARM Linux
2013-09-16 18:28 ` Russell King - ARM Linux
2013-09-17 3:43 ` Ethan Tuttle
2013-09-17 3:43 ` Ethan Tuttle
2013-09-17 6:01 ` Willy Tarreau
2013-09-17 6:01 ` Willy Tarreau
2013-09-18 6:30 ` Ethan Tuttle
2013-09-18 6:30 ` Ethan Tuttle
2013-09-18 16:35 ` Thomas Petazzoni [this message]
2013-09-18 16:35 ` Thomas Petazzoni
2013-09-18 16:49 ` Willy Tarreau
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=20130918183549.3e7b8f4c@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 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.