[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150520082848.GF26714@krava.redhat.com>
Date: Wed, 20 May 2015 10:28:48 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: lkml <linux-kernel@...r.kernel.org>, x86@...nel.org,
Robert Richter <rric@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [BUG] hard lockup on AMD server
On Wed, May 13, 2015 at 03:27:19PM +0200, Jiri Olsa wrote:
> On Wed, May 13, 2015 at 03:20:22PM +0200, Borislav Petkov wrote:
> > On Wed, May 13, 2015 at 03:11:46PM +0200, Jiri Olsa wrote:
> > > hi,
> > > I'm constantly getting hard lockups on single AMD server
> > > triggered just by kernel build.. make -j65
> > >
> > > I cannot reproduce on any other server, so I think this might
> > > be HW issue.. it's vanilla kernel v4.0 server with 64 CPUs:
> > >
> > > processor : 63
> > > vendor_id : AuthenticAMD
> > > cpu family : 21
> > > model : 2
> > > model name : AMD Eng Sample, ZS258045TGG54_34/25/20_2/16
> >
> > Yeah, first try reproducing that on an officially released CPU, not on
> > an engineering sample.
>
> yea.. I don't see it anywhere else
>
> just wanted to run it throught more eyes before I close it as HW issue ;-)
cured by latest microcode update.. sry for the noise
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists