kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu Vivid)
       Status: In Progress => Fix Committed

-- 
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/1478513

Title:
  MFG:Firestone, Linux Error message: SYSPARAM: Opal sysparam node not
  found

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  When using Firestone POWER8 hardware, the following message gets printed to the kernel log:
  SYSPARAM: Opal sysparam node not found

  [Test Case]
  1) Boot affected hardware.
  2) dmesg | grep 'Opal sysparam node not found'

  [Fix]
  $ git describe --contains 38c0488770983b2654f075540cc1fc71f55b6df5
  v4.2-rc1~135^2~144

  --

  == Comment: #0 - Application Cdeadmin <cdeadmin@xxxxxxxxxx> -
  2015-07-22 11:35:05 ==

  == Comment: #1 - Application Cdeadmin <cdeadmin@xxxxxxxxxx> - 2015-07-22 11:35:06 ==
  ==== State: Open by: knodelk on 22 July 2015 10:25:15 ====

  The following message is being posted to the linux message log on Firestone systems, and we need to know what action to take.
   - is this caused by a code bug that needs to be fixed?
   - does the message indicate a real hardware problem?
     or can the message be ignore?

  Until we here otherwise, manufacturing is ignoring this message

  dmesg --level=alert,crit,err

  SYSPARAM: Opal sysparam node not found

  system is running with the following code levels:
         ver 1.5.4.3 - OS, HTX, Firmware and Machine details

                             OS: GNU/Linux
                     OS Version: Ubuntu 14.04.2 LTS \n \l
                 Kernel Version: 3.16.0-30-generic
                    HTX Version: htxubuntu-343

  == Comment: #2 - MAMATHA INAMDAR <mainamdar@xxxxxxxxxx> - 2015-07-27 06:18:20 ==
  "SYSPARAM: Opal sysparam node not found" we get this warning on firestone system for every boot because For OpenPower BMC machines we do not place any sysparams in the device tree.

  This issue is addressed in the attached patch and patch is available in upstream.
  We need to backport following patch in ubuntu to address this issue.
  Commit ID:38c0488770983b2654f075540cc1fc71f55b6df5
  0001-powerpc-powernv-Silence-SYSPARAM-warning-on-boot.patch

  == Comment: #3 - MAMATHA INAMDAR <mainamdar@xxxxxxxxxx> - 2015-07-27 06:25:34 ==
  Please find upstream commit ID link

  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=38c0488770983b2654f075540cc1fc71f55b6df5

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