From: Dmitry Malichenko <dmitryml@gmail.com>
To: systemtap@sourceware.org
Cc: wcohen@redhat.com
Subject: Re: some scripts from WarStories don't work on F10
Date: Tue, 10 Mar 2009 23:26:00 -0000 [thread overview]
Message-ID: <7e975d0b0903100730v2f1a1628y33ad0ceaebef2dbf@mail.gmail.com> (raw)
In-Reply-To: <49B18571.6030201@redhat.com>
Hi William,
I'm sorry for late reply.
On Fri, Mar 6, 2009 at 11:20 PM, William Cohen <wcohen@redhat.com> wrote:
> I went through the list below to see whether any of these scriopts listed had
> problems with the current F10 kernel and upcoming systemtap-0.9 rpms. This was
> run on a dual processor Intel Core 2 machine. It is possible that problems might
> be specific to the architecture being used. Which machine are these problems
> occuring on? i386? Uniprocessor or multiprocessor?
>
> $ uname -a
> Linux tandem 2.6.27.19-170.2.35.fc10.x86_64 #1 SMP Mon Feb 23 13:00:23 EST 2009
> x86_64 x86_64 x86_64 GNU/Linux
>
I use laptop IBM T42. It is uniprocessor 1.7 GHz
"uname -a" says:
Linux laptop-fedora 2.6.27.9-159.fc10.i686 #1 SMP Tue Dec 16 15:12:04
EST 2008 i686 i686 i386 GNU/Linux
>> * WSFunctionCallCount.stp
>> link --- http://sourceware.org/systemtap/wiki/WSFunctionCallCount?highlight=((WarStories))
>> problem: hangs system
>
> This systemtap script will run for 30 seconds before printing any output
> ("timer.ms(30000)"). Alternatively a control-C will cause the script to printout
> the data and exit earlier. Did the machine require a reboot to clear this? This
> script also ran without error on the test machine.
>
Yes, the machine requires a reboot. Script starts working, but prints
nothing and it hangs system immediately, mouse doesn't move. Sometimes
it's being rebooted by itself, sometimes it requires hard reboot from
me.
Thanks a lot,
Dmitry
prev parent reply other threads:[~2009-03-10 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 17:21 Dmitry Malichenko
2009-03-07 4:10 ` William Cohen
2009-03-10 23:26 ` Dmitry Malichenko [this message]
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=7e975d0b0903100730v2f1a1628y33ad0ceaebef2dbf@mail.gmail.com \
--to=dmitryml@gmail.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@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).