This repository has been archived by the owner on May 12, 2021. It is now read-only.
Add initcall_debug to dev guide debug section #204
Assignees
Comments
jodh-intel
added a commit
to jodh-intel/documentation
that referenced
this issue
Jul 30, 2018
kata-containers/runtime#527 Removed the hard-coded `initcall_debug` kernel option (as it generates a lot of kernel output at boot). Add the `initcall_debug` option to the "Enable full debug" section to allow users to enable these potentially useful messages when debugging. Fixes kata-containers#204. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel
added a commit
to jodh-intel/documentation
that referenced
this issue
Jul 30, 2018
kata-containers/runtime#527 Removed the hard-coded `initcall_debug` kernel option (as it generates a lot of kernel output at boot). Add the `initcall_debug` option to the "Enable full debug" section to allow users to enable these potentially useful messages when debugging. Fixes kata-containers#204. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
kata-containers/runtime#527 removes the hard-coded
initcall_debugkernel option from the runtime so add it to the debug section in the dev guide.The text was updated successfully, but these errors were encountered: