[lkml]   [2011]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Regression from 2.6.36

Bisecting: 5103 revisions left to test after this (roughly 12 steps)

If i'm right, it will takes 12 reboots. I'm really able to reboot only once per day and NOT during weekend so this will take 2,5 weeks.

What about that 'perf' tool ? Can anyone, please, tell me how exactly should i run it to gather usefull data ?

Thank you.

> Od: "Dave Jones"
> Komu: Greg KH
> Dátum: 17.03.2011 01:53
> Predmet: Re: Regression from 2.6.36
> CC: On Wed, Mar 16, 2011 at 05:15:19PM -0700, Greg Kroah-Hartman wrote:

> > Do you need any other information from me ? I'm able to try other versions or
> > patches but, please, take into account that I have to do this on _production_
> > server (I failed to reproduce it in testing environment). Also, I'm able to try
> > only one kernel per day.
> Ick, one kernel per day might make this a bit difficult, but if there
> was any way you could use 'git bisect' to try to narrow this down to the
> patch that caused this problem, it would be great.
> You can mark 2.6.35 as working and 2.6.36 as bad and git will go from
> there and try to offer you different chances to find the problem.

Comparing the output of a perf profile between the good/bad kernels might
narrow it down faster than a bisect if something obvious sticks out.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2011-03-17 14:33    [W:0.165 / U:2.992 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site