[nSLUG] X freeze, odd error mssg (kernel panic?)
synrg at sanctuary.nslug.ns.ca
Thu Aug 29 08:32:07 ADT 2013
On 29/08/13 07:22 AM, Dop Ganger wrote:
> Signal 11 per signal(7) is SIGSEV, invalid memory reference. This was
> classically seen when people used to compile their own kernels
> frequently on marginal hardware which would result in memory corruption.
> Try running memtest for a while but it may just have been the machine
> overheating, has it been warm where you are?
> http://www.bitwizard.nl/sig11/ has a collection of FAQs that may help,
> even if it's a little dated ("4 16Mb SIMMs"... Those were the days!)
I *almost* quoted that but because it was so dated, I didn't know if it
was still relevant or not.
By the way, some percentage of RAM problems can be solved simply by
reseating all the RAM.
More information about the nSLUG