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?
It is always possible. But the problem appears just after the reboot due
to the bad resume (and here I'm sure that memory was corrupted because
ld.so work perfectly since the reboot). So it would be a strange
coincidence.
The forced fscks on all my partitions do not detect any other problems
(of course, fsck would not tell anything about data integrity within
files)
> Cheers,
> Julien
[
as a side note, I discovered that trying to reinstall bash and its dependency
with one apt-get command fails:
vdanjean@eyak:~$ sudo apt-get install --reinstall bash base-files debianutils dash libc6 libncurses5 bash-completion
[...]
Do you want to continue [Y/n]?
E: Could not perform immediate configuration on 'bash'.Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
vdanjean@eyak:~$
Do you know if this is expected or if this is a bug (of apt I suppose)
]
Regards,
Vincent
--
Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble
Téléphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot
Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann
Email: Vincent.Danjean@imag.fr 38330 Montbonnot Saint Martin
Reply to: