From owner-freebsd-current@FreeBSD.ORG Mon Aug 30 08:41:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0368916A4CE for ; Mon, 30 Aug 2004 08:41:39 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4385043D41 for ; Mon, 30 Aug 2004 08:41:38 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i7U8cV6Q030047 for current@freebsd.org.checked; (8.12.8/vak/2.1) Mon, 30 Aug 2004 12:38:31 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i7U8bg7j029941; (8.12.8/vak/2.1) Mon, 30 Aug 2004 12:37:42 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <4132E7B6.6010900@cronyx.ru> Date: Mon, 30 Aug 2004 12:39:18 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <412D02FE.2080805@root.org> <412F141E.5070102@cronyx.ru> <412F6283.7000900@root.org> <412F692D.7090007@cronyx.ru> <412FAAB2.3000407@root.org> In-Reply-To: <412FAAB2.3000407@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: John Baldwin Subject: Re: Bug reports requested - acpi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 08:41:39 -0000 Nate Lawson wrote: > 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 I was unaware of all that safe mode turns off, and than I last time check this I ovelooked that apic is also disabled. It seems that problem with APIC. But could you tell me how changes in ACPICA affect APIC code? rik >> 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"