From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105760] [4.17-rc1] RIP: smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930
Date: Thu, 12 Jul 2018 13:31:31 +0000 [thread overview]
Message-ID: <bug-105760-502-s0ZtDXnBzf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105760-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 540 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #40 from Thomas Martitz <kugel@rockbox.org> ---
Further investigations show that toc->num_entires and toc->structure_version
are set to -1 after the first call to smu7_request_smu_load_fw(). Does that
makes sense?
Since you say the GPU does not properly wake up, can you imagine a workaround?
The laptop works with windows (of course...) so I'd think there ought to be a
sw workaround.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1450 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
next prev parent reply other threads:[~2018-07-12 13:31 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 8:58 [Bug 105760] [4.17-drm-wip] RIP: smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930 bugzilla-daemon
2018-03-30 16:04 ` bugzilla-daemon
2018-03-30 16:12 ` bugzilla-daemon
2018-04-16 9:05 ` [Bug 105760] [4.17-rc1] " bugzilla-daemon
2018-04-16 9:06 ` bugzilla-daemon
2018-04-16 9:06 ` bugzilla-daemon
2018-04-16 13:01 ` bugzilla-daemon
2018-04-16 14:48 ` bugzilla-daemon
2018-04-17 7:58 ` bugzilla-daemon
2018-04-17 7:58 ` bugzilla-daemon
2018-04-17 10:16 ` bugzilla-daemon
2018-04-17 23:08 ` bugzilla-daemon
2018-04-24 9:13 ` bugzilla-daemon
2018-05-14 14:37 ` bugzilla-daemon
2018-05-21 20:02 ` bugzilla-daemon
2018-05-21 20:11 ` bugzilla-daemon
2018-05-21 21:33 ` bugzilla-daemon
2018-06-24 22:30 ` bugzilla-daemon
2018-06-25 5:37 ` bugzilla-daemon
2018-06-26 14:22 ` bugzilla-daemon
2018-06-27 7:50 ` bugzilla-daemon
2018-06-27 7:50 ` bugzilla-daemon
2018-06-28 7:25 ` bugzilla-daemon
2018-06-28 7:51 ` bugzilla-daemon
2018-06-29 19:08 ` bugzilla-daemon
2018-06-29 22:14 ` bugzilla-daemon
2018-07-11 14:31 ` bugzilla-daemon
2018-07-11 19:21 ` bugzilla-daemon
2018-07-11 19:21 ` bugzilla-daemon
2018-07-11 19:22 ` bugzilla-daemon
2018-07-11 19:22 ` bugzilla-daemon
2018-07-11 20:20 ` bugzilla-daemon
2018-07-11 20:24 ` bugzilla-daemon
2018-07-11 22:01 ` bugzilla-daemon
2018-07-12 4:45 ` bugzilla-daemon
2018-07-12 4:56 ` bugzilla-daemon
2018-07-12 5:09 ` bugzilla-daemon
2018-07-12 5:41 ` bugzilla-daemon
2018-07-12 6:34 ` bugzilla-daemon
2018-07-12 8:00 ` bugzilla-daemon
2018-07-12 13:17 ` bugzilla-daemon
2018-07-12 13:17 ` bugzilla-daemon
2018-07-12 13:19 ` bugzilla-daemon
2018-07-12 13:21 ` bugzilla-daemon
2018-07-12 13:28 ` bugzilla-daemon
2018-07-12 13:31 ` bugzilla-daemon [this message]
2018-07-12 13:35 ` bugzilla-daemon
2018-07-12 19:38 ` bugzilla-daemon
2018-07-12 20:33 ` bugzilla-daemon
2018-07-12 21:50 ` bugzilla-daemon
2018-07-13 22:00 ` bugzilla-daemon
2018-07-15 14:40 ` bugzilla-daemon
2018-07-16 14:36 ` bugzilla-daemon
2018-07-16 17:07 ` bugzilla-daemon
2018-07-16 17:12 ` bugzilla-daemon
2018-07-17 6:28 ` bugzilla-daemon
2018-07-17 6:30 ` bugzilla-daemon
2018-07-17 6:33 ` bugzilla-daemon
2018-07-19 14:14 ` bugzilla-daemon
2018-07-26 19:33 ` bugzilla-daemon
2018-07-26 22:32 ` bugzilla-daemon
2018-07-26 22:33 ` bugzilla-daemon
2018-08-28 16:43 ` bugzilla-daemon
2018-08-28 16:59 ` bugzilla-daemon
2018-08-29 21:21 ` bugzilla-daemon
2018-08-30 6:57 ` bugzilla-daemon
2018-08-30 6:59 ` bugzilla-daemon
2018-08-30 7:02 ` bugzilla-daemon
2018-08-30 7:05 ` bugzilla-daemon
2018-08-30 10:04 ` bugzilla-daemon
2018-09-08 11:03 ` bugzilla-daemon
2018-09-10 3:43 ` 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-105760-502-s0ZtDXnBzf@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.