linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: David Rientjes <rientjes@google.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Justin Piszcz <jpiszcz@lucidpixels.com>
Subject: Re: What to do with this message (2.6.30.1) ?
Date: Sun, 19 Jul 2009 15:22:10 +0200	[thread overview]
Message-ID: <20090719152210.b0ec33d7.skraw@ithnet.com> (raw)
In-Reply-To: <20090718122311.9955e912.skraw@ithnet.com>

On Sat, 18 Jul 2009 12:23:11 +0200
Stephan von Krawczynski <skraw@ithnet.com> wrote:

> On Wed, 15 Jul 2009 13:24:08 -0700 (PDT)
> David Rientjes <rientjes@google.com> wrote:
> 
> > On Wed, 15 Jul 2009, Stephan von Krawczynski wrote:
> > 
> > > > If you have some additional time, it would also be helpful to get a 
> > > > bisection of when the problem started occurring (it appears to be sometime 
> > > > between 2.6.29 and 2.6.30).
> > > 
> > > Do you know what version should definitely be not affected? I can check one
> > > kernel version per day, can you name a list which versions to check out? 
> > > 
> > 
> > To my knowledge, this issue was never reported on 2.6.29, so that should 
> > be a sane starting point.
> 
> Todays' news is that 2.6.29.4 has exactly the same problem. I was able to
> reproduce it. Tonight I will check out 2.6.28.10.
> 
> -- 
> Regards,
> Stephan

I can reproduce the problem with 2.6.28.10.
Next in line is 2.6.27.26.
In the meantime I do believe that the problem really lies inside the e1000e
driver and not the surrounding kernel code.
Any other driver shows this behaviour in the same environment, escpecially
neither e1000 nor tg3.

-- 
Regards,
Stephan

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-07-19 13:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090713134621.124aa18e.skraw@ithnet.com>
2009-07-14  5:40 ` Jesse Brandeburg
2009-07-14  5:53   ` David Rientjes
2009-07-14  9:21     ` Stephan von Krawczynski
2009-07-15  6:47     ` Stephan von Krawczynski
2009-07-15  8:18       ` David Rientjes
2009-07-15  8:31         ` Justin Piszcz
2009-07-15  9:37         ` Stephan von Krawczynski
2009-07-15 20:24           ` David Rientjes
2009-07-16 15:14             ` Justin Piszcz
2009-07-16 16:44               ` What to do with this message (2.6.30.1) ? (happened again) Justin Piszcz
2009-07-18 10:23             ` What to do with this message (2.6.30.1) ? Stephan von Krawczynski
2009-07-19 13:22               ` Stephan von Krawczynski [this message]
2009-07-20 12:15             ` Stephan von Krawczynski
2009-07-21 13:38             ` Stephan von Krawczynski
2009-07-22 11:53             ` Stephan von Krawczynski
2009-07-15  9:46         ` Stephan von Krawczynski
2009-07-15 20:22           ` David Rientjes
2009-07-16 13:19             ` Stephan von Krawczynski
2009-07-17  6:36             ` Stephan von Krawczynski
2009-07-14  9:16   ` Stephan von Krawczynski
2009-07-14 10:14   ` Stephan von Krawczynski

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=20090719152210.b0ec33d7.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=jesse.brandeburg@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --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