Re: Any working ichsmb(4) platforms out there?
On Thu, 11.09.2008 at 15:14:52 +0100, Bruce M Simpson wrote: > Does anyone have ichsmb(4) actually seeing SMBus devices? > e.g. you run "smbmsg -p" on your FreeBSD-STABLE system and see something. > > I just tried it again on my IBM ThinkPad T43 and saw nothing, all I get is: > ichsmb0: device timeout, status=0x41 > ...in dmesg. No luck with an ICH5, here: ichsmb0: port 0x2400-0x241f irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 ichsmb0: device timeout, status=0x41 ichsmb0: device timeout, status=0x41 ichsmb0: device timeout, status=0x41 ichsmb0: device timeout, status=0x41 ... # uname -rsm FreeBSD 6.3-STABLE i386 # devinfo -v|grep smb ichsmb0 pnpinfo vendor=0x8086 device=0x24d3 subvendor=0x1734 subdevice=0x101c class=0x0c0500 at slot=31 function=3 handle=\_SB_.PCI0.PM__ # kenv|grep smb smbios.bios.reldate="11/25/2004" smbios.bios.vendor="FUJITSU SIEMENS // Phoenix Technologies Ltd." smbios.bios.version="5.00 R2.14.1534.01 " smbios.chassis.maker="FUJITSU SIEMENS" smbios.chassis.serial="YBFC445826 " smbios.chassis.tag="" smbios.chassis.version="SCEE " smbios.planar.maker="FUJITSU SIEMENS" smbios.planar.product="D1534" smbios.planar.serial="" smbios.planar.version="S26361-D1534" smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="FUJITSU SIEMENS" smbios.system.product="SCENIC E" smbios.system.serial="YBFC445826 " smbios.system.uuid="93D4A7A3-705F-11D9-8688-00300577E7A0" smbios.system.version="" Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Bruce M Simpson wrote: I fished out the A/Open MX3S board I have. ... So I can confirm SMBus works on the MX3S from Linux 2.6.x. I'll blow it away with 7.1-BETA and see what happens next. I can confirm that SMBus appears to work on the A/Open MX3S under FreeBSD 7.1-BETA. After kldload ichsmb and kldload smb: %%% ichsmb0: port 0x5000-0x500f at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] smbus0: on ichsmb0 smb0: on smbus0 %%% smbmsg -p: %%% Probing for devices on /dev/smb0: Device @0x30: rw Device @0x50: rw Device @0xb0: rw Device @0xd0: rw %%% pciconf -a seems to be broken: %%% raisin:~ % s pciconf -a pci0:0:31:3 pciconf: ioctl(PCIOCATTACHED): Inappropriate ioctl for device %%% My theory at the moment is that the working platforms might have had some other bits twiddled in PCI config space. I'm ruling that out for now, based on the fact that when I dump the CSRs for the SMBus function on both the ICH2 (known good, working) and ICH7 (suspect), the HOSTC register contents are the same (SMBus is enabled) and both have interrupt lines routed to them. working system, ICH2: %%% raisin# pciconf -r pci0:0:31:3 0:0x40 24438086 0281 0c050002 5001 244b8086 020c 0001 %%% suspect system, ICH7: %%% foo:~ % s pciconf -r pci0:0:31:3 0:0x40 27da8086 0281 0c050001 0501 27da8086 0213 0001 %%% Both are using SMP-enabled kernels. The working system is running a 7.1-BETA kernel, GENERIC so it has SMP, but it's a uniprocessor 633MHz Celeron; the suspect system has dual-core (I *think* it is Intel Atom). I'm not sure how that could make a difference. The ichsmb(4) driver uses msleep() (now deprecated) to avoid busy-waiting when polling for SMB transaction completion. On the suspect system, msleep() always times out. So both are using ithreads... AHA! After a reboot it looks like I can see a device on the suspect system, interesting. But after the first probe, it doesn't respond. This could well be down to the implementation of that particular SMBus device on the platform, and it tends to move the finger of suspicion away from the smbus drivers themselves. cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Bruce M Simpson wrote: Jeremy Chadwick wrote: I'm trying my best to make things better, doing things purely from a userland perspective and using SMBus exclusively (since the interface is quite reliable, assuming the SMBus driver used on FreeBSD is working correctly). I understand-- Bruce is having problems with ichsmb(4), while on every ICH7 board I have (and I have many), I've had nothing but success. All of bsdhwmon's main development has been done on ICH7 boards I use and have physical access to, for example. I have a Dell PowerEdge SC440 here and I'm not having much luck with smbmsg: # smbmsg -p Probing for devices on /dev/smb0: [ lots and lots of 'ichsmb0: device timeout, status=0x41' ] As far as I can see, I've got all the relevant devices built into the kernel (from kldstat -v: ichsmb/smbus, pci/ichsmb, iicbus/iicsmb, smbus/smb, intsmb/smbus, pci/intsmb). This is a Dell-branded motherboard, so I've no idea what it's based on. The boot message shows 'ichsmb0: '. Cheers, --Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Jeremy Chadwick wrote: I don't consider this a "dependency issue" at all. These are all literally separate things; you do not meed smbus(4) and smb(4) if you just simply want to tie a driver to a feature/device that's on the PCI bus (e.g. ichsmb(4)). Besides, does kldload or kernel modules in general have *any* sort of dependency tree code? I didn't think they did. Some modules do, some modules don't. One of the issues here is that there is sometimes a diamond-like dependency graph between kernel modules, or there is no way to establish dependency at all. For example, smb(4) has no idea that ichsmb(4) should be loaded, for the very reason you point out that smb(4) isn't needed by ichsmb(4); whilst ichsmb(4) presents an smbus(4) interface in the kernel, which smb(4) will recognise and attach to, it has no idea that it should get loaded. Having said that, I thought your plain language explanation of how things are was excellent and clear. cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
On Fri, Sep 12, 2008 at 01:12:34PM -0500, Chris Ruiz wrote:
>
> On Sep 12, 2008, at 12:57 PM, Jeremy Chadwick wrote:
>
>> On Fri, Sep 12, 2008 at 12:19:55PM -0500, Chris Ruiz wrote:
>>> I have an ICH9 system and get the following:
>>>
>>> First, my kernel:
>>> FreeBSD attack.young-alumni.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE
>>> #0: Sat Sep 6 08:33:04 CDT 2008 root@:/usr/src/sys/amd64/
>>> compile/
>>> ATTACK amd64
>>>
>>> Dmesg:
>>> ichsmb0: port 0x3000-0x301f mem
>>> 0xe0427000-0xe04270ff
>>> irq 18
>>> at device 31.3 on pci0
>>> ichsmb0: [GIANT-LOCKED]
>>> ichsmb0: [ITHREAD]
>>> smbus0: on ichsmb0
>>>
>>> Error:
>>> attack:~ root# smbmsg -p
>>> smbmsg: Cannot open /dev/smb0: No such file or directory
>>
>> Does your kernel include all 3 of the following devices?
>>
>> device smbus
>> device smb
>> device ichsmb
>>
>> --
>> | Jeremy Chadwickjdc at parodius.com |
>> | Parodius Networking http://www.parodius.com/ |
>> | UNIX Systems Administrator Mountain View, CA, USA |
>> | Making life hard for others since 1977. PGP: 4BD6C0CB |
>>
>
> Jeremy,
>
> I loaded smb.ko and it fixed the situation. I had the line
> 'ichsmb_load="YES"' in my loader.conf and it loaded smbus.ko but not
> smb.ko for me. Seems like a module load dependency issue.
They're all independent pieces, that's why. I realise the naming
convention is confusing ("wait, what do I need? Do I need iicbus? What
is that thing?!"), and older FreeBSD kernel configuration syntaxes and
documentation made it even worse.
Here's the breakdown in layman's terms:
ichsmb(4) -- support for Intel ICHxx SMBus via PCI bus
smbus(4) -- adds support for kernel SMBus API framework and interfaces
with chipset SMBus driver (e.g. ichsmb(4))
smb(4)-- creates /dev/smbXX entries and provides ioctl(2) interface
for userland applications
Does this help reduce confusion?
I don't consider this a "dependency issue" at all. These are all
literally separate things; you do not meed smbus(4) and smb(4) if you
just simply want to tie a driver to a feature/device that's on the PCI
bus (e.g. ichsmb(4)).
Besides, does kldload or kernel modules in general have *any* sort
of dependency tree code? I didn't think they did.
> Here's my output:
> attack:~ root# smbmsg -p
> Probing for devices on /dev/smb0:
> Device @0x44: rw
> Device @0x50: rw
> Device @0x52: rw
> Device @0x64: w
> Device @0x80: rw
> Device @0x88: w
> Device @0x8c: r
> Device @0xc4: rw
> Device @0xd0: rw
> Device @0xd2: rw
> Device @0xe4: w
Good deal, this is functioning normally.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
On Sep 12, 2008, at 12:57 PM, Jeremy Chadwick wrote: On Fri, Sep 12, 2008 at 12:19:55PM -0500, Chris Ruiz wrote: I have an ICH9 system and get the following: First, my kernel: FreeBSD attack.young-alumni.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Sat Sep 6 08:33:04 CDT 2008 root@:/usr/src/sys/amd64/ compile/ ATTACK amd64 Dmesg: ichsmb0: port 0x3000-0x301f mem 0xe0427000-0xe04270ff irq 18 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] smbus0: on ichsmb0 Error: attack:~ root# smbmsg -p smbmsg: Cannot open /dev/smb0: No such file or directory Does your kernel include all 3 of the following devices? device smbus device smb device ichsmb -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | Jeremy, I loaded smb.ko and it fixed the situation. I had the line 'ichsmb_load="YES"' in my loader.conf and it loaded smbus.ko but not smb.ko for me. Seems like a module load dependency issue. Here's my output: attack:~ root# smbmsg -p Probing for devices on /dev/smb0: Device @0x44: rw Device @0x50: rw Device @0x52: rw Device @0x64: w Device @0x80: rw Device @0x88: w Device @0x8c: r Device @0xc4: rw Device @0xd0: rw Device @0xd2: rw Device @0xe4: w Thanks, Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Chris Ruiz wrote: Error: attack:~ root# smbmsg -p smbmsg: Cannot open /dev/smb0: No such file or directory Looks like the smb.ko module ain't loaded. cheers, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
On Fri, Sep 12, 2008 at 12:19:55PM -0500, Chris Ruiz wrote: > I have an ICH9 system and get the following: > > First, my kernel: > FreeBSD attack.young-alumni.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE > #0: Sat Sep 6 08:33:04 CDT 2008 root@:/usr/src/sys/amd64/compile/ > ATTACK amd64 > > Dmesg: > ichsmb0: port 0x3000-0x301f mem 0xe0427000-0xe04270ff > irq 18 > at device 31.3 on pci0 > ichsmb0: [GIANT-LOCKED] > ichsmb0: [ITHREAD] > smbus0: on ichsmb0 > > Error: > attack:~ root# smbmsg -p > smbmsg: Cannot open /dev/smb0: No such file or directory Does your kernel include all 3 of the following devices? device smbus device smb device ichsmb -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Jeremy Chadwick wrote: I'm trying my best to make things better, doing things purely from a userland perspective and using SMBus exclusively (since the interface is quite reliable, assuming the SMBus driver used on FreeBSD is working correctly). I understand-- Bruce is having problems with ichsmb(4), while on every ICH7 board I have (and I have many), I've had nothing but success. All of bsdhwmon's main development has been done on ICH7 boards I use and have physical access to, for example. I fished out the A/Open MX3S board I have. It seems to have an ICH2 south bridge. An old version of Gentoo I had installed finds the ICH2. mbmon is able to talk to a Winbond chip over ISA; it sees an SMBus slave 0xA0/0x50, I don't know what that is yet. I got this board years ago, I think because it does actually support smbus. I'm just futzing with Gentoo now to get the HWMON and other i2c drivers up. i2c-i801.ko probes and attaches. i2c-dev.ko created /dev/i2c* nodes ok. I then downloaded i2c-tools from http://www.lm-sensors.org/wiki/I2CTools and built it. %%% raisin i2c-tools-3.0.1 # /usr/local/sbin/i2cdetect 3 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c/3. I will probe address range 0x03-0x77. Continue? [Y/n] Y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- %%% %%% raisin i2c-tools-3.0.1 # mbmon -S -D Probe Request: none >>> Testing Reg's at SMBus <<< [Intel8XX(ICH/ICH2/ICH3/ICH4/ICH5/ICH6), IO-Base:0x5000] SMBus slave 0xA0(0x50) found... SMBus[Intel8XX(ICH/ICH2/ICH3/ICH4/ICH5/ICH6)] found, but No HWM available on it!! InitMBInfo: Success %%% Likely these are old versions of the mbmon tools. %%%raisin i2c-tools-3.0.1 # /usr/local/sbin/i2cdump 3 0x50 b 0 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c/3, address 0x50, mode byte Continue? [Y/n] Y 0 1 2 3 4 5 6 7 8 9 a b c d e f0123456789abcdef 00: 80 08 04 0c 0a 01 40 00 01 80 60 00 80 08 00 01[EMAIL PROTECTED] 10: 8f 04 06 01 01 00 0e a0 60 00 00 14 14 14 32 20?.??`..???2 20: 20 10 20 10 00 00 00 00 00 00 00 00 00 00 00 00 ? ? 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 f6..?? 40: 2c ff ff ff ff ff ff ff 08 38 4c 53 44 54 31 36,...?8LSDT16 50: 36 34 41 47 2d 31 30 45 45 31 20 01 00 03 10 6c64AG-10EE1 ?.??l 60: 08 95 7e 00 00 00 00 00 00 00 00 00 00 00 00 00??~. 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 64 af..d? 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff %%% Hey, that looks like a Micron DIMM. I didn't see anything on the other two i2c bus addresses. So I can confirm SMBus works on the MX3S from Linux 2.6.x. I'll blow it away with 7.1-BETA and see what happens next. cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
On Sep 11, 2008, at 9:14 AM, Bruce M Simpson wrote: Does anyone have ichsmb(4) actually seeing SMBus devices? e.g. you run "smbmsg -p" on your FreeBSD-STABLE system and see something. I just tried it again on my IBM ThinkPad T43 and saw nothing, all I get is: ichsmb0: device timeout, status=0x41 ...in dmesg. cheers BMS BMS, I have an ICH9 system and get the following: First, my kernel: FreeBSD attack.young-alumni.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Sat Sep 6 08:33:04 CDT 2008 root@:/usr/src/sys/amd64/compile/ ATTACK amd64 Dmesg: ichsmb0: port 0x3000-0x301f mem 0xe0427000-0xe04270ff irq 18 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] smbus0: on ichsmb0 Error: attack:~ root# smbmsg -p smbmsg: Cannot open /dev/smb0: No such file or directory Hope this helps, Chris Ruiz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED] " ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Jeremy Chadwick wrote: > didn't think anyone was still using Intel 440BX boards in this day and > age! (A great chipset, though!) I just updated an i440BX based dual-celeron-466 from some old 4.8-stable to 7.1-prerelease. "make buildworld" takes about eight hours (without -j), but I don't care, I just let it run over night. The machine is perfectly capable and fast enough to act as a name server, small mail and web server for a dozen people, and as a generic shell box for various tasks. There's also an old notebook (2001) with i440BX and a Pentium-III 850 MHz, which I use occasionally on trips. It's completely sufficient to get online, read e-mails, chat, browse the web, upload digital photos and so on. I hate throwing away hardware that's still working and up to the task. :-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd C++: "an octopus made by nailing extra legs onto a dog" -- Steve Taylor, 1998 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
On Thu, Sep 11, 2008 at 11:28:03AM -0400, Michael Butler wrote: > Richard Tector wrote: > > Bruce M Simpson wrote: > >> Richard, > >> > >> Thanks for this. > >> > >> Richard Tector wrote: > >>> > >>> I have an ICH9 machine, Tyan motherboard: > >>> FreeBSD 7.0-STABLE #0: Fri Aug 1 14:57:33 BST 2008 > >>> ichsmb0: port 0x18e0-0x18ff mem > >>> 0xf4a03000-0xf4a030ff irq 17 at device 31.3 on pci0 > >>> ichsmb0: [GIANT-LOCKED] > >>> ichsmb0: [ITHREAD] > >>> > >>> daffy# smbmsg -p > >>> Probing for devices on /dev/smb0: > >>> Device @0x2e: rw > >> ... > >> So it looks like yours works! I see no differences to RELENG_7_0. > >> > >> Are you using any hardware monitoring devices? > >> Can you give bsdhwmon a shot? > >> > >> cheers > >> BMS > > > > Sure. If yourself or Jeremy could send over the tarball? > > I don't use any hardware monitoring on it currently. > I'd also appreciate the opportunity to try it .. old hardware but .. > > [EMAIL PROTECTED]:/home/imb> devinfo -v | grep smb > intsmb0 pnpinfo vendor=0x8086 device=0x7113 subvendor=0x > subdevice=0x class=0x068000 at slot=7 function=3 handle=\_SB_.PCI0.PMU_ > smbus0 > smb0 > [EMAIL PROTECTED]:/home/imb> kenv | grep smbios > smbios.bios.reldate="07/20/2001" > smbios.bios.vendor="Intel Corp." > smbios.bios.version="TR440BXA.86B.0042.P15.0107200951" > smbios.chassis.maker="Dell Computer Corp." > smbios.chassis.serial="YC571 " > smbios.chassis.tag=" " > smbios.chassis.version="SPAW70W PA[CA] " > smbios.planar.maker="Intel Corporation " > smbios.planar.product="TR440BXA " > smbios.planar.serial="IMTR02702003 " > smbios.planar.version="A16643-305 " > smbios.socket.enabled="1" > smbios.socket.populated="1" > smbios.system.maker="Dell Computer Corp." > smbios.system.product="PowerApp.web 100 W " > smbios.system.serial="YC571 " > smbios.system.uuid="44454c4c-00ca-1059-8043-80c04f353731" > smbios.system.version="SPAW70W" didn't think anyone was still using Intel 440BX boards in this day and age! (A great chipset, though!) I can absolutely assure you bsdhwmon will not work on this board. I can add support for it, but I need to know full register details of what H/W monitoring IC is tied to SMBus, and what the SMBus slave address is of the monitoring IC. > [EMAIL PROTECTED]:/home/imb> sudo smbmsg -p > Probing for devices on /dev/smb0: > Device @0x5a: rw > Device @0x60: rw > Device @0x62: rw > Device @0x64: rw > Device @0x66: rw > Device @0xa0: rw > Device @0xa2: rw > Device @0xa4: rw > Device @0xa6: rw > [EMAIL PROTECTED]:/home/imb> sudo mbmon -d > Using SMBus-ioctl access method[IntelPIIX4(440BX/MX)]!! > * Analog Dev. Chip ADM9240 found. Can you confirm this is correct? Does this board really have an ADM H/W monitoring IC on it? Are the rpms/voltages/temps returned by mbmon *actually correct? Hardware monitoring software in the ports tree make some general assumptions over what the register offset/indexes are, which are often wrong depending upon what sub-model of chip is used. This is one reason why bsdhwmon reads the smbios data and matches motherboard model up with what chip is installed on the board. I'm sure I'll eventually encounter a situation where motherboard X has two different revisions of hardware monitoring ICs on it (e.g. one is a 1234A, and later releases of the same board use a 1234B), but the code should be able to account for that cleanly. The state of hardware monitoring on BSD is atrocious, and it was atrocious 10 years ago. Absolutely no evolution has occurred in this regard, while Linux's lm-sensors has pretty much dominated in this regard. OpenBSD has sensors framework, too. A user on #bsdports privately discussed this situation with me yesterday, as apparently there are a large number of Russian forums and mailing lists discussing how to get mbmon, consolehw, or healthd to work with their systems. What these people aren't aware of is how outdated the programs are, how it all works, and the risks involved when using a hardware monitor that blindly hits certain registers (this is especially risky with ISA bus interaction). I'm trying my best to make things better, doing things purely from a userland perspective and using SMBus exclusively (since the interface is quite reliable, assuming the SMBus driver used on FreeBSD is working correctly). I understand-- Bruce is having problems with ichsmb(4), while on every ICH7 board I have (and I have many), I've had nothing but success. All of bsdhwmon's main development has been done on ICH7 boards I use and have physical access to, for example. I wish I knew more about the inner-workings of PCI and SMBus in general, but as it stands, my knowledge is limited solely to interfacing with a device *on* the SMBus. -- | Jeremy Chadwick
Re: Any working ichsmb(4) platforms out there?
Richard Tector wrote: > Bruce M Simpson wrote: >> Richard, >> >> Thanks for this. >> >> Richard Tector wrote: >>> >>> I have an ICH9 machine, Tyan motherboard: >>> FreeBSD 7.0-STABLE #0: Fri Aug 1 14:57:33 BST 2008 >>> ichsmb0: port 0x18e0-0x18ff mem >>> 0xf4a03000-0xf4a030ff irq 17 at device 31.3 on pci0 >>> ichsmb0: [GIANT-LOCKED] >>> ichsmb0: [ITHREAD] >>> >>> daffy# smbmsg -p >>> Probing for devices on /dev/smb0: >>> Device @0x2e: rw >> ... >> So it looks like yours works! I see no differences to RELENG_7_0. >> >> Are you using any hardware monitoring devices? >> Can you give bsdhwmon a shot? >> >> cheers >> BMS > > Sure. If yourself or Jeremy could send over the tarball? > I don't use any hardware monitoring on it currently. I'd also appreciate the opportunity to try it .. old hardware but .. [EMAIL PROTECTED]:/home/imb> devinfo -v | grep smb intsmb0 pnpinfo vendor=0x8086 device=0x7113 subvendor=0x subdevice=0x class=0x068000 at slot=7 function=3 handle=\_SB_.PCI0.PMU_ smbus0 smb0 [EMAIL PROTECTED]:/home/imb> kenv | grep smbios smbios.bios.reldate="07/20/2001" smbios.bios.vendor="Intel Corp." smbios.bios.version="TR440BXA.86B.0042.P15.0107200951" smbios.chassis.maker="Dell Computer Corp." smbios.chassis.serial="YC571 " smbios.chassis.tag=" " smbios.chassis.version="SPAW70W PA[CA] " smbios.planar.maker="Intel Corporation " smbios.planar.product="TR440BXA " smbios.planar.serial="IMTR02702003 " smbios.planar.version="A16643-305 " smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="Dell Computer Corp." smbios.system.product="PowerApp.web 100 W " smbios.system.serial="YC571 " smbios.system.uuid="44454c4c-00ca-1059-8043-80c04f353731" smbios.system.version="SPAW70W" [EMAIL PROTECTED]:/home/imb> sudo smbmsg -p Probing for devices on /dev/smb0: Device @0x5a: rw Device @0x60: rw Device @0x62: rw Device @0x64: rw Device @0x66: rw Device @0xa0: rw Device @0xa2: rw Device @0xa4: rw Device @0xa6: rw [EMAIL PROTECTED]:/home/imb> sudo mbmon -d Using SMBus-ioctl access method[IntelPIIX4(440BX/MX)]!! * Analog Dev. Chip ADM9240 found. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Richard Tector wrote: Interestingly, I just tried on a couple of our webservers. Dell PowerEdge 860's with ICH7 running 7.0-STABLE, amd64. Loading the ichsmb module gives: ichsmb0: port 0x8c0-0x8df at device 31.3 on pci0 pcib0: no PRT entry for 0.31.INTB ichsmb0: can't get IRQ device_attach: ichsmb0 attach returned 6 I found one another ICH7 machine. 6.3-STABLE, i386. It exhibits the same problems you were having. An unkillable smbmsg, and several ichsmb0: device timeout, status=0x41 Regards, Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Bruce M Simpson wrote: Richard, Thanks for this. Richard Tector wrote: I have an ICH9 machine, Tyan motherboard: FreeBSD 7.0-STABLE #0: Fri Aug 1 14:57:33 BST 2008 ichsmb0: port 0x18e0-0x18ff mem 0xf4a03000-0xf4a030ff irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] daffy# smbmsg -p Probing for devices on /dev/smb0: Device @0x2e: rw ... So it looks like yours works! I see no differences to RELENG_7_0. Are you using any hardware monitoring devices? Can you give bsdhwmon a shot? cheers BMS Sure. If yourself or Jeremy could send over the tarball? I don't use any hardware monitoring on it currently. Interestingly, I just tried on a couple of our webservers. Dell PowerEdge 860's with ICH7 running 7.0-STABLE, amd64. Loading the ichsmb module gives: ichsmb0: port 0x8c0-0x8df at device 31.3 on pci0 pcib0: no PRT entry for 0.31.INTB ichsmb0: can't get IRQ device_attach: ichsmb0 attach returned 6 Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Richard, Thanks for this. Richard Tector wrote: I have an ICH9 machine, Tyan motherboard: FreeBSD 7.0-STABLE #0: Fri Aug 1 14:57:33 BST 2008 ichsmb0: port 0x18e0-0x18ff mem 0xf4a03000-0xf4a030ff irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] daffy# smbmsg -p Probing for devices on /dev/smb0: Device @0x2e: rw ... So it looks like yours works! I see no differences to RELENG_7_0. Are you using any hardware monitoring devices? Can you give bsdhwmon a shot? cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any working ichsmb(4) platforms out there?
Bruce M Simpson wrote: Does anyone have ichsmb(4) actually seeing SMBus devices? e.g. you run "smbmsg -p" on your FreeBSD-STABLE system and see something. I just tried it again on my IBM ThinkPad T43 and saw nothing, all I get is: ichsmb0: device timeout, status=0x41 ...in dmesg. I have an ICH9 machine, Tyan motherboard: FreeBSD 7.0-STABLE #0: Fri Aug 1 14:57:33 BST 2008 ichsmb0: port 0x18e0-0x18ff mem 0xf4a03000-0xf4a030ff irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] daffy# smbmsg -p Probing for devices on /dev/smb0: Device @0x2e: rw Device @0x44: rw Device @0x60: rw Device @0x88: w Device @0xae: rw Device @0xc4: rw Device @0xe0: rw daffy# Any use? Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Any working ichsmb(4) platforms out there?
Does anyone have ichsmb(4) actually seeing SMBus devices? e.g. you run "smbmsg -p" on your FreeBSD-STABLE system and see something. I just tried it again on my IBM ThinkPad T43 and saw nothing, all I get is: ichsmb0: device timeout, status=0x41 ...in dmesg. cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
