Timbiotic Posted February 2, 2018 Share Posted February 2, 2018 Recently upgraded to 6.4 then to 6.4.1-rc1. Got the call traces error so posting my diagnosis to see why. lillis.69.mu-diagnostics-20180202-1331.zip Quote Link to comment
Timbiotic Posted February 2, 2018 Author Share Posted February 2, 2018 i see elsewhere call traces mean memeory errors but i am only showing 37% used Quote Link to comment
Timbiotic Posted February 2, 2018 Author Share Posted February 2, 2018 I deleted the plugin preclear that had all the errors but i dont really see any out of memory errors in the logs. Could something else have caused it or should i go ahead and lower the " vm.dirty_background_ratio and vm.dirty_ratio, "? Quote Link to comment
pwm Posted February 4, 2018 Share Posted February 4, 2018 There are thousands of reasons to get call traces. So you can't expect that your call traces should mean you suffer from memory leaks. Quote Link to comment
Timbiotic Posted February 4, 2018 Author Share Posted February 4, 2018 Ok so how do I tell why it was flagged? I see a couple memory comments in log as well as a ton of issues with the preclear plugin which I’ve removed Quote Link to comment
Timbiotic Posted February 14, 2018 Author Share Posted February 14, 2018 Bump first time since I’ve had this server I had a crash today. Pretty sure it has something to do with the new 6.4.1 kernel. “kernel panic not syncing fatal exception in interrupt” was the error I saw when it froze. Any ideas? Do I open a ticket? The only change I’ve done was to enable AMD cool and quiet and that was just so a CPU driver would load as 6.4.1 didn’t seem to be loading my CPU driver. Quote Link to comment
Recommended Posts
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.