linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <shy828301@gmail.com>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: kernel BUG at mm/huge_memory.c:2736(linux 5.10.29)
Date: Mon, 12 Apr 2021 13:18:27 -0700	[thread overview]
Message-ID: <CAHbLzkoyq88zkCdzNNy5tu=ac4Pw2srmbTeoWFHsTVRYdCeVew@mail.gmail.com> (raw)
In-Reply-To: <20210412180659.B9E3.409509F4@e16-tech.com>

On Mon, Apr 12, 2021 at 3:07 AM Wang Yugui <wangyugui@e16-tech.com> wrote:
>
> Hi,
>
> kernel BUG at mm/huge_memory.c:2736(linux 5.10.29) is triggered
> by some files write test.
>
> mm/huge_memory.c:
>         if (IS_ENABLED(CONFIG_DEBUG_VM) && mapcount) {
>             pr_alert("total_mapcount: %u, page_count(): %u\n",
>                     mapcount, count);
>             if (PageTail(page))
>                 dump_page(head, NULL);
>             dump_page(page, "total_mapcount(head) > 0");
> L2736:           BUG();
>         }

We just can tell the mapcount of the page is not zero from the current
log, it might mean the unmap_page() call is failed. It seems you have
CONFIG_DEBUG_VM enabled, could you please paste more log? There is
"VM_BUG_ON_PAGE(!unmap_success, page)" in unmap_page(). It should be
able to tell us if unmap_page() is failed or not, or something else
happened.

>
> kernel version:5.10.29
>
> kernel BUG at mm/huge_memory.c:2736
> invalid opcode: 0000 [#1] SMP NOPTI
> CPU:9 pid:351 Comm: kswapd0 Tainted: G S
> RIP: 0010:split_huge_page_to_list.cold.86+0x19/8x1b
> ...
> Call Trace:
> ? shrink_inactive_list+0x241/0x3d0
> deferred_split_scan+0x1ca/0x320
> do_shrink_slab+0x20f/0x2c0
> shrink_node+0x24b/0x6d0
> balanced_pgdat+0x2db/0x550
> kswaped+0x201/0x390
> ? finish_wait+0x80/0x80
> ? balance_pgdat+0x550/0x550
> kthread+0x116/0x130
> ? ktrhead_park+0x80/0x80
> ret_from_fork+0x1f/0x30
>
> see OOPS.jpg for more info.
>
> Best Regards
> Wang Yugui (wangyugui@e16-tech.com)
> 2021/04/12
>


  reply	other threads:[~2021-04-12 20:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 10:07 kernel BUG at mm/huge_memory.c:2736(linux 5.10.29) Wang Yugui
2021-04-12 20:18 ` Yang Shi [this message]
2021-04-13 11:30   ` Wang Yugui
2021-04-15 11:18     ` Wang Yugui
2021-04-15 16:26       ` Yang Shi
2021-04-17  8:33   ` Wang Yugui
2021-04-22  0:11     ` Yang Shi
2021-04-23  2:16       ` Wang Yugui
2021-04-23  8:07         ` Wang Yugui
2021-04-23 21:05           ` Yang Shi
2021-04-24  5:28             ` Wang Yugui
2021-04-26 22:56               ` Yang Shi
2021-04-28 21:55                 ` Wang Yugui

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='CAHbLzkoyq88zkCdzNNy5tu=ac4Pw2srmbTeoWFHsTVRYdCeVew@mail.gmail.com' \
    --to=shy828301@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=wangyugui@e16-tech.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).