Hi Paul, Am 07.11.2014 um 12:53 schrieb Paul Bolle: > On Fri, 2014-11-07 at 12:10 +0100, Stefan Seyfried wrote: >> I bisected the issue multiple times and always arrived at >> >> # first bad commit: [d6dd50e07c5bec00db2005969b1a01f8ca3d25ef] Merge branch >> 'core-rcu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip >> >> which is a merge commit unfortunately. > > That merge commit actually does add some code: > > git show d6dd50e07c5bec00db2005969b1a01f8ca3d25ef > [...] > diff --cc init/main.c > index 8af2f1abfe38,e3c4cdd94d5b..c5c11da6c4e1 > --- a/init/main.c > +++ b/init/main.c > @@@ -583,6 -585,6 +583,7 @@@ asmlinkage __visible void __init start_ > early_irq_init(); > init_IRQ(); > tick_init(); > ++ rcu_init_nohz(); > init_timers(); > hrtimers_init(); > softirq_init(); > > Wild guess: is CONFIG_RCU_NOCB_CPU perhaps set in your > v3.18-rc3 .config?
Yes it is: tux@linux:~> zgrep CONFIG_RCU_NOCB_CPU /proc/config.gz CONFIG_RCU_NOCB_CPU=y # CONFIG_RCU_NOCB_CPU_NONE is not set # CONFIG_RCU_NOCB_CPU_ZERO is not set CONFIG_RCU_NOCB_CPU_ALL=y And I'll try without it, but looking at the backtrace and the actual BUG_ON() in the code, I cannot really believe it is the real problems. But I'll try with the config changed and with the above line removed. Thanks, Stefan -- Stefan Seyfried Linux Consultant & Developer -- GPG Key: 0x731B665B B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/