From: William Cohen <wcohen@redhat.com>
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: nightly testing 20060601
Date: Thu, 01 Jun 2006 19:10:00 -0000 [thread overview]
Message-ID: <447F3B95.4040303@redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2006-06-01 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 18:15 Stone, Joshua I
2006-06-01 19:10 ` William Cohen [this message]
2006-06-01 19:29 ` William Cohen
-- strict thread matches above, loose matches on Subject: below --
2006-06-01 17:44 William Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=447F3B95.4040303@redhat.com \
--to=wcohen@redhat.com \
--cc=joshua.i.stone@intel.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).