I was looking through my system log because I finished my first pre-clear, but I noticed at the top of the log It says: "AMI BIOS detected: BIOS may corrupt low RAM, working around it." What does this mean? My the time and date are incorrect because I forgot to set it in the settings so this would have been Sunday that this happened (I just finished building it on Sunday). I have posted below the log up until the error if that makes any difference. I have a core i3-540 with 4 gigs of ram on the Supermicro X8SIL-F motherboard.

 

ec  6 16:33:04 Tower syslogd 1.4.1: restart.

Dec  6 16:33:04 Tower kernel: klogd 1.4.1, log source = /proc/kmsg started.

Dec  6 16:33:04 Tower kernel: Linux version 2.6.32.9-unRAID (root@Develop) (gcc version 4.2.3) #5 SMP Wed Jun 16 20:45:26 MDT 2010

Dec  6 16:33:04 Tower kernel: KERNEL supported cpus:

Dec  6 16:33:04 Tower kernel:  Intel GenuineIntel

Dec  6 16:33:04 Tower kernel:  AMD AuthenticAMD

Dec  6 16:33:04 Tower kernel:  NSC Geode by NSC

Dec  6 16:33:04 Tower kernel:  Cyrix CyrixInstead

Dec  6 16:33:04 Tower kernel:  Centaur CentaurHauls

Dec  6 16:33:04 Tower kernel:  Transmeta GenuineTMx86

Dec  6 16:33:04 Tower kernel:  Transmeta TransmetaCPU

Dec  6 16:33:04 Tower kernel:  UMC UMC UMC UMC

Dec  6 16:33:04 Tower kernel: BIOS-provided physical RAM map:

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 0000000000000000 - 000000000009d800 (usable)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 0000000000100000 - 00000000bf790000 (usable)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000bf79e000 - 00000000bf7a0000 type 9

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000bf7a0000 - 00000000bf7ae000 (ACPI data)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000bf7ae000 - 00000000bf7d0000 (ACPI NVS)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000bf7d0000 - 00000000bf7e0000 (reserved)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000bf7ed000 - 00000000c0000000 (reserved)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000fed20000 - 00000000fed40000 (reserved)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)

Dec  6 16:33:04 Tower kernel:  BIOS-e820: 0000000100000000 - 000000013c000000 (usable)

Dec  6 16:33:04 Tower kernel: DMI present.

Dec  6 16:33:04 Tower kernel: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

Dec  6 16:33:04 Tower kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)

Dec  6 16:33:04 Tower kernel: last_pfn = 0x13c000 max_arch_pfn = 0x1000000

Dec  6 16:33:04 Tower kernel: MTRR default type: uncachable

 

Linux is detecting an AMI Bios.  Developers in the past determined that SOME AMI BIOS will corrupt the lower 64k of memory during a suspend/resume.  To work around it the Linux kernel just avoids using the segment of memory that the BIOS might write to.

 

See here: http://fixunix.com/kernel/557785-patch-03-49-x86-reserve-low-64k-ami-phoenix-bios-boxen.html

 

Your specific BIOS may or may not be one that writes to that block of memory.  The Linux kernel has protected you from having to find  out the hard way of the corruption.

Thanks Joe.