From: Michael Ellerman <mpe@ellerman.id.au>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: linux-mm@kvack.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Bad linux-next merge? (was Re: [6.4.0-rc7-next-20230620] Boot failure on IBM Power LPAR)
Date: Thu, 22 Jun 2023 22:54:42 +1000 [thread overview]
Message-ID: <87jzvvodwt.fsf@mail.lhotse> (raw)
In-Reply-To: <568F6E65-DBDF-43F2-8B3E-E783AE5A2B6C@linux.ibm.com>
Sachin Sant <sachinp@linux.ibm.com> writes:
>>> The problem was introduced in 6.4.0-rc7-next-20230619. I tried git bisect, but unsure of the
>>> result reported by it. Bisect points to following patch
>>>
>>> # git bisect bad
>>> 70c94cc2eefd4f98d222834cbe7512804977c2d4 is the first bad commit
>>> commit 70c94cc2eefd4f98d222834cbe7512804977c2d4
>>> Merge: 48f5ee5c48c3 3fe08f7d5e80
>>> Author: Stephen Rothwell <sfr@canb.auug.org.au>
>>> Date: Tue Jun 20 09:43:25 2023 +1000
>>>
>>> Merge branch 'mm-everything' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>>> # Conflicts:
>>> # mm/mmap.c
>>
>> Usually bisect pointing to a merge means something has gone wrong with
>> the bisect. It's not impossible for a merge to be the cause of a bug,
>> but IME it's rare.
>
> I have tried the bisect 3 times and the result was same. It always
> points to this merge commit.
>
> Is there anything else I can try to help debug this issue?
Looks like it's been reported, debugged and fixed over here:
https://lore.kernel.org/linux-next/20230619204309.GA13937@willie-the-truck/
So it should be resolved in today/tomorrow's linux-next hopefully.
cheers
prev parent reply other threads:[~2023-06-22 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 12:11 [6.4.0-rc7-next-20230620] Boot failure on IBM Power LPAR Sachin Sant
2023-06-20 19:34 ` Yu Zhao
2023-06-21 3:52 ` Michael Ellerman
2023-06-22 8:01 ` Sachin Sant
2023-06-22 12:54 ` Michael Ellerman [this message]
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=87jzvvodwt.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).