From: Deian Chepishev <deian@blue-edge.bg>
To: Maetee Maitri <new@ji-net.com>
Cc: tsd@asus.com, linux-kernel@vger.kernel.org
Subject: Re: P4P800-VM - ASUS - HIGH MEMORY extremely slow under some circumstaces - LOG FILES - added
Date: Thu, 08 Jan 2004 10:01:12 +0200 [thread overview]
Message-ID: <3FFD0E48.1090308@blue-edge.bg> (raw)
In-Reply-To: <3FFD09F1.2020702@ji-net.com>
I guess it will work if i do it like you have said but i had not much
time to play with that. I have done some further investigation and found
the following dependency:
Since my RAM is on 4 dims 512MB each i started to remove them one bu
one. First removed both dims on the second channel. Still the same
problem. But when i removed the third dimm and on the mainboard left
only one the problem did not appear. I guess that either the chipset has
some bug when allocating memory for the video card or ASUS have made
really poor implementation.
That is why i installed external AGP video card and disabled that one on
the main board and the problem have gone.
Maetee Maitri wrote:
> Hi,
>
> I just upgrade from P4 1.8G on GIGABYTE GA-8IGX (Intel 845G) to P4
> 2.4c on ASUS P4P800-VM and have the similar problem. My system runing
> RedHat 7.3 kernel 2.4.18-26.7.x. My system have only 1G RAM (2x512M
> DDR400). both of them set to use only 1M video ram.
>
> I notice that the setting of difference video RAM and AGP aperture
> size in BIOS affected speed of system.
> I see that /proc/mtrr on P4P800-VM has 6 lines and GA-8IGX has 2 lines.
>
> GA-8IGX:
> reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
> reg01: base=0x3ff00000 (1023MB), size= 1MB: uncachable, count=1
>
> P4P800-VM:
> reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
> reg01: base=0x20000000 ( 512MB), size= 256MB: write-back, count=1
> reg02: base=0x30000000 ( 768MB), size= 128MB: write-back, count=1
> reg03: base=0x38000000 ( 896MB), size= 64MB: write-back, count=1
> reg04: base=0x3c000000 ( 960MB), size= 32MB: write-back, count=1
> reg05: base=0x3e000000 ( 992MB), size= 16MB: write-back, count=1
>
> Why a lot of region???
> I try to clear all mtrr on P4P800-VM and set the new one base on GA-8IGX:
>
> [root /]# echo "disable=5" >| /proc/mtrr
> [root /]# echo "disable=4" >| /proc/mtrr
> [root /]# echo "disable=3" >| /proc/mtrr
> [root /]# echo "disable=2" >| /proc/mtrr
> [root /]# echo "disable=1" >| /proc/mtrr
> [root /]# echo "disable=0" >| /proc/mtrr
> [root /]# echo "base=0x00000000 size=0x40000000 type=write-back" >
> /proc/mtrr
> [root /]# echo "base=0x3ff00000 size=0x00100000 type=uncachable" >
> /proc/mtrr
>
> Yes!! It work, My system come fast again. the new /proc/mtrr show below:
> [root /]# cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size=1024MB:
> write-back, count=1
> reg01: base=0x3ff00000 (1023MB), size= 1MB: uncachable, count=1
>
> For your 2G RAM machine. You may change size of first region from
> 0x40000000 (1G) to 0x80000000 (2G). The value of base and size of
> second region base on your video RAM setting in BIOS.
>
> Hope this solution will work on your system too.
>
> Maetee Maitri
>
>
>> Hi,
>>
>> I have ASUS P4P800-VM mother board.
>> Chipset: Intel 865G GMCH
>> Intel ICH5 - 800MHz FSB
>>
>> BIOS Revision: 1007
>>
>> Embedded LAN : Intel 82562EZ
>> Embedded Graphics: Intel Extreme Graphics 2
>>
>> RAM 2G 4x512M DDR400 Samsung
>> HDD IDE Seagate Barracuda 120G
>> Processor: P4 - 2.6 GHz HyperThreading
>>
>> OS: Slackware Linux 9.1
>>
>> Description of the problem:
>>
>> I have installed 2 GB memory 4x512M
>> The embedded video uses system memory. If i set it to use only 1 MB or
>> 32MB of system RAM everything seems ok. The system boots normally and
>> working normally.
>> If i set it to use 4,8 or 16 MB of the system memory the system boots
>> much slower and despite it has no errors or something wrong it works
>> slow. I mean the difference between fast and slow working is really
>> HUGE.
>> I have made the following test: in a 600MB text file replace some text
>> with sed. The line looks like this:
>>
>> sed s/deian/test/g testfile > /dev/null
>>
>> when the system is working normally this is done for ~ 30sec. When the
>> system is working slowly it takes ~ 9 min and 30 sec.
>> I have tested this with kernel 2.4.23 from kernel.org. High memory
>> support is enabled - 4GB. If i have no high memory support enabled the
>> thing are ok but the kernel see only 900MB of my memory.
>> The other strange thing is that with kernel 2.6 the system works
>> normally ONLY IF video card uses 32MB. It is not like with 2.4.23 when 1
>> and 32M but only with 32MB.
>>
>> I dont think this is normal behavior. And i hope that the problem is not
>> the chipset or hardware. I have searched the news groups and other
>> people has the same problem too but no solution yet.
>> I have attached some logs which may help u find what is wrong. If u need
>> me to do something more just mail me i shall respond as fast as i can.
>> Regards,
>>
>> Deian Chepishev
>>
>
> Maetee Maitri
>
>
next prev parent reply other threads:[~2004-01-08 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 7:42 P4P800-VM - ASUS - HIGH MEMORY extremely slow under some circumstaces - LOG FILES - added Maetee Maitri
2004-01-08 8:01 ` Deian Chepishev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 13:55 Deian Chepishev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FFD0E48.1090308@blue-edge.bg \
--to=deian@blue-edge.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=new@ji-net.com \
--cc=tsd@asus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox