From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: oops in futex_init()
Date: Wed, 29 Apr 2009 16:20:46 +0200 [thread overview]
Message-ID: <49F8623E.9010807@paralogos.com> (raw)
In-Reply-To: <20090429141411.GA25905@roarinelk.homelinux.net>
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).
By any chance would it be possible for you to revert to the failing
configuration and dump the contents of the TLB at the oops? Your
description makes it sound like the multiple ioremaps are generating
duplicate or otherwise conflicting TLB entries. If that's so, there's a
bug in the TLB management code to be hunted down and killed while we
have a test case...
Regards,
Kevin K.
next prev parent reply other threads:[~2009-04-29 14:20 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 [this message]
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
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=49F8623E.9010807@paralogos.com \
--to=kevink@paralogos.com \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.net \
--cc=ralf@linux-mips.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 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.