Debian 8.2 computer freezing+crashing randomly
Clash Royale CLAN TAG#URR8PPP
I have a Debian media server which seems to be crashing several times daily for no apparent reason at all. It simply freezes up, without restarting, until you manually restart it. I have uploaded the syslog here and the kern.log here
Any restart indications in the log file were done manually by me and not as a direct result of the crash.
debian freeze crash
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
asked Dec 3 '15 at 4:19
hmndhmnd
34
add a comment |
I have a Debian media server which seems to be crashing several times daily for no apparent reason at all. It simply freezes up, without restarting, until you manually restart it. I have uploaded the syslog here and the kern.log here
Any restart indications in the log file were done manually by me and not as a direct result of the crash.
debian freeze crash
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
asked Dec 3 '15 at 4:19
hmndhmnd
34
Post your logs to pastebin, I would rather not download a file
– cutrightjm
Dec 3 '15 at 4:24
Just updated the links.
– hmnd
Dec 3 '15 at 4:35
Have you looked at all of the things that say "temperature alarms"? That might not be the answer, but it's a good thing to look in to at least
– cutrightjm
Dec 3 '15 at 4:40
I thought that as well. But it seems as though that sensor in particular is a virtual sensor created by lm-sensors since it always stays at 127.0°C. So it doesn't seem to be an overheating problem.
– hmnd
Dec 3 '15 at 5:06
add a comment |
I have a Debian media server which seems to be crashing several times daily for no apparent reason at all. It simply freezes up, without restarting, until you manually restart it. I have uploaded the syslog here and the kern.log here
Any restart indications in the log file were done manually by me and not as a direct result of the crash.
debian freeze crash
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
asked Dec 3 '15 at 4:19
hmndhmnd
34
I have a Debian media server which seems to be crashing several times daily for no apparent reason at all. It simply freezes up, without restarting, until you manually restart it. I have uploaded the syslog here and the kern.log here
Any restart indications in the log file were done manually by me and not as a direct result of the crash.
debian freeze crash
debian freeze crash
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
asked Dec 3 '15 at 4:19
hmndhmnd
34
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
asked Dec 3 '15 at 4:19
hmndhmnd
34
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
edited Feb 27 at 10:53
Rui F Ribeiro
41.7k1483142
41.7k1483142
asked Dec 3 '15 at 4:19
hmndhmnd
34
asked Dec 3 '15 at 4:19
hmndhmnd
34
asked Dec 3 '15 at 4:19
hmndhmnd
34
34
Post your logs to pastebin, I would rather not download a file
– cutrightjm
Dec 3 '15 at 4:24
Just updated the links.
– hmnd
Dec 3 '15 at 4:35
Have you looked at all of the things that say "temperature alarms"? That might not be the answer, but it's a good thing to look in to at least
– cutrightjm
Dec 3 '15 at 4:40
I thought that as well. But it seems as though that sensor in particular is a virtual sensor created by lm-sensors since it always stays at 127.0°C. So it doesn't seem to be an overheating problem.
– hmnd
Dec 3 '15 at 5:06
add a comment |
Post your logs to pastebin, I would rather not download a file
– cutrightjm
Dec 3 '15 at 4:24
Just updated the links.
– hmnd
Dec 3 '15 at 4:35
Have you looked at all of the things that say "temperature alarms"? That might not be the answer, but it's a good thing to look in to at least
– cutrightjm
Dec 3 '15 at 4:40
I thought that as well. But it seems as though that sensor in particular is a virtual sensor created by lm-sensors since it always stays at 127.0°C. So it doesn't seem to be an overheating problem.
– hmnd
Dec 3 '15 at 5:06
Post your logs to pastebin, I would rather not download a file
– cutrightjm
Dec 3 '15 at 4:24
Post your logs to pastebin, I would rather not download a file
– cutrightjm
Dec 3 '15 at 4:24
Just updated the links.
– hmnd
Dec 3 '15 at 4:35
Just updated the links.
– hmnd
Dec 3 '15 at 4:35
Have you looked at all of the things that say "temperature alarms"? That might not be the answer, but it's a good thing to look in to at least
– cutrightjm
Dec 3 '15 at 4:40
Have you looked at all of the things that say "temperature alarms"? That might not be the answer, but it's a good thing to look in to at least
– cutrightjm
Dec 3 '15 at 4:40
I thought that as well. But it seems as though that sensor in particular is a virtual sensor created by lm-sensors since it always stays at 127.0°C. So it doesn't seem to be an overheating problem.
– hmnd
Dec 3 '15 at 5:06
I thought that as well. But it seems as though that sensor in particular is a virtual sensor created by lm-sensors since it always stays at 127.0°C. So it doesn't seem to be an overheating problem.
– hmnd
Dec 3 '15 at 5:06
add a comment |
1 Answer
1
active
oldest
votes
I don't see any explicit question here, but here's what I would do to start debugging this issue.
The first thing I do in cases like this is to run memtest86 or memtest86+ a few hours on the machine. This will rule out a lot of the common hardware errors.
If that passes, I run mprime for good measure. It will check that the CPU continues to calculate most things correctly under stress. I've had subtle errors after several hours running this, although I have not had to use it in a couple of years.
Now, if these tests passes, your hardware and cooling should be fine. After this I'd try running the system from a live CD if possible, perhaps trying an i386 version instead of amd64, to see if there's something wrong there.
If this does not give any insight, feel free to update the question with any new information!
answered Dec 3 '15 at 5:29
pipepipe
316116
There have been regular complaints about instability in Debian 8, specially from the ARM community mainly due to buggy wifi cards and temperature issues. I would uninstall all the fluff, like avahi, and upgrade to the latest kernel 4. At least, that is what I did at home.
– Rui F Ribeiro
Dec 3 '15 at 7:58
The computer in question is not running on ARM hardware.
– pipe
Dec 3 '15 at 8:38
After checking the logs to verify the CPU model I see that he is using nouveau. I have had massive problems with that on a more recent kernel. I would comment on the original post, but alas, I don't have enough virtual points here.
– pipe
Dec 3 '15 at 8:48
pipe, write the answer and I will give you points.
– Rui F Ribeiro
Dec 3 '15 at 8:51
@pipe I ran a memtest overnight, 0 errors. So do you think I should upgrade to the latest kernel, or do you have any other suggestions?
– hmnd
Dec 3 '15 at 22:20
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f247038%2fdebian-8-2-computer-freezingcrashing-randomly%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't see any explicit question here, but here's what I would do to start debugging this issue.
The first thing I do in cases like this is to run memtest86 or memtest86+ a few hours on the machine. This will rule out a lot of the common hardware errors.
If that passes, I run mprime for good measure. It will check that the CPU continues to calculate most things correctly under stress. I've had subtle errors after several hours running this, although I have not had to use it in a couple of years.
Now, if these tests passes, your hardware and cooling should be fine. After this I'd try running the system from a live CD if possible, perhaps trying an i386 version instead of amd64, to see if there's something wrong there.
If this does not give any insight, feel free to update the question with any new information!
answered Dec 3 '15 at 5:29
pipepipe
316116
There have been regular complaints about instability in Debian 8, specially from the ARM community mainly due to buggy wifi cards and temperature issues. I would uninstall all the fluff, like avahi, and upgrade to the latest kernel 4. At least, that is what I did at home.
– Rui F Ribeiro
Dec 3 '15 at 7:58
The computer in question is not running on ARM hardware.
– pipe
Dec 3 '15 at 8:38
After checking the logs to verify the CPU model I see that he is using nouveau. I have had massive problems with that on a more recent kernel. I would comment on the original post, but alas, I don't have enough virtual points here.
– pipe
Dec 3 '15 at 8:48
pipe, write the answer and I will give you points.
– Rui F Ribeiro
Dec 3 '15 at 8:51
@pipe I ran a memtest overnight, 0 errors. So do you think I should upgrade to the latest kernel, or do you have any other suggestions?
– hmnd
Dec 3 '15 at 22:20
add a comment |
I don't see any explicit question here, but here's what I would do to start debugging this issue.
The first thing I do in cases like this is to run memtest86 or memtest86+ a few hours on the machine. This will rule out a lot of the common hardware errors.
If that passes, I run mprime for good measure. It will check that the CPU continues to calculate most things correctly under stress. I've had subtle errors after several hours running this, although I have not had to use it in a couple of years.
Now, if these tests passes, your hardware and cooling should be fine. After this I'd try running the system from a live CD if possible, perhaps trying an i386 version instead of amd64, to see if there's something wrong there.
If this does not give any insight, feel free to update the question with any new information!
answered Dec 3 '15 at 5:29
pipepipe
316116
There have been regular complaints about instability in Debian 8, specially from the ARM community mainly due to buggy wifi cards and temperature issues. I would uninstall all the fluff, like avahi, and upgrade to the latest kernel 4. At least, that is what I did at home.
– Rui F Ribeiro
Dec 3 '15 at 7:58
The computer in question is not running on ARM hardware.
– pipe
Dec 3 '15 at 8:38
After checking the logs to verify the CPU model I see that he is using nouveau. I have had massive problems with that on a more recent kernel. I would comment on the original post, but alas, I don't have enough virtual points here.
– pipe
Dec 3 '15 at 8:48
pipe, write the answer and I will give you points.
– Rui F Ribeiro
Dec 3 '15 at 8:51
@pipe I ran a memtest overnight, 0 errors. So do you think I should upgrade to the latest kernel, or do you have any other suggestions?
– hmnd
Dec 3 '15 at 22:20
add a comment |
I don't see any explicit question here, but here's what I would do to start debugging this issue.
The first thing I do in cases like this is to run memtest86 or memtest86+ a few hours on the machine. This will rule out a lot of the common hardware errors.
If that passes, I run mprime for good measure. It will check that the CPU continues to calculate most things correctly under stress. I've had subtle errors after several hours running this, although I have not had to use it in a couple of years.
Now, if these tests passes, your hardware and cooling should be fine. After this I'd try running the system from a live CD if possible, perhaps trying an i386 version instead of amd64, to see if there's something wrong there.
If this does not give any insight, feel free to update the question with any new information!
answered Dec 3 '15 at 5:29
pipepipe
316116
I don't see any explicit question here, but here's what I would do to start debugging this issue.
The first thing I do in cases like this is to run memtest86 or memtest86+ a few hours on the machine. This will rule out a lot of the common hardware errors.
If that passes, I run mprime for good measure. It will check that the CPU continues to calculate most things correctly under stress. I've had subtle errors after several hours running this, although I have not had to use it in a couple of years.
Now, if these tests passes, your hardware and cooling should be fine. After this I'd try running the system from a live CD if possible, perhaps trying an i386 version instead of amd64, to see if there's something wrong there.
If this does not give any insight, feel free to update the question with any new information!
answered Dec 3 '15 at 5:29
pipepipe
316116
answered Dec 3 '15 at 5:29
pipepipe
316116
answered Dec 3 '15 at 5:29
pipepipe
316116
answered Dec 3 '15 at 5:29
pipepipe
316116
316116
There have been regular complaints about instability in Debian 8, specially from the ARM community mainly due to buggy wifi cards and temperature issues. I would uninstall all the fluff, like avahi, and upgrade to the latest kernel 4. At least, that is what I did at home.
– Rui F Ribeiro
Dec 3 '15 at 7:58
The computer in question is not running on ARM hardware.
– pipe
Dec 3 '15 at 8:38
After checking the logs to verify the CPU model I see that he is using nouveau. I have had massive problems with that on a more recent kernel. I would comment on the original post, but alas, I don't have enough virtual points here.
– pipe
Dec 3 '15 at 8:48
pipe, write the answer and I will give you points.
– Rui F Ribeiro
Dec 3 '15 at 8:51
@pipe I ran a memtest overnight, 0 errors. So do you think I should upgrade to the latest kernel, or do you have any other suggestions?
– hmnd
Dec 3 '15 at 22:20
add a comment |
There have been regular complaints about instability in Debian 8, specially from the ARM community mainly due to buggy wifi cards and temperature issues. I would uninstall all the fluff, like avahi, and upgrade to the latest kernel 4. At least, that is what I did at home.
– Rui F Ribeiro
Dec 3 '15 at 7:58
The computer in question is not running on ARM hardware.
– pipe
Dec 3 '15 at 8:38
After checking the logs to verify the CPU model I see that he is using nouveau. I have had massive problems with that on a more recent kernel. I would comment on the original post, but alas, I don't have enough virtual points here.
– pipe
Dec 3 '15 at 8:48
pipe, write the answer and I will give you points.
– Rui F Ribeiro
Dec 3 '15 at 8:51
@pipe I ran a memtest overnight, 0 errors. So do you think I should upgrade to the latest kernel, or do you have any other suggestions?
– hmnd
Dec 3 '15 at 22:20
There have been regular complaints about instability in Debian 8, specially from the ARM community mainly due to buggy wifi cards and temperature issues. I would uninstall all the fluff, like avahi, and upgrade to the latest kernel 4. At least, that is what I did at home.
– Rui F Ribeiro
Dec 3 '15 at 7:58
There have been regular complaints about instability in Debian 8, specially from the ARM community mainly due to buggy wifi cards and temperature issues. I would uninstall all the fluff, like avahi, and upgrade to the latest kernel 4. At least, that is what I did at home.
– Rui F Ribeiro
Dec 3 '15 at 7:58
The computer in question is not running on ARM hardware.
– pipe
Dec 3 '15 at 8:38
The computer in question is not running on ARM hardware.
– pipe
Dec 3 '15 at 8:38
After checking the logs to verify the CPU model I see that he is using nouveau. I have had massive problems with that on a more recent kernel. I would comment on the original post, but alas, I don't have enough virtual points here.
– pipe
Dec 3 '15 at 8:48
After checking the logs to verify the CPU model I see that he is using nouveau. I have had massive problems with that on a more recent kernel. I would comment on the original post, but alas, I don't have enough virtual points here.
– pipe
Dec 3 '15 at 8:48
pipe, write the answer and I will give you points.
– Rui F Ribeiro
Dec 3 '15 at 8:51
pipe, write the answer and I will give you points.
– Rui F Ribeiro
Dec 3 '15 at 8:51
@pipe I ran a memtest overnight, 0 errors. So do you think I should upgrade to the latest kernel, or do you have any other suggestions?
– hmnd
Dec 3 '15 at 22:20
@pipe I ran a memtest overnight, 0 errors. So do you think I should upgrade to the latest kernel, or do you have any other suggestions?
– hmnd
Dec 3 '15 at 22:20
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f247038%2fdebian-8-2-computer-freezingcrashing-randomly%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Post your logs to pastebin, I would rather not download a file
– cutrightjm
Dec 3 '15 at 4:24
Just updated the links.
– hmnd
Dec 3 '15 at 4:35
Have you looked at all of the things that say "temperature alarms"? That might not be the answer, but it's a good thing to look in to at least
– cutrightjm
Dec 3 '15 at 4:40
I thought that as well. But it seems as though that sensor in particular is a virtual sensor created by lm-sensors since it always stays at 127.0°C. So it doesn't seem to be an overheating problem.
– hmnd
Dec 3 '15 at 5:06