| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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 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>
|
|
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
|
|
We're about to introduce a package for mctp utilities, called 'mctp'.
However, the libmctp package already uses that name.
This change renames 'mctp' to the upstream name of 'libmctp'.
Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Change-Id: Ia49a40c822e920d3bc36584cbc2c97b83828cfdd
|
|
In the spirit of consistency with the new upstream override
syntax, change phosphor-discovery-service.bbclass to use it
and make tree-wide changes as appropriate.
After the change checked on Witherspoon on QEMU:
```
root@witherspoon:/etc/avahi/services# ls
obmc_console.service obmc_redfish.service obmc_rest.service
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib1fe3cce57a0130378af789abd83b457e0c3a318
|
|
Matt Spinler (1):
Switch SdBusError to generic sdbusplus exception
Change-Id: I9fad0117559672b860270d86fb2538b649b3ee28
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Witherspoon systems are currently used for CI. Currently, CI does not
test the webui. This change will affect Swift systems, as swift.conf
requires witherspoon.conf.
Additionally, removing phosphor-webui saves us 397 kB in filesystem sz.
Built up-to-date images to see the size of the rootfs.squashfs-xz
The size of obmc-phosphor-image-witherspoon-<date>.rootfs.squashfs-xz:
1) With webui-vue: 19.836928 MB
2) With phosphor-webui: 19.78368 MB
3) Without either (i.e. this change): 19.386368 MB.
Testing using commit 7d637776938c77d69752a72a09edc90ebde93164:
1) Code update successful on hardware system.
HW system updated image and rebooted successfully
Signed-off-by: Ali Ahmed <ama213000@gmail.com>
Change-Id: Ib2488dd462851b98f557dd9c76086d48dcbe905c
|
|
Upstream bbclasses changed to typically use the `:${PN}` override
syntax, including the SYSTEMD_ variables. Change our systemd.bbclass
to do the same for consistency and perform a tree-wide variable
replacement.
Spot checked by building bletchley and witherspoon and checking
some of the SYSTEMD_LINK directives on installed packages under qemu.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
|
|
Testing:
Built image for p10bmc platform, installed on a test system,
and verified netipmid was started on both eth0 and eth1
interfaces. Also, verified that ipmitool commands work as
expected for IP addresses configured on eth0 and eth1 interfaces
Signed-off-by: Shantappa Teekappanavar <sbteeks@yahoo.com>
Change-Id: Ie8399ba1219dac2f9c4ac15b7dfcf7e746750f0d
|
|
Use nonarch_base_libdir instead of base_libdir, because the files are
always in /lib/udev/rules.d/. On ppc64le base_libdir is lib64, and the
files end up in the wrong spot.
Signed-off-by: Anton Blanchard <anton@ozlabs.org>
Change-Id: I3c24dae293f4166f1ed1826d09d4bde7cd7d0357
|
|
The hostboot dump collection initiated by watchdog_timeout
is disabled by default. This commit enables hostboot dump
collection on p10bmc platforms for watchdog timeout.
Build watchdog_timeout binary:
$ devtool modify -n openpower-debug-collector <local-source-path>
$ MACHINE=p10bmc bitbake openpower-debug-collector
Test:
Ran watchdog_timeout binary built by bitbake, and verified that
the binary takes the timeout value and times out after the specified
time interval
Signed-off-by: Shantappa Teekappanavar <sbteeks@yahoo.com>
Change-Id: I343aac95fd97feb226d8676c3c34c2902c1c6690
|
|
Running out of flash space on our witherspoon system so need to cut
back some function. Telemetry is fairly new and takes a sizeable chunk
of flash space (200KB)
Tested:
- Verified squashfs went from 19.20MB to 19.00MB with this change
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I1741649f573cd25363167d69b4a802f2f261d93a
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iadecbc8418d901f82fcc741d3e88d2d202fe96fe
|
|
Update with the latest version from upstream.
Change-Id: I1a7da37b0457dab873afaf6445aca360d54b47ca
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
This commit is add D-bus monitor config.yaml
for errorlog entries for snmp eventing.
Tested by:
Configured SNMP and created errorlog
observed snmp traps recieved on SNMP server
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
Change-Id: I59c1f8a3b03eb3aab4a55c3cfb0bfb3e9e600a4d
|
|
This commit would override response time out value for a request
to 4.8 seconds for all the ibm machines.
We have seen in our debugging that in rare cases host takes close
to 5 seconds to respond to the pldm message.This value (4.8 seconds)
is in sync with what phyp maintains for their messages(5 seconds).
As we do lot of fileIO operations, and the number of PDR's tend to grow,
picking 4.8 seconds seems to be less risky path & also larger timeout
would reduce the number of retries from BMC incase if the host does not
respond within 2-3 seconds.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ic0eac42b66dbc2c6d69bff440fe590775f35e390
|
|
Background:
OpenBMC provisions the BMC firmware image with the root account password
in a form which is no longer acceptable to Linux-PAM version 1.5.1.
Specifically, [phosphor-defaults.inc][] sets the password hash into
/etc/shadow as "\$1\$UGMqyqdG\$FZiylVFmRRfl9Z0Ue8G7e/", where $1
indicates the deprecated [MD5 hash algorithm][]. Ref: [wikipedia passwd
entry][]. Beginning around PAM version 1.5.1, when you log in, the
[pam_unix.so module][] authenticates okay but requires the password to
be changed. (For example, you'll get a message like "You are required
to change your password immediately (administrator enforced)." This
behavior is undesirable for OpenBMC project defaults, and is not
tolerated by the project's current continuous integration tools.)
This change is to replace the password hash to keep the same cleartext
password but hashed with an acceptable algorithm.
Specifically, the password hash supplied in phosphor-defaults.inc is
updated to use the same password as before but encoded
with the SHA-512 algorithm. The hash was generated by the
`openssl passwd -6 0penBmc` command. This change ought to be
transparent and forward and backward compatible.
Note various meta-layers use this same hash string in
conf/local.conf.sample files. They are changed to match.
References:
[phosphor-defaults.inc]: https://github.com/openbmc/openbmc/blob/1a977b269ed437bebb9ae7810e3157746ec9174d/meta-phosphor/conf/distro/include/phosphor-defa
ults.inc#L245
[wikipedia passwd entry]: https://en.wikipedia.org/wiki/Passwd
[pam_unix.so module]: https://github.com/linux-pam/linux-pam/tree/master/modules/pam_unix
[MD5 hash algorithm]: https://en.wikipedia.org/wiki/MD5
Tested:
Created image with new password hash and PAM 1.5.1 and checked that
login works okay and does not require the passwod to be changed.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
Change-Id: I5b189374f08ba506dbed7f8b9b991f2808cc3bc5
|
|
Background: The OpenBmc project default root account password is set
in meta-phosphor/conf/distro/include/phosphor-defaults.inc and can be
customized in each layer's local.conf file.
Many of these local.conf.sample files had redundant code to set the
password, which probably should not have been there. Removing them
allows the defaults in phosphor-defaults.inc to take effect.
Tested: No. Only meta-ibm was tested.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
Change-Id: I76dce00d269d7afa005d7bcfd63f846d3cf45596
|
|
Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com>
Change-Id: I62027c739eb4cf95bb1bfc8ccddec30964bb1906
|
|
The phosphor-gpio-presence application is no longer needed for power
supply presence detection after the updates to using libgpiod in the
phosphor-psu-monitor application.
Remove the systemd parts of the bbappend, and remove the obmc conf
files.
Signed-off-by: B. J. Wyman <bjwyman@gmail.com>
Change-Id: I18a7f36e21d18a22f7625aadc3229ce5439c8d6a
|
|
Change Ie1a7c389edb6b7a048836a49283ceb62de51bba5 will be transitioning
the 'Type' property in Inventory.Item.Chassis to an enumeration.
In order to avoid crashing in PIM we need these default values in the
starting YAML to be fully-qualified enumeration names that will match
the values which will start in Ie1a7c.
This code is safe to merge as is without any PDI or PIM changes. Prior
to the PDI change, we must make a change to PIM that allows conversion
automatic from string->enum, leveraging library interfaces available in
sdbusplus. These will be submitted independently.
I checked the codebase for usage of this string. It appears that the
value is currently, effectively, write-only. There is code in bmcweb
that fills in the equivalent Redfish value but currently just hard-codes
the string 'RackMount'.
Tested: Booted Witherspoon in a QEMU model with this change and proposed
changes to sdbusplus + PIM. PIM no longer coredumps with the PDI change
and yields an expected persistence file:
```
$ pwd
/var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis
$ cat xyz.openbmc_project.Inventory.Item.Chassis
{
"value0": {
"cereal_class_version": 2,
"Type": 3
}
}
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icaf9447f31ccdd945cdf74b3e017682e4aed686f
|
|
Change-Id: Iac6362f744113d9a405e4a4ec30077e513dda2d3
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
As for Rainier and Everest, use KCS2 as the debug-trigger interface.
Change-Id: I2614ffc3d97164658f2ad4fbb916cbf44be152e1
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Witherspoon uses a specialized phosphor-fan-control@.service file and
uses the phosphor-fan-control-init@.service file still to just set the
fans ready target. To correctly be included in the FILES directive,
these services need to be explicitly added on wiherspoon machines.
Change-Id: I76129a7833337aaf74fd83b0e28f3083f1a41b0a
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
- ddimm
- capi connector
- nvme
- pcie slot
- pcie cable card top and bottom enclosures
- base op panel
Signed-off-by: Lakshminarayana R. Kammath <lkammath@in.ibm.com>
Change-Id: I7de498f83ab3bace4ce39deb98c31c71c40f2dd4
|
|
MaxBootCycleCount is a dbus property that is used to indicate
the maximum number of boot cycles that the post-code-manager
daemon can store the progress codes for, before it starts
wrapping.
Unlike Intel postcodes, IBM progress codes are huge and it is
possible to get close to 230+ progress codes per boot cycle, so
tweaking this value to 5 boot cycles for IBM systems so that
we can get less number of log entries on a redfish GET request.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ida10e73992b01535d57c844d83366d786cd448e2
|
|
The Altitude measurement is from the computation of
the DPS310 pressure sensor with this
"Expression": "44330.0 * (1.0 - ((P0/101325.0) ^ (1/5.255)))"
Tested: busctl introspect xyz.openbmc_project.VirtualSensor \
/xyz/openbmc_project/sensors/altitude/Altitude returned
results consistent with location of the Rainier system.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: I07b83dd6b8f4ccf0755ccbdc81c40976a3e571cd
|
|
Phosphor logging PEL infrastructure provide supports to
process SBE chip-op failures and creating PEL.
PEL creation required to process SBE provided FFDC packets.
This FFDC is initially created by SBE using FAPI based
infrastructure for the hardware procedure execution failures.
To extract this data to convert into PEL required format
requires additional processing. This processing required
PHAL(Power Hardware Abstraction layer) based back-end
support.
Added required packages support for PHAL feature enabled
systems.
Test: verified build.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I5cf1a30514aa0a5bfdf2fe3a288dac9d5a0b5b47
|
|
Install the udev files to cover the transition between drivers and
devices.
Change-Id: I87ffe3ae82bb7a073a8140adcb308b09fc43c9b9
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
libmctp provides the MCTP implementation for communication between the
host and the BMC.
Change-Id: I6ae5a23fbb34c27db16a152afefb79ca6a649759
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
These were separated in a strange fashion. Perhaps we should reorganise
the whole file in platform-specific sections.
Change-Id: I51b8bb20060447c6e88557824e9465b1713f082f
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Change-Id: Ic1cde1cd67fa6f8f68df80a1f327ace64a39d72b
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Change-Id: I4453f9b01f986a529c76710d665ab57639232b2d
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
|
|
It's been found that the processors are generating more preheat than
anticipated and the rainier 4u systems currently being built may not
have the baffles available to be installed. Increasing the poweron fan
speed to overcome this preheat affect to the PCIE area so PCIE cards do
not overtemp.
Change-Id: I03414fc4cc9cd3aa8d248c4b1408bab658978f48
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
p10bmc systems have their own checkstop monitor, provided by the
openpower-hw-diags package. Having both installed on p10bmc systems is
wasteful and has shown some intermittent issues (checkstop-monitor
service core dumping when checkstops occur).
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I118b359bf551e6502086800a9081ca8856ecf4ae
|
|
The IBM host firmware team has requested an initial timeout of 10
minutes for the host watchdog. The goal is to bring this down once
bringup is complete.
When inband IPMI was used, there was a mechanism for the host to adjust
this timeout so the BMC firmware would set the initial 30 second timeout
and the host firmware would change it to 10 minutes once they started.
With PLDM there is no way for the host to adjust this timeout so we need
to start with the larger value.
Tested:
- Verified a p10bmc image had the new poweron file installed with 10
minute timeout.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If94766d5f2d62271c4adf366631f0b31a75ef8d0
|
