Date: Wed, 23 Sep 2009 16:05:35 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: kama <kama@pvp.se> Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.2-STABLE boot freeze when calibrating clock. Message-ID: <4ABA1D1F.3080704@icyb.net.ua> In-Reply-To: <20090922215700.V37424@ns1.as.pvp.se> References: <20090921140345.H37424@ns1.as.pvp.se> <20090922103150.V37424@ns1.as.pvp.se> <4AB8A95E.3060307@icyb.net.ua> <20090922142526.P37424@ns1.as.pvp.se> <4AB8E082.8050100@icyb.net.ua> <20090922215700.V37424@ns1.as.pvp.se>
next in thread | previous in thread | raw e-mail | index | archive | help
on 23/09/2009 15:47 kama said the following: > g24# nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo > /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo > /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo So this is what I was talking about - this symbol should not be undefined after normal build. This symbol should not be present and referenced at all unless ACPI_DISASSEMBLER is defined. This is clearly a build problem of some sort. > Just adding 'device acpi' into the generic kernel made it boot > successfully. (without KDB DDB ACPI_DEBUG) I am glad that this worked :) > Here are the outputfiles suggested from the webpage: > > http://fbsd-err.pvp.se/acpidump_acpi_compiled.asl > http://fbsd-err.pvp.se/dmesg_acpi_compiled.txt > http://fbsd-err.pvp.se/sysctl_acpi_compiled.txt This doesn't make it nay clearer why you get that build problem. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ABA1D1F.3080704>