From: Sanjoy Mahajan <sanjoy@MIT.EDU>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
NetDEV list <netdev@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>
Subject: Re: e1000e fails after several S3 resumes (2.6.26 Debian, TP T60)
Date: Tue, 28 Oct 2008 16:18:48 -0400 [thread overview]
Message-ID: <E1Kuv1c-00033M-Ia@approx.mit.edu> (raw)
In-Reply-To: Your message of "Fri, 24 Oct 2008 09:22:58 PDT." <F169D4F5E1F1974DBFAFABF47F60C10A069DFFA0@orsmsx507.amr.corp.intel.com> (sfid-20081024_142044_698098_A035A635)
> I think you should definitely try 2.6.27.y, the e1000e versions in the
> kernel are different than what is in ubuntu at least, so not sure if
> that applies to debian.
I'm running 2.6.27.4, and I haven't seen the e1000e problem yet. But it
happens quite often with wlan0 (iwl3945), whereupon unloading and
loading the module fixes it.
Is there an analogue of ethtool for wireless cards (for debugging and
resetting a la 'ethtool -r eth0'? Other than the tcpdump, what
debugging information should I collect for iwl3945? And who should I
add/remove from the CC before sending it out?
-Sanjoy
`Until lions have their historians, tales of the hunt shall always
glorify the hunters.' --African Proverb
prev parent reply other threads:[~2008-10-28 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 13:28 e1000e fails after several S3 resumes (2.6.26 Debian, TP T60) Sanjoy Mahajan
2008-10-22 16:29 ` Jesse Brandeburg
2008-10-22 19:21 ` Sanjoy Mahajan
2008-10-22 21:15 ` Yves-Alexis Perez
2008-10-23 13:26 ` Sanjoy Mahajan
2008-10-23 22:42 ` Brandeburg, Jesse
2008-10-24 14:24 ` Sanjoy Mahajan
2008-10-24 16:22 ` Brandeburg, Jesse
2008-10-24 19:54 ` Sanjoy Mahajan
2008-10-28 20:18 ` Sanjoy Mahajan [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=E1Kuv1c-00033M-Ia@approx.mit.edu \
--to=sanjoy@mit.edu \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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