From: "Graham, David" <david.graham@intel.com>
To: Karol Lewandowski <karol.k.lewandowski@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [E1000-devel] [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.
>
next prev parent reply other threads:[~2009-09-16 21:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 12:05 [BUG 2.6.30+] e100 sometimes causes oops during resume Karol Lewandowski
2009-09-15 15:32 ` Karol Lewandowski
2009-09-15 22:54 ` [E1000-devel] " Graham, David
2009-09-16 1:44 ` 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
2009-09-16 23:18 ` Rafael J. Wysocki
2009-09-17 20:42 ` Graham, David
2009-09-17 22:27 ` Rafael J. Wysocki
2009-09-22 23:35 ` Karol Lewandowski
2009-09-22 23:51 ` Rafael J. Wysocki
2009-09-23 14:22 ` Karol Lewandowski
2009-09-23 21:45 ` Rafael J. Wysocki
2009-09-29 13:58 ` Mel Gorman
2009-09-30 15:37 ` Karol Lewandowski
2009-09-30 15:55 ` Mel Gorman
2009-09-30 18:48 ` Karol Lewandowski
2009-09-17 23:05 ` Karol Lewandowski
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