cat /proc/meminfo reports that I have ~34 TB allocated. Yet, at the moment, my system seems very fast, even my VM under VMware seems fast. uptime reports: 14:30:03 up 23:01, 3 users, load average: 0.51, 0.43, 0.42
I've noticed though that every time my system slows to a halt (music pauses, mouse freezes), 34 TB has been allocated right after I start up VMware. After a while, the system stabilizes and gets fast again. What's going on here?
I'm using Ubuntu Dapper 6.06 64-bit. My friend's 32-bit Dapper system also has VMware and he doesn't have this issue. This has happened at least five times on mine. There's hardly a time I type meminfo and don't read 34 TB.
Kernel (which is custom compiled with reiser4 support): Linux ubuntu 2.6.16.18 #1 SMP PREEMPT Sun May 28 16:28:58 EDT 2006 x86_64 GNU/Linux
My friend is using a default 2.6.15-25-686 Ubuntu kernel, so maybe that is why he doesn't have the problem. Is there a bug in 2.6.16.18?
I've noticed though that every time my system slows to a halt (music pauses, mouse freezes), 34 TB has been allocated right after I start up VMware. After a while, the system stabilizes and gets fast again. What's going on here?
I'm using Ubuntu Dapper 6.06 64-bit. My friend's 32-bit Dapper system also has VMware and he doesn't have this issue. This has happened at least five times on mine. There's hardly a time I type meminfo and don't read 34 TB.
Kernel (which is custom compiled with reiser4 support): Linux ubuntu 2.6.16.18 #1 SMP PREEMPT Sun May 28 16:28:58 EDT 2006 x86_64 GNU/Linux
My friend is using a default 2.6.15-25-686 Ubuntu kernel, so maybe that is why he doesn't have the problem. Is there a bug in 2.6.16.18?