From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196117] amdgpu - RX 480 (polaris) - freeze during boot
Date: Fri, 23 Jun 2017 23:48:09 +0000 [thread overview]
Message-ID: <bug-196117-2300-5HddRFuq5s@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196117-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196117
--- Comment #6 from Paul K. Gerke (paulkgerke@craftware.nl) ---
Success! Everything seems to be fixed... "everything":
I tried the amdstaging-kernel for 4.11.0+ and it works now! Jippieh!
This is the log for the working driver (I cut away a bit of the beginning which
is the same as for the other kernel logs):
[ 102.328213] amdgpu 0000:02:00.0: fence driver on ring 0 use gpu addr
0x0000000000000008, cpu addr 0xffff8efe66e4e008
[ 102.328265] amdgpu 0000:02:00.0: fence driver on ring 1 use gpu addr
0x0000000000000018, cpu addr 0xffff8efe66e4e018
[ 102.328331] amdgpu 0000:02:00.0: fence driver on ring 2 use gpu addr
0x0000000000000028, cpu addr 0xffff8efe66e4e028
[ 102.328377] amdgpu 0000:02:00.0: fence driver on ring 3 use gpu addr
0x0000000000000038, cpu addr 0xffff8efe66e4e038
[ 102.328517] amdgpu 0000:02:00.0: fence driver on ring 4 use gpu addr
0x0000000000000048, cpu addr 0xffff8efe66e4e048
[ 102.328568] amdgpu 0000:02:00.0: fence driver on ring 5 use gpu addr
0x0000000000000058, cpu addr 0xffff8efe66e4e058
[ 102.328610] amdgpu 0000:02:00.0: fence driver on ring 6 use gpu addr
0x0000000000000068, cpu addr 0xffff8efe66e4e068
[ 102.328646] amdgpu 0000:02:00.0: fence driver on ring 7 use gpu addr
0x0000000000000078, cpu addr 0xffff8efe66e4e078
[ 102.328681] amdgpu 0000:02:00.0: fence driver on ring 8 use gpu addr
0x0000000000000088, cpu addr 0xffff8efe66e4e088
[ 102.328706] amdgpu 0000:02:00.0: fence driver on ring 9 use gpu addr
0x000000000000009c, cpu addr 0xffff8efe66e4e09c
[ 102.328795] amdgpu 0000:02:00.0: fence driver on ring 10 use gpu addr
0x00000000000000ac, cpu addr 0xffff8efe66e4e0ac
[ 102.328833] amdgpu 0000:02:00.0: fence driver on ring 11 use gpu addr
0x00000000000000bc, cpu addr 0xffff8efe66e4e0bc
[ 102.328847] [drm] Found UVD firmware Version: 1.79 Family ID: 16
[ 102.329116] amdgpu 0000:02:00.0: fence driver on ring 12 use gpu addr
0x000000f40122d420, cpu addr 0xffffa54243c5a420
[ 102.329128] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
[ 102.329209] amdgpu 0000:02:00.0: fence driver on ring 13 use gpu addr
0x00000000000000dc, cpu addr 0xffff8efe66e4e0dc
[ 102.329254] amdgpu 0000:02:00.0: fence driver on ring 14 use gpu addr
0x00000000000000ec, cpu addr 0xffff8efe66e4e0ec
[ 102.368327] amdgpu: [powerplay] [AVFS] Something is broken. See log!
[ 102.370210] amdgpu: [powerplay] Can't find requested voltage id in
vdd_dep_on_sclk table!
[ 102.382613] [drm] ring test on 0 succeeded in 14 usecs
[ 102.383115] [drm] ring test on 9 succeeded in 9 usecs
[ 102.383134] [drm] ring test on 1 succeeded in 8 usecs
[ 102.383144] [drm] ring test on 2 succeeded in 3 usecs
[ 102.383153] [drm] ring test on 3 succeeded in 3 usecs
[ 102.383163] [drm] ring test on 4 succeeded in 3 usecs
[ 102.383176] [drm] ring test on 5 succeeded in 5 usecs
[ 102.383185] [drm] ring test on 6 succeeded in 3 usecs
[ 102.383195] [drm] ring test on 7 succeeded in 3 usecs
[ 102.383204] [drm] ring test on 8 succeeded in 3 usecs
[ 102.383248] [drm] ring test on 10 succeeded in 5 usecs
[ 102.383256] [drm] ring test on 11 succeeded in 6 usecs
[ 102.429390] [drm] ring test on 12 succeeded in 1 usecs
[ 102.429399] [drm] UVD initialized successfully.
[ 102.539389] [drm] ring test on 13 succeeded in 7 usecs
[ 102.539400] [drm] ring test on 14 succeeded in 3 usecs
[ 102.539402] [drm] VCE initialized successfully.
[ 102.539658] [drm] ib test on ring 0 succeeded
[ 102.539821] [drm] ib test on ring 1 succeeded
[ 102.539870] [drm] ib test on ring 2 succeeded
[ 102.539913] [drm] ib test on ring 3 succeeded
[ 102.539955] [drm] ib test on ring 4 succeeded
[ 102.539994] [drm] ib test on ring 5 succeeded
[ 102.540031] [drm] ib test on ring 6 succeeded
[ 102.540072] [drm] ib test on ring 7 succeeded
[ 102.540112] [drm] ib test on ring 8 succeeded
[ 103.041685] [drm] ib test on ring 9 succeeded
[ 103.041722] [drm] ib test on ring 10 succeeded
[ 103.041751] [drm] ib test on ring 11 succeeded
[ 103.043080] [drm] ib test on ring 12 succeeded
[ 103.043301] [drm] ib test on ring 13 succeeded
[ 103.141511] [drm] fb mappable at 0xC1437000
[ 103.141519] [drm] vram apper at 0xC0000000
[ 103.141521] [drm] size 7680000
[ 103.141522] [drm] fb depth is 24
[ 103.141523] [drm] pitch is 6400
[ 103.141588] fbcon: amdgpudrmfb (fb0) is primary device
[ 103.263499] Console: switching to colour frame buffer device 200x75
[ 103.319197] systemd-journald[303]: Sent WATCHDOG=1 notification.
[ 103.365845] amdgpu 0000:02:00.0: fb0: amdgpudrmfb frame buffer device
[ 103.388258] [drm] Initialized amdgpu 3.17.0 20150101 for 0000:02:00.0 on
minor 0
-----------------
For anybody who wants to reproduce what I did, here the instructions which work
for ubuntu 16.04:
- git-clone the kernel at git://people.freedesktop.org/~agd5f/linux
- checkout the branch amd-staging-4.11
- I specifically used commit 3e3a7c55b8de38e0557fe954f236ca8e8e925d85
- Use the config-file attached below for building the kernel
- The config files includes rules to bake the polaris-firmware files into
the kernel itself. I do not know if this is good or bad, but it works for me.
- Build the kernel
- install the kernel (dpkg -i)
- Follow the the not-kernel-related instructions on
https://linuxconfig.org/getting-the-rx-480-running-with-amdgpu-on-linux
Reboot, and enjoy.
---------
I am lacking good synthetic tests for the OpenGL capabitlities at the moment,
and just tested it by running some games. glxinfo reports that amdgpu is
working, so all seems fine. I hope that this will not break again! Thanks again
for the suggestions regarding debugging @Michel, I finally chewed through it...
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-06-23 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 20:08 [Bug 196117] New: amdgpu RC 480 (polaris) freeze after initramfs, before kernel load bugzilla-daemon
2017-06-18 20:33 ` [Bug 196117] " bugzilla-daemon
2017-06-18 20:35 ` [Bug 196117] amdgpu - RX 480 (polaris) - freeze during boot bugzilla-daemon
2017-06-19 2:17 ` bugzilla-daemon
2017-06-19 8:17 ` bugzilla-daemon
2017-06-19 20:23 ` bugzilla-daemon
2017-06-22 23:22 ` bugzilla-daemon
2017-06-23 23:48 ` bugzilla-daemon [this message]
2017-06-23 23:50 ` bugzilla-daemon
2017-06-23 23: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-196117-2300-5HddRFuq5s@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.