This is the mail archive of the systemtap@sources.redhat.com 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: Runtime probe example causes oops


Yes, the problem was my environtment. It was resolved.

Thanks, Hien.
Spirakis, Charles wrote:

Hien --

Was this ever resolved? Based on your comment:



I also tried the other probes under the probes directory and had same
results. I am going to do what you suggest to figure out what is going on.



Was it a problem with the your environment? Is there a problem with the
os_timer example that I need to take a look at?


-- charles




-----Original Message-----
From: Tom Zanussi [mailto:zanussi@us.ibm.com] Sent: Wednesday, July 13, 2005 2:52 PM
To: Hien Nguyen
Cc: Martin Hunt; systemtap@sources.redhat.com; Spirakis, Charles
Subject: Re: Runtime probe example causes oops


Hien Nguyen writes:
> Martin Hunt wrote:
>
> >os_timer was written by Charles. I hadn't really looked at it. It > >works fine on my Pentium M running RHEL4 with the latest patches. Well, > >it doesn't crash but the data it collects is not right. I'm a bit > >concerned that the oops shows it was in the runtime, but I cannot see > >how it could have crashed at that particular point. Do you always get > >the Oops? If so, could you try putting some printks in > >_stp_symbol_sprint() in sym.c? The Oops says >


_stp_symbol_print() called kallsyms_lookup() and that is

where it > >crashed. > >
> >Martin
> >
> >
> >
> >
> I also tried the other probes under the probes directory and had same > results. I am going to do what you suggest to figure out what is going on.


I'm not seeing any problems running the probes on my Debian system with a 2.6.13-rc2-mm1 kernel.

Tom










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