From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, david.graham@intel.com
Subject: Re: [Bugme-new] [Bug 14147] New: System unresponsive if I unplug network cable while ethtool -p is running
Date: Fri, 11 Sep 2009 12:55:46 -0700 [thread overview]
Message-ID: <20090911125546.52185035.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-14147-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Wed, 9 Sep 2009 00:06:10 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14147
>
> Summary: System unresponsive if I unplug network cable while
> ethtool -p is running
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.30
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: david.graham@intel.com
> Regression: No
>
>
> When a user runs the "ethtool -p ethX" to identify the physical interface by
> flashing the appropriate interface LED, and then removes the cable at that
> interface, the keyboard locks up. This is naturally annoying to customers with
> multi-port systems, who wish to use ethtool -p so that they can
> disconnect/connect interface cables to appropriate ports.
>
> I am told that this is because "the RTNL lock is held by ethtool, and the link
> [down] message needs the RTNL", which would, I think, make this a kernel issue.
>
> This has been known about within INTEL for over 3 years, but only recently come
> to my attention. I have verified it on a 2.6.30 system using a default kernel
> configuration and the e1000e driver.
>
hah. cute.
parent reply other threads:[~2009-09-11 19:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-14147-10286@http.bugzilla.kernel.org/>]
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=20090911125546.52185035.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=david.graham@intel.com \
--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).