IS> Date: Thu, 13 Apr 2006 22:24:22 +0200
IS> From: Ignatios Souvatzis

IS> Let me add that the error occurs at the page boundary because that's
IS> where disk DMA usually starts...

That sounds plausible.  If DMA weren't involved, and it were strictly a 
RAM timing problem, might one instead expect errors on memory page 
boundaries?  Note that, in this case, I use "memory page boundaries" to 
describe the RAM's physical layout -- not in MMU-related context as has 
been discussed so far.


Eddy
--
Everquick Internet - http://www.everquick.net/
A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 785 865 5885 Lawrence and [inter]national
Phone: +1 316 794 8922 Wichita
________________________________________________________________________
DO NOT send mail to the following addresses:
davidc@brics.com -*- jfconmaapaq@intc.net -*- sam@everquick.net
Sending mail to spambait addresses is a great way to get blocked.
Ditto for broken OOO autoresponders and foolish AV software backscatter.