Where to clone kernel from

[Joseph Salisbury]

On 09/02/2015 10:18 AM, Nicholas Skaggs wrote:
> On 09/01/2015 02:05 PM, Colin Law wrote:
>> On 1 September 2015 at 16:38, Colin Law <clanlaw at gmail.com> wrote:
>>> Hi,
>>>
>>> Hopefully this is an appropriate forum to ask this. Am helping to
>>> track down bug https://bugzilla.kernel.org/show_bug.cgi?id=53071 which
>>> exhibits itself on my laptop running Wily.  By installing kernels from
>>> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D I have
>>> determined that it was introduced between 3.19.8-vivid and
>>> 4.0-rc1-vivid.  The plan is to clone the kernel git repo and git
>>> bisect to find the commit.  Since they are labelled vivid I cloned
>>> git://kernel.ubuntu.com/ubuntu/ubuntu-vivid.git (which took a long
>>> time on my 1.5Mb broadband) but the latest tag in there is
>>> 3.19.0-28.30
>>>
>>> Is the right one to use
>>> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily?
>>>
>> That does not contain the tags I am looking for either.  Does anyone
>> know where there is a repository with tags for 3.19.8-vivid and
>> 4.0-rc1-vivid?
>>
>> Colin
>>
>>> Cheers
>>>
>>> Colin Law
> Adding in the kernel team who might be able to help more. Colin, have
> you seen / read https://wiki.ubuntu.com/Kernel/KernelBisection?
>
> If I had to guess, I'd be looking in the mainline tree:
> http://kernel.ubuntu.com/git/ubuntu/linux.git, and the conversion
> table
> http://people.canonical.com/~kernel/info/kernel-version-map.html.
> Really, that wiki should have all the information you need to do the
> bisection.
>
> Thanks for making ubuntu better by tracking this down, and good luck!
>
> Nicholas
>

Hi Colin,

Nicholas is correct with the location of the mainline tree.  You could
also perform the bisect with the Wily tree, but it's usually more
straight forward to use the mainline tree.

One thing to note, 3.19.8 and 4.0-rc1 are not linear tags.  The kernel
forks when 3.19.1 is released as the first 3.19 stable version. 
Mainline then continues along with 4.0-rc1.  This means that you can
only bisect between v3.19 final and v4.0-rc1.  That is as long as you
are sure that 3.19 final does not have the bug and 4.0-rc1 does. 

Did you happen to open a Launchpad bug for this?  If so, can you send
the bug number?  I'd be more than happy to help you perform this
bisect.  I can perform the bisect and build test kernels for you to
test.  You would then just need to report back if the test kernel
exhibits the bug ore not.

Thanks,

Joe