also sprach martin f krafft <[email protected]> [2014-08-05 16:15 +0300]:
> > It's possible that this was caused by a memory corruption, but it
> > wouldn't have been high on my suspect list. Still, if this is
> > a new machine, it might not be a bad idea to run memtest86+ for
> > 24-48 hours.
>
> … and will do that. I did it before, but I also just upgraded the
> RAM and didn't do it again.
For posterity, the problems went away after I memtest86+-identified
a bad RAM module and swapped it, then recreated the filesystems for
safety,
Thanks Ted!
--
@martinkrafft | http://madduck.net/ | http://two.sentenc.es/
will kill for oil!
spamtraps: [email protected]