<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/21/15 06:00, Mike Thomas wrote:<br>
</div>
<blockquote
cite="mid:mailman.3.1450699201.31326.mythtv-users@mythtv.org"
type="cite">
<pre wrap=""><div class="moz-txt-sig">
On Sun, 20 Dec 2015 13:22:47 -0600 Craig Huff <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:huffcslists@gmail.com"><huffcslists@gmail.com></a> wrote:
</div></pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>Okay, I have a clue. Now what to do with it?
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>I found "general protection fault" and "Oops" messages while trolling
<span class="moz-txt-citetags">> </span>through the /var/log/kern.log* and /var/log/syslog* files. Here are
<span class="moz-txt-citetags">> </span>the ten I found in the kern.log* files over the last ~30 days and the
<span class="moz-txt-citetags">> </span>following RIP: lines that indicate where the problems occurred:
<span class="moz-txt-citetags">> </span>
The portions you show indicate that memory contains something
unexpected (corrupt). It is unlikely to be a kernel bug because these
code paths have been in use for decades. I don't think it is your CPU;
the errors would likely be much more extensive.
</pre>
</blockquote>
</blockquote>
I agree with Mike that memory is a likely culprit. If you're
comfortable with a little sysadmin work, the best way to test your
memory is with either <a href="http://www.memtest86.com/">memtest86</a>
or <a href="http://www.memtest.org/">memtest86+</a>. They're both
based on the same original work, but memtest86 is a commercial
package with a free option and memtest86+ is an open-source fork of
the original work. In either case, you boot the memory tester in
place of your normal kernel and it runs some very comprehensive
pattern tests on your memory. It can often identify the specific
module that has a problem. In the worst case. you can do a binary
search to find the bad one by pulling half the modules and testing,
repeating until the bad one is found. It can take several hours to
run a full test, depending on the amount of memory you have.<br>
<br>
You can generally create a bootable CD/DVD from ISO's available at
the sites above and just run that way. I believe there are options
for booting from a USB device, but haven't done this myself. I
think you have to use a Windows system to create the bootable USB
device. You can also install the memory tester as a boot option in
your bootloader if you don't have a suitable optical or USB device.<br>
<br>
Keith<br>
</body>
</html>