From: kr kr <kr-jiffy@yandex.ru>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [mips32r1 cpu] Advice needed: "Machine Check exception - caused by multiple matching entries in the TLB"
Date: Mon, 23 Jul 2012 21:22:28 +0400 [thread overview]
Message-ID: <189641343064148@web3g.yandex.ru> (raw)
In-Reply-To: <20120720091602.GA15546@linux-mips.org>
20.07.2012, 13:16, "Ralf Baechle" <ralf@linux-mips.org>:
> On Fri, Jul 13, 2012 at 12:03:25AM +0400, kr kr wrote:
>
>> [ 12.560000] Kernel panic - not syncing: Caught Machine Check exception - caused by multiple matching entries in the TLB.
>
> Running userland should never result in crashing the kernel except if
> programs directly touch I/O hardware an do stupid things or abuse their
> root priviledges..
>
> This type of crash specifically has in the past been produced by incorrect
> hazard barriers but also CPU hardware bugs so you may want to review the
> kernel code against a CPU datasheet and errata documentation. As always
> with hardware that is only supported out of tree we can't be too helpful ...
>
> Ralf
Ok, thank you.
But, in case of, say, Malta, we don't need to turn on (or turn off) some special CONFIG_* options in order to make it run MIPS-I binaries (which Debian provides), whereas MIPS32 binaries are native for the board?
Yuri
next prev parent reply other threads:[~2012-07-23 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 20:03 [mips32r1 cpu] Advice needed: "Machine Check exception - caused by multiple matching entries in the TLB" kr kr
2012-07-20 9:16 ` Ralf Baechle
2012-07-23 17:22 ` kr kr [this message]
2012-07-26 19:42 ` 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=189641343064148@web3g.yandex.ru \
--to=kr-jiffy@yandex.ru \
--cc=linux-mips@linux-mips.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox