public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111372] Dual-monitor desktop environment crash with certain monitor positions
Date: Mon, 12 Aug 2019 00:51:07 +0000	[thread overview]
Message-ID: <bug-111372-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111372
           Summary: Dual-monitor desktop environment crash with certain
                    monitor positions
           Product: Mesa
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: theodorettshaw@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 145032
  --> https://bugs.freedesktop.org/attachment.cgi?id=145032&action=edit
Monitor placement crash/working cutoff

There's an issue with certain desktop environments crashing on startup when the
monitors of a multi-display system are in certain positions. In my case, I have
two monitors, and my desktop environment crashes with the error 

cinnamon: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom
>= 1' failed.

when my secondary monitor is positioned to the left of the primary monitor. An
example placement can be seen in the attached image. This is roughly the
cutoff; moving the secondary monitor, the Philips, any farther left and
restarting the DE will result in a crash. Keeping it further right and
restarting the DE results in no issues. The secondary monitor can be either
above or below the primary monitor with the same results. This error also
occurs if the secondary monitor is too far left when the DE starts on system
startup. Switching which monitor is the primary and secondary results in the
same issue, with a crash if the new secondary is too far left.

I'm using Linux Mint 19.2, Cinnamon 4.2.3, and kernel version 5.0.0-23-generic,
though I've tried several different kernel versions. I'm using an RX480. The
issue has been confirmed by others at
https://github.com/linuxmint/cinnamon/issues/8754 and a very similar and likely
linked issue at https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1837087
. glxinfo output can be found at https://pastebin.com/RGnAR320 and I'm happy to
provide any other information needed, though I may need some pointers on
something like recompiling Mesa in debug mode and getting a trace stack.

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-08-12  0:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12  0:51 bugzilla-daemon [this message]
2019-09-25 18:50 ` [Bug 111372] Dual-monitor desktop environment crash with certain monitor positions bugzilla-daemon

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-111372-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox