From owner-freebsd-current@FreeBSD.ORG Mon Nov 10 20:14:11 2008 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 4B5361065678 for ; Mon, 10 Nov 2008 20:14:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id C07C18FC0C for ; Mon, 10 Nov 2008 20:14:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id mAAKE4af066594; Mon, 10 Nov 2008 15:14:04 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Jia-Shiun Li" Date: Mon, 10 Nov 2008 11:32:26 -0500 User-Agent: KMail/1.9.7 References: <1d6d20bc0809170846g69311401j7f93f97969756e43@mail.gmail.com> <200809250835.36444.jhb@freebsd.org> <1d6d20bc0811080944k270c74d4p593d3a93547669ed@mail.gmail.com> In-Reply-To: <1d6d20bc0811080944k270c74d4p593d3a93547669ed@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811101132.27065.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 10 Nov 2008 15:14:04 -0500 (EST) X-Virus-Scanned: ClamAV 0.93.1/8599/Mon Nov 10 11:43:18 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org, Navdeep Parhar Subject: Re: Unable to boot Asus P5QL-EM w/ acpi enabled 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: Mon, 10 Nov 2008 20:14:11 -0000 On Saturday 08 November 2008 12:44:21 pm Jia-Shiun Li wrote: > On Thu, Sep 25, 2008 at 8:35 PM, John Baldwin wrote: > > > > I'm not sure. Probably other OS's aren't using this a lot yet so it is just > > buggy BIOS. Linux has a rather silly SMAP-related check (requires an > > explicit SMAP region that covers the memcfg area) that effectively disables > > memcfg on most boxes, so Linux probably isn't using it on your hardware > > either. > > I attached the board to firewire console. The system goes wrong at the > second PCIB_READ_CONFIG() of pci_add_map(). That's strange because the > first read and write to the BAR works. Try this. It ensures the PCI-e window is mapped UC (though MTRR's should already cover that in theory): --- //depot/user/jhb/acpipci/i386/pci/pci_cfgreg.c +++ /home/jhb/work/p4/acpipci/i386/pci/pci_cfgreg.c @@ -634,7 +634,7 @@ pmap_kremove(elem->vapage); invlpg(elem->vapage); } - pmap_kenter(elem->vapage, papage); + pmap_kenter_attr(elem->vapage, papage, PAT_UNCACHEABLE); elem->papage = papage; } -- John Baldwin