From owner-freebsd-current@FreeBSD.ORG Fri Jun 26 13:23:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E26FB1065670 for ; Fri, 26 Jun 2009 13:23:39 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE3B8FC12 for ; Fri, 26 Jun 2009 13:23:39 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from stasss.yandex.ru (dhcp170-227-red.yandex.net [95.108.170.227]) by mx0.deglitch.com (Postfix) with ESMTPSA id C182D8FC27; Fri, 26 Jun 2009 17:23:36 +0400 (MSD) Date: Fri, 26 Jun 2009 17:23:36 +0400 From: Stanislav Sedov To: Ian J Hart Message-Id: <20090626172336.985160df.stas@FreeBSD.org> In-Reply-To: <20090626123727.18824c9jkz72dw8w@10.248.192.16> References: <20090626123727.18824c9jkz72dw8w@10.248.192.16> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: AMD errata 169 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2009 13:23:40 -0000 On Fri, 26 Jun 2009 12:37:27 +0100 Ian J Hart mentioned: > I know I asked this before but I figure the long post may have put > some people off. > > #169 > http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25759.pdf > > I'd like to eliminate this as a cause of my problem > > It appears I can read the value. > > #kldload cpuctl > #cpucontrol -m 0xc001001f /dev/cpuctl0 > MSR 0xc001001f: 0x00400000 0x00100008 > > #cpucontrol -m 0xc001001f=0x0040000000100008 /dev/cpuctl0 > > Causes an nfe0 watchdog timeout and a powerdown failed, so that's > clearly a dumb thing to do. > > Would I be better off asking somewhere else? > Hi, Ian. Currently, it is not possible to atomically set the value of specific bits of MSR registers with cpuctl. I suspect this might be a problem, as the value of this MSR register could change between calls. Do you run stable or current? BTW, is there description of this NB_CFG MSR register somewhere on the net? I think that some bits of this register could have specific meaning and it is not safe to write them. -- Stanislav Sedov ST4096-RIPE