From: Saul Wold <sgw@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] lttng-modules: Update revision to grab last bugfix releases
Date: Thu, 14 Nov 2013 08:09:53 -0800 [thread overview]
Message-ID: <5284F5D1.4010004@linux.intel.com> (raw)
In-Reply-To: <CADkTA4M8GkRVnHr5bW-1=Ff2PSdsYaOo6ROisjZDybnNpom2OA@mail.gmail.com>
On 11/13/2013 07:08 PM, Bruce Ashfield wrote:
> On Wed, Nov 13, 2013 at 8:45 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Wed, Nov 13, 2013 at 7:54 PM, Saul Wold <sgw@linux.intel.com> 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.
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
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
next prev parent reply other threads:[~2013-11-14 16:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 13:31 [PATCH 1/2] lttng-modules: Update revision to grab last bugfix releases Otavio Salvador
2013-11-01 13:31 ` [PATCH 2/2] lttng-modules: Backport fixes to allow use with 3.12 kernels Otavio Salvador
2013-11-13 21:54 ` [PATCH 1/2] lttng-modules: Update revision to grab last bugfix releases Saul Wold
2013-11-14 1:45 ` Otavio Salvador
2013-11-14 3:08 ` Bruce Ashfield
2013-11-14 16:09 ` Saul Wold [this message]
2013-11-14 16:18 ` Bruce Ashfield
2013-11-14 17:15 ` Bruce Ashfield
2013-11-14 17:48 ` Otavio Salvador
2013-11-18 12:25 ` Robert Yang
2013-11-18 14:18 ` Otavio Salvador
2013-11-18 14:50 ` Robert Yang
2013-11-18 15:31 ` Saul Wold
2013-11-18 15:50 ` Otavio Salvador
2013-11-18 15:59 ` Bruce Ashfield
2013-11-19 3:34 ` Robert Yang
2013-11-19 5:18 ` Bruce Ashfield
2013-11-21 3:05 ` Robert Yang
2013-11-21 6:05 ` Bruce Ashfield
2013-11-18 15:56 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5284F5D1.4010004@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.