OS/2, eCS & ArcaOS - Technical > Hardware
Monitor suggestions
Dariusz Piatkowski:
Hi Andi,
--- Quote from: Andi B. on December 08, 2024, 10:30:46 am ---Now I've here two systems which behave very strange when trying to use VIRTUALADDRESSLIMT = 3072. I've not a single system/installation which works okay with this setting. I've the same intermediate 'out of memory' errors loading some programs...
--- End quote ---
What other device drivers, especially the IFS stuff, are you loading? What size cache are you defining for these?
The symptoms you describe all look & feel like the "out of memory" stuff I was seeing when testing the very large (>1G) JFS cache sizes here.
On a running system, can you capture the output of mem.exe?
Here is what I see after 2 days of uptime:
--- Code: ---[G:\util\misc]mem /v
Total physical memory: 12,287 MB
Accessible to system: 3,327 MB
Additional (PAE) memory: 8,960 MB
Resident memory: 1,187 MB
Available virtual memory: 430 MB
Available process memory:
Private low memory: 179 MB
Private high memory: 1,344 MB
Shared low memory: 67 MB
Shared high memory: 282 MB
--- End code ---
Can you do this BEFORE and AFTER the issue appears?
Per E. Johannessen:
Forgot to mention that chkdsk has been run several times without any errors and nothing in populog either.
Although the Radeon offers lots of resolutions it's not stable enough for the time being.
I put back the Nvidia RTX 4060 Ti and connected with DP it now offers a max resolution of 1920x1080 and so far it seems stable
with VIRTUALADDRESSLIMIT = 2816
Andi B.:
--- Quote ---What other device drivers, especially the IFS stuff, are you loading? What size cache are you defining for these?
The symptoms you describe all look & feel like the "out of memory" stuff I was seeing when testing the very large (>1G) JFS cache sizes here.
--- End quote ---
I usually let the IFS stuff as it is defined by ArcaOS installer. For older systems I also don't have big JFS cache. HPFS386 is remed out since long as it produces similar problems.
'mem -v' - my last tests on a pretty vanilla ArcaOS system I build up last week leads to 'out of memory' even when trying to open 4os2 or cmd windows. Sometimes afterwards it magically worked for one session but no more. -> very weird behavior with VIRTUALADDRESSLIMIT=3072. Reminds me on same experience a few years ago with another system.
So for me I can't get any system to work only near reliable with 3072. Wild guess, it may interfere with my 3840 x 2160 resolution. My observations lead me to guess there is a memory problem with the WPS or gradd or VMAN or ... with this high resolution too.
Administrator - this now runs very off topic. Maybe you wann split this thread. Thanks.
Dave Yeo:
I think the problem is that IBM never finished the high memory support, or perhaps just buggy. PCI space, which is at the top of the 4GB address range, has grown with newer hardware. You put a video card in that uses address space for its large frame buffer and its BIOS and it takes up a bunch of address space. The JFS cache seems to be implemented up there too. So with 3072 virtualaddress space, it interferes with PCI address space and/or JFS address space and you get an unstable system. So you need a smaller virtualaddress space to be stable.
mem /v should tell you how much memory is accessible to the system, which should point to how much virtualaddress space you can use. Here, it is 3,502MB and using 3072 seems fine.
Per E. Johannessen:
Below is the output of mem /v
With VIRTUALADDRESSLIMIT=2816 the system seems stable.
I'm on thin ice here so, as always, I welcome comments.
Total physical memory: 16,102 MB
Accessible to system: 1,766 MB
Additional (PAE) memory: 14,336 MB
Resident memory: 290 MB
Available virtual memory: 1,382 MB
Available process memory:
Private low memory: 288 MB
Private high memory: 2,012 MB
Shared low memory: 234 MB
Shared high memory: 1,729 MB
Navigation
[0] Message Index
[*] Previous page
Go to full version