Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Greg McGary <greg@mcgary.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: do_page_fault crash on Indigo2
Date: Thu, 14 Sep 2000 03:35:00 +0200	[thread overview]
Message-ID: <20000914033500.A9395@bacchus.dhis.org> (raw)
In-Reply-To: <msk8cgsrz8.fsf@mcgary.org>; from greg@mcgary.org on Tue, Sep 12, 2000 at 11:53:15PM -0700

On Tue, Sep 12, 2000 at 11:53:15PM -0700, Greg McGary wrote:

> Here's the call trace.  I'm sure the symbol-table corresponds to the
> crashed system, but the trace looks bogus to me.  I should have a look
> at the call-trace dumping code in linux.  Since I have already written
> one of these things for an embedded system, I painfully aware that
> tracing the stack at runtime for MIPS is fraught with peril.

Backtracing a MIPS stack is tricky; this is about as good as it can get.

  Ralf

      reply	other threads:[~2000-09-14  1:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-12  1:07 do_page_fault crash on Indigo2 Greg McGary
2000-09-12  4:50 ` Greg McGary
2000-09-13  6:53 ` Greg McGary
2000-09-14  1:35   ` Ralf Baechle [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=20000914033500.A9395@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=greg@mcgary.org \
    --cc=linux-mips@oss.sgi.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