From: "Kohli, Gaurav" <gkohli@codeaurora.org>
To: Oleg Nesterov <oleg@redhat.com>, Qian Cai <cai@lca.pw>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at kernel/sched/core.c:3490!
Date: Fri, 11 Jan 2019 16:07:42 +0530 [thread overview]
Message-ID: <3a6d8f4c-d7ed-e888-601b-a379efec306a@codeaurora.org> (raw)
In-Reply-To: <20190107175644.GB7636@redhat.com>
On 1/7/2019 11:26 PM, Oleg Nesterov wrote:
> pr_crit("XXX: %ld %d\n", current->state, current->on_rq);
Can we also add flags, this may help to know the path of problem:
pr_crit("XXX: %ld %d 0x%x\n", current->state, current->on_rq,
current->flags);
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2019-01-11 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 5:44 kernel BUG at kernel/sched/core.c:3490! Qian Cai
2019-01-07 13:52 ` Peter Zijlstra
2019-01-07 14:36 ` Qian Cai
2019-01-07 17:56 ` Oleg Nesterov
2019-01-11 10:37 ` Kohli, Gaurav [this message]
2019-01-11 16:17 ` Qian Cai
2019-01-12 8:54 ` Kohli, Gaurav
2019-01-16 17:32 ` Oleg Nesterov
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=3a6d8f4c-d7ed-e888-601b-a379efec306a@codeaurora.org \
--to=gkohli@codeaurora.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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