From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31117] transport failures
Date: Thu, 14 Dec 2023 20:23:43 +0000 [thread overview]
Message-ID: <bug-31117-6586-UukIc7LlDQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31117-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31117
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
I am able to see issues with the transport layer in a number of the systemtap
tests.
Looking through the systemtap.log There are a number of warnings. Another
example warning output below is from systemtap.maps/map_hash_SSI.stp failure
(which has a significant amount of output):
"WARNING: There were 2 transport failures. Try stap -s to increase the
buffer size from 16."
"WARNING: There were 0 lost messages and 14 lost bytes."
Frank mentioned that the problem might be tied to transferring data more than a
page (4096 bytes). Didn't see the issue when less than 4K, but then started
seeing it when size got to the 4K range.
Also saw cases where the lost messages counts looked questionable, such as the
one for clone:
clone: set_robust_list (0x7f54e661ba20, 24) = 0
clone: mprotect (0x7f54e67f2000, 16384, PROT_READ) = 0
clone: mprotect (0x7f54e68df000, 4096, PROT_READ) = 0
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=66: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=67: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=68: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=69: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=70: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=71: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=72: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=73: No data
available
stapio:reader_thread_serialmode:299: ERROR: unexpected sequence=74: No data
available
WARNING: There were 4294967284 lost messages and 0 lost bytes.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-12-14 20:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 15:39 [Bug runtime/31117] New: " mcermak at redhat dot com
2023-12-06 21:17 ` [Bug runtime/31117] " wcohen at redhat dot com
2023-12-13 21:27 ` mcermak at redhat dot com
2023-12-14 20:23 ` wcohen at redhat dot com [this message]
2023-12-18 18:55 ` wcohen at redhat dot com
2023-12-21 21:43 ` wcohen at redhat dot com
2024-01-04 22:34 ` wcohen at redhat dot com
2024-01-05 14:50 ` mcermak at redhat dot com
2024-01-05 15:21 ` mcermak at redhat dot com
2024-01-08 14:56 ` wcohen at redhat dot com
2024-01-09 12:11 ` mcermak at redhat dot com
2024-01-10 12:37 ` mcermak at redhat dot com
2024-01-22 15:54 ` wcohen at redhat dot com
2024-01-23 18:24 ` wcohen at redhat dot com
2024-02-02 15:07 ` mcermak at redhat dot com
2024-02-02 15:15 ` mcermak at redhat dot com
2024-02-05 15:32 ` wcohen at redhat dot com
2024-03-04 16:52 ` wcohen at redhat dot com
2024-03-04 21:30 ` wcohen 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-31117-6586-UukIc7LlDQ@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).