Re: Crash in -next due to 'MIPS: Add cacheinfo support'

[Florian Fainelli <f.fainelli@gmail.com>]

On 02/10/2017 09:46 AM, Guenter Roeck wrote:
> On Fri, Feb 10, 2017 at 10:39:52AM +0000, James Hogan wrote:
>> On Fri, Feb 10, 2017 at 09:40:11AM +0000, James Hogan wrote:
>>> Hi Guenter,
>>>
>>> On Thu, Feb 09, 2017 at 08:50:04PM -0800, Guenter Roeck wrote:
>>>> On 02/09/2017 04:01 PM, Justin Chen wrote:
>>>>> Hello Guenter,
>>>>>
>>>>> I am unable to reproduce the problem. May you give me more details?
>>>>>
>>>> The scripts I am using are available at
>>>>
>>>> https://github.com/groeck/linux-build-test/tree/master/rootfs
>>>>
>>>> in the mips and mipsel subdirectories (both crash). Individual
>>>> build logs are always available at kerneltests.org/builders,
>>>> in the 'next' column.
>>>
>>> Did you find it 100% reproducible? I was trying to reproduce yesterday
>>> evening, and did hit it a few times, but then it stopped happening
>>> before I could try and figure out what was going wrong.
>>
>> I switched to gcc 5.2 (buildroot toolchain) for building kernel, and now
>> it reproduces every time :)
>>
> gcc 5.4.0 (binutils 2.26.1) also reliably crashes. The exact crash depends on
> the kernel (-next is different to ToT + offending patch, qemu command line
> makes a difference, qemu version makes a difference), but the crash is easy
> to reproduce, at least for me.

Just to clarify here, is the crash a combination of:

- the kernel image, based on different trees/branches
- different GCC versions
- different ways of invoking QEMU/QEMU version?

and essentially Justin's commit just made problem 1) to occur, but is
not the root cause of the crash you are seeing?
-- 
Florian