XW4100 4GB memory issues

[George Liu_4]

While it works fine when physical memory is 2GB total, the XW4100 workstation has various performance issues when 4GB memory is used. The OS is Redhat EL3.

Does anyone has similar issues?

1. # cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
reg03: base=0xd0000000 (3328MB), size= 64MB: write-back, count=1
reg04: base=0xd4000000 (3392MB), size= 32MB: write-back, count=1
reg05: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
reg06: base=0xf0000000 (3840MB), size= 128MB: write-combining, count=1
reg07: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1

usable memory is 3452MB

2.dmesg excerpt: no more MTRRs available

agpgart: Maximum main memory to use for agp memory: 3299M
agpgart: Detected Intel i875 chipset
agpgart: AGP aperture is 128M @ 0xd8000000
agpgart: Found an AGP 3.0 compliant device.
mtrr: no more MTRRs available
agpgart: Found an AGP 3.0 compliant device.
mtrr: no more MTRRs available
agpgart: Found an AGP 3.0 compliant device.
mtrr: no more MTRRs available
mtrr: no more MTRRs available

3. network connection delay

kernel: tg3: eth0: Link is up at 100 Mbps, full duplex.
Feb 1 12:55:47 kernel: tg3: eth0: Flow control is off for TX and off for RX.
Feb 1 12:55:56 mount: mount: RPC: Remote system error - No route to host
Feb 1 12:56:00 last message repeated 2 times
Feb 1 12:56:17 netfs: Mounting NFS filesystems: failed
Feb 1 12:56:17 netfs: Mounting other filesystems: succeeded

Thanks

[Steven E. Protter]

Looks to me like a networking problem.

Bad card,
bad cable,
bad driver.

thats what I'd check first.

SEP

[George Liu_4]

No issues if there is 2GB memory only.

So it is\
Not Bad card,
Not Bad cable,
Not Bad Hardware

But Bad driver/software.

[Mike Stroyan]

There is some discussion of avoiding MTRR
errors in chapter 5 of this document.
http://h20000.www2.hp.com/bizsupport/CoreRedirect.jsp?targetPage=http%3A%2F%2Fh200002.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00063015%2Fc00063015.pdf
It suggests forcing a larger AGP aperture.
You may also want to see if a newer BIOS will
avoid the problem by changing the memory
addressing. I don't have specific information
that it will help, but if you don't have the
most current BIOS available from
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=314653&Submit.y=7&Submit.x=12&taskId=135&cc=us&locale=en_US&prodTypeId=12454&prodSeriesId=314651&swEnvOID=1080
then it is worth a try.

[NiCK_76]

Hi, George Liu

For your problem we need you to perform command ifconfig. If collisions is high, perhaps switch socket or cable is broken .

NiCK