From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated
Date: Thu, 25 Jan 2018 13:24:59 +0100 [thread overview]
Message-ID: <20180125122458.GB3420@rei> (raw)
In-Reply-To: <20180125112013.GA6110@localhost.localdomain>
Hi!
> Hummm, wondering how LTP sched tests could trigger this, since a quick
> grep into ltp didn't show DEADLINE usage.
See kernel/syscalls/sched_setattr/sched_setattr01.c
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: lkp@lists.01.org
Subject: Re: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated
Date: Thu, 25 Jan 2018 13:24:59 +0100 [thread overview]
Message-ID: <20180125122458.GB3420@rei> (raw)
In-Reply-To: <20180125112013.GA6110@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
Hi!
> Hummm, wondering how LTP sched tests could trigger this, since a quick
> grep into ltp didn't show DEADLINE usage.
See kernel/syscalls/sched_setattr/sched_setattr01.c
--
Cyril Hrubis
chrubis(a)suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: kernel test robot <xiaolong.ye@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Juri Lelli <juri.lelli@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Luca Abeni <luca.abeni@santannapisa.it>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Claudio Scordino <claudio@evidence.eu.com>,
lkp@01.org, Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated
Date: Thu, 25 Jan 2018 13:24:59 +0100 [thread overview]
Message-ID: <20180125122458.GB3420@rei> (raw)
In-Reply-To: <20180125112013.GA6110@localhost.localdomain>
Hi!
> Hummm, wondering how LTP sched tests could trigger this, since a quick
> grep into ltp didn't show DEADLINE usage.
See kernel/syscalls/sched_setattr/sched_setattr01.c
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-01-25 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 6:28 [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated kernel test robot
2018-01-25 6:28 ` kernel test robot
2018-01-25 6:28 ` kernel test robot
2018-01-25 11:20 ` [LTP] " Juri Lelli
2018-01-25 11:20 ` Juri Lelli
2018-01-25 11:20 ` Juri Lelli
2018-01-25 12:24 ` Cyril Hrubis [this message]
2018-01-25 12:24 ` [LTP] " Cyril Hrubis
2018-01-25 12:24 ` Cyril Hrubis
2018-01-25 13:29 ` Juri Lelli
2018-01-25 13:29 ` Juri Lelli
2018-01-25 13:29 ` Juri Lelli
2018-01-25 13:35 ` Cyril Hrubis
2018-01-25 13:35 ` Cyril Hrubis
2018-01-25 13:35 ` Cyril Hrubis
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=20180125122458.GB3420@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.