Date: Wed, 23 Sep 2009 18:57:50 +0300 From: Andriy Gapon <avg@freebsd.org> 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: <4ABA457E.3060800@freebsd.org> In-Reply-To: <20090923171004.Q37424@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> <4ABA1D1F.3080704@icyb.net.ua> <20090923171004.Q37424@ns1.as.pvp.se>
next in thread | previous in thread | raw e-mail | index | archive | help
on 23/09/2009 18:19 kama said the following: > On Wed, 23 Sep 2009, Andriy Gapon wrote: > >> 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. > > Even though they dont exists on a acpi_debug kernel. It does not really > matter since the real problem is that freebsd freezes on a normal generic > config. What is acpi_debug kernel? And FreeBSD does not freeze on "a normal generic config". It freezes because of a mysterious build bug that only you seem to have (so far). >>> Just adding 'device acpi' into the generic kernel made it boot >>> successfully. (without KDB DDB ACPI_DEBUG) >> I am glad that this worked :) > > Me too. As a work around. But I would prefer a GENERIC kernel to boot. True GENERIC kernel is the one that you get from FreeBSD.Org :-) The one that you built yourself even using GENERIC config can always get tainted by unspecified problems with your build environment. Can you reproduce this problem if you build world, install it somewhere, chroot to it and then build a GENERIC kernel? (with no tweaking between the steps) >From practical point of view, I don't see why moving acpi from module to kernel could be an issue. >>> 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. > > I dunno. I dont have any insight into kernel programming. Hence trying to > get information how to help the people to fix the actual problem. That the > server freezes at boot. Im kind of lucky to have HP ILO on my side, to > test things. =) > > But I will upgrade the BIOS. If that does not work, I'll try a clean > 7.2-REL install. BIOS upgrade may improve some things for you, but I'd be very surprised if it fixes the build problem in question. > PS. > Another unrelated issue. I get a bounce everytime I send a mail to you. > > Final-Recipient: rfc822; avg@icyb.net.ua > Action: failed > Status: 5.0.0 > Diagnostic-Code: X-Postfix; host mt.icyb.net.ua[212.40.38.132] said: 550 > (LHP01) Not accepted (in reply to RCPT TO command) I'll investigate this. Meanwhile I will use my freebsd.org address in From. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ABA457E.3060800>