On Thu, Nov 14, 2013 at 11:18 AM, Bruce Ashfield <[email protected]> wrote: > On Thu, Nov 14, 2013 at 11:09 AM, Saul Wold <[email protected]> wrote: >> On 11/13/2013 07:08 PM, Bruce Ashfield wrote: >>> >>> On Wed, Nov 13, 2013 at 8:45 PM, Otavio Salvador >>> <[email protected]> wrote: >>>> >>>> On Wed, Nov 13, 2013 at 7:54 PM, Saul Wold <[email protected]> wrote: >>>>> >>>>> On 11/01/2013 06:31 AM, Otavio Salvador wrote: >>>>>> >>>>>> >>>>>> This updates lttng-modules for 2.3.2 and also includes a bugfix >>>>>> imported from 3.4 kernel. The changes included are: >>>>>> >>>>>> 6c26b01 Blacklist Linux kernels 3.10+ >>>>>> b97d469 LTTng trace-clock: shrink kernel blacklist >>>>>> 7d40f8e Version 2.3.1 >>>>>> 2aecb9b Blacklist kernels 3.10.13 and 3.11.2 >>>>>> 4f1217f Version 2.3.2 >>>>>> 92fff0c Import fix from LTSI: 3.4+ RT kernels use >>>>>> CONFIG_PREEMPT_RT_FULL >>>>>> 1874075 lttng-statedump-impl: Fix lttng_list_interrupts for empty >>>>>> implementation >>>>>> >>>>> >>>>> Otavio, >>>>> >>>>> Tried to build this locally and got the following failure with >>>>> genericx86 >>>>> and master: >>>>> >>>>> | CC [M] >>>>> >>>>> /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o >>>>> | In file included from >>>>> >>>>> /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-tracer.h:37:0, >>>>> | from >>>>> >>>>> /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.c:24: >>>>> | >>>>> >>>>> /srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/wrapper/trace-clock.h:40:2: >>>>> error: #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the >>>>> timekeeping subsystem. Fixed by commit >>>>> 7bd36014460f793c19e7d6c94dab67b0afcfcb7f \"timekeeping: Fix HRTICK >>>>> related >>>>> deadlock from ntp lock changes\" in Linux." >>>>> | #error "Linux kernels 3.10 and 3.11 introduce a deadlock in the >>>>> timekeeping subsystem. Fixed by commit >>>>> 7bd36014460f793c19e7d6c94dab67b0afcfcb7f \"timekeeping: Fix HRTICK >>>>> related >>>>> deadlock from ntp lock changes\" in Linux." >>>>> | ^ >>>>> | make[2]: *** >>>>> >>>>> [/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git/lttng-ring-buffer-client-discard.o] >>>>> Error 1 >>>>> | make[1]: *** >>>>> >>>>> [_module_/srv/ssd/sgw/builds/world/tmp/work/genericx86-poky-linux/lttng-modules/2.3.2+gitAUTOINC+1874075076-r0/git] >>>>> Error 2 >>>>> | make[1]: Leaving directory >>>>> `/srv/ssd/sgw/builds/world/tmp/sysroots/genericx86/usr/src/kernel' >>>>> | make: *** [default] Error 2 >>>>> | ERROR: oe_runmake failed >>>>> >>>>> So I am going to hold off on this patch set until you can resolve this. >>>> >>>> >>>> Yes; this is becase the linux-yocto seems to not have been updated to >>>>> >>>>> 3.10.13; so in fact it is failing to build to avoid people to >>>> >>>> trigger the deadlock. >>>> >>>> The change which introduces this in lttng-modules is: >>>> >>>> >>>> http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2aecb9b1cbb63f6c524ad9195d8fd06299ef9296 >>>> >>>> I can update this patch as 2.3.3 has been released and it includes the >>>> 3.12 fixes but please check when linux-yocto will be updated so we can >>>> fix it. >>> >>> >>> Saul: What board are you building ? I've had linux-yocto on 3.10.17 >>> for over a week >>> now. >> >> >> As mentioned above this is for genericx86, so maybe not all the BSPs are >> updated yet. > > Buried in the context, sorry about missing that. > > Yes, I'm about to update the reference boards, but there's a install > error that I'm fixing first, but I'll have the series out by end of day.
I just sent the update for this (cc'd [email protected]), but I haven't seen it loop around. If you didn't get the patch, let me know and I'll try again. Bruce > > Bruce > >> >> Sau! >> >> >>> >>> The meta-yocto-bsps need a SRCREV bump, which I was just about to send >>> out, but the code has been in tree for some time yet, and all the qemu* >>> BSPs are already running at that revision. >>> >>> Bruce >>> >>>> >>>> Regards, >>>> >>>> >>>> -- >>>> Otavio Salvador O.S. Systems >>>> http://www.ossystems.com.br http://code.ossystems.com.br >>>> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 >>>> _______________________________________________ >>>> Openembedded-core mailing list >>>> [email protected] >>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core >>> >>> >>> >>> >> > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
