public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22265] on rawhide, we're getting a kernel panic
Date: Mon, 09 Oct 2017 13:39:00 -0000	[thread overview]
Message-ID: <bug-22265-6586-hl7nhp8gHr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22265-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=22265

--- Comment #2 from David Smith <dsmith at redhat dot com> ---
(In reply to David Smith from comment #1)
> So, that test doesn't appear to be using a ton of memory.

Well, it looks like I was wrong.

If I remove testsuite/semok/twenty.stp, the entire testsuite will run to
completion. So, it is definitely semok/twenty.stp. What's odd of course is that
I can run semok/twenty.stp by itself with no problem.

I modified testsuite/systemtap.base/semok.exp to run "top" before each test.
Here's what I see right before trying to run twenty.stp:

====
top - 01:19:58 up  5:08,  0 users,  load average: 1.05, 1.25, 1.18
Tasks: 102 total,   1 running,  57 sleeping,   0 stopped,   0 zombie
%Cpu(s): 80.3 us, 10.2 sy,  0.0 ni,  8.9 id,  0.1 wa,  0.5 hi,  0.1 si,  0.0 st
KiB Mem :  4044076 total,  2474496 free,   284012 used,  1285568 buff/cache
KiB Swap:  3145724 total,  3145724 free,        0 used.  3425984 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
  852 root      20   0  184284  45968  11452 S  0.0  1.1   0:00.59 beah-beaker+
  864 root      20   0  179072  45144  11188 S  0.0  1.1   0:10.24 beah-rhts-t+
  849 root      20   0  167260  39216  11012 S  0.0  1.0   0:00.46 beah-srv
  850 root      20   0  151916  36756   9448 S  0.0  0.9   0:00.44 beah-fwd-ba+
  686 root      20   0  173460  33448  32332 S  0.0  0.8   0:00.17 sssd_nss
 8428 root      20   0   74640  25952   4544 S  0.0  0.6   0:11.79 expect
  453 root      20   0   97340  16836  16092 S  0.0  0.4   0:00.57 systemd-jou+
  557 root      20   0  599284  15512  12388 S  0.0  0.4   0:00.51 NetworkMana+
Running /root/src.copy/testsuite/semok/twenty.stp
====

That's a lot of memory & swap still available. I wonder if the bpf changes have
upped our memory requirements.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2017-10-09 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 16:10 [Bug runtime/22265] New: " dsmith at redhat dot com
2017-10-06 20:45 ` [Bug runtime/22265] " dsmith at redhat dot com
2017-10-09 13:39 ` dsmith at redhat dot com [this message]
2017-10-09 19:19 ` dsmith at redhat dot com
2020-02-19 21:39 ` 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-22265-6586-hl7nhp8gHr@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).