Age | Commit message (Collapse) | Author | Files | Lines |
|
At a high level, the purpose of this feature was to utilize the BMC
hardware watchdogs to switch the BMC boot flash when certain errors were
hit which were preventing the BMC from booting.
At a high level, this worked but some critical issues were found with
this:
- No failure data is gathered to understand why the boot flash was
switched
- No event or error is logged to notify the user of the system that the
boot flash has switched
- At times, switching sides didn't help because the BMC network
information was not properly copied to the other boot flash which
caused even more confusion for the user
Give the above, this patch proposes a reset on this logic until we can
come back and address the above issues and get this working end to end.
(From meta-ibm rev: d5069cffe865ea104915d8e0fdbe8d7d145644fc)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8c8d2b30c80940f4674e6c6848bd22f759e943a5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would enable the ibm-management-console compile-time
option for all the ibm machines.
(From meta-ibm rev: 9831b3a45141d4dc08b2624f07059299d65a9d7f)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I69abd87d28903d27d2390f20153d730f658f8068
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove executable permissions from the `70-max31785-hwmon.rules` file to
eliminate the systemd-udevd warning that its marked executable.
(From meta-ibm rev: 46984b5eda5c40e63cb9fab6aa5e667cec7f5b68)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ic7405ed73f2d7875c57696ae4e5b30e380502fd6
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
this commit is to enable hypervisor certficate manager feature
and install service for rainier and tacoma
(From meta-ibm rev: cf7a5811a21645a556b5e66433ce08ff67cf7cb2)
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
Change-Id: Ia38083851444134a55ff1b488f921b75cbd0d2e8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Enable OpenPower dumps on Tacoma and Rainier
(From meta-ibm rev: 0ce518f660df9490da3373dd64b580ea8672c93d)
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: Ic756ecbd793ca465ce3d6dc31ad93ac5170654d0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Similar to commit 567a8d for witherspoon, this issue has now popped
up on Romulus hardware.
The concept of warm reboot (reboot the host without removing chassis
power) was added a while back as a part of clarifying support for
the Redfish ComputerSystem.Reset Action. It has since been found that
some IBM hardware, including Romulus, do not support warm reboots.
The issue is intermittent and depends on the reboot being requested
while the host is in the middle of some i2c transactions. If a warm
reboot occurs during this window, then on the subsequent boot the i2c
hardware will be in a bad state and the host firmware is unable to
recover it.
Given this issue, it has been requested that BMC software go back to
doing cold reboots (cycling power to the chassis during any reboot
request) on this hardware.
(From meta-ibm rev: 718f2b5405c2c1f000cc0ccbf2860a283997c08a)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I31810e89977532d4368050871aba03d78deb9c59
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would switch the bmcweb options to meson
(From meta-ibm rev: fea636a8486e20e8ccd865670f56d34c9700a043)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ieda83403ff381c616664170462915198fdf30507
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: 03ff1fa3f6ce475760535c08dfea9b751aa71f65)
Change-Id: I17ddb7eef0853cb0a3ae23ab0f67043b931afc34
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
phosphor-dbus-interfaces recipe requires that we add to the
OBMC_ORG_YAML_DIRS, the directory paths where the interface
YAMLs reside. On IBM systems, we need com/ibm to be addded
to that list.
Tested: Built Witherspoon and Rainier images cleanly.
(From meta-ibm rev: 6f4a08414c5dcea760f75a402cc90a48b833a0aa)
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Ife7de39ff10a6ead641ccfe82c31481f5135a0f5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
witherspoon-tacoma systems do not utilize this feature
(From meta-ibm rev: b32849212c59c6383543ba769b8b4f6e2fbbc48b)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I59c5b19b6ad140447f5cdf4184db5acf251c2842
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This is wired as to do nothing on normal Witherspoons, so the code to do
so has questionable utility.
On Tacoma systems, the Witherspoon motherboard is reworked to allow the
BMC to control the reset. The control is provided as part of the FSI
driver in the kernel, so it should be removed from the userspace power
control tool.
Fixing this should resolve this message when doing poweron:
power_control.exe[250]: ERROR PowerControl: GPIO open error (gpio=BMC_CP0_RESET_N,rc=2)
The GPIO device can't be opened as the kernel has control of it.
(From meta-ibm rev: 5ef58e42bd2c27605cd952bf590b2879759425d8)
Change-Id: Id6889d8d889272a82c80b64ea3fa31ac4a464458
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
rainier systems do not utilize this feature
(From meta-ibm rev: dcfa1a4d7ad4065d983e3bf77cc88d5167492e9d)
Change-Id: I0a9b430c8245016237c0f168781ecf0b68438f96
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Build the u-boot and the SPL binary. The image_types_phosphor.bbclass
keys off these configs to concatenate them together into a single
file which is used during code update to update the device where
the SPL+U-Boot reside.
(From meta-ibm rev: 2e8a6ac2986dfbfc62139355cf663ec5161cb1b9)
Change-Id: Ia17635ef68c059bfa6fd937ac806c3f21fad8c84
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit will install the dump header script which
will create dump header and impose the same
on the dump.tar.xz file.
Header format will consist of the following:
-virtual file directory entry:
one file directory entry for BMC DUMP, which will have
file header and size of 40 bytes which consists of
system serial number, dump identifier, time stamp
of the dump.
-section directory entry:
This has SECTION as entry header, size is of 30 bytes
consists of total size of the dump along with other
details.
-dump header:
This has an eye catcher "BMC DUMP", dump
identifier, system serial number, system name etc.
-dump data table:
This will have dump version, dump valid
field and number of dump entries.
(From meta-ibm rev: 49710574e0e40b98d1b671b95568314838d55985)
Change-Id: I7906b6d602a8fd27655c90eb632ce55eaf8ab63a
Signed-off-by: Chirag Sharma <chirshar@in.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Mihawk cannot read the 250 soc sensor on the riser, this is because dts
defines pca9545riser@70 instead of pca9545@70.
(From meta-ibm rev: 731297ebde0eb4272d39260a30cd5f5b1f4e6f1a)
Change-Id: Ibcb72ef6be7c953cc35cc216e8cc45e283949e61
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Prior to this patch the Rainier system doesn't include any host
processor configuration. Rainier is a server with a host processor, so
include the correct host processor configuration.
(From meta-ibm rev: 5b44384b92419673b1ce7cca40c5dc613cc6d60a)
Change-Id: I3da77be772c3cd0f89539c8e56c5d0719ad84c44
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
It was found that the fan control services were constantly getting
restarted due to not failing within the previous start limits. After
experimenting with different combinations of limits, using the default
values for StartLimitBurst and StartLimitIntervalSec is sufficient.
Tested:
Changed limits, powered on, watched service fails in journal until
fan watchdog monitor started
Resolves: https://github.com/openbmc/phosphor-fan-presence/issues/23
(From meta-ibm rev: b8a65368cb39d6d82c4b025b25fdbe868dbbfe89)
Change-Id: Ibcb35028e8dbc67d7df70dfeee25d098e6041fe8
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The flags set by this bbappend are now handled automatically by the
phosphor-dbus-interfaces recipe.
(From meta-ibm rev: 73b735f30bb866b27e05fe6381064e5a9a55977b)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icf4e7beebaeea99ea74214989290d92ee4d006ee
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- meta-phosphor has bmcweb bitbake file under interfaces,so
moving the append files accordingly.
(From meta-ibm rev: b7952717a7c74b0ebda2d7971f75b1b060f8911c)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I86ba09396f109f0987220bcdd070a0fff8e1e972
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Leave the rest of the IBM AC Servers on phosphor-webui since things like
two file firmware update and Virtual Media are not currently supported on
webui-vue.
The hope is in the near future to move all IBM Servers to webui-vue,
including all ibm-ac-servers (e.g. Witherspooon).
webui-vue is a complete rewrite of phosphor-webui. It uses the Redfish
API, is translatable, themeable, does not suffer some the anti-patterns that
exist in phosphor-webui today and is built on Vue.
phosphor-webui was built on AngularJS and AngularJS goes End of Life June 2021.
Huge shoutout to the team here, webui-vue is an impressive GUI!
(From meta-ibm rev: 4d34f6c2bbde77d219d6a5ce306059661b80734c)
Tested: Built Witherspoon, see the AngularJS GUI.
Built witherspoon-tacoma see the Vue GUI.
Change-Id: I2d4ac657070b694381779a5bfe0bb8b202db97e3
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This application sets LEDs based on the contents of OpenBMC
event logs, and this will be done a different way on Rainier
and Witherspoon-tacoma so remove it.
(From meta-ibm rev: 553390e70165dc71f0efa3de074b497d998736e2)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I7831a225edc6382ee94b8c372ac6b2717bad172a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
For tacoma, adjusting the size of the eMMC image by making the
hostfw partition smaller.
(From meta-ibm rev: f12da2705f487a933cbf291c129d3832b91d1816)
Change-Id: Ic13d141d41ab513f2af7bff790efc7529739b11d
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This collects all of the PEL files on user and elog dumps.
They will show up in a subdirectory named 'logs' in the dump.
(From meta-ibm rev: 1a247b7c27ec3021bf7396874d34844ca2e6b033)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia23a2fb72acfc1e4473d3c47ad78e34b37529f34
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Implement power-sequencer of phosphor-power for mihawk.
(From meta-ibm rev: 65dbe8b7c2ed9507ea5842e6e91b637a9069b947)
Change-Id: I00ee20fbcfcd6dc34724c2f7caf50cf7ae94d124
Signed-off-by: Andy YF Wang <Andy_YF_Wang@wistron.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Mihawk can use up to eight 250-soc.
Tested:
The user can see the temperature when using 250-soc.
(From meta-ibm rev: 74b7557b08ed2582861cd7da390d84371ec2ff86)
Change-Id: I17b0d969d0902f6470287c6164f542ad84412f7d
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Fan control must support 250 soc thermal sensor.
Tested: Fan speed is automatically controlled when using 250 soc
(From meta-ibm rev: 05540e77d337f466bc339715153704edff3f6b88)
Change-Id: Ic17854a8556b5878bf506bfafd64762315390c39
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The concept of warm reboot (reboot the host without removing chassis
power) was added a while back as a part of clarifying support for
the Redfish ComputerSystem.Reset Action. It has since been found that
some IBM hardware, including Witherspoon, does not support warm reboots.
The issue is intermittent and depends on the reboot being requested
while the host is in the middle of some i2c transactions. If a warm
reboot occurs during this window, then on the subsequent boot the i2c
hardware will be in a bad state and the host firmware is unable to
recover it.
Given this issue, it has been requested that BMC software go back to
doing cold reboots (cycling power to the chassis during any reboot
request) on this hardware.
The issue has only been reported on Witherspoon so for now only disable
it on that platform.
Tested:
- Verified within QEMU that an image with this commit used the cold reboot
target during a warm reboot request
(From meta-ibm rev: 567a8dcf84dfb74e7bd27d6239be2878fcacdde6)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8d77c5e8bf7378a3d1accc79b510f14626a333e5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the D-Bus objects to enable the DHCP on the
hypervisor's virtual management interface.
New attributes are :
1. DHCPEnabled - At Interface level.
Values will be "v4/v6/both/none". Default is "none"
2. Enabled - At IPv4 object level : To indicate if the
Virtual Management Interface has consumed the IP
address or not.
Tested By:
1. busctl introspect xyz.openbmc_project.Settings /xyz/openbmc_project/network/hypervisor
2. busctl introspect xyz.openbmc_project.Settings /xyz/openbmc_project/network/hypervisor/eth0
3. busctl introspect xyz.openbmc_project.Settings /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0
4. On rainier : similar tests for eth1
(From meta-ibm rev: 988412a2463a58f85f50648f9497a8779203087e)
Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com>
Change-Id: I734347a8953cd11955eeaacfd67b815810587046
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds a new yaml file for holding the Hypervisor's
Virtual Management Interface's network objects.
This models two ethernet interfaces to the hypervisor and its
static IPv4 attributes.
Tested by:
busctl tree xyz.openbmc_project.Settings
(From meta-ibm rev: ae4ab28128052a57f8ddd4c910e27e04f92305d6)
Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com>
Change-Id: I9a32d943867d26fbf215f248ab944e6f8750f415
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-power updates for Rainier power supply VPD collection
introduces ibm-vpd configuration option. Use -Dibm-vpd=true for Rainier
builds.
See Change-Id: I431ae3ec8a9cb9c80a824029f110d5fd58a7d5d8
(From meta-ibm rev: 2f9e6a3b7be4ad5ff15344a6c63fa7577ccac6bf)
Change-Id: I14f9e573cc905fad72ea23c1195cb685f4be8c4c
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Use the installed `config.json` as the fan monitoring configuration to
load at runtime. This replaces the need of the build time YAML
`monitor.yaml` configuration.
Tested:
`monitor.yaml` removed from build image staging location
Built/powered on image using the `config.json` file
(From meta-ibm rev: 27be42e03193352d7c7ee51784448cb06d1b8e2c)
Change-Id: I80c268b26dddd820e7c9c640eab2d39452ab3a29
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: 2c67f194f16568dac0de6dbf965e823790440639)
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
Change-Id: Ib34136cd472803d01d398462814b14c0e876d52f
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
In prep for switching the witherspoon machine over to using a runtime
fan monitoring JSON configuration, install the configuration file into
the image now.
Tested:
Verified both `monitor.yaml` and `config.json` in phosphor-fan
Built/installed witherspoon image and config.json file present
Verified YAML config still used instead of present JSON config
(From meta-ibm rev: 36206800a699a1429d30ad32a36e4f960ac6c7b4)
Change-Id: I75d72a2731f201d37d38c9d436eff2af522bc6da
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This system will no longer be supported or maintained. Drop to minimize
cruft.
(From meta-ibm rev: 7c17e6a1f826cdfbbb39ffa3f237025e56fab52f)
Change-Id: Id954a1c91c754a1eb4eb67348c5fb01a115326ed
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
It was temporarily removed so that the commit that moves the IBM D-Bus
interface it uses from ibm-dbus-interfaces to phosphor-dbus-interfaces
could go in without getting compile fails.
The commit that removed it is bd17cae1d3a44f5fc82c4e037a91c97e092fcf57.
(From meta-ibm rev: a26d3db37979aaeab4343db41f5316425e9233e5)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia4463e27411c1075d36119e6121dc2163335d6e4
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The IBM D-Bus interfaces moved into phosphor-dbus-interfaces.
Also temporarily remove ibm-logging from every image so that
ibm-dbus-interfaces won't be pulled in and CI can work.
(From meta-ibm rev: bd17cae1d3a44f5fc82c4e037a91c97e092fcf57)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ic8bf9106592c7e7d161d928708554a91d5bb407e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- As per the commit merged in phosphor-networkd, the ibm-config
flag is now changed to sync-mac.
(From meta-ibm rev: 7bd9b4a226207205adf0093b7c64bc69f20ad1dc)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ia02e350ffa3ca42e56f3cac4b0dbc14980fab3b7
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit enables the ibm-config flag for phosphor-networkd
service while compiling for IBM machines.
- ibm-config compilation flag would enable the configurable
Inventory-Interface Mapping JSON for setting the corresponding
MAC Address that are obtanined from the Inventory on to the
respective ethernet interface(s) during the first boot.
(From meta-ibm rev: 4b0db6e07d3207e256f01f2f34d144aa93950224)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Fixed minor typo in commit message
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I31d284839969ea55f13165f5957c164b9b1f6ce8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit removes the first-boot-set-mac service as the
similar and a better functionaly is now implemented in
phosphor-networkd service.
- Here are the few disadvantages of the first-boot-set-mac service
1. The first-boot-set-mac is a script is not scalable with the
increase in the number of ethernet interfaces.
2. Why do we need a new service just for setting the MAC Address
when the network service alone can do it , and it makes sense
to tie up this feature with Network as setting MAC address
functionality is implemented and owned by networkd.
3. With first-boot-set MAC, we need to make sure the VPD is populated
before , if for any reason the VPD is not generated the first-boot
service cannot help set the MAC.
(From meta-ibm rev: 8638c6eb8d54507b632088b329c104e859cd8d19)
Signed-off-by: manojkiran.eda@gmail.com <manojeda@in.ibm.com>
Change-Id: I955834b56c28f9a311563dd40607c8f2ba305d40
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would enable a configuration JSON file, through which
one can map the inventory object paths to the actual ethernet
interfaces which are managed Network Service.
For Example:
- Lets say the Inventory path for a single ethernet Interface machine
would look something like below:
`/xyz/openbmc_project/inventory/system/chassis/motherboard/boxelder/bmc/ethernet`
Then the corresponding configuration JSON would looks something like below:
{
"eth0":"ethernet"
}
Note that the key (eth0) in the JSON is the actual ethernet Interface
managed by the Network Service, and the value (ethernet) is the search
pattern to be found in the Inventory Path String.
- The above JSON would help the phosphor-network service to look for a
match on the Interface Added signal under Inventory Path with an object
path that contains the pattern String ("ethernet"), and there it gets the
MAC address populated under the respective inventory path and set it as
the MAC address of the eth0 Interface.
(From meta-ibm rev: 0e69c800da414c88d24e4fa5fe8d9bf560b87637)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I9e0ab9d8368efae226334086f7b1c5b6fa821770
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Functionality is now covered with non-native YAML providers
via packagegroup-obmc-yaml-providers.
(From meta-ibm rev: 367e4b7ebf2754f224db71cba40e159a24590c87)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id6331322ffe1de17c2741e6572437141ae721e29
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove the extra -native YAML provider dependencies and use the
non-native YAML providers obtained via the phosphor-loggging DEPEND.
Add a missing python dependency.
Simplify task dependency between do_report and do_install.
(From meta-ibm rev: f11928baab0df3b845f59786ec934e8fb7272b4d)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I05040555fc98808cf00db150f7dcfcfab807b9da
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: dcb69381073974467c462609a4c0ebaba19f6b7f)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8dfa84af12606fbb8d6b6874d6642b89d55dc6cd
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: c453290155d686ce0d3604ea04db17cfcf06aa0d)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I559a93e0eadc92ebcdaa3aa4edd1923144986f48
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The hw-diags package adds advanced failure analysis support on Rainier
systems.
(From meta-ibm rev: 0cc373787485c1268efdfe2bf42364f84e07f80e)
Change-Id: Ia33d807ecce067747ef437b8761abf93254bc53d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
All the metadata in meta-witherspoon has been moved to meta-ibm. A
small set of config files remained while the OpenBMC CI infrastructure
was updated. That update has occurred so the remaining files can now be
removed.
(From meta-ibm rev: ea56691750114f9203f50b3d3455f9c6fb148291)
Change-Id: I44b4bed305b136ac62031ae7fa98d27d2967a5ff
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit updates the recipe for phosphor-dbus-interface to
enable ibm-dbus-interface flag irrespective of the machine type.
This was required as in case of native build the flag is not set
enabled.
(From meta-ibm rev: f195655090bc91fa75a33e32828cfdd2a567c538)
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I5d5c60068aa940c0762d0ad246410058c3854766
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: 34c7a88436d2e425429b7a61065e25ce4a9b0664)
Change-Id: I9d4259e36c7c7225e5f29041e204f7d75dc15720
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Configure the fan monitor and fan control services to be protected by
the fan watchdog. In the event that any of those services fail to run
on the BMC, the fan watchdog would trip and push fans to 100% PWM.
(From meta-ibm rev: 0860865b6c1003d5440a2be4990fc399931be92c)
Change-Id: I6be11de61cae544089553f8791cf599f98ca04f6
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Configure and include the fan watchdog services to drive the fans to
100% PWM if the BMC loses communication to the fan controller chip at
any time (i.e. BMC reset while powered on).
(From meta-ibm rev: 1264216bc2f10cf08f697bc1c95f10237c95515a)
Change-Id: I18865bdc06c1a2be0c2a83d5e83402b9316ee845
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|