Eth0 fix missing for meta-fbtp build on Portwell Neptune Board #135
Comments
facebook-github-bot
pushed a commit
that referenced
this issue
Jan 29, 2021
Summary: In `wedge_power.sh reset -s`, we sync and remount the eMMC read-only prior to powercycle. The recent addition of logging to eMMC has created an issue where we fail to remount the eMMC because the device is busy due to the logging. This change stops rsyslogd prior to remounting the eMMC, after logging the powercycle. ## Testing The current output when powercycling looks like this, with 5 failed retries: ``` oot@bmc-oob:/mnt/data1/log# wedge_power.sh reset -s mount: /mnt/data1: mount point is busy. Attempt 1/5 failed with 32, retrying... mount: /mnt/data1: mount point is busy. Attempt 2/5 failed with 32, retrying... mount: /mnt/data1: mount point is busy. Attempt 3/5 failed with 32, retrying... mount: /mnt/data1: mount point is busy. Attempt 4/5 failed with 32, retrying... mount: /mnt/data1: mount point is busy. Retry 5/5 failed with 32, no more retries left Power reset the whole system ... ``` With this fix, the output is now the expected: ``` root@bmc-oob:~# wedge_power.sh reset -s [ 504.442172] EXT4-fs (mmcblk0): re-mounted. Opts: (null) Power reset the whole system ... ``` And the powercycle is logged prior to stopping logging: ``` root@bmc-oob:/mnt/data1/log# grep "Power reset" messages 2021 Jan 12 11:19:08 bmc-oob. user.notice elbert-b61f75f445-dirty: root: Power reset the whole system ... ``` We stress tested this change by powercyling Elbert 150 times and verifying that no remount retries were detected. Pull Request resolved: facebookexternal/openbmc.arista#135 Reviewed By: benwei13 fbshipit-source-id: 8f6b602c7b
|
Hi @twlevin, Apologies if this is not relevant for you anymore, Did you find any fix for this issue ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a Portwell Neptune board that came with fbtp-2168080 loaded on it. When I downloaded the current facebook/openbmc, recompiled for meta-fbtp, and loaded on the board, I get the following error during initialization and no Ethernet.
Configuring network interfaces... [ 27.902809] Found NCSI NW Controller at (0, 0)
[ 30.399163] NCSI error: Unknown Mezz Vendor!
[ 31.059169] NCSI: MAC 00:11:22:33:44:55:
[ 39.559173] Using NCSI Network Controller (0, 0)
The fbtp-2168080 originally on the board has the following text during startup:
eth0 mac fixup
ethaddr= 72:42:FD:E8:BF:7F
use u-boot mac addr
Setup crond...starting Busybox Periodic Command Scheduler: crond... done.
done.
crond[384]: crond (busybox 1.24.1) started, log level 8
Starting mTerm console server...done.
Remove poweroff command from .bash
mTerm_log: mTerm: daemon started
mTerm_log: mTerm: daemon started
INIT: Entering runlevel: 5
Configuring network interfaces... [ 27.330000] bwdbg03 - rtl8211 config aneg
done.
When I contacted Portwell about the issue, I received the following response:
So when we were developing the kit with FB, they built the images for us
Later they had found an issue with Ethernet(NCSI) ports, so made another version to fix it(eth fix)
FB was in charge of the BMC image side development, not sure if they put this on repository as you mentioned
Unfortunately, source code of the image was never release to us
But you may find some resources on the Github forum or post questions for it, or start a new image build
Is anyone in the community aware of this issue and where I might find the fix? Does facebook still support this build and are they aware of this particular fix? I have attached the full boot logs for reference.
originalPortwellBoot.log
NoEthernetErrorBootLog.txt
PortwellEth0Issues.docx
The text was updated successfully, but these errors were encountered: