This kernel (2.6.16.17) no longer detects my asb100 i2c sensor device. I notice fewer directory nodes in /sys/bus/i2c/devices and lm_sensors (2.10) indicates that that are no sensors detected. sensors-detect find nothing. dmesg indicates nothing out of the ordinary. The previous kernel (2.6.16-gentoo-r7) did indeed detect my asb100 chip, so something is amiss. mobo is an asus p4pe. emerge --info ------------- Portage 2.1_rc1-r4 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.16-gentoo-r7 i686) ================================================================= System uname: 2.6.16-gentoo-r7 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distcc distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.mirrored.ca/ http://gentoo.mirrors.pair.com/http://open-systems.ufl.edu/mirrors/gentoo http://mirror.datapipe.net/gentoo" LANG="en_US.utf8" LC_ALL="en_US.utf8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X aalib alsa apm avi bitmap-fonts cdr cli crypt cups dri dvd dvdr eds emboss encode fbcon foomaticdb gif gpm gstreamer gtk gtk2 imlib isdnlog jpeg libg++ libwww mad mikmod mmx mp3 mpeg ncurses nls nptl ogg opengl oss pcre pdflib perl png pppd python quicktime readline reflection sdl session slang spell spl sse sse2 ssl tcpd truetype truetype-fonts type1-fonts udev unicode vorbis xml xml2 xorg xv xvid zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_nv" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
Attach (don't paste) your kernel .config, please.
Created attachment 87278 [details] kernel config attached
Please also upload your -r8 .config, and dmesg from both -r7 and -r8
Also, please identify which driver it is you are trying to use. I don't see any called "asb100".
CONFIG_SENSORS_ASB100=m The two configs -r7 and -r8 are absolutely identical except for the date-time stamps (i diff'd them).
i2c_adapter i2c-2: SMBus Quick command not supported, can't probe for chips i2c_adapter i2c-3: SMBus Quick command not supported, can't probe for chips these dmesg's look suspicious. i have had these on all 2.6.16's, but with -r7 asb100 is discovered and with -r8, it's not.
Created attachment 87288 [details] dmesg -r7
This device on the pci bus: 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 8089 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin B routed to IRQ 0 Region 4: I/O ports at e800 [size=32] ----sensors----under -r7----- asb100-i2c-0-2d Adapter: SMBus I801 adapter at e800 VCore 1: +1.63 V (min = +1.52 V, max = +1.74 V) +3.3V: +3.36 V (min = +3.14 V, max = +3.47 V) +5V: +5.03 V (min = +4.76 V, max = +5.24 V) +12V: +11.55 V (min = +10.82 V, max = +13.19 V) -12V (reserved): -12.07 V (min = -0.00 V, max = -0.00 V) -5V (reserved): -5.06 V (min = -0.00 V, max = -0.00 V) CPU Fan: 0 RPM (min = 1997 RPM, div = 4) Chassis Fan: 0 RPM (min = 3994 RPM, div = 2) Power Fan: 0 RPM (min = 3994 RPM, div = 2) M/B Temp: +35
This device on the pci bus: 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 8089 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin B routed to IRQ 0 Region 4: I/O ports at e800 [size=32] ----sensors----under -r7----- asb100-i2c-0-2d Adapter: SMBus I801 adapter at e800 VCore 1: +1.63 V (min = +1.52 V, max = +1.74 V) +3.3V: +3.36 V (min = +3.14 V, max = +3.47 V) +5V: +5.03 V (min = +4.76 V, max = +5.24 V) +12V: +11.55 V (min = +10.82 V, max = +13.19 V) -12V (reserved): -12.07 V (min = -0.00 V, max = -0.00 V) -5V (reserved): -5.06 V (min = -0.00 V, max = -0.00 V) CPU Fan: 0 RPM (min = 1997 RPM, div = 4) Chassis Fan: 0 RPM (min = 3994 RPM, div = 2) Power Fan: 0 RPM (min = 3994 RPM, div = 2) M/B Temp: +35°C (high = +45°C, hyst = +40°C) CPU Temp (Intel): +28°C (high = +60°C, hyst = +50°C) Power Temp: -0°C (high = +45°C, hyst = +40°C) CPU Temp (AMD): +25°C (high = +60°C, hyst = +50°C) vid: +1.525 V (VRM Version 9.0) alarms:
Created attachment 87298 [details] dmesg -r8 here's the dmesg on the -r8 kernel. the hardware device is Intel 82801 (ICH). lm_sensors was loading these modules on my machine: drivers/i2c/busses/i2c-i801.c drivers/hwmon/asb100.c drivers/i2c/chips/eeprom.c none of these files appears to have changed from -r7 to -r8. seems like the sysfs data for i2c has changed and i lost some sysfs data nodes: ---on 2.6.16-gentoo-r8---- $ls /sys/bus/i2c/devices 0-0040@ 0-0050@ 0-0060@ ---on 2.6.16-gentoo-r7---- $ls /sys/bus/i2c/devices 0-002d@ 0-0048@ 0-0049@ 0-0050@ 0-0051@ 1-0040@ 1-0050@ 1-0060@ you can see i went from 8 i2c information nodes on -r7 to only 3 on -r8 using the exact same config. lemme know if you need anything else. phil
I think this is intentional: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=ce007ea59729d627f62bb5fa8c1a81e25653a0ad;hp=eee391a66d774e644bf3cbb35403562e09d88bb2 If you disable CONFIG_ACPI_SLEEP it should be fine, but you might have lost some other functionality there...
ok, i localized the problem. note first that the salient difference in the dmesg logs for -r7 and -r8 is this line: PCI: Enabled i801 SMBus device Looking at the changelog for 2.6.16.17: http://lwn.net/Articles/184501/ You will note the entry: Carl-Daniel Hailfinger: smbus unhiding kills thermal management The exact kernel source file is: drivers/pci/quirks.c Just as a check I used the -r7 quirks.c file on my -r8 source tree and the i801 device was once again discovered. Apparently there is a claim that exposing the i801 chip breaks thermal management, so they are now explicitly hiding it. Not sure how to handle this. I was using the thermal sensors on that chip without any problems on my Asus P4PE.
i got a messgage collision there, as we posted essentially the same discovery at the same time.
disabling CONFIG_ACPI_SLEEP does indeed cause the kernel to expose that device again. i was not using chip-metered fans anyway. this is resolved to my satisfaction. thanks for your help.
Ok, thanks for confirming that. It will be fixed properly in a future kernel version, so that you can enable suspend support and still have sensor access. People just haven't decided on the best way to implement it yet.
*** Bug 134886 has been marked as a duplicate of this bug. ***
