From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 10 14:35:24 2006 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 7DDF116A4DA for ; Mon, 10 Jul 2006 14:35:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFCFF43D45 for ; Mon, 10 Jul 2006 14:35:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6AEZ8dX061078; Mon, 10 Jul 2006 10:35:16 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 10 Jul 2006 09:38:09 -0400 User-Agent: KMail/1.9.1 References: <20060710143810.61705f74@localhost> In-Reply-To: <20060710143810.61705f74@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607100938.10108.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Mon, 10 Jul 2006 10:35:17 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1590/Mon Jul 10 01:34:09 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: Selectively disabling acpi sub-systems 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: Mon, 10 Jul 2006 14:35:24 -0000 On Monday 10 July 2006 08:38, Fabian Keil wrote: > As described in: > http://lists.freebsd.org/pipermail/freebsd-stable/2006-June/026554.html > I'm currently experiencing strange hangs or crashes with a FreeBSD > RELENG_6 system running Tor. > > ... > > Could someone please tell me how to stop acpi0 from > grabbing sio0, without affecting fxp0? You most likely can't. You can't disable ACPI from managing devices and then expect it to manage PCI interrupts. As far as your actual panic. I've looked at the PR's, etc. and there are few if any details. For example, what is a "hard crash?" Does the machine turn off? Is it locked up such that it won't respond to pings? In general, even if it's deadlocked you can break into DDB via a serial console (trust me, I've seen this far too many times at my day job in the past few weeks). -- John Baldwin