BUG: spinlock trylock failure on UP - reverting timer patches helps
From: jordan <hidden>
Date: 2014-04-18 15:09:22
Also in:
linux-rt-users, lkml
Hey slavo
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.
No problem. It's good to hear that is working. My AMD Phenom II 965 has 1day, 10hours uptime. Hopefully that foreshadows your system running well.
My combined revert patch from 3.12.15-rt25 is at http://pastebin.com/MYLqbmZw That was all that was needed.
Yup. I suggest anyone from the list who can't get their machines to boot with those commits applied, test that patch.
quoted
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.
ah, thanks for the clarification [ i must have missed that bit - i was just glad someone else had verified on the list that those commits were problematic, as i hadn't gotten any response]. NO_HZ_FULL had been alright for me, for a while - so i didn't really notice the breakage with periodic timers, but that is good to know. I think periodic timers + reverting those patches + resurrecting sirq threads on seems to be the best on 3.14-rt, afaict. Jordan
Thanks
--
Stano