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 106772] Xorg crashes with nouveau and dual screen setup
Date: Fri, 01 Jun 2018 20:55:50 +0000	[thread overview]
Message-ID: <bug-106772-8800-8hnIR12C0i@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106772-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #5 from Keith Packard <keithp-aN4HjG94KOLQT0dZR+AlfA@public.gmane.org> ---
Looks like Nouveau still parties like it's 1999. I don't think more recent
drivers do mode setting this early. However, it's easy enough to handle this
case by simply skipping the RRCrtcIsLeased and RROutputIsLeased calls when the
respective DIX objects haven't been created yet. Here's a patch which simply
wraps those functions in xf86 code that checks for NULL pointers before calling
the DIX code.

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

[-- Attachment #1.2: Type: text/html, Size: 1378 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:[~2018-06-01 20:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 19:01 [Bug 106772] New: Xorg crashes with nouveau and dual screen setup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-106772-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-06-01 19:01   ` [Bug 106772] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-01 19:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-01 19:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-01 19:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-01 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-06-01 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-13  9:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-13  9:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-13  9:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:40   ` 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-106772-8800-8hnIR12C0i@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.