6,534
edits
Changes
Fixed grammar and some wording, added link to remote console setup to →If you have had an oops
If you have had an oops, the first thing you have to do is to check your hardware. It's described in article [[Hardware testing]]. If all tests are passed, then this is unfortunately kernel bug and we please you to send us a report about this bug in our bugzilla: http://bugzilla.openvz.org. Report must contain:
* Kernel version, and architecture (output of "<tt>uname -a" </tt> command on the kernel, that caused a problem)* If In case you comiled compiled your kernel by self - yourself — your <tt>.config </tt> file.* Kernel In case you have used some additional kernel patches — a link to those patches* Full text of kernel oops message caused by * Description of how to reproduce the oops. * Is it reproducable on your node? How?{{Note|some oopses are so fatal that they can't be writted into a log file. In that case, you should [[Remote console setup|set up a remote console]] to catch the oops.}}
[[Category: Troubleshooting]]
