From: "guanglei at cn dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2387] system crash on ppc64/2.6.15.4
Date: Wed, 01 Mar 2006 16:36:00 -0000 [thread overview]
Message-ID: <20060301163618.12906.qmail@sourceware.org> (raw)
In-Reply-To: <20060223094047.2387.guanglei@cn.ibm.com>
------- Additional Comments From guanglei at cn dot ibm dot com 2006-03-01 16:36 -------
(In reply to comment #4)
> If you are seen problem even when not using SystemTap the this is probably
> something outside of SystemTap. I suggest following this up on the linux-kernel
> and linuxppc64-dev mailing list to see if the problems is located in the kernel.
>
> We should mark this bug as rejected until its proven that it is a SystemTap
problem.
the error : end_request: I/O error, dev sda, sector 17445 ...
will happen without running systemtap. It will occur after I copied something
into that partition. But I am not sure if it is the reason of causing kernel
panic when running systemtap.
The error:
Unable to handle kernel paging request for data at address
will happed when running stap with -b option.
But I agree with Jose that it may not be a systemtap bug, because systemtap
could work quite well on the redhat shipped kernels(2.6.9-30.EL, 2.6.9-27.EL).
It should not be a hardware failure because I tried it on different machines,
and even after reformat the partition. all of them have the same error.
The 2.6.15 kernel has some changes about power arch(move ppc64 to powerpc
directory), and the relayfs diffs a lot from RH shipped kernel. I tried not to
compile relayfs in 2.6.15* and want systemtap compile it, but failed. the
relayfs shipped with systemtap can't be compiled. some function signatures has
changed, and if I have time I'll try to replace relayfs.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
http://sourceware.org/bugzilla/show_bug.cgi?id=2387
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-03-01 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 9:40 [Bug kprobes/2387] New: " guanglei at cn dot ibm dot com
2006-02-23 12:34 ` [Bug kprobes/2387] " fche at redhat dot com
2006-02-23 15:23 ` guanglei at cn dot ibm dot com
2006-03-01 14:41 ` guanglei at cn dot ibm dot com
2006-03-01 15:38 ` Frank Ch. Eigler
2006-03-01 16:25 ` jrs at us dot ibm dot com
2006-03-01 16:36 ` guanglei at cn dot ibm dot com [this message]
2006-03-01 16:56 ` zanussi at us dot ibm dot com
2006-03-02 5:08 ` zanussi at us dot ibm dot com
2006-03-02 5:36 ` guanglei at cn dot ibm dot com
2006-03-02 5:48 ` guanglei at cn dot ibm dot com
2006-03-02 5:53 ` zanussi at us dot ibm dot com
2006-03-02 5:58 ` guanglei at cn dot ibm dot com
2006-03-02 6:13 ` zanussi at us dot ibm dot com
2006-03-02 6:16 ` guanglei at cn dot ibm dot com
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=20060301163618.12906.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--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).