From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: kbuild test robot <lkp@intel.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [drm-tip:drm-tip 7/8] debug.c:undefined reference to `save_stack_trace'
Date: Mon, 23 Jul 2018 15:36:15 -0700 [thread overview]
Message-ID: <20180723223615.GB16907@intel.com> (raw)
In-Reply-To: <201807211123.JXxAXvzn%fengguang.wu@intel.com>
On Sat, Jul 21, 2018 at 11:30:27AM +0800, kbuild test robot wrote:
> Hi Rodrigo,
>
> It's probably a bug fix that unveils the link errors.
>
> tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
> head: 20532651221ed29af16e2db0a7ec8b9bd482c994
> commit: 315fade0d9f3edbf2592599056c8defbdd95a3ab [7/8] Merge remote-tracking branch 'drm-intel/topic/core-for-CI' into drm-tip
> config: m68k-allyesconfig (attached as .config)
> compiler: m68k-linux-gnu-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 315fade0d9f3edbf2592599056c8defbdd95a3ab
> # save the attached .config to linux build tree
> GCC_VERSION=7.2.0 make.cross ARCH=m68k
>
> All errors (new ones prefixed by >>):
>
> kernel/dma/debug.o: In function `dma_entry_alloc':
> >> debug.c:(.text+0x11d2): undefined reference to `save_stack_trace'
> kernel/backtracetest.o: In function `backtrace_regression_test':
> >> backtracetest.c:(.text+0xd8): undefined reference to `save_stack_trace'
> mm/slub.o: In function `set_track':
> >> slub.c:(.text+0x12b4): undefined reference to `save_stack_trace'
> fs/btrfs/ref-verify.o: In function `btrfs_ref_tree_mod':
> >> ref-verify.c:(.text+0x92e): undefined reference to `save_stack_trace'
> lib/debugobjects.o: In function `save_stack.isra.0':
> >> debugobjects.c:(.text+0x9f2): undefined reference to `save_stack_trace'
probably this?
commit 3ef9e3d575a2b725e5783fd57192ceb573359a33
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Tue Mar 20 17:02:58 2018 +0100
RFC: debugobjects: capture stack traces at _init() time
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-07-23 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 3:30 [drm-tip:drm-tip 7/8] debug.c:undefined reference to `save_stack_trace' kbuild test robot
2018-07-23 22:36 ` Rodrigo Vivi [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=20180723223615.GB16907@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=lkp@intel.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