Editing When you have an oops
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 43: | Line 43: | ||
</pre> | </pre> | ||
− | Error message contains | + | Error message contains usefull information to determine what was the reason of oops. This is contents of registers, information about the process caused oops and contents of a stack. Call trace is decoded stack that allows developers to understand how kernel comes to oops. |
− | + | So, to determine wether your system has had an oops or not you can grep: | |
− | |||
<pre> | <pre> | ||
grep -E "Call Trace|Code" /var/log/messages* | grep -E "Call Trace|Code" /var/log/messages* | ||
Line 51: | Line 50: | ||
=== If you have had an oops === | === 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 | + | 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) | * Kernel version and architecture (output of <tt>uname -a</tt> command on the kernel that caused a problem) | ||
Line 59: | Line 58: | ||
* Description of how to reproduce the oops. | * Description of how to reproduce the oops. | ||
− | {{Note|some oopses are so fatal that they can't be | + | {{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]] | [[Category: Troubleshooting]] | ||
[[Category: Kernel]] | [[Category: Kernel]] |