From: Auke Kok <auke-jan.h.kok@intel.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: e1000: ethtool -p + cable pull = system wedges hard
Date: Tue, 15 Aug 2006 18:03:35 -0700 [thread overview]
Message-ID: <44E26EE7.3000100@intel.com> (raw)
In-Reply-To: <200608160037.k7G0btZt002839@death.nxdomain.ibm.com>
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.
Can you include the output of `lspci -vv` and `ethtool -e ethX` ? We'll have to
go try to reproduce this.
It is certainly not a good thing that it hangs when you try to identify the
port and unplug the cable, that should certainly work :)
Cheers,
Auke
next prev parent reply other threads:[~2006-08-16 1:05 UTC|newest]
Thread overview: 4+ 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 [this message]
2006-08-16 3:01 ` [E1000-devel] " Auke Kok
2006-08-16 5:13 ` 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=44E26EE7.3000100@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 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).