summaryrefslogtreecommitdiff
path: root/meta-ibm/recipes-phosphor
AgeCommit message (Collapse)AuthorFilesLines
2021-09-04meta-phosphor: make discovery bbclass use override syntaxPatrick Williams2-4/+4
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
2021-09-04ibm-logging: srcrev bump 074d53b723..1eb63675afAndrew Geissler1-1/+1
Matt Spinler (1): Switch SdBusError to generic sdbusplus exception Change-Id: I9fad0117559672b860270d86fb2538b649b3ee28 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2021-09-03Remove phosphor-webui from witherspoon systemsAli Ahmed1-2/+2
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
2021-09-02meta-phosphor: change systemd.bbclass to match upstream override syntaxPatrick Williams14-48/+48
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
2021-08-25meta-ibm: Enable eth1 as an alternate RMCP+ interfaceShantappa Teekappanavar2-1/+184
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
2021-08-17Fix path to udev rules filesAnton Blanchard1-2/+2
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
2021-08-13meta-ibm: meson build option 'hostboot-dump-collection' is enabledShantappa Teekappanavar1-0/+1
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
2021-08-12witherspoon: remove telemetryAndrew Geissler1-0/+1
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
2021-08-11meta-{ibm, openpower}: minor override syntax fixesPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iadecbc8418d901f82fcc741d3e88d2d202fe96fe
2021-08-11meta-ibm: Update local.conf.sampleAdriana Kobylak1-1/+1
Update with the latest version from upstream. Change-Id: I1a7da37b0457dab873afaf6445aca360d54b47ca Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-08-11meta-ibm: prep for new override syntaxAdriana Kobylak65-371/+371
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-08-10Add D-bus monitor snmp policy for ibm systemsRavi Teja4-19/+38
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
2021-08-10Override pldm response time out valueManojkiran Eda1-0/+4
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
2021-08-10Change default password hashJoseph Reynolds1-5/+3
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
2021-08-10Remove redundant code to set root passwordJoseph Reynolds1-0/+1
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
2021-08-02PEL:Check-in Everest device callout JSONSumit Kumar2-0/+39004
Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com> Change-Id: I62027c739eb4cf95bb1bfc8ccddec30964bb1906
2021-07-20Remove phosphor-gpio-presence from p10bmcB. J. Wyman5-30/+0
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
2021-07-20treewide: inventory: switch ChassisType to future enum valuePatrick Williams2-2/+2
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
2021-07-20meta-ibm: mctp: Enable raw KCS udev supportAndrew Jeffery1-0/+1
Change-Id: Iac6362f744113d9a405e4a4ec30077e513dda2d3 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2021-07-20meta-ibm: witherspoon-tacoma: Enable debug-trigger supportAndrew Jeffery1-1/+1
As for Rainier and Everest, use KCS2 as the debug-trigger interface. Change-Id: I2614ffc3d97164658f2ad4fbb916cbf44be152e1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2021-07-07ibm: Prepare for fan control services installed from repoMatthew Barth1-0/+1
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>
2021-07-06everest: Add association entriesLakshminarayana R. Kammath1-2/+3143
- 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
2021-07-01Set MaxBootCycleCount for progresscodes on IBM systemsManojkiran Eda1-0/+4
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
2021-06-30meta-ibm: Adds virtual Altitude sensorBruce Mitchell1-0/+26
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
2021-06-30meta-ibm: sbe error handling supportJayanth Othayoth1-0/+4
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
2021-06-25meta-ibm: mctp: Enable astlpc raw KCS support for p10bmcAndrew Jeffery1-0/+2
Install the udev files to cover the transition between drivers and devices. Change-Id: I87ffe3ae82bb7a073a8140adcb308b09fc43c9b9 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2021-06-25meta-ibm: packagegroup-obmc-apps: p10bmc requires libmctpAndrew Jeffery4-1/+7
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>
2021-06-25meta-ibm: packagegroup-obmc-apps: Reorder p10bmc appendsAndrew Jeffery1-1/+1
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>
2021-06-17meta-ibm: Add debug-trigger to p10bmcAndrew Jeffery1-1/+1
Change-Id: Ic1cde1cd67fa6f8f68df80a1f327ace64a39d72b Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2021-06-11meta-ibm/state: fix meson param statementAnton D. Kachalov1-1/+1
Change-Id: I4453f9b01f986a529c76710d665ab57639232b2d Signed-off-by: Anton D. Kachalov <gmouse@google.com>
2021-06-08ibm: rainier4u: Increase poweron fan speed to 10000rpmMatthew Barth2-4/+4
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>
2021-06-07meta-ibm:checkstop-monitor: remove from p10bmcAndrew Geissler1-0/+1
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
2021-05-27meta-ibm:host-watchdog: increase timeout to 10 minAndrew Geissler2-0/+8
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
2021-05-24Set default system power mode to Maximum PerformanceChris Cain1-0/+6
Signed-off-by: Chris Cain <cjcain@us.ibm.com> Change-Id: I2ce6a862e0d16fe8a67c9dc12ceacbc01d3a0b1b
2021-05-20associations: rainier: Add associations for assemblyVishwanatha Subbanna2-0/+38
This commit adds associations for all the inventory that gets represented as Assemblies in Redfish. Change-Id: Id4e9e4ac870e5bed665462d161abde00c4b85554 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-05-18ibm: Update rainier 2U fan monitor configMatthew Barth1-24/+24
To support the new rainier 2U fan hardware, the fan monitor config needs to be updated to reflect the factor/offset between the target and feedback speeds of the new hardware. Change-Id: Ic63d678e89b210da77d4681ad44a209dd2807836 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
2021-05-18meta-ibm: phosphor-networkd: Remove autotools specific configWilliam A. Kennington III1-1/+1
We want to use packageconfig options instead of build system specific ones. Change-Id: I587d33e3dae82c4c9d85f59f4ee34618443f1dcb Signed-off-by: William A. Kennington III <wak@google.com>
2021-05-17ibm: fans: Switch to the 'count' fault methodMatt Spinler4-40/+70
Switch over to the 'count' method of determining fan faults. As a starting point, use a count interval of 1 and a threshold of 30. This is the preferred method as it is better at catching flakey fans. See docs/monitor/method.md in the phosphor-fan-presence repo for more info on how this works. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I153d05779a5a7af854f351c1be3a3448b85fc461
2021-05-17ibm: Use the generic fan-presence I2C pathsMatt Spinler5-24/+24
The fan presence detect application uses I2C device paths in its config files to address the IO expanders that IBM systems use to monitor fan presence detects. Use the /sys/bus/i2c/devices/... paths in these config files instead of the absolute paths. These new paths are links to the actual paths, and shouldn't change even if some internal kernel change drives an actual device path change. There are other config files today that do this the same way. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I39ed9d703cf6bdc821a54c6d5d087f7fc080705b
2021-05-13IBM DISTRO_FEATURE ibm-service-account-policyJoseph Reynolds1-0/+58
This creates a new DISTRO_FEATURE "ibm-service-account-policy" which - Adds an admin account which cannot SSH to the BMC's command shell. - Adds a service account which can SSH and has passwordless sudo access. This feature is applied to witherspoon-tacoma and p10bmc (rainier). Tested: The image behaves as before when the distro feature is not configured. When the distro feature is configured: The root user has the same access as before. The admin user: - Is not allowed to access the BMC's command shell. - Console login gets: This account is currently not available. - SSH login gets: Permission denied, please try again. - Redfish and REST API access works with role=Administrator. The service user: - Console login to the BMC's command shell works. The home directory is /. Passwordless sudo works. - SSH login works and using sudo from a SSH session works. - Redfish and REST API access works with role=Administrator. Change-Id: Icac5ba7f4fa663047709ab55007bbcfec8158f5e Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
2021-05-12associations: everest: Update association entriesVishwanatha Subbanna1-1/+1084
Change-Id: Ib7a9802582e146b5e2e5edb7b2df1800dfe36b22 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-05-12associations: rainier: Update rainier associationsVishwanatha Subbanna2-2/+841
Power supply, fans and pcie slots are tied to a particular chassis and thus need the associations for redfish to use them. Change-Id: I71b9596b811c910fac65c16af4f008954a934b30 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-05-12meta-ibm: rainier-4u: inventory: Add powersupply led associationsVishwanatha Subbanna1-0/+56
Rainier-4U systems have 4 power supply D-Bus objects and hence updated the associations json to have a mapping for powersupply2 and powersupply3 led group D-Bus objects. Change-Id: I21ea628928a5f6a7d2dc014eb25559c6d2e15722 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-05-12phosphor-power: Only build monitor when told toMatt Spinler1-0/+4
The 'monitor' package provides a power supply monitor application that uses an org.open_power phosphor-dbus-interface that is only used on a subset of the OpenPower systems. So that non OpenPower systems can use phosphor-power and not need to include the org.open_power D-Bus interfaces, add a packageconfig option for this application to turn off its compilation. It will then only be enabled for certain machines. Fixes openbmc/phosphor-power#6 Tested: Built Witherspoon, application still built and installed. Built Rainier, application not built. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ib7fca16217d93b7d021ba8fb6659e9ddca17d1d9
2021-04-22build phosphor-hwmon with mesonMatt Spinler1-1/+1
The repository supports it, so switch it over in bitbake. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I8d96c79b395ee2614ddd869091569f245426c5c7
2021-04-22meta-ibm: use systemd_system_unitdirBrad Bishop1-2/+2
This variable was added to bitbake.conf so lets use it. Using it is best pratice and enables things like alternative base_libdir paths. Change-Id: I9adcec7856c6242d86f0ffad8646a23219ccca21 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2021-04-20rainier-1s4u: add ibm logging callout supportAndrew Geissler1-0/+1
Starting with a link to the 4u file. The only difference between the two is 2 less fans so there should be no real impact to the callout file. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iae528ef6378fdcad524faeefcd6139a1d8223789
2021-04-20PELs: Rainier 4U device callouts fileMatt Spinler3-0/+17883
Now that entity manager provides the system name, name the Rainier 2U device callouts file after it and add the Rainier 4U device callouts file. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I95ba6cee167616ec01bd7779e88defc0e77810df Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2021-04-15ibm-logging: srcrev bump aeaa374a6f..074d53b723Andrew Geissler1-1/+1
Patrick Williams (2): bootstrap: fix shellcheck warnings MAINTAINERS: remove Deepak Change-Id: Id06241aa091d2c8f16b0f18383e244924030b12f Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2021-04-13meta-ibm: p10bmc: save ttyVUART1 data to separate fileAndrew Geissler1-0/+2
The hostboot team has started utilizing VUART1 for extra debug data during a boot. This extra debug data is enabled within the CI infrastructure. This extra debug data causes the critical information going to VUART0 to get wrapped out of the default /var/log/obmc_console.log file. Redirect the VUART1 data to its own /var/log/ file. The only other user of VUART1 on p10bmc systems is the PHYP software. That is mostly used for interactive purposes so writing its data to a separate log file should be fine. I will work with the test teams to ensure this new file is collected as a part of the standard debug data collection process. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I248e5e8536e58e137b5de35d7572789215566763
generated by cgit v1.2.3 (git 2.39.0) at 2024-07-12 02:57:20 +0300