Re: Where to clone kernel from

[Joseph Salisbury]

On 09/02/2015 11:24 AM, Colin Law wrote:
> On 2 September 2015 at 15:58, Joseph Salisbury
>  wrote:
>> 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  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.
>> ...
>> 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.
> Hi Joe
>
> Thanks for the offer. There was an existing bug
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793 but that
> has become out of date I think so I have opened a new one
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491467
>
> I have determined that the last of the 3.19 kernels is ok but the
> first version in the wily tree that will build using fakeroot
> debian/rules binary-headers binary-generic, which is
>
> commit 636cdd7b2930ca2cdaf90eedd04fdb9fc7a8d5ec
> Author: Stefan Bader 
> Date: Thu Feb 14 09:55:49 2008 -0500
> UBUNTU: SAUCE: (no-up) ubuntu: dm-raid45
>
> does have the problem, so I don't know where to go from there.
>
> Cheers
>
> Colin
Hi Colin,

Thanks for opening the bug.  I'll perform the bisect for you.  I just
update the bug with a couple of kernels to test before starting the bisect.

Thanks,

Joe

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: 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  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




-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Reporting Bugs

[Joseph Salisbury]

On 07/02/2013 01:34 PM, Istimsak Abdulbasir wrote:
> Hi Joe,
>
> When you say "new mainline kernel", are you referring to new kernels
> in the upstream ubuntu branch or kernels released on www.kernel.org
> <http://www.kernel.org>? 
>
> If the bug has been fixed, the fixed package will be available in the
> stable release repos, or, if not, you check how the bug was fixed then
> slowly add it to the stable release trees? So I am clear on this.
> Thanks for responding.
>
> Istimsak Abdulbasir
>
>
> On Tue, Jul 2, 2013 at 11:28 AM, Joseph Salisbury
>  <mailto:joseph.salisb...@canonical.com>> wrote:
>
> Can someone further analyze this paragraph.
>
> "For bugs in the Linux (Ubuntu)
> <https://launchpad.net/ubuntu/+source/linux> package,
> unless the upstream maintainer or kernel developer notes
> otherwise, if a
> new mainline kernel comes out, and you haven't tested with it,
> your report
> is considered Status Incomplete <https://wiki.ubuntu.com/Bugs/Status>
> whether
> or not someone toggled the Status of your report. "
>
> Source: https://help.ubuntu.com/community/ReportingBugs
>
>
> Hi Istimsak,
>
> When a new mainline kernel comes out, we usually ask to have it
> tested.
> The primary purpose of this is to see if the bug has already been
> fixed
> upstream.  If it has been fixed upstream, we check to see if it
> was also
> sent for inclusion in the upstream stable trees.  If it wasn't sent to
> upstream stable, we then figure what exact commit fixed the bug, then
> cherry pick it into the Ubuntu stable kernels.
>
> A bug is also set to Incomplete when the apport logs are not
> included in
> the report.
>
> I'm not sure if this is the information you were looking for.  If not,
> just let me know and I can provide some additional details.
>
> Thanks,
>
> Joe
>
>
When we refer to "new mainline kernel", it is the current upstream
development kernel, which is Linus' tree.  The kernel is compiled and
put into a .deb package whenever a new version comes out.  These kernel
are available for download from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
<http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/>

For example, v3.10 is the current mainline kernel, which can be
downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/


-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Reporting Bugs

[Joseph Salisbury]

On 07/02/2013 11:55 AM, Brian Murray wrote:
> On Tue, Jul 02, 2013 at 11:28:39AM -0400, Joseph Salisbury wrote:
>> Can someone further analyze this paragraph.
>>
>> "For bugs in the Linux (Ubuntu)
>> <https://launchpad.net/ubuntu/+source/linux> package,
>> unless the upstream maintainer or kernel developer notes otherwise, if a
>> new mainline kernel comes out, and you haven't tested with it, your report
>> is considered Status Incomplete <https://wiki.ubuntu.com/Bugs/Status>
>> whether
>> or not someone toggled the Status of your report. "
>>
>> Source: https://help.ubuntu.com/community/ReportingBugs
>>
>>
>> Hi Istimsak,
>>
>> When a new mainline kernel comes out, we usually ask to have it tested. 
>> The primary purpose of this is to see if the bug has already been fixed
>> upstream.  If it has been fixed upstream, we check to see if it was also
>> sent for inclusion in the upstream stable trees.  If it wasn't sent to
>> upstream stable, we then figure what exact commit fixed the bug, then
>> cherry pick it into the Ubuntu stable kernels.
>>
>> A bug is also set to Incomplete when the apport logs are not included in
>> the report.
>>
>> I'm not sure if this is the information you were looking for.  If not,
>> just let me know and I can provide some additional details.
> I also think part of the original statement "your report is considered
> Status Incomplete ... whether or not someone toggled the status of your
> report", is trying to address the fact that Launchpad automatically
> confirms bugs if a bug is made a duplicate of another or if someone
> clicks "affects me too".  Is that right Joe?
>
> --
> Brian Murray
Yes that is correct.

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Reporting Bugs

[Joseph Salisbury]

Can someone further analyze this paragraph.

"For bugs in the Linux (Ubuntu)
 package,
unless the upstream maintainer or kernel developer notes otherwise, if a
new mainline kernel comes out, and you haven't tested with it, your report
is considered Status Incomplete 
whether
or not someone toggled the Status of your report. "

Source: https://help.ubuntu.com/community/ReportingBugs


Hi Istimsak,

When a new mainline kernel comes out, we usually ask to have it tested. 
The primary purpose of this is to see if the bug has already been fixed
upstream.  If it has been fixed upstream, we check to see if it was also
sent for inclusion in the upstream stable trees.  If it wasn't sent to
upstream stable, we then figure what exact commit fixed the bug, then
cherry pick it into the Ubuntu stable kernels.

A bug is also set to Incomplete when the apport logs are not included in
the report.

I'm not sure if this is the information you were looking for.  If not,
just let me know and I can provide some additional details.

Thanks,

Joe


-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality