Date: Fri, 27 Aug 2004 14:42:10 -0700 From: Nate Lawson <nate@root.org> To: Roman Kurakin <rik@cronyx.ru> Cc: current@freebsd.org Subject: Re: Bug reports requested - acpi Message-ID: <412FAAB2.3000407@root.org> In-Reply-To: <412F692D.7090007@cronyx.ru> References: <412D02FE.2080805@root.org> <412F141E.5070102@cronyx.ru> <412F6283.7000900@root.org> <412F692D.7090007@cronyx.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Roman Kurakin wrote: > Nate Lawson wrote: > >> Roman Kurakin wrote: >> >>> You want it: >>> >>> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2624308+0+/usr/local/www/db/text/2004/freebsd-current/20040822.freebsd-current >>> >>> >>> It seems that problems I have due to acpi code update between >>> 2004-08-13 and 2004-08-14. >>> I'll check tomorrow that I didn't mix up sources. >>> >>> I've just applied changes in vm code that was made while 13-14, and >>> after >>> restart I was able to log in to buggy system. So vm is not the place >>> of problems. >>> The only unapplied patch is a acpi changes. >> >> >> Does booting without ACPI fix the problem? > > > No. Only safe mode. As I understand it also turn off MP. Safe mode disables the APIC in addition to ACPI. Since disabling ACPI alone doesn't fix your problem, I doubt I can be much more help right now since I'm not an APIC expert. Why don't you try booting with APIC disabled but ACPI still active and see how things work? set hint.apic.0.disabled="1" at the loader prompt > Again, if I set break point at install_ap_tramp this function start to > work correctly. > (No trap at write access). And panic occures from other place (And I > unable to fix > it by debugging ;-)) in mp_machdep.c. > > Now I'll try to understan what part of that ACPI commit I could leave > and which to > backout to minimize search area. -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?412FAAB2.3000407>