Date: Mon, 10 Nov 2008 11:32:26 -0500 From: John Baldwin <jhb@freebsd.org> To: "Jia-Shiun Li" <jiashiun@gmail.com> Cc: freebsd-current@freebsd.org, Navdeep Parhar <nparhar@gmail.com> Subject: Re: Unable to boot Asus P5QL-EM w/ acpi enabled Message-ID: <200811101132.27065.jhb@freebsd.org> In-Reply-To: <1d6d20bc0811080944k270c74d4p593d3a93547669ed@mail.gmail.com> References: <1d6d20bc0809170846g69311401j7f93f97969756e43@mail.gmail.com> <200809250835.36444.jhb@freebsd.org> <1d6d20bc0811080944k270c74d4p593d3a93547669ed@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 08 November 2008 12:44:21 pm Jia-Shiun Li wrote:
> On Thu, Sep 25, 2008 at 8:35 PM, John Baldwin <jhb@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811101132.27065.jhb>