From owner-freebsd-acpi@FreeBSD.ORG Sat Oct 1 23:03:48 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28D1D16A41F for ; Sat, 1 Oct 2005 23:03:48 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D33C443D45 for ; Sat, 1 Oct 2005 23:03:47 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-210-221-89.client.insightbb.com ([12.210.221.89] helo=familysquires.net) by rader.servnow.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1ELqOK-0000wl-Aw for freebsd-acpi@freebsd.org; Sat, 01 Oct 2005 19:03:40 -0400 Date: Sat, 1 Oct 2005 18:03:46 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: freebsd-acpi@freebsd.org In-Reply-To: <20050925.001550.41626219.haro@h4.dion.ne.jp> Message-ID: <20051001175954.U34460@familysquires.net> References: <43355527.1010308@e-broad.jp> <20050925.001550.41626219.haro@h4.dion.ne.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: Subject: Re: system hangs on boot up X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2005 23:03:48 -0000 I'm having a possibly similar problem with a Toshiba 8100. Symptoms are that trying to boot from a kernel from the past few days locks up after atapci0 is called; the kernel I compiled in May 2005 boots OK. Changing the "hw.pci.enable_io_modes=0" doesn't fix the problem; however, replacing the acpi.ko module in /boot/kernel with the one from the May 2005 kernel does allow the system to boot. Since this appears to at least be ACPI related I'm going to run the usual ACPI diagnostics and make them available. Mike Squires