From: kbuild test robot <lkp@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
dri-devel@lists.freedesktop.org
Subject: [drm-tip:drm-tip 144/320] debug.c:undefined reference to `save_stack_trace'
Date: Tue, 4 Sep 2018 23:17:28 +0800 [thread overview]
Message-ID: <20180904151728.GI17047@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
Hi Daniel,
FYI, the error/warning still remains.
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: 1b18cb66428cffa748719cf900b2decac3690029
commit: 7928ca5cc786fdc0269342f1b9e22c2af939b989 [144/320] RFC: debugobjects: capture stack traces at _init() time
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 7928ca5cc786fdc0269342f1b9e22c2af939b989
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=m68k
:::::: branch date: 9 hours ago
:::::: commit date: 3 weeks ago
All errors (new ones prefixed by >>):
kernel/dma/debug.o: In function `dma_entry_alloc':
>> debug.c:(.text+0x11c2): 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'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 46121 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2018-09-04 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180904151728.GI17047@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.org \
/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.