Age | Commit message (Collapse) | Author | Files | Lines |
|
Per [1], Yocto is going to start requiring both branch names and
`protocol=https` in GitHub SRC_URI variables. Ran the upstream tool to
automatically fix our URIs.
1. https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n10
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5f9619f7ff707050b469ae74c8aa16846568c5e4
|
|
This package does not currently support openssl v3:
| TpmToOsslMath.h:79:5: error: #error Untested OpenSSL version
| 79 | # error Untested OpenSSL version
| | ^~~~~
For now, remove this package so we can make forward progress with
openssl v3 in openbmc.
The following issue appears to be tracking support:
https://sourceforge.net/p/ibmswtpm2/tickets/18/
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I2249c323b8219525dcef856d8ceab63de417e299
|
|
To support the watchdog application being able to restart after expiring
the watchdog (by being killed) multiple times per BMC reboot, a manual
magic close must be issued by writing a 'V' into the watchdog device
before starting the watchdog. Without that, the underlying hardware
watchdog wouldn't actually start running when the watchdog app was
started again, such as on the next boot.
Most watchdogs simply reboot the system upon expiration, but in this
case it's being used to trip a GPIO that the fan hardware latches on to
go to full speed so must support being restarted multiple times.
The busybox watchdog application used to support this, but it was
removed since it apparently caused some undesireable print statements
from the kernel on other platforms.
An alternative may be to fix this in the ASPEED watchdog driver, though
I'm not sure what all that would entail or if it even makes sense.
Tested: Expire and start the watchdog multiple times and the fans now go
to full speed each time the watchdog expires, unlike before.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I770c4fd7cca15949abd7de9dc07975562080f032
|
|
This enables the TPM driver in the kernel configuration.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: I0278543d753c7526d14eb971ac678ff364719d49
|
|
This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the future.
Change-Id: Iea12e1691dbdda34a3f95d6d0862add0b15bcf37
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the future.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: Iaf709343b966c39ca707a10ef57fa0010bf6eb6f
|
|
strace(1) is a highly effective utility that allows for inspection of
the execution of a program through its interactions with the kernel.
strace can be used to extract syscall, data and timing information and
does not require any change to the running applications or firmware
image.
https://www.man7.org/linux/man-pages/man1/strace.1.html
Change-Id: I431f5ea6246a47fba259cc5af0cdc932b38be111
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
gdbserver can invoke or attach to running processes to expose a network
interface for a remote gdb connection. From there the instructions for
remote debugging in the Poky Reference Manual can be used to inspect the
state of processes on the BMC at runtime:
https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins
Change-Id: I8a54d642955da8f2491b77553c81e8b63452901c
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
The kdump effort has been set aside in favour of the lighter-weight and
better supported use of ramoops to capture debug data.
Change-Id: I4439a159a9783a2ff0e7335dd7efead3d82e0bc7
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Ben Pai (1):
Modify OWNERS file
Change-Id: I323eba87ed91fec6dba524f2a71528e24e907d68
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Witherspoon is running tight on space, and as our primary hardware CI
machine, we need to keep it going.
croserver can still be loaded into /tmp and run when needed
Tested:
- Reduced image size by ~100KB
- Will rely on CI to regression test
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I49b375d32462f0564b8310b430394077d0e887ed
|
|
Change-Id: Ifca5f828e58b6f86f4c7fe11544b50ff5f754702
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Tested By:
Was able to sucessfully build post-code-manager using meson
& was able to see that the daemon is working as before on a
BMC.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I4cf90fc8bf0a3350b944d5ef94fa131cb6f1c35f
|
|
Witherspoon is running tight on space, and as our primary hardware CI
machine, we need to keep it going.
The GUI has already been pulled out so the KVM package doesn't make much
sense anyway.
Tested:
- Reduced image size by ~200KB
- Will rely on CI to regression test
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I3e55702da764e4e1ca1673e158c7acf4f74c9bda
|
|
phosphor-led-manager already has platform and partition system attention
indicator D-Bus objects implementing xyz.openbmc_project.Led.Group. but,
was not added to association json which this commit is doing.
Signed-off-by: Lakshminarayana R. Kammath <lkammath@in.ibm.com>
Change-Id: I3803cbb2d07626e3af6474ea8e74d987f4a963b0
|
|
Make altitude sensor visible via redfish, chassis, all-sensors.
Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: I7e032e74ad8889e7e80e197dccc7b65a26482c0a
|
|
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required.
As it said by Yocto documentation it can be used by `Hob`
https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that already removed since Yocto-2.1
https://www.yoctoproject.org/tools-resources/projects/hob
Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
|
|
Earlier enclosure_identify and enclosure_fault associations were missing in the inventory manager.
With this checkin we are adding those associations.
busctl get-property xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory/system/chassis xyz.openbmc_project.Association.Definitions Associations
a(sss) 24 "fault_led_group" "fault_inventory_object" "/xyz/openbmc_project/led/groups/enclosure_fault" "identify_led_group" "identify_inventory_object"
"/xyz/openbmc_project/led/groups/enclosure_identify" "chassis" "inventory" "/xyz/openbmc_project/inventory/system/chassis" ....
After closely looking into all the LED's it was identified that
enclosure_fault and enclosure_identify is missing in the association
and this commit is to enable same
Signed-off-by: Lakshminarayana R. Kammath <lkammath@in.ibm.com>
Change-Id: I42728d994e9110c56c607aeea98623fe2613af92
|
|
Dumps are disabled by default. This commit enables
the dump feature for ibm based systems.
Tested By:
* Dump flag enabled:
GET https://${bmc}/redfish/v1/Managers/bmc/LogServices
{
"@odata.id": "/redfish/v1/Managers/bmc/LogServices",
"@odata.type": "#LogServiceCollection.LogServiceCollection",
"Description": "Collection of LogServices for this Manager",
"Members": [
{
"@odata.id": "/redfish/v1/Managers/bmc/LogServices/Dump"
}
],
"Members@odata.count": 1,
"Name": "Open BMC Log Services Collection"
}
* Dump flag disabled:
GET https://${bmc}/redfish/v1/Managers/bmc/LogServices
{
"@odata.id": "/redfish/v1/Managers/bmc/LogServices",
"@odata.type": "#LogServiceCollection.LogServiceCollection",
"Description": "Collection of LogServices for this Manager",
"Members": [],
"Members@odata.count": 0,
"Name": "Open BMC Log Services Collection"
}
Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
Change-Id: Iad5a364ac46b5bf62bc2186eb29786454f650802
|
|
Added "ipl" dependency to enable libphal library usage
in phosphor logging.
libphal library provides C++ wrapper functions for phal based
libraries provided API.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I754cc549af7af56e7026aaf0bea079ea562b84c2
|
|
`eslint` reported an issue with the supplied JSON and it appeared to
be missing a simple comma to separate two values in an array.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I2dd167143ea31c730c26254b3ddc2ad25109e34f
|
|
Manojkiran Eda (1):
Add OWNERS file
Change-Id: Iadf9a75728ff8321a6745d843abe649adbb6cf19
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
This recipe adds SBE UserData and SRC parsers in BMC
images for use by peltool.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ia6d3e2296fa1b874341eeade3e518de1576e0e98
|
|
Manojkiran Eda (1):
Add OWNERS file
Change-Id: Ic4bc0b1c8e3913db8406a0ec75cb28327a41230b
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Manojkiran Eda (1):
Add OWNERS file
Change-Id: Icb83eac96a7ab1a9e57439768ef3b5dc685ef43e
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Modify the machine meta-layer configs to remove the use of the
OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES
variable instead.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e
|
|
OBMC_MACHINE_FEATURES is a variable that probably shouldn't even exist
as all it does is provide a level of indirection to the real
MACHINE_FEATURES (in phosphor-base.inc, OBMC_ is added to the base).
There are a few recipes that have developed checks against
OBMC_MACHINE_FEATURES for enabling recipe-level features when they
should be checking the standard MACHINE_FEATURES variable. Clean up
this recipe-level indirection.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id437b93aa6c1de9a27726eea9b7e2c30e71ab3bf
|
|
openpower-pnor-code-mgmt: srcrev bump 9c2ef681e3..6fc7fcd6b1
Adriana Kobylak (2):
Add a new pldm feature option
Add support for the host PLDM transport that takes place of hiomap
(mboxd). Add this new feature to p10bmc.
Tested: Verified that tacoma (that doesn't support pldm) and p10bmc
(supports pldm) reached runtime.
Change-Id: I31e8beba5ff8a413b7b7fa7476f5f2403d3781dd
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Change-Id: Ic02f28215c02caf9d00d339b3b0643e990b83598
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
|
|
This tells phosphor-virtual-sensors to look on D-Bus for a virtual
sensor config of type ModifiedMedian. This way we can use the same
recipe for different hardware configurations.
Change-Id: I3ebd0a636f07a0854251e06b952ad9646f12f637
Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
|
|
Patrick Williams (1):
catch exceptions as const
Change-Id: I52b8b7321a4051ea327a1b3e245269e4cdeb8a7f
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Hostboot utilizes inband IPMI on witherspoon-tacoma. They relied on OPAL
firmware to continue pinging the watchdog and eventually disabling it.
For the most part though, IBM utilizes PHYP on witherspoon-tacoma
machines and they do not have the needed in-band IPMI support to do
this.
IBM needs either both firmware stacks (hostboot and PHYP) to use PLDM
(i.e. p10bmc) or IPMI (witherspoon). Tacoma is an outlier so just
disable the host watchdog function on Tacoma.
Tested:
- Verified a witherspoon-tacoma with PHYP booted successfully
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ibceb2ad6933973b97e122b83c89f6be7e7b8f868
|
|
The dependency is required to be the base name of the service file path,
otherwise we see:
```
Jan 01 00:00:33 p10bmc systemd[1]: /lib/systemd/system/obmc-led-set-all-groups-asserted@.service:3: Failed to add dependency on xyz.openbmc_project.LED.GroupManager, ignoring: Invalid argument
Jan 01 00:00:33 p10bmc systemd[1]: /lib/systemd/system/obmc-led-set-all-groups-asserted@.service:4: Failed to add dependency on xyz.openbmc_project.LED.GroupManager, ignoring: Invalid argument
```
Change-Id: Ide813cb3298e7f815b5f42b82473ab2a434193f7
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
The `witherspoon-tacoma` machine utilizes the same JSON config files as
the `witherspoon` machine so override the PKG_DEFAULT_MACHINE variable
for tacoma to be set to the witherspoon machine name "witherspoon". This
will then install the witherspoon machine JSON config files into the
tacoma image.
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I6ce40547ebe536ca149930c439b0ee21d66061fb
|
|
The documentation for CONFIG_PSTORE_CONSOLE indicates the following:
"pstore will log all kernel messages, even if no oops or panic happened"
This causes a console-ramoops-0 to appear in /var/lib/systemd/pstore/ on
any BMC reboot. This in turn causes phosphor-debug-collector, which
monitors for any files in this directory, to generate a BMC dump with
the file. This is not what we want.
What we really need are the dmesg-ramoops-* files which are generated
when a kernel panic or oops occur. Remove the CONSOLE setting so we only
get dumps when an actual BMC failure occurs.
Tested:
- Verified that console-ramoops-0 file no longer appears in
/var/lib/systemd/pstore/ after a BMC reboot.
- Verified we still get needed dmesg-ramoops-* files when a kernel panic
occurs.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6b48a8715946b193257bcc4892e07f87c13c95e6
|
|
The Rainier and Tacoma using of both virtual UARTs provided by the
AST2600. Expose them both to the network via obmc-console.
where ttyVUART0 Exposer name is @obmc-console
and ttyVUART1 Exposer name is @obmc-console.guests
@obmc-console.guests initial exposed to access to phyp guests over that
interface that why its name is guests, but now we are using that
socket-it to run PHYP debug shell.
So it is good to change the name of that exposer socket-id "guests" as
"hypervisor".
Signed-off-by: Abhishek Patel <Abhishek.Patel@ibm.com>
Change-Id: I47dc71095795afbda8fb544fde4bcae78712093a
|
|
With commit c184a0f08, the phosphor-hwmon instance for the max31785 fan
control device no longer waited for the cooling-type application to
finish before starting. Since the fan control service depends on the
phosphor-hwmon instance, it is now starting earlier than before, before
cooling-type, which was causing a crash.
To fix this, add the cooling-type dependency into the witherspoon fan
control service file.
Tested: Can see in the journal that fan control now starts after
phosphor-cooling-type, and it doesn't crash on a genesis reboot when the
inventory had previously been cleared.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I4bf9d8eb7f39acea71b790a61edfe1e8c4dae788
|
|
There is an upcoming systemd change that doesn't handle what was being
done, which was to delay starting phosphor-hwmon from udev until the
chassis cooling type was on D-Bus.
This commit removes this method and goes down to a single hwmon config
file that only supports the air cooled system, which has 2 more fan
rotors than the water cooled one does.
This change also applies to the similar systems witherspoon-tacoma and
swift.
Resolves openbmc/phosphor-hwmon/#19.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ic4ed46a5bf310fb1fef8704dcafc0376c441f8c4
|
|
After over a year of discussion, Redfish released new power and thermal
schemas as part of the Redfish 2020.4 release.
These new powersubsystem, thermalsubsystem, fan, powersupply, etc
schemas can co-exist with the old power and thermal schemas.
The old schemas and the new schemas are controlled by different options.
The current plan for bmcweb is:
1. Until the new schemas are all in and tested, as a default, enable the
old schemas and disable the new.
2. After the new have been in and tested, enable them. This means the
old and new will co-exist if running the defaults. The sensor
collection behavior will reflect the new schemas, that is all sensors
can be found under the sensor collection.
3. After an OpenBMC release, at a later time, disable the old and add
appropriate deprecation.
This change here, enabling the new schemas, jumps meta-ibm to #2.
This reflects our desire for our Redfish clients to start using the new
schemas.
Some reasons why the ThermalSubsystem/PowerSubsystem are an improvement
on the existing Thermal/Power schemas:
1. They include the latest properties like LocationIndicatorActive.
2. Fans, PowerSupplies, Temperatures were arrays in the old schemas.
This was cumbersome and could hit limits of JSON arrays.
3. Large amount of static data mixed with sensor readings, which hurt
performance in certain cases.
4. Inconsistent definitions of properties vs newer schemas like Processor
and Memory schemas.
Reference:
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2020.4.pdf
Tested: Built bmcweb. See the new sensor behavior.
Change-Id: I9a698cbc162a331c21c7dc5138000faac6247f9b
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d
|
|
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the
choice is functionally arbitrary for image generation but control over
the package format becomes important if we want to:
1. Include runtime package management functionality in the firmware image
2. Mess about with the packages on the build system
With respect to 1 the IPK format and opkg (an ipk package manager) are
designed for embedded systems[1] - by contrast to RPMs have heavier
dependencies and a greater impact on the size and complexity of the
firmware image.
Regarding 2, the embedded nature and the need for opkg to work without
much fuss leads to a lower configuration barrier by comparison to RPMs.
With ipk it becomes possible to reuse the packages built during image
preparation for core analysis without needing to generate an SDK:
```
$ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib
$ MY_DEBUG_ROOT=tmp/rootfs-debug
$ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \
-o $MY_DEBUG_ROOT \
update
$ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \
-o $MY_DEBUG_ROOT \
install dbus-sensors dbus-sensors-dbg
$ gdb-multiarch
(gdb) set solib-absolute-prefix .../tmp/rootfs-debug
(gdb) add-auto-load-safe-path .../tmp/rootfs-debug
(gdb) file tmp/rootfs-debug/usr/bin/nvmesensor
(gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000
Core was generated by `/usr/bin/nvmesensor'.
Program terminated with signal SIGABRT, Aborted.
pthread_kill.c:45
45 pthread_kill.c: No such file or directory.
(gdb) bt
pthread_kill.c:45
../sysdeps/posix/raise.c:26
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
"xyz.openbmc_project.NVMeSensor", this=0x488f04) at
/usr/include/sdbusplus/bus.hpp:234
../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159
(gdb)
```
This approach documented in the Poky Reference Manual:
https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins
Switch all machines to IPK to align the debugging experience with
upstream's documentation and to facilitate efficient use of packaged
software at runtime.
[1] https://openwrt.org/docs/guide-user/additional-software/opkg
Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
This feature is not needed on p10bmc systems and causes unwanted probing
of i2c hardware and journal entries.
Tested:
- Booted p10bmc machine and made sure it still worked as expected
and no new errors arose
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Idff2477060f5719ad85529daff28ef945e77700e
|
|
This reverts commit bcc5f6b0f24e8ad0b03b8217e88a19ff3002c084.
bcc5f6b0f24e ("Override pldm response time out value") talks about
timeouts due to the endpoint taking some time to respond. However, the
net effect of the change is the response to a retried request races
against the instance ID expiration interval because the retry interval
is effectively equal to the instance ID expiration interval once we
account for some timer slack.
This is demonstrated by the following strace on pldmd, where we can see
a retried request go out, followed by the report that the request
failed, further followed by the response to the request coming in. Note
the values are string-literal-escaped-octal, so the [ 0x80 0x00 0x03 ...
] byte encoding of the GetPLDMVersions request appears as "\200\0\3...":
```
...
11:56:25.046173 socket(AF_UNIX, SOCK_SEQPACKET, 0) = 3
...
11:56:25.183936 connect(3, {sa_family=AF_UNIX, sun_path=@"mctp-mux"}, 11) = 0
11:56:25.190994 write(3, "\1", 1) = 1
...
11:56:25.195272 sendmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\t\1", iov_len=2}, {iov_base="\200\0\3\0\0\0\0\1\0", iov_len=9}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, 0) = 11
...
11:56:30.202298 sendmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\t\1", iov_len=2}, {iov_base="\200\0\3\0\0\0\0\1\0", iov_len=9}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, 0) = 11
11:56:30.202820 gettid() = 1918
11:56:30.203029 timerfd_settime64(6, TFD_TIMER_ABSTIME, {it_interval={tv_sec=0, tv_nsec=0}, it_value={tv_sec=3848, tv_nsec=61124978641398328}}, NULL) = 0
11:56:30.203286 epoll_wait(4, [{EPOLLIN, {u32=14373240, u64=14373240}}], 14, 0) = 1
11:56:30.203509 clock_gettime64(CLOCK_REALTIME, {tv_sec=1629806190, tv_nsec=203587376}) = 0
11:56:30.203687 clock_gettime64(CLOCK_MONOTONIC, {tv_sec=3843, tv_nsec=523046301}) = 0
11:56:30.203844 clock_gettime64(CLOCK_BOOTTIME, {tv_sec=3843, tv_nsec=523206110}) = 0
11:56:30.204049 write(2, "Response not received for the re"..., 59) = 59
11:56:30.204427 write(2, " EID = ", 7) = 7
11:56:30.204745 write(2, "9", 1) = 1
11:56:30.205047 write(2, " INSTANCE_ID = ", 15) = 15
11:56:30.205389 write(2, "0", 1) = 1
11:56:30.205719 write(2, " TYPE = ", 8) = 8
11:56:30.205997 write(2, "0", 1) = 1
11:56:30.206266 write(2, " COMMAND = ", 11) = 11
11:56:30.206576 write(2, "3", 1) = 1
11:56:30.206893 write(2, "\n", 1) = 1
11:56:30.209402 write(2, "Failed to receive response for ", 31) = 31
11:56:30.209814 write(2, "getPLDMVersion command, Host see"..., 46) = 46
11:56:30.210969 gettid() = 1918
11:56:30.211171 timerfd_settime64(6, TFD_TIMER_ABSTIME, {it_interval={tv_sec=0, tv_nsec=8549172174085160960}, it_value={tv_sec=0, tv_nsec=8566510441663037440}}, NULL) = 0
11:56:30.211406 epoll_wait(4, [{EPOLLIN, {u32=14373240, u64=14373240}}], 14, 0) = 1
11:56:30.211640 clock_gettime64(CLOCK_REALTIME, {tv_sec=1629806190, tv_nsec=211720512}) = 0
11:56:30.211825 clock_gettime64(CLOCK_MONOTONIC, {tv_sec=3843, tv_nsec=531188829}) = 0
11:56:30.211983 clock_gettime64(CLOCK_BOOTTIME, {tv_sec=3843, tv_nsec=531335706}) = 0
11:56:30.212143 recv(3, NULL, 0, MSG_PEEK|MSG_TRUNC) = 15
11:56:30.212366 recv(3, "\t\1\0\0\3\0\0\0\0\0\5\361\361\360\0", 15, 0) = 15
```
That is, at 11:56:30.202298 we send out the retry for the request
initiated at 11:56:25.195272 and the reply arrives back at
11:56:30.212366, but in between we've already cancelled the request
handler due to the instance ID interval timer expiring.
Resolve this by removing the explicit configuration of the
response-time-out build parameter setting the per-request response time
to 4.8 seconds, setting its value back to the default of two seconds.
Anecdotal testing of with the following shell script produced no
failures (by inspection of the journal as the iterations executed):
```
for i in `seq 1 30`; do echo $i; ( systemctl stop pldmd mctp-demux && echo 1e78902c.kcs > /sys/bus/platform/drivers/ast-kcs-bmc/unbind && sleep 1 && echo 1e78902c.kcs > /sys/bus/platform/drivers/ast-kcs-bmc/bind && systemctl start pldmd && sleep 15 ) || break; done
```
Change-Id: Ide125d686e79376b412fca0105449c8bef722cfe
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
The `p10bmc` machine's JSON config files should now use the JSON config
files installed from the repository.
Change-Id: Ibd9bbc055e4d00a5f799a291e9fd3a9955d774c5
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
The `witherspoon` and `p10bmc` machines' JSON config files should now
use the JSON config files installed from the repository.
Change-Id: I47669745aa7047c4de64ee8aedc98437593a3b62
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
The `witherspoon` and `p10bmc` machines' JSON config files should now
use the JSON config files installed from the repository.
Change-Id: Ie40264435ca5278a50f2aa3c688d882d72cb376b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
All IBM systems support the SNMP trap notification for error logs. This
means phosphor-dbus-monitor needs to be careful to not start until the
SNMP service is up and running.
Without this dependency, situations can be hit, when lots of errors are
present, where the phosphor-dbus-monitor calls into the SNMP shared
library and hits an unhandled exception when trying to talk to the SNMP
service.
Tested:
- Verified the unhandled exception is no longer seen and
phosphor-dbus-monitor starts after the SNMP service.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8b4ca94c0cdd7721aa8847dc478f3827f040a654
|
|
To build webui-vue with IBM theme, need to set IBM environment variable
during the webui-vue build.
Yocto has many layers of abstraction. To specify IBM environment
variables, we use --mode npm build Commandline argument, which helps to
set IBM environment variables.
We need to set this environment variable during IBM build only. So
created webui-vue_%.bbappend file, which sets that env variable only
for IBM builds.
More information could be found at
https://github.com/openbmc/webui-vue/blob/master/docs/customization/build.md
Tested with IBM build.
Signed-off-by: Abhishek Patel <Abhishek.Patel@ibm.com>
Change-Id: I6ff997a94eb59b695741ccca95acb7693a4714ff
|
|
Adriana Kobylak (1):
oem: ibm: Add services to reset PHYP NVRAM
Tom Joseph (1):
tools: Extend pldm_fwup_pkg_creator
Change-Id: I9dce25f3137a938c84dd080eaa8f37aa5a5147eb
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
- In this patch, added a setting to enable or disable the
HardwareIsolation (aka Guard) in the OpenPOWER based system.
- By default, the setting is enabled, that's means the
HardwareIsolation feature is enabled for the IBM system so,
the respective BMC components need to take care of the
functionality based on the roles of each application usage
by using this setting if needs.
Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: If03c98b74f5bc26941ddc825cde81ea307518742
|