nightly testing 20060601

[William Cohen]

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