netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@gmail.com>,
	e1000-devel@lists.sourceforge.net, jgarzik@pobox.com,
	netdev@vger.kernel.org
Subject: Re: [1/5] 2.6.21-rc5: known regressions
Date: Fri, 30 Mar 2007 20:04:44 +0200	[thread overview]
Message-ID: <20070330180444.GH14134@stusta.de> (raw)
In-Reply-To: <460AB9E8.8070803@intel.com>

On Wed, Mar 28, 2007 at 11:54:32AM -0700, Kok, Auke wrote:
> Adrian Bunk wrote:
> >Subject    : e1000 resume weirdness
> >References : http://lkml.org/lkml/2007/3/26/91
> >Submitter  : Ingo Molnar <mingo@elte.hu>
> >Handled-By : Jesse Brandeburg <jesse.brandeburg@gmail.com>
> >             Auke Kok <auke-jan.h.kok@intel.com>
> >Status     : problem is being debugged
> 
> The issue comes from a corner case and the underlying problem is that e1000 
> isn't stopping tx properly. We have a fix for this pending in our tree that 
> I'll push upstream for 2.6.22 to Jeff, but I don't think this should be a 
> blocker and it's probably is not a regression at all, the gap has always 
> been present.
> 
> on a side note, this is probably fixed easily by turning the adapters 
> detect_tx_hung flag off in e1000_down, so if someone spots this reoccurring 
> somewhat regularly, please contact me so we can debug it. I myself have a 
> system suspend/resuming in circles for an hour now with traffic flying 
> across without a single hit on it....
> 
> Adrian, you probably want to drop this issue from your list.

Thanks for the update, dropped as non-regression.

> Cheers,
> 
> 
> Auke

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2007-03-30 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0703251559560.6730@woody.linux-foundation.org>
2007-03-27  1:59 ` [1/5] 2.6.21-rc5: known regressions Adrian Bunk
2007-03-28 18:54   ` Kok, Auke
2007-03-28 19:23     ` Ingo Molnar
2007-03-30 18:04     ` Adrian Bunk [this message]
     [not found] ` <20070327230024.GJ16477@stusta.de>
2007-03-28  0:50   ` 2.6.21-rc5: known regressions with patches Jay Cliburn
2007-03-30 21:32 ` [2/4] 2.6.21-rc5: known regressions (v2) Adrian Bunk
2007-03-30 21:32 ` [3/4] " Adrian Bunk
2007-03-31  2:52   ` Jeff Chua
2007-04-13 16:32   ` Michal Piotrowski

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=20070330180444.GH14134@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@linux-foundation.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jesse.brandeburg@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).