All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95261] R5 M330 GPU lockup with DPM + high power states
Date: Fri, 10 Jun 2016 15:43:52 +0000	[thread overview]
Message-ID: <bug-95261-502-FREMq01wfF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95261-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from Andrzej Mendel-Nykorowycz <andrzej.mendel@gmail.com> ---
(In reply to Alex Deucher from comment #7)
> Does it work any better with my drm-next-4.8-wip branch:
> https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.8-wip
> and the new smu firmware here:
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/
> commit/?id=9693ff6d749dcf1dfd81f0f6b227ab07a3d76c90

Unfortunately, no, I get the same hangup with any GPU intensive application.
I've put new firmware files in /lib/firmware/radeon and I believe it is being
loaded (the filesize reported is that of hainan_k_smc.bin):

Jun 10 16:02:49 Sulejman kernel: [  511.257607]
[drm:radeon_ucode_print_smc_hdr] SMC
Jun 10 16:02:49 Sulejman kernel: [  511.257608]
[drm:radeon_ucode_print_common_hdr] size_bytes: 61932
Jun 10 16:02:49 Sulejman kernel: [  511.257609]
[drm:radeon_ucode_print_common_hdr] header_size_bytes: 36
Jun 10 16:02:49 Sulejman kernel: [  511.257610]
[drm:radeon_ucode_print_common_hdr] header_version_major: 1
Jun 10 16:02:49 Sulejman kernel: [  511.257610]
[drm:radeon_ucode_print_common_hdr] header_version_minor: 0
Jun 10 16:02:49 Sulejman kernel: [  511.257611]
[drm:radeon_ucode_print_common_hdr] ip_version_major: 6
Jun 10 16:02:49 Sulejman kernel: [  511.257612]
[drm:radeon_ucode_print_common_hdr] ip_version_minor: 0
Jun 10 16:02:49 Sulejman kernel: [  511.257613]
[drm:radeon_ucode_print_common_hdr] ucode_version: 0x01337baa
Jun 10 16:02:49 Sulejman kernel: [  511.257614]
[drm:radeon_ucode_print_common_hdr] ucode_size_bytes: 61676
Jun 10 16:02:49 Sulejman kernel: [  511.257614]
[drm:radeon_ucode_print_common_hdr] ucode_array_offset_bytes: 256
Jun 10 16:02:49 Sulejman kernel: [  511.257615]
[drm:radeon_ucode_print_common_hdr] crc32: 0x9624ad7c
Jun 10 16:02:49 Sulejman kernel: [  511.257616]
[drm:radeon_ucode_print_smc_hdr] ucode_start_addr: 65536

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

[-- Attachment #1.2: Type: text/html, Size: 3094 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:[~2016-06-10 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 13:27 [Bug 95261] R5 M330 GPU lockup with DPM + high power states bugzilla-daemon
2016-05-04 13:28 ` bugzilla-daemon
2016-05-04 13:39 ` bugzilla-daemon
2016-05-04 13:39 ` bugzilla-daemon
2016-05-04 13:41 ` bugzilla-daemon
2016-05-04 13:42 ` bugzilla-daemon
2016-05-08  9:58 ` bugzilla-daemon
2016-06-09 18:45 ` bugzilla-daemon
2016-06-09 20:12 ` bugzilla-daemon
2016-06-10 15:43 ` bugzilla-daemon [this message]
2016-06-10 16:31 ` bugzilla-daemon
2019-11-19  9:16 ` 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-95261-502-FREMq01wfF@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.