From owner-freebsd-current@FreeBSD.ORG Fri Aug 27 21:42:15 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 4F3DF16A4CE for ; Fri, 27 Aug 2004 21:42:15 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E3AF43D58 for ; Fri, 27 Aug 2004 21:42:15 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i7RLgAjn000700; Fri, 27 Aug 2004 14:42:11 -0700 Message-ID: <412FAAB2.3000407@root.org> Date: Fri, 27 Aug 2004 14:42:10 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7 (X11/20040702) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roman Kurakin References: <412D02FE.2080805@root.org> <412F141E.5070102@cronyx.ru> <412F6283.7000900@root.org> <412F692D.7090007@cronyx.ru> In-Reply-To: <412F692D.7090007@cronyx.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org 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: Fri, 27 Aug 2004 21:42:15 -0000 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