All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: oops in futex_init()
Date: Wed, 29 Apr 2009 16:35:23 +0200	[thread overview]
Message-ID: <20090429143523.GA10242@linux-mips.org> (raw)
In-Reply-To: <20090429141411.GA25905@roarinelk.homelinux.net>

On Wed, Apr 29, 2009 at 04:14:11PM +0200, Manuel Lauss wrote:

> FWIW, I think I fixed it: I have a small area (< 4kB) with a lot of UARTs
> and 3 interrupt controllers in it.  An ioremap() was done for each uart and
> irq ctl area.  Now there's one ioremap of the whole area and the oops is
> gone.  I don't know why, but it seems fixed. (The oops appeared after one
> of the remapped areas was touched).

That should be benign - especially if the mappings are for physical
addresses < 512MB which would become mapped as KSEG1 addresses.  The
dangerous cases are where multiple mappings alias (can't happen on
Alchemy caches) or where different machines use different cache modes
which also shouldn't hit you because I/O addresses should be mapped
uncachable.  So you may want to try out what Kevin suggested to get to
the root of this.

  Ralf

  parent reply	other threads:[~2009-04-29 14:35 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 [this message]
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

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=20090429143523.GA10242@linux-mips.org \
    --to=ralf@linux-mips.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.