Error: Call Traces found on your server


Recommended Posts

  • 4 weeks later...
29 minutes ago, johnnie.black said:

Yep, there's another one related to a kernel problem, fixed in rc3

Thanks for lightning fast response! 

 

Can you elaborate what you mean by fixed in rc3? Do I need to do anything other than the XFS_repair command I did earlier to avoid something like this happening again? 

Link to comment

The first call trace:

 

Mar 31 06:43:17 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038

is unrelated to the second one (and xfs_repair), it's a kernel bug fixed on rc3, the second one was filesystem corruption and should be fine now after running xfs_repair.

  • Upvote 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.