Hi Robert,
I did some tests.
On 2018-03-10 00:01:27 + Robert Elz wrote:
| X does not get "killed" either, I do not return to console.
If it gets killed, that (not returning to console) is expected.
| On this system usually the X driver is decently well-behaved,
Date:Fri, 9 Mar 2018 22:53:57 +0100
From:Riccardo Mottola
Message-ID: <2135aaf6-afc5-f10b-1511-cf59e0df2...@libero.it>
| X does not get "killed" either, I do not return to console.
If it gets killed, that (not returning to console) is
Hi.
On 09/03/2018 17:14, m...@netbsd.org wrote:
I strongly suspect you are running out of RAM due to lang/rust not
respecting MAKE_JOBS and linking in parallel, killing Xorg.
I've seen the same.
You can tell if normal shutdown works fine and you get a message in UVM
about Xorg being killed
On 09/03/2018 16:14, m...@netbsd.org wrote:
I strongly suspect you are running out of RAM due to lang/rust not
respecting MAKE_JOBS and linking in parallel, killing Xorg.
The rust compiler is multi-threaded so 1 process can use all the cores
of the system all on its own. However if you have
You can confirm this by reading /var/log/messages
It will look like:
UVM pid 123 (X) killed: out of swap
I strongly suspect you are running out of RAM due to lang/rust not
respecting MAKE_JOBS and linking in parallel, killing Xorg.
I've seen the same.
You can tell if normal shutdown works fine and you get a message in UVM
about Xorg being killed
So it's three bugs:
- lang/rust doesn't respect
Hi All,
I upgraded 7.1.1 on my ThinkPad R51 (this means x86 32bit single core),
the machine was rock stable 7.1, it is not with 7.1.1
In a couple of hours it crashed several times: it means it "hangs", I
need to power-cycle.
What I do is starting a package upgrade (in specific, rust, which