From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: "Tantilov, Emil S" <emil.s.tantilov@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com>
Subject: Re: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
Date: Mon, 12 Jul 2010 18:56:18 +0300 [thread overview]
Message-ID: <1278950178.17933.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1278323885.5277.0.camel@localhost.localdomain>
On Mon, 2010-07-05 at 12:58 +0300, Maxim Levitsky wrote:
> On Mon, 2010-07-05 at 01:13 -0700, Jeff Kirsher wrote:
> > On Sun, Jul 4, 2010 at 15:48, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> > > Did few guesses, and now I see that reverting the below commit fixes the
> > > problem.
> > >
> > > "e1000e: Fix/cleanup PHY reset code for ICHx/PCHx"
> > > e98cac447cc1cc418dff1d610a5c79c4f2bdec7f.
> > >
> > >
> > > Best regards,
> > > Maxim Levitsky
> > >
> > > --
> >
> > Can you give us till Tuesday to respond? I know that there are some
> > additional e1000e patches in my queue, which may resolve the issue,
> > but this weekend the power is down to do some infrastructure upgrades
> > which prevents us from doing any investigation.debugging until
> > Tuesday.
> >
>
> Sure.
>
> Best regards,
> Maxim Levitsky
>
Updates?
or 2.6.35 will ship with e0000e ? :-)
I really have very little time to help further with that for now.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-07-12 15:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 17:27 [REGRESSION] e1000e stopped working Maxim Levitsky
2010-06-27 17:29 ` Maxim Levitsky
2010-06-27 17:43 ` Maxim Levitsky
2010-06-27 17:47 ` Maxim Levitsky
2010-06-28 17:04 ` Allan, Bruce W
2010-06-28 17:14 ` Maxim Levitsky
2010-06-29 1:09 ` Allan, Bruce W
2010-06-29 10:32 ` Maxim Levitsky
2010-06-29 18:37 ` Tantilov, Emil S
2010-06-30 22:59 ` Maxim Levitsky
2010-07-04 0:41 ` Maxim Levitsky
2010-07-04 22:48 ` [REGRESSION] e1000e stopped working [MANUALLY BISECTED] Maxim Levitsky
2010-07-05 8:13 ` Jeff Kirsher
2010-07-05 9:58 ` Maxim Levitsky
2010-07-12 15:56 ` Maxim Levitsky [this message]
2010-07-12 21:23 ` Tantilov, Emil S
2010-07-13 0:38 ` Maxim Levitsky
2010-07-14 22:56 ` Tantilov, Emil S
2010-07-14 23:33 ` Maxim Levitsky
2010-07-15 18:57 ` Maxim Levitsky
2010-07-15 19:02 ` Tantilov, Emil S
2010-07-15 19:09 ` Maxim Levitsky
2010-07-16 19:25 ` Maxim Levitsky
2010-07-16 23:23 ` Tantilov, Emil S
2010-07-17 13:54 ` Maxim Levitsky
2010-07-26 0:25 ` Maxim Levitsky
2010-07-28 7:04 ` Maxim Levitsky
2010-07-29 1:10 ` Jeff Kirsher
2010-08-01 2:08 ` Jeff Kirsher
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=1278950178.17933.2.camel@localhost.localdomain \
--to=maximlevitsky@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=emil.s.tantilov@intel.com \
--cc=jeffrey.e.pieper@intel.com \
--cc=jeffrey.t.kirsher@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).