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] New: Xorg crashes with nouveau and dual screen setup
Date: Fri, 01 Jun 2018 19:01:21 +0000	[thread overview]
Message-ID: <bug-106772-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 106772
           Summary: Xorg crashes with nouveau and dual screen setup
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: bircoph-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 139910
  --> https://bugs.freedesktop.org/attachment.cgi?id=139910&action=edit
gdb.log

Hi!

I tried Nouveau (xorg-dri-nouveau-18.1.0 from mesa 18.1.0 and
xorg-drv-nouveau-1.0.15) with the latest xorg-1.20 and dual monitors. With
single screen and xinerama it works fine, with dual screens (w/o xinerama) it
segfaults, see log below.

I want to use separate X screens, since monitors have sufficiently different
DPI and color temp and Xinerama doesn't allow different DPI on different
monitors.

Kernel in use is 4.6.13 with nouveau built as module.

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

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

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

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

             reply	other threads:[~2018-06-01 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 19:01 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-106772-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-06-01 19:01   ` [Bug 106772] Xorg crashes with nouveau and dual screen setup 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
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@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.