public inbox for
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <>
Subject: [Bug runtime/29108] New: persistent intermittent bufhdr-corruption / transport-failures, even with large -s
Date: Sun, 01 May 2022 14:39:31 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 29108
           Summary: persistent intermittent bufhdr-corruption /
                    transport-failures, even with large -s
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: fche at redhat dot com
  Target Milestone: ---

# stap -b -s400 -e 'probe syscall.* { println(name, argstr) }' -c 'sleep 30'

Even with 400MB of buffers per cpu, we can get a handful of transport failures.
 This phenomenon appears to be affecting the syscalls* testsuite.

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

             reply	other threads:[~2022-05-01 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 14:39 fche at redhat dot com [this message]
2022-05-02 13:11 ` [Bug runtime/29108] " fche at redhat dot com
2023-07-31 18:11 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).