Created attachment 865172 [details] kernel-3.14.0-0.rc3 OOPS Description of problem: Kernel oops at boot on ARM, in most cases the network is down. Version-Release number of selected component (if applicable): kernel-3.14.0-0.rc3.git0.1.fc21 How reproducible: everytime. Additional info: Log attached.
It'd be helpful if you included which board{s} you're seeing this on, and such... Also, to include the full log, as there should be at least one other oops in there as well...
In any case, we can turn off CONFIG_JUMP_LABEL for now to work around the problem.
Also, what was the last working version?
It's been on all the 3.14 kernels I believe and I've seen it on BeagleBone Black, and the trimslice and Paul has seen it on the Wandboard Quad. It seems to be a generic ARM issue.
All boards using the multiplatform kernel in my testing (beaglebone, trimslice, highbank, wandboard and in qemu). It seems to have started around kernel-3.14.0-0.rc0.git8.1.fc21. I did not see this on midway (LPAE).
Created attachment 865226 [details] wandboard-3.14.0-0.rc3.git0.1.fc21.armv7hl
So the problem here is that once CONFIG_DEBUG_SET_MODULE_RONX marks the module text readonly, we're unable to patch the instructions (which is done through a mucky call chain via do_one_initcall through the module init and netfilter code.) Basically as it stands right now, CONFIG_DEBUG_SET_MODULE_RONX and kprobes/jump labels are mutually exclusive. ARM needs to grow some manner of method of either re-mapping the page at a new vaddr and modifying it through there, then flushing. Or simply cache the state, flip it back, and flush it twice. In any case, simply turning it off for now seems sensible. regards, Kyle
Committed a config change for now.