Am 07.11.2014 um 12:56 schrieb Stefan Seyfried: > Hi Paul, > > Am 07.11.2014 um 12:53 schrieb Paul Bolle: >> 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.
JFTR, this did not help: tux@linux:~/linux> zgrep CONFIG_RCU_NOCB_CPU /proc/config.gz # CONFIG_RCU_NOCB_CPU is not set neither did: --- a/init/main.c +++ b/init/main.c @@ -583,7 +583,7 @@ asmlinkage __visible void __init start_kernel(void) early_irq_init(); init_IRQ(); tick_init(); - rcu_init_nohz(); +// rcu_init_nohz(); init_timers(); hrtimers_init(); softirq_init(); -- 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/