[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1391395399.5357.16.camel@marge.simpson.net>
Date: Mon, 03 Feb 2014 03:43:19 +0100
From: Mike Galbraith <bitbucket@...ine.de>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org,
rostedt@...dmis.org, tglx@...utronix.de
Subject: Re: [PATCH 1/2] irq_work: allow certain work in hard irq context
On Sun, 2014-02-02 at 21:10 +0100, Sebastian Andrzej Siewior wrote:
> So CPU5 & CPU52 were eating 100% CPU doing "nothing" instead of running
> cc1 & objdump right?
Yeah.
> According to the backtrace both of them are trying to access the
> per-cpu hrtimer (sched_timer) in order to cancel but they seem to fail
> to get the timer lock here. They shouldn't spin there for minutes, I
> have no idea why they did so…
I dumped it for later-guy.. but he tends to get busy doing other crap,
and just whacks my carefully saved data ;-)
> I guess this problem does not occur without -RT and before that patch
> you saw only that one warning from can_stop_full_tick()?
I didn't try it without -RT, and yes, without, you just get the warning.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists