From: "Brown, Aaron F" <aaron.f.brown@intel.com>
To: "Avargil, Raanan" <raanan.avargil@intel.com>,
Denis Turischev <denis.turischev@compulab.co.il>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [Intel-wired-lan] e1000e: PHY cann't be initialized correctly on some I218 controllers
Date: Tue, 9 Aug 2016 18:59:04 +0000 [thread overview]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B81F70C7D@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <f9d596bd-226b-0faf-bab1-858823f17ee4@intel.com>
> -----Original Message-----
> From: Avargil, Raanan
> Sent: Tuesday, August 9, 2016 8:11 AM
> To: Denis Turischev <denis.turischev@compulab.co.il>; intel-wired-
> lan@lists.osuosl.org; Brown, Aaron F <aaron.f.brown@intel.com>; Kirsher,
> Jeffrey T <jeffrey.t.kirsher@intel.com>
> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [Intel-wired-lan] e1000e: PHY cann't be initialized correctly on
> some I218 controllers
>
>
>
> On 8/7/2016 11:56, Denis Turischev wrote:
> > Hi Raanan,
> >
> > On 08/04/2016 07:18 PM, Raanan Avargil wrote:
> >> It is hard to determine what is exactly the problem here and what causes
> the -3 error, but this is not the place to perform hw reset and retry to init the
> phy.
> > I agree that may be this is not the correct place for hw reset, can you advice
> about another solution?
> >
> > It works, not only for me, for example it helps here:
> > http://www.linux.org.ru/forum/linux-hardware/10268216
> >
> > Another fact that Windows drivers work fine with the same hw.
> >
> > Denis
> >
>
> Hi Denis,
>
> More suitable place to retry init the device would be in probe function.
> However, we haven't seen initialization issues like this on i218.
>
> Adding Aaron.
>
> @Aaron - have you seen initialization errors on i218 devices?
I have not. But I don't have many systems with i218 so all that means is my systems do not exhibit the problem.
>
> Raanan
WARNING: multiple messages have this Message-ID (diff)
From: Brown, Aaron F <aaron.f.brown@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] e1000e: PHY cann't be initialized correctly on some I218 controllers
Date: Tue, 9 Aug 2016 18:59:04 +0000 [thread overview]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B81F70C7D@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <f9d596bd-226b-0faf-bab1-858823f17ee4@intel.com>
> -----Original Message-----
> From: Avargil, Raanan
> Sent: Tuesday, August 9, 2016 8:11 AM
> To: Denis Turischev <denis.turischev@compulab.co.il>; intel-wired-
> lan at lists.osuosl.org; Brown, Aaron F <aaron.f.brown@intel.com>; Kirsher,
> Jeffrey T <jeffrey.t.kirsher@intel.com>
> Cc: netdev at vger.kernel.org; linux-kernel at vger.kernel.org
> Subject: Re: [Intel-wired-lan] e1000e: PHY cann't be initialized correctly on
> some I218 controllers
>
>
>
> On 8/7/2016 11:56, Denis Turischev wrote:
> > Hi Raanan,
> >
> > On 08/04/2016 07:18 PM, Raanan Avargil wrote:
> >> It is hard to determine what is exactly the problem here and what causes
> the -3 error, but this is not the place to perform hw reset and retry to init the
> phy.
> > I agree that may be this is not the correct place for hw reset, can you advice
> about another solution?
> >
> > It works, not only for me, for example it helps here:
> > http://www.linux.org.ru/forum/linux-hardware/10268216
> >
> > Another fact that Windows drivers work fine with the same hw.
> >
> > Denis
> >
>
> Hi Denis,
>
> More suitable place to retry init the device would be in probe function.
> However, we haven't seen initialization issues like this on i218.
>
> Adding Aaron.
>
> @Aaron - have you seen initialization errors on i218 devices?
I have not. But I don't have many systems with i218 so all that means is my systems do not exhibit the problem.
>
> Raanan
next prev parent reply other threads:[~2016-08-09 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 12:28 e1000e: PHY cann't be initialized correctly on some I218 controllers Denis Turischev
2016-08-01 12:28 ` [Intel-wired-lan] " Denis Turischev
2016-08-04 16:18 ` Raanan Avargil
2016-08-04 16:18 ` Raanan Avargil
2016-08-07 8:56 ` Denis Turischev
2016-08-07 8:56 ` Denis Turischev
2016-08-09 15:10 ` Raanan Avargil
2016-08-09 15:10 ` Raanan Avargil
2016-08-09 18:59 ` Brown, Aaron F [this message]
2016-08-09 18:59 ` Brown, Aaron F
2016-08-10 15:00 ` Neftin, Sasha
2016-08-10 15:00 ` Neftin, Sasha
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=309B89C4C689E141A5FF6A0C5FB2118B81F70C7D@ORSMSX101.amr.corp.intel.com \
--to=aaron.f.brown@intel.com \
--cc=denis.turischev@compulab.co.il \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raanan.avargil@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.