Hi all,
I've been using Fedora 29 for some time now with no problems, but
recently (the last couple of weeks or so, I can't be 100% sure) it has
taken to locking up randomly for no apparent reason, even when I am not
using the machine. This happens at least once a day, and can be within
an hour of starting up or 12 hours+ later.
Hardware is a Dell Latitude E6420 with a 500GB drive and 4GB RAM. The computer is solely running Fedora, there is no dual booting involved. Applications that are usually left open are Thunderbird, Firefox and
possibly LibreOffice.
Does anyone have any idea why this is happening and what I can do about
it..? I am not a programmer or developer, just a simple end user.
Interestingly, my partner is running an identical system and is not
having any problems at all.
On Sun, 10 Mar 2019 20:01:23 +0000, MissRiaElaine scribbled:
Hi all,
I've been using Fedora 29 for some time now with no problems, but
recently (the last couple of weeks or so, I can't be 100% sure) it has
taken to locking up randomly for no apparent reason, even when I am not
using the machine. This happens at least once a day, and can be within
an hour of starting up or 12 hours+ later.
Hardware is a Dell Latitude E6420 with a 500GB drive and 4GB RAM. The
computer is solely running Fedora, there is no dual booting involved.
Applications that are usually left open are Thunderbird, Firefox and
possibly LibreOffice.
Does anyone have any idea why this is happening and what I can do about
it..? I am not a programmer or developer, just a simple end user.
Interestingly, my partner is running an identical system and is not
having any problems at all.
Have you run memtest86 [*] on the machine? It is possible that you're experiencing a failing memory module.
Another possibility could be overheating due to dust in the fans. Check
the fans and air filters, and use a can of compressed air to clean out
the dust. While you're at it, also check whether all memory modules,
cables and plug-in cards are properly seated.
Yet another possibility could be a failing power supply. A sudden drop
(or spike) in voltage on a particular line can cause random lockups.
[*] For good measure, it should be left running 24 hours. If it does
nor report any errors, then that is no guarantee that there's
nothing wrong with the hardware. If it /does/ report errors, then
there most certainly _is_ a hardware problem.
On 10/03/2019 21:45, Aragorn wrote:
Have you run memtest86 [*] on the machine?-a It is possible that you're
experiencing a failing memory module.
Another possibility could be overheating due to dust in the fans.-a Check
the fans and air filters, and use a can of compressed air to clean out
the dust.-a While you're at it, also check whether all memory modules,
cables and plug-in cards are properly seated.
Yet another possibility could be a failing power supply.-a A sudden drop
(or spike) in voltage on a particular line can cause random lockups.
[*] For good measure, it should be left running 24 hours.-a If it does
-a-a-a-a nor report any errors, then that is no guarantee that there's
-a-a-a-a nothing wrong with the hardware.-a If it /does/ report errors, then >> -a-a-a-a there most certainly _is_ a hardware problem.
Thanks, I'll check and report back.
On 12/03/2019 20:01, Aragorn wrote:
Always remember that penguins like it really, really cold. :p
They do..! Just done the re-pasting of the thermal compound and so far
so good, according to the instructions it can be anything up to 200
hours before it's fully broken in, but already the CPU temperature has dropped to 44-46 degrees so it looks like that was the problem. Will
have to see how it goes.
Well, a final update on this. I've replaced the machine with a Latitude
E6430 with 8GB RAM and the problem has gone away entirely, the CPU on
this machine is running at an average of 40-50-#C. Fortunately, Linux
doesn't suffer from the Windoze issue of transplanting hard drives to
another machine, it just works..!
The old machine has already proved its worth in donating parts, such as
the US keyboard (don't like the UK layout) and wifi card (the one that
came in this only seemed to like 2.4GHz and didn't recognise my 5GHz
access point for some reason) and also the bluetooth module, which this machine didn't seem to have either (well it came at a good price..!)
I can only assume it was the graphics processor, as after I'd repasted
the CPU that was running reasonably cool, but the GPU was still way up.
Anyway, problem now solved (fingers crossed..!)
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:44:11 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
10 files (20,373K bytes) |
| Messages: | 264,188 |