linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Sachin Sant" <sachinp@linux.ibm.com>,
	"Mike Rapoport" <rppt@linux.ibm.com>
Cc: "linuxppc-dev" <linuxppc-dev@lists.ozlabs.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [6.1.0-rc3-next-20221104] Boot failure - kernel BUG at mm/memblock.c:519
Date: Wed, 09 Nov 2022 11:32:27 +0000	[thread overview]
Message-ID: <6e32f14ae25909138e40b2cfd7448ed8@linux.dev> (raw)
In-Reply-To: <74979021-D386-4402-BD70-167531C7405B@linux.ibm.com>

November 9, 2022 6:55 PM, "Sachin Sant" <sachinp@linux.ibm.com> wrote:

>> On 09-Nov-2022, at 3:55 PM, Yajun Deng <yajun.deng@linux.dev> wrote:
>> 
>> November 9, 2022 6:03 PM, "Yajun Deng" <yajun.deng@linux.dev> wrote:
>> 
>>> Hey Mike,
>> 
>> Sorry, this email should be sent to Sachin but not Mike.
>> Please forgive my confusion. So:
>> 
>> Hey Sachin,
>> Can you help me test the attached file?
>> Please use this new patch instead of the one in memblock tree.
> 
> Thanks for the fix. With the updated patch kernel boots correctly.
> 

Thanks for your test results.

Hi Mike,
Do you have any other suggestions for this patch? If not, I'll send a v3 patch.

> Tested-by: Sachin Sant <sachinp@linux.ibm.com <sachinp@linux.ibm.com>>
> 
> - Sachin


  parent reply	other threads:[~2022-11-09 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 12:07 [6.1.0-rc3-next-20221104] Boot failure - kernel BUG at mm/memblock.c:519 Sachin Sant
2022-11-08  2:27 ` Yajun Deng
2022-11-08  7:55   ` Mike Rapoport
2022-11-08  9:59   ` Yajun Deng
2022-11-09 10:03   ` Yajun Deng
2022-11-09 10:25   ` Yajun Deng
2022-11-09 10:55     ` Sachin Sant
2022-11-09 11:32     ` Yajun Deng [this message]
2022-11-09 11:42       ` Mike Rapoport
2022-11-09 11:48       ` Yajun Deng

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=6e32f14ae25909138e40b2cfd7448ed8@linux.dev \
    --to=yajun.deng@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rppt@linux.ibm.com \
    --cc=sachinp@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).