mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: qianli zhao <zhaoqianligood@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	axboe@kernel.dk, akpm@linux-foundation.org,
	Felix.Kuehling@amd.com, John Stultz <john.stultz@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	ben.dooks@codethink.co.uk, bfields@redhat.com, cl@rock-chips.com,
	linux-kernel@vger.kernel.org, Qianli Zhao <zhaoqianli@xiaomi.com>,
	0day robot <lkp@intel.com>,
	lkp@lists.01.org
Subject: Re: [kthread] 2e7d8748eb: last_state.is_incomplete_run
Date: Wed, 2 Sep 2020 15:53:13 +0800	[thread overview]
Message-ID: <dbe28d52-1879-66b7-a490-29fe5e14a703@intel.com> (raw)
In-Reply-To: <CAPx_LQGBY-QzXnYMB4zZ=Q5yyRGFF9W68NgB8gqqXchRjUD2WQ@mail.gmail.com>

Thanks for the input, we do detect this on this commit but not its parent.
It may be merged into a wrong base branch or something else that
we are not aware of. And it's kind difficulty now for us to provide a
reproduction step for kexec issue, we will consider this further.

Best Regards,
Rong Chen


On 8/27/2020 11:49 AM, qianli zhao wrote:
> I did not see any exceptions related to my changes,the corresponding
> macro CONFIG_DEBUG_OBJECTS_KTHREAD is not enabled,so i think the issue
> has nothing to do with my changes
>
> Thanks
>
> On Thu, 20 Aug 2020 at 14:26, kernel test robot <rong.a.chen@intel.com> wrote:
>> Greeting,
>>
>> FYI, we noticed the following commit (built with gcc-9):
>>
>> commit: 2e7d8748eba7e32150cbd4f57129ea77d1255892 ("[RFC V2] kthread: add object debug support")
>> url: https://github.com/0day-ci/linux/commits/Qianli-Zhao/kthread-add-object-debug-support/20200812-131719
>> base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git fb893de323e2d39f7a1f6df425703a2edbdf56ea
>>
>> in testcase: boot
>>
>> on test machine: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G memory
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>>
>> kernel boot failed by kexec:
>>
>> user  :notice:  [32m[  +0.371313]  [0m [33mLKP [0m: kexec loading...
>> user  :notice:  [32m[  +0.007118]  [0mkexec --noefi -l /opt/rootfs/tmp/pkg/linux/x86_64-rhel-8.3/gcc-9/2e7d8748eba7e32150cbd4f57129ea77d1255892/vmlinuz-5.8.0-12610-g2e7d8748eba7e --initrd=/opt/rootfs/tmp/initrd-concatenated
>>
>>
>>
>>
>> Thanks,
>> Rong Chen
>>


      reply	other threads:[~2020-09-02  7:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12  5:14 [RFC V2] kthread: add object debug support Qianli Zhao
2020-08-12  8:34 ` Stephen Boyd
2020-08-12 10:27   ` Thomas Gleixner
2020-08-15  8:37     ` Stephen Boyd
2020-08-16 19:38       ` Thomas Gleixner
2020-08-12 10:10 ` Thomas Gleixner
2020-08-20  6:25 ` [kthread] 2e7d8748eb: last_state.is_incomplete_run kernel test robot
2020-08-27  3:49   ` qianli zhao
2020-09-02  7:53     ` Chen, Rong A [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=dbe28d52-1879-66b7-a490-29fe5e14a703@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=ben.dooks@codethink.co.uk \
    --cc=bfields@redhat.com \
    --cc=cl@rock-chips.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=zhaoqianli@xiaomi.com \
    --cc=zhaoqianligood@gmail.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

Powered by JetHome