mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: "Kalyan" <kalyand@cruise-controls.com>
Cc: "ML-linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: wild pointer!!!!!
Date: Sun, 21 Oct 2001 22:21:40 +1000 (EST)	[thread overview]
Message-ID: <15314.48596.433523.34566@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <017f01c159b7$83943520$aac8a8c0@cruise>
In-Reply-To: <016a01c15831$ef51c5c0$5c044589@legato.com> <m33d4gjaoa.fsf@linux.local> <20011020171730.A28057@parallab.uib.no> <3BD28673.1060302@sap.com> <20011021120755.A1252@parallab.uib.no> <017f01c159b7$83943520$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....

What code base did you start from?  Linus' official 2.4.11-pre5
release, or the linuxppc_2_4_devel PPC development tree at
ppc.bkserver.net?  See http://www.penguinppc.org/dev/kernel.shtml for
details on how to access the PPC development tree.  That tree would
have the most up-to-date support for the MPC860T processor.

>         upon back tracing i found that at some point the kernel tries to
> execute code in Letext ( according to System.map)....

Hmmm, I don't know where that symbol would have come from, sorry.  It
doesn't appear anywhere in the kernel source that I can find.  Did you
add it?

>         it'd be great if someone can explain me what this Letext is and why
> is the control going there???

I suggest you ask on the linuxppc-dev@lists.linuxppc.org mailing list,
you will find other hackers working on Linux for MPC8xx processors
there.

Paul.

  parent reply	other threads:[~2001-10-21 12:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19  0:06 Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch David E. Weekly
2001-10-19  0:22 ` Davide Libenzi
2001-10-19  1:26   ` safemode
2001-10-19  5:12     ` Daniel T. Chen
2001-10-19  8:28 ` Christoph Rohland
2001-10-20 15:17   ` Jan-Frode Myklebust
2001-10-21  8:25     ` Christoph Rohland
2001-10-21 10:07       ` Jan-Frode Myklebust
2001-10-20 22:35         ` wild pointer!!!!! Kalyan
2001-10-21 12:15         ` Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch safemode
2001-10-21 12:21         ` Paul Mackerras [this message]
     [not found]         ` <E15vHVx-0001Nc-00@ii.uib.no>
2001-10-21 12:34           ` Jan-Frode Myklebust
2001-10-21 12:53             ` safemode
     [not found]             ` <E15vI6n-0001oC-00@ii.uib.no>
2001-10-21 13:10               ` bk regression fails on tmpfs /tmp, was: " Jan-Frode Myklebust
2001-10-21 13:36                 ` safemode
2001-10-21 16:35       ` Larry McVoy
2001-10-21 17:50         ` Linus Torvalds
2001-10-21 20:15           ` Daniel Phillips
2001-10-22 17:03           ` bill davidsen
2001-10-22 17:12             ` Larry McVoy
2001-10-22 17:29               ` Alexander Viro
2001-10-23  5:25               ` Keith Owens
2001-10-22  9:44         ` Christoph Rohland
2001-10-22 10:01           ` Alexander Viro
2001-10-30 17:29             ` Theodore Tso
2001-10-22 13:29           ` Wayne Scott
2001-10-22 17:31             ` bill davidsen

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=15314.48596.433523.34566@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=kalyand@cruise-controls.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®