Re: aptitude not working
On Mon, Nov 14, 2016 at 04:52:25PM +0100, Richard Braun wrote: > > (btw: can you read out these values later on, with a command similar to > > dmesg? pausing VirtualBOX and typing out things is boring) Ah, by the way, practically none of us run the Hurd on VirtualBox, and it's known to behave badly in some cases, so you're on your own about that. -- Richard Braun
Re: aptitude not working
On Mon, Nov 14, 2016 at 11:55:46AM +0100, Riccardo Mottola wrote: > how do I know actually which console I am running? could it be meaningful? > I have the issue also when running aptitude from a remote console (e.g. > through telnet) Well, telnet and ssh are remote so they're subject to netdde hangs. The hurd and machs console use the VGA interface (or something similar). You can identify the hurd console by switching to virtual terminals with ALT-FX [1-6]. You can disable it by editing /etc/default/hurd-console. When the hurd console is disabled, the system remains on the default mach console, with a single terminal only. -- Richard Braun
Re: aptitude not working
On Mon, Nov 14, 2016 at 11:53:44AM +0100, Riccardo Mottola wrote: > I increased the allocated RAM size of the VM to 1024MB and now I read this: Try 2g or even 3g. > (btw: can you read out these values later on, with a command similar to > dmesg? pausing VirtualBOX and typing out things is boring) See /var/log/dmesg. > 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'm not sure what's happening there and it's likely a screenshot won't help. > 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. Always keep an eye on swap usage, and maybe /proc/slabinfo. One problem with increasing swap usage is that it requires more kernel objects to track memory, and it can in some cases (and easily with older kernels) exhaust kernel memory. > 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? I don't think you're doing something "wrong", I think we (the developers) know the system enough to avoid most of the caveats. But yes, it's probably caused by a Hurd defect. -- Richard Braun
Re: aptitude not working
Hi Richard, Richard Braun wrote: 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. how do I know actually which console I am running? could it be meaningful? I have the issue also when running aptitude from a remote console (e.g. through telnet) Riccardo
Re: aptitude not working
Hi, 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 stops. 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? Riccardo
