On Sat, 29 Dec 2007, Sandro Tosi wrote: > # debsums | grep -v OK > ... > /usr/lib/gcc/x86_64-linux-gnu/4.2/cc1plus > FAILED > ... > > That was the problem (even if I really don't know how this could be > happened: the pc is new, bought 2 months ago)!! After a
IMO you should do a throughout 48h check on the system memory, and run the smart long self-tests on the disks. That one reeks of data corruption, and bad memory is the most common reason for that, but bad SATA cables or bad disks could also be the cause. There is also the kernel bugs in the filesystem or vfs layers, but I don't know of any such a bug in the field right now... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
