Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Ewen Chan
Aivils: The output of the ps aux command gives the following column headers: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND Per the ps(1) man page: VSZ virtual memory size of the process in KiB (1024-byte units). Device mappings are currentl

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Vladimir Dergachev
On Tue, 5 Dec 2017, Ewen Chan wrote: I'm a little bit confused by your reply here. X is a network protocol, so it can be used to render to a remote display. ssh -Y performs the forwarding over the tunnel. However, in practice the forwarding only works for applications with modest interfac

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Vladimir Dergachev
Keep in mind that Xorg will show memory usage from mapping graphics memory.. which could be large on your card. Also, are you using CUDA ? best Vladimir Dergachev On Wed, 6 Dec 2017, Hi-Angel wrote: Oh, wow, this looks like a Xorg bug then. I'd recommend trying latest Xorg then — yours o

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Vladimir Dergachev
Also, given the the high usage does not happen outside of gnome session, perhaps this is connected to compositing.. best Vladimir Dergachev On Wed, 6 Dec 2017, Hi-Angel wrote: The troubleshooting link you provided states that the high memory usage typically belongs to some other applicatio

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Hi-Angel
On 6 December 2017 at 15:25, Vladimir Dergachev wrote: > > Keep in mind that Xorg will show memory usage from mapping graphics memory.. > which could be large on your card. > > Also, are you using CUDA ? I don't think Matrox provides CUDA functional. @Ewen, by the way, this mail pushed me to ano

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Hi-Angel
On 7 December 2017 at 05:45, Hi-Angel wrote: > On 6 December 2017 at 15:25, Vladimir Dergachev > wrote: >> >> Keep in mind that Xorg will show memory usage from mapping graphics memory.. >> which could be large on your card. >> >> Also, are you using CUDA ? > > I don't think Matrox provides CUDA

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Ewen Chan
Hi-Angel: Thank you for that!!! Two questions: 1) Will the commands from the CentOS distro work with SuSE? 2) Do you think there will be problems using the VESA driver instead of the mgag200 driver? (i.e. the GUI/remote X/VNC would exhibit unexpected behaviours? Thanks. Sincerely, Ewen On We

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Hi-Angel
On 7 December 2017 at 06:05, Ewen Chan wrote: > Hi-Angel: > > Thank you for that!!! > > Two questions: > > 1) Will the commands from the CentOS distro work with SuSE? Well, the linked post doesn't show how to blacklist because it was created after the fact (author forgot to re-build initramfs). F

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Ewen Chan
Thanks. I'll have to try that. (The thread links to another CentOS thread that talks about how. I just wasn't sure if the commands were a 1:1 match.) On Wed, Dec 6, 2017 at 10:19 PM, Hi-Angel wrote: > On 7 December 2017 at 06:05, Ewen Chan wrote: > > Hi-Angel: > > > > Thank you for that!!! >

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Hi-Angel
On 7 December 2017 at 06:19, Hi-Angel wrote: > On 7 December 2017 at 06:05, Ewen Chan wrote: >> Hi-Angel: >> >> Thank you for that!!! >> >> Two questions: >> >> 1) Will the commands from the CentOS distro work with SuSE? > > Well, the linked post doesn't show how to blacklist because it was > cre

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Ken Moffat
On Thu, Dec 07, 2017 at 07:39:27AM +0300, Hi-Angel wrote: > > On 7 December 2017 at 06:05, Ewen Chan wrote: > > You know, btw, another silly idea: if blacklisting the driver will > help, but you actually care of graphics performance — you could try > enabling it back, and then installing modesett

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Ewen Chan
Thanks. I just tried the blacklisting right now so it will be some time (as I re-run my tests) to find out whether that worked or not. Thanks. On Thu, Dec 7, 2017 at 12:17 AM, Ken Moffat wrote: > On Thu, Dec 07, 2017 at 07:39:27AM +0300, Hi-Angel wrote: > > > On 7 December 2017 at 06:05, Ewen

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Ewen Chan
Stupid question though (again, I'm a grossly underqualified sysadmin). How can I tell if the blacklisting worked correctly? When I type in: # lspci -v | more this is what it outputs for the VGA section: 08:01.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Felix Miata
Ewen Chan composed on 2017-12-07 00:32 (UTC-0500): > 08:01.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA > G200eW WPCM450 (rev 0a) (prog-if 00 [VGA controller]) Seeing this thread get so long makes me curious. I'm neither dev nor all that familiar with th

Re: X is consuming ~100 GiB of RAM(!)

2017-12-06 Thread Hi-Angel
Don't worry, I don't believe in Laplace's demon, and hence I believe everybody don't know something. Tbh I'm not sure if the output of lspci implies the module is still loaded, although I would assume it still is. Either way, to be sure you can use `lsmod` command, it lists all currently loaded mo