From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: huang ying <huang.ying.caritas@gmail.com>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Huang Ying <ying.huang@intel.com>
Subject: Re: kernel BUG at mm/swap_state.c:170!
Date: Mon, 22 Jul 2019 12:31:36 +0500 [thread overview]
Message-ID: <CABXGCsOo-4CJicvTQm4jF4iDSqM8ic+0+HEEqP+632KfCntU+w@mail.gmail.com> (raw)
In-Reply-To: <CAC=cRTMz5S636Wfqdn3UGbzwzJ+v_M46_juSfoouRLS1H62orQ@mail.gmail.com>
On Mon, 22 Jul 2019 at 06:37, huang ying <huang.ying.caritas@gmail.com> wrote:
>
> I am trying to reproduce this bug. Can you give me some information
> about your test case?
It not easy, but I try to explain:
1. I have the system with 32Gb RAM, 64GB swap and after boot, I always
launch follow applications:
a. Google Chrome dev channel
Note: here you should have 3 windows full of tabs on my
monitor 118 tabs in each window.
Don't worry modern Chrome browser is wise and load tabs only on demand.
We will use this feature later (on the last step).
b. Firefox Nightly ASAN this build with enabled address sanitizer.
c. Virtual Machine Manager (virt-manager) and start a virtual
machine with Windows 10 (2048 MiB RAM allocated)
d. Evolution
e. Steam client
f. Telegram client
g. DeadBeef music player
After all launched applications 15GB RAM should be allocated.
2. This step the most difficult, because we should by using Firefox
allocated 27-28GB RAM.
I use the infinite scroll on sites Facebook, VK, Pinterest, Tumblr
and open many tabs in Firefox as I could.
Note: our goal is 27-28GB allocated RAM in the system.
3. When we hit our goal in the second step now go to Google Chrome and
click as fast as you can on all unloaded tabs.
As usual, after 60 tabs this issue usually happens. 100%
reproducible for me.
Of course, I tried to simplify my workflow case by using stress-ng but
without success.
I hope it will help to make autotests.
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2019-07-22 7:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 4:05 kernel BUG at mm/swap_state.c:170! Mikhail Gavrilov
2019-05-29 17:32 ` Mikhail Gavrilov
2019-05-29 18:09 ` Michal Hocko
2019-05-29 19:28 ` Mikhail Gavrilov
2019-06-05 20:07 ` Mikhail Gavrilov
2019-06-11 3:59 ` Mikhail Gavrilov
2019-06-16 10:12 ` Mikhail Gavrilov
2019-06-17 12:17 ` Vlastimil Babka
2019-06-17 20:09 ` Mikhail Gavrilov
2019-06-30 21:15 ` Mikhail Gavrilov
2019-07-05 15:19 ` Mikhail Gavrilov
2019-07-05 23:03 ` Jan Kara
2019-07-06 2:39 ` Linus Torvalds
2019-06-17 12:47 ` Vlastimil Babka
2019-07-22 1:37 ` huang ying
2019-07-22 7:31 ` Mikhail Gavrilov [this message]
2019-07-22 7:52 ` Huang, Ying
2019-07-22 7:56 ` Mikhail Gavrilov
2019-07-23 5:08 ` Huang, Ying
2019-07-25 6:17 ` Mikhail Gavrilov
2019-07-25 7:14 ` Huang, Ying
2019-07-25 11:44 ` Matthew Wilcox
2019-07-26 3:20 ` Huang, Ying
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=CABXGCsOo-4CJicvTQm4jF4iDSqM8ic+0+HEEqP+632KfCntU+w@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ying.huang@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).