From: Michael Chan <mchan@broadcom.com>
To: "Sébastien Bocahu" <sbu@reportlinker.com>, harish.patil@qlogic.com
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: Linux kernel commit breaks IPMI on iface downing
Date: Thu, 13 Aug 2015 18:30:34 -0700 [thread overview]
Message-ID: <1439515834.7684.24.camel@LTIRV-MCHAN1.corp.ad.broadcom.com> (raw)
In-Reply-To: <CAJPaPGU2_68J4BZanm+Lw3O+WTiwO3swegh5grP5Bn-XprLOwg@mail.gmail.com>
+netdev and Harish who is the current maintainer of bnx2 at qlogic.
The patch in question effectively just removes the
bnx2_set_power_state() call during "ip link set down". If there is
IPMI, the firmware should know the link needs to stay up when the driver
resets the device during bnx2_close(). This should be a very common
scenario. Please provide the firmware versions to Harish with ethtool
-i. Perhaps upgrading the firmware can resolve this issue.
On Thu, 2015-08-13 at 15:47 +0200, Sébastien Bocahu wrote:
> Hi,
>
> Being unable to install Debian Jessie via IPMI on mainstream Dell R410
> servers that used to be well supported by Debian Wheezy, I tracked the
> problem down to a specific commit in the Linux kernel, specifically in
> the bnx2 driver.
> The issue is that "ip link set eth0 down" takes the Ethernet part of
> the BMC down (shared NIC for BMC+eth0), cutting off the IPMI session.
> The BMC gets back only after power cycling.
>
> Hardware: Dell R410 w/ a Broadcom 5716 NIC:
> Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit
> Ethernet (rev 20) )
> Part number: BCM95716C1
> Vendor specific: 6.4.5 (Firmware has been updated to the latest
> version available by Dell's support website)
>
> I built many kernels to track which change caused the issue and it
> seems that's :
> 25bfb1dd4ba3b2d9a49ce9d9b0cd7be1840e15ed (bnx2: Add pci shutdown handler.)
>
> Before, 'ip link set eth0 down' would just cause 2/3s of packet loss
> but IPMI would still be working afterwards.
>
> I'm available for more informations and/or testing if needed.
>
> Thanks !
>
>
>
next parent reply other threads:[~2015-08-14 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJPaPGU2_68J4BZanm+Lw3O+WTiwO3swegh5grP5Bn-XprLOwg@mail.gmail.com>
2015-08-14 1:30 ` Michael Chan [this message]
2015-08-14 9:22 ` Linux kernel commit breaks IPMI on iface downing Sébastien Bocahu
2015-09-04 7:55 ` Sébastien Bocahu
2015-09-04 8:29 ` Michael Chan
2015-09-09 1:33 ` Harish Patil
2016-08-02 7:58 ` Chen-Yu Tsai
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=1439515834.7684.24.camel@LTIRV-MCHAN1.corp.ad.broadcom.com \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=harish.patil@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=sbu@reportlinker.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.