El día miércoles, marzo 15, 2017 a las 01:28:02p. m. -0000, Alexey Dokuchaev escribió:
> Some more ideas, from most to least probable:
>
> 1. We're dealing with some kind of stack corruption, e.g. because large
> object (or large number of objects) is allocated on stack, or local
> buffer gets overrun, destroying return address and we end up trying to
> resume execution from wrong memory.
>
> 2. Can you try to restart X11 server with VESA backend (slow) and see if
> it changes anything?
The Acer C720 run all in VESA mode because the Haswell is not yet supported in FreeBSD.
> 3. Faulty memory. You might try replacing RAM sticks (unless they're
> soldered) or run memtest86+ (e.g. from a live bootable CD as I recall
> FreeBSD port is broken on amd64).
I know three C720, all with the same crash in stellarium; this deletes
this option number 3, I think;
El día miércoles, marzo 15, 2017 a las 01:28:02p. m. -0000, Alexey Dokuchaev escribió:
> Some more ideas, from most to least probable:
>
> 1. We're dealing with some kind of stack corruption, e.g. because large
> object (or large number of objects) is allocated on stack, or local
> buffer gets overrun, destroying return address and we end up trying to
> resume execution from wrong memory.
>
> 2. Can you try to restart X11 server with VESA backend (slow) and see if
> it changes anything?
The Acer C720 run all in VESA mode because the Haswell is not yet supported in FreeBSD.
> 3. Faulty memory. You might try replacing RAM sticks (unless they're
> soldered) or run memtest86+ (e.g. from a live bootable CD as I recall
> FreeBSD port is broken on amd64).
I know three C720, all with the same crash in stellarium; this deletes
this option number 3, I think;