From: Oliver Sang <oliver.sang@intel.com>
To: Abel Wu <wuyun.abel@bytedance.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
<aubrey.li@linux.intel.com>, <yu.c.chen@intel.com>,
Tiwei Bie <tiwei.btw@antgroup.com>, <oliver.sang@intel.com>
Subject: Re: Re: [linus:master] [sched/eevdf] 2227a957e1: BUG:kernel_NULL_pointer_dereference,address
Date: Thu, 1 Feb 2024 09:47:46 +0800 [thread overview]
Message-ID: <Zbr4QsJ5JyLEkjn6@xsang-OptiPlex-9020> (raw)
In-Reply-To: <a253ee7d-8351-4cd1-bebe-fca1370b4093@bytedance.com>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
hi, Abel,
On Wed, Jan 31, 2024 at 08:34:09PM +0800, Abel Wu wrote:
> On 1/30/24 10:09 PM, Oliver Sang Wrote:
> > hi, Abel,
> >
> > On Tue, Jan 30, 2024 at 06:13:32PM +0800, Abel Wu wrote:
> > > On 1/30/24 3:24 PM, kernel test robot Wrote:
> > > >
> > > > we found this issue happens in very random way (23 out of 999 runs).
> > > > but keeps clean on parent.
> > >
> > > Thanks for reporting, I will try to reproduce the issue. Does the 'parent'
> > > mean the same code branch without this commit?
> >
> >
> > it just means the parent in git log.
> >
> > xsang@inn:/c/repo/linux$ git log --oneline --graph 2227a957e1
> > * 2227a957e1d5b sched/eevdf: Sort the rbtree by virtual deadline
> > * 84db47ca7146d sched/numa: Fix mm numa_scan_seq based unconditional scan <-- parent
>
> Thanks for clarifying, Oliver. And can you please check the parent's
> dmesg for the log:
>
> pr_err("EEVDF scheduling fail, picking leftmost\n");
>
> which potentially turns a kernel panic to a message.
yeah, there is. and there are 27 runs have this log from 999 runs, almost same
rate as the crash we reported for 2227a957e1 (which is 23 out of 999 runs).
attached one FYI.
[ 600.569585][ T16] EEVDF scheduling fail, picking leftmost
[ 600.569900][ T16]
[ 600.569902][ T16] ======================================================
[ 600.569903][ T16] WARNING: possible circular locking dependency detected
[ 600.569905][ T16] 6.7.0-rc1-00005-g84db47ca7146 #1 Tainted: G W N
[ 600.569907][ T16] ------------------------------------------------------
[ 600.569908][ T16] rcu_preempt/16 is trying to acquire lock:
[ 600.569910][ T16] c3bb4a48 (console_owner){-.-.}-{0:0}, at: console_lock_spinning_enable+0x27/0x50
[ 600.569937][ T16]
[ 600.569937][ T16] but task is already holding lock:
[ 600.569938][ T16] e75ff0b0 (&rq->__lock){-.-.}-{2:2}, at: rq_lock+0x1f/0xe0
....
[-- Attachment #2: dmesg-parent.xz --]
[-- Type: application/x-xz, Size: 59040 bytes --]
next prev parent reply other threads:[~2024-02-01 1:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 7:24 kernel test robot
2024-01-30 10:13 ` Abel Wu
2024-01-30 14:09 ` Oliver Sang
2024-01-31 12:34 ` Abel Wu
2024-02-01 1:47 ` Oliver Sang [this message]
2024-02-01 1:29 ` Honglei Wang
2024-02-01 1:54 ` Oliver Sang
2024-02-01 2:52 ` Honglei Wang
2024-01-31 12:10 ` Tiwei Bie
2024-01-31 12:28 ` Abel Wu
2024-01-31 13:14 ` Tiwei Bie
2024-02-19 12:35 ` Chen Yu
2024-02-20 3:39 ` Abel Wu
2024-02-21 2:16 ` Oliver Sang
2024-02-19 12:49 ` Chen Yu
2024-02-20 4:04 ` Abel Wu
2024-02-20 9:17 ` Chen Yu
2024-02-21 2:32 ` Oliver Sang
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=Zbr4QsJ5JyLEkjn6@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=tiwei.btw@antgroup.com \
--cc=wuyun.abel@bytedance.com \
--cc=yu.c.chen@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
all inboxes | Powered by JetHome®