All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederik Himpe <fhimpe@telenet.be>
To: jeffrey.t.kirsher@intel.com, linux-kernel@vger.kernel.org,
	netdev <netdev@vger.kernel.org>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"e1000-devel@lists.sourceforge.net" 
	<e1000-devel@lists.sourceforge.net>,
	Lucas Nussbaum <lucas@lucas-nussbaum.net>,
	"Ronciak, John" <john.ronciak@intel.com>,
	John Ronciak <john.ronciak@gmail.com>
Subject: Re: [E1000-devel] e1000e: NIC not working, power management issue?
Date: Wed, 21 Sep 2011 22:57:23 +0200	[thread overview]
Message-ID: <1316638644.16838.3.camel@defected> (raw)
In-Reply-To: <1316598051.2182.48.camel@jtkirshe-mobl>

On Wed, 2011-09-21 at 02:40 -0700, Jeff Kirsher wrote:
> On Tue, 2011-09-20 at 12:03 -0700, Frederik Himpe wrote:
> > On Sun, 2011-09-18 at 18:04 +0200, Frederik Himpe wrote:
> > > On Sun, 2011-09-18 at 17:38 +0200, Frederik Himpe wrote:
> > > 
> > > > I also tried some older Debian kernels and 2.6.34-1~experimental.2 is
> > > > working fine, while 2.6.35-1~experimental.3 (and later kernels I tried)
> > > > is broken, so I guess the problem started between 2.6.34 and 2.6.35.
> > > > Maybe I'll try to bisect now...
> > > 
> > > Apparently these old kernels do not build anymore with my recent
> > > toolchain:
> > > 
> > >   AS      arch/x86/kernel/entry_64.o
> > > /tmp/ccksyA7i.s: Assembler messages:
> > > /tmp/ccksyA7i.s: Error: .size expression for do_hypervisor_callback does
> > > not evaluate to a constant
> > > 
> > > So I'm stuck here.
> > 
> > Any further thing we can do to help this problem getting fixed?
> > 
> 
> You noted that the problem started between 2.6.34 and 2.6.35, and that
> you were going to try and bisect to find the "problem" patch.  How is
> that effort coming along?

I cannot successfully build these kernels with my toolchain (see above).

> It also appears that you copied netdev and lkml on the original email,
> but they appear to have been dropped from the CC earlier on in this
> email discussion.  It sounds like it would be prudent to add lkml &
> netdev back on to the email thread with what Jesse & John have suggested
> and seen based on the information provided.  This way the power
> management maintainers are aware of the issue and potentially suggest
> other possible fix(es) that have not already been suggested.

Added these lists again.

To resume what we have found up to now: when runtime PM is activated for
the e1000e NIC, it does not wake up when a cable is plugged or when
ethtool is run. Runtime PM has to be deactivated to get the NIC working
again. Apparently this problem started between 2.6.34 and 2.6.35. 



-- 
Frederik Himpe <fhimpe@telenet.be>


WARNING: multiple messages have this Message-ID (diff)
From: Frederik Himpe <fhimpe@telenet.be>
To: jeffrey.t.kirsher@intel.com, linux-kernel@vger.kernel.org,
	netdev <netdev@vger.kernel.org>
Cc: "e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	Lucas Nussbaum <lucas@lucas-nussbaum.net>,
	"Ronciak, John" <john.ronciak@intel.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	John Ronciak <john.ronciak@gmail.com>
Subject: Re: e1000e: NIC not working, power management issue?
Date: Wed, 21 Sep 2011 22:57:23 +0200	[thread overview]
Message-ID: <1316638644.16838.3.camel@defected> (raw)
In-Reply-To: <1316598051.2182.48.camel@jtkirshe-mobl>

On Wed, 2011-09-21 at 02:40 -0700, Jeff Kirsher wrote:
> On Tue, 2011-09-20 at 12:03 -0700, Frederik Himpe wrote:
> > On Sun, 2011-09-18 at 18:04 +0200, Frederik Himpe wrote:
> > > On Sun, 2011-09-18 at 17:38 +0200, Frederik Himpe wrote:
> > > 
> > > > I also tried some older Debian kernels and 2.6.34-1~experimental.2 is
> > > > working fine, while 2.6.35-1~experimental.3 (and later kernels I tried)
> > > > is broken, so I guess the problem started between 2.6.34 and 2.6.35.
> > > > Maybe I'll try to bisect now...
> > > 
> > > Apparently these old kernels do not build anymore with my recent
> > > toolchain:
> > > 
> > >   AS      arch/x86/kernel/entry_64.o
> > > /tmp/ccksyA7i.s: Assembler messages:
> > > /tmp/ccksyA7i.s: Error: .size expression for do_hypervisor_callback does
> > > not evaluate to a constant
> > > 
> > > So I'm stuck here.
> > 
> > Any further thing we can do to help this problem getting fixed?
> > 
> 
> You noted that the problem started between 2.6.34 and 2.6.35, and that
> you were going to try and bisect to find the "problem" patch.  How is
> that effort coming along?

I cannot successfully build these kernels with my toolchain (see above).

> It also appears that you copied netdev and lkml on the original email,
> but they appear to have been dropped from the CC earlier on in this
> email discussion.  It sounds like it would be prudent to add lkml &
> netdev back on to the email thread with what Jesse & John have suggested
> and seen based on the information provided.  This way the power
> management maintainers are aware of the issue and potentially suggest
> other possible fix(es) that have not already been suggested.

Added these lists again.

To resume what we have found up to now: when runtime PM is activated for
the e1000e NIC, it does not wake up when a cable is plugged or when
ethtool is run. Runtime PM has to be deactivated to get the NIC working
again. Apparently this problem started between 2.6.34 and 2.6.35. 



-- 
Frederik Himpe <fhimpe@telenet.be>


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

  parent reply	other threads:[~2011-09-21 20:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14 13:40 e1000e: NIC not working, power management issue? Lucas Nussbaum
2011-09-14 20:31 ` Frederik Himpe
2011-09-14 20:31   ` Frederik Himpe
2011-09-14 21:14   ` John Ronciak
2011-09-14 21:14     ` John Ronciak
2011-09-15  4:48     ` Lucas Nussbaum
     [not found]       ` <CALWPMBH0LSZV0yM8_24yANmn+AbscoqwiJKUnWnzGsN6hJdrhw@mail.gmail.com>
     [not found]         ` <20110915162354.GA5935@xanadu.blop.info>
     [not found]           ` <D38E8E86660E514AB505863C19C9287C16E92FA6@ORSMSX101.amr.corp.intel.com>
     [not found]             ` <20110915172927.GA9854@xanadu.blop.info>
     [not found]               ` <D38E8E86660E514AB505863C19C9287C16E93015@ORSMSX101.amr.corp.intel.com>
     [not found]                 ` <20110915175004.GA11691@xanadu.blop.info>
     [not found]                   ` <D38E8E86660E514AB505863C19C9287C16E934D4@ORSMSX101.amr.corp.intel.com>
     [not found]                     ` <20110916053808.GA4992@xanadu.blop.info>
     [not found]                       ` <alpine.WNT.2.00.1109161020490.3092@jbrandeb-mobl2.amr.corp.intel.com>
     [not found]                         ` <1316545412.19344.5.camel@defected>
     [not found]                           ` <1316598051.2182.48.camel@jtkirshe-mobl>
2011-09-21 20:57                             ` Frederik Himpe [this message]
2011-09-21 20:57                               ` Frederik Himpe

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=1316638644.16838.3.camel@defected \
    --to=fhimpe@telenet.be \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@gmail.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas@lucas-nussbaum.net \
    --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 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.