Bug#545125: Intel + KSM still corrupt memory after resuming from suspend to disk
On 14/07/2010 20:18, Julien Cristau wrote:
> On Wed, Jul 14, 2010 at 15:57:32 +0200, Vincent Danjean wrote:
>
>> Even if the problem occurs less often, I still experiment it sometimes
>> with 2.6.32-17.
>> The last time (yesterday), just after a resume, any new processus
>> segfault within the ld.so code... So I rebooted.
>> And today, I discovered, just before submitting a new bug, that the
>> fact that bash core dump each time I hit [tab] or [backspace] was due
>> to a disk corruption of bash binary (ie pb fixed by reinstalling my current
>> version of bash). I will now start a global fsck to check if other
>> on-disk structures have been corrupted or not.
>> So, this bug is not fully fixed.
>>
> I don't suppose it's possible that this was earlier on-disk corruption
> still showing up after the reboot on the new kernel?
Note that before the memory corruption, I boot and made several cycles of
suspend/resume with 2.6.32-17 (this is a improvement with the previous
versions).
Regards,
Vincent
> Cheers,
> Julien
--
Vincent Danjean GPG key ID 0x9D025E87 vdanjean@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main
Reply to: