From: Auke Kok <auke-jan.h.kok@intel.com>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [E1000-devel] e1000: ethtool -p + cable pull = system wedges hard
Date: Tue, 15 Aug 2006 20:01:41 -0700 [thread overview]
Message-ID: <44E28A95.9080802@intel.com> (raw)
In-Reply-To: <44E26EE7.3000100@intel.com>
Auke Kok wrote:
> Jay Vosburgh wrote:
>> Running both 2.6.17.6 plus the e1000 7.2.7 from sourceforge, or
>> the e1000 in netdev-2.6#upstream (7.1.9-k4).
>>
>> Starting up "ethtool -p ethX" then unplugging the cable
>> connected to the identified port is causing my system to completely
>> freeze; even sysrq is unresponsive. I'm running on a 2-way x86 box,
>> with an 82545GM.
>>
>> Is this by any chance a known problem?
>
> not at all.
One of my brain halves (the third one ;)) poked me and told me that it *is* a
known issue. Not good. Apparently as early as kernel 2.5.50 a change was
introduced that causes this. I am unsure what exactly caused it and I assume it
is generic (other nic's might also suffer). The issue is documented in our
standalone driver documentation. Not sure what to do with this.
Auke
next prev parent reply other threads:[~2006-08-16 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 0:37 e1000: ethtool -p + cable pull = system wedges hard Jay Vosburgh
2006-08-16 1:03 ` Auke Kok
2006-08-16 3:01 ` Auke Kok [this message]
2006-08-16 5:13 ` Jay Vosburgh
-- strict thread matches above, loose matches on Subject: below --
2006-08-16 15:39 [E1000-devel] " Brandeburg, Jesse
2006-08-16 18:33 ` Jay Vosburgh
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=44E28A95.9080802@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=jesse.brandeburg@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 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.