All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99907] linux-firmware 2017-02-17 update causes varying breaks in AMDGPU for recent cards
Date: Wed, 22 Feb 2017 18:07:11 +0000	[thread overview]
Message-ID: <bug-99907-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 99907
           Summary: linux-firmware 2017-02-17 update causes varying breaks
                    in AMDGPU for recent cards
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: saunders.52@wright.edu

Currently on Arch Linux after they shipped an update to the linux-firmware set
(20170217.12987ca-1), there's been reports of various issues ranging from power
management failing to in my case (AMD Radeon RX 460) Xorg failing to work at
all (it either blinks and goes back to a frozen VT as the GPU hangs, or the GPU
hangs on a full-screen corruption of some kind.) This is broken on both kernel
4.9.11 and 4.10 in my testing, on Xorg 1.19.1. The system still responds to SSH
connections, but fails to shutdown properly if attempted over that. Tracker
link: https://bugs.archlinux.org/task/53042

I've traced it back to a specific commit to linux-firmware,    
7a110b85a46d7f884f4ac712ff52e02ed57234bd,
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/carrizo_ce.bin?id=7a110b85a46d7f884f4ac712ff52e02ed57234bd,
pushed to the git repo on 2-17-17, which updates a large subset of the firmware
images used by AMDGPU. Seeing as how this is a binary file set, I'm really not
sure how to proceed from here in testing it to give any more useful information
here. 

Apologies if this is the wrong place to report a firmware issue, but I was
unsure where to file it otherwise.

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

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

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

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

             reply	other threads:[~2017-02-22 18:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 18:07 bugzilla-daemon [this message]
2017-02-22 18:10 ` [Bug 99907] linux-firmware 2017-02-17 update causes varying breaks in AMDGPU for recent cards bugzilla-daemon
2017-02-22 18:33 ` bugzilla-daemon
2017-02-22 20:37 ` bugzilla-daemon
2017-02-22 20:37 ` bugzilla-daemon
2017-02-22 20:38 ` bugzilla-daemon
2017-02-22 20:38 ` bugzilla-daemon
2017-02-22 20:39 ` bugzilla-daemon
2017-02-23  1:46 ` bugzilla-daemon
2017-02-23  1:47 ` bugzilla-daemon
2017-02-23  2:10 ` bugzilla-daemon
2017-02-23  2:30 ` bugzilla-daemon
2017-02-23  8:33 ` bugzilla-daemon
2017-02-23 16:27 ` bugzilla-daemon
2017-02-23 16:29 ` bugzilla-daemon
2017-02-23 16:30 ` bugzilla-daemon
2017-02-23 16:32 ` bugzilla-daemon
2017-02-23 16:34 ` bugzilla-daemon
2017-02-23 16:35 ` bugzilla-daemon
2017-02-23 16:37 ` bugzilla-daemon
2017-02-23 16:38 ` bugzilla-daemon
2017-02-23 16:43 ` bugzilla-daemon
2017-02-23 16:52 ` bugzilla-daemon
2017-02-23 18:38 ` bugzilla-daemon
2019-11-19  8:14 ` 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-99907-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 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.