Mukesh - you need to get your developers to look at this failure to
boot.
--
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/1619552
Title:
Failed to acknowledge elog:
/sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or
directory)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Released
Bug description:
== Comment: #0 - Mukesh K. Ojha <mukeo...@in.ibm.com> - 2016-09-02 02:10:14 ==
---Problem Description---
Kernel is failed to free the kobject while acknowledging the error log which
has been notified two times.
Contact Information = Contact Information = mukeo...@in.ibm.com
---uname output---
Ubuntu 16.04.01 LTS
Machine Type = All power machine
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Steps to reproduce:
1.Boot the system to petitboot.
2. Issue FSP Soft reset of Service Processor From ASMI page.
3. After FSP comes up, boot the system to host OS.
4. In the host OS seen the failure to acknowledge for one of elog.
root@p8wookie ~]# service opal_errd status
Redirecting to /bin/systemctl status opal_errd.service
opal_errd.service - opal_errd (PowerNV platform error handling) Service
Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled)
Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago
Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start
(code=exited, status=0/SUCCESS)
Main PID: 3497 (opal_errd)
CGroup: /system.slice/opal_errd.service
??3497 /usr/sbin/opal_errd
Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]:
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service
action required
Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such
file or directory)
Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]:
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service
action required
Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such
file or directory)
Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]:
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service
action required
Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such
file or directory)
Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]:
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service
action required
Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such
file or directory)
Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]:
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service
action required
Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such
file or directory)
[root@p8wookie ~]# cd /sys/firmware/opal/elog/
[root@p8wookie elog]# ls
0x5018d709
[root@p8wookie elog]#
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for Contact Information = mukeo...@in.ibm.com:
-Attach sysctl -a output output to the bug.
== Comment: #1 - Mukesh K. Ojha <mukeo...@in.ibm.com> - 2016-09-02 02:12:45 ==
Upstream commit :
commit a9cbf0b2195b695cbeeeecaa4e2770948c212e9a
Author: Mukesh Ojha <mukes...@linux.vnet.ibm.com>
Date: Mon Aug 22 12:17:44 2016 +0530
powerpc/powernv : Drop reference added by kset_find_obj()
In a situation, where Linux kernel gets notified about duplicate error log
from OPAL, it is been observed that kernel fails to remove sysfs entries
(/sys/firmware/opal/elog/0xXXXXXXXX) of such error logs. This is because,
we currently search the error log/dump kobject in the kset list via
'kset_find_obj()' routine. Which eventually increment the reference count
by one, once it founds the kobject.
Above patch is the solution of this bugzilla.
Kindly pull this patch in for both Ubuntu 16.04 LTS and Ubuntu 16.10.
-Mukesh
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619552/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
