On Sun, 21 Dec 2003 21:11:13 +0100 Arjen van der Meijden
wrote: First of all, does that explain the 1.5G swapusage? As in: would it use 1.5G of swap if the memory is broken, even if there is plenty of diskcache to remove?
Broken memory has nothing to do with swapping. I'm just commenting on how the oops looks like. I don't know what causes the swapping.
It could be memory corruption from a bad driver too, but usually bad memory is the first guess. Well, the machine is still running stable since my previous email (over
- Changed our 32bits mysql to use less than 2G of memory instead of more (mysql (actually, innodb) used to crash itself when it was configured with more than 2G of memory available to its buffers and such, due to issues with glibc orso).
Best would be to run some memory and IO checker independent of mysql just to verify that both IO and memory work reliably on your system.
e.g. run http://people.redhat.com/dledford/memtest.html for some time. We have run quite a few tests (including a few heavy mysql tests and
Andi Kleen wrote: three days and eight hours now). So one of the software changes has resulted in the stability. that memorytest, or a similar tool) before putting the machine into production use, we were very surprised by its instability after putting it into production.
You need a new kernel for that option, it is not in the 9.0 kernel. like the kernel in ftp://ftp.suse.com/pub/people/ak/test12/* It will only do anything if your IO device uses the IOMMU. This would generally only happen if it's IDE based of some sort, most other IO devices are not crippled and can access the full address space without assistance. It becomes quite hard to track/deduce what caused the instabilities now :)
If we find out what did, we'll let you know. Best regards and a merry christmas, Arjen van der Meijden