From: Baoquan He <bhe@redhat.com>
To: kkabe@vega.pgw.jp
Cc: bugzilla-daemon@bugzilla.kernel.org, akpm@linux-foundation.org,
richardw.yang@linux.intel.com, david@redhat.com,
mhocko@kernel.org, n-horiguchi@ah.jp.nec.com, linux-mm@kvack.org
Subject: Re: [Bug 206401] kernel panic on Hyper-V after 5 minutes duetomemory hot-add
Date: Fri, 14 Feb 2020 22:48:57 +0800 [thread overview]
Message-ID: <20200214144857.GA4816@MiWiFi-R3L-srv> (raw)
In-Reply-To: <200214232629.M0108877@vega.pgw.jp>
On 02/14/20 at 11:26pm, kkabe@vega.pgw.jp wrote:
> bhe@redhat.com sed in <20200213081941.GA19207@MiWiFi-R3L-srv>
>
> >> On 02/13/20 at 01:22pm, kabe@vega.pgw.jp wrote:
> >> > bhe@redhat.com sed in <20200212073123.GG8965@MiWiFi-R3L-srv>
> >> >
> >> > >> On 02/11/20 at 04:41pm, Andrew Morton wrote:
> >> > >> > On Tue, 11 Feb 2020 07:07:41 +0800 Wei Yang <richardw.yang@linux.intel.com> wrote:
> >> > >> >
> >> > >> > > On Mon, Feb 10, 2020 at 02:15:51PM +0800, Baoquan He wrote:
> >> > >> > > >On 02/10/20 at 02:09pm, Baoquan He wrote:
> >> > >> > > >> On 02/09/20 at 09:56pm, Andrew Morton wrote:
> >> > >> > > >> > On Mon, 10 Feb 2020 13:40:27 +0800 Baoquan He <bhe@redhat.com> wrote:
> >> > >> > > >> >
> >> > >> > > >> > > Hi Andrew,
> >> > >> > > >> > >
> >> > >> > > >> > > On 02/09/20 at 09:32pm, Andrew Morton wrote:
> >> > >> > > >> > > > On Tue, 04 Feb 2020 11:25:48 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> >> > >> > > >> > > >
> >> > >> > > >> > > > > https://bugzilla.kernel.org/show_bug.cgi?id=206401
> >> > >> > > >> > > > >
> >> > >> > > >> > > >
> >> > >> > > >> > > > An oops during mem hotadd. Could someone please take a look when
> >> > >> > > >> > > > convenient?
> >> > >> > > >> > >
> >> > >> > > >> > > This has been addressed by Wei Yang's patch, please check it here:
> >> > >> > > >> > >
> >> > >> > > >> > > http://lkml.kernel.org/r/20200209104826.3385-7-bhe@redhat.com
> >> > >> > > >> > >
> >> > >> > > >> >
> >> > >> > > >> > hm, OK, thanks. It's unfortunate that a 5.5 fix is buried in a
> >> > >> > > >> > six-patch series which is still in progress! Can we please merge that
> >> > >> > > >> > as a standalone fix with a cc:stable, Fixes:, etc?
> >> > >> > > >
> >> > >> > > >Maybe can add Fixes tag as follow when merge:
> >> > >> > > >
> >> > >> > > >Fixes: ba72b4c8cf60 ("mm/sparsemem: support sub-section hotplug")
> >> > >> > > >
> >> > >> >
> >> > >> > The reporter (cc'ed here) is still seeing issues:
> >> > >> > https://bugzilla.kernel.org/show_bug.cgi?id=206401
> >> > >> >
> >> > >> > Could we please continue this investigation via emailed reply-to-all,
> >> > >> > rather than via the bugzilla interface?
> >> > >>
> >> > >> Yes, people prefer mailing list to discuss issues.
> >> > >>
> >> > >> Hi T.Kabe,
> >> > >>
> >> > >> Could you provide the call trace again after below patch is applied?
> >> > >> The comment #9 in bugzilla is not very clear to me.
> >> > >>
> >> > >> mm/sparsemem: pfn_to_page is not valid yet on SPARSEMEM
> >> > >> http://lkml.kernel.org/r/20200209104826.3385-7-bhe@redhat.com
> >> > >>
> >> > >> And, as you said, applying above patch, and do not call
> >> > >> __free_pages_core() in generic_online_page() will work. I doubt it,
> >> > >> because without __free_pages_core(), your added pages are not added
> >> > >> into buddy for managing. I think we should make clear this problem
> >> > >> firstly, in order not to introduce new problem by improper work around,
> >> > >> then check next.
> >> > >>
> >> > >> Thanks
> >> > >> Baoquan
> >> >
> >> > Got it, I restarted off fresh from kernel-5.6-rc1,
> >> > applied patch
> >> > >> http://lkml.kernel.org/r/20200209104826.3385-7-bhe@redhat.com
> >> > and got the following panic.
> >> >
> >> > Diag printk's for add_memory() et al is not there, but I guess
> >> > memory hot-add request from hypervisor is returning "success",
> >> > corrupting something else and bombing out later.
> >> >
> >> >
> >> > [ 24.289967] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
> >> > [ 302.263730] hv_balloon: Max. dynamic memory size: 1048576 MB
> >> > [ 635.216014] BUG: unable to handle page fault for address: d13ff000
> >> > [ 635.216058] #PF: supervisor write access in kernel mode
> >> > [ 635.216076] #PF: error_code(0x0002) - not-present page
> >> > [ 635.216106] *pde = 00000000
> >>
> >> Thanks for the info. What ARCH is your system? Could you attach your
> >> kernel config and paste the output of executing 'readelf /proc/kcore'?
>
> Arch is i386(i586), non-PAE.
>
> I'll attach the "readelf -a /proc/kcore", dmesg and .config .
> The stack trace is different this time also;
> it seems to have slightly difference panic trace every time
> after handle_mm_fault().
Sorry, I didn't say it clearly. 'readelf -l /proc/kcore' is OK, and the
relevant call trace.
>
> I've temporary added pr_info() before and after add_memory() in hv_baloon.ko,
> so it says it's taining the kernel.
> add_memory() itself is returning 0 (success).
>
>
next prev parent reply other threads:[~2020-02-14 14:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-206401-27@https.bugzilla.kernel.org/>
[not found] ` <bug-206401-27-zYD8WfDKqD@https.bugzilla.kernel.org/>
2020-02-10 5:32 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes due to memory hot-add Andrew Morton
2020-02-10 5:40 ` Baoquan He
2020-02-10 5:56 ` Andrew Morton
2020-02-10 6:09 ` Baoquan He
2020-02-10 6:15 ` Baoquan He
2020-02-10 23:07 ` Wei Yang
2020-02-12 0:41 ` Andrew Morton
2020-02-12 7:31 ` Baoquan He
2020-02-12 8:21 ` David Hildenbrand
2020-02-13 4:22 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes due tomemory hot-add kabe
2020-02-13 8:19 ` Baoquan He
2020-02-14 14:26 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes duetomemory hot-add kkabe
2020-02-14 14:48 ` Baoquan He [this message]
2020-02-14 15:01 ` Baoquan He
2020-02-17 4:48 ` Baoquan He
2020-02-17 5:31 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes duetomemoryhot-add kkabe
2020-02-17 8:00 ` David Hildenbrand
2020-02-17 10:33 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes duetomemory hot-add Michal Hocko
2020-02-17 11:21 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes due to memory hot-add kkabe
2020-02-17 5:46 ` kkabe
2020-02-17 7:44 ` Baoquan He
2020-02-17 9:34 ` Oscar Salvador
2020-02-17 10:13 ` Baoquan He
2020-02-17 10:17 ` Baoquan He
2020-02-17 10:24 ` David Hildenbrand
2020-02-17 10:33 ` Baoquan He
2020-02-17 10:38 ` David Hildenbrand
2020-02-17 11:20 ` Baoquan He
2020-02-17 12:47 ` Michal Hocko
2020-02-18 6:24 ` kkabe
2020-02-18 8:47 ` Michal Hocko
2020-02-18 9:19 ` kkabe
2020-02-18 9:26 ` David Hildenbrand
2020-02-18 10:05 ` [RFC PATCH] memory_hotplug: disable the functionality for 32b (was: Re: [Bug 206401] kernel panic on Hyper-V after 5 minutes due to) " Michal Hocko
2020-02-18 10:11 ` David Hildenbrand
2020-02-19 3:23 ` Baoquan He
2020-02-19 21:46 ` Andrew Morton
2020-02-19 23:07 ` [RFC PATCH] memory_hotplug: disable the functionality for 32b Robin Murphy
2020-02-19 3:39 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes due to memory hot-add Baoquan He
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=20200214144857.GA4816@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=david@redhat.com \
--cc=kkabe@vega.pgw.jp \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=richardw.yang@linux.intel.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).