I suddenly couldn't send to the mailinglist any longer.. I'm going back to 2.4.28 for now. My 4GB of RAM support was already turned off.. Good luck further. Here is my mail:
On Monday 17 January 2005 22:34, you wrote:
omes wrote:
I have the same problem as you. At least our problems are much alike. I got two Western digital hard disks. One 120GB 7200RPM 2MB Cache IDE, and one 80GB 7200 2MB Cache IDE. I get high loads when reading large files for some time, as well as when copying from one partition to another. All my partitions are in ext3, and i'm running 2.6.10.
I have a similar problem. I am running 2.6.9 on FC3 not the stock kernel, but a vanilla kernel. I have 3 NFS shares mounted on this 2.6.9 machine (ASUS P4C800 ICH5 motherboard with 1024 MB RAM and sk98lin gigabit LOM (non-functional since thesk98lin driver broke apart) so i use an additional 3Com 3C59x 100 Mbps adapter, with a nvidia VGA adapter, but no nvidia modules but only VESAFB at 1024x768.
This is the same series as i got P4C800/P4P800..
Gabriel worte this in an earlier post: "The performance issues (below) where due to a strange bug in the kernel VM triggered by the motherboard BIOS. This affects Asus P4P800 motherboards(-MX and -VM tested) with more that 1 GB RAM. The built-in
I have exactly 1GB.
I don't have 4GB support, nor do i have shared VGA. I have a nvidia(64M onboard, not shared) card using vesafb.VGA can use 1-32 MB RAM for display but configured with less than 16 MB of video RAM the board will behave EXTREMELY poor in linux (2.6.9 also tested to behave like this).
No X either.
It was broken when i tried it out on 2.6.7 i think, and i stumbled upon the a post stating about incorrect VPD entries.. So i thought i would wait for things to cool down a bit.There are several ways around this problem, I've just configured the board with 16 MB of video RAM. Disabling support for 4 GB of RAM works too but more memory is lost this way. Running FreeBSD is also an option but we don't like that, don't we ? Memtest86 (1.11) doesn't seems affected either - but it detects the memory as "single channel" while memory is installed in dual channel configuration (also confirmed by BIOS).
If anybody knows what's going on please let me know. Loosing 15 MB of RAM is not a big deal but I like linux bug-free, fast and stable.
I'm available to give more details or run some tests if anyone cares.
Regards,
Gabriel" (adapted)
As for the LOM, use this driver comes with the kernel: Device Drivers -> Networking support -> Ethernet (1000 Mbit) -> Marvell Yukon Chipset / SysKonnect SK-98xx Support
Manu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
