On Sun, 2014-12-14 at 17:03 -0800, Andy Lutomirski wrote: > On Sun, Dec 14, 2014 at 4:58 PM, Huang Ying <[email protected]> > wrote: > > FYI, we noticed the below changes on > > > > commit 1ad83c858c7d4ea210429142c99a1548e6715a35 ("x86_64,vsyscall: Make > > vsyscall emulation configurable") > > > > This is expected. You turned off an expert option, disabling > emulation of a deprecated feature that your init needs. :) If you > enable that option but boot with vsyscall=none, you'll get the same > OOPS, but you'll get a helpful error message, too. > > Either force CONFIG_X86_VSYSCALL_EMULATION=y or upgrade to a modern > gilbc and make sure you rebuild all your static binaries.
Thanks a lot for your information! That is helpful for our testing! Best Regards, Huang, Ying -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
