From owner-freebsd-current@FreeBSD.ORG Fri Aug 27 18:32:09 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 5371C16A4CE for ; Fri, 27 Aug 2004 18:32:09 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80A3B43D4C for ; Fri, 27 Aug 2004 18:32:08 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i7RIT31i060188 for current@freebsd.org.checked; (8.12.8/vak/2.1) Fri, 27 Aug 2004 22:29:03 +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 i7RIQTcf060077; (8.12.8/vak/2.1) Fri, 27 Aug 2004 22:26:29 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <412F7D32.8010104@cronyx.ru> Date: Fri, 27 Aug 2004 22:28:02 +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: Roman Kurakin References: <412D02FE.2080805@root.org> <412F141E.5070102@cronyx.ru> <412F6283.7000900@root.org> <412F692D.7090007@cronyx.ru> <412F70BC.5070703@cronyx.ru> In-Reply-To: <412F70BC.5070703@cronyx.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: Nate Lawson 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 18:32:09 -0000 Roman Kurakin wrote: > I've put old code in current Curent and get same panic. > I've need a gun but I do not know the object of it application > this one PC or me self. I need to check sources one more > time. I've really tired of it. Probably dependences problems. (I've touched all, so I don't know why). Seems ACPI. To not get mad I really need some beer as a cure. And system didn't got off by ACPI. rik > > PS. > > By the way, in any case ACPI this problem or not (in case > I've mixed up sources) could you point to any "ACPI for > dummies" resource so that I will be able to understand smth > from ACPI code? > > rik > > 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. >> >> I've just updated to current Current, so I may send fresh dump do you >> need it? >> But I hope I've described it more detailed ;-) >> >> 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. >> >> I don't have remote power control over that machine so I have only >> two hours to >> test smth with direct access. After that I will go to home. I can >> access to that >> machine remotely but it may stuck whith some big enough probability >> at any reboot. >> It seems that this machine has many ACPI related problem, but this is >> only machine >> I could use for testing ISA drivers for SMP, so I don't have choice ;-( >> >> Now I'll try to understan what part of that ACPI commit I could leave >> and which to >> backout to minimize search area. >> >> rik >> >> >> >> _______________________________________________ >> 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" >> >> > > > > _______________________________________________ > 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" > >