Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755562AbbHFSKt (ORCPT ); Thu, 6 Aug 2015 14:10:49 -0400 Received: from mga14.intel.com ([192.55.52.115]:52258 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753324AbbHFSKr convert rfc822-to-8bit (ORCPT ); Thu, 6 Aug 2015 14:10:47 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,624,1432623600"; d="scan'208";a="763444022" From: "Liang, Kan" To: Matthew Leach , Ingo Molnar CC: "linux-kernel@vger.kernel.org" , "linux-ia64@vger.kernel.org" , "eranian@google.com" , "'Andi Kleen'" , "'Bjorn Helgaas'" , "'Vince Weaver'" , "'Peter Zijlstra'" , "'Sonny Rao'" Subject: RE: [BUG]: Intel uncore boot warning introduced in 4.1 Thread-Topic: [BUG]: Intel uncore boot warning introduced in 4.1 Thread-Index: AQHQ0DQDWimE4aNdy0203FBuIqvjX53/JUDlgAAZuZA= Date: Thu, 6 Aug 2015 18:10:40 +0000 Message-ID: <37D7C6CF3E00A74B8858931C1DB2F077018D32C2@SHSMSX103.ccr.corp.intel.com> References: <1438853676.3139.20.camel@mattleach.net> <87bneko0o5.fsf@mattleach.net> In-Reply-To: <87bneko0o5.fsf@mattleach.net> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1848 Lines: 60 > > Hi Ingo, > > Matthew Leach writes: > > [...] > > > I've bisected the kernel and found that commit [2] seems to introduce > > the warning message. I have checked on a v4.2-rc5 kernel and the > > warning message is still there. > > [...] > > > [2]: 8cf1a3de97804b047973dd44cfacdc1930da8403 > > Apologies, I got it wrong. The commit that is causing the issue is [1]. > If I revert it, the warning goes away. I'm also testing to see if this is the > cause of the random freezing that occurs (which I can confirm is also > happening with v4.2-rc5). > > [1]: 15c1247953e8a45232ed5a5540f291d2d0a77665 > The issue may be caused by uncore box initialization. For preventing the potential issues of uncore box initialization, I once moved the uncore_box_init() out of driver initialization in commit c05199e5a57a579fea1e8fa65e2b511ceb524ffc. However, it cause some desktop crash, because the box initialization codes were moved in IPI context. For fixing the crash issue, we had two choice at that time. - Simply revert the codes. That's where is 15c1247953e8a45232ed5a5540f291d2d0a77665 from. - Move uncore_box_init out of IPI context to uncore event init. I provided a patch for it. https://lkml.org/lkml/2015/4/28/21 Stephane Eranian also verified it on his platform At that time, we chose first option. But it looks there is some issue now. I guess we may try the second option this time. Matthew, Could you please revert 15c1247953e8a45232ed5a5540f291d2d0a77665 and apply the patch https://lkml.org/lkml/2015/4/26/294? See if it works? Thanks, Kan -- 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/