From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "Mao, Bibo" <bibo.mao@intel.com>, <systemtap@sources.redhat.com>
Subject: RE: summary nightly test 20060207 in smp IA32 platfrom
Date: Tue, 07 Feb 2006 21:07:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC0656CEA0@scsmsx403.amr.corp.intel.com> (raw)
Mao, Bibo wrote:
> Kernel: Linux 2.6.9-30.EL.root #1 SMP Mon Feb 6 14:30:00 CST 2006 i686
> i686 i386 GNU/Linux
>
> Stap translator summary of failed tests
> buildok-syscall.stp
>
> Testsuite summary of failed tests
> === systemtap Summary ===
> # of expected passes 127
> And system crashed when running systemtap.stress/current.stp script,
> the kernel version is latest RHEL4-U3 refresh kernel. And attachment
> is dump message.
This looks remarkably similar to the crash that I reported a few weeks
ago here:
http://sources.redhat.com/ml/systemtap/2006-q1/msg00157.html
I will file a bug report on this issue...
Josh
next reply other threads:[~2006-02-07 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 21:07 Stone, Joshua I [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 5:07 Mao, Bibo
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=CBDB88BFD06F7F408399DBCF8776B3DC0656CEA0@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=bibo.mao@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).