sensors command is not getting executed in Ubuntu 14.04.3 on PowerNV 8335-GTA Hardware

Bug #1472549 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

---Problem Description---
sensors command is not getting executed in Ubuntu 14.04.3 on PowerNV 8335-GTA Hardware

Machine Type = P8

---Steps to Reproduce---
Install a PowerNV 8335-GTA machine with Ubuntu 14.04.3 netboot images.
Then load the kernel module ibmpowernv on the same.

root@tul8p1:~# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

root@tul8p1:~# sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): YES
modprobe: FATAL: Module cpuid not found.
Failed to load module cpuid.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
Sorry, no supported PCI bus adapters found.

Next adapter: p8_00000008_e0p0 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)

Next adapter: p8_00000008_e0p1 (i2c-1)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)

Next adapter: p8_00000000_e0p0 (i2c-2)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)

Next adapter: p8_00000000_e0p1 (i2c-3)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `at24' (already loaded), chip type `24c128'
    (note: this is probably NOT a sensor chip!)

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

root@tul8p1:~# lsmod | grep ibm
ibmpowernv 4808 0

root@tul8p1:~# ls -l /sys/class/hwmon/
total 0
lrwxrwxrwx 1 root root 0 Jul 7 07:46 hwmon0 -> ../../devices/platform/opal-sensor/hwmon/hwmon0

root@tul8p1:~# dpkg --list | grep lm-sensors
ii lm-sensors 1:3.3.4-2ubuntu1 ppc64el utilities to read temperature/voltage/fan sensors

---uname output---
Linux tul8p1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

---Debugger---
A debugger is not configured

Contact Information = <email address hidden>

Userspace tool common name: /usr/bin/sensors

Userspace rpm: lm-sensors-3.3.4-2

System Dump Info:
  The system is not configured to capture a system dump.

Stack trace output:
 no

Oops output:
 no

The userspace tool has the following bit modes: 64-bit

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-127378 severity-critical targetmilestone-inin14043
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1472549/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Luciano Chavez (lnx1138)
affects: ubuntu → lm-sensors (Ubuntu)
Revision history for this message
Phillip Susi (psusi) wrote :

As the error message indicates, your system does not have any supported sensors.

Changed in lm-sensors (Ubuntu):
status: New → Invalid
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-07-09 12:05 EDT-------
Hello Ubuntu,

The below upstream commit id's of the patches fix the problem in our testing.
They apply cleanly to the Ubuntu 14.04.3 kotd. so this is what we are requesting
for 14.04.3. Let us know if any concerns. Thx.

9612461 hwmon: (ibmpowernv) replace AMBIENT_TEMP by TEMP
c4ad472 hwmon: (ibmpowernv) add a get_sensor_type() routine
ccc9ac6 hwmon: (ibmpowernv) add a convert_opal_attr_name() routine
f9f54f1 hwmon: (ibmpowernv) change create_hwmon_attr_name() prototype
fcaf57b hwmon: (ibmpowernv) do not use the OPAL index for hwmon attribute names
9e4f74b hwmon: (ibmpowernv) add a helper routine create_hwmon_attr
1468163 hwmon: (ibmpowernv) add support for the new device tree
2bcd378 hwmon: (ibmpowernv) add a label attribute
3df2f59 hwmon: (ibmpowernv) pretty print labels
8416915 hwmon: (ibmpowernv) Fix build error seen for some configurations

Phillip Susi (psusi)
affects: lm-sensors (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Invalid → New
Revision history for this message
Chris J Arges (arges) wrote :

(Another duplicate of the same issue)
All of these commits are in v3.18-rc4, and thus in 15.10 and 14.04.3's kernel (which is v3.19).
I think the issue here is that you did not modprobe the module in the firstplace.
From a clean install do:
modprobe ibmpowernv

The reason this doesn't get autoloaded seems to be another issue here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452473

I looked into this a while back and it seems like there is a mismatch between the modalias and what OF provides.

Marking this a dup of that bug. Thanks

Revision history for this message
bugproxy (bugproxy) wrote :
Download full text (5.0 KiB)

------- Comment From <email address hidden> 2015-08-11 15:35 EDT-------
I have installed the P8 Hardware with Ubuntu 14.04.3 and executed the test scenario again.

root@ltc-fire8:~# uname -a
Linux ltc-fire8 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:17:43 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

root@ltc-fire8:~# modprobe ibmpowernv
root@ltc-fire8:~# lsmod | grep ibmpowernv
ibmpowernv 4808 0

root@ltc-fire8:~# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

root@ltc-fire8:~# sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): YES
modprobe: FATAL: Module cpuid not found.
Failed to load module cpuid.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
Sorry, no supported PCI bus adapters found.

Next adapter: p8_00000008_e0p0 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Handled by driver `at24' (already loaded), chip type `24c128'
(note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `at24' (already loaded), chip type `24c128'
(note: this is probably NOT a sensor chip!)

Next adapter: p8_00000008_e0p1 (i2c-1)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Handled by driver `at24' (already loaded), chip type `24c128'
(note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `at24' (already loaded), chip type `24c128'
(note: this is probably NOT a sensor chip!)

Next adapter: p8_00000000_e0p0 (i2c-2)
Do you want to scan it? (YES...

Read more...

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-10-12 10:04 EDT-------
This issue is still occurring in latest Ubuntu 14.04.3 kernels on P8 Open Power Hardware's.

root@ltchabanero002:~# uname -a
Linux ltchabanero002 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@ltchabanero002:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04.3 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.3 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

root@ltchabanero002:~# cat /proc/cpuinfo | tail
processor : 79
cpu : POWER8 (raw), altivec supported
clock : 3491.000000MHz
revision : 2.0 (pvr 004d 0200)

timebase : 512000000
platform : PowerNV
model : TN71-BP012
machine : PowerNV TN71-BP012
firmware : OPAL v3

root@ltchabanero002:~# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

root@ltchabanero002:~# lsmod | grep ibmpowernv
ibmpowernv 4808 0

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-12-16 10:19 EDT-------
Hi Canonical,

Can you please assign this bug to an appropriate developer to fix it as soon as possible.

This has been hanging around a long time without an update.

Thanks for your support.!!

Revision history for this message
Breno Leitão (breno-leitao) wrote :

This bug is a dup of Bug #1452473

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.