From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 4.16.16 (Fedora 27)
Date: Sun, 26 Aug 2018 06:27:00 -0000 [thread overview]
Message-ID: <bug-23493-6586-YqzJShhmkx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23493-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23493
--- Comment #7 from agentzh <agentzh at gmail dot com> ---
It seems like that the stuck usually happens after running
`uprobes_onthefly.exp` and/or `kprobes_onthefly.exp`. By checking the
`/proc/buddyinfo` output during the nearby time window, the fragmentation
becomes dramatically worse, for example:
```
$ cat /proc/buddyinfo
Node 0, zone DMA 0 0 0 0 2 1 1 0
1 1 3
Node 0, zone DMA32 14 23 27 27 23 12 17 16
9 4 739
Node 0, zone Normal 379 4113 3506 3803 2461 733 221 0
0 0 0
$ cat /proc/buddyinfo
Node 0, zone DMA 0 0 0 0 2 1 1 0
1 1 3
Node 0, zone DMA32 5 5 10 20 15 5 16 16
9 4 700
Node 0, zone Normal 344 1273 1414 1396 1047 473 143 0
0 0 0
```
Even though there's a lot of free memory in the system at the same times:
```
$ free -m
total used free shared buff/cache available
Mem: 11700 4897 3510 76 3293 5702
Swap: 2047 0 2047
```
I'm thinking about enforcing VM compaction every few minutes during the test
suite runs as a work around...
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-08-26 6:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:23 [Bug testsuite/23493] New: Test suite makes all CPU stuck forever on kernel 2.6.16 " agentzh at gmail dot com
2018-08-07 17:23 ` [Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 2.16.16 " agentzh at gmail dot com
2018-08-07 17:24 ` [Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 4.16.16 " agentzh at gmail dot com
2018-08-07 17:26 ` agentzh at gmail dot com
2018-08-07 17:42 ` agentzh at gmail dot com
2018-08-08 23:03 ` fche at redhat dot com
2018-08-10 18:41 ` agentzh at gmail dot com
2018-08-10 18:43 ` agentzh at gmail dot com
2018-08-10 18:50 ` agentzh at gmail dot com
2018-08-26 6:27 ` agentzh at gmail dot com [this message]
2018-08-29 1:20 ` agentzh at gmail dot com
2018-08-29 12:59 ` mark at klomp dot org
2018-08-29 17:47 ` agentzh at gmail dot com
2018-08-29 18:02 ` agentzh at gmail dot com
2020-02-20 14:26 ` fche at redhat dot com
2020-02-20 20:41 ` agentzh at gmail dot com
2023-05-25 16:35 ` fche at redhat dot com
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=bug-23493-6586-YqzJShhmkx@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).