Re: Xorg freezes

2019-12-04 Thread Chris Sorenson


Message: 2
Date: Wed, 4 Dec 2019 11:41:49 +0530
From: Fabin Mundattil 
To: x...@freedesktop.org
Subject: Xorg freezes
Message-ID:

Content-Type: text/plain; charset="utf-8"

I have Ubuntu 18 running Google Chrome. Google chrome freezes my 
machine. I

figured it out that the hardware acceleration is the issue. From what I
understand, something like this shouldn't freeze Xorg. I need to 
disable

GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors
anywhere in logs either. Is this a bug in Xorg? Should I submit any 
more

information?

--
Regards
Fabin M

Message: 3
Date: Wed, 4 Dec 2019 10:54:13 +0100
From: Michel Dänzer 
To: Fabin Mundattil 
Cc: x...@freedesktop.org
Subject: Re: Xorg freezes
Message-ID: <9d22380b-f6c2-25ca-a296-5a56a309a...@daenzer.net>
Content-Type: text/plain; charset=utf-8

On 2019-12-04 7:11 a.m., Fabin Mundattil wrote:
I have Ubuntu 18 running Google Chrome. Google chrome freezes my 
machine. I
figured it out that the hardware acceleration is the issue. From what 
I
understand, something like this shouldn't freeze Xorg. I need to 
disable

GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors
anywhere in logs either. Is this a bug in Xorg?


More likely in the Mesa/kernel drivers you're using.

--

Message: 4
Date: Wed, 04 Dec 2019 11:27:42 +0100
From: walter harms 
To: xorg@lists.x.org
Cc: mfa...@gmail.com
Subject: Re: Xorg freezes
Message-ID: <5de78a1e.7060...@bfs.de>
Content-Type: text/plain; charset=UTF-8



Am 04.12.2019 07:11, schrieb Fabin Mundattil:
I have Ubuntu 18 running Google Chrome. Google chrome freezes my 
machine. I
figured it out that the hardware acceleration is the issue. From what 
I
understand, something like this shouldn't freeze Xorg. I need to 
disable

GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors
anywhere in logs either. Is this a bug in Xorg? Should I submit any 
more

information?



Hi Fabin,
independent of everything:

The big problem for developers is replication, if the problem is not
reproduceable it is less likely that it can be fixed. So if you
want to submit a problem report take the seat of the developer and
ask yourself: could you replicate the problem with that
information ? It helps a lot if you can reduce the number of
libraries needed etc.

just my 2 cents,

re,
 wh



Regards Fabian,

In particular, it would help to know what graphics hardware exists on 
your system. If there are binary kernel modules for that hardware from 
its manufacturer it would likely be best if you used those, though that 
is admittedly not the "free software" way.

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

[PATCH] Flush buffer in time for global (un)lock xserver operation

2019-12-04 Thread chengang
From: Chen Gang 

The global (un)lock xserver operations will have effect to the whole
system, and all the other gui apps have to be blocked, so the operations
should not be buffered, or may cause sync issue, e.g. reboot machine.

Cc: Lv Li-song 
Signed-off-by: Chen Gang 
---
 src/GrServer.c  | 1 +
 src/UngrabSvr.c | 1 +
 2 files changed, 2 insertions(+)

diff --git a/src/GrServer.c b/src/GrServer.c
index c4c62bef..8f81157c 100644
--- a/src/GrServer.c
+++ b/src/GrServer.c
@@ -35,6 +35,7 @@ XGrabServer (register Display *dpy)
_X_UNUSED register xReq *req;
LockDisplay(dpy);
 GetEmptyReq(GrabServer, req);
