This is the mail archive of the mailing list for the systemtap project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/22265] on rawhide, we're getting a kernel panic

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

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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]