From owner-freebsd-questions@FreeBSD.ORG Tue Jul 10 23:40:57 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7976A16A468 for ; Tue, 10 Jul 2007 23:40:57 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 6644613C45B for ; Tue, 10 Jul 2007 23:40:57 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 5C50B33C6C for ; Tue, 10 Jul 2007 16:21:23 -0700 (PDT) Received: from postfix.alerce.com (unknown [128.177.16.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "satchel.alerce.com", Issuer "alerce.com" (verified OK)) by merlin.alerce.com (Postfix) with ESMTP id 24AB733C64 for ; Tue, 10 Jul 2007 16:21:23 -0700 (PDT) Received: by postfix.alerce.com (Postfix, from userid 501) id 05452F80B9; Tue, 10 Jul 2007 19:21:00 -0400 (EDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18068.5212.880020.408754@almost.alerce.com> Date: Tue, 10 Jul 2007 19:21:00 -0400 To: freebsd-questions@freebsd.org X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV using ClamSMTP Subject: acpi_smbust_read_2: AE_ERROR 0x10 on a mac pro running -STABLE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2007 23:40:57 -0000 I have a mac pro running amd64 -STABLE from about a week or so ago. The console and dmesg output are flooded by acpi_smbus_read_2: AE_ERROR 0x10 message. There will be a couple, then silence, then a burst of them, then.... The don't seem to be hurting anything, but they push other stuff out of dmesg. Can anyone help me identify the problem and reduce the chatter (short of commenting out the line that's generating the output...). Thanks, g.