From owner-freebsd-current@FreeBSD.ORG Fri Jun 26 17:49:49 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 BA3F51065672 for ; Fri, 26 Jun 2009 17:49:49 +0000 (UTC) (envelope-from ianjhart@ntlworld.com) Received: from mtaout02-winn.ispmail.ntl.com (mtaout02-winn.ispmail.ntl.com [81.103.221.48]) by mx1.freebsd.org (Postfix) with ESMTP id 194D28FC18 for ; Fri, 26 Jun 2009 17:49:48 +0000 (UTC) (envelope-from ianjhart@ntlworld.com) Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090626174947.EXNY6611.mtaout02-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com>; Fri, 26 Jun 2009 18:49:47 +0100 Received: from cpc1-cove3-0-0-cust909.sol2.cable.ntl.com ([86.20.31.142]) by aamtaout03-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090626174947.LNSA2093.aamtaout03-winn.ispmail.ntl.com@cpc1-cove3-0-0-cust909.sol2.cable.ntl.com>; Fri, 26 Jun 2009 18:49:47 +0100 X-Virus-Scanned: amavisd-new at cpc2-cove3-0-0-cust311.sol2.cable.ntl.com Received: from localhost (localhost [127.0.0.1]) by cpc1-cove3-0-0-cust909.sol2.cable.ntl.com (8.14.3/8.14.3) with ESMTP id n5QHnR4w010385; Fri, 26 Jun 2009 18:49:27 +0100 (BST) (envelope-from ianjhart@cpc1-cove3-0-0-cust909.sol2.cable.ntl.com) Received: from gamma.private.lan (gamma.private.lan [192.168.0.12]) by webmail (Horde Framework) with HTTP; Fri, 26 Jun 2009 18:49:27 +0100 Message-ID: <20090626184927.14362wxz3wlpt7uo@webmail> Date: Fri, 26 Jun 2009 18:49:27 +0100 From: Ian J Hart To: rea-fbsd@codelabs.ru References: <20090626123727.18824c9jkz72dw8w@10.248.192.16> <20090626172336.985160df.stas@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.3.3 / FreeBSD-7.2 X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on cpc1-cove3-0-0-cust909.sol2.cable.ntl.com X-Cloudmark-Analysis: v=1.0 c=1 a=zd2uoN0lAAAA:8 a=6I5d2MoRAAAA:8 a=W-TzU-Rp0lDqUSCd37QA:9 a=SFbV6bLDp_4-bbShywYA:7 a=_YJTHXYjEhCJ-9tsQ-ZsFAyD72AA:4 a=SV7veod9ZcQA:10 Cc: Stanislav Sedov , freebsd-current@freebsd.org, Hart , Ian 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 17:49:50 -0000 Quoting Eygene Ryabinkin : > Fri, Jun 26, 2009 at 05:23:36PM +0400, Stanislav Sedov wrote: >> > 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. > > Hmm, if I am reading the thing properly, you're trying to set the > register to it's current value, aren't you? Yeah, I figured that was a safe test. If it worked my next question was 'which bit is bit 32, followed by how do I set DsNpReqLmt0?' Since this locked the primary network card, I guess I'm not going anywhere with this. > I would expect the final > value of MSR to be 0x00400001:0x00100008. And you should also set > F0x68[22:21] (Link Transaction Register) to 01b (one non-posted > downstream request). F0x68 means "configuration register 0x68, > function 0", so looks like you'll be playing with bus 0, device 24, > function 0, pci0:0:24:0 for the pciconf(8). > > By the way, here's what I got for my Asus M2NPV-VM: > ----- > $ cpucontrol -m 0xc001001f /dev/cpuctl0 > MSR 0xc001001f: 0x00400001 0x00000008 > > $ pciconf -r pci0:0:24:0 0x68 > 0f20c820 > ----- > As you can see, workaround for #169 is applied. > >> > Would I be better off asking somewhere else? > > You can try to look for BIOS update the implements the fix for #169, > but may be such version for your MB isn't available. As stated elsewhere later BIOS have the fix (which is how I know about it) but break other stuff. Thanks anyway, that was useful info. > >> BTW, is there description of this NB_CFG MSR register somewhere on the >> net? > > Google helps: > > http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/31116.pdf > >> I think that some bits of this register could have specific meaning >> and it is not safe to write them. > > Hmm, generally, yes, but in this case, bit 32 is reserved too, so > I would just try to left the current value of MSR untouched, but just > turn on the needed bits. > -- > Eygene > _ ___ _.--. # > \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard > / ' ` , __.--' # to read the on-line manual > )/' _/ \ `-_, / # while single-stepping the kernel. > `-'" `"\_ ,_.-;_.-\_ ', fsc/as # > _.-'_./ {_.' ; / # -- FreeBSD Developers handbook > {_.-``-' {_/ # > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- ian j hart -- ian j hart ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.