From: Mark Hounschell <markh@compro.net>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Mark Hounschell <dmarkh@cfl.rr.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: floppy.c soft lockup
Date: Mon, 04 Jun 2007 10:00:54 -0400 [thread overview]
Message-ID: <46641B16.9090701@compro.net> (raw)
In-Reply-To: <20070603081417.GA81@tv-sign.ru>
Oleg Nesterov wrote:
> On 06/02, Mark Hounschell wrote:
>> Jun 2 16:36:11 harley kernel: ERR!! events/1 flush hang: c201dbc0
>> c201dbc0 10012 10012
>> Jun 2 16:36:11 harley kernel: CURR: 7974 7974 vrsx 93 26
>> Jun 2 16:36:11 harley kernel: wq_barrier_func+0x0/0x8
>> Jun 2 16:36:11 harley kernel: vmstat_update+0x0/0x24
>> Jun 2 16:36:11 harley kernel: ----
>> Jun 2 16:36:11 harley kernel: cache_reap+0x0/0xf4
>
> As expected.
>
> Note that ->nivcsw/->nvcsw doesn't change. There is no "spare time"
> on CPU 1, "vrsx" monopolizes CPU. events/1->cache_reap() was preempted
> by vrsx, it had no chance to run since then. Note that jobs == 7974
> doesn't change too. I forgot to print cwq->thread->state, but it should
> be TASK_RUNNING. It would not be possible to kill vrsx if cache_reap()
> stalled.
>
> I don't think this is a kernel problem, vrsx breaks flush_workqueue().
> Ingo can answer authoritatively, but I think SCHED_RR/SCHED_FIFO were
> not designed to be 100% cpu-bound.
>
> That said, I think it makes sense to get rid of flush_scheduled_work()
> in floppy.c.
>
Oleg, thanks for your time in diagnosing this.
As far as a 100% CPU bound task being a valid thing to do, it has been
done for many years on SMP machines. Any kernel limitation on this
surely must be considered a bug?
Thanks again
Regards
Mark
next prev parent reply other threads:[~2007-06-04 14:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 17:31 floppy.c soft lockup Mark Hounschell
2007-05-31 5:46 ` Andrew Morton
2007-05-31 14:28 ` Mark Hounschell
2007-05-31 17:06 ` Oleg Nesterov
2007-05-31 18:01 ` Mark Hounschell
2007-05-31 18:44 ` Mark Hounschell
2007-05-31 19:22 ` Oleg Nesterov
2007-05-31 20:18 ` Mark Hounschell
2007-06-01 9:51 ` Mark Hounschell
2007-06-01 11:00 ` Oleg Nesterov
2007-06-01 14:10 ` Mark Hounschell
2007-06-01 15:16 ` Oleg Nesterov
2007-06-01 17:11 ` Mark Hounschell
2007-06-01 18:36 ` Oleg Nesterov
2007-06-01 19:52 ` Mark Hounschell
2007-06-02 12:30 ` Oleg Nesterov
2007-06-02 20:44 ` Mark Hounschell
2007-06-03 8:14 ` Oleg Nesterov
2007-06-04 14:00 ` Mark Hounschell [this message]
2007-06-06 13:12 ` Mark Hounschell
2007-06-06 17:28 ` Andrew Morton
2007-06-07 1:31 ` Matt Mackall
2007-06-07 10:18 ` Mark Hounschell
2007-06-07 14:25 ` Matt Mackall
2007-06-08 9:54 ` Mark Hounschell
2007-06-13 16:17 ` 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=46641B16.9090701@compro.net \
--to=markh@compro.net \
--cc=akpm@linux-foundation.org \
--cc=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
/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.