Date: Sat, 15 Nov 2008 01:27:02 +0800 From: "Jia-Shiun Li" <jiashiun@gmail.com> To: "John Baldwin" <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, Navdeep Parhar <nparhar@gmail.com> Subject: Re: Unable to boot Asus P5QL-EM w/ acpi enabled Message-ID: <1d6d20bc0811140927p4a4e2aeaj2aa5d17892582d89@mail.gmail.com> In-Reply-To: <200811131146.59034.jhb@freebsd.org> References: <1d6d20bc0809170846g69311401j7f93f97969756e43@mail.gmail.com> <200811101132.27065.jhb@freebsd.org> <1d6d20bc0811130830k41160c8en5e145acbd4c2f7a0@mail.gmail.com> <200811131146.59034.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 14, 2008 at 12:46 AM, John Baldwin <jhb@freebsd.org> wrote: > On Thursday 13 November 2008 11:30:45 am Jia-Shiun Li wrote: >> On Tue, Nov 11, 2008 at 12:32 AM, John Baldwin <jhb@freebsd.org> wrote: >> > Try this. It ensures the PCI-e window is mapped UC (though MTRR's should >> > already cover that in theory): >> > >> >> It does not work. Still hang at the same place. Could this be related >> to specific device (the IGD)? > > I'm not really sure. I don't think it should matter to the end device since > the chipset is responsible (I think) for translating either type of config > space access into config transactions on the bus. Does an amd64 kernel work > fine with MCFG? > No. amd64 kernel hang at the same place. Jia-Shiun.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1d6d20bc0811140927p4a4e2aeaj2aa5d17892582d89>