[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53513A7E.5050907@meduna.org>
Date: Fri, 18 Apr 2014 16:45:18 +0200
From: Stanislav Meduna <stano@...una.org>
To: jordan <triplesquarednine@...il.com>
CC: "linux-rt-users@...r.kernel.org" <linux-rt-users@...r.kernel.org>,
Linux ARM Kernel <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: BUG: spinlock trylock failure on UP - reverting timer patches
helps
On 18.04.2014 01:10, jordan wrote:
Hi Jordan,
many thanks for the tests. I probably botched something during
the reverting - I now tried some more experiments and the system
now runs without BUGs and without kernel leak - of course
it needs some more uptime to be really sure.
My combined revert patch from 3.12.15-rt25 is at
http://pastebin.com/MYLqbmZw
That was all that was needed.
> Yeah, i know a handful of people [amd users] that have now reported
> success booting into 3.14-rt1 reverting those patches. Personally, I
> have disabled NO_HZ_FULL and have switched back to 'old tick' method
> in kconfig. I don't think the latest no_hz stuff is stable enough...
My problems were with periodic timers (I am on an embedded system
that runs things periodically anyway and I have also my doubts
regarding the stability), so the latest code did not break
only NO_HZ_FULL.
Thanks
--
Stano
--
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