From: Ralf Baechle <ralf@linux-mips.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: THP broken on OCTEON?
Date: Mon, 23 May 2016 21:22:20 +0200 [thread overview]
Message-ID: <20160523192219.GB24125@linux-mips.org> (raw)
In-Reply-To: <5743529A.4070506@gentoo.org>
On Mon, May 23, 2016 at 02:57:30PM -0400, Joshua Kinard wrote:
> NAK, this issue looks completely different to IP30/IP27. In this case, it
> looks like the hardware is detecting the case where multiple TLB entries match
> and it's killing the machine to avoid hardware damage. I don't want to know
> how the SGI systems handle this scenario (does the R10000 do a TLB shutdown??).
The R10000 detects if duplicate entries when writing to the TLB and
invalidates the previous entry. That is, there will never be duplicate
entries in the TLB and of course no TLB shutdown.
That's the theory. I'm wondering how well that is going to work if
the entries are having a different page size.
And Aaro doesn't always get machine checks so it's not like always a
duplicate entry is written.
> On IP30, using THP usually results in instruction bus errors (IBE), after a set
> time, depending on the machine's configuration (<2GB RAM, virtually instant on
> userland init; >2GB RAM, might survive for a few minutes, even getting all the
> way to runlevel 3 randomly).
>
> IP27 was somewhat similar to IP30, in that THP usually results in IBEs after a
> few seconds of hitting userland bringup (bash is pretty quick at triggering an
> IBE), but I haven't tried experimenting with varying the amount of RAM in that
> machine, due to the fragility of pulling the nodeboards out constantly. I also
> haven't tried THP since refactoring/rewriting the IP27 code back in Feb to see
> if I magically fixed it...
Ralf
next prev parent reply other threads:[~2016-05-23 19:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 15:13 THP broken on OCTEON? Aaro Koskinen
2016-05-23 15:20 ` Ralf Baechle
2016-05-23 16:21 ` David Daney
2016-05-23 18:52 ` Aaro Koskinen
2016-05-23 19:03 ` David Daney
2016-05-23 19:03 ` David Daney
2016-05-23 19:08 ` Joshua Kinard
2016-05-23 20:02 ` Alastair Bridgewater
2016-05-23 18:57 ` Joshua Kinard
2016-05-23 19:22 ` Ralf Baechle [this message]
2016-05-23 19:40 ` Joshua Kinard
2016-05-23 20:01 ` Ralf Baechle
2016-05-24 21:21 ` Aaro Koskinen
2016-05-24 22:39 ` David Daney
2016-05-25 13:41 ` Aaro Koskinen
2016-05-26 9:33 ` Joshua Kinard
2016-05-26 13:36 ` Aaro Koskinen
2016-05-26 17:59 ` David Daney
2016-05-26 19:23 ` Aaro Koskinen
2016-05-26 22:13 ` David Daney
2016-05-27 17:14 ` Aaro Koskinen
2016-05-27 21:03 ` Joshua Kinard
2016-05-27 22:05 ` Aaro Koskinen
2016-05-27 22:22 ` Joshua Kinard
2016-06-22 22:05 ` David Daney
2016-06-23 12:08 ` Aaro Koskinen
2016-06-23 12:08 ` Aaro Koskinen
2016-06-24 11:38 ` Joshua Kinard
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=20160523192219.GB24125@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@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.