From: Dmitry Vyukov <dvyukov@google.com>
To: Michal Hocko <mhocko@suse.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, Linux-MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [memcg:akpm/kcov 4/4] /tmp/ccMETRHQ.s:35: Error: .err encountered
Date: Mon, 11 Jun 2018 09:25:05 +0200 [thread overview]
Message-ID: <CACT4Y+aDpO2VLATSv5YJeS6gYe7eB_67Lq9hQ64+rs78YE5org@mail.gmail.com> (raw)
In-Reply-To: <20180611070916.GB13364@dhcp22.suse.cz>
On Mon, Jun 11, 2018 at 9:09 AM, Michal Hocko <mhocko@suse.com> wrote:
> On Mon 11-06-18 14:57:10, kbuild test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git akpm/kcov
>> head: 99027ccd1ec1b31fc74d63df2f13945ae44da62a
>> commit: 99027ccd1ec1b31fc74d63df2f13945ae44da62a [4/4] arm: port KCOV to arm
>> config: arm-allmodconfig (attached as .config)
>> compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
>> reproduce:
>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> git checkout 99027ccd1ec1b31fc74d63df2f13945ae44da62a
>> # save the attached .config to linux build tree
>> make.cross ARCH=arm
>>
>> All errors (new ones prefixed by >>):
>>
>> /tmp/ccMETRHQ.s: Assembler messages:
>> >> /tmp/ccMETRHQ.s:35: Error: .err encountered
>> /tmp/ccMETRHQ.s:36: Error: .err encountered
>> /tmp/ccMETRHQ.s:37: Error: .err encountered
>
> Huh, what is this supposed to mean?
I think that Arnd has fixed this with "ARM: disable KCOV for
trusted foundations code" now:
https://patchwork.kernel.org/patch/10434909/
The failure mode he referenced matches reported here.
prev parent reply other threads:[~2018-06-11 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 6:57 [memcg:akpm/kcov 4/4] /tmp/ccMETRHQ.s:35: Error: .err encountered kbuild test robot
2018-06-11 7:09 ` Michal Hocko
2018-06-11 7:25 ` Dmitry Vyukov [this message]
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=CACT4Y+aDpO2VLATSv5YJeS6gYe7eB_67Lq9hQ64+rs78YE5org@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).