This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: nightly testing 20060601

From: William Cohen <wcohen at redhat dot com>
To: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
Cc: SystemTAP <systemtap at sources dot redhat dot com>
Date: Thu, 01 Jun 2006 15:10:13 -0400
Subject: Re: nightly testing 20060601
References: <CBDB88BFD06F7F408399DBCF8776B3DC0759AE2A@scsmsx403.amr.corp.intel.com>

Stone, Joshua I wrote:

On Thursday, June 01, 2006 9:30 AM, William Cohen wrote:

On RHEL4 i686 UP kernel the testsuite "scheduler_tick" test dies due
to a spinlock already be grabbed.

I assume this is systemtap.base/probefunc.exp?  Do you have any details
on the spinlock contention?

Josh

Yes, 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. The console had the following error messages:

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

Looking at linux/kernel/module.c:2114, it is a spin_lock_irqsave() in search_module_extables(). Not sure why it is getting stuck there.

-Will

References:
- RE: nightly testing 20060601
  - From: Stone, Joshua I

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]