Random system Freezes on two different machines in the same room
I have been encountering a problem with 2 desktop workstations in my home office. This problem began on an old dell machine, and when I finally gave up diagnosing it, I purchased a new desktop, only to have the problem follow. (Machine specs below).
The problem is that both machines will simply stop responding. No mouse or keyboard input, can't switch to another tty, nothing. The only way to get the machine back is to power cycle. When I bring it back there are no errors in xorg logs, nor in the systemd journal, the logging simply stops at the point of the freeze. This can happen when idle, or under load. It happens between 2 and 12 hours after the machine is booted.The machine is also not reachable via ssh.
I don't have detailed specs on the old machine, it was a freebie I picked up from someone. It was a core2duo with 2GB of RAM running Fedora 21
The new machine is a 4th gen i5, 32GB of RAM, Nvidia Geforce GT 720 using the nouveau driver. When I first got it I installed Fedora 21, when I thought the OS may be the issue I installed Arch.
My troubleshooting steps thus far:
- I have replaced the computer
- Changed Distros from Fedora to Arch
- I thought this may be a power related issue, like a drop in the outlet voltage so I tried different outlets in the same room, and eventually put the machine on a new UPS to try and eliminate the house power and the power strip as an issue
- I just switched out the mouse, if it happens again the keyboard is next.
At this point the only things that are the same are the location, the modem and router, the monitor and the network cable.
arch-linux hardware freeze
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
asked Jan 4 '15 at 2:52
Ben Sebastian
263
|
show 4 more comments
I have been encountering a problem with 2 desktop workstations in my home office. This problem began on an old dell machine, and when I finally gave up diagnosing it, I purchased a new desktop, only to have the problem follow. (Machine specs below).
The problem is that both machines will simply stop responding. No mouse or keyboard input, can't switch to another tty, nothing. The only way to get the machine back is to power cycle. When I bring it back there are no errors in xorg logs, nor in the systemd journal, the logging simply stops at the point of the freeze. This can happen when idle, or under load. It happens between 2 and 12 hours after the machine is booted.The machine is also not reachable via ssh.
I don't have detailed specs on the old machine, it was a freebie I picked up from someone. It was a core2duo with 2GB of RAM running Fedora 21
The new machine is a 4th gen i5, 32GB of RAM, Nvidia Geforce GT 720 using the nouveau driver. When I first got it I installed Fedora 21, when I thought the OS may be the issue I installed Arch.
My troubleshooting steps thus far:
- I have replaced the computer
- Changed Distros from Fedora to Arch
- I thought this may be a power related issue, like a drop in the outlet voltage so I tried different outlets in the same room, and eventually put the machine on a new UPS to try and eliminate the house power and the power strip as an issue
- I just switched out the mouse, if it happens again the keyboard is next.
At this point the only things that are the same are the location, the modem and router, the monitor and the network cable.
arch-linux hardware freeze
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
asked Jan 4 '15 at 2:52
Ben Sebastian
263
Which kernel(s) are you running? Have you tried LTS?
– jasonwryan
Jan 4 '15 at 3:27
3.17.6-1-ARCH I have not tried any LTS Distros
– Ben Sebastian
Jan 4 '15 at 3:33
Do you have headphones that have any metal on them? I had a similar problem that used to occur only during the winter. It turned out that static charge from touching the metal on my headphones was causing it.
– jordanm
Jan 4 '15 at 3:38
I do, but they have not been plugged in every time its happened. Good thought though.
– Ben Sebastian
Jan 4 '15 at 3:55
Update: I've booted the machine into a non graphical mode, and unplugged all peripherals. I'm going to see how it does this way to see if it may related to Xorg, the video drivers, or a peripheral.
– Ben Sebastian
Jan 4 '15 at 4:11
|
show 4 more comments
I have been encountering a problem with 2 desktop workstations in my home office. This problem began on an old dell machine, and when I finally gave up diagnosing it, I purchased a new desktop, only to have the problem follow. (Machine specs below).
The problem is that both machines will simply stop responding. No mouse or keyboard input, can't switch to another tty, nothing. The only way to get the machine back is to power cycle. When I bring it back there are no errors in xorg logs, nor in the systemd journal, the logging simply stops at the point of the freeze. This can happen when idle, or under load. It happens between 2 and 12 hours after the machine is booted.The machine is also not reachable via ssh.
I don't have detailed specs on the old machine, it was a freebie I picked up from someone. It was a core2duo with 2GB of RAM running Fedora 21
The new machine is a 4th gen i5, 32GB of RAM, Nvidia Geforce GT 720 using the nouveau driver. When I first got it I installed Fedora 21, when I thought the OS may be the issue I installed Arch.
My troubleshooting steps thus far:
- I have replaced the computer
- Changed Distros from Fedora to Arch
- I thought this may be a power related issue, like a drop in the outlet voltage so I tried different outlets in the same room, and eventually put the machine on a new UPS to try and eliminate the house power and the power strip as an issue
- I just switched out the mouse, if it happens again the keyboard is next.
At this point the only things that are the same are the location, the modem and router, the monitor and the network cable.
arch-linux hardware freeze
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
asked Jan 4 '15 at 2:52
Ben Sebastian
263
I have been encountering a problem with 2 desktop workstations in my home office. This problem began on an old dell machine, and when I finally gave up diagnosing it, I purchased a new desktop, only to have the problem follow. (Machine specs below).
The problem is that both machines will simply stop responding. No mouse or keyboard input, can't switch to another tty, nothing. The only way to get the machine back is to power cycle. When I bring it back there are no errors in xorg logs, nor in the systemd journal, the logging simply stops at the point of the freeze. This can happen when idle, or under load. It happens between 2 and 12 hours after the machine is booted.The machine is also not reachable via ssh.
I don't have detailed specs on the old machine, it was a freebie I picked up from someone. It was a core2duo with 2GB of RAM running Fedora 21
The new machine is a 4th gen i5, 32GB of RAM, Nvidia Geforce GT 720 using the nouveau driver. When I first got it I installed Fedora 21, when I thought the OS may be the issue I installed Arch.
My troubleshooting steps thus far:
- I have replaced the computer
- Changed Distros from Fedora to Arch
- I thought this may be a power related issue, like a drop in the outlet voltage so I tried different outlets in the same room, and eventually put the machine on a new UPS to try and eliminate the house power and the power strip as an issue
- I just switched out the mouse, if it happens again the keyboard is next.
At this point the only things that are the same are the location, the modem and router, the monitor and the network cable.
arch-linux hardware freeze
arch-linux hardware freeze
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
asked Jan 4 '15 at 2:52
Ben Sebastian
263
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
asked Jan 4 '15 at 2:52
Ben Sebastian
263
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
edited Dec 15 at 12:47
Rui F Ribeiro
38.9k1479129
38.9k1479129
asked Jan 4 '15 at 2:52
Ben Sebastian
263
asked Jan 4 '15 at 2:52
Ben Sebastian
263
asked Jan 4 '15 at 2:52
Ben Sebastian
263
263
Which kernel(s) are you running? Have you tried LTS?
– jasonwryan
Jan 4 '15 at 3:27
3.17.6-1-ARCH I have not tried any LTS Distros
– Ben Sebastian
Jan 4 '15 at 3:33
Do you have headphones that have any metal on them? I had a similar problem that used to occur only during the winter. It turned out that static charge from touching the metal on my headphones was causing it.
– jordanm
Jan 4 '15 at 3:38
I do, but they have not been plugged in every time its happened. Good thought though.
– Ben Sebastian
Jan 4 '15 at 3:55
Update: I've booted the machine into a non graphical mode, and unplugged all peripherals. I'm going to see how it does this way to see if it may related to Xorg, the video drivers, or a peripheral.
– Ben Sebastian
Jan 4 '15 at 4:11
|
show 4 more comments
Which kernel(s) are you running? Have you tried LTS?
– jasonwryan
Jan 4 '15 at 3:27
3.17.6-1-ARCH I have not tried any LTS Distros
– Ben Sebastian
Jan 4 '15 at 3:33
Do you have headphones that have any metal on them? I had a similar problem that used to occur only during the winter. It turned out that static charge from touching the metal on my headphones was causing it.
– jordanm
Jan 4 '15 at 3:38
I do, but they have not been plugged in every time its happened. Good thought though.
– Ben Sebastian
Jan 4 '15 at 3:55
Update: I've booted the machine into a non graphical mode, and unplugged all peripherals. I'm going to see how it does this way to see if it may related to Xorg, the video drivers, or a peripheral.
– Ben Sebastian
Jan 4 '15 at 4:11
Which kernel(s) are you running? Have you tried LTS?
– jasonwryan
Jan 4 '15 at 3:27
Which kernel(s) are you running? Have you tried LTS?
– jasonwryan
Jan 4 '15 at 3:27
3.17.6-1-ARCH I have not tried any LTS Distros
– Ben Sebastian
Jan 4 '15 at 3:33
3.17.6-1-ARCH I have not tried any LTS Distros
– Ben Sebastian
Jan 4 '15 at 3:33
Do you have headphones that have any metal on them? I had a similar problem that used to occur only during the winter. It turned out that static charge from touching the metal on my headphones was causing it.
– jordanm
Jan 4 '15 at 3:38
Do you have headphones that have any metal on them? I had a similar problem that used to occur only during the winter. It turned out that static charge from touching the metal on my headphones was causing it.
– jordanm
Jan 4 '15 at 3:38
I do, but they have not been plugged in every time its happened. Good thought though.
– Ben Sebastian
Jan 4 '15 at 3:55
I do, but they have not been plugged in every time its happened. Good thought though.
– Ben Sebastian
Jan 4 '15 at 3:55
Update: I've booted the machine into a non graphical mode, and unplugged all peripherals. I'm going to see how it does this way to see if it may related to Xorg, the video drivers, or a peripheral.
– Ben Sebastian
Jan 4 '15 at 4:11
Update: I've booted the machine into a non graphical mode, and unplugged all peripherals. I'm going to see how it does this way to see if it may related to Xorg, the video drivers, or a peripheral.
– Ben Sebastian
Jan 4 '15 at 4:11
|
show 4 more comments
1 Answer
1
active
oldest
votes
It looks like the problem was with the nouveau drivers. I installed the Nvidia drivers from Arch's core repo and the issue has not occured again in over 24 hours. Thanks for everyone's help!
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
answered Jan 5 '15 at 17:27
Ben Sebastian
263
Strange. My experience has been exactly the other way around: nouveau rock solid (after a rocky start), nVidia leading to all sorts of "interesting" behaviour. But the nVidia experiments I gave up a long way back, now using bog-standard Fedora.
– vonbrand
Dec 28 '15 at 23:56
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%2f177307%2frandom-system-freezes-on-two-different-machines-in-the-same-room%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
It looks like the problem was with the nouveau drivers. I installed the Nvidia drivers from Arch's core repo and the issue has not occured again in over 24 hours. Thanks for everyone's help!
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
answered Jan 5 '15 at 17:27
Ben Sebastian
263
Strange. My experience has been exactly the other way around: nouveau rock solid (after a rocky start), nVidia leading to all sorts of "interesting" behaviour. But the nVidia experiments I gave up a long way back, now using bog-standard Fedora.
– vonbrand
Dec 28 '15 at 23:56
add a comment |
It looks like the problem was with the nouveau drivers. I installed the Nvidia drivers from Arch's core repo and the issue has not occured again in over 24 hours. Thanks for everyone's help!
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
answered Jan 5 '15 at 17:27
Ben Sebastian
263
Strange. My experience has been exactly the other way around: nouveau rock solid (after a rocky start), nVidia leading to all sorts of "interesting" behaviour. But the nVidia experiments I gave up a long way back, now using bog-standard Fedora.
– vonbrand
Dec 28 '15 at 23:56
add a comment |
It looks like the problem was with the nouveau drivers. I installed the Nvidia drivers from Arch's core repo and the issue has not occured again in over 24 hours. Thanks for everyone's help!
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
answered Jan 5 '15 at 17:27
Ben Sebastian
263
It looks like the problem was with the nouveau drivers. I installed the Nvidia drivers from Arch's core repo and the issue has not occured again in over 24 hours. Thanks for everyone's help!
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
answered Jan 5 '15 at 17:27
Ben Sebastian
263
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
edited Jan 5 '15 at 17:46
Ramesh
23.2k32101181
23.2k32101181
answered Jan 5 '15 at 17:27
Ben Sebastian
263
answered Jan 5 '15 at 17:27
Ben Sebastian
263
answered Jan 5 '15 at 17:27
Ben Sebastian
263
263
Strange. My experience has been exactly the other way around: nouveau rock solid (after a rocky start), nVidia leading to all sorts of "interesting" behaviour. But the nVidia experiments I gave up a long way back, now using bog-standard Fedora.
– vonbrand
Dec 28 '15 at 23:56
add a comment |
Strange. My experience has been exactly the other way around: nouveau rock solid (after a rocky start), nVidia leading to all sorts of "interesting" behaviour. But the nVidia experiments I gave up a long way back, now using bog-standard Fedora.
– vonbrand
Dec 28 '15 at 23:56
Strange. My experience has been exactly the other way around: nouveau rock solid (after a rocky start), nVidia leading to all sorts of "interesting" behaviour. But the nVidia experiments I gave up a long way back, now using bog-standard Fedora.
– vonbrand
Dec 28 '15 at 23:56
Strange. My experience has been exactly the other way around: nouveau rock solid (after a rocky start), nVidia leading to all sorts of "interesting" behaviour. But the nVidia experiments I gave up a long way back, now using bog-standard Fedora.
– vonbrand
Dec 28 '15 at 23:56
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f177307%2frandom-system-freezes-on-two-different-machines-in-the-same-room%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
Which kernel(s) are you running? Have you tried LTS?
– jasonwryan
Jan 4 '15 at 3:27
3.17.6-1-ARCH I have not tried any LTS Distros
– Ben Sebastian
Jan 4 '15 at 3:33
Do you have headphones that have any metal on them? I had a similar problem that used to occur only during the winter. It turned out that static charge from touching the metal on my headphones was causing it.
– jordanm
Jan 4 '15 at 3:38
I do, but they have not been plugged in every time its happened. Good thought though.
– Ben Sebastian
Jan 4 '15 at 3:55
Update: I've booted the machine into a non graphical mode, and unplugged all peripherals. I'm going to see how it does this way to see if it may related to Xorg, the video drivers, or a peripheral.
– Ben Sebastian
Jan 4 '15 at 4:11