I've recently upgraded my kernel from 2.4.21-4 to 2.4.21-37 because of the newer drivers for the raid controller. This didn't help. Last week, we upgraded the firmware from 2.32 to 2.48 and upgraded the cache memory from 128 tot 512 MB. I'll have to watch the server for a while to see if this helped. I'll post when I know more.

Turning off HT is an option enabled by default in most BIOS', might take a little bit of searching around in the menu's but it'll be in there somewhere. Simply set to 'Disabled' and that psuedo-cpu/s should disappear.

We have some hard disk problems on a Proliant 64xx controller. The machine works ok when we put 300 GB + 150 GB disks in Raid 0 config to get a total of 300 GB space. But if we put 300 GB + 300 GB disks - the disks randomly go into read only or the superblock becomes inaccessible.

We are using RHEL4 with kernel-smp-2.6.9-22.

If anyone has faced such a problem or has some clue about the source of the problem - do tell.

For the above problem - after the disk goes into read only mode... it becomes inaccessible....

dmesg gives output lines saying -

Buffer I/O error on device cciss/c1d0p1, logical block xxx
EXT3-fs error (device cciss/c1d0p1) in start_transaction: Journal has aborted

And now this problem is coming with the 300+150 disks as well...

To be more correct: with RHEL 3 and 800MHz Xeons

We are a hosting company and have several dozen dual Xeons running on RHEL 3 and have been using it since it came out. October last year our stock of Xeons 533 MHz was depleted and we where thinking about making the switch to 800 MHz machines.
The first server we replaced was one with about 300 domains on it and the very same day we started getting calls the machine was very slow. We imidiatly switched back to a 533 MHz and it all was back ok.
Then we started testing with different MoBo's with different chipsets (all Supermicro), got new BIOS updates from them, the works. On Xeon 533 MHz: no problem, on 800 MHz: big problem. We havent tested on higher MHz boards yet.

As a professional hosting company we cant afford to just test it under pressure (with clients on it reading a lot of files), so we bought up all the 533 Xeons we could find and now are waiting for RHEL 5 to be released.

Regards
Jan

Hello guys,

I had same problem with one of my RHEL4 server and the problem was high swap usage and cpu usage due to mysql process. I had upgraded the kernel and it was fixed itself after a reboot.

Again today, I have upgraded kernal on another server (RHLE3 server) on which i was suffering with high IOWAIT. It seems to br workning peferct after reboot.

Very simple to upgrade for RHEL

(SEE CURRENT VERSION)
$ uname -r


(UPGRADE)
$ up2date -if kernel


---Cheers