From: Shawn Warren <shawn.warren@rackspace.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [BUG]ethtool: NIC blink
Date: Tue, 20 May 2014 14:50:47 +0000 [thread overview]
Message-ID: <CFA0D571.2E331%shawn.warren@rackspace.com> (raw)
In-Reply-To: <1400596740.17377.50.camel@deadeye.wl.decadent.org.uk>
Hello Ben,
Thank you for sharing this link. This sounds about right for what I saw
but I was not checking the network connections to the server looking for
RTNL. Once I have a test server up and confirm this I will respond back.
Thanks,
Shawn Warren
Rackspace hosting
On 5/20/14 9:39 AM, "Ben Hutchings" <ben@decadent.org.uk> wrote:
>[Re-sending with cc to netdev]
>
>On Tue, 2014-05-20 at 12:53 +0000, Shawn Warren wrote:
>> Hello Ben and NetDev,
>>
>>
>> I am curious how exactly the ethtool p flag works when blinking
>> interface lights. I ran into an issue on a DELL R820 with an Intel
>> proc that when I blinked an interface and put ethtool in the
>> background, the load on the server began steadily increasing. I ran
>> the following command to reproduce the issue:
>>
>>
>> # ethtool p eth2 3600 &
>>
>>
>> The load increased until the ethtool process was halted. Is this a
>> known bug/issue?
>
>It's not a bug in the ethtool utility.
>
>Perhaps you have run into the problem explained in
><https://git.kernel.org/linus/68f512f21a64c9b264df6c61a9333e7890faf74b>.
>The load will increase as processes wait (uninterruptibly) to obtain the
>RTNL lock. They will appear as being in D state.
>
>This was fixed in Linux 3.0, but older versions can't practically be
>fixed as it required an incompatible change to the driver API.
>
>Ben.
>
>--
>Ben Hutchings
>Life would be so much easier if we could look at the source code.
prev parent reply other threads:[~2014-05-20 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CFA0BA5E.2E2E6%shawn.warren@rackspace.com>
2014-05-20 14:39 ` [BUG]ethtool: NIC blink Ben Hutchings
2014-05-20 14:50 ` Shawn Warren [this message]
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=CFA0D571.2E331%shawn.warren@rackspace.com \
--to=shawn.warren@rackspace.com \
--cc=ben@decadent.org.uk \
--cc=netdev@vger.kernel.org \
/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).