[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7hvbg3gfeb.fsf@deeprootsystems.com>
Date: Fri, 08 May 2015 10:14:52 -0700
From: Kevin Hilman <khilman@...nel.org>
To: Simon Horman <horms@...ge.net.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, linux-sh@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Magnus Damm <magnus.damm@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
LAK <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Possible regression due to "hrtimer: Get rid of hrtimer softirq"
Simon Horman <horms@...ge.net.au> writes:
> Hi Thomas,
>
> On Thu, May 07, 2015 at 02:35:59PM +0200, Thomas Gleixner wrote:
>> On Thu, 7 May 2015, Simon Horman wrote:
>> > ------------[ cut here ]------------
>> > kernel BUG at kernel/irq_work.c:135!
>>
>> BUG_ON(!irqs_disabled());
>>
>> So something enables interrupts in the periodic tick handling
>> machinery. Seems you have high resolution timers disabled, but nohz
>> enabled. And that code path has a local_irq_disable/enable pair which
>> causes havoc. Patch below.
>
> Thanks for your quick response. I have been able to confirm that
> when applied on top of next-20150507 the problem I observed no longer
> manifests. I have successfully tested it on all the boards
> where I previously observed a problem.
>
> If you are planning to formally submit the patch below feel free to add:
>
> Tested-by: Simon Horman <horms+renesas@...ge.net.au>
FWIW, I confirmed this fixed a boot hang on my kzm9d in next-20150507
also.
Tested-by: Kevin Hilman <khilman@...aro.org>
--
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