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.

- 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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I don't think it's a function of the Kernel or anything in the software... Could this be with the Tyan 2880? we've had the same problems. I've spoken with Tyan about it, even went to their office with our server, and they claim it's an error in the CPU, that they can reproduce the problem on a B-stepping CPU, but the problem was corrected by the C-stepping CPU (we're using the 246). Then I spoke with my uncle, who came to visit from Taiwan, where he is one the guys at Phoenix BIOS, who writes the BIOS for Tyan(and almost everyone else). He says that it's a design flaw in the Mobo, and that there is no fix for it, other than run 4GB. which is what we're doing, and it has been stable for a while now running 64-bit MySQL. Kris. Arjen van der Meijden wrote: | Andi Kleen wrote: | |> 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 | three days and eight hours now). So one of the software changes has | resulted in the stability. | |>> - 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 | 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 | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQE/6jKNuBLfyXibQuYRAs+AAJ4tHcHok8T8xqOUnLIEUbqOIC2oNwCgp0g2 Qq8bRBeTXTNfz5j5A4gV8bs= =UcNc -----END PGP SIGNATURE-----