[Bug 557445] New: Service lm_sensors is not started
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c0 Summary: Service lm_sensors is not started Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: ylalym@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; ru) Presto/2.2.15 Version/10.10 suse:/home/yura # cat /etc/sysconfig/lm_sensors # Generated by sensors-detect on Sat Nov 21 00:11:53 2009 ## Path: Hardware/Sensors ## Description: Defines the modules to used ## Type: string ## ServiceRestart: lm_sensors ## Default: "" # # This file is sourced by /etc/init.d/lm_sensors and defines the modules to # be loaded/unloaded. # # The format of this file is a shell script that simply defines variables: # HWMON_MODULES for hardware monitoring driver modules, and optionally # BUS_MODULES for any required bus driver module (for example for I2C or SPI). HWMON_MODULES="coretemp w83627ehf" # For compatibility reasons, modules are also listed individually as variables # MODULE_0, MODULE_1, MODULE_2, etc. # You should use BUS_MODULES and HWMON_MODULES instead if possible. MODULE_0=coretemp MODULE_1=w83627ehf suse:/home/yura # modprobe w83627ehf FATAL: Error inserting w83627ehf (/lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy suse:/home/yura # rclm_sensors start Starting up sensors: failed suse:/home/yura #dmesg [ 78.684538] w83627ehf: Found W83627DHG chip at 0x290 [ 78.684697] ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299] [ 78.684701] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c1 --- Comment #1 from Yuriy Lalym <ylalym@gmail.com> 2009-11-20 22:30:45 UTC --- Excuse I was mistaken, Reproducible: Always The motherboard: ASUS P5K -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jdelvare@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c2 Jean Delvare <jdelvare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Jean Delvare <jdelvare@novell.com> 2009-11-24 13:12:51 UTC --- This is the typical resource conflict between ACPI and native hardware monitoring drivers. The kernel knows about the conflict and thus prevents you from loading the w83627ehf driver, but sensors-detect does NOT know about it and thus tells your to load it. The workaround in your case is to manually edit /etc/sysconfig/lm_sensors and remove "w83627ehf" from HWMON_MODULES, and also remove MODULE_1. Then the lm_sensors service should start again. On your motherboard, the asus_atk0110 driver should get loaded automatically, providing the hardware monitoring information you are looking for. Now the general fix would be to let sensors-detect know about the resource conflict, so that it doesn't tell the user to load drivers which will not load. Unfortunately it is not trivial because ACPI resources are not visible from user-space. I must discuss this upstream with the acpi developers, but couldn't find the time to actually do it yet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c3 Yuriy Lalym <ylalym@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW --- Comment #3 from Yuriy Lalym <ylalym@gmail.com> 2009-11-24 21:05:29 UTC --- Has deleted records "w83627ehf" At start the system swears .. conflicts with ACPI region HWRE [0x290-0x299] But lm_sensors successfully starts and sensors shows a state of all sensors. Thanks. Has found still here http://bugzilla.kernel.org/show_bug.cgi? id=13571 "From now on you can add acpi_enforce_resources=lax to the kernel command line to restore old behaviour." And now I am confused, let and further swears at start or I should add an option acpi_enforce_resources=lax. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c4 Jean Delvare <jdelvare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #4 from Jean Delvare <jdelvare@novell.com> 2009-11-25 10:30:53 UTC --- Boot parameter acpi_enforce_resources is to restore the old (and dangerous) behavior where the kernel did not prevent resource conflicts. It is discouraged to use it, especially in your case were the asus_atk0110 driver works just fine. BTW, if you no longer attempt to load the w83627ehf driver, the error message should no longer show at boot time. I'm leaving this bug opened as a reminder that sensors-detect needs to be somehow made aware of ACPI resource conflicts. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c5 Yuriy Lalym <ylalym@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW --- Comment #5 from Yuriy Lalym <ylalym@gmail.com> 2009-11-25 22:12:25 UTC ---
BTW, if you no longer attempt to load the w83627ehf driver, the error message should no longer show at boot time.
Precisely, but still there was an error with sensor controls suse:/home/yura # dmesg ... [ 4.184785] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 4.184788] ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] [ 4.184798] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver And it already a problem with i2c-i801 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c6 Jean Delvare <jdelvare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #6 from Jean Delvare <jdelvare@novell.com> 2009-11-26 09:08:09 UTC --- Please stop changing the status of this bug back to NEW, it's getting annoying. The second resource conflict message is about the SMBus controller. It happens because the i2c-i801 driver loads automatically (as all PCI drivers.) The message is harmless as far as hardware monitoring is concerned (you have the asus_atk0110 driver working.) If you really want to get rid of it, you can blacklist the i2c-i801 driver. For example create /etc/modprobe.d/acpi_blacklist.conf with the following contents: blacklist i2c-i801 This minor annoyance illustrates once again how ACPI fails to properly integrate with the rest of the system. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c7 Yuriy Lalym <ylalym@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW --- Comment #7 from Yuriy Lalym <ylalym@gmail.com> 2009-11-26 20:39:43 UTC --- Certainly it would be desirable that operation of a kernel with ACPI was at higher level. I am very grateful to you for answers. Such solution quite satisfies me. I have put status NEW, but you decide what to do with this question if want - will close. Once again - many thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c8 Jean Delvare <jdelvare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #8 from Jean Delvare <jdelvare@novell.com> 2009-11-27 09:34:38 UTC --- Can't you read English? PLEASE STOP SETTING THE STATUS BACK TO NEW! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c9 Yuriy Lalym <ylalym@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #9 from Yuriy Lalym <ylalym@gmail.com> 2009-11-29 10:31:58 UTC --- No. I tranlate through google. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c10 Jean Delvare <jdelvare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #10 from Jean Delvare <jdelvare@novell.com> 2009-11-29 15:30:18 UTC --- Huh. Then I hope that google can translate the following for you: DO NOT CHANGE THE STATUS OF THIS BUG EVER AGAIN. Thank you very much. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=557445 http://bugzilla.novell.com/show_bug.cgi?id=557445#c Jean Delvare <jdelvare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=557445 https://bugzilla.novell.com/show_bug.cgi?id=557445#c11 Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |jeffm@suse.com Resolution| |WONTFIX --- Comment #11 from Jeff Mahoney <jeffm@suse.com> 2012-08-02 11:59:44 EDT --- With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained. Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue. We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users. We're working hard to make openSUSE 12.2 the best openSUSE release yet! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=557445 https://bugzilla.novell.com/show_bug.cgi?id=557445#c12 --- Comment #12 from Jeff Mahoney <jeffm@suse.com> 2012-08-02 12:00:39 EDT --- With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained. Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue. We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users. We're working hard to make openSUSE 12.2 the best openSUSE release yet! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com