public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche 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: Wed, 19 Feb 2020 21:39:00 -0000	[thread overview]
Message-ID: <bug-22265-6586-nPJaThrH5S@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22265-6586@http.sourceware.org/bugzilla/>

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

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |fche at redhat dot com
         Resolution|---                         |WORKSFORME

--- Comment #4 from Frank Ch. Eigler <fche at redhat dot com> ---
The twenty.stp test is our most memory-hungry one.  On a modern box, seeing
such numbers:

stap -vuwp2 -e 'probe kernel.function("*") {} probe module("*").function("*")
{} probe kernel.function("*").call {} probe module("*").function("*").call {}
probe kernel.function("*").return {} probe module("*").function("*").return {}
probe kernel.function("*").inline {} probe module("*").function("*").inline {}'
> /dev/null
Pass 1: parsed user script and 505 library scripts using
373036virt/143836res/13180shr/130332data kb, in 250usr/40sys/291real ms.
Pass 2: analyzed script: 2722800 probes, 0 functions, 0 embeds, 0 globals using
6493280virt/6016040res/14220shr/6250576data kb, in 58160usr/3890sys/102443real
ms.

i.e., over 6 GB memory is used for probing every single function (+ all their
inlined copies) in the entire kernel.  That's very high, but note that it
doesn't even run any kernel module code.  So if the kernel has a problem, and
it doesn't signal this as an ordinary OOM, it's a kernel bug, not a stap one.

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

      parent reply	other threads:[~2020-02-19 21: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
2017-10-09 19:19 ` dsmith at redhat dot com
2020-02-19 21:39 ` fche at redhat dot com [this message]

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-nPJaThrH5S@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).