![](https://seccdn.libravatar.org/avatar/72797eb301227cdf055baee4f0a48df0.jpg?s=120&d=mm&r=g)
On Sun, 21 Dec 2003 21:11:13 +0100 Arjen van der Meijden <acm@tweakers.net> 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.
- 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.
And now it is already running for about 5 hours en 52 minutes, without a hick on exactly the same type of load as before (using the full 6G of memory), when it didn't get past the 2 hours.
The question is now: Is our problem solved now? And if so: What did solve it?
When it hits the 24hour mark, we'll probably try a few steps changing back, like booting without the iommu=fullflush and such things.
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. -Andi