System Crashes With Memory Remapping Enabled

Hi @all
About a week ago I re-installed 64 bit SuSE 10.3 with memory remapping enabled on my C2D 6420 @Asus P5B-E with 4 GB RAM installed because the default kernel *and* bios would only see 3 GB. Installation went just fine. But when I copied all backups back to the machine via network the system crashed completely (hardware reset necessary) several times after having copied very few GByte no matter if I copied from the backup machine running Windows XP to the Linux machine or vice versa. Because the Linux machine ran fine without memory remapping enabled I disabled the setting again - and no crashes since then. I could copy all my several hundreds GByte of data back to the Linux machine without a single crash.
Is this issue known to anyone?
At the moment 3 GB are fairly enough but if there is a simple way to use all installed memory it would be great. (The machine will probably host some VMs in the future.)
Could the bigsmp kernel help me? If yes, why did the installation routine not install it? Remapping was enabled during installation.

Complete hardware:
Asus P5B-E
Intel C2D 6420 (not overclocked)
4 * 1 GB Infineon original 666 MHz
ATI 1050
4 * 500 GB Seagate SATA (no Raid) @onboard ports

Hi there, would it possible for you to post about how you did the memory remapping? I'd like to do the same as well (I'm only seeing 3.2 GB of RAM when I've got 4 GB installed).

Thanks

Hi there, would it possible for you to post about how you did the memory remapping? I'd like to do the same as well (I'm only seeing 3.2 GB of RAM when I've got 4 GB installed).

Thanks
[/b]

I just enabled the corresponding bios setting.
In the meantime I read a lot about this stuff. Many bioses don't handle the setting correctly and that probably's the reason for my crashes. Maybe a bios setup would help - but the machine is running stable with 3 GB addressable which is fairly enough at the moment.
Never touch a running system.

problems with >3GB RAM are not related to OS but hardware (e.g. PCI hole). Main reason why MS does not push something which on ****py (sorry) hardware is not possible (any cheap = desktop mobo). When you get expensive 64-bit only (meaning no legacy) mobo more RAM is fine otherwise not crashing does not mean efficiently used. Still hardware problem, not software.
some cheap mobos simply do not handle memory problems at all, other claim that can but crash, few can and still problems persist (except crashing).

AGP aperture size in BIOS setup to 64M increases the usable memory to about 3.3 GB. So bigger AGP aperture less memory available. This is only one example of memory handling not related to OS at all.