From: Eddie James <eajames@linux.ibm.com>
To: sam@mendozajonas.com, peter@pjd.dev, delphine_cc_chiu@wiwynn.com,
Paul Fertser <fercerpav@gmail.com>,
davem@davemloft.net, Jakub Kicinski <kuba@kernel.org>,
Potin Lai <potin.lai.pt@gmail.com>,
pabeni@redhat.com
Cc: netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
eajames@linux.ibm.com
Subject: NCSI incorrect response type to command
Date: Wed, 16 Jul 2025 16:01:28 -0500 [thread overview]
Message-ID: <780b1ce5-dc05-4fd7-8a1c-15b283de0e69@linux.ibm.com> (raw)
Hello all,
I am trying to debug an NCSI issue where the driver ends up with
> eth0: NCSI: No channel found to configure!
during boot and I cannot ping the system. This is AST2600 BMC using
ftgmac100 in NCSI mode to an Intel I210. By adding some debug prints I
found that this happens because the response to the CIS command on
channel 0 never returns or returns the wrong response type. As seen
below, after CIS (packet type 0x0) is sent, a GLS (get link state, 0x8a)
response is seen. Unfortunately I did not print the sequence number. The
BMC gets a few correct responses (though NCSI state machine cannot
handle them since CIS didn't respond) and then no more responses to any
commands, so no channel is found. Has anyone seen similar or have any
suggestions for further debug?
Thanks,
Eddie
[ 21.186332] systemd[1]: Started Network Configuration.
[ 21.201977] 8021q: adding VLAN 0 to HW filter on device eth0
[ 21.209910] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x200 pkg:0
[ 21.219708] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.229468] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.230140] ftgmac100 1e670000.ethernet eth0: NCSI: Handler for
packet type 0x82 returned -19
[ 21.237713] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.255476] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.263680] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.271935] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.280170] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.288441] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x2
[ 21.345826] systemd[1]: Starting Wait for Network to be Configured...
[ 22.314495] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x202 pkg:0
[ 22.323088] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x1
[ 22.331929] ftgmac100 1e670000.ethernet eth0: NCSI: Handler for
packet type 0x81 success
[ 22.341190] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x203 pkg:0
[ 22.363321] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x206 pkg:0
[ 22.372049] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x0
[ 22.380844] ftgmac100 1e670000.ethernet eth0: NCSI: Handler for
packet type 0x8a returned -19
[ 22.394122] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x208 pkg:0
[ 22.402856] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x15
[ 22.412073] ftgmac100 1e670000.ethernet eth0: NCSI: Handler for
packet type 0x95 returned -19
[ 22.422259] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x209 pkg:0
[ 22.430986] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x16
[ 22.440141] ftgmac100 1e670000.ethernet eth0: NCSI: Handler for
packet type 0x96 returned -19
[ 22.449987] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x20a pkg:0
[ 22.458684] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0xa
[ 22.468979] ftgmac100 1e670000.ethernet eth0: NCSI: Handler for
packet type 0x8a returned -19
[ 22.480251] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x206 pkg:0
[ 22.490479] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x0
[ 23.514450] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x208 pkg:0
[ 23.523040] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x15
[ 23.988455] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x50
[ 23.997826] ftgmac100 1e670000.ethernet eth0: NCSI: Handler for
packet type 0xd0 success
[ 24.554418] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x209 pkg:0
[ 24.564436] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x16
[ 25.594426] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x20a pkg:0
[ 25.603126] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0xa
[ 26.634449] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x206 pkg:0
[ 26.643134] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x0
[ 27.674640] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x208 pkg:0
[ 27.683312] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x15
[ 28.714443] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x209 pkg:0
[ 28.724744] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0x16
[ 29.754439] ftgmac100 1e670000.ethernet eth0: NCSI: Probe channel
state:0x20a pkg:0
[ 29.763047] ftgmac100 1e670000.ethernet eth0: NCSI: Command for
packet type 0xa
reply other threads:[~2025-07-16 21:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=780b1ce5-dc05-4fd7-8a1c-15b283de0e69@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=delphine_cc_chiu@wiwynn.com \
--cc=fercerpav@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter@pjd.dev \
--cc=potin.lai.pt@gmail.com \
--cc=sam@mendozajonas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).