From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965060AbbEMN2P (ORCPT ); Wed, 13 May 2015 09:28:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59237 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934090AbbEMN2M (ORCPT ); Wed, 13 May 2015 09:28:12 -0400 Date: Wed, 13 May 2015 15:27:19 +0200 From: Jiri Olsa To: Borislav Petkov Cc: lkml , x86@kernel.org, Robert Richter , Peter Zijlstra , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner Subject: Re: [BUG] hard lockup on AMD server Message-ID: <20150513132719.GC25652@krava.redhat.com> References: <20150513131146.GB25652@krava.redhat.com> <20150513132022.GK1517@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150513132022.GK1517@pd.tnic> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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