kernel-packages team mailing list archive

[bugproxy <bugproxy@xxxxxxxxxx>]

*** This bug is a duplicate of bug 1452473 ***
    https://bugs.launchpad.net/bugs/1452473

------- Comment From hepatel2@xxxxxxxxxx 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.!!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1472549

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

Status in linux package in Ubuntu:
  New

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 = pavsubra@xxxxxxxxxx 
   
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472549/+subscriptions