From owner-freebsd-current@FreeBSD.ORG Thu Jan 15 23:10:35 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 00FD3106567B; Thu, 15 Jan 2009 23:10:35 +0000 (UTC) (envelope-from oz@nixil.net) Received: from nixil.net (nixil.net [161.58.222.1]) by mx1.freebsd.org (Postfix) with ESMTP id AFD7E8FC12; Thu, 15 Jan 2009 23:10:34 +0000 (UTC) (envelope-from oz@nixil.net) Received: from demigorgon.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by nixil.net (8.13.6.20060614/8.13.6) with ESMTP id n0FMqLKm057686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Jan 2009 15:52:28 -0700 (MST) Message-ID: <496FBE25.5000207@nixil.net> Date: Thu, 15 Jan 2009 15:52:21 -0700 From: Phil Oleson User-Agent: Thunderbird 2.0.0.14 (X11/20080623) MIME-Version: 1.0 To: John Baldwin References: <200812041421.53099.jhb@freebsd.org> <20081214.035113.104070918.Tor.Egge@cvsup.no.freebsd.org> <8D488E8F-BDEB-4384-9D64-48812E8DFC7B@baldwin.cx> <200901151642.35495.jhb@freebsd.org> In-Reply-To: <200901151642.35495.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (nixil.net [161.58.222.1]); Thu, 15 Jan 2009 15:52:29 -0700 (MST) X-Virus-Scanned: ClamAV version 0.94.2-exp, clamav-milter version 0.94.2-exp on nixil.net X-Virus-Status: Clean Cc: "yr.retarded@gmail.com" , "freebsd-current@freebsd.org" Subject: Re: lockup booting 8.0-CURRENT-200811 snap image 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: Thu, 15 Jan 2009 23:10:36 -0000 John Baldwin wrote: > On Tuesday 16 December 2008 10:18:16 am John Baldwin wrote: >> So the real fix is that we need to disable memory and I/O decoding int >> the PCI command register when messing with the BARs. One thing to be >> careful with is we can't do any console I/O (i.e. printfs) while the >> BAR is disabled. I will come up with a proper patch when I get back to >> a real computer. > > Please try this instead (compiled, but not run-tested): > I'll check out the patch tonight and let you know if it removes the need for hw.pci.mcfg=0. -Phil.