Delta: add agc032a openBMC build #165

Summary: The test_system_airflow_config.py CIT test is failing because the reference PIM types are not being properly interpreted from the output of the `kv get` command. The cause is a [change](https://github.com/facebookexternal/openbmc.arista/commit/e4020cc9a3c8b3519d07313df5315d46373516f0) in the kv util from this past weekend, which adds a newline to the output of the `kv get` command. ## Testing ``` root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py --platform elbert -r tests.elbert.test_system_airflow_config test_system_airflow_config (tests.elbert.test_system_airflow_config.SystemAirflowConfigTest) ... ok ---------------------------------------------------------------------- Ran 1 test in 0.259s OK ``` Pull Request resolved: https://github.com/facebookexternal/openbmc.arista/pull/227 Reviewed By: binhuang00 fbshipit-source-id: 2ed45b9134

…o add missing accountrole skeleton endpoint into account service Summary: Fix redfish validator tests by importing a reasonable $metadata schema from bmcweb Test Plan: ``` ../tools/rest_api/run_rest_on_oob fboss8845005-oob.snc1 ``` Verify by executing validator: ``` buck run //neteng/netcastle:netcastle -- --team openbmcfb --platform wedge --skip-build --skip-upgrade --regex "test_redfish_schemas.*" --basset-query openbmc:wedge40:fboss8845005.snc1 ``` RESULTS: ``` [ PASSED] test_redfish_schemas.RedfishValidator.test_redfish_schemas (4 mins 7.883 secs) ================================================================================ Ran 1 tests in 5 mins 29.396 secs [ ERROR] 0 [ FAILED] 0 [ TIMEOUT] 0 [ PASSED] 1 [ SKIPPED] 0 [ OMITTED] 0 [ RETRIED] 0 ``` Reviewed By: jerrt2003 fbshipit-source-id: f2815f5251

Summary: Adding support of regexp paths in ACLs. It is required to control access of Actions likes: ``` /redfish/v1/Systems/server4/Bios/FirmwareDumps/3543808e-2010-4285-977a-b41d1199a811 ``` where `server4` and `3543808e-2010-4285-977a-b41d1199a811` are variables, therefore: ``` r'^/redfish/v1/Systems/server\d+/Bios/FirmwareDumps(/[^/]+)?$':{'POST':['attestation'], 'DELETE':['attestation']} ``` Since we cannot use map to find appropriate regexp by path, we have to use a slice, instead. Which creates performance risks, therefore we adding a LRU cache: ``` functools.lru_cache(maxsize=1024) def get(self, method: str, path: str) -> List[str]: ``` Test Plan: ``` root@sled2403-oob:~# cat /usr/local/fbpackages/rest-api/acl_config.py RULES = {'/api/sys/fscd_sensor_data': {'POST': ['MANAGED_HOST_ANY']}, '/api/attestation/tpm': {'POST': ['attestation']}, '/api/sys/modbus/cmd': {'POST': ['MANAGED_HOST_ANY', 'POST:api.sys.modbus.cmd']}} RULES_REGEXP={ r'^/redfish/v1/Systems/server\d+/Bios/FirmwareDumps(/[^/]+)?$':{'POST':['attestation'], 'DELETE':['attestation']} } ``` And it works: ``` [xaionaro@devvm3590.ftw0 ~/fbcode] HTTP_PROXY= HTTPS_PROXY= GO111MODULE=off go run ./openbmc/experimental/cli/cmd/openbmc 312681353 bios_firmware_dump /tmp/test6.fd unable to issue a job to start firmware dumping process: unable to create dump: 507: already have 1 images, while the limit is 1 ``` Code is 507 because the limit of dumps is already reached, so this is expected. Server logs: ``` AUTH:Authorized Identity(user='user:xaionaro', host=None) for [POST]/redfish/v1/Systems/server4/Bios/FirmwareDumps/28be24e7-0ab4-4a28-9fce-00235e55c450 2401:db00:eef0:1120:3520:0:1c05:e7c6 - - [05/Oct/2021:14:06:20 +0000] "POST /redfish/v1/Systems/server4/Bios/FirmwareDumps/28be24e7-0ab4-4a28-9fce-00235e55c450 HTTP/1.1" 507 231 405329us "Identity(user='user:xaionaro', host=None)" "-" "gofish/1.0" ``` If I replace `redfish` with `rdfish` (to make a wrong path) in the rule, then: ``` [xaionaro@devvm3590.ftw0 ~/fbcode] HTTP_PROXY= HTTPS_PROXY= GO111MODULE=off go run ./openbmc/experimental/cli/cmd/openbmc 312681353 bios_firmware_dump /tmp/test6.fd unable to issue a job to start firmware dumping process: unable to create dump: 403: 403: Forbidden ``` ``` AUTH:Missing acl config for non-get[POST] endpoint /redfish/v1/Systems/server4/Bios/FirmwareDumps/82b52e13-6306-40d0-9760-c66a85a93fea. Blocking access 2401:db00:eef0:1120:3520:0:1c05:e7c6 - - [05/Oct/2021:14:13:25 +0000] "POST /redfish/v1/Systems/server4/Bios/FirmwareDumps/82b52e13-6306-40d0-9760-c66a85a93fea HTTP/1.1" 403 191 159698us "-" "-" "gofish/1.0" ``` (as expected) Reviewed By: zhdaniel12 fbshipit-source-id: f8d0de6216

Summary: There is an "exit" command before BIC setup in wedge_power.sh That makes wedge_power.sh skip BIC initialization. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1243 Test Plan: 1. Run the command wedge_power.sh off 2. Run the command wedge_power.sh on 3. Expect the BIC initializing message. test log: ``` root@bmc-oob:~# wedge_power.sh off Power off microserver ... Done root@bmc-oob:~# wedge_power.sh on Power on microserver ... Done root@bmc-oob:~# Initializing Bridge-IC I2C Frequency... Bridge-IC version is v1.11. Bridge-IC is initialized SCL to 1Mhz. ``` Reviewed By: joancaneus fbshipit-source-id: 5da8243ea7

Summary: fby2: Fix after update BIC may not update sensord's SDR. Since "SDR update flag” (/tmp/cache_store/slotx_sdr_thresh_update) may enable before bic-cache update the SDR “at background”, sensord may not get the updated SDR once “SDR update flag” enable is detected. Therefore, try to put “SDR update flag enable” to background, make sure it execute rigtht after bic-cache update the SDR. Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2704 Test Plan: Make sure after BIC update, "bic-cahe update SDR" and "SDR update flag enable" execute in backgpround together. Also,"bic-cahe update SDR"execute before "SDR update flag enable". root@bmc-oob:~# fw-util slot2 --update bic /tmp/f09_snowflake_124.bin && ps | grep bic updating fw on slot 2: size of file is 197336 bytes ok: down: ipmbd_3: 0s, normally up stop ipmbd for slot 2.. Stopped ipmbd for this slot 2.. start ipmbd -u for this slot 2.. ipmbd ready for update after 1 tries stop ipmbd for slot 2.. bic ready for update after 4 tries updated bic: 5 % updated bic: 10 % updated bic: 15 % updated bic: 20 % updated bic: 25 % updated bic: 30 % updated bic: 35 % updated bic: 40 % updated bic: 45 % updated bic: 50 % updated bic: 55 % updated bic: 60 % updated bic: 65 % updated bic: 70 % updated bic: 75 % updated bic: 80 % updated bic: 85 % updated bic: 90 % updated bic: 95 % updated bic: 100 % ok: run: ipmbd_3: (pid 15076) 1s Upgrade of slot2 : bic succeeded 15100 root 2876 S sh -c (/usr/local/bin/bic-cached 2; /usr/bin/kv set slot2_sdr_thresh_update 1) & 15102 root 8320 R /usr/local/bin/bic-cached 2 15106 root 3044 S grep bic Reviewed By: williamspatrick fbshipit-source-id: 709a9a8356

Summary: fby2: fix servers do not power on after sled cycle Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2703 Test Plan: check bmc console log after sled cycle, all TL server should power on. Before: Syncing up BMC time with server2... Wed Oct 13 19:58:37 PDT 2021 lps /etc/rc5.d/S70power-on.sh: line 49: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 53: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 57: [: ==: unary operator expected lps /etc/rc5.d/S70power-on.sh: line 49: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 53: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 57: [: ==: unary operator expected lps /etc/rc5.d/S70power-on.sh: line 49: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 53: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 57: [: ==: unary operator expected lps /etc/rc5.d/S70power-on.sh: line 49: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 53: [: ==: unary operator expected /etc/rc5.d/S70power-on.sh: line 57: [: ==: unary operator expected After: Syncing up BMC time with server2... Thu Oct 14 04:21:27 PDT 2021 Powering fru 2 to ON state... Powering fru 4 to ON state... Reviewed By: williamspatrick fbshipit-source-id: 0f358a4309

Summary: Symptom: a "System powered OFF" event is logged when 12V-on 4 slot4 2021-10-13 00:25:33 power-util SERVER_12V_OFF successful for FRU: 4 4 slot4 2021-10-13 00:28:00 gpiod FRU: 4, System powered OFF 4 slot4 2021-10-13 00:28:07 power-util SERVER_12V_ON successful for FRU: 4 4 slot4 2021-10-13 00:28:10 gpiod FRU: 4, System powered ON Change: clear (set as low) old GPIO value when 12V is off, to align the actual pin status: (1) PWRGD_CPU_LVC3_R (note: align previous behavior that no System powered OFF is logged when 12V cycle) (2) RST_PLTRST_BMC_N (note: need a rst_timer()) Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2701 Test Plan: Build and tested pass on fby3 root@bmc-oob:~# log-util all --print | grep -E '(power-util|gpiod)' 1 slot1 2021-10-13 00:41:14 power-util SERVER_12V_OFF successful for FRU: 1 2 slot2 2021-10-13 00:41:21 power-util SERVER_12V_OFF successful for FRU: 2 3 slot3 2021-10-13 00:41:28 power-util SERVER_12V_OFF successful for FRU: 3 4 slot4 2021-10-13 00:41:32 power-util SERVER_12V_OFF successful for FRU: 4 4 slot4 2021-10-13 00:42:09 power-util SERVER_12V_ON successful for FRU: 4 4 slot4 2021-10-13 00:42:12 gpiod FRU: 4, System powered ON 1 slot1 2021-10-13 00:42:25 power-util SERVER_12V_ON successful for FRU: 1 1 slot1 2021-10-13 00:42:27 gpiod FRU: 1, System powered ON 2 slot2 2021-10-13 00:42:49 power-util SERVER_12V_ON successful for FRU: 2 2 slot2 2021-10-13 00:42:52 gpiod FRU: 2, System powered ON 3 slot3 2021-10-13 00:43:05 power-util SERVER_12V_ON successful for FRU: 3 3 slot3 2021-10-13 00:43:07 gpiod FRU: 3, System powered ON 1 slot1 2021-10-13 00:45:17 power-util SERVER_12V_CYCLE successful for FRU: 1 1 slot1 2021-10-13 00:45:20 gpiod FRU: 1, System powered ON 2 slot2 2021-10-13 00:45:44 power-util SERVER_12V_CYCLE successful for FRU: 2 2 slot2 2021-10-13 00:45:47 gpiod FRU: 2, System powered ON 3 slot3 2021-10-13 00:46:12 power-util SERVER_12V_CYCLE successful for FRU: 3 3 slot3 2021-10-13 00:46:15 gpiod FRU: 3, System powered ON 4 slot4 2021-10-13 00:46:54 power-util SERVER_12V_CYCLE successful for FRU: 4 4 slot4 2021-10-13 00:46:56 gpiod FRU: 4, System powered ON Reviewed By: williamspatrick fbshipit-source-id: aca7c795f0

Summary: The latest poky container which we used in circleci was outdated thus causing following certificate error as in `setup` step: ``` Warning: Permanently added the RSA host key for IP address '140.82.113.4' to the list of known hosts. warning: no common commits remote: Enumerating objects: 78423, done. remote: Counting objects: 100% (2/2), done. remote: Compressing objects: 100% (2/2), done. remote: Total 78423 (delta 0), reused 0 (delta 0), pack-reused 78421 Receiving objects: 100% (78423/78423), 30.42 MiB | 32.12 MiB/s, done. Resolving deltas: 100% (44336/44336), done. From ssh://github.com/openembedded/meta-openembedded * branch rocko -> FETCH_HEAD * [new branch] rocko -> yocto-meta-openembedded/rocko Preparing ./yocto/rocko/meta-openembedded (identifier meta-openembedded) HEAD is now at eae996301d glm: update 0.9.8.5 -> 0.9.9-a2 to fix x86_64 (sse-simd) build fatal: unable to access 'https://git.yoctoproject.org/git/meta-security/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none ``` We need to update/install the ca-certifiacte pkg as workaround for the container Test Plan: CircleCI can pass the `setup` step: [circleci job](https://app.circleci.com/pipelines/github/facebookexternal/openbmc.wiwynn/5405/workflows/6bd0bbea-7ea8-4c5d-9e04-0a5357a8a7b9/jobs/109258) Reviewed By: williamspatrick fbshipit-source-id: 49cc412984

Summary: Add capability to query for FRU capability. Test Plan: ``` >>> import pal >>> pal.pal_get_fru_capability(1) {<FruCapability.FRU_CAPABILITY_MANAGEMENT_CONTROLLER: 7>, <FruCapability.FRU_CAPABILITY_SENSOR_THRESHOLD_UPDATE: 3>, <FruCapability.FRU_CAPABILITY_POWER_RESET: 12>, <FruCapability.FRU_CAPABILITY_POWER_OFF: 10>, <FruCapability.FRU_CAPABILITY_SENSOR_HISTORY: 4>, <FruCapability.FRU_CAPABILITY_SERVER: 5>, <FruCapability.FRU_CAPABILITY_SENSOR_READ: 2>, <FruCapability.FRU_CAPABILITY_POWER_CYCLE: 11>, <FruCapability.FRU_CAPABILITY_POWER_STATUS: 8>, <FruCapability.FRU_CAPABILITY_FRUID_WRITE: 0>, <FruCapability.FRU_CAPABILITY_POWER_ON: 9>, <FruCapability.FRU_CAPABILITY_FRUID_READ: 1>} ``` Reviewed By: zhdaniel12 fbshipit-source-id: 5802f527e9

Summary: Becasue the Delta & Liteon 48V DC psu meet the PMBus spec. So need add the Delta and Liteon psu support in the psu_drvier. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1241 Test Plan: ``` root@bmc:~# cat /etc/issue OpenBMC Release fuji-04596875a00-dirty <1>. Liteon PSU root@bmc:~# cat /sys/bus/i2c/devices/48-0058/ curr1_input driver/ hwmon/ in2_input power/ power3_input temp2_input curr2_input fan1_input in0_input modalias power1_input subsystem/ temp3_input curr3_input fan2_input in1_input name power2_input temp1_input uevent root@bmc:~# cat /sys/bus/i2c/devices/48-0058/curr1_input 5828 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/curr2_input 23000 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/curr3_input 222 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/power1_input 294000 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/power2_input 288000 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/power3_input 625 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/fan1_input 9984 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/fan2_input 8448 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/in0_input 47875 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/in1_input 12000 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/in2_input 3312 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/temp1_input 32500 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/temp2_input 39625 root@bmc:~# cat /sys/bus/i2c/devices/48-0058/temp3_input 41000 <2>.Delta PSU root@bmc:~# cat /sys/bus/i2c/devices/49-005a/ curr1_input driver/ hwmon/ in2_input power/ power3_input temp2_input curr2_input fan1_input in0_input modalias power1_input subsystem/ temp3_input curr3_input fan2_input in1_input name power2_input temp1_input uevent root@bmc:~# cat /sys/bus/i2c/devices/49-005a/curr1_input 6445 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/curr2_input 23687 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/curr3_input 7 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/fan1_input 9872 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/fan2_input 3120 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/power1_input 309500 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/power2_input 285000 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/power3_input 23 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/in0_input 48000 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/in1_input 12031 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/in2_input 3250 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/temp1_input 37000 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/temp2_input 48000 root@bmc:~# cat /sys/bus/i2c/devices/49-005a/temp3_input 50000 ``` Reviewed By: joancaneus fbshipit-source-id: 81dcb95b88

Summary: Add the Liteon and Delta 48V DC support. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1242 Test Plan: ``` root@bmc:~# cat /etc/issue OpenBMC Release fuji-854530560b7-dirty root@bmc:~# psu-util psu1 --get_psu_info PSU Information : PSU1 (Bus:48 Addr:0x58) --------------- : ----------------------- MFR_ID (0x99) : Liteon MFR_MODEL (0x9A) : DD-2152-2L MFR_REVISION (0x9B) : X1 MFR_DATE (0x9D) : 20210716 MFR_SERIAL (0x9E) : 6D00201X1929104 PRI_FW_VER (0xDD) : 1.0 SEC_FW_VER (0xD7) : 1.0 STATUS_WORD (0x79) : 0x0000 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0x00 STATUS_INPUT (0x7C) : 0x00 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x0000 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : NA OPTN_TIME_PRESENT (0xD9) : NA root@bmc:~# psu-util psu1 --get_eeprom_info [ 266.538633] at24 48-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write [ 266.627139] i2c i2c-48: new_device: Instantiated device 24c02 at 0x50 [ 266.763233] i2c i2c-48: delete_device: Deleting device 24c02 at 0x50 print EEPROM info ret = 0x0! FRU Information : PSU1 (Bus:48 Addr:0x50) --------------- : ----------------------- Version : 3 Product Name : MINIPACK2-DC-PEM-48V Product Part Number : System Assembly Part Number : XX-XXXXXXX-XX Facebook PCBA Part Number : XXX-XXXXXX-XX Facebook PCB Part Number : XXX-XXXXXX-XX ODM PCBA Part Number : 8A0M12 ODM PCBA Serial Number : 6CL01X1135000 Product Production State : 1 Product Version : 0 Product Sub-Version : 0 Product Serial Number : 6CL01X1135000 Product Asset Tag : xxxxxxxx System Manufacturer : Liteon System Manufacturing Date : 07-21-88 PCB Manufacturer : LaiHe Assembled At : Liteon Local MAC : 00:00:00:00:00:00 Extended MAC Base : 00:00:00:00:00:00 Extended MAC Address Size : 0 Location on Fabric : PEM CRC8 : 0xf3 root@bmc:~# psu-util psu1 --get_blackbox_info --print Blackbox Information : PSU1 (Bus:48 Addr:0x58) -------------------- : ----------------------- PAGE : 0 PRI_FW_VER (0xDD) : 1.0 SEC_FW_VER (0xD7) : 53.190 STATUS_WORD (0x79) : 0x4850 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0xa0 STATUS_INPUT (0x7C) : 0x00 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x0840 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : 40D:23H:2M:31S OPTN_TIME_PRESENT (0xD9) : 23101D:10H:33M:36S IN_VOLT (0x88) : 46.94 V 12V_VOLT (0x89) : 12.17 V IN_CURR (0x8B) : 38.56 A 12V_CURR (0x8C) : 146.75 A TEMP1 (0x8D) : 26.62 C TEMP2 (0x8E) : 49.00 C TEMP3 (0x8F) : 48.25 C FAN_SPEED (0x90) : 20480.00 RPM FAN_SPEED2 (0x91) : 1.00 RPM Blackbox Information : PSU1 (Bus:48 Addr:0x58) -------------------- : ----------------------- PAGE : 1 PRI_FW_VER (0xDD) : 1.0 SEC_FW_VER (0xD7) : 194.28 STATUS_WORD (0x79) : 0x2840 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0x00 STATUS_INPUT (0x7C) : 0x80 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x2840 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : 11D:9H:4M:0S OPTN_TIME_PRESENT (0xD9) : 23101D:10H:33M:36S IN_VOLT (0x88) : 59.06 V 12V_VOLT (0x89) : 11.67 V IN_CURR (0x8B) : 0.00 A 12V_CURR (0x8C) : 0.42 A TEMP1 (0x8D) : 29.50 C TEMP2 (0x8E) : 27.38 C TEMP3 (0x8F) : 28.88 C FAN_SPEED (0x90) : 9888.00 RPM FAN_SPEED2 (0x91) : 1.00 RPM Blackbox Information : PSU1 (Bus:48 Addr:0x58) -------------------- : ----------------------- PAGE : 2 PRI_FW_VER (0xDD) : 1.0 SEC_FW_VER (0xD7) : 179.28 STATUS_WORD (0x79) : 0x2840 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0x00 STATUS_INPUT (0x7C) : 0x80 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x2840 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : 6D:19H:50M:24S OPTN_TIME_PRESENT (0xD9) : 23101D:10H:33M:36S IN_VOLT (0x88) : 59.00 V 12V_VOLT (0x89) : 11.64 V IN_CURR (0x8B) : 0.00 A 12V_CURR (0x8C) : 0.42 A TEMP1 (0x8D) : 29.00 C TEMP2 (0x8E) : 27.25 C TEMP3 (0x8F) : 28.50 C FAN_SPEED (0x90) : 13056.00 RPM FAN_SPEED2 (0x91) : 1.00 RPM Blackbox Information : PSU1 (Bus:48 Addr:0x58) -------------------- : ----------------------- PAGE : 3 PRI_FW_VER (0xDD) : 1.0 SEC_FW_VER (0xD7) : 170.28 STATUS_WORD (0x79) : 0x2840 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0x00 STATUS_INPUT (0x7C) : 0x80 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x2840 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : 16D:16H:29M:52S OPTN_TIME_PRESENT (0xD9) : 23101D:10H:33M:36S IN_VOLT (0x88) : 59.88 V 12V_VOLT (0x89) : 11.69 V IN_CURR (0x8B) : 0.00 A 12V_CURR (0x8C) : 0.42 A TEMP1 (0x8D) : 28.88 C TEMP2 (0x8E) : 27.12 C TEMP3 (0x8F) : 28.38 C FAN_SPEED (0x90) : 9984.00 RPM FAN_SPEED2 (0x91) : 1.00 RPM Blackbox Information : PSU1 (Bus:48 Addr:0x58) -------------------- : ----------------------- PAGE : 4 PRI_FW_VER (0xDD) : 1.0 SEC_FW_VER (0xD7) : 149.26 STATUS_WORD (0x79) : 0x4850 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0xa0 STATUS_INPUT (0x7C) : 0x00 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x0840 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : 18D:23H:6M:40S OPTN_TIME_PRESENT (0xD9) : 23101D:10H:33M:36S IN_VOLT (0x88) : 55.81 V 12V_VOLT (0x89) : 12.00 V IN_CURR (0x8B) : 31.75 A 12V_CURR (0x8C) : 134.75 A TEMP1 (0x8D) : 26.12 C TEMP2 (0x8E) : 49.62 C TEMP3 (0x8F) : 50.12 C FAN_SPEED (0x90) : 22112.00 RPM FAN_SPEED2 (0x91) : 1.00 RPM ``` Reviewed By: joancaneus fbshipit-source-id: 0af05b40e6

Summary: Becasue wedge400 will invove the Detla & Liteon 48V DC PSU and per 48V DC PSU will have two psu fans, so need detect the PSU48 by PSU P/N. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1245 Test Plan: ``` 1. Wedge400 with Liteon 48V DC PSU root@bmc-oob:~# cat /etc/issue OpenBMC Release wedge400-c5c48fdc82b-dirty root@bmc-oob:~# source /usr/local/bin/openbmc-utils.sh root@bmc-oob:~# wedge_power_supply_type PSU48 2. Wedge400 with AC PSUs root@bmc-oob:~# cat /etc/issue OpenBMC Release wedge400-c5c48fdc82b-dirty root@bmc-oob:~# source /usr/local/bin/openbmc-utils.sh root@bmc-oob:~# wedge_power_supply_type PSU ``` Reviewed By: joancaneus fbshipit-source-id: 1ddfd37ae1

Summary: Because 48V DC psu meet the standard IPMB spec, so it has the same driver with AC PSUs. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1246 Test Plan: ``` Wedge400 with 48V DC PSU: root@bmc-oob:~# cat /etc/issue OpenBMC Release wedge400-c5c48fdc82b-dirty root@bmc-oob:~# cat /sys/bus/i2c/devices/24-0058/name psu_driver root@bmc-oob:~# cat /sys/bus/i2c/devices/25-0058/name psu_driver ``` Reviewed By: joancaneus fbshipit-source-id: fa4a3f2dbd

Summary: As the title. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1253 Test Plan: ``` root@bmc-oob:~# cat /etc/issue OpenBMC Release wedge400-2129ca4a7a5-dirty root@bmc-oob:~# sensor-util pem2 PEM2_IN_VOLT (0x2C) : 11.96 Volts | (ok) PEM2_OUT_VOLT (0x2D) : 11.97 Volts | (ok) PEM2_FET_BAD (0x2E) : 0.00 Volts | (ok) PEM2_FET_SHORT (0x2F) : 0.00 Volts | (ok) PEM2_CURR (0x30) : 22.92 Amps | (ok) PEM2_POWER (0x31) : 275.00 Watts | (ok) PEM2_FAN1_SPEED (0x32) : 8228.00 RPM | (ok) PEM2_FAN2_SPEED (0x33) : 9600.00 RPM | (ok) PEM2_HOT_SWAP_TEMP (0x34) : 27.70 C | (ok) PEM2_AIR_INLET_TEMP (0x35) : 24.38 C | (ok) PEM2_AIR_OUTLET_TEMP (0x36) : 26.42 C | (ok) root@bmc-oob:~# pem-util pem2 --get_pem_info PEM Information : PEM2 (Bus:25 Addr:0x58) [ 1345.922943] at24 25-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write [ 1346.003478] i2c i2c-25: new_device: Instantiated device 24c02 at 0x50 [ 1346.321150] i2c i2c-25: delete_device: Deleting device 24c02 at 0x50 --------------- : ----------------------- Version [ 1346.555935] at24 25-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write : 3 [ 1346.638744] i2c i2c-25: new_device: Instantiated device 24c02 at 0x50 Product Name : WEDGE400-PEM Product Part Number : 00-000000 Product Version : 2 Product Sub-Version : 0 Product Serial Number : S112420471162 System Manufacturer : CLSSAN System Manufacturing Date : 12-12-20 [ 1347.446767] i2c i2c-25: delete_device: Deleting device 24c02 at 0x50 PEM Hot Swap status : PEM2 (Bus:25 Addr:0x58) --------------- : ----------------------- PEM2_IN_VOLT : 11.96 Volts PEM2_OUT_VOLT : 11.97 Volts PEM2_FET_BAD : 0.00 Volts PEM2_FET_SHORT : 0.00 Volts PEM2_CURR : 22.97 Amps PEM2_POWER : 276.00 Watts PEM2_FAN1_SPEED : 9600.00 RPM PEM2_FAN2_SPEED : 9600.00 RPM PEM2_HOT_SWAP_TEMP : 27.70 C PEM2_AIR_INLET_TEMP : 24.38 C PEM2_AIR_OUTLET_TEMP : 26.42 C ON_STATUS : 1 FET_BAD_COOLDOWN_STATUS : 0 FET_SHORT_PRESENT : 0 ON_PIN_STATUS : 1 POWER_GOOD_STATUS : 1 OC_COOLDOWN_STATUS : 0 UV_STATUS : 0 OV_STATUS : 0 GPIO3_STATUS : 0 GPIO2_STATUS : 1 GPIO1_STATUS : 1 ALERT_STATUS : 1 EEPROM_BUSY : 0 ADC_IDLE : 0 TICKER_OVERFLOW_PRESENT : 0 METER_OVERFLOW_PRESENT : 0 EEPROM_Done : 0 FET_Bad_Fault : 0 FET_Short_Fault : 0 On_Fault : 0 Power_Bad_Fault : 0 OC_Fault : 0 UV_Fault : 0 OV_Fault : 0 Power_Alarm_High : 0 Power_Alarm_Low : 1 Vsense_Alarm_High : 0 Vsense_Alarm_Low : 0 VSourve_Alarm_High : 0 VSourve_Alarm_Low : 0 VGPIO_Alarm_High : 1 VGPIO_Alarm_Low : 0 root@bmc-oob:~# pem-util pem2 --get_eeprom_info --print FRU Information : PEM2 (Bus:25 Addr:0x58) [ 1388.052599] at24 25-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write [ 1388.133189] i2c i2c-25: new_device: Instantiated device 24c02 at 0x50 [ 1388.588340] i2c i2c-25: delete_device: Deleting device 24c02 at 0x50 --------------- : ----------------------- Version : 3 Product Name : WEDGE400-PEM Product Part Number : 00-000000 System Assembly Part Number : 03-000840 Facebook PCBA Part Number : 132-000093-05 Facebook PCB Part Number : 131-000071-05 ODM PCBA Part Number : R1149G001501 ODM PCBA Serial Number : G151420470305 Product Production State : 4 Product Version : 2 Product Sub-Version : 0 Product Serial Number : S112420471162 Product Asset Tag : N/A System Manufacturer : CLSSAN System Manufacturing Date : 12-12-20 PCB Manufacturer : WUS Assembled At : CTH Local MAC : 00:00:00:00:00:00 Extended MAC Base : 00:00:00:00:00:00 Extended MAC Address Size : 0 Location on Fabric : PEM CRC8 : 0x98 Hot Swap EEPROM Information : PEM2 (Bus:25 Addr:0x58) --------------- : ----------------------- On Fault Mask : 0 On Delay : 0 On/Enb : 1 Mass Write Enable : 1 Fet on : 1 OC Autoretry : 1 UV Autoretry : 1 OV Autoretry : 1 On FB Mode : external On UV Mode : external On OV Mode : external On Vin Mode : 12V EEPROM Done Alert : 0 FET Bad Fault Alert : 0 FET Short Alert : 0 On Alert : 0 PB Alert : 0 OC Alert : 0 UV Alert : 0 OV Alert : 0 Power Alarm High : 0 Power Alarm Low : 0 Vsense Alarm High : 0 Vsense Alarm Low : 0 VSourve Alarm High : 0 VSourve Alarm Low : 0 VGPIO Alarm High : 0 VGPIO Alarm Low : 0 EEPROM_Done : 1 FET_Bad_Fault : 0 FET_Short_Fault : 0 On_Fault : 1 Power_Bad_Fault : 1 OC_Fault : 0 UV_Fault : 1 OV_Fault : 0 Power_Alarm_High : 0 Power_Alarm_Low : 1 Vsense_Alarm_High : 0 Vsense_Alarm_Low : 1 VSourve_Alarm_High : 0 VSourve_Alarm_Low : 0 VGPIO_Alarm_High : 1 VGPIO_Alarm_Low : 0 GPIO3 PD : 0 GPIO2 PD : 0 GPIO1 Config : Power Good GPIO1 Output : 0 ADC Conv Alert : 0 Stress to GPIO2 : 0 Meter Overflow Alert : 0 Coulomb Meter : 0 Tick Out : 0 Int Clock Out : 0 Clock Divider : 8 ILIM Adjust : 2 Foldback Mode : 2 Vsource/VDD : 1 GPIO Mode : 1 ADC 16-BIT/12-BIT : 16-bit root@bmc-oob:~# pem-util pem2 --get_blackbox_info --print FRU Information : PEM2 (Bus:25 A[ 1400.492953] at24 25-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write ddr:0x58) [ 1400.591598] i2c i2c-25: new_device: Instantiated device 24c02 at 0x50 [ 1401.441796] i2c i2c-25: delete_device: Deleting device 24c02 at 0x50 --------------- : ----------------------- Version : 3 Product Name : WEDGE400-PEM Product Part Number : 00-000000 System Assembly Part Number : 03-000840 Facebook PCBA Part Number : 132-000093-05 Facebook PCB Part Number : 131-000071-05 ODM PCBA Part Number : R1149G001501 ODM PCBA Serial Number : G151420470305 Product Production State : 4 Product Version : 2 Product Sub-Version : 0 Product Serial Number : S112420471162 Product Asset Tag : N/A System Manufacturer : CLSSAN System Manufacturing Date : 12-12-20 PCB Manufacturer : WUS Assembled At : CTH Local MAC : 00:00:00:00:00:00 Extended MAC Base : 00:00:00:00:00:00 Extended MAC Address Size : 0 Location on Fabric : PEM CRC8 : 0x98 Hot Swap EEPROM Information : PEM2 (Bus:25 Addr:0x58) --------------- : ----------------------- On Fault Mask : 0 On Delay : 0 On/Enb : 1 Mass Write Enable : 1 Fet on : 1 OC Autoretry : 1 UV Autoretry : 1 OV Autoretry : 1 On FB Mode : external On UV Mode : external On OV Mode : external On Vin Mode : 12V EEPROM Done Alert : 0 FET Bad Fault Alert : 0 FET Short Alert : 0 On Alert : 0 PB Alert : 0 OC Alert : 0 UV Alert : 0 OV Alert : 0 Power Alarm High : 0 Power Alarm Low : 0 Vsense Alarm High : 0 Vsense Alarm Low : 0 VSourve Alarm High : 0 VSourve Alarm Low : 0 VGPIO Alarm High : 0 VGPIO Alarm Low : 0 EEPROM_Done : 1 FET_Bad_Fault : 0 FET_Short_Fault : 0 On_Fault : 1 Power_Bad_Fault : 1 OC_Fault : 0 UV_Fault : 1 OV_Fault : 0 Power_Alarm_High : 0 Power_Alarm_Low : 1 Vsense_Alarm_High : 0 Vsense_Alarm_Low : 1 VSourve_Alarm_High : 0 VSourve_Alarm_Low : 0 VGPIO_Alarm_High : 1 VGPIO_Alarm_Low : 0 GPIO3 PD : 0 GPIO2 PD : 0 GPIO1 Config : Power Good GPIO1 Output : 0 ADC Conv Alert : 0 Stress to GPIO2 : 0 Meter Overflow Alert : 0 Coulomb Meter : 0 Tick Out : 0 Int Clock Out : 0 Clock Divider : 8 ILIM Adjust : 2 Foldback Mode : 2 Vsource/VDD : 1 GPIO Mode : 1 ADC 16-BIT/12-BIT : 16-bit PEM Hot Swap status : PEM2 (Bus:25 Addr:0x58) --------------- : ----------------------- PEM2_IN_VOLT : 11.96 Volts PEM2_OUT_VOLT : 11.97 Volts PEM2_FET_BAD : 0.00 Volts PEM2_FET_SHORT : 0.00 Volts PEM2_CURR : 23.02 Amps PEM2_POWER : 276.00 Watts PEM2_FAN1_SPEED : 9600.00 RPM PEM2_FAN2_SPEED : 9600.00 RPM PEM2_HOT_SWAP_TEMP : 27.70 C PEM2_AIR_INLET_TEMP : 24.38 C PEM2_AIR_OUTLET_TEMP : 26.42 C ON_STATUS : 1 FET_BAD_COOLDOWN_STATUS : 0 FET_SHORT_PRESENT : 0 ON_PIN_STATUS : 1 POWER_GOOD_STATUS : 1 OC_COOLDOWN_STATUS : 0 UV_STATUS : 0 OV_STATUS : 0 GPIO3_STATUS : 0 GPIO2_STATUS : 1 GPIO1_STATUS : 1 ALERT_STATUS : 1 EEPROM_BUSY : 0 ADC_IDLE : 0 TICKER_OVERFLOW_PRESENT : 0 METER_OVERFLOW_PRESENT : 0 EEPROM_Done : 0 FET_Bad_Fault : 0 FET_Short_Fault : 0 On_Fault : 0 Power_Bad_Fault : 0 OC_Fault : 0 UV_Fault : 0 OV_Fault : 0 Power_Alarm_High : 0 Power_Alarm_Low : 1 Vsense_Alarm_High : 0 Vsense_Alarm_Low : 0 VSourve_Alarm_High : 0 VSourve_Alarm_Low : 0 VGPIO_Alarm_High : 1 VGPIO_Alarm_Low : 0 root@bmc-oob:~# ``` Reviewed By: joancaneus fbshipit-source-id: e3071a2951

Summary: As the title. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1252 Test Plan: ``` root@bmc-oob:~# cat /etc/issue OpenBMC Release wedge400-2129ca4a7a5-dirty root@bmc-oob:~# ps w |grep pemd 1357 root 2912 S runsv /etc/sv/pemd 1371 root 24556 S /usr/local/bin/pemd pem1 pem2 12698 root 3044 S grep pemd root@bmc-oob:~# ``` Reviewed By: joancaneus fbshipit-source-id: e85d134fc6

Summary: use the common pem-util. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1251 Test Plan: ``` root@bmc-oob:~# cat /etc/issue OpenBMC Release wedge400-22539701c3b-dirty root@bmc-oob:~# pem-util Usage: pem-util <pem1|pem2> --update [--force] <file_path> Usage: pem-util <pem1|pem2> <command> <options> command: --get_pem_info --get_eeprom_info options: --print --clear --get_blackbox_info options: --print --clear --get_archive_log options: --print --clear --archive_pem_chips root@bmc-oob:~# pem-util pem2 --get_pem_info PEM Information : PEM2 (Bus:25 Addr:0x58) [ 2023.933947] at24 25-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write [ 2024.014771] i2c i2c-25: new_device: Instantiated device 24c02 at 0x50 [ 2024.525129] i2c i2c-25: delete_device: Deleting device 24c02 at 0x50 --------------- : ----------------------- Versi[ 2024.671092] at24 25-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write on [ 2024.763899] i2c i2c-25: new_device: Instantiated device 24c02 at 0x50 : 3 Product Name : WEDGE400-PEM Product Part Number : 00-000000 Product Version : 2 Product Sub-Version : 0 Product Serial Number : S112420471162 System Manufacturer : CLSSAN System Manufacturing Date : 12-12-20 [ 2025.492251] i2c i2c-25: delete_device: Deleting device 24c02 at 0x50 PEM Hot Swap status : PEM2 (Bus:25 Addr:0x58) --------------- : ----------------------- PEM2_IN_VOLT : 11.96 Volts PEM2_OUT_VOLT : 11.98 Volts PEM2_FET_BAD : 0.00 Volts PEM2_FET_SHORT : 0.00 Volts PEM2_CURR : 23.02 Amps PEM2_POWER : 275.00 Watts PEM2_FAN1_SPEED : 8228.00 RPM PEM2_FAN2_SPEED : 9600.00 RPM PEM2_HOT_SWAP_TEMP : 27.70 C PEM2_AIR_INLET_TEMP : 24.38 C PEM2_AIR_OUTLET_TEMP : 26.42 C ON_STATUS : 1 FET_BAD_COOLDOWN_STATUS : 0 FET_SHORT_PRESENT : 0 ON_PIN_STATUS : 1 POWER_GOOD_STATUS : 1 OC_COOLDOWN_STATUS : 0 UV_STATUS : 0 OV_STATUS : 0 GPIO3_STATUS : 0 GPIO2_STATUS : 1 GPIO1_STATUS : 1 ALERT_STATUS : 1 EEPROM_BUSY : 0 ADC_IDLE : 0 TICKER_OVERFLOW_PRESENT : 0 METER_OVERFLOW_PRESENT : 0 EEPROM_Done : 0 FET_Bad_Fault : 0 FET_Short_Fault : 0 On_Fault : 0 Power_Bad_Fault : 0 OC_Fault : 0 UV_Fault : 0 OV_Fault : 0 Power_Alarm_High : 0 Power_Alarm_Low : 1 Vsense_Alarm_High : 0 Vsense_Alarm_Low : 0 VSourve_Alarm_High : 0 VSourve_Alarm_Low : 0 VGPIO_Alarm_High : 1 VGPIO_Alarm_Low : 0 ``` Reviewed By: joancaneus fbshipit-source-id: adad9725f5

Summary: Delete the wedge400 ltc4282 and max6615 code, instead use the common code. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1250 Test Plan: ``` root@bmc-oob:~# cat /etc/issue OpenBMC Release wedge400-22539701c3b-dirty root@bmc-oob:~# cat /sys/bus/i2c/devices/25-0018/name max6615 root@bmc-oob:~# cat /sys/bus/i2c/devices/25-0058/name ltc4282 root@bmc-oob:~# ``` Reviewed By: joancaneus fbshipit-source-id: 8cf0d97d8a

Summary: No functional change. Test Plan: ``` 0 ~/local/openbmc/tools/flashy $ go test ./... ok github.com/facebook/openbmc/tools/flashy (cached) ok github.com/facebook/openbmc/tools/flashy/checks_and_remediations/common (cached) ok github.com/facebook/openbmc/tools/flashy/checks_and_remediations/galaxy100 (cached) ok github.com/facebook/openbmc/tools/flashy/checks_and_remediations/wedge100 (cached) ok github.com/facebook/openbmc/tools/flashy/checks_and_remediations/yamp (cached) ? github.com/facebook/openbmc/tools/flashy/flash_procedure [no test files] ok github.com/facebook/openbmc/tools/flashy/install (cached) ok github.com/facebook/openbmc/tools/flashy/lib/fileutils (cached) ok github.com/facebook/openbmc/tools/flashy/lib/flash (cached) ok github.com/facebook/openbmc/tools/flashy/lib/flash/flashcp (cached) ok github.com/facebook/openbmc/tools/flashy/lib/flash/flashutils (cached) ok github.com/facebook/openbmc/tools/flashy/lib/flash/flashutils/devices (cached) ? github.com/facebook/openbmc/tools/flashy/lib/logger [no test files] ok github.com/facebook/openbmc/tools/flashy/lib/step (cached) ok github.com/facebook/openbmc/tools/flashy/lib/utils (cached) ok github.com/facebook/openbmc/tools/flashy/lib/validate (cached) ok github.com/facebook/openbmc/tools/flashy/lib/validate/image (cached) ok github.com/facebook/openbmc/tools/flashy/lib/validate/partition (cached) ? github.com/facebook/openbmc/tools/flashy/tests [no test files] ? github.com/facebook/openbmc/tools/flashy/utilities [no test files] ``` fbshipit-source-id: 864ea30f82

Summary: Adds four beacon LED modes (distinct color/blink) for the beacon LED. These following modes are supported: | Mode | Use Case | LED Color | Blink Interval (sec) | |-------|----------|------------|--------------| | locator | For physically locating a switch | Blue | .5 | | netstate | Indicates a "netstate" type failure where something is wrong but the device doesn’t drain | Red | .25 | | drained | Indicates that the switch is drained | Green | 1 | | audit | For when a switch is undergoing some sort of audit or alert suppression | Amber | 2 | The beacon_led.sh script is expanded to allow setting a mode (if no mode is given, locator is used by default to keep backward compatibility with the existing script): ``` root@bmc-oob:~# beacon_led.sh Usage: beacon_led.sh <on|off> [locator | netstate | drained | audit] ``` The script writes an int to a cookie file, which led-controld reads to determine how to set the beacon. led-controld is also smart enough to track the current beacon state and only log when the state changes. ## Testing Here's an example sequence which indicates the script usage and logging: ``` root@bmc-oob:~# beacon_led.sh on Beacon LED: now ON in locator mode root@bmc-oob:~# grep -i beacon /var/log/messages 2021 Aug 24 17:18:19 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode locator root@bmc-oob:~# beacon_led.sh off Beacon LED: now OFF root@bmc-oob:~# grep -i beacon /var/log/messages 2021 Aug 24 17:18:19 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode locator 2021 Aug 24 17:19:19 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is OFF root@bmc-oob:~# beacon_led.sh on netstate Beacon LED: now ON in netstate mode root@bmc-oob:~# beacon_led.sh on audit Beacon LED: now ON in audit mode root@bmc-oob:~# grep -i beacon /var/log/messages 2021 Aug 24 17:18:19 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode locator 2021 Aug 24 17:19:19 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is OFF 2021 Aug 24 17:19:43 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode netstate 2021 Aug 24 17:20:44 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode audit root@bmc-oob:~# beacon_led.sh on netstate Beacon LED: now ON in netstate mode root@bmc-oob:~# beacon_led.sh on netstate Beacon LED: already ON in netstate mode root@bmc-oob:~# beacon_led.sh off Beacon LED: now OFF root@bmc-oob:~# grep -i beacon /var/log/messages 2021 Aug 24 17:18:19 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode locator 2021 Aug 24 17:19:19 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is OFF 2021 Aug 24 17:19:43 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode netstate 2021 Aug 24 17:20:44 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode audit 2021 Aug 24 17:21:20 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode drained 2021 Aug 24 17:21:44 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is ON in mode netstate 2021 Aug 24 17:23:08 bmc-oob. user.info elbert-ccbe7e8110-dirty: led-controld: Beacon LED is OFF ``` Pull Request resolved: https://github.com/facebookexternal/openbmc.arista/pull/228 Reviewed By: binhuang00 fbshipit-source-id: 76b8c10758

Summary: NOTE: this PR depends on PR https://github.com/facebookexternal/openbmc.arista/issues/228. Merge that PR first. Adds REST endpoints for setting the Beacon LED modes added in https://github.com/facebookexternal/openbmc.arista/issues/228. The new endpoints are: ``` /api/sys/beacon /api/sys/beacon/locator /api/sys/beacon/netstate /api/sys/beacon/drained /api/sys/beacon/audit /api/sys/beacon/off ``` Also adds a new REST CIT test case. ## Testing Endpoints work correctly: ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 126 100 126 0 0 845 0 --:--:-- --:--:-- --:--:-- 840 { "Information": { "Description": "Beacon LED" }, "Actions": [], "Resources": [ "audit", "drained", "locator", "netstate", "off" ] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/locator | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 83 100 83 0 0 1317 0 --:--:-- --:--:-- --:--:-- 1317 { "Information": { "state": "ON", "mode": "locator" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/netstate | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 84 100 84 0 0 1527 0 --:--:-- --:--:-- --:--:-- 1527 { "Information": { "state": "ON", "mode": "netstate" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/drained | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 83 100 83 0 0 1338 0 --:--:-- --:--:-- --:--:-- 1338 { "Information": { "state": "ON", "mode": "drained" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/audit | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 81 100 81 0 0 1588 0 --:--:-- --:--:-- --:--:-- 1588 { "Information": { "state": "ON", "mode": "audit" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/off | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 79 100 79 0 0 1316 0 --:--:-- --:--:-- --:--:-- 1338 { "Information": { "state": "OFF", "mode": "NA" }, "Actions": [], "Resources": [] } ``` REST CIT test passes: ``` root@bmc-oob:/usr/local/bin/tests2# python3 cit_runner.py --platform=elbert -r tests.elbert.test_rest_endpoint test_endpoint_api (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_bmc (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_bmc_mtd (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_bmc_secondary_boot (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_fc_present (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_firmware_info_all (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_mb (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_mb_fruid (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_pim_present (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_piminfo (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_pimserial (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_pimstatus (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_sensors (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_server (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_beacon (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_server_httperror_code_404 (tests.elbert.test_rest_endpoint.RestEndpointTest) Test if REST server return 404 code when url is not accessible ... ok ---------------------------------------------------------------------- Ran 17 tests in 20.789s OK ``` Pull Request resolved: https://github.com/facebookexternal/openbmc.arista/pull/229 Reviewed By: binhuang00 fbshipit-source-id: 8ec6b3a8bc

Summary: NOTE: this PR depends on PR https://github.com/facebookexternal/openbmc.arista/issues/228. Merge that PR first. Adds REST endpoints for setting the Beacon LED modes added in https://github.com/facebookexternal/openbmc.arista/issues/228. The new endpoints are: ``` /api/sys/beacon /api/sys/beacon/locator /api/sys/beacon/netstate /api/sys/beacon/drained /api/sys/beacon/audit /api/sys/beacon/off ``` Also adds a new REST CIT test case. ## Testing Endpoints work correctly: ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 126 100 126 0 0 845 0 --:--:-- --:--:-- --:--:-- 840 { "Information": { "Description": "Beacon LED" }, "Actions": [], "Resources": [ "audit", "drained", "locator", "netstate", "off" ] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/locator | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 83 100 83 0 0 1317 0 --:--:-- --:--:-- --:--:-- 1317 { "Information": { "state": "ON", "mode": "locator" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/netstate | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 84 100 84 0 0 1527 0 --:--:-- --:--:-- --:--:-- 1527 { "Information": { "state": "ON", "mode": "netstate" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/drained | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 83 100 83 0 0 1338 0 --:--:-- --:--:-- --:--:-- 1338 { "Information": { "state": "ON", "mode": "drained" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/audit | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 81 100 81 0 0 1588 0 --:--:-- --:--:-- --:--:-- 1588 { "Information": { "state": "ON", "mode": "audit" }, "Actions": [], "Resources": [] } ``` ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/beacon/off | python /usr/lib/python3.7/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 79 100 79 0 0 1316 0 --:--:-- --:--:-- --:--:-- 1338 { "Information": { "state": "OFF", "mode": "NA" }, "Actions": [], "Resources": [] } ``` REST CIT test passes: ``` root@bmc-oob:/usr/local/bin/tests2# python3 cit_runner.py --platform=elbert -r tests.elbert.test_rest_endpoint test_endpoint_api (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_bmc (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_bmc_mtd (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_bmc_secondary_boot (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_fc_present (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_firmware_info_all (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_mb (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_mb_fruid (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_pim_present (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_piminfo (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_pimserial (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_pimstatus (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_sensors (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_api_sys_server (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_endpoint_beacon (tests.elbert.test_rest_endpoint.RestEndpointTest) ... ok test_server_httperror_code_404 (tests.elbert.test_rest_endpoint.RestEndpointTest) Test if REST server return 404 code when url is not accessible ... ok ---------------------------------------------------------------------- Ran 17 tests in 20.789s OK ``` Pull Request resolved: https://github.com/facebookexternal/openbmc.arista/pull/229 Reviewed By: binhuang00 fbshipit-source-id: 2ea5fe7a65

Summary: Missing escape before end of line Test Plan: elbert build Reviewed By: joancaneus, peterdelevoryas fbshipit-source-id: e7f7afbb20

Summary: Since now both rest and pypartition supports ptest method of running unit-tests, we can safely remove this. This also enables us to start cleaning up all the *-native depends which is peppered all over the recipes (And improve build time since we dont need to build in native version of almost everything). Test Plan: Build all the platforms! Reviewed By: williamspatrick fbshipit-source-id: eeb95d8153

Summary: Adding `ComputerSystem`, which is a parent for `Bios`, which is a parent for `FirmwareDumps` (introduced in the next Diffs). Current implementation exists only to provide link to `Bios`, which exists only to provide link to `FirmwareDumps`, so other fields are omitted at this time. See examples of `ComputerSystem` in https://www.dmtf.org/sites/default/files/standards/documents/DSP0266_1.12.0.pdf Test Plan: See Test Plan in: D31400585 Reviewed By: deathowl fbshipit-source-id: 8617d9d8e4

Summary: This essentially makes wedge40, wedge100, wedge400 which currently use rackmon to prefer v0.1 (No-operation). This allows us to develop v0.2 in an iterative fashion without affecting production machines. Test Plan: Build all the platforms. Reviewed By: williamspatrick fbshipit-source-id: e3b858c0a2

Summary: As title, removes redundant line Test Plan: Build elbert Reviewed By: doranand fbshipit-source-id: 6c2d94d805

Summary: As title Test Plan: Build elbert Reviewed By: doranand fbshipit-source-id: c08b847b96

Summary: As title Test Plan: Build grandcanyon Reviewed By: doranand fbshipit-source-id: 2bdbe02b9b

Summary: Adding a type for error responses. See 9.6 in https://www.dmtf.org/sites/default/files/standards/documents/DSP0266_1.12.0.pdf. Test Plan: See Test Plan in: D31400585 Reviewed By: deathowl fbshipit-source-id: 79902689d2

Summary: Here I add entity, which represents BIOS firmware dumps collection by path: ``` /redfish/v1/Systems/server\d+/Bios/FirmwareDumps(/[^/]+) ``` More specifically: * Create firmware dump. * Download the content of the dump. * Delete firmware dump. * Show the collection of dumps. Test Plan: See Test Plan in: D31400585 Reviewed By: lsiudut fbshipit-source-id: ecac02d321

Summary: Adding routes to: * ComputerSystems collection * ComputerSystem * Bios * FirmwareDumps collection Test Plan: # Preparing the test environment Uploading the new version: ``` source openbmc-init-build-env meta-facebook/meta-fby2/meta-fby2-nd build-fbnd cd ~/openbmc bash -x ./tools/rest_api/run_rest_on_oob rtptest1233-oob.prn5 ``` Adding myself to `/etc/aclcache.json.gz` on the OOB. Adding to `/usr/local/fbpackages/rest-api/acl_config.py`: ``` RULES_REGEXP={ r'^/redfish/v1/Systems/server\d+/Bios/FirmwareDumps(/[^/]+)?$':{'POST':['attestation'], 'DELETE':['attestation']} } ``` Trying different cases. # Test case: finding the FirmwareDumps collection entity {P461490519} Getting `/redfish/v1/Systems`: {P461490582} Getting `/redfish/v1/Systems/server4`: {P461490643} Getting `/redfish/v1/Systems/server4/Bios`: {P461490691} And, finally, getting `/redfish/v1/Systems/server4/Bios/FirmwareDumps`: {P461490735} # Test case: making a new dump Starting: {P461490844} Checking an in-progress state: {P461490877} Getting an in-progress/partial content: {P461490938} Re-getting an partial content, but now with using `start_pos` and `end_pos`: {P461491038} Getting the state after the dumping is complete: {P461492859} Getting the image: {P461492926} # Test case: create a one more image (which is forbidden) {P461493302} Try to use the same ID as the first dump: {P461493500} # Test case: delete the dump {P461493520} Reviewed By: deathowl fbshipit-source-id: 435ba748d5

Summary: In previous Diffs I added support of dumping BIOS firmware images. Which should not remain on the OpenBMC side forever (if a client forgot to request to delete an image), thus introducing a cron script which will cleanup them on a daily basis. Test Plan: It builds: {P462598932} **I have no idea how to check if the built image is valid!** But: ``` [xaionaro@devvm3590.ftw0 /data/users/xaionaro/openbmc] find build-fbnd -name biosfwimages-cleanup.sh build-fbnd/tmp/work/armv6-fb-linux-gnueabi/busybox/1.31.0-r0/cron.daily/biosfwimages-cleanup.sh build-fbnd/tmp/work/armv6-fb-linux-gnueabi/busybox/1.31.0-r0/image/etc/cron.daily/biosfwimages-cleanup.sh build-fbnd/tmp/work/armv6-fb-linux-gnueabi/busybox/1.31.0-r0/package/etc/cron.daily/biosfwimages-cleanup.sh build-fbnd/tmp/work/armv6-fb-linux-gnueabi/busybox/1.31.0-r0/packages-split/busybox/etc/cron.daily/biosfwimages-cleanup.sh build-fbnd/tmp/work/northdome-fb-linux-gnueabi/northdome-image/1.0-r0/rootfs/etc/cron.daily/biosfwimages-cleanup.sh ``` --- Validating just the script itself. Prepare: ``` root@sled3102-oob:~# mkdir /tmp/restapi-bios_images/server3/obsolete root@sled3102-oob:~# touch -d '2020-01-01' /tmp/restapi-bios_images/server3/obsolete/image root@sled3102-oob:~# mkdir '/tmp/restapi-bios_images/server3/non obsolete' ``` Run: ``` [xaionaro@devvm3590.ftw0 /data/users/xaionaro/openbmc] scp meta-facebook/recipes-core/busybox/busybox/cron.daily/biosfwimages-cleanup.sh root@rtptest6053-oob.atn1:/tmp/ biosfwimages-cleanup.sh ``` {P462599039} Reviewed By: deathowl fbshipit-source-id: d49038fb69

Summary: slot power off failed due to the changes of NIC_FW_VER_PATH (from full filepath to kv key name) remove direct file access, and replace with fby2_get_nic_mfgid function Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2702 Test Plan: 1. Build passed on northdome 2. Slot power off by power-util without fail ``` root@bmc-oob:~# for i in {1..4}; do power-util slot$i off; done Powering fru 1 to OFF state... Powering fru 2 to OFF state... Powering fru 3 to OFF state... Powering fru 4 to OFF state... root@bmc-oob:~# log-util all --print 2018 Mar 09 04:38:55 log-util: User cleared all logs 1 slot1 2018-03-09 04:40:18 gpiod FRU: 1, System powered OFF 1 slot1 2018-03-09 04:40:20 power-util SERVER_POWER_OFF successful for FRU: 1 2 slot2 2018-03-09 04:40:26 gpiod FRU: 2, System powered OFF 2 slot2 2018-03-09 04:40:28 power-util SERVER_POWER_OFF successful for FRU: 2 3 slot3 2018-03-09 04:40:34 gpiod FRU: 3, System powered OFF 3 slot3 2018-03-09 04:40:36 power-util SERVER_POWER_OFF successful for FRU: 3 4 slot4 2018-03-09 04:40:42 gpiod FRU: 4, System powered OFF 4 slot4 2018-03-09 04:40:43 power-util SERVER_POWER_OFF successful for FRU: 4 ``` Reviewed By: zhdaniel12 fbshipit-source-id: 73a697ea3a

Summary: pal.pal_get_fru_capability expects fruid to be passed (int), but name was passed to it (str). Fix this as reported by jerrt2003 Test Plan: * pick a box using libpal. * upload the latest pal.py * test in an interactive python shell ``` >>> import pal >>> fru_name_map = pal.pal_fru_name_map() >>> fru_name_map {'spb': 5, 'slot2': 2, 'slot3': 3, 'slot1': 1, 'slot4': 4, 'nic': 6} >>> fru_name_map.items() dict_items([('spb', 5), ('slot2', 2), ('slot3', 3), ('slot1', 1), ('slot4', 4), ('nic', 6)]) >>> for key, fruid in fru_name_map.items(): ... print(pal.pal_get_fru_capability(fruid)) ... {<FruCapability.FRU_CAPABILITY_SENSOR_READ: 2>, <FruCapability.FRU_CAPABILITY_SENSOR_HISTORY: 4>, <FruCapability.FRU_CAPABILITY_FRUID_READ: 1>, <FruCapability.FRU_CAPABILITY_MANAGEMENT_CONTROLLER: 7>, <FruCapability.FRU_CAPABILITY_SENSOR_THRESHOLD_UPDATE: 3>, <FruCapability.FRU_CAPABILITY_FRUID_WRITE: 0>} {<FruCapability.FRU_CAPABILITY_POWER_CYCLE: 11>, <FruCapability.FRU_CAPABILITY_SENSOR_READ: 2>, <FruCapability.FRU_CAPABILITY_SENSOR_HISTORY: 4>, <FruCapability.FRU_CAPABILITY_FRUID_READ: 1>, <FruCapability.FRU_CAPABILITY_POWER_12V_OFF: 14>, <FruCapability.FRU_CAPABILITY_POWER_12V_CYCLE: 15>, <FruCapability.FRU_CAPABILITY_POWER_RESET: 12>, <FruCapability.FRU_CAPABILITY_HAS_DEVICE: 18>, <FruCapability.FRU_CAPABILITY_POWER_STATUS: 8>, <FruCapability.FRU_CAPABILITY_SERVER: 5>, <FruCapability.FRU_CAPABILITY_POWER_12V_ON: 13>, <FruCapability.FRU_CAPABILITY_POWER_ON: 9>, <FruCapability.FRU_CAPABILITY_SENSOR_THRESHOLD_UPDATE: 3>, <FruCapability.FRU_CAPABILITY_POWER_OFF: 10>, <FruCapability.FRU_CAPABILITY_FRUID_WRITE: 0>} {<FruCapability.FRU_CAPABILITY_POWER_CYCLE: 11>, <FruCapability.FRU_CAPABILITY_SENSOR_READ: 2>, <FruCapability.FRU_CAPABILITY_SENSOR_HISTORY: 4>, <FruCapability.FRU_CAPABILITY_FRUID_READ: 1>, <FruCapability.FRU_CAPABILITY_POWER_12V_OFF: 14>, <FruCapability.FRU_CAPABILITY_POWER_12V_CYCLE: 15>, <FruCapability.FRU_CAPABILITY_POWER_RESET: 12>, <FruCapability.FRU_CAPABILITY_HAS_DEVICE: 18>, <FruCapability.FRU_CAPABILITY_POWER_STATUS: 8>, <FruCapability.FRU_CAPABILITY_SERVER: 5>, <FruCapability.FRU_CAPABILITY_POWER_12V_ON: 13>, <FruCapability.FRU_CAPABILITY_POWER_ON: 9>, <FruCapability.FRU_CAPABILITY_SENSOR_THRESHOLD_UPDATE: 3>, <FruCapability.FRU_CAPABILITY_POWER_OFF: 10>, <FruCapability.FRU_CAPABILITY_FRUID_WRITE: 0>} {<FruCapability.FRU_CAPABILITY_POWER_CYCLE: 11>, <FruCapability.FRU_CAPABILITY_SENSOR_READ: 2>, <FruCapability.FRU_CAPABILITY_SENSOR_HISTORY: 4>, <FruCapability.FRU_CAPABILITY_FRUID_READ: 1>, <FruCapability.FRU_CAPABILITY_POWER_12V_OFF: 14>, <FruCapability.FRU_CAPABILITY_POWER_12V_CYCLE: 15>, <FruCapability.FRU_CAPABILITY_POWER_RESET: 12>, <FruCapability.FRU_CAPABILITY_HAS_DEVICE: 18>, <FruCapability.FRU_CAPABILITY_POWER_STATUS: 8>, <FruCapability.FRU_CAPABILITY_SERVER: 5>, <FruCapability.FRU_CAPABILITY_POWER_12V_ON: 13>, <FruCapability.FRU_CAPABILITY_POWER_ON: 9>, <FruCapability.FRU_CAPABILITY_SENSOR_THRESHOLD_UPDATE: 3>, <FruCapability.FRU_CAPABILITY_POWER_OFF: 10>, <FruCapability.FRU_CAPABILITY_FRUID_WRITE: 0>} {<FruCapability.FRU_CAPABILITY_POWER_CYCLE: 11>, <FruCapability.FRU_CAPABILITY_SENSOR_READ: 2>, <FruCapability.FRU_CAPABILITY_SENSOR_HISTORY: 4>, <FruCapability.FRU_CAPABILITY_FRUID_READ: 1>, <FruCapability.FRU_CAPABILITY_POWER_12V_OFF: 14>, <FruCapability.FRU_CAPABILITY_POWER_12V_CYCLE: 15>, <FruCapability.FRU_CAPABILITY_POWER_RESET: 12>, <FruCapability.FRU_CAPABILITY_HAS_DEVICE: 18>, <FruCapability.FRU_CAPABILITY_POWER_STATUS: 8>, <FruCapability.FRU_CAPABILITY_SERVER: 5>, <FruCapability.FRU_CAPABILITY_POWER_12V_ON: 13>, <FruCapability.FRU_CAPABILITY_POWER_ON: 9>, <FruCapability.FRU_CAPABILITY_SENSOR_THRESHOLD_UPDATE: 3>, <FruCapability.FRU_CAPABILITY_POWER_OFF: 10>, <FruCapability.FRU_CAPABILITY_FRUID_WRITE: 0>} {<FruCapability.FRU_CAPABILITY_SENSOR_READ: 2>, <FruCapability.FRU_CAPABILITY_SENSOR_HISTORY: 4>, <FruCapability.FRU_CAPABILITY_FRUID_READ: 1>, <FruCapability.FRU_CAPABILITY_NETWORK_CARD: 6>, <FruCapability.FRU_CAPABILITY_SENSOR_THRESHOLD_UPDATE: 3>, <FruCapability.FRU_CAPABILITY_FRUID_WRITE: 0>} ``` Reviewed By: doranand fbshipit-source-id: 487fd8c6e9

Summary: adding a new job `qemu-cit`, this job will: 1. initiate a docker container using image: `ubuntu:focal` 2. download the qemu bin `qemu-system-arm` from AWS s3 storage 3. execute new test wrapper `cit_test_wrapper.py` Test Plan: Sample CirclieCI run: https://app.circleci.com/pipelines/github/facebookexternal/openbmc.wiwynn?branch=qemu-ci Reviewed By: binhuang00 fbshipit-source-id: 07f4fa7daf

Summary: This is a simple test wrapper to help container to run CIT within QEMU environment. it provides following function: 1. convert bmc image to bootable image (we are simulating a image file in flash drive thus need to pad file with 0 till 128Mb) 2. start qemu and use `pexpect` to check if image boots up successfully (checking for `login:` keywords and try to login) 3. check/wait till SSHD is up and run. 4. scp tests into BMC 5. run CIT test (using `cit_runner.py`) 6. print simple test report 7. If all tests passed, it will exit with code `0` otherwise `1`, and this return code will help circieci to determine if this job pass or not. CircleCI workflow chart: {F671288473} Test Plan: circleci sample test run: https://app.circleci.com/pipelines/github/facebookexternal/openbmc.wiwynn?branch=qemu-ci Reviewed By: zhdaniel12 fbshipit-source-id: 282cd0163b

Summary: As title, convert from hand woven main with tests to gtest. gets rid of a lot of code! Test Plan: Runs unit test. Reviewed By: zhdaniel12 fbshipit-source-id: fa07a5c2bc

Summary: 1. because nic bmc ocpdbg and vr is not had sensor list in the fru, so sensor-util should not allow these frus and not print mb sensor list. 2. These frus are reserved for the convenience of fw-util to update the FW of these frus Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2693 Test Plan: 1.Build and test pass on fbcc system. root@bmc-oob:~# sensor-util vr Usage: sensor-util [fru] <sensor num> <option> .. sensor-util [fru] <option> .. [fru] : all, mb, bsm, pdb, carrier1, carrier2, fio, nic0, nic1, nic2, nic3, nic4, nic5, nic6, nic7 [historical fru]: all, mb, bsm, pdb, carrier1, carrier2, fio, nic0, nic1, nic2, nic3, nic4, nic5, nic6, nic7 Use "aggregate" as the [fru] to print just aggregated sensors defined for this platform <sensor num>: 0xXX (Omit [sensor num] means all sensors.) <option>: --threshold show all thresholds --history <period> show max, min and average values of last <period> seconds --history <period>[m/h/d] show max, min and average values of last <period> minutes/hours/days example --history 4d means history of 4 days --history-clear clear history values --force read the sensor directly from the h/w (not cache).Ensure sensord is killed before executing this command --json JSON representation --filter <sensor name with slot name> filtered by <sensor name with slot name> for fscd usage. <sensor name with slot_name> will convert space " " to "_",and convert upper case to lower case before filtering <sensor name with slot name>: "<slot_name>_<sensor_name>" "<slot_name> <sensor_name>" e.g., sensor-util all --filter "slot2_soc_therm_margin" slot2 SOC Therm Margin (0xXX) : XX.XX C | (ok) e.g., sensor-util all --filter "slot2 SOC Therm Margin" slot2 SOC Therm Margin (0xXX) : XX.XX C | (ok) root@bmc-oob:~# sensor-util ocpdbg Usage: sensor-util [fru] <sensor num> <option> .. sensor-util [fru] <option> .. [fru] : all, mb, bsm, pdb, carrier1, carrier2, fio, nic0, nic1, nic2, nic3, nic4, nic5, nic6, nic7 [historical fru]: all, mb, bsm, pdb, carrier1, carrier2, fio, nic0, nic1, nic2, nic3, nic4, nic5, nic6, nic7 Use "aggregate" as the [fru] to print just aggregated sensors defined for this platform <sensor num>: 0xXX (Omit [sensor num] means all sensors.) <option>: --threshold show all thresholds --history <period> show max, min and average values of last <period> seconds --history <period>[m/h/d] show max, min and average values of last <period> minutes/hours/days example --history 4d means history of 4 days --history-clear clear history values --force read the sensor directly from the h/w (not cache).Ensure sensord is killed before executing this command --json JSON representation --filter <sensor name with slot name> filtered by <sensor name with slot name> for fscd usage. <sensor name with slot_name> will convert space " " to "_",and convert upper case to lower case before filtering <sensor name with slot name>: "<slot_name>_<sensor_name>" "<slot_name> <sensor_name>" e.g., sensor-util all --filter "slot2_soc_therm_margin" slot2 SOC Therm Margin (0xXX) : XX.XX C | (ok) e.g., sensor-util all --filter "slot2 SOC Therm Margin" slot2 SOC Therm Margin (0xXX) : XX.XX C | (ok) Reviewed By: tao-ren fbshipit-source-id: 2355e83817

Summary: We have finished validating ncsid and is deemed stable on current NPI platforms. Test Plan: 1. Check log-util: ``` root@bmc-oob:~# log-util all --print |grep ncsid 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type supported = 0x35 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 0 version = 1.0.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 2 version = 1.1.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 4 version = 1.0.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 5 version = 1.0.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM sensor monitoring enabled ``` 2. Check messages: ``` root@bmc-oob:~# cat /var/log/messages |grep ncsid 2021 Oct 19 13:08:53 bmc-oob. user.info fby2-v2021.42.0.Test: ncsid: send_registration_msg: registering PID 2488 2021 Oct 19 13:08:53 bmc-oob. user.info fby2-v2021.42.0.Test: ncsid: ncsid-v2 ncsi_aen_handler thread started 2021 Oct 19 13:08:53 bmc-oob. user.info fby2-v2021.42.0.Test: ncsid: NIC Firmware Version: Mellanox 14.27.2606 2021 Oct 19 13:08:53 bmc-oob. user.crit fby2-v2021.42.0.Test: ncsid: FRU: 6 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 2021 Oct 19 13:08:53 bmc-oob. user.info fby2-v2021.42.0.Test: ncsid: PLDM discovery status= 0(SUCCESS) 2021 Oct 19 13:08:53 bmc-oob. user.crit fby2-v2021.42.0.Test: ncsid: FRU: 6 PLDM type supported = 0x35 2021 Oct 19 13:08:53 bmc-oob. user.crit fby2-v2021.42.0.Test: ncsid: FRU: 6 PLDM type 0 version = 1.0.0.0 2021 Oct 19 13:08:53 bmc-oob. user.crit fby2-v2021.42.0.Test: ncsid: FRU: 6 PLDM type 2 version = 1.1.0.0 2021 Oct 19 13:08:53 bmc-oob. user.crit fby2-v2021.42.0.Test: ncsid: FRU: 6 PLDM type 4 version = 1.0.0.0 2021 Oct 19 13:08:53 bmc-oob. user.crit fby2-v2021.42.0.Test: ncsid: FRU: 6 PLDM type 5 version = 1.0.0.0 2021 Oct 19 13:08:53 bmc-oob. user.crit fby2-v2021.42.0.Test: ncsid: FRU: 6 PLDM sensor monitoring enabled 2021 Oct 19 13:08:53 bmc-oob. user.info fby2-v2021.42.0.Test: ncsid: rx: ncsi_rx_handler thread started 2021 Oct 19 13:08:53 bmc-oob. user.info fby2-v2021.42.0.Test: ncsid: ncsi_tx_handler thread started 2021 Oct 19 13:08:53 bmc-oob. user.info fby2-v2021.42.0.Test: ncsid: enable aens: mask=0x7 2021 Oct 19 13:08:53 bmc-oob. user.warning fby2-v2021.42.0.Test: ncsid: NIC link up:Rsp:0x0000 Rsn:0x0000 Link:0x71 (LF:0x1 SP:0x8 SD:0x0) Other:0x0 (Driver:0x0) OEM:0x0 2021 Oct 19 13:10:08 bmc-oob. user.warning fby2-v2021.42.0.Test: ncsid: NIC Event: , LinkStatus=0x0000-0000 // ---> test AEN, pull out network cable 2021 Oct 19 13:10:29 bmc-oob. user.warning fby2-v2021.42.0.Test: ncsid: NIC Event: , LinkStatus=0x0000-0011 // ---> test AEN, plug in network cable ``` 3. PLDM sensors: ``` root@bmc-oob:~# sensor-util nic MEZZ_SENSOR_TEMP (0x82) : 64.00 C | (ok) NIC_SOC_TEMP (PLDM) (0xB0) : 64.00 C | (ok) PORT_0_TEMP (PLDM) (0xB1) : 0.00 C | (ok) PORT_0_LINK_SPEED (PLDM) (0xB2) : 10.00 Gbps | (ok) NIC_HEALTH_STATE (PLDM) (0xC0) : Normal | (ok) PORT_0_LINK_STATE (PLDM) (0xC1) : Normal | (ok) ``` 4. Recovery Test (1) Reset channel ``` root@bmc-oob:~# ncsi-util 0x5 NC-SI Command Response: cmd: RESET_CHANNEL(0x5) Response: COMMAND_COMPLETED(0x0000) Reason: NO_ERROR(0x0000) Payload length = 4 root@bmc-oob:~# root@bmc-oob:~# [ 299.119039] Found NCSI NW Controller at (0, 0) // ---> ncsid does ifdown eth0 and then ifup eth0 [ 299.231449] NCSI: MAC EC:0D:9A:D2:CA:A7: [ 302.152579] NCSI: Mezz Vendor = Mellanox [ 306.234869] Using NCSI Network Controller (0, 0) [ 307.314835] ftgmac: eth0 AEN handler (pid:2488) registered ``` (2) Check log ``` root@bmc-oob:~# log-util all --print |grep ncsid 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type supported = 0x35 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 0 version = 1.0.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 2 version = 1.1.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 4 version = 1.0.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM type 5 version = 1.0.0.0 6 nic 2021-10-19 13:08:53 ncsid FRU: 6 PLDM sensor monitoring enabled 0 all 2021-10-19 13:12:53 ncsid re-configure NC-SI and restart eth0 interface 0 all 2021-10-19 13:13:04 ncsid re-start eth0 interface done! ret=0 ``` (3) Then check ssh to BMC ...... success Reviewed By: zhdaniel12 fbshipit-source-id: 56272b8ef1

Summary: peter_bmc@peter-bmc:~/FB_BMC$ curl -4 -X GET "http://10.10.12.116:8080/api/sled/mezz0/logs" | python -m json.tool % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2190 100 2190 0 0 753 0 0:00:02 0:00:02 --:--:-- 753 { "Actions": [ "clear" ], "Information": { "Logs": [ { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 NIC AEN Supported: 0x7, AEN Enable Mask=0x7", "TIME_STAMP": "2021-10-13 20:02:00" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type supported = 0x35", "TIME_STAMP": "2021-10-13 20:02:00" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 0 version = 1.0.0.0", "TIME_STAMP": "2021-10-13 20:02:00" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 2 version = 1.1.0.0", "TIME_STAMP": "2021-10-13 20:02:00" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 4 version = 1.0.0.0", "TIME_STAMP": "2021-10-13 20:02:00" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 5 version = 1.0.0.0", "TIME_STAMP": "2021-10-13 20:02:00" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM sensor monitoring enabled", "TIME_STAMP": "2021-10-13 20:02:00" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 NIC AEN Supported: 0x7, AEN Enable Mask=0x7", "TIME_STAMP": "2021-10-13 22:30:57" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type supported = 0x35", "TIME_STAMP": "2021-10-13 22:30:57" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 0 version = 1.0.0.0", "TIME_STAMP": "2021-10-13 22:30:57" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 2 version = 1.1.0.0", "TIME_STAMP": "2021-10-13 22:30:57" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 4 version = 1.0.0.0", "TIME_STAMP": "2021-10-13 22:30:57" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM type 5 version = 1.0.0.0", "TIME_STAMP": "2021-10-13 22:30:57" }, { "APP_NAME": "ncsid", "FRU#": "3", "FRU_NAME": "tray0_nic0", "MESSAGE": "FRU: 3 PLDM sensor monitoring enabled", "TIME_STAMP": "2021-10-13 22:30:57" } ] }, "Resources": [] } Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2710 Reviewed By: zhdaniel12 fbshipit-source-id: 9b7755af5f

Summary: As title, low risk since NCSIDv2 is backwards compatible. And since all NPI platforms have been on V2 for about a year now, this is low risk upgrade Test Plan: 1. check messages (Note FBTP does not support PLDM, so that is expected to fail) ``` root@bmc-oob:~# cat /var/log/messages |grep ncsid 2021 Oct 19 11:17:44 bmc-oob. user.info fbtp-d49038fb69-dirty: ncsid: send_registration_msg: registering PID 503 2021 Oct 19 11:17:44 bmc-oob. user.info fbtp-d49038fb69-dirty: ncsid: ncsid-v2 ncsi_aen_handler thread started 2021 Oct 19 11:17:44 bmc-oob. user.info fbtp-d49038fb69-dirty: ncsid: NIC Firmware Version: Mellanox 14.17.2058 2021 Oct 19 11:17:44 bmc-oob. user.crit fbtp-d49038fb69-dirty: ncsid: FRU: 2 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 2021 Oct 19 11:17:44 bmc-oob. user.err fbtp-d49038fb69-dirty: ncsid: send_cmd(0x51): Command failed, resp = 0x3 2021 Oct 19 11:17:44 bmc-oob. user.err fbtp-d49038fb69-dirty: ncsid: do_pldm_discovery: failed PLDM Discovery 2021 Oct 19 11:17:44 bmc-oob. user.info fbtp-d49038fb69-dirty: ncsid: enable aens: mask=0x7 2021 Oct 19 11:17:44 bmc-oob. user.info fbtp-d49038fb69-dirty: ncsid: rx: ncsi_rx_handler thread started 2021 Oct 19 11:17:44 bmc-oob. user.info fbtp-d49038fb69-dirty: ncsid: ncsi_tx_handler thread started 2021 Oct 19 11:17:44 bmc-oob. user.warning fbtp-d49038fb69-dirty: ncsid: NIC link up:Rsp:0x0000 Rsn:0x0000 Link:0x15 (LF:0x1 SP:0xa SD:0x0) Other:0x0 (Driver:0x0) OEM:0x0 2021 Oct 19 11:17:44 bmc-oob. user.warning fbtp-d49038fb69-dirty: ncsid: updated /tmp/cache_store/nic_fw_ver ``` 2. check ncsi-util ``` root@bmc-oob:~# ncsi-util 0x16 NC-SI Command Response: cmd: GET_CAPABILITIES(0x16) Response: COMMAND_COMPLETED(0x0000) Reason: NO_ERROR(0x0000) ``` 3. check log-util (FBTP does not support PLDM) ``` root@bmc-oob:~# log-util all --print |grep ncsid 2 nic 2021-07-23 14:35:08 ncsid FRU: 2 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 ``` Reviewed By: tao-ren fbshipit-source-id: 89fe3a5837

Summary: For verified boot system, when system boot into golden image (reccovery_boot) skip mount external persistent storage partition data0. The rationale is: 1. Avoid golden image boot up failure because of mounting external partition failure. 2. Avoid post decommission (erased) bootup, golden image will build up file system (pollute) flash1 again. Test Plan: Test on GrandCanyon: * set force_recovery u-boot environment to boot into golden image. ``` ... [ 26.534516] tpm_tis_spi spi2.0: 2.0 TPM (device-id 0x1B, rev-id 22) Recovery boot, skip mounting /mnt/data Starting mTerm console server...done. ... root@dhcp-100-96-192-136:~# mount none on / type rootfs (rw) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) devtmpfs on /dev type devtmpfs (rw,relatime,size=204228k,nr_inodes=51057,mode=755) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /var/volatile type tmpfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) ``` * common boot up, on GC will mount /mnt/data0 as ubifs 32MB. ``` root@dhcp-100-96-192-136:~# mount none on / type rootfs (rw) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) devtmpfs on /dev type devtmpfs (rw,relatime,size=204228k,nr_inodes=51057,mode=755) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /var/volatile type tmpfs (rw,relatime) /dev/ubi0_0 on /mnt/data type ubifs (rw,relatime,compr=zstd,assert=read-only,ubi=0,vol=0) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) root@dhcp-100-96-192-136:~# df -h Filesystem Size Used Available Use% Mounted on devtmpfs 199.4M 404.0K 199.0M 0% /dev tmpfs 219.4M 124.0K 219.3M 0% /run tmpfs 219.4M 2.4M 217.0M 1% /var/volatile /dev/ubi0_0 27.4M 40.0K 25.9M 0% /mnt/data ``` * Test on non-vboot system, yoesmite v1, booting up log ``` ... /etc/rcS.d/S05mount_data0.sh: line 269: /usr/local/bin/vboot-util: No such file or directory jffs2_mount /dev/mtdblock3 to /mnt/data.. Check jffs2 filesystem health on /dev/mtdblock3.. jffs2 health check passed: no error found. ... ``` * yosemite v1 mount and df ``` root@dhcp-100-96-192-146:~# mount rootfs on / type rootfs (rw) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) devtmpfs on /dev type devtmpfs (rw,relatime,size=115836k,nr_inodes=28959,mode=755) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /var/volatile type tmpfs (rw,relatime) /dev/mtdblock3 on /mnt/data type jffs2 (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620) root@dhcp-100-96-192-146:~# df -h Filesystem Size Used Available Use% Mounted on devtmpfs 113.1M 1.4M 111.7M 1% /dev tmpfs 120.6M 88.0K 120.5M 0% /run tmpfs 120.6M 1.4M 119.1M 1% /var/volatile /dev/mtdblock3 4.0M 336.0K 3.7M 8% /mnt/data ``` Reviewed By: doranand fbshipit-source-id: 572f9dbecf

Summary: 1. fscd will report sensor fail event while it's running before sensord started. 2. Fix the issue by waiting sensord ready flag before start fscd. (Maximum waiting time: 3 min). Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1894 Test Plan: Build and test pass on Grand Canyon. 1. Check fscd startup without fail event. * before 2018 Mar 9 04:35:10 bmc-oob. user.warning grandcanyon-v2021.40.2: fscd: nic:nic_sensor_temp Fail 2018 Mar 9 04:35:10 bmc-oob. user.warning grandcanyon-v2021.40.2: fscd: scc:scc_ioc_temp Fail 2018 Mar 9 04:35:10 bmc-oob. user.warning grandcanyon-v2021.40.2: fscd: uic:uic_inlet_temp Fail 2018 Mar 9 04:35:18 bmc-oob. user.warning grandcanyon-v2021.40.2: fscd: e1s_iocm:e1s_a1_temp Fail 2018 Mar 9 04:35:18 bmc-oob. user.warning grandcanyon-v2021.40.2: fscd: e1s_iocm:e1s_a0_temp Fail * after root@bmc-oob:~# sv status fscd run: fscd: (pid 1776) 156s root@bmc-oob:~# sv status sensord run: sensord: (pid 581) 219s root@bmc-oob:~# cat /var/log/messages | grep fscd root@bmc-oob:~# Reviewed By: peterdelevoryas fbshipit-source-id: b0fa23c74b

Summary: 1. If IOC f/w was reset while it was sending data to BMC. The slave state machine in I2C driver would not be set to "stop" so BMC couldn't write data to IOC f/w anymore. 2. Reattach IOC I2C device if BMC failed to do I2C write twice in IOCD. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1897 Test Plan: 1. Build and test pass on Grand Canyon. 2. Check there are no unexpected error logs in BMC /var/log/messages and BMC SELs. 3. Get IOC data successfully. root@bmc-oob:~# sensor-util scc | grep SCC_IOC_TEMP SCC_IOC_TEMP (0x41) : 42.00 C | (ok) root@bmc-oob:~# sensor-util e1s_iocm | grep IOCM_IOC_TEMP IOCM_IOC_TEMP (0x26) : 58.00 C | (ok) root@bmc-oob:~# fw-util scc --version Expander Version: 0x03010010 SCC IOC Version: 8.0031.02-0000 root@bmc-oob:~# fw-util iocm --version IOCM IOC Version: 8.0031.02-0000 4. Update SCC IOC f/w in UEFI and check the I2C device would be reattached. root@bmc-oob:~# cat /var/log/messages ... 2021 Oct 14 19:34:34 bmc-oob. user.warning grandcanyon-3b57d89a002: iocd: mctp_i2c_write(): Failed to write i2c raw to bus:11 2021 Oct 14 19:34:34 bmc-oob. user.warning grandcanyon-3b57d89a002: iocd: mctp_ioc_command(): failed to do 'vdm reset' on bus:11 because i2c write failed. 2021 Oct 14 19:34:34 bmc-oob. user.warning grandcanyon-3b57d89a002: iocd: check_ioc_support_pec(): VDM reset failed, bus: 11 2021 Oct 14 19:34:47 bmc-oob. user.warning grandcanyon-3b57d89a002: iocd: mctp_i2c_write(): Failed to write i2c raw to bus:11 2021 Oct 14 19:34:47 bmc-oob. user.warning grandcanyon-3b57d89a002: iocd: mctp_ioc_command(): failed to do 'vdm reset' on bus:11 because i2c write failed. 2021 Oct 14 19:34:47 bmc-oob. user.warning grandcanyon-3b57d89a002: iocd: check_ioc_support_pec(): VDM reset failed, bus: 11 2021 Oct 14 19:34:47 bmc-oob. user.warning grandcanyon-3b57d89a002: iocd: get_ioc_temp(): Failed to do i2c write, reattach i2c device on bus:11 2021 Oct 14 19:34:47 bmc-oob. kern.info grandcanyon-3b57d89a002: kernel: [ 506.475979] i2c i2c-11: delete_device: Deleting device slave-mqueue at 0x10 2021 Oct 14 19:34:47 bmc-oob. kern.info grandcanyon-3b57d89a002: kernel: [ 506.499628] i2c i2c-11: new_device: Instantiated device slave-mqueue at 0x10 - Get IOC data successfully after SCC IOC f/w updating. root@bmc-oob:~# sensor-util scc | grep SCC_IOC_TEMP SCC_IOC_TEMP (0x41) : 35.00 C | (ok) root@bmc-oob:~# sensor-util e1s_iocm | grep IOCM_IOC_TEMP IOCM_IOC_TEMP (0x26) : 47.00 C | (ok) root@bmc-oob:~# fw-util scc --version Expander Version: 0x03010010 SCC IOC Version: 8.0031.02-0000 root@bmc-oob:~# fw-util iocm --version IOCM IOC Version: 8.0031.02-0000 Reviewed By: zhdaniel12 fbshipit-source-id: c32a23b5cd

Summary: 1. add SEL log for 10K fan (only northdome) 2. increase sleep to 5 seconds (fan takes a while to stabilize) Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2707 Test Plan: 1. Build passed on northdome 2. Install 10K & 15 Fan then reboot BMC, check SEL log & fan_config - 15K Fan installed ``` root@bmc-oob:~# log-util all --print | grep 10K root@bmc-oob:~# cat /tmp/fan_config 1 ``` - 10K Fan installed, a "10K Fan detected" SEL log recorded ``` root@bmc-oob:~# log-util all --print | grep 10K 0 all 2018-03-09 04:35:26 root 10K Fan detected root@bmc-oob:~# cat /tmp/fan_config 0 ``` Reviewed By: zhdaniel12 fbshipit-source-id: 4eb1848e7e

Summary: -Fix ValueError while get endpoint /api/fwinfo and cit_runner RestEndpointTest -rest_fwinfo.py split fw-util output line by colon then assign to variables "identifier, version" but for components SB VR, the output line will split to 3 strings but only two variable to store cause this ValueError rising. ``` root@bmc-oob:~# fw-util all --version ... VCCIN_VSA Version : Renesas A8009F7D, Remaining Writes: 24 VCCIO Version : Renesas 071E99C4, Remaining Writes: 23 VDDQ_ABC Version : Renesas C7CD8991, Remaining Writes: 24 VDDQ_DEF Version : Renesas 39D8D6AA, Remaining Writes: 24 ... ``` -modify :split by first colon to guarantee only two strings for "identifier, version" Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2705 Test Plan: -Before ``` root@bmc-oob:~# curl http:/localhost:8080/api/fwinfo {"Information": {"reason": "ValueError('too many values to unpack (expected 2)')"}, "Actions": [], "Resources": []} root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py --run-test tests.fby3.test_rest_endpoint.RestEndpointTest ... ====================================================================== ERROR: test_restendpoint_/api (tests.fby3.test_rest_endpoint.RestEndpointTest) (item='fwinfo') partial(func, *args, **keywords) - new function with partial application ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/bin/tests2/common/base_rest_endpoint_test.py", line 131, in verify_endpoint_resource ) from None common.base_rest_endpoint_test.BaseRestEndpointException: HTTPError on GET /api/fwinfo : <HTTPError 500: 'Internal Server Error'> ``` -After Build OK and test on fby3 1. get endpoint OK ``` root@bmc-oob:~# curl http:/localhost:8080/api/fwinfo {"Information": {"fruid_info": {"slot1": {"vendor": "Quanta", "model": "Delta Lake-Class1", "serial_number": "TW3YX04200029", "part_number": "N/A"}, "nic": {"vendor": "Broadcom", "model": "BRCM 100G 1P 57504 OCP Mezz", "serial_number": "N1100FY19450001MCQ", "part_number": "BCM957504-N1100FY"}, "nicexp": {"vendor": null, "model": null, "serial_number": null, "part_number": null}}, "fw_info": {"bmc_ver": "fby3-d83e710a465-dirty", "bmc_cpld_ver": "00030A04", "bic_version": "NA (2ou is empty)"}}, "Actions": [], "Resources": []} ``` 2.cit_runner tests.fby3.test_rest_endpoint.RestEndpointTest OK ``` root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py --run-test tests.fby3.test_rest_endpoint.RestEndpointTest test_restendpoint_/api (tests.fby3.test_rest_endpoint.RestEndpointTest) partial(func, *args, **keywords) - new function with partial application ... ok test_restendpoint_/api/bmc (tests.fby3.test_rest_endpoint.RestEndpointTest) partial(func, *args, **keywords) - new function with partial application ... ok ....... test_restendpoint_/api/spb/logs (tests.fby3.test_rest_endpoint.RestEndpointTest) partial(func, *args, **keywords) - new function with partial application ... ok test_restendpoint_/api/spb/sensors (tests.fby3.test_rest_endpoint.RestEndpointTest) partial(func, *args, **keywords) - new function with partial application ... ok test_server_httperror_code_404 (tests.fby3.test_rest_endpoint.RestEndpointTest) Test if REST server return 404 code when url is not accessible ... ok ---------------------------------------------------------------------- Ran 68 tests in 1192.402s OK ``` Reviewed By: zhdaniel12 fbshipit-source-id: a0812f476f

…log (#2711) Summary: wrong array index calculated due to MAX_NUM_FRUS changed replace calculation by using slot_id directly Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2711 Test Plan: 1. Build passed on northdome 2. Test slot removal & insertion, SEL should recorded slot id correctly - Before ``` root@bmc-oob:~# log-util all --print 2018 Mar 09 04:36:54 log-util: User cleared all logs 1 slot1 2018-03-09 04:37:01 gpiointrd FRU: 1, SLOT1_EJECTOR_LATCH is not closed while in VCubby 1 slot1 2018-03-09 04:37:18 gpiointrd FRU: 1, Slot3 Removal Without 12V-OFF 1 slot1 2018-03-09 04:37:33 gpiointrd FRU: 1, Slot2 Insertion ``` - After ``` root@bmc-oob:~# log-util all --print 2018 Mar 09 04:36:00 log-util: User cleared all logs 1 slot1 2018-03-09 04:36:10 gpiointrd FRU: 1, SLOT1_EJECTOR_LATCH is not closed while in VCubby 1 slot1 2018-03-09 04:36:12 gpiointrd FRU: 1, Slot1 Removal Without 12V-OFF 1 slot1 2018-03-09 04:36:24 gpiointrd FRU: 1, Slot1 Insertion ``` Reviewed By: zhdaniel12 fbshipit-source-id: c08eaac3cb

Summary: update build name from `fbgc` to `grandcanyon` to match build name defined in `platforms.thrift` Test Plan: Sandcastle CIT run: https://www.internalfb.com/intern/sandcastle/job/36028797524301144/ Reviewed By: zhdaniel12 fbshipit-source-id: 867b6fcd07

Summary: 1. add platform layer get_fan_mode support 2. set fan duty base on thermal team's request sensor_fail: 60% sensor_hit_UCR: 100% Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2691 Test Plan: 1. Build and test passed on northdome & fby3 2. fscd running normally without unexpected error log Reviewed By: amithash fbshipit-source-id: 6aa6e4c2d2

Summary: Preliminary support for Config_B: (1) show_sys_config (2) load fsc table Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2709 Test Plan: Build and test pass on fby35 (Used DP riser to test Riser Present) root@bmc-oob:~# show_sys_config Type : Class 1, Config: B --------------------------- Slot1 : Present, Config B Slot3 : Present, Config B Reviewed By: zhdaniel12 fbshipit-source-id: 58725734f4

Summary: as title Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2708 Test Plan: Build and tested pass on fby35 Reviewed By: GoldenBug fbshipit-source-id: 2ce3ba4c6a

…895) Summary: - This commit provides new bic-util options to set/get cwc usb hub mux status Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1895 Test Plan: - Check if cwc usb hub mux can be set/get by bic-uitl - pass Log: root@bmc-oob:~# bic-util Usage: bic-util <slot1|slot2|slot3|slot4> <[0..n]data_bytes_to_send> Usage: bic-util <slot1|slot2|slot3|slot4> <2U-cwc|2U-top|2U-bot> <[0..n]data_bytes_to_send> Usage: bic-util <slot1|slot2|slot3|slot4> <option> Usage: bic-util <slot1|slot2|slot3|slot4> <2U-cwc|2U-top|2U-bot> <option> option: --get_gpio --set_gpio [gpio_num] [value] --get_gpio_config --set_gpio_config $gpio_num $value --check_status --get_dev_id --reset --get_post_code --get_sdr --read_sensor --perf_test [loop_count] (0 to run forever) --clear_cmos --file [path] --check_usb_port [sb|1ou|2ou] --get_board_revision 1ou --get_slot_id --set_usb_hub [0|1|2|all] [on|off|reset|to-bmc|to-usbc] --get_usb_hub [0|1|2|all] --get_pci_link root@bmc-oob:~# bic-util slot1 2U-cwc --get_usb_hub 0 USB HUB0 is on USB HUB is switched to bmc root@bmc-oob:~# bic-util slot1 2U-cwc --set_usb_hub 0 to-usbc root@bmc-oob:~# bic-util slot1 2U-cwc --get_usb_hub 0 USB HUB0 is on USB HUB is switched to usb c root@bmc-oob:~# bic-util slot1 2U-cwc --set_usb_hub 0 to-bmc root@bmc-oob:~# bic-util slot1 2U-cwc --get_usb_hub 0 USB HUB0 is on USB HUB is switched to bmc root@bmc-oob:~# Reviewed By: zhdaniel12 fbshipit-source-id: 1bf6e6db10

…evices by usbip (#1896) Summary: - There are many steps to bind a usb device on usbip server side, this commit provide a script in bmc fw to simplify the process to bind/unbind usb devices. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1896 Test Plan: - Check if usb devices can be bind/unbind on cwc and gpv3 - pass Log: - on gpv3 root@bmc-oob:~# usb-util.sh Usage: usb-util.sh [ bind | unbind ] [ slot1-2U | slot1-2U-exp | slot1-2U-top | slot1-2U-bot ] [ pesw-uart, uart0, uart1, uart2, dev0, dev1, ..., dev11 ] Usage: usb-util.sh bus-id [ slot1-2U | slot1-2U-exp | slot1-2U-top | slot1-2U-bot ] [ pesw-uart, uart0, uart1, uart2, dev0, dev1, ..., dev11 ] root@bmc-oob:~# usb-util.sh bus-id slot1-2U dev0 slot1-2U dev0 usb bus id is 1-1.3.4.1 root@bmc-oob:~# usb-util.sh bind slot1-2U dev0 Initializing USB devs... 1-1.3.4.1 usbip: info: bind device on busid 1-1.3.4.1: complete root@bmc-oob:~# usb-util.sh unbind slot1-2U dev0 usbip: info: unbind device on busid 1-1.3.4.1: complete root@bmc-oob:~# usb-util.sh bind slot1-2U dev0 1-1.3.4.1 usbip: info: bind device on busid 1-1.3.4.1: complete root@bmc-oob:~# usb-util.sh bind slot1-2U dev1 1-1.3.3.1 usbip: info: bind device on busid 1-1.3.3.1: complete root@bmc-oob:~# usb-util.sh bind slot1-2U pesw-uart 1-1.3.4.2.4 usbip: info: bind device on busid 1-1.3.4.2.4: complete root@bmc-oob:~# usb-util.sh bind slot1-2U uart0 1-1.3.1 usbip: info: bind device on busid 1-1.3.1: complete root@bmc-oob:~# - on cwc root@bmc-oob:~# usb-util.sh Usage: usb-util.sh [ bind | unbind ] [ slot1-2U | slot1-2U-exp | slot1-2U-top | slot1-2U-bot ] [ pesw-uart, uart0, uart1, uart2, dev0, dev1, ..., dev11 ] Usage: usb-util.sh bus-id [ slot1-2U | slot1-2U-exp | slot1-2U-top | slot1-2U-bot ] [ pesw-uart, uart0, uart1, uart2, dev0, dev1, ..., dev11 ] root@bmc-oob:~# usb-util.sh binf slot1-2U-top dev0 Usage: usb-util.sh [ bind | unbind ] [ slot1-2U | slot1-2U-exp | slot1-2U-top | slot1-2U-bot ] [ pesw-uart, uart0, uart1, uart2, dev0, dev1, ..., dev11 ] Usage: usb-util.sh bus-id [ slot1-2U | slot1-2U-exp | slot1-2U-top | slot1-2U-bot ] [ pesw-uart, uart0, uart1, uart2, dev0, dev1, ..., dev11 ] root@bmc-oob:~# usb-util.sh bind slot1-2U-top dev0 Initializing USB devs... 1-1.3.1.4.1 usbip: info: bind device on busid 1-1.3.1.4.1: complete root@bmc-oob:~# usb-util.sh unbind slot1-2U-top dev0 usbip: info: unbind device on busid 1-1.3.1.4.1: complete root@bmc-oob:~# usb-util.sh bind slot1-2U-top dev0 1-1.3.1.4.1 usbip: info: bind device on busid 1-1.3.1.4.1: complete root@bmc-oob:~# usb-util.sh bind slot1-2U-top dev11 1-1.3.1.3.2.4 usbip: info: bind device on busid 1-1.3.1.3.2.4: complete root@bmc-oob:~# usb-util.sh bind slot1-2U-top pesw-uart 1-1.3.1.4.2.4 usbip: info: bind device on busid 1-1.3.1.4.2.4: complete root@bmc-oob:~# usb-util.sh bind slot1-2U-top uart0 1-1.3.1.1 usbip: info: bind device on busid 1-1.3.1.1: complete root@bmc-oob:~# usb-util.sh bind slot1-2U-exp pesw-uart 1-1.3.2.2 usbip: info: bind device on busid 1-1.3.2.2: complete root@bmc-oob:~# usb-util.sh bus-id slot1-2U-exp pesw-uart slot1-2U-exp pesw-uart usb bus id is 1-1.3.2.2 root@bmc-oob:~# Reviewed By: zhdaniel12 fbshipit-source-id: 1bb5b7697a

Summary: handle_flashy_error() was returning the exit code of an "echo" command instead of the exit code of the flashy binary. It wasn't noticed till now since this is only used manually and in CIT. Test Plan: Fake up a dodgy flashy binary on my devserver and try the script out: ``` 0 ~/local/openbmc/tools/flashy/scripts $ cat /opt/flashy/flashy exit 66 0 ~/local/openbmc/tools/flashy/scripts $ ./run_flashy.sh --device mtd:flash0 Getting buildname of device Buildname: Rotor 2021 Installing flashy 66 ~/local/openbmc/tools/flashy/scripts $ echo $? 66 ``` Reviewed By: lhl2617 fbshipit-source-id: 36ad0fdab2

Summary: This allows us to do things like ``` openbmc::syslog_crit << "This is a log " << 1 << '\n'; ``` wrapping around the good old ``` syslog(LOG_CRIT, "This is a log %d\n", 1); ``` More importantly, now that syslog is a ostream type class, it becomes first class with cout, cerr, ofstream and stringstream. What this gives us is a way to unit test syslog messages in daemons/utilities. Just replace the syslog_err with stringstream and viola you can now see what would have gone to syslog. Test Plan: Tested on dev system to ensure that things were reaching /var/log/messages. ``` #include "syslog.hpp" int main(void) { openbmc::syslog_crit << "Hello world" << std::endl; } ``` output in /var/log/messages ``` Oct 18 19:23:10 <snip hostname> a.out: Hello world ``` Reviewed By: zhdaniel12 fbshipit-source-id: 2141ff1d7b

Summary: consider the current circleci workflow, we don't need to build the `qemux86` again during the `build` step since that image will be built and tests (ptest) in `unittest` step. {F671947342} Test Plan: passed circleci Reviewed By: amithash fbshipit-source-id: 800f51b686

Summary: As the title. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1256 Test Plan: Build success for wedge400. Reviewed By: zhdaniel12 fbshipit-source-id: fcebe38f55

Summary: Summary : modify board_ver bit length in smb_syscpld follow cpld changing. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1255 Test Plan: ``` root@bmc-oob:~# source /usr/local/bin/openbmc-utils.sh root@bmc-oob:~# wedge_board_type_rev WEDGE400-C_DVT root@bmc-oob:~# cat /sys/bus/i2c/devices/12-003e/board_type 0x1 Note: 0: Wedge400 1: Wedge400-C Bit[5:4] @ register 0x0, register value 0x12 root@bmc-oob:~# cat /sys/bus/i2c/devices/12-003e/board_ver 0x2 Note: Bit[2:0] @ register 0x0, register value 0x12 root@bmc-oob:~# ``` Reviewed By: zhdaniel12 fbshipit-source-id: 509f0c8435

Summary: As the title. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1257 Test Plan: build success by wedge400. Reviewed By: tao-ren fbshipit-source-id: 09d5942068

Summary: 1. Check cfg-util can get one value, get multiple values, and set value successfully. 2. Check CPU utilization is normal in the case that excluding some needed but quite unpredictable processes. 3. Check eth0 ipv6 interface is normal. 4. Check all BMC GPIOs are normal. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1899 Test Plan: 1. CfgUtilTest is pass. root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py -p grandcanyon --run-test tests.grandcanyon.test_cfg_util.CfgUtilTest test_cfg_util_set (tests.grandcanyon.test_cfg_util.CfgUtilTest) To test cfg-uti to set server_por_cfg value to on then back to original value ... ok test_cfg_util_show (tests.grandcanyon.test_cfg_util.CfgUtilTest) To test cfg-uti to show individual key ... ok test_dump_all (tests.grandcanyon.test_cfg_util.CfgUtilTest) To test cfg-util dump-all ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.354s OK 2. CpuUtilizationTest is pass. root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py -p grandcanyon --run-test tests.grandcanyon.test_cpu_utilization.CpuUtilizationTest test_cpu_utilization (tests.grandcanyon.test_cpu_utilization.CpuUtilizationTest) This test is ran a specific number of time ... ok ---------------------------------------------------------------------- Ran 1 test in 61.782s OK 3. InterfaceTest is pass. root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py -p grandcanyon --run-test tests.grandcanyon.test_interface.InterfaceTest test_eth0_v4_interface (tests.grandcanyon.test_interface.InterfaceTest) Tests eth0 v4 interface ... skipped 'Test not supported in environment' test_eth0_v6_interface (tests.grandcanyon.test_interface.InterfaceTest) Tests eth0 v6 interface ... ok ---------------------------------------------------------------------- Ran 2 tests in 0.048s OK (skipped=1) 4. GpioTest is pass. root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py -p grandcanyon --run-test tests.grandcanyon.test_gpios.GpioTest test_gpios (tests.grandcanyon.test_gpios.GpioTest) ... ok ---------------------------------------------------------------------- Ran 1 test in 0.124s OK Reviewed By: peterdelevoryas fbshipit-source-id: 70c425a327

Summary: If uServer is powered down with wedge_power.sh, and it becomes impossible to read sensors from COMe (uServer) due to some unexpected condition, then the following can occur: - fscd throws an exception trying to read sensors - this causes fscd to die - BMC then suffers watchdog reset after ~30s - BMC turns uServer power back on when coming back up Test Plan: Test change on device in unprovisioning (rsw1hi-oob.06.ftw1): ``` $ rebootservicecli poweroff --OperationType HARD --wait rsw1hi.06.ftw1.facebook.com ``` Observe the BMC does not reboot but instead logs an error: ``` 2021 Oct 22 09:43:59 bmc user.crit wedge100-v2021.35.0: fscd: Exception while trying to read '/sys/bus/i2c/devices/4-0033/temp1_input': OSError(6, 'No such device or address') ``` Reviewed By: vineelasmile fbshipit-source-id: a56c8e776c

Summary: 1. Support CIT test for PPR test. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1891 Test Plan: 1. Build and test pass on Grand Canyon with test BIOS firmware. 2. Check there are no unexpected error logs in BMC /var/log/messages and BMC SELs 3. PPR test pass. (1) Set up BIOS setting for PPR test. (2) Run PPR test root@guaigaui-Freedom:~/Ricky/tests2# python3 cit_runner.py --platform fbgc --run-test tests.fbgc.external_ppr_test --external --host 192.168.88.35 --bmc-host 192.168.88.33 test_ppr (tests.fbgc.external_ppr_test.PPRTest) ... ====== PPR test information ====== BMC IP: 192.168.88.33 Slot Number: 1 PPR function: Soft System DIMM Quantity: 4 ====== Inject PPR error ====== Inject memory error for DIMM#0 Inject memory error for DIMM#1 Inject memory error for DIMM#2 Inject memory error for DIMM#3 Inject memory error successfully Memory correctable error SEL in BMC: 1 server 2021-10-15 00:13:35 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 00, Slot 00, DIMM A0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:40 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 01, Slot 00, DIMM B0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:45 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 03, Slot 00, DIMM D0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:50 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 04, Slot 00, DIMM E0, DIMM Failure Event: Memory correctable error ====== Get DIMM Row Count ====== 4 ====== Get DIMM Row Address ====== 00 01 00 00 00 00 00 00 01 01 04 00 00 00 00 00 02 01 0C 00 00 00 00 00 03 01 10 00 00 00 00 00 ====== Enable Soft PPR function ====== Enable PPR function successfully ====== Get PPR History Data ====== 00 FB EE EE BF AA 23 19 5D 61 D2 27 69 61 03 00 A0 01 FB EE EE BF A8 24 19 5D 61 D3 27 69 61 03 00 B0 02 FB EE EE BF A6 25 19 5D 61 D4 27 69 61 03 00 D0 03 FB EE EE BF A6 25 19 5D 61 D4 27 69 61 03 00 E0 <<< Restart System >>> ====== PPR SEL LOG ====== 1 server 2021-10-15 00:13:35 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 00, Slot 00, DIMM A0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:40 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 01, Slot 00, DIMM B0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:45 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 03, Slot 00, DIMM D0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:50 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 04, Slot 00, DIMM E0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:14:01 gpiod FRU: 1, Server is powered off 1 server 2021-10-15 00:14:09 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2021-10-15 00:14:09, Sensor: ME_POWER_STATE (0x16), Event Data: (000000) RUNNING Assertion 1 server 2021-10-15 00:14:10 power-util SERVER_POWER_CYCLE successful for FRU: 1 1 server 2021-10-15 00:14:10 gpiod FRU: 1, Server is powered on 1 server 2021-10-15 00:14:26 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 00, Slot 00, DIMM A0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:27 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 01, Slot 00, DIMM B0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 03, Slot 00, DIMM D0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 04, Slot 00, DIMM E0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:28, MFG ID: 9c9c00, OEM Data: (A00100000000) 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:28, MFG ID: 9c9c00, OEM Data: (B00100000000) 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:28, MFG ID: 9c9c00, OEM Data: (D00100000000) 1 server 2021-10-15 00:14:29 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:29, MFG ID: 9c9c00, OEM Data: (E00100000000) ====== Get PPR History Data ====== 00 FB EE EE BF 25 23 19 5D 61 53 2A 69 61 04 00 A0 01 FB EE EE BF 24 24 19 5D 61 53 2A 69 61 04 00 B0 02 FB EE EE BF 22 25 19 5D 61 54 2A 69 61 04 00 D0 03 FB EE EE BF 21 25 19 5D 61 55 2A 69 61 04 00 E0 ok ---------------------------------------------------------------------- Ran 1 test in 100.095s OK Reviewed By: jerrt2003 fbshipit-source-id: 5b828a99f8

Summary: Change platform name from 'fbgc' to 'grandcanyon'. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1900 Test Plan: 1. Check FwUtilVersionTest can run pass. - Before root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py -p grandcanyon --run-test tests.grandcanyon.test_fw_util.FwUtilVersionTest test_version_header (tests.grandcanyon.test_fw_util.FwUtilVersionTest) ... ERROR ====================================================================== ERROR: test_version_header (tests.grandcanyon.test_fw_util.FwUtilVersionTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/bin/tests2/common/base_fw_util_test.py", line 50, in setUp with open( FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/bin/tests2/tests/fbgc/test_data/fwutil/fw_util_list.json' - After root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py -p grandcanyon --run-test tests.grandcanyon.test_fw_util.FwUtilVersionTest test_version_header (tests.grandcanyon.test_fw_util.FwUtilVersionTest) ... ok ---------------------------------------------------------------------- Ran 1 test in 2.416s OK Reviewed By: peterdelevoryas fbshipit-source-id: ae54cee237

Summary: - Currently, it will take longer to cache all device fru if some of the devices have no fru, or the device takes long time to get nvme ready. This commit reduce the retries for each device every loop, and bypass nvme ready to shorten the time needed for caching fru. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1902 Test Plan: - Check if device fru can be read more quickly - pass Log: - on cwc root@bmc-oob:~# fruid-util slot1 2U-top 2U-dev0 FRU Information : TOP GPV3 2U-dev0 --------------- : ------------------ Board Mfg Date : Mon Jan 25 23:57:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210307093 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210307093 Product Asset Tag : Product FRU ID : 0.35 root@bmc-oob:~# fruid-util slot1 2U-bot 2U-dev0 FRU Information : BOT GPV3 2U-dev0 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA root@bmc-oob:~# fruid-util slot1 2U-top 2U-dev11 FRU Information : TOP GPV3 2U-dev11 --------------- : ------------------ Board Mfg Date : Sun Oct 10 01:00:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306860 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306860 Product Asset Tag : Product FRU ID : 0.35 root@bmc-oob:~# fruid-util slot1 2U-bot 2U-dev11 FRU Information : BOT GPV3 2U-dev11 --------------- : ------------------ Board Mfg Date : Wed Jan 27 03:37:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306950 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306950 Product Asset Tag : Product FRU ID : 0.35 root@bmc-oob:~# Reviewed By: zhdaniel12 fbshipit-source-id: 36f4beff48

…?=20error=20cases=20of=20sensor=20from=20Redfish=20Service=20Val?= =?UTF-8?q?id=E2=80=A6?= (#1898) Summary: …ator 1. Support to get sensor that the fru name contains "_". 2. The properties of "Thresholds" should be JSON object. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1898 Test Plan: 1. Build and test pass on Grand Canyon. 2. Check there are no unexpected error logs in BMC /var/log/messages and BMC SELs. 3. Get sensor URI of FRU: e1s_iocm successfully. - Before root@bmc-oob:~#:/usr/local/fbpackages/rest-api# curl -kvvvv http://127.0.0.1:8080/redfish/v1/Chassis/1/Sensors/e1s_iocm_32 | python3 -m json.tool ... { "Information": { "reason": "ValueError(\"invalid literal for int() with base 10: 'iocm'\")" }, "Actions": [], "Resources": [] } - After root@bmc-oob:~# curl -kvvvv http://127.0.0.1:8080/redfish/v1/Chassis/1/Sensors/e1s_iocm_32 | python3 -m json.tool ... { "odata.type": "#Sensor.v1_2_0.Sensor", "Id": "32", "Name": "e1s_iocm/e1s_iocm/E1S_B0_CUR", "Oem": {}, "PhysicalContext": "Chassis", "Status": { "State": "Enabled", "Health": "OK" }, "Reading": 0.23000000417232513, "ReadingUnits": "Amps", "ReadingRangeMin": -99999, "ReadingRangeMax": 99999, "Thresholds": { "UpperCaution": { "Reading": 0 }, "UpperCritical": { "Reading": 1 }, "UpperFatal": { "Reading": 0 }, "LowerCaution": { "Reading": 0 }, "LowerCritical": { "Reading": 0 }, "LowerFatal": { "Reading": 0 } }, "odata.id": "/redfish/v1/Chassis/1/Sensors/e1s_iocm_32" } 4. Run Redfish Service Validator for sensor successfully. - Before (1) E1S_B0_CUR root@guaigaui-Freedom:~/Ricky/OCP/service/Redfish-Service-Validator# python3.8 RedfishServiceValidator.py --ip http://192.168.88.46:8080 --payload Single /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 Redfish Service Validator, version 2.0.3 ... *** /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 Attempt 1 of /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 Response Time for GET to /redfish/v1/Chassis/1/Sensors/e1s_iocm_32: 0.009495147038251162 seconds. URI did not return resource /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 Metadata: Namespaces missing from $metadata: set() Elapsed time: 0:02:01 1 failGet errors in /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 failGet: 1 metadataNamespaces: 2263 Validation has failed: 1 problems found (2) BS_INLET_TEMP root@guaigaui-Freedom:~/Ricky/OCP/service/Redfish-Service-Validator# python3.8 RedfishServiceValidator.py --ip http://192.168.88.46:8080 --payload Single /redfish/v1/Chassis/1/Sensors/server_1 Redfish Service Validator, version 2.0.3 ... *** /redfish/v1/Chassis/1/Sensors/server_1 Attempt 1 of /redfish/v1/Chassis/1/Sensors/server_1 Response Time for GET to /redfish/v1/Chassis/1/Sensors/server_1: 0.015173589810729027 seconds. Unable to gather property info for URI /redfish/v1/Chassis/1/Sensors/server_1: AttributeError("'int' object has no attribute 'get'") Metadata: Namespaces missing from $metadata: set() Elapsed time: 0:02:00 1 exceptionResource errors in /redfish/v1/Chassis/1/Sensors/server_1 exceptionResource: 1 metadataNamespaces: 2263 Validation has failed: 1 problems found - After (1) E1S_B0_CUR root@guaigaui-Freedom:~/Ricky/OCP/service/Redfish-Service-Validator# python3.8 RedfishServiceValidator.py --ip http://192.168.88.46:8080 --payload Single /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 Redfish Service Validator, version 2.0.3 ... *** /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 Attempt 1 of /redfish/v1/Chassis/1/Sensors/e1s_iocm_32 Response Time for GET to /redfish/v1/Chassis/1/Sensors/e1s_iocm_32: 0.01086290180683136 seconds. Type (Sensor.v1_2_0.Sensor), GET SUCCESS (time: 0:00:00.011411) PASS Metadata: Namespaces missing from $metadata: set() Elapsed time: 0:02:01 metadataNamespaces: 2263 pass: 15 passGet: 1 skipOptional: 50 Validation has succeeded. (2) BS_INLET_TEMP root@guaigaui-Freedom:~/Ricky/OCP/service/Redfish-Service-Validator# python3.8 RedfishServiceValidator.py --ip http://192.168.88.46:8080 --payload Single /redfish/v1/Chassis/1/Sensors/server_1 Redfish Service Validator, version 2.0.3 ... *** /redfish/v1/Chassis/1/Sensors/server_1 Attempt 1 of /redfish/v1/Chassis/1/Sensors/server_1 Response Time for GET to /redfish/v1/Chassis/1/Sensors/server_1: 0.008306454867124557 seconds. Type (Sensor.v1_2_0.Sensor), GET SUCCESS (time: 0:00:00.008794) PASS Metadata: Namespaces missing from $metadata: set() Elapsed time: 0:02:01 metadataNamespaces: 2263 pass: 15 passGet: 1 skipOptional: 50 Validation has succeeded. Reviewed By: williamspatrick fbshipit-source-id: 62533944b1

Summary: 1. Support CIT test for PPR test. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1892 Test Plan: 1. Build and test pass on Grand Canyon with test BIOS image. 2. Check there are no unexpected error logs in BMC /var/log/messages and BMC SELs 3. PPR test pass. (1) Set up BIOS setting for PPR test. (2) Run PPR test root@guaigaui-Freedom:~/Ricky/tests2# python3 cit_runner.py --platform fbgc --run-test tests.fbgc.external_ppr_test --external --host 192.168.88.35 --bmc-host 192.168.88.33 test_ppr (tests.fbgc.external_ppr_test.PPRTest) ... ====== PPR test information ====== BMC IP: 192.168.88.33 Slot Number: 1 PPR function: Soft System DIMM Quantity: 4 ====== Inject PPR error ====== Inject memory error for DIMM#0 Inject memory error for DIMM#1 Inject memory error for DIMM#2 Inject memory error for DIMM#3 Inject memory error successfully Memory correctable error SEL in BMC: 1 server 2021-10-15 00:13:35 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 00, Slot 00, DIMM A0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:40 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 01, Slot 00, DIMM B0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:45 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 03, Slot 00, DIMM D0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:50 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 04, Slot 00, DIMM E0, DIMM Failure Event: Memory correctable error ====== Get DIMM Row Count ====== 4 ====== Get DIMM Row Address ====== 00 01 00 00 00 00 00 00 01 01 04 00 00 00 00 00 02 01 0C 00 00 00 00 00 03 01 10 00 00 00 00 00 ====== Enable Soft PPR function ====== Enable PPR function successfully ====== Get PPR History Data ====== 00 FB EE EE BF AA 23 19 5D 61 D2 27 69 61 03 00 A0 01 FB EE EE BF A8 24 19 5D 61 D3 27 69 61 03 00 B0 02 FB EE EE BF A6 25 19 5D 61 D4 27 69 61 03 00 D0 03 FB EE EE BF A6 25 19 5D 61 D4 27 69 61 03 00 E0 <<< Restart System >>> ====== PPR SEL LOG ====== 1 server 2021-10-15 00:13:35 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 00, Slot 00, DIMM A0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:40 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 01, Slot 00, DIMM B0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:45 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 03, Slot 00, DIMM D0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:13:50 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MEMORY_ECC_ERR(0x21), DIMM Slot Location: Sled 01/Socket 00, Channel 04, Slot 00, DIMM E0, DIMM Failure Event: Memory correctable error 1 server 2021-10-15 00:14:01 gpiod FRU: 1, Server is powered off 1 server 2021-10-15 00:14:09 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2021-10-15 00:14:09, Sensor: ME_POWER_STATE (0x16), Event Data: (000000) RUNNING Assertion 1 server 2021-10-15 00:14:10 power-util SERVER_POWER_CYCLE successful for FRU: 1 1 server 2021-10-15 00:14:10 gpiod FRU: 1, Server is powered on 1 server 2021-10-15 00:14:26 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 00, Slot 00, DIMM A0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:27 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 01, Slot 00, DIMM B0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 03, Slot 00, DIMM D0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: Facebook Unified SEL (0xFB), GeneralInfo: MemEvent(0x2A), DIMM Slot Location: Sled 01/Socket 00, Channel 04, Slot 00, DIMM E0, DIMM Failure Event: PPR success 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:28, MFG ID: 9c9c00, OEM Data: (A00100000000) 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:28, MFG ID: 9c9c00, OEM Data: (B00100000000) 1 server 2021-10-15 00:14:28 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:28, MFG ID: 9c9c00, OEM Data: (D00100000000) 1 server 2021-10-15 00:14:29 ipmid SEL Entry: FRU: 1, Record: OEM timestamped (0xD0), Time: 2021-10-15 00:14:29, MFG ID: 9c9c00, OEM Data: (E00100000000) ====== Get PPR History Data ====== 00 FB EE EE BF 25 23 19 5D 61 53 2A 69 61 04 00 A0 01 FB EE EE BF 24 24 19 5D 61 53 2A 69 61 04 00 B0 02 FB EE EE BF 22 25 19 5D 61 54 2A 69 61 04 00 D0 03 FB EE EE BF 21 25 19 5D 61 55 2A 69 61 04 00 E0 ok ---------------------------------------------------------------------- Ran 1 test in 100.095s OK Reviewed By: peterdelevoryas fbshipit-source-id: 65a90722e0

Summary: for fbtp we have 2 NIC vender. Need to include both of them into the fw-util checking list Test Plan: root@dhcp-100-96-192-192:~# python3 /usr/local/bin/tests2/cit_runner.py --run-test tests.fbtp.test_fw_util.FwUtilVersionTest.test_version_header test_version_header (tests.fbtp.test_fw_util.FwUtilVersionTest) ... ok ---------------------------------------------------------------------- Ran 1 test in 2.603s OK Reviewed By: zhdaniel12 fbshipit-source-id: 44f450959b

Summary: Update fscd version 20211005 base on thermal team's request 1. sensor fail: 60% 2. sensor UCR: 100% This commit needs to be tested with another PR https://github.com/facebookexternal/openbmc.quanta/issues/2691 together Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2697 Test Plan: 1. Build and test passed on northdome 2. fscd running normally without unexpected error log 3. fan pwm duty works as expected Reviewed By: amithash fbshipit-source-id: e446afee99

Summary: after discussing with amithash we will remove the test from fbtp Test Plan: not required Reviewed By: peterdelevoryas fbshipit-source-id: d056784e5f

Summary: we have different kinds of fbtp configuration in our CIT pool. For certain type for tiogapass we don't have riser_slot. We need to skip fruid-util test against riser_slot for those platforms to reduce test result noise. Test Plan: ``` root@dhcp-100-96-192-135:/usr/local/bin/tests2# python3 /usr/local/bin/tests2/cit_runner.py --run-test tests.fbtp.test_fru test_fru_fields (tests.fbtp.test_fru.FruMbTest) ... ok test_fru_fields (tests.fbtp.test_fru.FruRiserSlot2Test) ... skipped 'skip test due to missing riser_slot' test_fru_fields (tests.fbtp.test_fru.FruRiserSlot3Test) ... skipped 'skip test due to missing riser_slot' test_fru_fields (tests.fbtp.test_fru.FruRiserSlot4Test) ... skipped 'skip test due to missing riser_slot' ---------------------------------------------------------------------- Ran 4 tests in 0.619s OK (skipped=3) ``` Reviewed By: zhdaniel12 fbshipit-source-id: 9eeddb2b6b

…h unspecified unit (#2698) Summary: as title Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2698 Test Plan: 1. Build and test passed on northdome 2. check "Soc Temp" sensor through restapi - before, threshold was missing ``` root@bmc-oob:~# sensor-util slot1 0x5 -t SOC Temp (0x5) : 40.00 | (ok) | UCR: 100.00 | UNC: NA | UNR: NA | LCR: NA | LNC: NA | LNR: NA root@bmc-oob:~# curl -g 'http://127.0.0.1:8080/api/server1/sensors?name=Soc%20Temp&display=units,thresholds' | python -m json.tool % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 111 100 111 0 0 55 0 0:00:02 0:00:02 --:--:-- 55 { "Actions": [ "history-clear" ], "Information": { "SOC Temp": { "units": "na", "value": "40.00" } }, "Resources": [] } ``` - after, shows corrected information ``` root@bmc-oob:~# sensor-util slot1 0x5 -t SOC Temp (0x5) : 40.00 | (ok) | UCR: 100.00 | UNC: NA | UNR: NA | LCR: NA | LNC: NA | LNR: NA root@bmc-oob:~# curl -g 'http://127.0.0.1:8080/api/server1/sensors?name=Soc%20Temp&display=units,thresholds' | python -m json.tool % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 142 100 142 0 0 49 0 0:00:02 0:00:02 --:--:-- 49 { "Actions": [ "history-clear" ], "Information": { "SOC Temp": { "thresholds": { "UCR": "100.00" }, "units": "", "value": "40.00" } }, "Resources": [] } ``` Reviewed By: amithash fbshipit-source-id: 62747157af

Summary: 1. update vr version format 2. add json format support Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2706 Test Plan: t rebase --interactive 1. Build passed on northdome 2. Check vr version by fw-util - Normal format ``` root@bmc-oob:~# fw-util slot1 --version vr PVDDCR_CPU VR Version: E000CA46, Remaining Writes: 23 PVDDCR_SOC VR Version: 2911482B, Remaining Writes: 26 PVDDIO_ABCD VR Version: DC637D5A, Remaining Writes: 26 PVDDIO_EFGH VR Version: DC637D5A, Remaining Writes: 26 ``` - JSON format ``` root@bmc-oob:~# fw-util slot1 --version-json vr [ { "COMPONENT": "vr", "FRU": "slot1", "VERSION": { "PVDDCR_CPU": { "rmng_w": "23", "version": "e000ca46" }, "PVDDCR_SOC": { "rmng_w": "26", "version": "2911482b" }, "PVDDIO_ABCD": { "rmng_w": "26", "version": "dc637d5a" }, "PVDDIO_EFGH": { "rmng_w": "26", "version": "dc637d5a" } } } ] ``` Reviewed By: zhdaniel12 fbshipit-source-id: 3334cc29b0

…2712) Summary: fruid_paser could return error in some cases, and furid contents might not valid. Add return value check before doing fruid_trim Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2712 Test Plan: 1. Build passed on fby3 2. Tested on fby3-dp - Before, fruid-util crashed due to fru not avaliable (parsing failed) ``` root@bmc-oob:~# fruid-util slot1 1U-dev0 Segmentation fault ``` - After, fruid-util shows error message when fru not avaliable ``` root@bmc-oob:~# fruid-util slot1 1U-dev0 Failed print FRUID for Server board 1 1U-dev0 Check syslog for errors! (err 2h) ``` Reviewed By: zhdaniel12 fbshipit-source-id: 65a4e563b6

Summary: As titled. Test Plan: Compile northdome and observe no more compile warning. Reviewed By: doranand fbshipit-source-id: 836b6ea6ef

…2684) Summary: There are risks that reboot and fw-util running at very close time 1. There is 1 - 2 seconds gap between user launching fw-util and healthd set permission, reboot could be launched in this period 2. reboot takes 5 - 10 seconds to reset BMC, so there is a chance to start fw-util and cause the update incomplete Add following two check mechanisms to minimize the risks 1. wait_shutdown_non_executable() Wait until the permission of commands changed, to prevent new reboot command launched The default timeout is 2 seconds, if the permission not changed after 2 seconds, fw-util will write a warning message to syslog, then continue the process 2. is_reboot_ongoing() Check the reboot_ongoing kv file, if reboot_ongoing set to 1, then abort the fw-util Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2684 Test Plan: Build and test on northdome 1. launching reboot & fw-util at same time, fw-util should notice reboot is ongoing and abort ``` root@bmc-oob:~# cat ./test.sh #!/bin/bash fw-util slot1 --update vr test_file & reboot root@bmc-oob:~# ./test.sh Broadcast message from root@bmc-oob. (ttyS0) (Fri Mar 9 04:36:26 2018): The system is going down for reboot NOW! INIT: Switching to runlevel: 6 INIT: Sending processes configured via /etc/inittab the TERM signal root@bmc-oob:~# Stopping OpenBSD Secure Shell server: sshdstopped /usr/sbin/sshd (pid 501) . Stopping ntpd: done Aborted action due to reboot ongoing --> fw-util aborted stopping rsyslogd ... done Stopping random number generator daemon. Deconfiguring network interfaces... done. Sending all processes the TERM signal... logout Sending all processes the KILL signal... Unmounting remote filesystems... Deactivating swap... Unmounting local filesystems... [ 120.949435] UBIFS (ubi0:0): un-mount UBI device 0 [ 120.959014] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" stops Rebooting... [ 121.175152] reboot: Restarting system ``` 2. force stop healthd & run fw-util, syslog should record a warning message ``` root@bmc-oob:~# sv stop healthd ok: down: healthd: 0s, normally up root@bmc-oob:~# fw-util slot1 --update vr test_file > /dev/null root@bmc-oob:~# cat /var/log/messages | grep fw-util 2018 Mar 9 20:44:28 bmc-oob. user.warning northdome-320eacb9aca-dirty: fw-util: fw-util: shutdown command can still be executed after 2 seconds ``` Reviewed By: williamspatrick fbshipit-source-id: 7783ab011a

Summary: As title, prever v2 since it is fully backwards compatible and is fully validated in newer NPI platforms for about a year now. Test Plan: 1. check messages (Note FBTP does not support PLDM, so that is expected to fail) ``` root@dhcp-100-96-192-234:~# cat /var/log/messages | grep ncsid 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.info fbttn-2355e83817-dirty: ncsid: send_registration_msg: registering PID 1484 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.info fbttn-2355e83817-dirty: ncsid: ncsid-v2 ncsi_aen_handler thread started 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.info fbttn-2355e83817-dirty: ncsid: NIC Firmware Version: Broadcom 20.6.4.9 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.crit fbttn-2355e83817-dirty: ncsid: FRU: 5 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.err fbttn-2355e83817-dirty: ncsid: send_cmd(0x51): Command failed, resp = 0x1 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.err fbttn-2355e83817-dirty: ncsid: do_pldm_discovery: failed PLDM Discovery 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.info fbttn-2355e83817-dirty: ncsid: enable aens: mask=0x7 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.info fbttn-2355e83817-dirty: ncsid: rx: ncsi_rx_handler thread started 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.info fbttn-2355e83817-dirty: ncsid: ncsi_tx_handler thread started 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.warning fbttn-2355e83817-dirty: ncsid: NIC link up:Rsp:0x0000 Rsn:0x0000 Link:0x130075 (LF:0x1 SP:0xa SD:0x1) Other:0x1 (Driver:0x1) OEM:0x0 2021 Oct 20 15:32:12 dhcp-100-96-192-234.dhcp.thefacebook.com user.warning fbttn-2355e83817-dirty: ncsid: updated /tmp/cache_store/nic_fw_ver 2021 Oct 20 15:34:57 dhcp-100-96-192-234.dhcp.thefacebook.com authpriv.info fbttn-2355e83817-dirty: -bash[5238]: HISTORY: PID=5238 UID=0 cat /var/log/messages | grep ncsid ``` 2. check ncsi-util works ``` root@dhcp-100-96-192-234:~# ncsi-util 0x16 NC-SI Command Response: cmd: GET_CAPABILITIES(0x16) Response: COMMAND_COMPLETED(0x0000) Reason: NO_ERROR(0x0000) <snip> ``` 3. check log-util (FBTP does not support PLDM) ``` root@dhcp-100-96-192-234:~# log-util nic --print | tail -n 2 5 nic 2021-10-20 15:00:57 ncsid FRU: 5 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 5 nic 2021-10-20 15:32:12 ncsid FRU: 5 NIC AEN Supported: 0x7, AEN Enable Mask=0x7 ``` Reviewed By: zhdaniel12 fbshipit-source-id: f5b14b2e4b

Summary: This allows users to profile at the ms granularity of the current scope. Example: ``` void psu_req(req, resp) { // Send profile info as syslog info logs PROFILE_SCOPE(psu_req, openbmc::syslog::info); // long stuff taking many ms. } ``` Will automatically measure and print the log to syslog. User can of course provide std::cout, std::ofstream (file) or whatever they want as the optional ostream argument. Note, this is more useful for long running operations taking many milliseconds. Sub-millisecond operations for general performance optimization is better done with callgrind or other tools which have better tools and visualization capabilities Test Plan: Run unit-tests and ensure it passes Reviewed By: zhdaniel12 fbshipit-source-id: 6c585ce4a6

Summary: As title Test Plan: #doitlive Since there are no test hosts. Reviewed By: jerrt2003 fbshipit-source-id: 8645dbddf2

Summary: According to the ubifs documentation[1], it is by default an async file system and operates different from jffs2 in the event of sudden power drops. Since our code was not explicitly written to handle async file system operations (there is a sum total of 1 `fsync` call in the entire repository), it is safer to revert back to jffs2 file-system semantics. Change the mount option to be `-osync`. 1. http://www.linux-mtd.infradead.org/doc/ubifs.html#L_sync_semantics Test Plan: Enabled in QEMU and observed sync mount. ``` root@bmc-oob:/# mount | grep ubifs /dev/ubi0_0 on /mnt/data type ubifs (rw,sync,relatime,compr=zstd,assert=read-only,ubi=0,vol=0) ``` Reviewed By: amithash fbshipit-source-id: acc51d4685

Summary: It was reported on Northdome that certain invocations of `fruid-util` could result in an error such as: ``` malloc(): invalid size(unsorted) ``` Looking at the glibc source code this appears to be a buffer-overrun resulting in corruption of the buddy information in the heap allocation. I visually inspected the code and found two instances where strings were not properly NUL-terminated. I then hacked at the executable to get it to compile on an x86-64 system so I could run the tool against an EEPROM capture that was reported to cause the problem. I enabled GCC's ASAN and it identified the following problem: ``` $ gcc recipes-lib/fruid/files/fruid.c recipes-core/fruid/files/fruid-util.c \ -Irecipes-lib/fruid/files -Irecipes-lib/ipmi/files \ -Irecipes-lib/obmc-pal/files -ljansson -O1 -g -fsanitize=address $ ./a.out slot1 --modify --CCD1 9KF8120U10147 5.bin ================================================================= ==166643==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000003cf at pc 0x55c4c24403db bp 0x7ffc2cb11cf0 sp 0x7ffc2cb11ce0 READ of size 1 at 0x6020000003cf thread T0 #0 0x55c4c24403da in rtrim recipes-core/fruid/files/fruid-util.c:70 #1 0x55c4c2440e7d in fruid_trim recipes-core/fruid/files/fruid-util.c:87 #2 0x55c4c2440e7d in get_fruid_info recipes-core/fruid/files/fruid-util.c:511 #3 0x55c4c2444ad7 in do_action recipes-core/fruid/files/fruid-util.c:1148 #4 0x55c4c2444fe3 in main recipes-core/fruid/files/fruid-util.c:1273 #5 0x7fd8bd86b7fc in __libc_start_main (/lib64/libc.so.6+0x237fc) #6 0x55c4c2436459 in _start (/home/apwillia/local/sync/fbopenbmc/common/a.out+0x7459) 0x6020000003cf is located 1 bytes to the left of 2-byte region [0x6020000003d0,0x6020000003d2) allocated by thread T0 here: #0 0x7fd8bdacd777 in __interceptor_malloc (/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/libasan.so.6+0xb6777) #1 0x55c4c2436b4f in _fruid_area_field_read recipes-lib/fruid/files/fruid.c:192 AddressSanitizer: heap-buffer-overflow recipes-core/fruid/files/fruid-util.c:70 in rtrim ``` Through some additional debug I determined that the `chassis.custom2` field in this EEPROM was initialized with 0's. This causes `_fruid_area_field_read` to interpret the data as {TYPE_BINARY, len 0} for which it allocates a 1-byte NUL-terminated string. Later on the `rtrim` function does not correctly handle strings where `strlen` is 0 without causing corruption past the end of the string. Added a case to skip `rtrim` when the string is 0-bytes long. After this was resolved, ASAN identified another problem: ``` $ ./a.out slot1 --modify --CCD1 9KF8120U10147 5.bin ================================================================= ==170880==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x611000000110 at pc 0x7fa7c0d8481b bp 0x7fffe02a33c0 sp 0x7fffe02a2b68 WRITE of size 14 at 0x611000000110 thread T0 #0 0x7fa7c0d8481a in __interceptor_memcpy (/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/libasan.so.6+0x3a81a) #1 0x55dd7892aced in memcpy /usr/include/bits/string_fortified.h:29 #2 0x55dd7892aced in fruid_modify recipes-lib/fruid/files/fruid.c:1852 #3 0x55dd7892fb2c in do_action recipes-core/fruid/files/fruid-util.c:1148 #4 0x55dd78930062 in main recipes-core/fruid/files/fruid-util.c:1278 #5 0x7fa7c0b9e7fc in __libc_start_main (/lib64/libc.so.6+0x237fc) #6 0x55dd78921459 in _start (/home/apwillia/local/sync/fbopenbmc/common/a.out+0x7459) 0x611000000110 is located 0 bytes to the right of 208-byte region [0x611000000040,0x611000000110) allocated by thread T0 here: #0 0x7fa7c0e00777 in __interceptor_malloc (/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/libasan.so.6+0xb6777) #1 0x55dd78927e9d in fruid_modify recipes-lib/fruid/files/fruid.c:1618 ``` The source of this issue is found when adding a new optional field, such as `CCD1`, it can cause an entirely new section (ex. `chassis`) to be added with all of its optional fields becoming 1-byte type/len entries. In order to prevent a buffer overrun when creating the modified EEPROM image, we need to account for these additional optional fields. Over-estimate this size by adding an allocation for all optional fields in the entire image. Test Plan: Fix issues and confirm ASAN no longer reports problems. Reviewed By: amithash fbshipit-source-id: 6729ce2a43

Summary: reset debgu card then update to make sure i2c don't conflict. root@bmc-oob:~# fw-util ocpdbg --update mcubl /tmp/f08_lcd_4c129_bootloader_003.bin updated bootloader: 100 % Upgrade of ocpdbg : mcubl succeeded Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2699 Reviewed By: zhdaniel12 fbshipit-source-id: 835b87691a

Summary: Set fan pwm to 100 when BMC receiving IERR event. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1901 Test Plan: Build and test pass on fby35 system. 1. Trigger IERR assert/deassert and check fan speed root@bmc-oob:~# sv status fscd run: fscd: (pid 17817) 13s root@bmc-oob:~# ipmi-util 1 0x28 0x44 0x00 0x00 0x02 0xD7 0xF4 0x49 0x5A 0x40 0x00 0x04 0x07 0xEB 0x6F 0x00 0xFF 0xFF 2C 44 00 09 00 root@bmc-oob:~# log-util all --print | grep IERR 1 slot1 2021-10-20 20:13:30 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2021-10-20 20:13:22, Sensor: CATERR (0xEB), Event Data: (00FFFF) IERR/CATERR Assertion root@bmc-oob:~# fan-util --get Fan 0 Speed: 12032 RPM (100%) Fan 1 Speed: 10418 RPM (100%) Fan 2 Speed: 12122 RPM (100%) Fan 3 Speed: 10054 RPM (100%) Fan 4 Speed: 11622 RPM (100%) Fan 5 Speed: 10500 RPM (100%) Fan 6 Speed: 11622 RPM (100%) Fan 7 Speed: 10267 RPM (100%) Fan Mode: Manual(No fscd running) FSCD Driver: Not support in manual mode(No fscd running) Sensor Fail: Not support in manual mode(No fscd running) Fan Fail: Not support in manual mode(No fscd running) root@bmc-oob:~# ipmi-util 1 0x28 0x44 0x00 0x00 0x02 0xD7 0xF4 0x49 0x5A 0x40 0x00 0x04 0x07 0xEB 0xEF 0x00 0xFF 0xFF 2C 44 00 0B 00 root@bmc-oob:~# log-util all --print | grep IERR 1 slot1 2021-10-20 20:13:30 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2021-10-20 20:13:22, Sensor: CATERR (0xEB), Event Data: (00FFFF) IERR/CATERR Assertion 1 slot1 2021-10-20 20:14:02 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2021-10-20 20:13:57, Sensor: CATERR (0xEB), Event Data: (00FFFF) IERR/CATERR Deassertion root@bmc-oob:~# fan-util --get Fan 0 Speed: 8311 RPM (70%) Fan 1 Speed: 7284 RPM (70%) Fan 2 Speed: 8339 RPM (70%) Fan 3 Speed: 7274 RPM (70%) Fan 4 Speed: 8311 RPM (70%) Fan 5 Speed: 7219 RPM (70%) Fan 6 Speed: 8251 RPM (70%) Fan 7 Speed: 7308 RPM (70%) Fan Mode: Transitional FSCD Driver: linear_nic+pid_nic(nic:nic_sensor_temp) Sensor Fail: None Fan Fail: None Reviewed By: williamspatrick fbshipit-source-id: 29af595377

Summary: 1. There's a chance BMC reboot before rsyslog dumping log to file. Fix the issue by adding 1s delay before BMC reboot. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1904 Test Plan: Build and test pass on Grand Canyon. 1. Send cold reset command to BMC and check log is expected. [root@BartonSprings ~]# ipmitool bmc reset cold root@bmc-oob:~# log-util all --print | grep Cold 0 all 2021-10-24 22:11:14 ipmid BMC Cold Reset. Reviewed By: williamspatrick fbshipit-source-id: 755f70c35e

Summary: Since some MB does not support dump via PECI from BIC, crashdump should also support dump via ME for them. Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2696 Test Plan: For those MB does not support dump via PECI from BIC: bic-util slot2 0xe0 0x29 0x15 0xa0 0x00 0x30 0x05 0x05 0xa1 0x00 0x00 0x04 0x00 15 A0 00 FD FF FF FF FF They would change to dump via ME instead. Some of the data should return Completion Code 0x40 (Success) Reviewed By: zhdaniel12 fbshipit-source-id: 49270fc88b

Summary: -BMC can help protect the sled if OV(over voltage) or OT(over temperature) occurs to avoid causing sled to be broken. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1903 Test Plan: -build code(pass) -check the system can be turned off when OV or OT occurs(pass) 0 all 2021-10-20 19:22:53 sensord HSC vdelta(Vin-Vout) 0.31 >= 0.3, turn off P12V_STBY 0 all 2016-02-05 14:08:23 sensord MB_OUTLET_TEMP sensor is over the threshold, turn off P12V_STBY Reviewed By: GoldenBug fbshipit-source-id: b42b0e3ae1

Summary: This fixes a sync issue with netcastle not able to build fby35 after thrift sync. Test Plan: {gif:1198dd2z} Reviewed By: garnermic fbshipit-source-id: 34195ecaca

Summary: redirect output of healthd checking cmd to /dev/null, keep fw-util message clean Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2713 Test Plan: 1. Build passed on noethdome 2. Test BMC update, no more extra message - before, a extra message printed (output of healthd check) ``` root@bmc-oob:~# fw-util bmc --update bmc flash-northdome 17342 root 69048 S /usr/local/bin/healthd Flashing to device: /dev/mtd6 Erasing block: 444/444 (100%) Writing kb: 28406/28406 (100%) Verifying kb: 28406/28406 (100%) Upgrade of bmc : bmc succeeded ``` - after, no extra message ``` root@bmc-oob:~# fw-util bmc --update bmc flash-northdome Flashing to device: /dev/mtd6 Erasing block: 444/444 (100%) Writing kb: 28406/28406 (100%) Verifying kb: 28406/28406 (100%) Upgrade of bmc : bmc succeeded ``` Reviewed By: amithash fbshipit-source-id: 990d266f40

Summary: as title Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2715 Test Plan: 1. Build passed on northdome 2. Check /proc/mtd is correct ``` root@bmc-oob:~# cat /proc/mtd dev: size erasesize name mtd0: 00040000 00010000 "romx" mtd1: 00010000 00010000 "env" mtd2: 00010000 00010000 "meta" mtd3: 000a0000 00010000 "u-boot" mtd4: 01e60000 00010000 "fit" mtd5: 02000000 00010000 "data0" mtd6: 08000000 00010000 "flash1" mtd7: 07ff0000 00010000 "flash1rw" mtd8: 00040000 00010000 "rom" mtd9: 000a0000 00010000 "recovery" mtd10: 00010000 00010000 "metaro" mtd11: 01e60000 00010000 "fitro" mtd12: 02000000 00010000 "flash0" ``` Reviewed By: amithash fbshipit-source-id: 7f0c1f5413

Summary: Add SEL to record BMC/ROM update fail with invalid image Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2714 Test Plan: Build OK and test OK on fby35 1.Make a corrupted image from flash_fby35 then try to update it. 2.Try to update other platform's image. 3.These update actions should be block 4.Check SEL have record these failed actions ``` root@bmc-oob:/tmp# fw-util bmc --update bmc corrupted_flash_fby35 corrupted_flash_fby35 is not a valid BMC image for fby35 Upgrade of bmc : bmc failed root@bmc-oob:/tmp# fw-util bmc --update rom corrupted_flash_fby35 corrupted_flash_fby35 is not a valid BMC image for fby35 Upgrade of bmc : rom failed oot@bmc-oob:/tmp# fw-util bmc --update bmc flash-fby3 flash-fby3 is not a valid BMC image for fby35 Upgrade of bmc : bmc failed root@bmc-oob:/tmp# fw-util bmc --update rom flash-fby3 flash-fby3 is not a valid BMC image for fby35 Upgrade of bmc : rom failed root@bmc-oob:/tmp# log-util all --print 2018 Jan 01 16:28:22 log-util: User cleared all logs 0 all 2018-01-01 16:28:24 fw-util Updating bmc Fail. File: corrupted_flash_fby35 is not a valid image 0 all 2018-01-01 16:28:57 fw-util Updating rom Fail. File: corrupted_flash_fby35 is not a valid image 0 all 2018-01-01 00:04:10 fw-util Updating bmc Fail. File: flash-fby3 is not a valid image 0 all 2018-01-01 16:31:53 fw-util Updating rom Fail. File: flash-fby3 is not a valid image ``` Reviewed By: amithash fbshipit-source-id: b6d8d023ff

Summary: Get available LEBs on ubi device (/dev/ubi0) by ubinfo Resize ubi volume (/dev/ubi0_0) and use all LEBs if there are still LEBs available Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2716 Test Plan: 1. Build passed on northdome 2. Test UBIFS resize, from 4MB to 32MB - The boot log shows volume resize successfully ``` [ 18.260911] ubi0: default fastmap pool size: 25 [ 18.270103] ubi0: default fastmap WL pool size: 12 [ 18.279753] ubi0: attaching mtd5 [ 18.292250] ubi0: scanning is finished [ 18.317694] ubi0: attached mtd5 (name "data0", size 32 MiB) [ 18.328974] ubi0: PEB size: 65536 bytes (64 KiB), LEB size: 65408 bytes [ 18.342280] ubi0: min./max. I/O unit sizes: 1/256, sub-page size 1 [ 18.354706] ubi0: VID header offset: 64 (aligned 64), data offset: 128 [ 18.367821] ubi0: good PEBs: 512, bad PEBs: 0, corrupted PEBs: 0 [ 18.379900] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128 [ 18.394420] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 2056151151 [ 18.412751] ubi0: available PEBs: 448, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 0 [ 18.431308] ubi0: background thread "ubi_bgt0d" started, PID 108 UBI device number 0, total 512 LEBs (33488896 bytes, 31.9 MiB), available 448 LEBs (29302784 bytes, 27.9 MiB), LEB size 65408 bytes (63.8 KiB) ubifs_mount /dev/ubi0_0 to /mnt/data.. [ 18.629533] UBIFS (ubi0:0): Mounting in unauthenticated mode [ 18.653928] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 110 [ 19.406664] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "data0" [ 19.421406] UBIFS (ubi0:0): LEB size: 65408 bytes (63 KiB), min./max. I/O unit sizes: 8 bytes/256 bytes [ 19.440269] UBIFS (ubi0:0): FS size: 3139584 bytes (2 MiB, 48 LEBs), journal size 523265 bytes (0 MiB, 6 LEBs) [ 19.460339] UBIFS (ubi0:0): reserved for root: 148290 bytes (144 KiB) [ 19.473302] UBIFS (ubi0:0): media format: w5/r0 (latest is w5/r0), UUID 34B7B593-DDB1-4B88-86B9-6C6F9BEBAC64, small LPT model Check ubifs filesystem health on /dev/ubi0_0.. ubifs health check passed: no error found. [ 30.620447] UBIFS (ubi0:0): un-mount UBI device 0 [ 30.630041] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" stops ubifs_mount /dev/ubi0_0 to /mnt/data.. [ 33.776174] UBIFS (ubi0:0): Mounting in unauthenticated mode [ 33.803901] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 128 [ 34.379507] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "data0" [ 34.394259] UBIFS (ubi0:0): LEB size: 65408 bytes (63 KiB), min./max. I/O unit sizes: 8 bytes/256 bytes [ 34.413117] UBIFS (ubi0:0): FS size: 32442368 bytes (30 MiB, 496 LEBs), journal size 4316928 bytes (4 MiB, 66 LEBs) [ 34.434043] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB) [ 34.445781] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID 8ED63ADA-3D79-422C-A485-AD00C1932B68, small LPT model ubifs volume resize done, vol: /dev/ubi0_0, origin LEBs: 58, new LEBs: 506 ``` - ubi device (/dev/ubi0) LEBs are all used (available: 0) ``` root@bmc-oob:~# ubinfo /dev/ubi0 ubi0 Volumes count: 1 Logical eraseblock size: 65408 bytes, 63.8 KiB Total amount of logical eraseblocks: 512 (33488896 bytes, 31.9 MiB) Amount of available logical eraseblocks: 0 (0 bytes) Maximum count of volumes 128 Count of bad physical eraseblocks: 0 Count of reserved physical eraseblocks: 0 Current maximum erase counter value: 2 Minimum input/output unit size: 1 byte Character device major/minor: 246:0 Present volumes: 0 ``` - ubi volume (/dev/ubi0_0) LEBs count increased from 56 to 506 ``` root@bmc-oob:~# ubinfo /dev/ubi0_0 Volume ID: 0 (on ubi0) Type: dynamic Alignment: 1 Size: 506 LEBs (33096448 bytes, 31.5 MiB) State: OK Name: data0 Character device major/minor: 246:1 ``` - /mnt/data size increased (27.4M) ``` root@bmc-oob:~# df -h Filesystem Size Used Available Use% Mounted on devtmpfs 189.7M 1.5M 188.2M 1% /dev tmpfs 209.6M 92.0K 209.6M 0% /run tmpfs 209.6M 1.1M 208.5M 1% /var/volatile /dev/ubi0_0 27.4M 232.0K 27.2M 1% /mnt/data ``` Reviewed By: tao-ren fbshipit-source-id: ba057d7cc3

Summary: as title, use lower case for consistency. Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2719 Test Plan: Build pass on fby35 Reviewed By: williamspatrick fbshipit-source-id: 24316a0a22

Summary: this func will check if given FRU is available or not Test Plan: check sandcastle RUN on D31911231 Reviewed By: binhuang00 fbshipit-source-id: 1f967a3e60

Summary: we need to add more fan to fan-util check list due to new fby3 in basset pool Test Plan: Sandcastle RUN: https://www.internalfb.com/intern/sandcastle/job/4503600137714370/ Reviewed By: binhuang00 fbshipit-source-id: 2c5d76a258

Summary: update restendpoint.json since we got a new batch of fby3 in basset pool Test Plan: Sandcastle RUN: https://www.internalfb.com/intern/sandcastle/job/4503600137418339/ Reviewed By: binhuang00 fbshipit-source-id: 19cc771365

Summary: For tiogapass T6 we don't have riser_slot. We'll need to check if riser_slot exists before run fru-util test. This will help to reduce false-alarm of the CIT. Test Plan: Sandcastle RUN: https://www.internalfb.com/intern/sandcastle/job/36028797527188987/ Reviewed By: binhuang00 fbshipit-source-id: 4faf54e734

Summary: Some of our test fby3 in basset pool doesn't equip with all FRU (e.g. missing slot2/3/4), thus for certain CIT test we'll need to first check FRU availability before running the test. Test Plan: Sandcastle RUN: https://www.internalfb.com/intern/sandcastle/job/36028797527472319/ Reviewed By: binhuang00 fbshipit-source-id: 45d83b8c9f

Summary: FansTest failed recently because wdtcli was not able to open watchdog, as fscd still owns watchdog that time. Should run wtdcli after fscd is stopped Test Plan: test is on wedge400 and wedge400c: ``` root@bmc-oob:/usr/local/bin/tests2# python3 cit_runner.py --platform wedge400 --run-test tests.wedge400.test_fans.FansTest test_all_fans_read (tests.wedge400.test_fans.FansTest) Test if all fan dump is returning sane data ... ok test_fan1_pwm_set (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok test_fan1_read (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok test_fan2_pwm_set (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok test_fan2_read (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok test_fan3_pwm_set (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok test_fan3_read (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok test_fan4_pwm_set (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok test_fan4_read (tests.wedge400.test_fans.FansTest) For each fan read and test speed ... ok ---------------------------------------------------------------------- Ran 9 tests in 215.997s OK ``` Reviewed By: joancaneus fbshipit-source-id: dff72d5923

Summary: 1. BMC report chassis type error if there's daemon access chassis type via the kv node before the node creation. - The sku info is got from setup-platform.sh at rc.5 order 92. 2. Fix the issue by accessing GPIO directly while the cache is not ready. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1910 Test Plan: Build and test pass on Grand Canyon. 1. Hard code delay the cache init time and check there's no error message in BMC syslog. root@bmc-oob:~# cat /var/log/messages | grep fbgc_common_get_chassis_type root@bmc-oob:~# 2. Make sure IPMID runnging before setup-platform.sh in rc.5 and check BMC could get fru data successfully. root@bmc-oob:~# fruid-util e1s_iocm FRU Information : IOC Module --------------- : ------------------ Board Mfg Date : Mon Jun 14 11:56:00 2021 Board Mfg : Wiwynn Board Product : IOC Module Board Serial : WR1612200AZSA Board Part Number : B81.04910.0116 Board FRU ID : 1.0 Board Custom Data 1 : 19-001899 Board Custom Data 2 : PCB Supplier - GCE Product Manufacturer : Wiwynn Product Name : Grand Canyon DVT Product Part Number : N/A Product Version : DVT Product Serial : N/A Product Asset Tag : N/A Product FRU ID : 1.0 Product Custom Data 1 : N/A Reviewed By: zhdaniel12 fbshipit-source-id: 57d03f5b37

Summary: D31822993 PR from ODM broke Redfish Sensors unit test. Fixing it Test Plan: ./tests2/ptest-runner rest-api Reviewed By: lsiudut, doranand fbshipit-source-id: 6bd705586c

Summary: Implement the Redfish powercycle endpoint for Managers and Systems. * For both single sled and multislot servers * For compute we use power-util and for fboss, we use wedge_power.sh * Add unit tests Test Plan: /tests2/ptest-runner rest-api Coverage is: ``` /usr/local/fbpackages/rest-api/redfish_powercycle.py 59 10 83% 70, 81, 87, 95, 105, 124, 129, 131, 139, 144 ``` OOB reset curl: P465897926 Compute system reset curl:P465896744 Reviewed By: doranand fbshipit-source-id: 4a2e7da98c

Summary: As the title. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1244 Test Plan: ``` root@bmc:~# cat /etc/issue OpenBMC Release cloudripper-a411d942140-dirty root@bmc:~# threshold-util Usage: threshold-util [fru] <--set> <snr_num> [thresh_type] <threshold_value> threshold-util [fru] <--clear> [fru] : all, scm, smb, psu1, psu2, fan1, fan2, fan3, fan4 <snr_num> : 0xXX [thresh_type] : UCR, UNC, UNR, LCR, LNC, LNR root@bmc:~# ``` Reviewed By: binhuang00 fbshipit-source-id: 483de26af2

Summary: Remove some kv_keys which don't exist in pal.c. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1249 Test Plan: 1. run cit test test_kv on cloudripper unit. test log: root@bmc-oob:/usr/local/bin/tests2# python3.7 cit_runner.py --platform cloudripper --run-test tests.cloudripper.test_kv.KvTest.test_kv_get_key test_kv_get_key (tests.cloudripper.test_kv.KvTest) ... ok ---------------------------------------------------------------------- Ran 1 test in 0.291s OK root@bmc-oob:/usr/local/bin/tests2# python3.7 cit_runner.py --platform cloudripper --run-test tests.cloudripper.test_kv.KvTest.test_kv_path_exists test_kv_path_exists (tests.cloudripper.test_kv.KvTest) ... ok ---------------------------------------------------------------------- Ran 1 test in 0.006s OK root@bmc-oob:/usr/local/bin/tests2# Reviewed By: binhuang00 fbshipit-source-id: bae6cdf9c7

Summary: Background: from the MFG MP build feedback, there are some Fuji Units always upgrade CPLD fail. From the Lattice FAE feedback it maybe the difference between silicon, he suggust us use the CPU freq to set the g_usCpu_Frequency parameter. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1254 Test Plan: ``` 1. With this solution, the MFG 350 Pcs MP build verificaton all pass. 2. This solution will increase the upgrade time about 5s. <1>. Fuji unit CPLD upgrade log: root@bmc:/mnt/data1/BMC_Diag/firmware/CPLD# cat /etc/issue OpenBMC Release fuji-7a2ba3eb77f-dirty root@bmc:/mnt/data1/BMC_Diag/firmware/CPLD# cpld_update.sh -s SMB -f MiniPack2_SMB_CPLD_TOP_v1p3p1.vme sw Program SMB 1 times Lattice Semiconductor Corp. ispVME(tm) V12.2 Copyright 1998-2011. For daisy chain programming of all in-system programmable devices CPU Freq set as 1000 MHZ calibration .... Processing virtual machine file (MiniPack2_SMB_CPLD_TOP_v1p3p1.vme)...... Diamond Deployment Tool 3.10 CREATION DATE: Sat Dec 12 18:52:35 2020 Warning! Don't power off...... [100%] +=======+ | PASS! | +=======+ Upgrade successful. root@bmc:/mnt/data1/BMC_Diag/firmware/CPLD# cpld_update.sh -s SCM -f MiniPack2_SCM_CPLD_TOP_v0p6p0.vme sw Program SCM 1 times Lattice Semiconductor Corp. ispVME(tm) V12.2 Copyright 1998-2011. For daisy chain programming of all in-system programmable devices CPU Freq set as 1000 MHZ calibration .... Processing virtual machine file (MiniPack2_SCM_CPLD_TOP_v0p6p0.vme)...... Diamond Deployment Tool 3.10 CREATION DATE: Thu Aug 06 14:12:56 2020 Warning! Don't power off...... [100%] +=======+ | PASS! | +=======+ Upgrade successful. root@bmc:/mnt/data1/BMC_Diag/firmware/CPLD# cpld_update.sh -s FCM-T -f MiniPack2_FAN_CPLD_TOP_v0p3p1.vme sw Program FCM-T 1 times Lattice Semiconductor Corp. ispVME(tm) V12.2 Copyright 1998-2011. For daisy chain programming of all in-system programmable devices CPU Freq set as 1000 MHZ calibration .... Processing virtual machine file (MiniPack2_FAN_CPLD_TOP_v0p3p1.vme)...... Diamond Deployment Tool 3.10 CREATION DATE: Sat Nov 07 16:24:48 2020 Warning! Don't power off...... [100%] +=======+ | PASS! | +=======+ Upgrade successful. root@bmc:/mnt/data1/BMC_Diag/firmware/CPLD# ``` Reviewed By: binhuang00 fbshipit-source-id: 05cb60c25d

Summary: Becasue Fuji will invove the Detla & Liteon 48V DC PSU and per 48V DC PSU will have two psu fans, so need detect the PSU48 by PSU P/N. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1258 Test Plan: ``` <1>. DELTA 48V DC PSU root@bmc:~# cat /etc/issue OpenBMC Release fuji-ee6a7bd9aa4-dirty root@bmc:~# source /usr/local/bin/openbmc-utils.sh root@bmc:~# wedge_power_supply_type PSU48 <2>. DELTA AC PSU root@bmc:~# cat /etc/issue OpenBMC Release fuji-ee6a7bd9aa4-dirty root@bmc:~# source /usr/local/bin/openbmc-utils.sh root@bmc:~# wedge_power_supply_type PSU <3>. LITEON 48V DC PSU root@bmc:~# cat /etc/issue OpenBMC Release fuji-ee6a7bd9aa4-dirty root@bmc:~# source /usr/local/bin/openbmc-utils.sh root@bmc:~# wedge_power_supply_type PSU48 ``` Reviewed By: binhuang00 fbshipit-source-id: 23b8d6ef63

Summary: As the title. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1260 Test Plan: ``` <1>. Check Liteon 48V DC firmware version root@bmc:/mnt/data1/REV_10_10# cat /etc/issue OpenBMC Release fuji-80b92d8b341-dirty root@bmc:/mnt/data1/REV_10_10# psu-util psu2 --get_psu_info PSU Information : PSU2 (Bus:49 Addr:0x5a) --------------- : ----------------------- MFR_ID (0x99) : Liteon MFR_MODEL (0x9A) : DD-2152-2L MFR_REVISION (0x9B) : X1 MFR_DATE (0x9D) : 20210716 MFR_SERIAL (0x9E) : 6D00201X1929101 PRI_FW_VER (0xDD) : 0.0 SEC_FW_VER (0xD7) : 0.0 STATUS_WORD (0x79) : 0x0000 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0x00 STATUS_INPUT (0x7C) : 0x00 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x0000 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : NA OPTN_TIME_PRESENT (0xD9) : NA <2>. Update PSU firmware root@bmc:/mnt/data1/REV_10_10# psu-util psu2 --update HEX_PRI_8009_CRC166273_BIN.bin Vendor: Liteon Model: DD-2152-2L HW Compatibility: 1 MCU: primary Ver: 1.0 -- Bootloader Mode -- -- Transmit Primary Firmware -- -- (2688/2688) (100%/100%) -- -- Transmit CRC -- -- Reset PSU -- -- Upgrade Done -- root@bmc:/mnt/data1/REV_10_10# psu-util psu2 --update HEX_SEC_0D60_CRC88F3_BIN.bin Vendor: Liteon Model: DD-2152-2L HW Compatibility: 1 MCU: secondary Ver: 1.0 -- Bootloader Mode -- -- Transmit Secondary Firmware -- -- (5504/5504) (100%/100%) -- -- Transmit CRC -- -- Reset PSU -- -- Upgrade Done -- <3>. Check PSU firmware version root@bmc:/mnt/data1/REV_10_10# psu-util psu2 --get_psu_info PSU Information : PSU2 (Bus:49 Addr:0x5a) --------------- : ----------------------- MFR_ID (0x99) : Liteon MFR_MODEL (0x9A) : DD-2152-2L MFR_REVISION (0x9B) : X1 MFR_DATE (0x9D) : 20210716 MFR_SERIAL (0x9E) : 6D00201X1929101 PRI_FW_VER (0xDD) : 1.0 SEC_FW_VER (0xD7) : 1.0 STATUS_WORD (0x79) : 0x0000 STATUS_VOUT (0x7A) : 0x00 STATUS_IOUT (0x7B) : 0x00 STATUS_INPUT (0x7C) : 0x00 STATUS_TEMP (0x7D) : 0x00 STATUS_CML (0x7E) : 0x00 STATUS_FAN (0x81) : 0x00 STATUS_STBY_WORD (0xD3) : 0x0000 STATUS_VSTBY (0xD4) : 0x00 STATUS_ISTBY (0xD5) : 0x00 OPTN_TIME_TOTAL (0xD8) : NA OPTN_TIME_PRESENT (0xD9) : NA ``` Reviewed By: binhuang00 fbshipit-source-id: 2c89082f07

Summary: when finish power-util test, CIT suppose to power-on (reset) FRU when test is finished. But in recent D31911233 I enable a check to check FRU's availability before doing so. However in power-util test when we power off the FRU, the previous FRU check will always fail thus causing the power-on logic in `tearDown` step never work. Need to remove that check to force power-on whenever power-util test finished Test Plan: Sandcastle RUN: https://www.internalfb.com/intern/sandcastle/job/513168741/ Reviewed By: joancaneus fbshipit-source-id: ea582a8f39

…cebook#234) Summary: This is an improvement to psu-util on Elbert. This adds a step to the library that checks for bootloader mode before the power check and will skip the power check if the PSU is still in bootloader mode, allowing reprogramming of PSUs that are in bootloader mode. ## Testing Inject a CRC error using a corrupted firmware image: ``` root@bmc-oob:/mnt/data1# psu-util psu1 --update ECD15020056_Pri2.5_Sec2.8.bin.bad --vendor delta Vendor: Delta Model: ECD15020056 HW Compatibility: 2 Primary Ver: 2.5 Secondary Ver: 2.8 -- Write Protect Disabled -- -- Bootloader Mode -- -- Transmit Header -- -- (4/4) (100%/100%) -- -- Transmit Primary Firmware -- -- (1252/1252) (100%/100%) -- CRC check failed 8a 1e != b3 68: Success PSU1 update fail! ``` Reprogram to recover from bootloader mode: ``` root@bmc-oob:/mnt/data1# psu-util psu1 --update ECD15020056_Pri2.5_Sec2.8.bin --vendor delta Vendor: Delta Model: ECD15020056 HW Compatibility: 2 Primary Ver: 2.5 Secondary Ver: 2.8 -- Write Protect Disabled -- -- Bootloader Mode -- -- Transmit Header -- -- (4/4) (100%/100%) -- -- Transmit Primary Firmware -- -- (1252/1252) (100%/100%) -- -- Transmit Secondary Firmware -- -- (4332/4332) (100%/100%) -- -- Reset PSU -- -- Write Protect Enabled -- -- Upgrade Done -- PSU1 update success! ``` Case where PSU isn't inserted: ``` root@bmc-oob:/mnt/data1# psu-util psu3 --update ECD15020056_Pri2.5_Sec2.8.bin PSU3 is not present! ``` Case where PSU isn't connected to power: ``` root@bmc-oob:/mnt/data1# psu-util psu4 --update ECD15020056_Pri2.5_Sec2.8.bin Vendor: Delta Model: ECD15020056 HW Compatibility: 2 Primary Ver: 2.5 Secondary Ver: 2.8 PSU4 power is not OK! Please verify that the PSU is not connected to AC power. The PSU must be connected to AC power in order to perform this firmware update. PSU4 update fail! ``` Stressed PSU upgrade 100 times, 100/100 passes. Pull Request resolved: https://github.com/facebookexternal/openbmc.arista/pull/234 Reviewed By: binhuang00 fbshipit-source-id: 5c429bb23e

Summary: ## Issue lf-dunfell uses a different version of i2c-tools than zeus (4.1 vs 3.1). One difference is the way that block reads are printed: 3.1: ``` root@bmc-oob:~# i2cget -f -y 3 0x4E 0xf1 i Byte CT = 6 0x000000000001 ``` 4.1: ``` root@bmc-oob:~# i2cget -f -y 3 0x4E 0xf1 i 0x06 0x00 0x00 0x00 0x00 0x00 0x01 0xab 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ``` This formatting difference has broken the logic for disabling DPM write protect and reading DPM logs, as well as caused the I2C CIT test to fail. dpm_dump.sh is broken: ``` root@bmc-oob:/mnt/data# dpm_dump.sh Reading DPM logs... /usr/local/bin/board-utils.sh: line 237: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x01 0xab 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0 xff 0xff 0xff 0xff 0xff: invalid hex number /usr/local/bin/board-utils.sh: line 244: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0xac 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0 xff 0xff 0xff 0xff 0xff: invalid hex number Failed to lock UCD90160B 3-000x4e Attempt 1/3 failed with 1, retrying... /usr/local/bin/board-utils.sh: line 237: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0xac 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0 xff 0xff 0xff 0xff 0xff: invalid hex number /usr/local/bin/board-utils.sh: line 244: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x01 0xab 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0 xff 0xff 0xff 0xff 0xff: invalid hex number Failed to lock UCD90160B 3-000x4e Attempt 2/3 failed with 1, retrying... /usr/local/bin/board-utils.sh: line 237: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x01 0xab 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0 xff 0xff 0xff 0xff 0xff: invalid hex number /usr/local/bin/board-utils.sh: line 244: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0xac 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0 xff 0xff 0xff 0xff 0xff: invalid hex number Failed to lock UCD90160B 3-000x4e Retry 3/3 failed with 1, no more retries left Clearing SWITCHCARD DPM logs... Dumping and clearing PIM DPM logs... Script cannot run while driver present ``` disable_switchcard_power_security is broken ``` root@bmc-oob:/mnt/data# disable_switchcard_power_security -bash: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0xac 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff: invalid hex number -bash: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x01 0xab 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff: invalid hex number Failed to lock UCD90160B 3-000x4e Attempt 1/3 failed with 1, retrying... -bash: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x01 0xab 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff: invalid hex number -bash: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0xac 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff: invalid hex number Failed to lock UCD90160B 3-000x4e Attempt 2/3 failed with 1, retrying... -bash: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0xac 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff: invalid h ex number -bash: printf: 0x06 0x00 0x00 0x00 0x00 0x00 0x01 0xab 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff: invalid hex number Failed to lock UCD90160B 3-000x4e Retry 3/3 failed with 1, no more retries left -bash: disable_isp_wp: command not found Attempt 1/3 failed with 127, retrying... -bash: disable_isp_wp: command not found Attempt 2/3 failed with 127, retrying... -bash: disable_isp_wp: command not found Retry 3/3 failed with 127, no more retries left -bash: disable_isp_wp: command not found Attempt 1/3 failed with 127, retrying... -bash: disable_isp_wp: command not found Attempt 2/3 failed with 127, retrying... -bash: disable_isp_wp: command not found Retry 3/3 failed with 127, no more retries left ``` pim_dpm_dump.sh --clear is broken: ``` root@bmc-oob:~# pim_dpm_dump.sh 2 {'Date':'2021-10-23 03:09:41','Source':'PIM2','Log':'0x00','detail_0':{'m':'0x0a','e':'0x16'},'detail_1':{'m':'0x0a','e':'0x16'},'detail_2':{'m':'0x0a','e':'0x16'},'detail_3':{'m':'0x0a','e':'0x16'},'detail_4':{'m':'0x0a','e':'0x16'},'detail_5':{'m':'0x0a','e':'0x16'},'detail_6':{'m':'0x0a','e':'0x16'},'detail_7':{'m':'0x0a','e':'0x16'},'detail_8':{'m':'0x0a','e':'0x16'},'detail_9':{'m':'0x0a','e':'0x16'},'detail_10':{'m':'0x0a','e':'0x16'},'detail_11':{'m':'0x0a','e':'0x16'}} root@bmc-oob:~# pim_dpm_dump.sh 2 --clear {'Date':'2021-10-23 03:09:52','Source':'PIM2','Log':'0x00','detail_0':{'m':'0x0a','e':'0x16'},'detail_1':{'m':'0x0a','e':'0x16'},'detail_2':{'m':'0x0a','e':'0x16'},'detail_3':{'m':'0x0a','e':'0x16'},'detail_4':{'m':'0x0a','e':'0x16'},'detail_5':{'m':'0x0a','e':'0x16'},'detail_6':{'m':'0x0a','e':'0x16'},'detail_7':{'m':'0x0a','e':'0x16'},'detail_8':{'m':'0x0a','e':'0x16'},'detail_9':{'m':'0x0a','e':'0x16'},'detail_10':{'m':'0x0a','e':'0x16'},'detail_11':{'m':'0x0a','e':'0x16'}} ``` ## Fix The fix is to use the SMBus block read supported in the new i2cget, which has better formatting: ``` root@bmc-oob:/mnt/data# i2cget -f -y 3 0x4E 0xf1 s 0x00 0x00 0x00 0x00 0x00 0x01 root@bmc-oob:/mnt/data# printf "%d" $(i2cget -f -y 3 0x4E 0xf1 s | awk '{print $(NF)}') 1 ``` I also updated the CIT test to account for the difference. Additionally, I found an issue with a typo in disable_switchcard_power_security and fixed that. ## Testing dpm_dump.sh works: ``` root@bmc-oob:~# dpm_dump.sh Reading DPM logs... UCD bus 3 device 0x4e already unlocked! Clearing SWITCHCARD DPM logs... Dumping and clearing PIM DPM logs... ``` pim_dpm_dump.sh works: ``` root@bmc-oob:~# pim_dpm_dump.sh 2 --clear {'Date':'2021-10-23 03:23:24','Source':'PIM2','Log':'0x00'} ``` disable_switchcard_power_security works: ``` root@bmc-oob:/mnt/data1# enable_switchcard_power_security root@bmc-oob:/mnt/data1# disable_switchcard_power_security ``` CIT test passes: ``` root@bmc-oob:/usr/local/bin/tests2# python cit_runner.py -p elbert -r tests.elbert.test_i2c test_i2c_security (tests.elbert.test_i2c.ElbertI2cTest) ... ok test_i2c_tree (tests.elbert.test_i2c.ElbertI2cTest) ... ok ---------------------------------------------------------------------- Ran 2 tests in 9.805s OK ``` Pull Request resolved: https://github.com/facebookexternal/openbmc.arista/pull/232 Reviewed By: binhuang00 fbshipit-source-id: 82d49dc961

Summary: Adds logic to dpm_ver.sh for reading the ISL68224 revision on PIM8DDM. Also updates the REST API to include the PIM ISL revisions. Adds a helper function to board-util.sh for retrieving the PIM type value cached by front-paneld. ## Testing Tested on Elbert with PIM8DDM and PIM16Q. ``` root@bmc-oob:~# pim_types.sh PIM 2: PIM16Q PIM 3: PIM16Q PIM 4: PIM16Q PIM 5: PIM16Q PIM 6: PIM16Q PIM 7: PIM8DDM PIM 8: PIM8DDM PIM 9: PIM8DDM ``` dpm_ver.sh output: ``` root@bmc-oob:~# dpm_ver.sh !!! !!! WARNING: Displaying Digital Power Manager (DPM) version may disrupt sensor reading !!! !!! SCM.: SFT013030303 SMB.: SFT013180108 PIM2.: SFT012990104 PIM3.: SFT012990104 PIM4.: SFT012990104 PIM5.: SFT012990104 PIM6.: SFT012990104 PIM7.: SFT013860105 PIM8.: SFT013860105 PIM9.: SFT013860105 SMB ISL68226: SFT013200106 SMB RAA228228: SFT013190105 PIM2 has no ISL... skipping. PIM3 has no ISL... skipping. PIM4 has no ISL... skipping. PIM5 has no ISL... skipping. PIM6 has no ISL... skipping. PIM7 ISL68224: SFT014820103 PIM8 ISL68224: SFT014820103 PIM9 ISL68224: SFT014820103 !!! Done. ``` REST API output: ``` root@bmc-oob:~# curl -g http://localhost:8080/api/sys/firmware_info/all | python /usr/lib/python3.8/json/tool.py % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 732 100 732 0 0 694 0 0:00:01 0:00:01 --:--:-- 695 { "SCM": "2.14", "FAN": "1.11", "SMB": "3.8", "SMB_CPLD": "5.1", "PIM 2": "7.4", "PIM 3": "7.4", "PIM 4": "7.4", "PIM 5": "7.4", "PIM 6": "7.4", "PIM 7": "8.7", "PIM 8": "8.7", "PIM 9": "8.7", "SCM DPM": "SFT013030303", "SMB DPM": "SFT013180108", "PIM2 DPM": "SFT012990104", "PIM3 DPM": "SFT012990104", "PIM4 DPM": "SFT012990104", "PIM5 DPM": "SFT012990104", "PIM6 DPM": "SFT012990104", "PIM7 DPM": "SFT013860105", "PIM8 DPM": "SFT013860105", "PIM9 DPM": "SFT013860105", "SMB ISL68226": "SFT013200106", "SMB RAA228228": "SFT013190105", "PIM7 ISL68224": "SFT014820103", "PIM8 ISL68224": "SFT014820103", "PIM9 ISL68224": "SFT014820103" } ``` I also ran all CIT tests (which pass) and verified that shellcheck passes. Pull Request resolved: https://github.com/facebookexternal/openbmc.arista/pull/233 Reviewed By: binhuang00 fbshipit-source-id: 8b3f72060e

Summary: This is a followup diff to D32076574. when we try to power on a no exist FRU, power-util will exit with code 255 causing test exception. However in our devices in basset pool, we can't always guarantee to have full HW installed like we had in the production. So we'll have to first check HW availability before the test start, and only power-on devices which are marked as available. Test Plan: Sandcastle FBTP: https://www.internalfb.com/intern/sandcastle/job/4503600141224000 Sandcastle FBY3: https://www.internalfb.com/intern/sandcastle/job/18014399021045635 Reviewed By: binhuang00 fbshipit-source-id: c158724f98

Summary: Add a markdown doc for vboot-util in preperation for automatically generating BMC spec. Test Plan: up2date_documentation Reviewed By: zhdaniel12 fbshipit-source-id: 924573fca0

Summary: Adding support to test for benchmark testing for wedge100 cli measurement. Test Plan: do it live Reviewed By: jerrt2003 fbshipit-source-id: 2b2b4c53cc

Summary: Add a markdown doc for fw-util in preperation for automatically generating BMC spec. Test Plan: documentation_ Reviewed By: zhdaniel12 fbshipit-source-id: c05dd01f64

Summary: Logic seems flaky and there's no guarantee of getting a stable name from DNS if there are multiple entries. Test Plan: Run `hostname.sh` on both sysv and systemd test devices with and without `/mnt/data/hostname` Reviewed By: doranand fbshipit-source-id: c026a70cce

Summary: Benchmark cli test data for minipack Test Plan: coming up Reviewed By: binhuang00 fbshipit-source-id: 5b3bcf1308

Summary: ^See Title Test Plan: {gif:m5tk7spz} Reviewed By: zhdaniel12 fbshipit-source-id: 16862c8a34

Summary: Adjust HSC power/current reading to meet actual value. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1913 Test Plan: Build and test pass on fby35 system. 1. Get sensor reading of HSC root@bmc-oob:~# sensor-util bmc | grep -i hsc BMC_SENSOR_HSC_TEMP (0xF8) : 25.95 C | (ok) BMC_SENSOR_HSC_VIN (0xF7) : 12.10 Volts | (ok) BMC_SENSOR_HSC_PIN (0xF9) : 121.20 Watts | (ok) BMC_SENSOR_HSC_EIN (0xCB) : 126.28 Watts | (ok) BMC_SENSOR_HSC_IOUT (0xFA) : 10.04 Amps | (ok) BMC_SENSOR_HSC_PEAK_IOUT (0xC8) : 10.74 Amps | (ok) BMC_SENSOR_HSC_PEAK_PIN (0xC9) : 130.33 Watts | (ok) Reviewed By: GoldenBug fbshipit-source-id: 3745667f4b

Summary: As the title. Pull Request resolved: https://github.com/facebookexternal/openbmc.celestica/pull/1265 Test Plan: ``` Build for wedge400 platform success. ``` Reviewed By: tao-ren fbshipit-source-id: 6a5f283c98

Summary: as title Test Plan: testplan_testplan_eyes Reviewed By: doranand fbshipit-source-id: f8e44d1e8f

Summary: BMC can't update fan fru when changing fan at the runtime. To deal with this case, Expander will send SEL if FAN FRU update is completed. Support to handle the SEL, BMC compare the checksum and decide whether to update FAN FRU. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1911 Test Plan: 1. Build and test pass on Grand Canyon. 2. Check there are no unexpected error logs in BMC /var/log/messages and BMC SELs. 3. Use old Expander firmware. root@bmc-oob:~# fw-util scc --version Expander Version: 0x03010010 SCC IOC Version: 8.0031.02-0000 (1) Check all FRU dump successfully. root@bmc-oob:~# cat /var/log/messages | grep exp 2021 Oct 28 23:49:36 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: scc initial is done. 2021 Oct 28 23:49:37 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: dpb initial is done. 2021 Oct 28 23:49:37 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan0 initial is done. 2021 Oct 28 23:49:37 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan1 initial is done. 2021 Oct 28 23:49:37 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan2 initial is done. 2021 Oct 28 23:49:37 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan3 initial is done. root@bmc-oob:~# ls /tmp | grep fruid fruid_bmc.bin fruid_dpb.bin fruid_fan0.bin fruid_fan1.bin fruid_fan2.bin fruid_fan3.bin fruid_nic.bin fruid_scc.bin fruid_server.bin fruid_uic.bin 4. Use new Expander firmware. root@bmc-oob:~# fw-util scc --version Expander Version: 0x04010011 SCC IOC Version: 8.0031.02-0000 (1) Booting: Expander FAN FRU is ready root@bmc-oob:~# cat /var/log/messages | grep exp 2021 Oct 29 00:23:29 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: scc initial is done. 2021 Oct 29 00:23:30 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: dpb initial is done. 2021 Oct 29 00:23:31 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan0 initial is done. 2021 Oct 29 00:23:31 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan2 initial is done. 2021 Oct 29 00:23:31 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan1 initial is done. 2021 Oct 29 00:23:31 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan3 initial is done. root@bmc-oob:~# ls /tmp | grep fruid fruid_bmc.bin fruid_dpb.bin fruid_fan0.bin fruid_fan1.bin fruid_fan2.bin fruid_fan3.bin fruid_scc.bin fruid_server.bin fruid_uic.bin (2) Booting: Expander FAN FRU isn't ready *BMC will dump FAN FRU until get SEL sent by Expander. root@bmc-oob:~# cat /var/log/messages | grep exp 2021 Oct 29 00:30:42 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: scc initial is done. 2021 Oct 29 00:30:42 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: dpb initial is done. 2021 Oct 29 00:30:42 bmc-oob. user.warning grandcanyon-6e34e8a87e4-dirty: exp-cached: fruid_cache_init(): FAN FRUs status are not ready, initial is failed. 2021 Oct 29 00:30:54 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan0 initial is done. 2021 Oct 29 00:30:54 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan1 initial is done. 2021 Oct 29 00:30:54 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan3 initial is done. 2021 Oct 29 00:30:54 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan2 initial is done. (3) Change FAN runtime root@bmc-oob:~# fruid-util fan0 FRU Information : FAN0 --------------- : ------------------ Product Manufacturer : AVC Product Name : Grand Canyon FRU Fan Product Part Number : DFPD0956B2HY002 Product Version : 01.01.00 Product Serial : 00CQ Product Asset Tag : Product Custom Data 1 : 05-000627 Smart Fan Manufacturer ID : 40981 Smart Fan Version : 01.06.00 Smart Fan FW Version : 01.01.00 Smart Fan Mfg Date : Fri Jun 4 15:59:00 2021 Smart Fan Voltage (mV) : 12000 Smart Fan Current (mA) : 5300 Smart Fan Front RPM : 11200 Smart Fan Rear RPM : 10300 root@bmc-oob:~# fruid-util fan1 FRU Information : FAN1 --------------- : ------------------ Product Manufacturer : AVC Product Name : Grand Canyon FRU Fan Product Part Number : DFPD0956B2HY002 Product Version : 01.01.00 Product Serial : 00AY Product Asset Tag : Product Custom Data 1 : 05-000627 Smart Fan Manufacturer ID : 40981 Smart Fan Version : 01.06.00 Smart Fan FW Version : 01.01.00 Smart Fan Mfg Date : Fri Jun 4 16:41:00 2021 Smart Fan Voltage (mV) : 12000 Smart Fan Current (mA) : 5300 Smart Fan Front RPM : 11200 Smart Fan Rear RPM : 10300 *BMC will dump FAN FRU root@bmc-oob:~# cat /var/log/messages | grep exp ... 2021 Oct 29 02:01:19 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan1 initial is done. 2021 Oct 29 02:01:19 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan0 initial is done. root@bmc-oob:~# fruid-util fan0 FRU Information : FAN0 --------------- : ------------------ Product Manufacturer : AVC Product Name : Grand Canyon FRU Fan Product Part Number : DFPD0956B2HY002 Product Version : 01.01.00 Product Serial : 00AY Product Asset Tag : Product Custom Data 1 : 05-000627 Smart Fan Manufacturer ID : 40981 Smart Fan Version : 01.06.00 Smart Fan FW Version : 01.01.00 Smart Fan Mfg Date : Fri Jun 4 16:41:00 2021 Smart Fan Voltage (mV) : 12000 Smart Fan Current (mA) : 5300 Smart Fan Front RPM : 11200 Smart Fan Rear RPM : 10300 root@bmc-oob:~# fruid-util fan1 FRU Information : FAN1 --------------- : ------------------ Product Manufacturer : AVC Product Name : Grand Canyon FRU Fan Product Part Number : DFPD0956B2HY002 Product Version : 01.01.00 Product Serial : 00CQ Product Asset Tag : Product Custom Data 1 : 05-000627 Smart Fan Manufacturer ID : 40981 Smart Fan Version : 01.06.00 Smart Fan FW Version : 01.01.00 Smart Fan Mfg Date : Fri Jun 4 15:59:00 2021 Smart Fan Voltage (mV) : 12000 Smart Fan Current (mA) : 5300 Smart Fan Front RPM : 11200 Smart Fan Rear RPM : 10300 (4) Expander reset - FAN FRU checksum is same root@bmc-oob:~# sol-util scc_exp_smart ------------------TERMINAL MULTIPLEXER--------------------- CTRL-l ? : Display help message. CTRL-l x : Terminate the connection. /var/log/mTerm_scc_exp_smart.log : Log location CTRL-l + b : Send Break ----------------------------------------------------------- cmd >reset *BMC won't dump FAN FRU again root@bmc-oob:~# cat /var/log/messages | grep exp ... - FAN FRU checksum is different root@bmc-oob:~# cp /tmp/fruid_fan1.bin /tmp/fruid_fan0.bin root@bmc-oob:~# sol-util scc_exp_smart ------------------TERMINAL MULTIPLEXER--------------------- CTRL-l ? : Display help message. CTRL-l x : Terminate the connection. /var/log/mTerm_scc_exp_smart.log : Log location CTRL-l + b : Send Break ----------------------------------------------------------- cmd >reset *BMC will dump FAN FRU again root@bmc-oob:~# cat /var/log/messages | grep exp .. 2021 Oct 29 01:38:13 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan0 initial is done. - FAN FRU binary data isn't exsit root@bmc-oob:~# rm /tmp/fruid_fan0.bin root@bmc-oob:~# rm /tmp/fruid_fan1.bin root@bmc-oob:~# rm /tmp/fruid_fan2.bin root@bmc-oob:~# rm /tmp/fruid_fan3.bin root@bmc-oob:~# ls /tmp | grep fruid fruid_bmc.bin fruid_dpb.bin fruid_nic.bin fruid_scc.bin fruid_server.bin fruid_uic.bin root@bmc-oob:~# sol-util scc_exp_smart ------------------TERMINAL MULTIPLEXER--------------------- CTRL-l ? : Display help message. CTRL-l x : Terminate the connection. /var/log/mTerm_scc_exp_smart.log : Log location CTRL-l + b : Send Break ----------------------------------------------------------- cmd >reset *BMC will dump FAN FRU again root@bmc-oob:~# cat /var/log/messages | grep exp .. 2021 Oct 29 01:42:45 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan0 initial is done. 2021 Oct 29 01:42:45 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan1 initial is done. 2021 Oct 29 01:42:45 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan3 initial is done. 2021 Oct 29 01:42:45 bmc-oob. user.info grandcanyon-6e34e8a87e4-dirty: exp-cached: FRU: fan2 initial is done. root@bmc-oob:~# ls /tmp | grep fruid fruid_bmc.bin fruid_dpb.bin fruid_fan0.bin fruid_fan1.bin fruid_fan2.bin fruid_fan3.bin fruid_nic.bin fruid_scc.bin fruid_server.bin fruid_uic.bin Reviewed By: williamspatrick fbshipit-source-id: 2b6724032a

Summary: ipmi_handle_oem_usb_dbg will exit when it's not supposed to if the key does not exist in the kv store. Assume that no one is blocking if the key does not exist. Otherwsie check value. Test Plan: Build Reviewed By: amithash fbshipit-source-id: c7d26679a9

…1919) Summary: -There are 3 USB HUBs on GPv3 board and many devices are attached to them. If the system power is changed to S5 state, these devices will be lost at the same time. And it would make USB HUBs to be abnormal. In order to make sure the USB HUBs can work, BMC will run USB HUB reset if needed. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1919 Test Plan: -build code(pass) -run GPv3 VR firmware update 200 rounds on 18 blades(9 sleds) (pass) -run CWC VR firmware update 200 rounds on 4 blades(4 sleds) (pass) Reviewed By: zhdaniel12 fbshipit-source-id: d18362200e

…ot1 fru on cwc (#1916) Summary: - Currently, fruid-util slot1 all will not show 2u top/bot device fru on cwc, however, 2u top/bot also belong to slot1, and thus their fru should be shown when print all slot1 fru. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1916 Test Plan: - Check if fruid-util slot1 all can also show 2u top/bot device fru - pass Log: root@bmc-oob:~# fruid-util slot1 all FRU Information : Server board 1 --------------- : ------------------ Chassis Type : Rack Mount Chassis Chassis Part Number : N/A Chassis Serial Number : N/A Chassis Custom Data 1 : M0Y861L100272 Board Mfg Date : Sun Oct 24 20:33:00 2021 Board Mfg : Wiwynn Board Product : Delta Lake-Class1 Board Serial : WN3302201DN1A Board Part Number : B81.02610.0133 Board FRU ID : 1.0 Board Custom Data 1 : 02-000342 Board Custom Data 2 : PCB Supplier - GCE Product Manufacturer : Wiwynn Product Name : Delta Lake DVT Product Part Number : BZA.02601.0094 Product Version : YoDL03 Product Serial : BZA02400026N01A Product Asset Tag : N/A Product FRU ID : 1.0 Product Custom Data 1 : 01-005128 Product Custom Data 2 : N/A Failed print FRUID for Server board 1 1U-dev0 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 1U-dev1 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 1U-dev2 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 1U-dev3 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev0 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev1 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev2 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev3 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev4 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev5 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev6 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev7 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev8 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev9 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev10 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev11 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev12 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U-dev13 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 1U Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 2U Check syslog for errors! (err 2h) FRU Information : Server board 1 2U-top --------------- : ------------------ Board Mfg Date : Thu Jul 29 15:35:00 2021 Board Mfg : Wiwynn Board Product : GPV3 Expansion Board Board Serial : WC1612900RN1A Board Part Number : R81.06D10.A016 Board FRU ID : 1.0 Board Custom Data 1 : 19-001950 Board Custom Data 2 : PCB Supplier - GCE Product Manufacturer : Wiwynn Product Name : Kings Canyon 4U T17 YV3 EVT Product Part Number : TBC Product Version : EVT1 Product Serial : TBC Product Asset Tag : AA44338 Product FRU ID : 1.0 Product Custom Data 1 : 00-000000 Product Custom Data 2 : N/A FRU Information : Server board 1 2U-bot --------------- : ------------------ Board Mfg Date : Thu Jul 29 15:35:00 2021 Board Mfg : Wiwynn Board Product : GPV3 Expansion Board Board Serial : WC1612900RN1A Board Part Number : R81.06D10.A016 Board FRU ID : 1.0 Board Custom Data 1 : 19-001950 Board Custom Data 2 : PCB Supplier - GCE Product Manufacturer : Wiwynn Product Name : Kings Canyon 4U T17 YV3 EVT Product Part Number : TBC Product Version : EVT1 Product Serial : TBC Product Asset Tag : AA44338 Product FRU ID : 1.0 Product Custom Data 1 : 00-000000 Product Custom Data 2 : N/A FRU Information : Server board 1 2U-cwc --------------- : ------------------ Board Mfg Date : Tue Aug 3 22:48:00 2021 Board Mfg : Wiwynn Board Product : CWC Switch Board Board Serial : WC03129003NSB Board Part Number : R81.06D10.A003 Board FRU ID : 1.0 Board Custom Data 1 : 19-001952 Board Custom Data 2 : GCE Product Manufacturer : Wiwynn Product Name : Kings Canyon 4U T17 YV3 EVT Product Part Number : TBC Product Version : EVT1 Product Serial : TBC Product Asset Tag : AA44338 Product FRU ID : 1.0 Product Custom Data 1 : 00-000000 Product Custom Data 2 : N/A Failed print FRUID for Server board 1 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 Check syslog for errors! (err 2h) Failed print FRUID for Server board 1 Check syslog for errors! (err 2h) FRU Information : TOP GPV3 --------------- : ------------------ Board Mfg Date : Thu Jul 29 15:35:00 2021 Board Mfg : Wiwynn Board Product : GPV3 Expansion Board Board Serial : WC1612900RN1A Board Part Number : R81.06D10.A016 Board FRU ID : 1.0 Board Custom Data 1 : 19-001950 Board Custom Data 2 : PCB Supplier - GCE Product Manufacturer : Wiwynn Product Name : Kings Canyon 4U T17 YV3 EVT Product Part Number : TBC Product Version : EVT1 Product Serial : TBC Product Asset Tag : AA44338 Product FRU ID : 1.0 Product Custom Data 1 : 00-000000 Product Custom Data 2 : N/A Failed print FRUID for TOP GPV3 Check syslog for errors! (err 2h) Failed print FRUID for TOP GPV3 Check syslog for errors! (err 2h) Failed print FRUID for TOP GPV3 Check syslog for errors! (err 2h) Failed print FRUID for TOP GPV3 Check syslog for errors! (err 2h) Failed print FRUID for TOP GPV3 2U-dev0 Check syslog for errors! (err 2h) FRU Information : TOP GPV3 2U-dev1 --------------- : ------------------ Board Mfg Date : Wed Jan 13 15:05:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210117751 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021017 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210117751 Product Asset Tag : Product FRU ID : 0.35 FRU Information : TOP GPV3 2U-dev2 --------------- : ------------------ Board Mfg Date : Mon Jan 25 20:13:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306759 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306759 Product Asset Tag : Product FRU ID : 0.35 FRU Information : TOP GPV3 2U-dev3 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA FRU Information : TOP GPV3 2U-dev4 --------------- : ------------------ Board Mfg Date : Sun Oct 10 01:00:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306860 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306860 Product Asset Tag : Product FRU ID : 0.35 Failed print FRUID for TOP GPV3 2U-dev5 Check syslog for errors! (err 2h) FRU Information : TOP GPV3 2U-dev6 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA FRU Information : TOP GPV3 2U-dev7 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA FRU Information : TOP GPV3 2U-dev8 --------------- : ------------------ Board Mfg Date : Tue Jan 26 08:32:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306942 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306942 Product Asset Tag : Product FRU ID : 0.35 FRU Information : TOP GPV3 2U-dev9 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA FRU Information : TOP GPV3 2U-dev10 --------------- : ------------------ Board Mfg Date : Wed Jan 27 03:37:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306950 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306950 Product Asset Tag : Product FRU ID : 0.35 FRU Information : TOP GPV3 2U-dev11 --------------- : ------------------ Board Mfg Date : Sun Oct 10 01:00:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306860 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306860 Product Asset Tag : Product FRU ID : 0.35 Failed print FRUID for TOP GPV3 2U-dev12 Check syslog for errors! (err 2h) Failed print FRUID for TOP GPV3 2U-dev13 Check syslog for errors! (err 2h) FRU Information : BOT GPV3 --------------- : ------------------ Board Mfg Date : Thu Jul 29 15:35:00 2021 Board Mfg : Wiwynn Board Product : GPV3 Expansion Board Board Serial : WC1612900RN1A Board Part Number : R81.06D10.A016 Board FRU ID : 1.0 Board Custom Data 1 : 19-001950 Board Custom Data 2 : PCB Supplier - GCE Product Manufacturer : Wiwynn Product Name : Kings Canyon 4U T17 YV3 EVT Product Part Number : TBC Product Version : EVT1 Product Serial : TBC Product Asset Tag : AA44338 Product FRU ID : 1.0 Product Custom Data 1 : 00-000000 Product Custom Data 2 : N/A Failed print FRUID for BOT GPV3 Check syslog for errors! (err 2h) Failed print FRUID for BOT GPV3 Check syslog for errors! (err 2h) Failed print FRUID for BOT GPV3 Check syslog for errors! (err 2h) Failed print FRUID for BOT GPV3 Check syslog for errors! (err 2h) FRU Information : BOT GPV3 2U-dev0 --------------- : ------------------ Board Mfg Date : Wed Jan 13 11:19:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210118076 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021017 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210118076 Product Asset Tag : Product FRU ID : 0.35 FRU Information : BOT GPV3 2U-dev1 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA FRU Information : BOT GPV3 2U-dev2 --------------- : ------------------ Board Mfg Date : Sun Oct 10 01:00:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306860 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306860 Product Asset Tag : Product FRU ID : 0.35 FRU Information : BOT GPV3 2U-dev3 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA Failed print FRUID for BOT GPV3 2U-dev4 Check syslog for errors! (err 2h) FRU Information : BOT GPV3 2U-dev5 --------------- : ------------------ Board Mfg Date : Tue Jan 26 00:50:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210307278 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210307278 Product Asset Tag : Product FRU ID : 0.35 FRU Information : BOT GPV3 2U-dev6 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA FRU Information : BOT GPV3 2U-dev7 --------------- : ------------------ Board Mfg Date : Sun Oct 10 01:00:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306860 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306860 Product Asset Tag : Product FRU ID : 0.35 FRU Information : BOT GPV3 2U-dev8 --------------- : ------------------ Board Mfg Date : Sun Oct 10 01:00:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306860 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306860 Product Asset Tag : Product FRU ID : 0.35 FRU Information : BOT GPV3 2U-dev9 --------------- : ------------------ Board Mfg Date : Tue Jan 12 21:20:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210116481 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021017 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210116481 Product Asset Tag : Product FRU ID : 0.35 FRU Information : BOT GPV3 2U-dev10 --------------- : ------------------ Board Mfg Date : Fri Sep 24 01:00:00 2021 Board Mfg : Foxconn Board Product : 29-000006 Board Serial : SNB370000N Board Part Number : SNB370000N Board FRU ID : NA Board Custom Data 1 : Accelerator Dual M.2 Product Manufacturer : Broadcom Product Name : P3-50121-11 Product Part Number : Defined by vendor Product Version : PreQCP Product Serial : SNB370000N Product Asset Tag : NA FRU Information : BOT GPV3 2U-dev11 --------------- : ------------------ Board Mfg Date : Mon Feb 1 05:30:00 2021 Board Mfg : Intel Corporation Board Product : NNPI1150 Board Serial : WTS210306553 Board Part Number : 999WTT Board FRU ID : 0.35 Board Custom Data 1 : 4062 Board Custom Data 2 : Accelerator M.2 Board Custom Data 3 : 5020 Board Custom Data 4 : 2021035 Board Custom Data 5 : ATS Board Custom Data 6 : Intel Corporation Product Manufacturer : Intel Corporation Product Name : NNPI1150 Product Part Number : K31501-804 Product Version : Product Serial : WTS210306553 Product Asset Tag : Product FRU ID : 0.35 Failed print FRUID for BOT GPV3 2U-dev12 Check syslog for errors! (err 2h) Failed print FRUID for BOT GPV3 2U-dev13 Check syslog for errors! (err 2h) root@bmc-oob:~# Reviewed By: peterdelevoryas fbshipit-source-id: 5f5e1101ef

Summary: 1. Implement the fan table that thermal provided. 2. When HOST power on, BMC would check the 2U config for setting the corresponding sensor correction. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1915 Test Plan: - Build code:pass - Check by thermal team:pass Reviewed By: zhdaniel12 fbshipit-source-id: 5f29b4d365

Summary: - Per FB SW team's request to change utility syntax to keep consistency, this commit changes the syntax in enclosure-util on cwc. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1907 Test Plan: - Check if end device info can be shown with new syntax on cwc - pass Log: - on cwc root@bmc-oob:~# enclosure-util Usage: enclosure-util <slot1|slot2|slot3|slot4> --drive-status <all|1U-dev[0..3]|2U-dev[0..13]> enclosure-util <slot1|slot2|slot3|slot4> --drive-health Usage: enclosure-util <slot1-2U-top|slot1-2U-bot> --drive-status <all|2U-dev[0..13]> enclosure-util <slot1-2U-top|slot1-2U-bot> --drive-health root@bmc-oob:~# enclosure-util slot1-2U-top --drive-health * Mux selecting...bus 2, chn: 0, dev_id: 0 slot1-2U-dev0 : NA * Mux selecting...bus 2, chn: 1, dev_id: 1 slot1-2U-dev1 : Abnormal * Mux selecting...bus 4, chn: 0, dev_id: 2 slot1-2U-dev2 : NA * Mux selecting...bus 4, chn: 1, dev_id: 3 slot1-2U-dev3 : Abnormal * Mux selecting...bus 6, chn: 0, dev_id: 4 slot1-2U-dev4 : NA * Mux selecting...bus 6, chn: 1, dev_id: 5 slot1-2U-dev5 : Abnormal * Mux selecting...bus 5, chn: 0, dev_id: 6 slot1-2U-dev6 : Abnormal * Mux selecting...bus 5, chn: 1, dev_id: 7 slot1-2U-dev7 : Abnormal * Mux selecting...bus 7, chn: 0, dev_id: 8 slot1-2U-dev8 : Abnormal * Mux selecting...bus 7, chn: 1, dev_id: 9 slot1-2U-dev9 : Abnormal * Mux selecting...bus 3, chn: 0, dev_id: 10 slot1-2U-dev10 : Abnormal * Mux selecting...bus 3, chn: 1, dev_id: 11 slot1-2U-dev11 : Abnormal * Mux selecting...bus 9, chn: 4, dev_id: 12 slot1-2U-dev12 : Normal * Mux selecting...bus 9, chn: 8, dev_id: 13 slot1-2U-dev13 : Normal root@bmc-oob:~# enclosure-util slot1-2U-bot --drive-health * Mux selecting...bus 2, chn: 0, dev_id: 0 slot1-2U-dev0 : Abnormal * Mux selecting...bus 2, chn: 1, dev_id: 1 slot1-2U-dev1 : Abnormal * Mux selecting...bus 4, chn: 0, dev_id: 2 slot1-2U-dev2 : Abnormal * Mux selecting...bus 4, chn: 1, dev_id: 3 slot1-2U-dev3 : Abnormal * Mux selecting...bus 6, chn: 0, dev_id: 4 slot1-2U-dev4 : Abnormal * Mux selecting...bus 6, chn: 1, dev_id: 5 slot1-2U-dev5 : Abnormal * Mux selecting...bus 5, chn: 0, dev_id: 6 slot1-2U-dev6 : Abnormal * Mux selecting...bus 5, chn: 1, dev_id: 7 slot1-2U-dev7 : Abnormal * Mux selecting...bus 7, chn: 0, dev_id: 8 slot1-2U-dev8 : Abnormal * Mux selecting...bus 7, chn: 1, dev_id: 9 slot1-2U-dev9 : Abnormal * Mux selecting...bus 3, chn: 0, dev_id: 10 slot1-2U-dev10 : Abnormal * Mux selecting...bus 3, chn: 1, dev_id: 11 slot1-2U-dev11 : Abnormal * Mux selecting...bus 9, chn: 4, dev_id: 12 slot1-2U-dev12 : Normal * Mux selecting...bus 9, chn: 8, dev_id: 13 slot1-2U-dev13 : Normal root@bmc-oob:~# enclosure-util slot1-2U-top --drive-status 2U-dev0 * Mux selecting...bus 2, chn: 0, dev_id: 0 slot1-2U-dev0 : NA root@bmc-oob:~# enclosure-util slot1-2U-top --drive-status 2U-dev1 * Mux selecting...bus 2, chn: 1, dev_id: 1 slot1-2U-dev1 : Status Flags: 0x00 SMBUS block read complete: No Drive Ready: Ready Drive Functional: Unrecoverable Failure Reset Required: Required Port 0 PCIe Link Active: Down Port 1 PCIe Link Active: Down SMART Critical Warning: 0x00 Spare Space: Low Temperature Warning: Abnormal NVM Subsystem Reliability: Degraded Media Status: Read Only mode Volatile Memory Backup Device: Failed Composite Temperature: 49 C Percentage Drive Life Used: 0 Vendor: Intel(0x8086) Serial Number: WTS210117751▒▒▒▒▒▒▒▒ root@bmc-oob:~# enclosure-util slot1-2U-bot --drive-status 2U-dev0 * Mux selecting...bus 2, chn: 0, dev_id: 0 slot1-2U-dev0 : Status Flags: 0x00 SMBUS block read complete: No Drive Ready: Ready Drive Functional: Unrecoverable Failure Reset Required: Required Port 0 PCIe Link Active: Down Port 1 PCIe Link Active: Down SMART Critical Warning: 0x00 Spare Space: Low Temperature Warning: Abnormal NVM Subsystem Reliability: Degraded Media Status: Read Only mode Volatile Memory Backup Device: Failed Composite Temperature: 47 C Percentage Drive Life Used: 0 Vendor: Intel(0x8086) Serial Number: ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ root@bmc-oob:~# Reviewed By: zhdaniel12 fbshipit-source-id: 037dfb918f

…ower-util (#1918) Summary: - Recently, it is found that the cpld fw update process can be interrupted by power-util on cwc/gpv3, the reason is that the time out for cpld fw update is 60 seconds now, but it actually takes more than 100 seconds for cpld fw update on cwc/gpv3. This commit extend the time out for cpld fw update to 300 seconds to avoid interruption. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1918 Test Plan: - Check if 12v cycle can be executed during cpld fw update - pass Log: - update cpld fw root@bmc-oob:/tmp# fw-util slot1 --update 2U-top 2U_cpld Y3CG3_MCHP_D02.jed 3358 root 69640 S /usr/local/bin/healthd slot_id: 1, comp: 32, intf: 0, img: Y3CG3_MCHP_D02.jed, force: 0 * Turning off BIC sensor monitor... Init libusb Successful! .... Elapsed time: 101 sec. * Turning on BIC sensor monitor... Upgrade of slot1 : 2U_cpld_top succeeded root@bmc-oob:/tmp# - power cycle root@bmc-oob:~# power-util slot1 12V-cycle FW update for slot1 is ongoing, block the power controlling. ERROR: power-util fru[1] [12V_CYCLE] failed root@bmc-oob:~# power-util slot1 12V-cycle FW update for slot1 is ongoing, block the power controlling. ERROR: power-util fru[1] [12V_CYCLE] failed root@bmc-oob:~# Reviewed By: peterdelevoryas fbshipit-source-id: 88b4068041

Summary: in title Test Plan: do it live Reviewed By: doranand fbshipit-source-id: 5657bb0851

Summary: Adjust fan table of UIC inlet temperature on Type 7 system. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1917 Test Plan: 1. Build and test pass on Grand Canyon. 2. Check there are no unexpected error logs in BMC /var/log/messages and BMC SELs 3. Check FSC version is correct. root@bmc-oob:~# fw-util bmc --version fscd Fan Speed Controller Version: fbgc-type7-pvt-v1 4. Check fans' speed are normal. root@bmc-oob:~# fan-util --get Fan 0 Front Speed: 2700 RPM (20%) Fan 1 Front Speed: 2790 RPM (20%) Fan 2 Front Speed: 2730 RPM (20%) Fan 3 Front Speed: 2760 RPM (20%) Fan Mode: Normal FSCD Driver: linear_soc_therm_margin+pid_soc_therm_margin(server:bs_therm_margin) Sensor Fail: None Fan Fail: None Sled Fan Latch Open: False Reviewed By: garnermic fbshipit-source-id: 0a2006c03e

Summary: This diff expands process restarts test to all other fboss platforms. Closing on tech tebt Test Plan: live on this diff. Reviewed By: doranand fbshipit-source-id: 9d182bbf08

…e get Summary: when BMC restart, the cache for FRU postcode will get deleted. We should add empty string as matching pattern. Test Plan: BMC postcode is empty: ``` [davcheng@devvm4100.prn0 ~/fbsource/fbcode] ssh root@fbtp-oob.312681494.fre101 Last login: Thu Nov 4 09:33:01 2021 from 2401:db00:eef0:1120:3520:0:1401:c86e root@dhcp-100-96-192-172:~# bios-util mb --postcode get root@dhcp-100-96-192-172:~# ``` Run CIT on this particular host and pass: https://www.internalfb.com/intern/sandcastle/job/4503600142872077/ Reviewed By: doranand fbshipit-source-id: 02989df88e

Summary: early GPIOA1 export for re-spin baseboard - ADM1278: LOW (0) - LTC4282: HIGH (1) Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2725 Test Plan: 1. Build passed on northdome 2. Check GPIOA1 with PVT BB, the value should be 0 (ADM1278) ``` root@bmc-oob:~# cat /tmp/gpionames/HSC_SELECT/direction in root@bmc-oob:~# cat /tmp/gpionames/HSC_SELECT/value 0 ``` Reviewed By: GoldenBug fbshipit-source-id: 81ffdacdc2

…?=20continue=20power=20action=20even=20power-up=20prepare=20co?= =?UTF-8?q?=E2=80=A6?= (#2726) Summary: Workaround for NIC firmware issue To prevent slot can not be powered off or 12V-off when NIC firmware crashed Add extra messages to inform user the command fail, but always return 0 (successful) Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2726 Test Plan: 1. Build passed on northdome 2. Manual test with power off & 12V-off with dead NIC - power off ``` root@bmc-oob:~# power-util slot1 off Powering fru 1 to OFF state... Power-up prepare command failed! Discard power-up prepare command fail, continue the power action... root@bmc-oob:~# power-util slot1 status Power status for fru 1 : OFF root@bmc-oob:~# log-util all --print 2011 Jan 18 15:40:57 log-util: User cleared all logs 1 slot1 2011-01-18 15:42:15 gpiod FRU: 1, System powered OFF 1 slot1 2011-01-18 15:42:17 power-util SERVER_POWER_OFF successful for FRU: 1 ``` - 12V-off ``` root@bmc-oob:~# power-util slot1 12V-off 12V Powering fru 1 to OFF state... Power-up prepare command failed! Discard power-up prepare command fail, continue the power action... root@bmc-oob:~# log-util all --print 2011 Jan 18 15:40:57 log-util: User cleared all logs 1 slot1 2011-01-18 15:42:15 gpiod FRU: 1, System powered OFF 1 slot1 2011-01-18 15:42:17 power-util SERVER_POWER_OFF successful for FRU: 1 1 slot1 2011-01-18 15:43:20 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2011-01-18 15:43:20, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Assertion 1 slot1 2011-01-18 15:43:21 gpiod FRU: 1, System powered ON 1 slot1 2011-01-18 15:43:22 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2011-01-18 15:43:22, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Deassertion 1 slot1 2011-01-18 15:43:26 power-util SERVER_POWER_ON successful for FRU: 1 1 slot1 2011-01-18 15:44:36 power-util SERVER_12V_OFF successful for FRU: 1 ``` Reviewed By: GoldenBug fbshipit-source-id: 4868198d35

Summary: as title Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2722 Test Plan: 1. Build passed on northdome 2. Manual generate a SEL and check SEL log is correct ``` root@bmc-oob:~# log-util all --clear root@bmc-oob:~# ipmi-util 1 0x28 0x44 0x00 0x00 0x02 0x00 0x00 0x00 0x00 0x40 0x00 0x04 0xC8 0x46 0x6F 0xEE 0x69 0xff 2C 44 00 02 00 root@bmc-oob:~# log-util all --print 2018 Mar 09 04:35:50 log-util: User cleared all logs 1 slot1 2018-03-09 04:35:58 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2018-03-09 04:35:58, Sensor: PSB_STS (0x46), Event Data: (EE69FF) BIOS OEM key revoked Assertion ``` Reviewed By: GoldenBug fbshipit-source-id: 29fe92abdf

Summary: 1. add ubifs health monitor in healthd, if "/sys/kernel/debug/ubifs/ubi0_0/ro_error" not equal to 0 then set UBIFS_ERROR flag in SRAM (rboot cause) and rboot BMC 2. in mount_data0.sh, BMC check UBIFS_ERROR flag is set or not, do force recovery if UBIFS_ERROR is set 3. add Reboot cause SEL for UBIFS_ERROR in healthd, so USER will know /mnt/data was cleard due to UBIFS_ERROR Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2723 Test Plan: 1. Build passed on Northdome 2. Simulate UBIFS read-only error, then BMC should force recovery (format) data0 partition during boot - trigger UBIFS read-only error from sysfs, then healthd will reboot BMC ``` root@bmc-oob:~# log-util all --print 2018 Mar 09 04:35:50 log-util: User cleared all logs 1 slot1 2018-03-09 04:35:58 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2018-03-09 04:35:58, Sensor: PSB_STS (0x46), Event Data: (EE69FF) BIOS OEM key revoked Assertion 0 all 2018-03-09 09:20:13 fw-util BMC fw upgrade initiated 0 all 2018-03-09 09:24:17 fw-util BMC fw upgrade completed. Version: northdome-8c7dd56e51e-dirty 1 slot1 2018-03-09 04:35:21 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2018-03-09 04:35:21, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Assertion 2 slot2 2018-03-09 04:35:22 ipmid SEL Entry: FRU: 2, Record: Standard (0x02), Time: 2018-03-09 04:35:22, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Assertion 3 slot3 2018-03-09 04:35:22 ipmid SEL Entry: FRU: 3, Record: Standard (0x02), Time: 2018-03-09 04:35:22, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Assertion 4 slot4 2018-03-09 04:35:23 ipmid SEL Entry: FRU: 4, Record: Standard (0x02), Time: 2018-03-09 04:35:23, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Assertion 1 slot1 2018-03-09 04:35:23 ipmid SEL Entry: FRU: 1, Record: Standard (0x02), Time: 2018-03-09 04:35:23, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Deassertion 2 slot2 2018-03-09 04:35:24 ipmid SEL Entry: FRU: 2, Record: Standard (0x02), Time: 2018-03-09 04:35:24, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Deassertion 3 slot3 2018-03-09 04:35:24 ipmid SEL Entry: FRU: 3, Record: Standard (0x02), Time: 2018-03-09 04:35:24, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Deassertion 4 slot4 2018-03-09 04:35:25 ipmid SEL Entry: FRU: 4, Record: Standard (0x02), Time: 2018-03-09 04:35:25, Sensor: SYSTEM_STATUS (0x10), Event Data: (07FFFF) Platform_Reset Deassertion 1 slot1 2018-03-09 04:35:27 power-util SERVER_POWER_ON successful for FRU: 1 2 slot2 2018-03-09 04:35:28 power-util SERVER_POWER_ON successful for FRU: 2 3 slot3 2018-03-09 04:35:28 power-util SERVER_POWER_ON successful for FRU: 3 4 slot4 2018-03-09 04:35:29 power-util SERVER_POWER_ON successful for FRU: 4 0 all 2018-03-09 04:35:41 healthd ASSERT: Verified boot failure (3,35) 0 all 2018-03-09 04:35:41 healthd Verified boot failure reason: U-Boot FIT did not contain the /keys node 0 all 2018-03-09 04:35:41 healthd SLED Powered OFF at Fri Mar 9 08:52:11 2018 4 slot4 2011-01-17 00:26:34 ipmid SEL Entry: FRU: 4, Record: Standard (0x02), Time: 2011-01-17 00:26:34, Sensor: PSB_STS (0x46), Event Data: (EE00FF) PSB Pass Assertion 1 slot1 2011-01-17 00:27:07 gpiod FRU: 1, System powered OFF 1 slot1 2011-01-17 00:27:09 power-util SERVER_POWER_OFF successful for FRU: 1 1 slot1 2011-01-17 00:27:24 power-util SERVER_12V_OFF successful for FRU: 1 0 all 2011-01-17 00:27:36 healthd SLED Powered ON at Mon Jan 17 00:24:51 2011 6 nic 2018-03-09 04:35:29 ncsid FRU: 6 NIC AEN Supported: 0x70007, AEN Enable Mask=0x70007 6 nic 2018-03-09 04:35:29 ncsid FRU: 6 PLDM type supported = 0x25 6 nic 2018-03-09 04:35:29 ncsid FRU: 6 PLDM type 0 version = 1.0.0.0 6 nic 2018-03-09 04:35:30 ncsid FRU: 6 PLDM type 2 version = 1.1.1.0 6 nic 2018-03-09 04:35:30 ncsid FRU: 6 PLDM type 5 version = 1.0.0.0 6 nic 2018-03-09 04:35:30 ncsid FRU: 6 PLDM sensor monitoring enabled 0 all 2018-03-09 04:35:31 healthd BMC Reboot detected - caused by reboot command root@bmc-oob:~# root@bmc-oob:~# echo 1 > /sys/kernel/debug/ubifs/ubi0_0/enable_ro [ 249.974345] UBIFS warning (ubi0:0 pid 2275): ubifs_ro_mode.part.0: switched to read-only mode, error 1 [ 249.993162] CPU: 0 PID: 2275 Comm: bash Not tainted 5.6.19-fby2 https://github.com/facebookexternal/openbmc.quanta/issues/1 [ 250.005614] Hardware name: Generic DT based system [ 250.015255] Backtrace: [ 250.020252] [<80108200>] (dump_backtrace) from [<8010849c>] (show_stack+0x20/0x24) [ 250.035515] r7:00000002 r6:97bc6000 r5:91f237f8 r4:97ad8800 [ 250.046937] [<8010847c>] (show_stack) from [<80817170>] (dump_stack+0x20/0x28) [ 250.061474] [<80817150>] (dump_stack) from [<803a42d0>] (ubifs_ro_mode.part.0+0x4c/0x54) [ 250.077750] [<803a4284>] (ubifs_ro_mode.part.0) from [<803a4414>] (ubifs_ro_mode+0x24/0x28) [ 250.094518] r5:91f237f8 r4:97a34c00 [ 250.101701] [<803a43f0>] (ubifs_ro_mode) from [<803c9264>] (dfs_file_write+0x120/0x1dc) [ 250.117790] [<803c9144>] (dfs_file_write) from [<803e02ec>] (full_proxy_write+0x64/0x80) [ 250.134064] r7:91f237f8 r6:005c8888 r5:90caeb40 r4:803c9144 [ 250.145487] [<803e0288>] (full_proxy_write) from [<8027c108>] (__vfs_write+0x4c/0x1e4) [ 250.161442] r9:00000000 r8:00000000 r7:803e0288 r6:00000002 r5:9a577f60 r4:90caeb40 [ 250.177019] [<8027c0bc>] (__vfs_write) from [<8027ef68>] (vfs_write+0xbc/0x18c) [ 250.191709] r9:00000000 r8:00000000 r7:9a577f60 r6:005c8888 r5:90caeb40 r4:00000002 [ 250.207272] [<8027eeac>] (vfs_write) from [<8027f210>] (ksys_write+0x70/0xf8) [ 250.221608] r8:00000000 r7:00000002 r6:005c8888 r5:90caeb40 r4:90caeb40 [ 250.235092] [<8027f1a0>] (ksys_write) from [<8027f2b0>] (sys_write+0x18/0x1c) [ 250.249428] r9:9a576000 r8:80101204 r7:00000004 r6:76f49b40 r5:76fbdff0 r4:00000002 [ 250.264989] [<8027f298>] (sys_write) from [<80101000>] (ret_fast_syscall+0x0/0x54) [ 250.280208] Exception stack(0x9a577fa8 to 0x9a577ff0) [ 250.290411] 7fa0: 00000002 76fbdff0 00000001 005c8888 00000002 00000001 [ 250.306839] 7fc0: 00000002 76fbdff0 76f49b40 00000004 76f4a0fc 76f49c64 00000000 0059fde4 [ 250.323244] 7fe0: 00000498 7e92a9e8 76ecd5e4 76ecd604 [ 251.974056] reboot: Restarting system ``` - BMC do force recovery (format) when detected UBIFS_ERROR is set ``` [ 18.287630] ubi0: default fastmap pool size: 25 [ 18.296821] ubi0: default fastmap WL pool size: 12 [ 18.306475] ubi0: attaching mtd5 [ 18.322910] ubi0: scanning is finished [ 18.348447] ubi0: attached mtd5 (name "data0", size 32 MiB) [ 18.359716] ubi0: PEB size: 65536 bytes (64 KiB), LEB size: 65408 bytes [ 18.373026] ubi0: min./max. I/O unit sizes: 1/256, sub-page size 1 [ 18.385465] ubi0: VID header offset: 64 (aligned 64), data offset: 128 [ 18.398584] ubi0: good PEBs: 512, bad PEBs: 0, corrupted PEBs: 0 [ 18.410659] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128 [ 18.425174] ubi0: max/mean erase counter: 18/8, WL threshold: 4096, image sequence number: 2073383838 [ 18.443669] ubi0: available PEBs: 0, total reserved PEBs: 512, PEBs reserved for bad PEB handling: 0 [ 18.462041] ubi0: background thread "ubi_bgt0d" started, PID 106 UBI device number 0, total 512 LEBs (33488896 bytes, 31.9 MiB), available 0 LEBs (0 bytes), LEB size 65408 bytes (63.8 KiB) UBIFS ERROR flag is set, start recovery.. [ 18.665756] ubi0: detaching mtd5 [ 18.677288] ubi0: mtd5 is detached ubiformat: mtd5 (nor), size 33554432 bytes (32.0 MiB), 512 eraseblocks of 65536 bytes (64.0 KiB), min. I/O size 1 bytes libscan: scanning eraseblock 511 -- 100 % complete ubiformat: 512 eraseblocks have valid erase counter, mean value is 8 ubiformat: formatting eraseblock 511 -- 100 % complete [ 116.836542] ubi0: default fastmap pool size: 25 [ 116.845731] ubi0: default fastmap WL pool size: 12 [ 116.855381] ubi0: attaching mtd5 [ 116.871814] ubi0: scanning is finished [ 116.893395] ubi0: attached mtd5 (name "data0", size 32 MiB) [ 116.904664] ubi0: PEB size: 65536 bytes (64 KiB), LEB size: 65408 bytes [ 116.917963] ubi0: min./max. I/O unit sizes: 1/256, sub-page size 1 [ 116.930399] ubi0: VID header offset: 64 (aligned 64), data offset: 128 [ 116.943523] ubi0: good PEBs: 512, bad PEBs: 0, corrupted PEBs: 0 [ 116.955601] ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128 [ 116.970112] ubi0: max/mean erase counter: 19/9, WL threshold: 4096, image sequence number: 288564054 [ 116.988436] ubi0: available PEBs: 506, total reserved PEBs: 6, PEBs reserved for bad PEB handling: 0 [ 117.006802] ubi0: background thread "ubi_bgt0d" started, PID 120 UBI device number 0, total 512 LEBs (33488896 bytes, 31.9 MiB), available 506 LEBs (33096448 bytes, 31.5 MiB), LEB size 65408 bytes (63.8 KiB) Set volume size to 33096448 Volume ID 0, size 506 LEBs (33096448 bytes, 31.5 MiB), LEB size 65408 bytes (63.8 KiB), dynamic, name "data0", alignment 1 ubifs_mount /dev/ubi0_0 to /mnt/data.. [ 117.509363] UBIFS (ubi0:0): default file-system created [ 117.520410] UBIFS (ubi0:0): Mounting in unauthenticated mode [ 117.545309] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 123 [ 117.569641] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "data0" [ 117.584404] UBIFS (ubi0:0): LEB size: 65408 bytes (63 KiB), min./max. I/O unit sizes: 8 bytes/256 bytes [ 117.603270] UBIFS (ubi0:0): FS size: 32442368 bytes (30 MiB, 496 LEBs), journal size 1635200 bytes (1 MiB, 25 LEBs) [ 117.624195] UBIFS (ubi0:0): reserved for root: 1532332 bytes (1496 KiB) [ 117.637517] UBIFS (ubi0:0): media format: w5/r0 (latest is w5/r0), UUID 094CA4C2-7E1F-4A7B-A041-092315BA32C9, small LPT model ``` - after BMC booted, check SEL log, It should contains UBIFS_ERROR log ``` root@bmc-oob:~# log-util all --print 6 nic 2018-03-09 04:35:57 ncsid FRU: 6 NIC AEN Supported: 0x70007, AEN Enable Mask=0x70007 6 nic 2018-03-09 04:35:57 ncsid FRU: 6 PLDM type supported = 0x25 6 nic 2018-03-09 04:35:57 ncsid FRU: 6 PLDM type 0 version = 1.0.0.0 6 nic 2018-03-09 04:35:57 ncsid FRU: 6 PLDM type 2 version = 1.1.1.0 6 nic 2018-03-09 04:35:57 ncsid FRU: 6 PLDM type 5 version = 1.0.0.0 6 nic 2018-03-09 04:35:57 ncsid FRU: 6 PLDM sensor monitoring enabled 0 all 2018-03-09 04:35:59 healthd ASSERT: Verified boot failure (3,35) 0 all 2018-03-09 04:35:59 healthd Verified boot failure reason: U-Boot FIT did not contain the /keys node 0 all 2018-03-09 04:35:59 healthd UBIFS Error detected during boot 0 all 2018-03-09 04:35:59 healthd BMC Reboot detected - caused by reboot command ``` Reviewed By: GoldenBug fbshipit-source-id: cf5b10d206

Summary: Fix the typo of Drive Plane Board in fruid-util. Pull Request resolved: https://github.com/facebookexternal/openbmc.wiwynn/pull/1920 Test Plan: 1. Build and test pass on Grand Canyon. 2. Check there are no unexpected error logs in BMC /var/log/messages and BMC SELs. 3. Check the FRU name of DPB is correct in fruid-util. root@bmc-oob:~# fruid-util dpb FRU Information : Drive Plane Board --------------- : ------------------ Chassis Type : Rack Mount Chassis Chassis Part Number : B81.04901.0065 Chassis Serial Number : WTR212901LZSA Board Mfg Date : Tue Jul 13 00:04:00 2021 Board Mfg : Wiwynn Board Product : FrontDPB Board Serial : WR9412702EZSA Board Part Number : B81.04910.0094 Board Custom Data 1 : 19-001895 Board Custom Data 2 : PCB Supplier - GCE Product Manufacturer : Wiwynn Product Name : Grand Canyon DVT Product Part Number : B81.04901.0065 Product Version : DVT Product Serial : WTR212901LZSA Product Asset Tag : AS76273 Product Custom Data 1 : BZA.04901.0061 Product Custom Data 2 : 19-001896 Reviewed By: garnermic fbshipit-source-id: 56f087d4f8

Summary: as title Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2724 Test Plan: 1. Build and test passed on northdome Reviewed By: GoldenBug fbshipit-source-id: a943f17158

Summary: enclosure-util dispaly more GPv3 m.2 device info Pull Request resolved: https://github.com/facebookexternal/openbmc.quanta/pull/2727 Test Plan: Could show more GPv3 m.2 device info: root@bmc-oob:~# enclosure-util slot1 --drive-status 2U-dev0 * Mux selecting...bus 2, chn: 0, dev_id: 0 slot1-2U-dev0 : Status Flags: 0x3B SMBUS block read complete: No Drive Ready: Ready Drive Functional: Functional Reset Required: No Port 0 PCIe Link Active: Up Port 1 PCIe Link Active: Down SMART Critical Warning: 0x00 Spare Space: Low Temperature Warning: Abnormal NVM Subsystem Reliability: Degraded Media Status: Read Only mode Volatile Memory Backup Device: Failed Composite Temperature: 55 C Percentage Drive Life Used: 0 Vendor: Broadcom(0x14E4) Serial Number: M2AFB21370007IFVX00 Module Product Part Number: BCM958402M2AFB Management End Point Form Factor: M.2 22110 (0x35) Form Factor Information 0 Register: Accelerator (0x01) Module health: 0x00 Lower Thermal Threshold: 0 C Upper Thermal Threshold: 0 C Power State: Unknown (0x00) SMBus/I2C Frquency: 400 kHz Module Static TDP level setting: Unknown (0x00) ASIC version: 0x01 FW version: v2.0 ASIC Core1 Voltage: 0.1789 V ASIC Core2 Voltage: 0.3314 V Module Power Rail1 Voltage: 0.0669 V Module Power Rail2 Voltage: 0.0000 V ASIC Error Type Report: 0x00 Module Error Type Report: 0x00 Warning Flag: 0x00 Interrupt Flag: 0x00 Historical Max ASIC Temperature: 0 C Total internal memory error count: 0 Total external memory error count: 0 SMBus error: 0x00 Reviewed By: williamspatrick fbshipit-source-id: ab6962153c

Summary: With this diff, prepare wedge100 to upgrade to v2019.04 Nothing will happen until D32050664 land. Add FBOSS common change: * network support * dual boot Apply Wedge special change: * use UART3 as console * use MAC2 for network * PHY address is 24 Test Plan: Test on Wedge100 with stack D32050664 * boot up * uboot env * network ``` DRAM Init-DDR3 CBR0-1234567012345670123456701234567 CBR134Done U-Boot 2019.04 wedge100-50a5f79ee527 (Nov 03 2021 - 04:35:37 +0000) Model: Facebook Wedge100 DRAM: 248 MiB Watchdog: 300s MMC: Loading Environment from SPI Flash... SF: Detected mx25l25635e with page size 256 Bytes, erase size 64 KiB, total 32 MiB *** Warning - bad CRC, using default environment Saving Environment to SPI Flash... SF: Detected mx25l25635e with page size 256 Bytes, erase size 64 KiB, total 32 MiB Erasing SPI flash...Writing to SPI flash...done OK In: serial Out: serial Err: serial H/W: AST2400 series chip Rev. 01 Net: Warning: ethernet@1e680000 (eth0) using random MAC address - e6:e4:a2:83:09:50 eth0: ethernet@1e680000 autoboot in 3 seconds (stop with 'Delete' key)... stop wdt2 Wedge-boot=> print baudrate=9600 bootargs=console=ttyS2,9600n8 root=/dev/ram rw bootcmd=bootm 20080000; bootdelay=3 bootfile=flash-wedge100 eeprom=y fdtcontroladdr=4f69c4e0 initrd_high=a0000000 spi_dma=no stderr=serial stdin=serial stdout=serial updatefile=flash-wedge100.fit verify=no Environment size: 270/131068 bytes Wedge-boot=> set ipaddr 100.96.192.201 Wedge-boot=> set netmask 255.255.255.128 Wedge-boot=> set gatewayip 100.96.192.129 Wedge-boot=> ping 100.96.192.214 Hacking, assume Mode-1000X ethernet@1e680000: link up, 1000 Mbps full-duplex mac:e6:e4:a2:83:09:50 Using ethernet@1e680000 device host 100.96.192.214 is alive Wedge-boot=> ping 100.96.192.200 Hacking, assume Mode-1000X ethernet@1e680000: link up, 1000 Mbps full-duplex mac:e6:e4:a2:83:09:50 Using ethernet@1e680000 device host 100.96.192.200 is alive Wedge-boot=> saveenv Saving Environment to SPI Flash... Erasing SPI flash...Writing to SPI flash...done OK Wedge-boot=> print baudrate=9600 bootargs=console=ttyS2,9600n8 root=/dev/ram rw bootcmd=bootm 20080000; bootdelay=3 bootfile=flash-wedge100 eeprom=y ethact=ethernet@1e680000 fdtcontroladdr=4f69c4e0 gatewayip=100.96.192.129 initrd_high=a0000000 ipaddr=100.96.192.201 netmask=255.255.255.128 spi_dma=no stderr=serial stdin=serial stdout=serial updatefile=flash-wedge100.fit verify=no Environment size: 366/131068 bytes Wedge-boot=> reset resetting ... DRAM Init-DDR3 CBR0-1234567012345670123456701234567 CBR134Done U-Boot 2019.04 wedge100-50a5f79ee527 (Nov 03 2021 - 04:35:37 +0000) Model: Facebook Wedge100 DRAM: 248 MiB Watchdog: 300s MMC: Loading Environment from SPI Flash... SF: Detected mx25l25635e with page size 256 Bytes, erase size 64 KiB, total 32 MiB OK In: serial Out: serial Err: serial H/W: AST2400 series chip Rev. 01 Net: Warning: ethernet@1e680000 (eth0) using random MAC address - 52:50:93:93:ae:f7 eth0: ethernet@1e680000 autoboot in 3 seconds (stop with 'Delete' key)... ## Loading kernel from FIT Image at 20080000 ... .... dhcp6-2620-10d-c0b9-c14-0-0-0-136.dhcp.thefacebook.com login: root Password: Last login: Tue Nov 2 21:53:53 -0700 2021 on /dev/ttyS2. root@dhcp6-2620-10d-c0b9-c14-0-0-0-136:~# fw_printenv baudrate=9600 bootargs=console=ttyS2,9600n8 root=/dev/ram rw bootcmd=bootm 20080000; bootdelay=3 bootfile=flash-wedge100 eeprom=y ethact=ethernet@1e680000 fdtcontroladdr=4f69c4e0 gatewayip=100.96.192.129 initrd_high=a0000000 ipaddr=100.96.192.201 netmask=255.255.255.128 spi_dma=no stderr=serial stdin=serial stdout=serial updatefile=flash-wedge100.fit verify=no ethaddr=8C:EA:1B:4E:39:36 ``` * test dualboot remove wdt2 auto stop in pre-cli command ``` diff --git a/meta-aspeed/recipes-bsp/u-boot/files/u-boot-v2019.04/include/configs/facebook_common_v0.h b/meta-aspeed/recipes-bsp/u-boot/files/u-boot-v2019.04/include/configs/facebook_common_v0.h index 2e5fcc4634d7..d0d5b5d4f4bf 100644 --- a/meta-aspeed/recipes-bsp/u-boot/files/u-boot-v2019.04/include/configs/facebook_common_v0.h +++ b/meta-aspeed/recipes-bsp/u-boot/files/u-boot-v2019.04/include/configs/facebook_common_v0.h @@ -180,7 +180,7 @@ # if defined(CONFIG_ASPEED_AST2600) /* stop fmcwdt2 */ # define CONFIG_PRECLICOMMAND "echo stop fmcwdt2; mw 1e620064 0; " # else /* stop wdt2 */ -# define CONFIG_PRECLICOMMAND "echo stop wdt2; mw 1e78502c 0; " +# define CONFIG_PRECLICOMMAND "echo test dualboot; " # endif #else /* stop wdt1 */ # if defined(CONFIG_CMD_VBS) ``` stop in u-boot command line and let it trigger dual boot after watchdog timeout, and successfully boot into alterbmc. ``` U-Boot 2019.04 wedge100-50a5f79ee527-dirty (Nov 03 2021 - 22:12:04 +0000) Model: Facebook Wedge100 DRAM: 248 MiB Watchdog: 300s MMC: Loading Environment from SPI Flash... SF: Detected mx25l25635e with page size 256 Bytes, erase size 64 KiB, total 32 MiB OK In: serial Out: serial Err: serial H/W: AST2400 series chip Rev. 01 Net: eth0: ethernet@1e680000 autoboot in 3 seconds (stop with 'Delete' key)... test dualboot Wedge-boot=> md 1e785000 20 1e785000: 03ef1480 03ef1480 00000000 00000010 ................ 1e785010: 00001700 00000000 000000ff 00000000 ................ 1e785020: 111165ea 11e1a300 00000000 000000b3 .e.............. 1e785030: 00000600 00000000 000000ff 00000000 ................ 1e785040: 03ef1480 03ef1480 00000000 00000010 ................ 1e785050: 00001700 00000000 000000ff 00000000 ................ 1e785060: 110d2529 11e1a300 00000000 000000b3 )%.............. 1e785070: 00000600 00000000 000000ff 00000000 ................ Wedge-boot=> DRAM Init-DDR3 CBR0-1234567012345670123456701234567 CBR134Done U-Boot 2016.07 wedge100-v2021.35.0 (Aug 31 2021 - 07:07:28 +0000) DRAM: 248 MiB Dual boot watchdog: 295s Watchdog: 300s Flash: FMC-CS0: flash ID: 1920c2 FMC-CS1: flash ID: 1920c2 64 MiB In: serial Out: serial Err: serial H/W: AST2400 series chip Rev. 01 Net: aspeednic#1 autoboot in 2 seconds (stop with 'Delete' key)... ## Loading kernel from FIT Image at 20080000 ... ... OpenBMC Release wedge100-v2021.35.0 bmc login: [ 165.928354] ftgmac100 1e680000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 166.427523] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 166.837518] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.4088: link becomes ready [ 292.440062] tpm_i2c_infineon 9-0020: 1.2 TPM (device-id 0x1A) [ 292.626182] tpm tpm0: TPM is disabled/deactivated (0x7) [ 292.709662] i2c i2c-9: new_device: Instantiated device tpm_i2c_infineon at 0x20 OpenBMC Release wedge100-v2021.35.0 dhcp6-2620-10d-c0b9-c14-0-0-0-136 login: ``` flash the non-hacked image back ``` root@dhcp6-2620-10d-c0b9-c14-0-0-0-136:~# devmem 0x1e785030 l 0x00000702 root@dhcp6-2620-10d-c0b9-c14-0-0-0-136:~# devmem 0x1e785034 l 1 root@dhcp6-2620-10d-c0b9-c14-0-0-0-136:~# strings /dev/mtd0 | grep 'U-Boot 20' U-Boot 2019.04 wedge100-50a5f79ee527-dirty (Nov 03 2021 - 22:12:04 +0000) root@dhcp6-2620-10d-c0b9-c14-0-0-0-136:~# flashcp -v /tmp/u-boot.bin /dev/mtd0 Erasing block: 6/6 (100%) Writing kb: 337/337 (100%) Verifying kb: 337/337 (100%) root@dhcp6-2620-10d-c0b9-c14-0-0-0-136:~# strings /dev/mtd0 | grep 'U-Boot 20' U-Boot 2019.04 wedge100-50a5f79ee527 (Nov 03 2021 - 04:35:37 +0000) root@dhcp6-2620-10d-c0b9-c14-0-0-0-136:~# reboot Connection to 2620:10d:c0b9:c14:8eea:1bff:fe4e:3936 closed by remote host. Connection to 2620:10d:c0b9:c14:8eea:1bff:fe4e:3936 closed. ``` Reviewed By: tao-ren fbshipit-source-id: 15efdd9156

Summary: With this diff land, the wedge100 platform will upgrade the u-boot to v2019.04 Test Plan: Test following, detail test log refer to D32050665 * bootup, successfully boot up and after boot up can access to the device remotely. * uboot env, change uboot env in uboot and check after boot into openbmc, and vice versa. * network, setup the ip and ping. * test dualboot: * build a test u-boot: remove wdt2 auto stop in pre-cli command * stop in u-boot command line and let it trigger dual boot and boot into alterbmc * after dual boot, login to the system, clear dualboot flag, and restore the u-boot , reboot to successfully boot into main image Reviewed By: tao-ren fbshipit-source-id: 1e08c9687e

Summary: all plaforms now are running logrotate hourly instead of daily, using the cron.daily job script. this commit does not change the behavior, but put the logrotate job in corn.hourly to avoid confusing. Test Plan: All build and check the build script and final rootfs ``` [~l/workspaces/openbmc/build-fbgc/tmp/work/grandcanyon-fb-linux-gnueabi/grandcanyon-image/1.0-r0] tree rootfs/etc/cron* rootfs/etc/cron.daily └── biosfwimages-cleanup.sh rootfs/etc/cron.hourly └── logrotate 0 directories, 2 files [~/workspaces/openbmc/build-fbgc/tmp/work/grandcanyon-fb-linux-gnueabi/grandcanyon-image/1.0-r0] cat rootfs/etc/init.d/setup_crond.sh #!/bin/sh # # Copyright 2015-present Facebook. All Rights Reserved. # # This program file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the # Free Software Foundation; version 2 of the License. # # This program is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License # for more details. # # You should have received a copy of the GNU General Public License # along with this program in a file named COPYING; if not, write to the # Free Software Foundation, Inc., # 51 Franklin Street, Fifth Floor, # Boston, MA 02110-1301 USA # ### BEGIN INIT INFO # Provides: setup-crond # Required-Start: # Required-Stop: # Default-Start: S # Default-Stop: # Short-Description: Setup crond history buffering ### END INIT INFO # TODO: check for the if slot/server is present before starting the daemon echo -n "Setup crond..." mkdir /etc/cron mkdir /etc/cron/crontabs echo "0 * * * * run-parts /etc/cron.hourly" > /etc/cron/crontabs/root echo "0 0 * * * run-parts /etc/cron.daily" >> /etc/cron/crontabs/root /etc/init.d/busybox-cron start echo "done." ``` Reviewed By: peterdelevoryas fbshipit-source-id: 55a1d7aa0e

Summary: Use the common busybox config, as common busybox config just add more features as lightning. Use the common crond setup which is the same as lightning local version. Only keep the hwclock.sh which patched to use RTC1 for time sync. Test Plan: Build for lightning. Reviewed By: peterdelevoryas fbshipit-source-id: 6b534ef61a

Summary : add agc032a board layer into meta-delta layer

merge with facebook

Merge

…o pr_delta

Pr delta new

Pr delta

…elta

Using old files merge with FB again.

Update to FB commit

Update with facebook/helium

Update

Sync with FB per day [2022/2/17]

Update

Update per day

Update with helium

Update.

Update

Update at 02/25 10:53 a.m.

Update at 02/25 12:21 a.m.

Sync 2022/03/01 9:00 a.m.

At 2022/03/02 11:00 a.m.

At 2022/03/03 9:00 a.m.

… fru info & command

At 20220304 9:30 a.m.

… fru info & command

At 20220304 2:00 p.m.

At 20220304 2:30 p.m.

At 20220307 9:00 a.m.

At 0311 9:00 a.m.

At 0314 9:00 a.m.

At 0316 11:30 a.m.

At 3/17 9:00 a.m.

At 0318 9:00 a.m.

At 0321 2:00 p.m.

At 9:00 a.m.

At 11:20 a.m. May 5 2022

Commits on Feb 11, 2022

original files

charleenee committed Feb 11, 2022

Configuration menu

View commit details

Copy full SHA for 495d46f

Browse repository at this point

Copy the full SHA

495d46f View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Delta: add agc032a openBMC build #165

Delta: add agc032a openBMC build #165

Commits on Nov 9, 2021

Commits on Nov 11, 2021

Commits on Jan 26, 2022

Commits on Feb 7, 2022

Commits on Feb 8, 2022

Commits on Feb 9, 2022

Commits on Feb 11, 2022

Commits on Feb 14, 2022

Commits on Feb 15, 2022

Commits on Feb 16, 2022

Commits on Feb 17, 2022

Commits on Feb 18, 2022

Commits on Feb 21, 2022

Commits on Feb 22, 2022

Commits on Feb 23, 2022

Commits on Feb 24, 2022

Commits on Feb 25, 2022

Commits on Mar 1, 2022

Commits on Mar 2, 2022

Commits on Mar 3, 2022

Commits on Mar 4, 2022

Commits on Mar 7, 2022

Commits on Mar 11, 2022

Commits on Mar 14, 2022

Commits on Mar 16, 2022

Commits on Mar 17, 2022

Commits on Mar 18, 2022

Commits on Mar 21, 2022

Commits on Mar 23, 2022

Commits on May 5, 2022

Commits on May 6, 2022

Delta: add agc032a openBMC build #165

Are you sure you want to change the base?

Delta: add agc032a openBMC build #165

Commits on Nov 9, 2021

Commits on Nov 11, 2021

Commits on Jan 26, 2022

Commits on Feb 7, 2022

Commits on Feb 8, 2022

Commits on Feb 9, 2022

Commits on Feb 11, 2022

Commits on Feb 14, 2022

Commits on Feb 15, 2022

Commits on Feb 16, 2022

Commits on Feb 17, 2022

Commits on Feb 18, 2022

Commits on Feb 21, 2022

Commits on Feb 22, 2022

Commits on Feb 23, 2022

Commits on Feb 24, 2022

Commits on Feb 25, 2022

Commits on Mar 1, 2022

Commits on Mar 2, 2022

Commits on Mar 3, 2022

Commits on Mar 4, 2022

Commits on Mar 7, 2022

Commits on Mar 11, 2022

Commits on Mar 14, 2022

Commits on Mar 16, 2022

Commits on Mar 17, 2022

Commits on Mar 18, 2022

Commits on Mar 21, 2022

Commits on Mar 23, 2022

Commits on May 5, 2022

Commits on May 6, 2022