Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753259AbbFNPY0 (ORCPT ); Sun, 14 Jun 2015 11:24:26 -0400 Received: from mail-oi0-f43.google.com ([209.85.218.43]:36026 "EHLO mail-oi0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752183AbbFNPYR (ORCPT ); Sun, 14 Jun 2015 11:24:17 -0400 MIME-Version: 1.0 X-Originating-IP: [175.156.5.168] In-Reply-To: <1434293384.14412.1.camel@googlemail.com> References: <1434256796.1699.5.camel@googlemail.com> <1434293384.14412.1.camel@googlemail.com> Date: Sun, 14 Jun 2015 23:24:16 +0800 Message-ID: Subject: Re: lockup when C1E and high-resolution timers enabled From: Daniel J Blueman To: Christoph Fritz Cc: Linux Kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 802 Lines: 21 On 14 June 2015 at 22:49, Christoph Fritz wrote: > On Sun, 2015-06-14 at 15:54 +0800, Daniel J Blueman wrote: >> As a workaround, you can probably just disable message triggered C1E >> (see the BKDG p399 [1]): >> >> val=0x$(setpci -s 00:18.4 0xd4.l) # read D18F3xD4 > > mhm... $(setpci -s 00:18.4 0xd4.l) returns zero, this can't be right. Ahh, try: val=0x$(setpci -s 00:18.3 0xd4.l) # read D18F3xD4 val=$((val &~(1 << 13))) # clear bit13 (MTC1eEn) setpci -d 1022:1603 0xd4.l=$(printf %x $val) # write back -- Daniel J Blueman -- 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/