linux-mips
[Top] [All Lists]

Re: [mips32r1 cpu] Advice needed: "Machine Check exception - caused by m

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [mips32r1 cpu] Advice needed: "Machine Check exception - caused by multiple matching entries in the TLB"
From: kr kr <kr-jiffy@yandex.ru>
Date: Mon, 23 Jul 2012 21:22:28 +0400
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1343064149; bh=ciB0e/Tov2bVNZ6oW4S1LZLVJTSmkpxKNVlkcWFi7pk=; h=From:To:Cc:In-Reply-To:References:Subject:MIME-Version:Message-Id: Date:Content-Transfer-Encoding:Content-Type; b=v5JT6S31us1gvPNHIMhRShXODqSt4WWsd7NILhsw5gHDUdh6LqK5iqszKvYoQ+Joi aw7tGZrMh9roTo3FDiss39JrV0F/sw3qFMTizo4+VNZpKJOJkz1h2GrFvOmi9ndump oXviv+7OSmNDVhk6Nx6JDOVdEhnOKtAdwrDLMTa8=
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1343064149; bh=ciB0e/Tov2bVNZ6oW4S1LZLVJTSmkpxKNVlkcWFi7pk=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=b6yBI0VBjeF9c1tgZTL6A6K6xh34b2NCjjPozLmTZBMmKYYBdNlt2CwH6wpWcr9ZB 1/LWJwcBKvs+LFZMDD2aswHMpk3C/7LNQi2x65AJc2s1gO9T+rORiBjiAdGH5g2RMi DCgOCPsj3PrDfyypPCVmO5vA/pijHj+3n8l3jcUo=
In-reply-to: <20120720091602.GA15546@linux-mips.org>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
References: <194011342123405@web6e.yandex.ru> <20120720091602.GA15546@linux-mips.org>
Sender: linux-mips-bounce@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

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