All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 92961] Xorg freezes (only mouse and ssh are still working)
Date: Tue, 18 Oct 2016 16:33:03 +0000	[thread overview]
Message-ID: <bug-92961-8800-OoSjSadvMN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92961-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 888 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=92961

--- Comment #12 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to Marcelo Jimenez from comment #7)
> The freeze happens at random times, there is no particular sequence to
> produce it. I use KDE on opensuse 42.1.

A number of users have been experiencing issues with KDE across a variety of
hardware with nouveau. My current advice is to either not use KDE or not use
nouveau_dri.so. [It's most likely not KDE's fault, but this is the present
reality.]

Separately, OpenSuSE included some patches of mine in their Mesa builds that
address some but hardly all of the issues involved. I believe the approach to
be fundamentally flawed and in need of redoing. (The latest may be that they
have dropped those.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1720 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2016-10-18 16:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-15 10:41 [Bug 92961] New: Xorg freezes (only mouse and ssh are still working) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-92961-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-11-15 11:11   ` [Bug 92961] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-15 11:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-22 23:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 10:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 18:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-24 20:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-18 16:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-18 16:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-18 16:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-18 16:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-18 16:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-18 16:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-10-18 16:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-18 16:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-13  7:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-13  7:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-13  8:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-16  9:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-02 23:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-02 23:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-92961-8800-OoSjSadvMN@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.