From: Paul Mackerras <paulus@samba.org>
To: "Kalyan" <kalyand@cruise-controls.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Wild Pointer!!!! ( some more info )
Date: Mon, 22 Oct 2001 21:41:20 +1000 (EST) [thread overview]
Message-ID: <15316.1504.603255.831736@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <03c101c15a76$7d067320$aac8a8c0@cruise>
Kalyan writes:
> I recently ported the linux kernel v 2.4.11-pre5 to MDPPro (
> MPC860T processor ) board..the kernel dies with an Oops and everytime at a
> different place.... i have taken the code from bitkeeper
The linuxppc_2_4 tree or the linuxppc_2_4_devel tree? Have you made
local changes? If so what are they?
> Call backtrace:
> C0014538 C0012314 C00121D4 C0011E14 C0003FAC C00026E0 C0003CF0
> C0003D04 C0002270 C00FC744 C0002138
Have you looked up these addresses in System.map? That could be
enlightening.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-10-22 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <03c101c15a76$7d067320$aac8a8c0@cruise>
2001-10-22 11:41 ` Paul Mackerras [this message]
2001-10-22 13:49 ` Wild Pointer!!!! ( some more info ) Wolfgang Denk
[not found] <20011022101239.K4933@cpe-24-221-152-185.az.sprintbbd.net>
2001-10-22 22:45 ` Wolfgang Denk
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=15316.1504.603255.831736@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=kalyand@cruise-controls.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 NNTP newsgroup(s).