Noah Meyerhans wrote: [snip] > The call trace in this latter case isn't always the same, but free_block > does always seem to be at the top of the stack. > > It's quite possible that this is a hardware problem. Do others concur? > Is there any chance that it is software? If it is hardware, my > inclination would be to suspect RAM. Does anybody have a decent source > for Cobalt Raq2 memory?
As the easiest and cheapest option, did you try to re-seat the RAM module? Apparently the connectors corrode slightly over time, re-seating the module and probably treating the module's contact pads with an eraser rubber can help in that case. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
