Date: Thu, 14 Jun 2012 00:06:51 +0200
From: Borislav Petkov <bp@alien8.de>
To: Boszormenyi Zoltan <zboszor@pr.hu>
Cc: 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?
Message-ID: <20120613220651.GA12065@liondog.tnic>
Mail-Followup-To: Borislav Petkov <bp@alien8.de>,
	Boszormenyi Zoltan <zboszor@pr.hu>,
	Johannes Stezenbach <js@sig21.net>, linux-kernel@vger.kernel.org,
	Andreas Herrmann <andreas.herrmann3@amd.com>
References: <4FD4F45D.5050103@pr.hu>
 <20120611084318.GA1685@liondog.tnic>
 <20120611094905.GA10349@liondog.tnic>
 <20120611110557.GA4599@sig21.net>
 <4FD8417B.8020702@pr.hu>
 <20120613155733.GA17726@liondog.tnic>
 <4FD8DB3F.7050106@pr.hu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4FD8DB3F.7050106@pr.hu>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 888
Lines: 22

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 :-)

-- 
Regards/Gruss,
    Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/