Messages in this thread | | | Date | Sun, 19 Jul 2009 15:22:10 +0200 | From | Stephan von Krawczynski <> | Subject | Re: What to do with this message (2.6.30.1) ? |
| |
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
| |