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

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

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

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

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

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

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

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: X is consuming ~100 GiB of RAM(!)

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

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

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

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

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: >

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

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

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

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

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

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,

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

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(!)

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

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

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

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

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

Re: [PATCH xwayland] xwayland: Keep separate variables for pointer and tablet foci

On Tue, 2017-12-05 at 08:39 +0100, Olivier Fourdan wrote: > Hi, > > On Mon, Dec 4, 2017 at 10:22 PM, Jason Gerecke wrote: > > On Mon, Dec 4, 2017 at 7:55 AM, Carlos Garnacho wrote: > > > The tablet/stylus interfaces reused xwl_seat->focus_window, which >

[PATCH xserver] test: Fix build dependency for bigreq test

libxcb-xinput isn't a thing in whichever Ubuntu it is that Travis is using. The test is already optional, make it more so. Signed-off-by: Adam Jackson --- test/bigreq/meson.build | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/test/bigreq/meson.build

Re: [PATCH xserver 0/6] Signal handling cleanups

On 21 November 2017 at 06:43, Adam Jackson wrote: > I started writing a review of Olivier's patch and got sidetracked. I > can't really think of a good reason _not_ to generate a core if > possible, even for xfree86, and I think things look a lot simpler if we > do: These look

[Bug 33183] mouse cursor turns into thin vertical dashed line

https://bugs.freedesktop.org/show_bug.cgi?id=33183 --- Comment #49 from H Zeng --- I ran into a similar situation just now. Here is my system environment: ``` openSUSE Tumbleweed: 20171129 KDE Plasma: 5.11.3 Qt: 5.9.2 KDE Frameworks: 5.40.0 KDE Applications: 17.08.3 Kernel:

Re: Merged repo for protocol headers? Why are they split?

Hi all, if anyone would like to have a look, I've pushed my current work on the merged proto repo here: https://github.com/bartsch/xorg-proto2k/ It's generated as is with: https://github.com/bartsch/proto2k-generator/ I used git-filter-branch to: - move files to specific directories and

[Bug 103147] Radeon X600 (RV370): gpu reset/lockup (PCIe, ppc64)

https://bugs.freedesktop.org/show_bug.cgi?id=103147 --- Comment #4 from erhar...@mailbox.org --- Had some time to test kernels 4.14.4 and 4.15-rc2. Sadly nothing new concerning this issue. -- You are receiving this mail because: You are the assignee for the

Re: Merged repo for protocol headers? Why are they split?

Hi, 06.12.2017 13:37 Daniel Martin: PS: Just talked to Peter, he's okay with filter-branch as it gives us git-log without a struggle and references to other commits can be looked up in the old repos A suggestion: you could add the old IDs into the new commit logs. This makes it possible to

Re: [RFC PATCH xserver] xwayland: Fix non-argb cursor conversion

On Tue, 2017-12-05 at 10:51 +, Daniel Stone wrote: > On 27 September 2017 at 17:01, Olivier Fourdan > wrote: > > Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=103012 > > Signed-off-by: Olivier Fourdan > > Reviewed-by: Daniel Stone