From: Johannes Stezenbach <js@sig21.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Boszormenyi Zoltan <zboszor@pr.hu>,
linux-kernel@vger.kernel.org,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: AMD FX CPU bug, not fixed by latest microcode?
Date: Mon, 11 Jun 2012 13:05:57 +0200 [thread overview]
Message-ID: <20120611110557.GA4599@sig21.net> (raw)
In-Reply-To: <20120611094905.GA10349@liondog.tnic>
On Mon, Jun 11, 2012 at 11:49:05AM +0200, Borislav Petkov wrote:
> On Mon, Jun 11, 2012 at 10:43:18AM +0200, Borislav Petkov wrote:
> > On Sun, Jun 10, 2012 at 09:24:13PM +0200, Boszormenyi Zoltan wrote:
> > > I have an AMD FX-8120 boxed CPU in an ASUS M5A99X-EVO mainboard
> > > with 32GB DDR3/1600 memory, running Fedora 17, upgraded from 16.
> > > memtest86+ show no problems.
>
> Ohe other thing: if there's an option in the BIOS to disable the IOMMU,
> can you do that and try reproducing the issue with IOMMU disabled?
Maybe not related, but I had bad memory in my Intel Core-i5
based system some months ago which resulted in rare crashes,
usually manifested itself as g++ ICEs when compiling a
mid-sized C++ project -- compiling a kernel with make -p4 showed
no problem. Also memtest86+ didn't show the issue,
so I tried memtest86-4.0a which claims to find more errors
due to SMP support. An overnight run left me with a screen
full of garbage and a crashed memtest86-4.0. I replaced
the RAM anyway and the box was stable since then.
memtest86-4.0a is at
http://memtest86.com/
The page claims:
With a single CPU it is not possible to drive multi-channel memory
controllers at full speed making it impossible to detect some types of errors
Maybe someone knowledgable could comment if this is true.
Johannes
next prev parent reply other threads:[~2012-06-11 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 19:24 AMD FX CPU bug, not fixed by latest microcode? Boszormenyi Zoltan
2012-06-11 7:52 ` Clemens Ladisch
2012-06-11 8:13 ` Boszormenyi Zoltan
2012-06-11 10:21 ` Clemens Ladisch
2012-06-11 10:57 ` Boszormenyi Zoltan
2012-06-11 8:43 ` Borislav Petkov
2012-06-11 9:49 ` Borislav Petkov
2012-06-11 11:05 ` Johannes Stezenbach [this message]
2012-06-13 7:30 ` Boszormenyi Zoltan
2012-06-13 15:57 ` Borislav Petkov
2012-06-13 18:26 ` Boszormenyi Zoltan
2012-06-13 22:06 ` Borislav Petkov
2012-06-14 4:23 ` Boszormenyi Zoltan
-- strict thread matches above, loose matches on Subject: below --
2012-06-11 3:45 Rus
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=20120611110557.GA4599@sig21.net \
--to=js@sig21.net \
--cc=andreas.herrmann3@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@pr.hu \
/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