1,734
edits
Changes
m
Bugzilla -> bug tracker
</pre>
Error message contains usefull useful information to determine what was the reason of an oops. This is includes contents of registers, information about the process caused the oops and the contents of a stack. Call A call trace is a decoded stack that allows developers to understand how the kernel comes to an oops.So, to To determine wether whether your system has had an oops or not you can , grepyour logs:
<pre>
grep -E "Call Trace|Code" /var/log/messages*
=== 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 would please ask you to send us a report about this bug in our bugzillabug tracker: httphttps://bugzillabugs.openvz.org. Report must contain:
* Kernel version and architecture (output of <tt>uname -a</tt> command on the kernel that caused a problem)
* Description of how to reproduce the oops.
{{Note|some oopses are so fatal that they can't be writted written into a log file. In that case, you should [[Remote console setup|set up a remote console]] to catch the oops.}}
[[Category: Troubleshooting]]
[[Category: Kernel]]
