From: Philip Li <philip.li@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: kernel test robot <lkp@intel.com>, LKP <lkp@lists.01.org>,
linaro-mm-sig@lists.linaro.org, dri-devel@lists.freedesktop.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2989f64510 ("dma-buf: Add selftests for dma-fence"): WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:524 __debug_object_init
Date: Wed, 27 Nov 2019 15:30:54 +0800 [thread overview]
Message-ID: <20191127073054.GG30842@intel.com> (raw)
In-Reply-To: <20191122013244.GC313@intel.com>
On Fri, Nov 22, 2019 at 09:32:45AM +0800, Philip Li wrote:
> On Thu, Nov 21, 2019 at 07:26:05AM +0000, Chris Wilson wrote:
> > Quoting kernel test robot (2019-11-21 07:19:43)
> > > Greetings,
> > >
> > > 0day kernel testing robot got the below dmesg and the first bad commit is
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > >
> > > commit 2989f6451084aed3f8cc9992477f7a9bf57a3716
> > > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > > AuthorDate: Mon Aug 19 10:59:27 2019 +0100
> > > Commit: Chris Wilson <chris@chris-wilson.co.uk>
> > > CommitDate: Mon Aug 19 18:09:46 2019 +0100
> >
> > That's a belated report, fixed by
> Hi Chris, thanks for the feedback, we will double check this report and
> provide update later.
Hi Chris, it is confirmed that this report is false positive. 6ac3a0e had
fixed the issue. Sorry for inconvenience.
>
> >
> > commit 6ac3a0ebfcc2f0c75ca0ca6974389ce421aa5cbd
> > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > Date: Tue Aug 20 13:21:18 2019 +0100
> >
> > dmabuf: Mark up onstack timer for selftests
> >
> > No?
> > -Chris
prev parent reply other threads:[~2019-11-27 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 7:19 2989f64510 ("dma-buf: Add selftests for dma-fence"): WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:524 __debug_object_init kernel test robot
2019-11-21 7:26 ` Chris Wilson
2019-11-22 1:32 ` Philip Li
2019-11-27 7:30 ` Philip Li [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=20191127073054.GG30842@intel.com \
--to=philip.li@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.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 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).