From owner-freebsd-gnome@FreeBSD.ORG Wed Apr 29 16:11:55 2009 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A92F106566C for ; Wed, 29 Apr 2009 16:11:55 +0000 (UTC) (envelope-from marcus@freebsd.org) Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.freebsd.org (Postfix) with ESMTP id C442B8FC18 for ; Wed, 29 Apr 2009 16:11:54 +0000 (UTC) (envelope-from marcus@freebsd.org) X-TACSUNS: Virus Scanned Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n3TGBmo4028336; Wed, 29 Apr 2009 12:11:48 -0400 (EDT) Received: from [64.102.221.219] (dhcp-64-102-221-219.cisco.com [64.102.221.219]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n3TGBlgo005776; Wed, 29 Apr 2009 12:11:48 -0400 (EDT) Message-ID: <49F87C46.2060302@freebsd.org> Date: Wed, 29 Apr 2009 12:11:50 -0400 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Anton Shterenlikht References: <20090429093327.GA63678@mech-cluster238.men.bris.ac.uk> In-Reply-To: <20090429093327.GA63678@mech-cluster238.men.bris.ac.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-gnome@freebsd.org Subject: Re: acd0 failure with dbus daemon X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2009 16:11:55 -0000 Anton Shterenlikht wrote: > This is on Compaq Armada 1700 laptop running FreeBSD 7.1-stable i386. > > As soon as I add dbus_enable="YES" to /etc/rc.conf and reboot > I get this error message on system console repeated every second > or so: > > acd0: FAILURE - unknown CMD (0x03) ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0 > x00 0x00 > > What's going on? This is actually caused by hald, and it is not a problem. You can ignore it. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome