On Wed, Dec 13, 2006 at 09:11:29PM +0100, Christoph Anton Mitterer wrote: > - error in the Opteron (memory controller) > - error in the Nvidia chipsets > - error in the kernel My guess without further information would be that some, but not all BIOSes are doing some work to avoid this. Does anyone have an amd64 with an nforce4 chipset and >4GB that does NOT have this problem? If so it might be worth chasing the BIOS vendors to see what errata they are dealing with. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Christoph Anton Mitterer <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Karsten Weiss <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Christoph Anton Mitterer <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Karsten Weiss <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Christoph Anton Mitterer <[email protected]>
- data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Prev by Date: Re: [GIT PATCH] more Driver core patches for 2.6.19
- Next by Date: [PATCH 2.6.19] m32r: Fix do_page_fault and update_mmu_cache
- Previous by thread: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Next by thread: Re: data corruption with nvidia chipsets and IDE/SATA drives
- Index(es):
 |