From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 13 16:14:16 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F0A916A4CE; Tue, 13 Jan 2004 16:14:16 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6F6C43D1D; Tue, 13 Jan 2004 16:14:14 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc12) with ESMTP id <20040114001413012007t5rce>; Wed, 14 Jan 2004 00:14:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA02200; Tue, 13 Jan 2004 16:14:11 -0800 (PST) Date: Tue, 13 Jan 2004 16:14:10 -0800 (PST) From: Julian Elischer To: Stijn Hoop In-Reply-To: <20040113235511.GB39353@pcwin002.win.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org cc: imp@freebsd.org Subject: Re: PCI interrupt allocation question.. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2004 00:14:16 -0000 On Wed, 14 Jan 2004, Stijn Hoop wrote: > On Tue, Jan 13, 2004 at 03:26:00PM -0800, Julian Elischer wrote: > > The kernel includes teh ichsmb driver to try access the SMBus > > for temperature reading reasons (yes I know I can do it other ways..) > > > > Any thoughts that move me towards getting th eichsmb driver working on > > this machine are welcome. > > Make sure that the mainboard really does support SMBus -- it turns out that > this is optional. The ICH docs talk about a bit that should be enabled in the > PCI config when SMB is present. I ran into this once, it should be documented > in the archives (of -current off the top of my head). OTOH, I didn't even > succeed in getting an ichsmb device probed so this might be something totally > unrelated. > > FWIW, I had to try other ways to get the temperature (xmbmon & related). I > don't have the box anymore or I'd show you the exact config... xmbmon uses the SMBus to read the temperatures but it does it from userland using direct read and write operations and when there are timing glitches caused by the process not getting scheduled quite quick enough you get garbage results.. teh theory is that the kernel driver wouldn't be susceptible to this but it looks like unless I resort to polling I will not be able to use it because it relies on the interrupts and they are not being delivered. ASUS motherboards actually turn off the SMBus. (why?) So you need to turn it back on before you can read the temperatures.. I have a little script that uses pciconf to do it.. > > --Stijn > > -- > Beware of he who would deny you access to information. For in his heart > he thinks himself your master. > -- Sid Meier, "Sid Meier's Alpha Centauri" >