From: "lkml@tigusoft.pl" <lkml@tigusoft.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: 3.2.35 problem with M5A97 PRO ram: bad_page free_pages_prepare mem_init
Date: Wed, 09 Jan 2013 15:04:00 +0100 [thread overview]
Message-ID: <kcjtcf$iqd$1@ger.gmane.org> (raw)
In-Reply-To: <kcj877$d31$1@ger.gmane.org>
On 09/01/13 09:02, lkml@tigusoft.pl wrote:
> On 08/01/13 16:59, Borislav Petkov wrote:
>> On Tue, Jan 08, 2013 at 01:21:26AM +0100, lkml@tigusoft.pl wrote:
>>> On 08/01/13 01:13, lkml@tigusoft.pl wrote:
>>>
>>>> linux kernel
>>>> 3.2.0-0.bpo.4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.35-2~bpo60+1 x86_64
>>>> GNU/Linux
>>>
>>> will post later how it behaves on vanilla 3.2.36 and 3.7.1
>>
>> Yes, also, if your DRAM supports ECC, try enabling it in the BIOS.
>> This board should support ECC. Then, enable CONFIG_EDAC_AMD64 and
>> CONFIG_EDAC_DECODE_MCE to check whether it catches any DRAM errors.
>>
>> If your DRAM is non-ECC, try consecutively swapping out a DIMM each time
>> and booting to see whether removing one of the DIMMs makes the errors go
>> away.
>>
>> HTH.
>>
>
> Thank you;
> On vanilla 3.2.36 there is the same problem.
>
> Also problems happen on each boot so not random memory error, but I will
> try to swap rams, run memtest and so on.
Turned out it was just a hardware problem after all.
Solution is simply to try good memtest86 memory tester and swap out bad
chip.
Sorry for the trouble, thanks.
prev parent reply other threads:[~2013-01-09 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 0:13 3.2.35 problem with M5A97 PRO ram: bad_page free_pages_prepare mem_init lkml
2013-01-08 0:21 ` lkml
2013-01-08 15:59 ` Borislav Petkov
2013-01-09 8:02 ` lkml
2013-01-09 14:04 ` lkml [this message]
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='kcjtcf$iqd$1@ger.gmane.org' \
--to=lkml@tigusoft.pl \
--cc=linux-kernel@vger.kernel.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