Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: "Kevin D. Kissell" <kevink@paralogos.com>,
	Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: oops in futex_init()
Date: Thu, 30 Apr 2009 13:23:06 +0200	[thread overview]
Message-ID: <20090430112305.GA12355@linux-mips.org> (raw)
In-Reply-To: <20090430104130.GA1878@roarinelk.homelinux.net>

On Thu, Apr 30, 2009 at 12:41:30PM +0200, Manuel Lauss wrote:

> This is really embarrassing:  The oops is what happens when you
> ioremap(0x10) and write 0xffffffff at the resulting address (0xa0000010).

That address is the TLB reload handler.  You just overwrote the TLB
exception hander.  0xffffffff is sd $31, -1($31) which is a MIPS III
that is 64-bit instruction which the Alchemy core duly honors with a
reserved instruction exception.  The handler is running with
c0_status.exl=1 so the EPC will point to the LL instruction but the
exception printed in the panic will be the 2nd exception.  Case closed,
I'd say.

  Ralf

      parent reply	other threads:[~2009-04-30 11:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 12:46 oops in futex_init() Manuel Lauss
2009-04-28 12:46 ` Manuel Lauss
2009-04-29  6:03 ` Ralf Baechle
2009-04-29  8:25   ` Manuel Lauss
2009-04-29  8:33     ` Ralf Baechle
2009-04-29 11:40       ` Manuel Lauss
2009-04-29 14:14         ` Manuel Lauss
2009-04-29 14:20           ` Kevin D. Kissell
2009-04-29 14:35           ` Ralf Baechle
2009-04-29 15:32             ` Manuel Lauss
2009-04-30 10:41               ` Manuel Lauss
2009-04-30 11:14                 ` Kevin D. Kissell
2009-04-30 11:22                   ` Manuel Lauss
2009-04-30 11:51                     ` Ralf Baechle
2009-04-30 11:23                 ` 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=20090430112305.GA12355@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kevink@paralogos.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    /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