From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0726B385841C; Tue, 9 Jan 2024 12:11:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0726B385841C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704802273; bh=zASb/ZGlQoIf+2KhT2KP16s98vJxFIbgYiq5hkhXmUs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bAhudq0zfVMdOnDbtMQmMTaqKkXDcarn5liSZNP/Jp8GjveiTBkOq4s8kvSba9I5z XYNxIibOh1exUpp/Er/jkFqpvnTUlpgcDsP3sRrq3wMMQKGrhFj0d36EIlho79G58F gjlgQbA52+tCTf3s6kjG4iNd373bXowfgHy2WpKM= From: "mcermak at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/31117] transport failures Date: Tue, 09 Jan 2024 12:11:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: runtime X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mcermak at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31117 --- Comment #9 from Martin Cermak --- (In reply to William Cohen from comment #8) > However, there still seems to be drops > output in the tests. When running the syscall.exp testsuite multiple tim= es > see the PASS change to FAIL and vice versa from run to run. Maybe on > shutdown not all the output is getting flushed out. Agreed. E.g. the following is based on syscall testsuite artifacts: el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l WARNING: There were 0 lost messages and 2 lost bytes. 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l WARNING: There were 0 lost messages and 2 lost bytes. 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 4 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 0 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l WARNING: There were 0 lost messages and 2 lost bytes. 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 #=20 BUT ... I seem to see improvements when I put all the CPU cores offline but= the first one: el8 x86_64 # for i in `seq 1 23`; do echo 0 > /sys/devices/system/cpu/cpu$i/online; done el8 x86_64 # el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # staprun -R /tmp/syscall_longlonglong.ko -c /tmp/adjtimex | wc = -l 62 el8 x86_64 # --=20 You are receiving this mail because: You are the assignee for the bug.=