From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, <linux-mips@linux-mips.org>
Subject: Re: Boot problems on Malta with EVA (bisected to 12220dea07f1 "mm/slab: support slab merge")
Date: Tue, 28 Oct 2014 13:19:16 +0000 [thread overview]
Message-ID: <544F97D4.4030408@imgtec.com> (raw)
In-Reply-To: <CAAmzW4NdBNhsPtx1yw+drN+J=a23SS3yLkgQdvQx-Giokwxu-Q@mail.gmail.com>
On 10/28/2014 01:01 PM, Joonsoo Kim wrote:
> 2014-10-28 19:45 GMT+09:00 Markos Chandras <Markos.Chandras@imgtec.com>:
>> Hi,
>>
>> It seems I am unable to boot my Malta with EVA. The problem appeared in
>> the 3.18 merge window. I bisected the problem (between v3.17 and
>> v3.18-rc1) and I found the following commit responsible for the broken boot.
>
> Hello,
>
> Did you start to bisect from v3.18-rc1?
> I'd like to be sure that this is another bug which is fixed by following commit.
>
> commit 85c9f4b04a08f6bc770b77530c22d04103468b8f
> Author: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Date: Mon Oct 13 15:51:01 2014 -0700
>
> mm/slab: fix unaligned access on sparc64
>
> This fix is merged into v3.18-rc1 sometime later that
> 'support slab merge' is merged.
>
> Thanks.
>
Hi,
I bisected from v3.17 until 3.18-rc1. But 3.18-rc2 and the latest
mainline (f7e87a44ef60ad379e39b45437604141453bf0ec) still have the same
problem
btw i did more tests and this is not EVA specific. A maltaup_defconfig
fails in the same way. I suspect all malta*_defconfigs will fail in a
similar way which makes it probably easier for you to reproduce it on a
QEMU.
--
markos
next prev parent reply other threads:[~2014-10-28 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 10:45 Boot problems on Malta with EVA (bisected to 12220dea07f1 "mm/slab: support slab merge") Markos Chandras
2014-10-28 13:01 ` Joonsoo Kim
2014-10-28 13:19 ` Markos Chandras [this message]
2014-10-28 13:24 ` Markos Chandras
2014-10-28 13:48 ` Joonsoo Kim
2014-10-28 14:21 ` Joonsoo Kim
2014-10-28 14:32 ` Markos Chandras
2014-10-28 15:00 ` Joonsoo Kim
2014-10-28 15:45 ` Markos Chandras
2014-10-28 16:00 ` Joonsoo Kim
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=544F97D4.4030408@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/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