From: Balbir Singh <bsingharora@gmail.com>
To: vrbagal1 <vrbagal1@linux.vnet.ibm.com>,
Oscar Salvador <osalvador@techadventures.net>
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
linux-mm@kvack.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
nfont@linux.vnet.ibm.com,
Linuxppc-dev
<linuxppc-dev-bounces+vrbagal1=linux.vnet.ibm.com@lists.ozlabs.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [powerpc/powervm]kernel BUG at mm/memory_hotplug.c:1864!
Date: Tue, 12 Jun 2018 20:28:43 +1000 [thread overview]
Message-ID: <605b4df2-4cf1-2dda-3661-68b78845f8ec@gmail.com> (raw)
In-Reply-To: <0aac625ee724d877b87c69bba5ac9a0e@linux.vnet.ibm.com>
On 11/06/18 17:41, vrbagal1 wrote:
> On 2018-06-08 17:45, Oscar Salvador wrote:
>> On Fri, Jun 08, 2018 at 05:11:24PM +0530, vrbagal1 wrote:
>>> On 2018-06-08 16:58, Oscar Salvador wrote:
>>> >On Fri, Jun 08, 2018 at 04:44:24PM +0530, vrbagal1 wrote:
>>> >>Greetings!!!
>>> >>
>>> >>I am seeing kernel bug followed by oops message and system reboots,
>>> >>while
>>> >>running dlpar memory hotplug test.
>>> >>
>>> >>Machine Details: Power6 PowerVM Platform
>>> >>GCC version: (gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC))
>>> >>Test case: dlpar memory hotplug test (https://github.com/avocado-framework-tests/avocado-misc-tests/blob/master/memory/memhotplug.py)
>>> >>Kernel Version: Linux version 4.17.0-autotest
>>> >>
>>> >>I am seeing this bug on rc7 as well.
>
> Observing similar traces on linux next kernel: 4.17.0-next-20180608-autotest
>
> Block size [0x4000000] unaligned hotplug range: start 0x220000000, size 0x1000000
size < block_size in this case, why? how? Could you confirm that the block size is 64MB and your trying to remove 16MB
Balbir Singh.
next prev parent reply other threads:[~2018-06-12 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 11:14 [powerpc/powervm]kernel BUG at mm/memory_hotplug.c:1864! vrbagal1
2018-06-08 11:28 ` Oscar Salvador
2018-06-08 11:41 ` vrbagal1
2018-06-08 12:15 ` Oscar Salvador
2018-06-11 7:41 ` vrbagal1
2018-06-12 10:28 ` Balbir Singh [this message]
2018-06-26 14:54 ` Nathan Fontenot
2018-06-27 13:42 ` vrbagal1
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=605b4df2-4cf1-2dda-3661-68b78845f8ec@gmail.com \
--to=bsingharora@gmail.com \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev-bounces+vrbagal1=linux.vnet.ibm.com@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=osalvador@techadventures.net \
--cc=sachinp@linux.vnet.ibm.com \
--cc=vrbagal1@linux.vnet.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).