* Using linux-yocto_3.10 with dylan
@ 2013-10-23 22:40 Colin Walters
2013-10-23 23:06 ` Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Colin Walters @ 2013-10-23 22:40 UTC (permalink / raw)
To: poky
Hi, I have a system derived from Poky Dylan, it is currently using
linux-yocto-dev.bb. Things were working fine up until recently when
that branch was rebased to 3.12, and the new linux-yocto-3.10 git repo
was made. I had actually been unaware up until then that I was tracking
a git branch instead of a fixed revision.
Anyways, I'm trying now to continue using 3.10 with Dylan, but I'll be
honest - the way the linux-yocto kernel has the configuation built and
patches are applied is convoluted enough I'm having a lot of trouble
figuring out what's going wrong. The error looks like this in do_patch:
DEBUG: Executing shell function do_patch
Deleted branch meta-temp (was f58e62b).
[INFO] validating against known patches (qemux86-64-standard-meta)
... snip progress bar ...
error: patch failed: arch/arm/mm/fault.c:448
error: arch/arm/mm/fault.c: patch does not apply
To force apply this patch, use 'guilt push -f'
[ERROR] unable to complete push
pending patches are:
links/kernel-cache/arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch
links/kernel-cache/arch/arm/arm-ARM-EABI-socketcall.patch
links/kernel-cache/arch/mips/malta-uhci-quirks-make-allowance-for-slow-4k-e-c.patch
links/kernel-cache/arch/mips/4kc-cache-tlb-hazard-tlbp-cache-coherency.patch
... continued
I've verified I can take current oe-core git master, change the kernel
to 3.10, and it builds OK. The main variation is I have a small set of
config additions, but I don't know why this would result in the set of
patches changing. Is there an way I can see which patches are being
applied and why?
At the moment I'm trying to isolate what configuration change is causing
this, but hopefully someone here will have a useful hint. Thanks!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using linux-yocto_3.10 with dylan
2013-10-23 22:40 Using linux-yocto_3.10 with dylan Colin Walters
@ 2013-10-23 23:06 ` Bruce Ashfield
2013-10-23 23:17 ` Colin Walters
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Ashfield @ 2013-10-23 23:06 UTC (permalink / raw)
To: Colin Walters; +Cc: poky@yoctoproject.org
On Wed, Oct 23, 2013 at 6:40 PM, Colin Walters <walters@verbum.org> wrote:
> Hi, I have a system derived from Poky Dylan, it is currently using
> linux-yocto-dev.bb. Things were working fine up until recently when
> that branch was rebased to 3.12, and the new linux-yocto-3.10 git repo
> was made. I had actually been unaware up until then that I was tracking
> a git branch instead of a fixed revision.
>
> Anyways, I'm trying now to continue using 3.10 with Dylan, but I'll be
> honest - the way the linux-yocto kernel has the configuation built and
> patches are applied is convoluted enough I'm having a lot of trouble
> figuring out what's going wrong. The error looks like this in do_patch:
>
> DEBUG: Executing shell function do_patch
> Deleted branch meta-temp (was f58e62b).
> [INFO] validating against known patches (qemux86-64-standard-meta)
>
> ... snip progress bar ...
>
> error: patch failed: arch/arm/mm/fault.c:448
> error: arch/arm/mm/fault.c: patch does not apply
> To force apply this patch, use 'guilt push -f'
> [ERROR] unable to complete push
> pending patches are:
> links/kernel-cache/arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch
> links/kernel-cache/arch/arm/arm-ARM-EABI-socketcall.patch
> links/kernel-cache/arch/mips/malta-uhci-quirks-make-allowance-for-slow-4k-e-c.patch
> links/kernel-cache/arch/mips/4kc-cache-tlb-hazard-tlbp-cache-coherency.patch
> ... continued
>
> I've verified I can take current oe-core git master, change the kernel
> to 3.10, and it builds OK. The main variation is I have a small set of
> config additions, but I don't know why this would result in the set of
> patches changing. Is there an way I can see which patches are being
> applied and why?
>
> At the moment I'm trying to isolate what configuration change is causing
> this, but hopefully someone here will have a useful hint. Thanks!
It's the kernel tools. You need to bring back the matched tools -> the new 3.10
kernel tree, since they no longer use guilt to manage patches on branches, but
instead use pure git. The guilt tools can't detect that the patches are in fact
already applied to the tree, and try to push changes again, which lead to your
error.
Bruce
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using linux-yocto_3.10 with dylan
2013-10-23 23:06 ` Bruce Ashfield
@ 2013-10-23 23:17 ` Colin Walters
2013-10-23 23:19 ` Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Colin Walters @ 2013-10-23 23:17 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: poky@yoctoproject.org
On Wed, 2013-10-23 at 19:06 -0400, Bruce Ashfield wrote:
> It's the kernel tools. You need to bring back the matched tools -> the new 3.10
> kernel tree, since they no longer use guilt to manage patches on branches, but
> instead use pure git. The guilt tools can't detect that the patches are in fact
> already applied to the tree, and try to push changes again, which lead to your
> error.
Ah hah! Yep, after a quick copy of kern-tools.bb from oe-core master
and a "bitbake kern-tools-native", looks like "bitbake linux-yocto" is
past do_patch and onto do_compile now. I should have posted a few hours
earlier before I was knee deep in debugging prints and generated shell
scripts...
Thank you!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using linux-yocto_3.10 with dylan
2013-10-23 23:17 ` Colin Walters
@ 2013-10-23 23:19 ` Bruce Ashfield
0 siblings, 0 replies; 4+ messages in thread
From: Bruce Ashfield @ 2013-10-23 23:19 UTC (permalink / raw)
To: Colin Walters, Bruce Ashfield; +Cc: poky@yoctoproject.org
On 13-10-23 07:17 PM, Colin Walters wrote:
> On Wed, 2013-10-23 at 19:06 -0400, Bruce Ashfield wrote:
>
>> It's the kernel tools. You need to bring back the matched tools -> the new 3.10
>> kernel tree, since they no longer use guilt to manage patches on branches, but
>> instead use pure git. The guilt tools can't detect that the patches are in fact
>> already applied to the tree, and try to push changes again, which lead to your
>> error.
>
> Ah hah! Yep, after a quick copy of kern-tools.bb from oe-core master
> and a "bitbake kern-tools-native", looks like "bitbake linux-yocto" is
> past do_patch and onto do_compile now. I should have posted a few hours
> earlier before I was knee deep in debugging prints and generated shell
> scripts...
:( sorry about that. The tools are always backwards compatible, but the
newest
kernel always needs the newest tools.
I have a solution to this, and can finally bring it into play in yocto
1.6, where the copy of the tools in the kernel tree is actively used,
which means a tree always carries the tools that it needs .. and no more
issues like you ran into.
Bruce
>
> Thank you!
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-10-23 23:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-23 22:40 Using linux-yocto_3.10 with dylan Colin Walters
2013-10-23 23:06 ` Bruce Ashfield
2013-10-23 23:17 ` Colin Walters
2013-10-23 23:19 ` Bruce Ashfield
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.