linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	x86@kernel.org, Robert Richter <rric@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [BUG] hard lockup on AMD server
Date: Wed, 13 May 2015 15:27:19 +0200	[thread overview]
Message-ID: <20150513132719.GC25652@krava.redhat.com> (raw)
In-Reply-To: <20150513132022.GK1517@pd.tnic>

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

jirka

  reply	other threads:[~2015-05-13 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 13:11 [BUG] hard lockup on AMD server Jiri Olsa
2015-05-13 13:20 ` Borislav Petkov
2015-05-13 13:27   ` Jiri Olsa [this message]
2015-05-20  8:28     ` Jiri Olsa

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=20150513132719.GC25652@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rric@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).