From: Paul Burton <paul.burton@imgtec.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: <linux-next@vger.kernel.org>, Ralf Baechle <ralf@linux-mips.org>,
<linux-kernel@vger.kernel.org>, <linux-mips@linux-mips.org>
Subject: Re: Crash in -next due to 'MIPS: Move FP usage checks into protected_{save, restore}_fp_context'
Date: Mon, 27 Jul 2015 11:04:42 -0700 [thread overview]
Message-ID: <20150727180442.GG7289@NP-P-BURTON> (raw)
In-Reply-To: <20150727174622.GA10708@roeck-us.net>
On Mon, Jul 27, 2015 at 10:46:22AM -0700, Guenter Roeck wrote:
> On Mon, Jul 27, 2015 at 10:21:42AM -0700, Paul Burton wrote:
> > On Mon, Jul 27, 2015 at 08:06:52AM -0700, Guenter Roeck wrote:
> > > On Wed, Jul 15, 2015 at 09:09:18AM -0700, Guenter Roeck wrote:
> > > > Hi,
> > > >
> > > > my qemu test for mipsel crashes with next-20150715 as follows.
> > > >
> > > ping ... problem is still seen as of next-20150727.
> >
> > Hi Guenter,
> >
> > Apologies for the delay. Could you share your affected kernel
> > configuration & which userland you're running?
> >
> > I've just tested with a malta_defconfig kernel & a buildroot based
> > initramfs without problems, and things are also fine on my physical
> > MIPSr6 setups. If you have any directions with which I can reproduce
> > this problem that would be great.
> >
> This is with qemu in little endian mode. Big endian works fine.
Yup, I was using little endian in both cases. malta_defconfig is little
endian - sadly use of the el suffix is pretty inconsistent...
> The configuration, the script to build and run the kernel,
> and the root file system used are are available at
> https://github.com/groeck/linux-build-test, in directory
> rootfs/mipsel/. The log for the latest build failure is in
> http://server.roeck-us.net:8010/builders/qemu-mipsel-next/builds/194/steps/qemubuildcommand/logs/stdio.
Thanks for the pointers, I'm able to reproduce it using your config and
initramfs, and I'll dig into what's going on here.
Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Burton <paul.burton@imgtec.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-next@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: Crash in -next due to 'MIPS: Move FP usage checks into protected_{save, restore}_fp_context'
Date: Mon, 27 Jul 2015 11:04:42 -0700 [thread overview]
Message-ID: <20150727180442.GG7289@NP-P-BURTON> (raw)
Message-ID: <20150727180442.IOLwRsqlMzwKnMna13_go1zIViPCducBiPFXhBvvqfI@z> (raw)
In-Reply-To: <20150727174622.GA10708@roeck-us.net>
On Mon, Jul 27, 2015 at 10:46:22AM -0700, Guenter Roeck wrote:
> On Mon, Jul 27, 2015 at 10:21:42AM -0700, Paul Burton wrote:
> > On Mon, Jul 27, 2015 at 08:06:52AM -0700, Guenter Roeck wrote:
> > > On Wed, Jul 15, 2015 at 09:09:18AM -0700, Guenter Roeck wrote:
> > > > Hi,
> > > >
> > > > my qemu test for mipsel crashes with next-20150715 as follows.
> > > >
> > > ping ... problem is still seen as of next-20150727.
> >
> > Hi Guenter,
> >
> > Apologies for the delay. Could you share your affected kernel
> > configuration & which userland you're running?
> >
> > I've just tested with a malta_defconfig kernel & a buildroot based
> > initramfs without problems, and things are also fine on my physical
> > MIPSr6 setups. If you have any directions with which I can reproduce
> > this problem that would be great.
> >
> This is with qemu in little endian mode. Big endian works fine.
Yup, I was using little endian in both cases. malta_defconfig is little
endian - sadly use of the el suffix is pretty inconsistent...
> The configuration, the script to build and run the kernel,
> and the root file system used are are available at
> https://github.com/groeck/linux-build-test, in directory
> rootfs/mipsel/. The log for the latest build failure is in
> http://server.roeck-us.net:8010/builders/qemu-mipsel-next/builds/194/steps/qemubuildcommand/logs/stdio.
Thanks for the pointers, I'm able to reproduce it using your config and
initramfs, and I'll dig into what's going on here.
Paul
next prev parent reply other threads:[~2015-07-27 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:09 Crash in -next due to 'MIPS: Move FP usage checks into protected_{save, restore}_fp_context' Guenter Roeck
2015-07-27 15:06 ` Guenter Roeck
2015-07-27 17:21 ` Paul Burton
2015-07-27 17:21 ` Paul Burton
2015-07-27 17:46 ` Guenter Roeck
2015-07-27 18:04 ` Paul Burton [this message]
2015-07-27 18:04 ` Paul Burton
2015-07-27 18:17 ` Guenter Roeck
2015-07-27 19:44 ` Guenter Roeck
2015-07-27 20:02 ` Paul Burton
2015-07-27 20:02 ` Paul Burton
2015-07-27 20:41 ` Guenter Roeck
2015-07-28 8:31 ` Ralf Baechle
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=20150727180442.GG7289@NP-P-BURTON \
--to=paul.burton@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ralf@linux-mips.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.