From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <efault@gmx.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v4.11.12-rt9
Date: Mon, 7 Aug 2017 09:52:54 +0200 [thread overview]
Message-ID: <20170807075254.pdu7immtbakn7f7g@linutronix.de> (raw)
In-Reply-To: <1501913583.7917.42.camel@gmx.de>
On 2017-08-05 08:13:03 [+0200], Mike Galbraith wrote:
>
> Steven's script annoyed the scheduler here, but woohoo regardless, it
> hasn't yet made boom, or stopped dead in its tracks. I'll give it some
> exercise on my 64 core box, where death has never (modulo fugly hacks
> that survived 30 hrs of hell.. once) been more than minutes away.
>
> [ 190.589248] ------------[ cut here ]------------
> [ 190.589273] WARNING: CPU: 1 PID: 5679 at kernel/sched/core.c:6346 __might_sleep+0x80/0x90
> [ 190.589277] do not call blocking ops when !TASK_RUNNING; state=2 set at [<ffffffff810d2c45>] __finish_swait+0x5/0x60
> [ 190.589340] CPU: 1 PID: 5679 Comm: stress-cpu-hotp Tainted: G E 4.11.12-rt9-virgin #11
> [ 190.589341] Hardware name: MEDION MS-7848/MS-7848, BIOS M7848W08.20C 09/23/2013
> [ 190.589341] Call Trace:
> [ 190.589355] __might_sleep+0x80/0x90
> [ 190.589358] rt_mutex_lock_state+0x25/0x60
> [ 190.589361] rt_mutex_lock+0x13/0x20
> [ 190.589362] _mutex_lock+0x39/0x40
> [ 190.589365] stop_cpus+0x23/0x50
> [ 190.589367] stop_machine_cpuslocked+0xed/0x130
> [ 190.589370] takedown_cpu+0x80/0x110
> [ 190.589372] cpuhp_invoke_callback+0x248/0x9d0
> [ 190.589376] cpuhp_down_callbacks+0x42/0x80
> [ 190.589378] _cpu_down+0xc5/0x100
> [ 190.589380] do_cpu_down+0x3c/0x60
> [ 190.589381] cpu_down+0x10/0x20
> [ 190.589384] cpu_subsys_offline+0x14/0x20
> [ 190.589385] device_offline+0x8a/0xb0
> [ 190.589387] online_store+0x40/0x80
> [ 190.589389] dev_attr_store+0x18/0x30
> [ 190.589391] sysfs_kf_write+0x44/0x60
> [ 190.589392] kernfs_fop_write+0x13c/0x1d0
> [ 190.589395] __vfs_write+0x28/0x140
can you reproduce that one? I don't see where this TASK_UNINTERRUPTIBLE
is coming from.
Sebastian
next prev parent reply other threads:[~2017-08-07 7:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 17:38 [ANNOUNCE] v4.11.12-rt9 Sebastian Andrzej Siewior
2017-08-05 6:13 ` Mike Galbraith
2017-08-05 14:57 ` Mike Galbraith
2017-08-07 7:33 ` Sebastian Andrzej Siewior
2017-08-07 8:22 ` Mike Galbraith
2017-08-08 10:00 ` Mike Galbraith
2017-08-11 7:55 ` [patch-rt] hotplug, hrtimer: Migrate expired/deferred timers during cpu offline Mike Galbraith
2017-08-11 8:15 ` Mike Galbraith
2017-08-14 7:59 ` Mike Galbraith
2017-08-17 16:50 ` Sebastian Andrzej Siewior
2017-08-17 17:17 ` Sebastian Andrzej Siewior
2017-08-17 17:26 ` Mike Galbraith
2017-08-17 17:37 ` Mike Galbraith
2017-08-17 18:43 ` Mike Galbraith
2017-08-07 7:52 ` Sebastian Andrzej Siewior [this message]
2017-08-07 8:38 ` [ANNOUNCE] v4.11.12-rt9 Mike Galbraith
2017-08-09 12:04 ` [patch-rt] locking, rwlock-rt: do not save state multiple times in __write_rt_lock() Mike Galbraith
2017-08-18 9:06 ` Sebastian Andrzej Siewior
2017-08-07 9:10 ` [ANNOUNCE] v4.11.12-rt9 Mike Galbraith
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=20170807075254.pdu7immtbakn7f7g@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).