From: Boszormenyi Zoltan <zboszor@pr.hu>
To: Borislav Petkov <bp@alien8.de>,
Johannes Stezenbach <js@sig21.net>,
linux-kernel@vger.kernel.org,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: AMD FX CPU bug, not fixed by latest microcode?
Date: Thu, 14 Jun 2012 06:23:30 +0200 [thread overview]
Message-ID: <4FD96742.9090700@pr.hu> (raw)
In-Reply-To: <20120613220651.GA12065@liondog.tnic>
2012-06-14 00:06 keltezéssel, Borislav Petkov írta:
> On Wed, Jun 13, 2012 at 08:26:07PM +0200, Boszormenyi Zoltan wrote:
>> I did exactly that, the remaining two 8GB modules don't have faults
>> according to memtest86+ and the machine is stable with "make -j8" in
>> the kernel tree. Neither thunderbird nor firefox crashed for a day,
>> these are the usual victims when hitting the bad memory address.
> Cool.
>
> I guess you could try to limit it even further by taking a known-good
> 8GB module and pairing it with one of the "bad" ones to see whether one
> of the "bad" 8GB modules is faulty or both of them are.
>
> Or you could stop wasting time and go buy two new ones :-)
Yesterday I took the bad pair back to the shop with a screenshot
showing memtest86+ results and they accepted it for warranty.
I will get a new pair or RAMs for no extra fee.
next prev parent reply other threads:[~2012-06-14 4:23 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
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 [this message]
-- 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=4FD96742.9090700@pr.hu \
--to=zboszor@pr.hu \
--cc=andreas.herrmann3@amd.com \
--cc=bp@alien8.de \
--cc=js@sig21.net \
--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