linux-mips
[Top] [All Lists]

Re: oops in futex_init()

To: Manuel Lauss <mano@roarinelk.homelinux.net>
Subject: Re: oops in futex_init()
From: "Kevin D. Kissell" <kevink@paralogos.com>
Date: Wed, 29 Apr 2009 16:20:46 +0200
Cc: Ralf Baechle <ralf@linux-mips.org>, Linux-MIPS <linux-mips@linux-mips.org>
In-reply-to: <20090429141411.GA25905@roarinelk.homelinux.net>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20090428124645.GA14347@roarinelk.homelinux.net> <20090429060317.GB15627@linux-mips.org> <20090429082556.GA22844@roarinelk.homelinux.net> <20090429083349.GB26289@linux-mips.org> <20090429114042.GA24576@roarinelk.homelinux.net> <20090429141411.GA25905@roarinelk.homelinux.net>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Thunderbird 2.0.0.21 (Windows/20090302)
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.

<Prev in Thread] Current Thread [Next in Thread>