Bug 433907

Description of problem:
Hardware: Asus M2A-VM MB, AMD 64 dual core 2x2MB dual channel corsair ram

If I install Fedora Core 8, click on the "suspend" (S3/Suspend to Ram) option
from the gui, the computer suspends. At this point, there are no problems. When
I attempt to resume, there is massive filesystem corruption. It may or may not
resume to a semi-functional state. When it does, the suspend and resume logs
show no errors. The first errors appear when I try to access files that have
been mutilated.

There is not pattern to said corruption. It sometimes affects only some files,
and can be fscked back to life (albeit with lots of corrupted inodes, spread
over the disk). Sometimes it destroys the grub installation.

This is true for pm-suspend and direct access to /sys/power/state and
/proc/acpi/sleep even if the gui is not running.

It occurs in the ram filesystem when booting from the live CD (indicating that
this may not be pata ide driver specific). It occurs using tuxonice (custom
atrpms kernel), swsusp, uswsusp. Found in the default kernel, the latest patch,
and the alpha kernel (2.6.24) from FC9. I reproduced this in Ubuntu, and its
livecd. I reproduced it in the latest stable kernel.org generic kernel.

When the corruption occurs, there is usually no relevant log entry (until it
starts finding the filesystem corruptions). The "resume" can appear to work with
no problems. Hence there is nothing to attach.

This is reproduced with many permutations of possible BIOS parameters, as well
as with 3 different manufacturer provided BIOS'es.

If I reboot after suspend (but without the resume) things are fine.

Key observation: If I remove 2GB of memory, there are no problems whatsoever.
This doesn't depend on which SIMM, and both have passed lengthy memchecks.

This looks like a x86_64 kernel problem, and is certainly not specific to
Fedora. In fact, it could very well be a bug in the MB/BIOS, given that I can
find few others that have had the problem. Nonetheless, it's such a nasty
problem that I felt I should document it here, and hope that you can point me in
the right direction as far as reporting it elsewhere. Thanks!

Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. Install Fedora
2. Boot
3. Click on Logout --> suspend
  
Actual results:
The filesystem is corrupted beyond repair

Expected results:
Anything else! :)

Additional info: