<div class="gmail_quote">On Sun, Feb 24, 2013 at 8:38 AM, Neil Salstrom <span dir="ltr"><<a href="mailto:salstrom@gmail.com" target="_blank">salstrom@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sat, Feb 23, 2013 at 9:56 PM, Karl Newman <<a href="mailto:newmank1@asme.org">newmank1@asme.org</a>> wrote:<br>
><br>
> Since you're set up to compile and use your own kernel, you might try a<br>
> bisect to find the offending commit. Here's the documentation:<br>
> <a href="http://www.kernel.org/pub//software/scm/git/docs/git-bisect.html" target="_blank">http://www.kernel.org/pub//software/scm/git/docs/git-bisect.html</a> In your<br>
> case you should start with the first 3.6.0 kernel and the first "bad" 3.7<br>
> kernel (3.7.0?). Based on my limited knowledge about kernel development<br>
> practices, I believe that will minimize the number of commits between the<br>
> good and bad trees. Ideally you would find a bad commit which could be<br>
> reported upstream to the linux kernel list, but if they don't confirm it as<br>
> a bug, at the least you could create a reverse patch that you could apply<br>
> which would remove the problematic commit for your custom kernel and then<br>
> the mythtv devs could look at it on their end. I've done this once and it<br>
> took about 12 iterations to find the commit which caused my problem (not<br>
> mythtv related).<br>
><br>
> Karl<br>
><br>
<br>
Wow... That's crazy. I had no idea git-bisect was a thing. Giving<br>
it a go now!!!!<br>
<br>
Do I need to do a kpkg-clean between compiles?<br>
<br>
First iteration was "bad". On to iteration number two....<br></blockquote><div><br>Yeah, git has all kinds of handy functions. I don't know about kpkg-clean (I use gentoo) but I doubt it. I think you just need to make sure you install the modules for each iteration with 'make modules_install' (usually I'll build the kernel and install modules in one line like: 'make && make modules_install').<br>
<br>Karl<br></div></div>