Re: Unable to boot Asus P5QL-EM w/ acpi enabled - FreeBSD

This is a discussion on Re: Unable to boot Asus P5QL-EM w/ acpi enabled - FreeBSD ; On Wed, Sep 17, 2008 at 11:46 PM, Jia-Shiun Li wrote: > The mainboard is an ASUS P5QL-EM (Intel G43/ICH10) with BIOS revision 0406. > > dmesg, pciconf, acpidump and kernel config file attached. > Files available at http://jiashiun.googlepages.com/p5ql-em_acpi.tar.gz Jia-Shiun. ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Re: Unable to boot Asus P5QL-EM w/ acpi enabled

  1. Re: Unable to boot Asus P5QL-EM w/ acpi enabled

    On Wed, Sep 17, 2008 at 11:46 PM, Jia-Shiun Li wrote:
    > The mainboard is an ASUS P5QL-EM (Intel G43/ICH10) with BIOS revision 0406.
    >
    > dmesg, pciconf, acpidump and kernel config file attached.
    >


    Files available at http://jiashiun.googlepages.com/p5ql-em_acpi.tar.gz

    Jia-Shiun.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/lis...reebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  2. Re: Unable to boot Asus P5QL-EM w/ acpi enabled

    On Thu, Sep 25, 2008 at 1:35 AM, John Baldwin wrote:
    > On Wednesday 24 September 2008 01:11:31 pm jiashiun li wrote:
    >>
    >> I did a binary search and found the problem lies between 2008-08-22
    >> and 2008-08-23. Here is my note:
    >>

    > If you grab the latest bits from HEAD you can use 'hw.pci.mcfg=0' to disable
    > memcfg.
    >


    Thanks, quick search the mailing list revealed some cases and your
    solution just a few days ago. I should have followed the mailing list
    more carefully.

    Just curious, any idea why the memory mapped configuration prevents
    kernel from booting? Maybe buggy hardware, acpi code, or combination
    of both that users can help testing to find the cause?

    Jia-Shiun.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/lis...reebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  3. Re: Unable to boot Asus P5QL-EM w/ acpi enabled

    "Jia-Shiun Li" wrote:

    > On Thu, Sep 25, 2008 at 1:35 AM, John Baldwin wrote:
    >> On Wednesday 24 September 2008 01:11:31 pm jiashiun li wrote:
    >>>
    >>> I did a binary search and found the problem lies between 2008-08-22
    >>> and 2008-08-23. Here is my note:
    >>>

    >> If you grab the latest bits from HEAD you can use 'hw.pci.mcfg=0' to disable
    >> memcfg.
    >>

    >
    > Thanks, quick search the mailing list revealed some cases and your
    > solution just a few days ago. I should have followed the mailing list
    > more carefully.
    >
    > Just curious, any idea why the memory mapped configuration prevents
    > kernel from booting? Maybe buggy hardware, acpi code, or combination
    > of both that users can help testing to find the cause?


    I had a similar problem with r181987 on the Intel DQ965GF desktop board
    (http://www.intel.com/products/deskto...f-overview.htm)
    1 or 2 weeks ago, and 'hw.pci.mcfg=0' helped to resolve the freeze on
    booting.

    Regards,
    loader
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/lis...reebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  4. Re: Unable to boot Asus P5QL-EM w/ acpi enabled

    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.

    The device at pci0:0:2:0 is the integrated graphics device on G43 chipset.

    dmesg when mcfg disabled:
    http://jiashiun.googlepages.com/mcfgdisabled.dmesg.txt
    enabled:
    http://jiashiun.googlepages.com/mcfgenabled.dmesg.txt

    The backtrace just before hanging:

    (kgdb) bt
    #0 pciereg_cfgread (bus=Variable "bus" is not available.
    ) at /freebsd-current/sys/i386/pci/pci_cfgreg.c:669
    #1 0xc07be7f4 in pci_docfgregread (bus=0, slot=Variable "slot" is not
    available.
    )
    at /freebsd-current/sys/i386/pci/pci_cfgreg.c:210
    #2 0xc07be874 in pci_cfgregread (bus=0, slot=2, func=0, reg=24, bytes=4)
    at /freebsd-current/sys/i386/pci/pci_cfgreg.c:232
    #3 0xc047e0ed in acpi_pcib_read_config (dev=0xc655c980, bus=0, slot=2, func=0,
    reg=24, bytes=4) at /freebsd-current/sys/dev/acpica/acpi_pcib_acpi.c:303
    #4 0xc04c5ac8 in pci_add_map (pcib=0xc655c980, bus=0xc6645080, dev=0xc6644e80,
    b=0, s=2, f=0, reg=24, rl=0xc659f404, force=0, prefetch=0) at pcib_if.h:40
    #5 0xc04c684b in pci_add_resources (bus=0xc6645080, dev=0xc6644e80, force=0,
    prefetchmask=0) at /freebsd-current/sys/dev/pci/pci.c:2549
    #6 0xc04c697d in pci_add_child (bus=0xc6645080, dinfo=0xc659f400)
    at /freebsd-current/sys/dev/pci/pci.c:2619
    #7 0xc04c86e3 in pci_add_children (dev=0xc6645080, domain=0, busno=0,
    dinfo_size=240) at /freebsd-current/sys/dev/pci/pci.c:2603
    #8 0xc047b7e8 in acpi_pci_attach (dev=0xc6645080)
    at /freebsd-current/sys/dev/acpica/acpi_pci.c:313
    #9 0xc058215f in device_attach (dev=0xc6645080) at device_if.h:178
    #10 0xc058311c in device_probe_and_attach (dev=0xc6645080)
    at /freebsd-current/sys/kern/subr_bus.c:2400
    #11 0xc05831f9 in bus_generic_attach (dev=0xc655c980)
    at /freebsd-current/sys/kern/subr_bus.c:2936
    #12 0xc047d814 in acpi_pcib_attach (dev=0xc655c980, prt=0xc6646234, busno=0)
    at /freebsd-current/sys/dev/acpica/acpi_pcib.c:170
    #13 0xc047e3b6 in acpi_pcib_acpi_attach (dev=0xc655c980)
    at /freebsd-current/sys/dev/acpica/acpi_pcib_acpi.c:243
    #14 0xc058215f in device_attach (dev=0xc655c980) at device_if.h:178
    #15 0xc058311c in device_probe_and_attach (dev=0xc655c980)
    at /freebsd-current/sys/kern/subr_bus.c:2400
    #16 0xc05831f9 in bus_generic_attach (dev=0xc660f400)
    at /freebsd-current/sys/kern/subr_bus.c:2936
    #17 0xc04732d6 in acpi_attach (dev=0xc660f400)
    at /freebsd-current/sys/dev/acpica/acpi.c:1557
    #18 0xc058215f in device_attach (dev=0xc660f400) at device_if.h:178
    ---Type to continue, or q to quit---
    #19 0xc058311c in device_probe_and_attach (dev=0xc660f400)
    at /freebsd-current/sys/kern/subr_bus.c:2400
    #20 0xc05831f9 in bus_generic_attach (dev=0xc655b180)
    at /freebsd-current/sys/kern/subr_bus.c:2936
    #21 0xc079070e in nexus_acpi_attach (dev=0xc655b180)
    at /freebsd-current/sys/i386/acpica/acpi_machdep.c:580
    #22 0xc058215f in device_attach (dev=0xc655b180) at device_if.h:178
    #23 0xc058311c in device_probe_and_attach (dev=0xc655b180)
    at /freebsd-current/sys/kern/subr_bus.c:2400
    #24 0xc058314b in root_bus_configure ()
    at /freebsd-current/sys/kern/subr_bus.c:3846
    #25 0xc079585c in configure (dummy=0x0)
    at /freebsd-current/sys/i386/i386/autoconf.c:112
    #26 0xc051d596 in mi_startup () at /freebsd-current/sys/kern/init_main.c:251
    #27 0xc0445dc5 in begin () at /freebsd-current/sys/i386/i386/locore.s:328
    (kgdb)

    Jia-Shiun.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/lis...reebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


+ Reply to Thread