I am sorry for the bug report. The fault is mine. I realized I had been
changing at some point login.conf. When I made a diff to the original I
found a typo. ( :datasize-cur=2048:\ vs :datasize-cur=2048M:\ )
46,51c46,51
< :datasize-max=512M:\
< :datasize-cur=512M:\
< :maxproc-max=256:\
< :maxproc-cur=128:\
< :openfiles-cur=512:\
< :stacksize-cur=4M:\
---
> :datasize-max=2048M:\
> :datasize-cur=2048:\
> :maxproc-max=1024:\
> :maxproc-cur=1024:\
> :openfiles-cur=2048:\
> :stacksize-cur=16M:\
75c75
< :datasize-cur=512M:\
---
> :datasize-cur=2048M:\
77,78c77,78
< :maxproc-max=512:\
< :maxproc-cur=128:\
---
> :maxproc-max=1024:\
> :maxproc-cur=1024:\
On 09/11/13 14:30, Lars Engblom wrote:
In recent snapshots, I can not do a console login anymore. *dm, like
xdm works still. The latest message is the date on ttyC0.
authlog is full of this kind of messages:
init: can't exec getty '/usr/libexec/getty' for port /dev/ttyC0:
Cannot allocate memory
I somehow suspect this came together with radeon fb, but I am not
sure. With this particular computer, I will not have a chance to
revert to an older snapshot for testing this theory.
I have attached dmesg.
