From owner-freebsd-current@FreeBSD.ORG Fri Aug 27 11:02:07 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 5671316A4CE for ; Fri, 27 Aug 2004 11:02:07 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2986D43D64 for ; Fri, 27 Aug 2004 11:02:06 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i7RAxC06037647 for current@freebsd.org.checked; (8.12.8/vak/2.1) Fri, 27 Aug 2004 14:59:12 +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 i7RAwCFL037550; (8.12.8/vak/2.1) Fri, 27 Aug 2004 14:58:12 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <412F141E.5070102@cronyx.ru> Date: Fri, 27 Aug 2004 14:59:42 +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> In-Reply-To: <412D02FE.2080805@root.org> Content-Type: text/plain; charset=ISO-8859-1; 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 11:02:07 -0000 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 send this report while catching my LORs so I didn't include first part of trace. Since for LOR it is a part of witness code. Initialy I didn't pay any attention to the first half of trace. I can't send it now since I've started from wrong disk and unable to log on to machine that could access buggy one via console :-( >From install_ap_tramp while copping srt => dst I got a trap while attempt to write to dst. (I've checked dst is readable). Trap calls a code from pmap_failure which in turn tries to lock (mtx_lock). And system hangs while this attempt. 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. rik Nate Lawson: > If you have a system that panics or hangs when booting with acpi > enabled but works ok if it is disabled, please let me know. You > should be running RELENG_5 or -current, no 5.2 or 4.x reports please. >