From: "Graham, David" <david.graham@intel.com>
To: Karol Lewandowski <karol.k.lewandowski@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [BUG 2.6.30+] e100 sometimes causes oops during resume
Date: Wed, 16 Sep 2009 14:06:55 -0700 [thread overview]
Message-ID: <4AB1536F.9070205@intel.com> (raw)
In-Reply-To: <20090916014448.GA1070@bizet.domek.prywatny>
Karol Lewandowski wrote:
>
> I can test, or rather -- start testing this tommorow, if this makes
> sense to you.
>
Yes please Karol, test with 6905b1f1...removed. I will continue testing
here too on 2.6.31, though I have not had a repro yet. And are you
performing a standby or hibernate, I want to be sure that I'm resuming
from the same state.
Thanks.
> Thanks.
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
next prev parent reply other threads:[~2009-09-16 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090915120538.GA26806@bizet.domek.prywatny>
2009-09-15 22:54 ` [BUG 2.6.30+] e100 sometimes causes oops during resume Graham, David
2009-09-16 1:44 ` [E1000-devel] " Karol Lewandowski
2009-09-16 9:19 ` Karol Lewandowski
2009-09-16 21:06 ` Graham, David [this message]
2009-09-16 21:17 ` Karol Lewandowski
2009-09-16 23:11 ` Rafael J. Wysocki
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=4AB1536F.9070205@intel.com \
--to=david.graham@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=karol.k.lewandowski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).