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: systemtap crashed the kernel


FChE,

This issue turns to be a bnx2 driver issue and has
nothing to do with systemtap. 

But while I was working on the issue, I wonder how
systemtap protects global variables by concurrent multiple 
threads with multiple CPUs. For example, one probe would
call to "delete an array" while another or the same probe is trying
to read an element of this array at the same time. 

Any comments?

Thanks,
--
John Liang

-----Original Message-----
From: fche@redhat.com [mailto:fche@redhat.com] 
Sent: Tuesday, March 20, 2007 10:49 AM
To: John Liang
Cc: systemtap@sources.redhat.com
Subject: Re: systemtap crashed the kernel

"John Liang" <jliang@ibrix.com> writes:

> I consistently run into the following coredump while I have
> my script running to monitor NFS traffic. The core stack is 
> as following [...]

It seems not to include any systemtap-related code, interesting.
If you could gather other information requested by the
http://sources.redhat.com/systemtap/wiki/HowToReportBugs page,
it would help.

> I can reproduce this with "version 0.5.8 built 2006-07-14" and
> earlier version that comes with redhat 4 update 3. [...]

For what it's worth, a version labeled 0.5.10 was released for RHEL4U4.

- FChE


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