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 105935] New: DRI3 suddenly stopped turning on at some point in the past 5 months
Date: Fri, 06 Apr 2018 22:00:03 +0000	[thread overview]
Message-ID: <bug-105935-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 105935
           Summary: DRI3 suddenly stopped turning on at some point in the
                    past 5 months
           Product: Mesa
           Version: 17.3
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: jimijames.bove-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org

Created attachment 138667
  --> https://bugs.freedesktop.org/attachment.cgi?id=138667&action=edit
kernel_log.txt

(The attached files are from when I was on kernel version 4.9.78-lts, but I've
confirmed that this bug persists on non-LTS 4.12.12 as well as up to
4.14.31-lts.)

I have two GPUs a GT 740 on nouveau, and an AMD R9 Fury on amdgpu. Both cards
are working fine, and both drivers seem to be working fine, other than this
issue.

Problem:
DRI3 won't activate, despite no logs that I know of ever spitting out an error
message related to it, and despite nothing about my system changing since it
last worked other than package versions. I'm not sure exactly when this problem
started, because I haven't been playing video games on Linux as often lately
(DRI_PRIME is what I need DRI3 for), but it most likely started within the last
5 months.

Steps to reproduce:
I have no idea. This is why I'm stumped. The Xorg conf files are exactly what
they should be and exactly what they were the last time this worked. Here are
the packages I've tried downgrading to versions that I had when this worked,
even all at the same time just in case:
-linux{,-lts} (currently 4.14.31-lts)
-xorg-server{,-common,-devel} (currently 1.19.6+13+gd0d1a694f)
-xf86-input-libinput & libinput (currently 0.27.0 and 1.10.3, respectively)
-{,lib32-}mesa (currently 17.3.7)
-mesa-vdpau (also 17.3.7)
-xf86-video-{nouveau,amdgpu} (currently 1.0.15 and 18.0.1, respectively)
And my current version of libdrm is 2.4.91.

I found one other person with this problem, on reddit:
https://www.reddit.com/r/VFIO/comments/7u8o50/dri3_and_dri_prime_randomly_stopped_working_in/dwx5vl2/?context=3
They're using a similar NVidia card to mine (GT 730), and the only way they've
managed to fix this issue is by replacing it with an AMD card, leading me to
suspect nouveau.
I also made a report for Arch Linux, but it's pretty much the same report:
https://bugs.archlinux.org/task/57564

I first noticed this problem about 2 months ago, but have spent all this time
trying to figure out how to reproduce it before doing a bug report, even
getting help from #nouveau (and trying to get help from #xorg-users and
#xorg-devel, but the former was empty and the latter ignored me). I give up. I
can't figure out how to reproduce it unless there are even more packages I can
try downgrading that I haven't heard of.

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

[-- Attachment #1.2: Type: text/html, Size: 4815 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-04-06 22:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 22:00 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-105935-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-04-06 22:00   ` [Bug 105935] DRI3 suddenly stopped turning on at some point in the past 5 months bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-06 22:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-06 22:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-06 22:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-06 22:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-09 21:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-09 21:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-09 21:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:46   ` 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-105935-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.