From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 5 15:28:17 2004 Return-Path: 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 1DEED16A4CE for ; Mon, 5 Jul 2004 15:28:17 +0000 (GMT) Received: from web41105.mail.yahoo.com (web41105.mail.yahoo.com [66.218.93.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 0392443D2F for ; Mon, 5 Jul 2004 15:28:17 +0000 (GMT) (envelope-from jmkatcher@yahoo.com) Message-ID: <20040705152815.92220.qmail@web41105.mail.yahoo.com> Received: from [24.18.54.216] by web41105.mail.yahoo.com via HTTP; Mon, 05 Jul 2004 08:28:15 PDT Date: Mon, 5 Jul 2004 08:28:15 -0700 (PDT) From: Jeffrey Katcher To: freebsd-acpi@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Atheros driver doesn't work with ACPI enabled (revisited) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2004 15:28:17 -0000 A day or so after I wrote my original note, it started to work again. Unfortunately in the last few days, it no longer works with the same failure mode as before: ath0: hardware error One new change is that the system now panics when booting without ACPI, so I have little recourse but to roll the system back to July 1st and bypass the recent ACPI changes. (All praise to cvsup...) Anyone else seeing renewed ACPI related peripheral failures? Jeff Katcher