dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106258] AMD Xorg start failes with non-4K page sizes
Date: Fri, 25 May 2018 19:09:44 +0000	[thread overview]
Message-ID: <bug-106258-502-kYYAtXGeLZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106258-502@http.bugs.freedesktop.org/>


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

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

--- Comment #19 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Timothy Pearson from comment #17)
> We have been unable to replicate this with the latest AMD GPU firmware from
> https://people.freedesktop.org/~agd5f/radeon_ucode/polaris/ .  Xorg starts
> fine with no errors.

Those are old firmware files I posted for testing a while ago.  Please test
with the latest firmware from the linux-firmware tree:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

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

[-- Attachment #1.2: Type: text/html, Size: 1675 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

  parent reply	other threads:[~2018-05-25 19:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 21:12 [Bug 106258] AMD Xorg start failes with non-4K page sizes bugzilla-daemon
2018-04-26 21:14 ` bugzilla-daemon
2018-04-26 21:17 ` bugzilla-daemon
2018-04-26 21:19 ` bugzilla-daemon
2018-04-26 21:22 ` bugzilla-daemon
2018-04-27 20:25 ` bugzilla-daemon
2018-05-01 10:08 ` bugzilla-daemon
2018-05-01 13:02 ` bugzilla-daemon
2018-05-01 13:06 ` bugzilla-daemon
2018-05-01 16:05 ` bugzilla-daemon
2018-05-02  9:22 ` bugzilla-daemon
2018-05-02 19:54 ` bugzilla-daemon
2018-05-02 20:38 ` bugzilla-daemon
2018-05-02 20:38 ` bugzilla-daemon
2018-05-02 22:12 ` bugzilla-daemon
2018-05-06  3:09 ` bugzilla-daemon
2018-05-15 11:54 ` bugzilla-daemon
2018-05-25 18:04 ` bugzilla-daemon
2018-05-25 19:07 ` bugzilla-daemon
2018-05-25 19:09 ` bugzilla-daemon [this message]
2018-05-30 17:16 ` bugzilla-daemon
2018-06-05 15:52 ` bugzilla-daemon
2018-06-05 16:10 ` bugzilla-daemon
2018-06-05 17:17 ` bugzilla-daemon
2018-06-06  7:18 ` bugzilla-daemon
2018-06-06 20:39 ` bugzilla-daemon
2018-06-06 21:10 ` bugzilla-daemon
2018-06-07  7:14 ` bugzilla-daemon
2018-06-18 17:37 ` bugzilla-daemon
2018-06-18 22:24 ` bugzilla-daemon
2018-06-19  9:07 ` bugzilla-daemon
2018-06-20  1:14 ` bugzilla-daemon
2018-06-20 21:50 ` bugzilla-daemon
2018-06-20 22:39 ` bugzilla-daemon
2018-06-20 22:57 ` bugzilla-daemon
2018-06-21  9:29 ` bugzilla-daemon
2018-06-21 10:22 ` bugzilla-daemon
2018-06-21 10:34 ` bugzilla-daemon
2018-06-21 11:17 ` bugzilla-daemon
2018-06-21 22:32 ` bugzilla-daemon
2018-06-24  9:15 ` bugzilla-daemon
2018-06-28  9:12 ` bugzilla-daemon
2018-07-12 11:51 ` 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-106258-502-kYYAtXGeLZ@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;
as well as URLs for NNTP newsgroup(s).