From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9A013385841E; Tue, 12 Mar 2024 18:16:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A013385841E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710267415; bh=Cq+ZXEUIP+wGGvbKTNeuG1oPMA0JyytnonacTWddIdA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=q06dH8woF37p/0wCe0MnMpbWaALOVAYptzN8TS41Xr1xOHMpCV5ubxW/canw85jED 4Ep93ZTrrnxtBe2Z5pwtr0PEdGNmkwOWrl6OZHucedNpECjZlhp5R1AqC8KS1N2duY 3dGKG6g4eybsJiv2d1ytHRZXRNodaPaDRvIloFWc= From: "wcohen at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/31472] systemtap.base/tracepoints.stp causes reboot with RHEL9 linux 5.14.0-428.el9.x86_64 Date: Tue, 12 Mar 2024 18:16:55 +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: wcohen 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: attachments.created 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=3D31472 --- Comment #3 from William Cohen --- Created attachment 15400 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D15400&action=3Ded= it smaller reproducer using just mmap_lock:* tracepoints for the reboot Took a look at the difference between the RHEL9 427 and 428 kernel tracepoi= nts. Suspected there was a set of tracepoints that were triggering the reboot in the RHEL9 428 kernel. With a pared down tracepoints.stp check which wildca= rd tracepoints were causing the problem. The following three tracepoints are causing the reboot on RHEL9 428 kernel: kernel.trace("mmap_lock:mmap_lock_acquire_returned") kernel.trace("mmap_lock:mmap_lock_released") kernel.trace("mmap_lock:mmap_lock_start_locking") Check f39 and fedora rawhide and they both have those tracepoints. Attempte= d to fedora 39 kernel-6.7.9-200.fc39.x86_64 and the reproducer ran with out issu= e. The reproduce also ran without issue on rawhide with kernel-6.8.0-0.rc7.20240308git3aaa8ce7a335.60.fc41.x86_64 Looks like the next step is to compare the difference between RHEL9 and f39/rawhide. --=20 You are receiving this mail because: You are the assignee for the bug.=