[nSLUG] X freeze, odd error mssg (kernel panic?)
dguptill at accesswave.ca
Thu Aug 29 09:49:04 ADT 2013
On Thu, Aug 29, 2013 at 08:32:07AM -0300, Ben Armstrong wrote:
> 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.
While reseating the RAM, you might take an eraser to the contacts.
Use a clean soft one, like on the end of a new pencil.
Bold character derived from stubborn patience and adversity.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: Digital signature
More information about the nSLUG