+   _XFlush(dpy); /* For Global (un)lock ops must be sent quickly */
UnlockDisplay(dpy);
SyncHandle();
return 1;
diff --git a/src/UngrabSvr.c b/src/UngrabSvr.c
index 20ad9aa3..49c8b9af 100644
--- a/src/UngrabSvr.c
+++ b/src/UngrabSvr.c
@@ -37,6 +37,7 @@ XUngrabServer (
 
 LockDisplay(dpy);
 GetEmptyReq(UngrabServer, req);
+   _XFlush(dpy); /* For Global (un)lock ops must be sent quickly */
 UnlockDisplay(dpy);
SyncHandle();
return 1;
-- 
2.20.1



___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Re: Xorg freezes

2019-12-04 Thread walter harms


Am 04.12.2019 07:11, schrieb Fabin Mundattil:
> I have Ubuntu 18 running Google Chrome. Google chrome freezes my machine. I
> figured it out that the hardware acceleration is the issue. From what I
> understand, something like this shouldn't freeze Xorg. I need to disable
> GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors
> anywhere in logs either. Is this a bug in Xorg? Should I submit any more
> information?


Hi Fabin,
independent of everything:

The big problem for developers is replication, if the problem is not 
reproduceable
it is less likely that it can be fixed. So if you want to submit a problem 
report
take the seat of the developer and ask yourself: could you replicate the problem
with that information ? It helps a lot if you can reduce the number of libraries
needed etc.

just my 2 cents,

re,
 wh
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Xorg freezes

2019-12-04 Thread Michel Dänzer
On 2019-12-04 7:11 a.m., Fabin Mundattil wrote:
> I have Ubuntu 18 running Google Chrome. Google chrome freezes my machine. I
> figured it out that the hardware acceleration is the issue. From what I
> understand, something like this shouldn't freeze Xorg. I need to disable
> GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors
> anywhere in logs either. Is this a bug in Xorg?

More likely in the Mesa/kernel drivers you're using.


-- 
Earthling Michel Dänzer   |   https://redhat.com
Libre software enthusiast | Mesa and X developer
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Xorg freezes

2019-12-04 Thread Fabin Mundattil
I have Ubuntu 18 running Google Chrome. Google chrome freezes my machine. I
figured it out that the hardware acceleration is the issue. From what I
understand, something like this shouldn't freeze Xorg. I need to disable
GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors
anywhere in logs either. Is this a bug in Xorg? Should I submit any more
information?

-- 
Regards
Fabin M

The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not
the intended recipient, you should not disseminate, distribute or copy this
e-mail. Please notify the sender immediately and destroy all copies of this
message and any attachments
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

[ANNOUNCE] xf86-video-sis 0.12.0

2019-12-04 Thread Kevin Brace
This release is a maintenance release to support X.Org X Server 1.20.

Kevin Brace
Brace Computer Laboratory blog
https://bracecomputerlab.com

---
Kevin Brace (4):
  Do not call xf86DisableRandR() for X Server 1.20
  Fix for xf86InterceptSigIll() discontinuation in X Server 1.20
  Enable SISGAMMARAMP macro on X.Org X Server
  Version bumped to 0.12.0

git tag: xf86-video-sis-0.12.0

https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.bz2
MD5:  b8ec9c21758043b1480f11baec296f5d  xf86-video-sis-0.12.0.tar.bz2
SHA1: d22f0d0081e222a62f9e788f5e73246c6d339f80  xf86-video-sis-0.12.0.tar.bz2
SHA256: 119d3f17d53c862ec4bf891ed696a6f1d32cdf8bd11d944a9f0ad24625333a5b  
xf86-video-sis-0.12.0.tar.bz2
SHA512: 
5aa101e5217f15667f2c94f7a76f4afcf47717b61f5d206ce65efe35dc3f674ca294f98ca8586971c6467f31decdd94d8255ebfc7dc220fac0179afc61995952
  xf86-video-sis-0.12.0.tar.bz2
PGP:  https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.bz2.sig

https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.gz
MD5:  52d2d74982393c32a0a9c3d5d3ce99a3  xf86-video-sis-0.12.0.tar.gz
SHA1: 1e4dfd77d36973a4218b8d0076d5bef2a0576a16  xf86-video-sis-0.12.0.tar.gz
SHA256: 9bcc3b649001e99eb9b7f64437ee8fd65863d84bd812978fe0269180b2884702  
xf86-video-sis-0.12.0.tar.gz
SHA512: 
ddf83452ec4c1f79f4d926c0b9bb78b0cc6df4a5473b1da00fa4eb28f159491b240205d19d6d82f33169b50539d8982a529020e0d935cdeee8f37dd6bd1ece65
  xf86-video-sis-0.12.0.tar.gz
PGP:  https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.gz.sig

___
xorg-announce mailing list
xorg-announce@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-announce