From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 775 invoked by alias); 1 Jun 2006 19:28:21 -0000 Received: (qmail 32766 invoked by uid 48); 1 Jun 2006 19:28:14 -0000 Date: Thu, 01 Jun 2006 19:28:00 -0000 From: "wcohen at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20060601192814.2726.wcohen@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug kprobes/2726] New: systemtap.base/probefunc.exp crash in kernel/module.c:2114 on RHEL4 X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q2/txt/msg00528.txt.bz2 When running the systemtap testsuite on a RHEL4 machine with the 2.6.9-37.EL kernel, the systemtap.base/probesfunc.exp crashes the machine with the following message on the console: Linux slingshot.devel.redhat.com 2.6.9-37.EL #1 Fri May 19 17:55:44 EDT 2006 i686 athlon i386 GNU/Linux Kernel panic - not sync: kernel/module.c:2114: spin_lock(kernel/module.c:c036b280) already locked by kernel/module.c:2114 Badness in panic at kernel/panic.c:118 systemtap.base/probefunc.exp definitely causes the crash when trying to probe kernel.function("scheduler_tick"). I don't have a great deal of details about the failure on the RHEL4 UP kernel. There wasn't a traceback or oops on the screen. -- Summary: systemtap.base/probefunc.exp crash in kernel/module.c:2114 on RHEL4 Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: kprobes AssignedTo: systemtap at sources dot redhat dot com ReportedBy: wcohen at redhat dot com GCC target triplet: i386-linux http://sourceware.org/bugzilla/show_bug.cgi?id=2726 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.