[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: aptitude not working

From: Riccardo Mottola
Subject: Re: aptitude not working
Date: Mon, 14 Nov 2016 11:53:44 +0100
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40


Richard Braun wrote:
Yes, but specifically :

vm_page: page table size: 786414 entries (43008k)
vm_page: DMA: pages: 4080 (15M), free: 0 (0M)
vm_page: DMA: min:500 low:600 high:1000
vm_page: DIRECTMAP: pages: 233472 (912M), free: 217899 (851M)
vm_page: DIRECTMAP: min:11673 low:14008 high:23347

the "high" threshold. If you add all the high thresholds together,
you'll know how much memory must be free before the pageout daemon

I increased the allocated RAM size of the VM to 1024MB and now I read this:

page table size: 262112 entries  (14335)(
DMA: pages 4080 (15M), free: 0 (0M)
DMA: min:500 low:600 high:1000
DIRECTMAP: pages: 233472 (912M), free: 227669 (889M)
DIRECTMAP: pages min:1228 low:1473 high:2456
HIGHMEM: pages: 24560 (95M), free: 0 (0M)
HIGHMEM: min: 1228 low:1473 high:2456

(btw: can you read out these values later on, with a command similar to dmesg? pausing VirtualBOX and typing out things is boring)
 From what you describe, it doesn't seem to be a hang caused by this.
With your amount of memory, you shouldn't even have a HIGHMEM segment,
which makes bugs even less likely. So I don't know what happened to
your system, or if you're doing something wrong or not. I've just
installed a Hurd system on a VM myself, and I had paging problems
when upgrading from the snapshot to unstable, but once I assigned 2g
of RAM, I could upgrade without too much trouble with aptitude. I
use it on all my machines, Linux and Hurd, and never have such issues.

Now with 1024MB I do have a highmem segment. The issue still happens. Is it actually safer to go back to 768? Aptitude doesn't seem to be memory-bound.

I think something dies: it might have to do with the console, I find it strange that if I type into aptitude while it appears hanging, after killing it in ctrl-c I actually see what I type in console. Do you want a screenshot?

I did an upgrade with apt-get which works fine and which included an aptitude update. I retried aptitude afterwards: having updated everything with apt-get, I just tried to remove package, thus, no actual download needed! Yet it hangs.

If I am doing something wrong, I guess it is not in the usage of aptitude itself, but more in something in my HURD setup?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]