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 102913] New: Nouveau on >4.12.12 not loading EDID
Date: Thu, 21 Sep 2017 00:48:24 +0000	[thread overview]
Message-ID: <bug-102913-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 102913
           Summary: Nouveau on >4.12.12 not loading EDID
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: andrewb03-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 134394
  --> https://bugs.freedesktop.org/attachment.cgi?id=134394&action=edit
Arch 4.12.13 dmesg

System: Arch Linux
CPU: AMD Ryzen 1700
Motherboard: Gigabyte AX370 Gaming K7
After an upgrade from Arch Linux kernel 4.12.10 to 4.12.12 (or 4.12.13) the
system will hang just before initializing nouveaufb.  The system doesn't
respond to keyboard or mouse but can be reset with the Ctrl+Alt+Del or
accessible via ssh.

If I turn off KMS via nomodeset nouveau.modeset=0, I am able to boot normally
but without graphics acceleration.c

The following showed in dmesg from kernel 4.12.13:

[   12.945435] nouveau 0000:0a:00.0: DRM: DDC responded, but no EDID for DP-1
[   13.087167] gnome-shell[901]: segfault at 28 ip 00007ffab9d672f5 sp
00007fff5771ba20 error 4 in libmutter-0.so.0.0.0[7ffab9d1d000+139000]
[   16.264988] nouveau 0000:0a:00.0: DRM: DDC responded, but no EDID for DP-1
[   16.286324] nouveau 0000:0a:00.0: DRM: DDC responded, but no EDID for DP-1

As a result of this I have to either use the nvidia proprietary drivers or not
upgrade.

This seems to be the exact opposite of a 4.12 regression reported where EDID
would not load on 4.12 kernels with DP.

I have two PCIe GPUs: GK104 and GP102.  Neither are detected on those kernel
versions.  I tested 4.13 as well and it can't find the EDID either on that
kernel version.

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

[-- Attachment #1.2: Type: text/html, Size: 3484 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:[~2017-09-21  0:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  0:48 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-102913-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-09-21  0:50   ` [Bug 102913] Nouveau on >4.12.12 not loading EDID bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-01 15:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 13:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 17:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:31   ` 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-102913-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.