From mboxrd@z Thu Jan 1 00:00:00 1970 From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni) Date: Wed, 18 Sep 2013 18:35:49 +0200 Subject: mvneta: oops in __rcu_read_lock on mirabox In-Reply-To: References: <20130915205701.5c61a444@skate> <20130916065047.GH27487@1wt.eu> <20130916175152.4e013457@skate> <20130916163937.GC3188@1wt.eu> <20130916164412.GD3188@1wt.eu> <20130916174708.GG3188@1wt.eu> <20130916182807.GO12758@n2100.arm.linux.org.uk> <20130917060111.GB9325@1wt.eu> Message-ID: <20130918183549.3e7b8f4c@skate> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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 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