From: "Milton Miller II" <miltonm@us.ibm.com>
To: "Thu Nguyen" <thu@amperemail.onmicrosoft.com>,
"openbmc" <openbmc@lists.ozlabs.org>
Subject: Re: NC-SI driver: Detect OCP module power down!
Date: Sun, 3 Jan 2021 16:44:40 +0000 [thread overview]
Message-ID: <OF1171F140.21EF2A71-ON00258652.005BFA8E-1609692280165@notes.na.collabserv.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1381 bytes --]
January 03, 2021 8:45 AM Thu Nguyen wrote and miltonm@us.ibm.com responded:
In our test platform, BMC boot up with NC-SI module is plugged and
powered. NC-SI interface (eth0) is up and worked well.
Then the power of NC-SI module is power off. NC-SI driver can't detect
this state.
BMC console keeps print:
[ 1780.411126] ftgmac100 1e660000.ethernet eth0: NCSI Channel 0 timed out!
[ 1785.579455] ftgmac100 1e660000.ethernet eth0: NCSI: No channel with
link found, configuring channel 0
[ 1802.253375] ftgmac100 1e660000.ethernet eth0: NCSI Channel 0 timed out!
[ 1807.501456] ftgmac100 1e660000.ethernet eth0: NCSI: No channel with
link found, configuring channel 0
Look at the ncs-manager.c code, it seems if a channel of NC-SI module is
time out its' monitor_state will be disabled, the link will be down then
the driver will go to next channel.
But if all of channels of NC-SI module are down. The driver will reset
the monitor_state of all channels and check their states again.
Milton> The NCSI specification explicitly says that power to the nics and the controller must be synchronized.
Do we have any mechanism to detect power off state of NC-SI module?
Milton> No, but the state machines will reset if you ifconfig down the interface.
How about hot plug NC-SI module?
Regards.
Thu Nguyen.
[-- Attachment #1.2: Type: text/html, Size: 1517 bytes --]
next reply other threads:[~2021-01-03 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 16:44 Milton Miller II [this message]
2021-01-05 15:38 ` NC-SI driver: Detect OCP module power down! Thu Nguyen
-- strict thread matches above, loose matches on Subject: below --
2021-01-03 14:43 Thu Nguyen
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=OF1171F140.21EF2A71-ON00258652.005BFA8E-1609692280165@notes.na.collabserv.com \
--to=miltonm@us.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=thu@amperemail.onmicrosoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.