Intel CPU Crashdump utilities for dumping CPU Crashdump and registers over PECI
CS20 CHLi30
CHLI30 at nuvoton.com
Wed Oct 9 12:54:30 AEDT 2019
Hi All,
We found that oem system log type didn't show any log entries on "System logs" page in WebUI.
Even we had modify bmcweb_%.bbappend to enable these options as below:
bmcweb_%.bbappend:
# Enable CPU Log and Raw PECI support
EXTRA_OECMAKE += "-DBMCWEB_ENABLE_REDFISH_CPU_LOG=ON"
EXTRA_OECMAKE += "-DBMCWEB_ENABLE_REDFISH_RAW_PECI=ON"
In bmcweb/redfish-core/lib/log_services.hpp, we found that seems need to include com.intel.crashdump.service.
Then the crashdump daemon will help to dump CPU Crashdump and registers over PECI.
Thus, we include crashdump_git.bb recipe to build this daemon, but we got build fail due to fetch fail.
Could someone help us to check whether the SRC_URI of crashdump already move to the other source? Thanks.
crashdump_git.bb:
SRC_URI = "git://git@github.com/Intel-BMC/crashdump;protocol=ssh;nobranch=1"
SRCREV = "c99e4fb7727545501fe65b90a8a97e84d469d45e"
build fail log:
Fetcher failure for URL: 'git://git@github.com/Intel-BMC/crashdump;protocol=ssh;nobranch=1'. Unable to fetch URL from any source.
Sincerely,
Tim Lee
________________________________
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20191009/07d2622e/attachment.htm>
More information about the openbmc
mailing list