Tioga Pass OpenBMC 2.8

[Vijay Khemka]

Hi Bruce,
What NCSI issues you are facing, kernel messages mentioned below are initial log when ncsi configuration completes but it doesn't create any issues in functioning of NCSI. Is your network working? Or are you facing anything with NCSI. You don't need anything for NCSI management if you are just using as network card and not doing any NCSI management from application. Network works perfectly for ipv4 and ipv6 seamlessly since 1 year.

Please let me know actual issues you are facing, I will try to fix it. 

Regards
-Vijay 

On 8/24/20, 2:17 PM, "openbmc on behalf of Bruce Mitchell" <openbmc-bounces+vijaykhemka=fb.com at lists.ozlabs.org on behalf of Bruce_Mitchell at phoenix.com> wrote:

    In addition to what Neil has ask I am find this issue with NC-SI:

    Yet Ben Wei's OSFC 2019 "NIC Management and Monitoring in OpenBMC" 
    leads me to believe that NC-SI should be in my image and functioning.
    Has something changed since Ben's paper?

    root at tiogapass:~#
    root at tiogapass:~# uname -a
    Linux tiogapass 5.4.39-30079d6 #1 Fri Aug 21 17:14:22 UTC 2020 armv6l GNU/Linux
    root at tiogapass:~# cat /proc/version
    Linux version 5.4.39-30079d6 (oe-user at oe-host) (gcc version 9.3.0 (GCC)) #1 Fri Aug 21 17:14:22 UTC 2020
    root at tiogapass:~# cat /proc/sys/kernel/version
    #1 Fri Aug 21 17:14:22 UTC 2020
    root at tiogapass:~# cat /etc/os-release
    ID=openbmc-phosphor
    NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
    VERSION="v00.000.000-45"
    VERSION_ID=v00.000.000-45-g645f5cc08
    PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) v00.000.000-45"
    BUILD_ID="v00.000.000"
    OPENBMC_TARGET_MACHINE="tiogapass"
    root at tiogapass:~# dmesg | grep -i ncsi
    [    1.854939] ftgmac100 1e660000.ethernet: Using NCSI interface
    [   17.831827] ftgmac100 1e660000.ethernet eth0: NCSI: Handler for packet type 0x82 returned -19
    [   33.526950] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.535564] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.543813] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.554345] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.562598] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.570958] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.612936] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.629318] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.638683] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.647978] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.657291] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.665690] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.673956] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.682381] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    [   33.690792] ftgmac100 1e660000.ethernet eth0: NCSI: 'bad' packet ignored for type 0x8b
    root at tiogapass:~#

    From: Neil Bradley 
    Sent: Friday, August 21, 2020 18:36
    To: openbmc at lists.ozlabs.org
    Cc: Bruce Mitchell; Patrick Voelker
    Subject: Tioga Pass OpenBMC 2.8

    Greetings fellow BMC folk ? I’m Neil Bradley, Phoenix Technologies’ BMC architect and have a question for the group.

    We are attempting to load OpenBMC 2.8 on a Tioga Pass. This is what we did:

    mkdir tiogapass
    cd tiogapass
    git clone https://github.com/openbmc/openbmc.git
    cd openbmc
    git checkout 35a774200999ac2fca48693c1c169bf99d2f63ea
    export TEMPLATECONF=meta-facebook/meta-tiogapass/conf
    source openbmc-env
    bitbake obmc-phosphor-image

    The BMC does boot fully, however there are two major problems we’ve encountered:

    1. Host will not power on via the front panel power button
    2. BMC Will not obtain or try DHCP even though its set enabled for the primary LAN channel

    I have a couple of questions:

    1. Was this built/done correctly? In other words, did I do something wrong in this process?
    2. Does anyone know the current state of Tioga Pass support in 2.8 or the general health therein?

    We’re coming up to speed on this quickly, so apologies if these are stupid questions. And greetings!

    →Neil