From owner-freebsd-stable@FreeBSD.ORG Mon Mar 1 15:05:15 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20E9C16A4D2 for ; Mon, 1 Mar 2004 15:05:15 -0800 (PST) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36DEB43D45 for ; Mon, 1 Mar 2004 15:05:08 -0800 (PST) (envelope-from Mikhail.Teterin@Murex.com) Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])i21N504J016201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 1 Mar 2004 18:05:06 -0500 (EST) (envelope-from Mikhail.Teterin@Murex.com) Received: from localhost (mteterin@localhost [127.0.0.1]) i21N4sw3048883; Mon, 1 Mar 2004 18:04:54 -0500 (EST) (envelope-from Mikhail.Teterin@Murex.com) From: Mikhail Teterin Organization: Murex N.A. To: Nicolas Souchu Date: Mon, 1 Mar 2004 18:04:53 -0500 User-Agent: KMail/1.5.4 References: <200403011650.08391@misha-mx.virtual-estates.net> <20040301234411.C1821@armor.freesurf.fr> In-Reply-To: <20040301234411.C1821@armor.freesurf.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403011804.53480@misha-mx.virtual-estates.net> X-Scanned-By: MIMEDefang 2.39 cc: stable@FreeBSD.org Subject: Re: troubles with smb0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: mi+mx@aldan.algebra.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2004 23:05:15 -0000 On Mon, Mar 01, 2004 at 04:50:08PM -0500, Mikhail Teterin wrote: =[...] => [...] => 1179 lmmon CALL open(0x8049135,0x2,0x804912c) => 1179 lmmon NAMI "/dev/smb0" => 1179 lmmon RET open 3 => 1179 lmmon CALL ioctl(0x3,SMB_READB,0xbfbffa04) => 1179 lmmon RET ioctl -1 errno 6 Device not configured => [...] => => The kernel config file has the following devices listed: => => device smbus => device smb => device ichsmb => => What am I missing? Thanks! =The monitoring chip (not the controller which seems ok) you access must =be at the expected address on the SMB bus. Is that the case? Thank you for the prompt response, but I have no idea, what you are asking about. How do I find out the answer? I'll e-mail you the dmesg.boot privately -- may be, that'll help. Yours, -mi