All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103370] `vblank_mode=0 DRI_PRIME=1 glxgears` will introduce GPU lock up on Intel Graphics [8086:5917] + AMD Graphics [1002:6665] (rev c3)
Date: Tue, 21 Nov 2017 08:05:53 +0000	[thread overview]
Message-ID: <bug-103370-502-bS6VyuoYp8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103370-502@http.bugs.freedesktop.org/>


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

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

--- Comment #36 from Robert Liu <tsunghanliu@gmail.com> ---
(In reply to Alex Deucher from comment #33)
> I think Sonny fixed this.  It was due to using the wrong firmware.
> [    1.827060] [drm] initializing kernel modesetting (HAINAN 0x1002:0x6665
> 0x1028:0x0844 0xC3).  This chip should be using radeon/banks_k_2_smc.bin smc
> firmware.  Is that available on the test system and kernel?
The firmware radeon/banks_k_2_smc.bin is on the test system.
With Ubuntu kernel 4.4.0-101-generic, I am not pretty sure the radeon driver is
using this firmware.
With Ubuntu kernel 4.13.0-16-generic, I tried both amdgpu and radeon drivers,
but the system hang. as soon as the system hang, the amdgpu_pm_info shows
'invalid dpm profile 15'.

(In reply to Alex Deucher from comment #34)
> The following commits are relevant:
> abb2e3c1ce64c8bba678973800c34ea1dc97c42c
> 6458bd4dfd9414cba5804eb9907fe2a824278c34
> ef736d394e85b1bf1fd65ba5e5257b85f6c82325
> 4e6e98b1e48c9474aed7ce03025ec319b941e26e
These commits would be already included in Ubuntu kernel 4.13.0-16-generic.

(In reply to Alex Deucher from comment #35)
> Does reverting a628392cf03e0eef21b345afbb192cbade041741 fix the issue?
Removing this commit does not fix the issue.


BTW, with 4.13.0-16-generic, I change the max_sclk in drm/radeon/si_dpm.c (what
we did with Ubuntu kernel 4.4.0-101-generic) from 75000 to 65000, but still met
the hang issue.

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

[-- Attachment #1.2: Type: text/html, Size: 2746 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:[~2017-11-21  8:05 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20  9:16 [Bug 103370] `DRI_PRIME=1 glxgears -info` halts the system with Intel Graphics [8086:5917] + AMD Graphics [1002:6665] bugzilla-daemon
2017-10-20  9:19 ` bugzilla-daemon
2017-10-20  9:20 ` bugzilla-daemon
2017-10-20  9:26 ` bugzilla-daemon
2017-10-20  9:33 ` bugzilla-daemon
2017-10-20  9:55 ` bugzilla-daemon
2017-10-20 10:01 ` bugzilla-daemon
2017-10-20 11:04 ` bugzilla-daemon
2017-10-20 14:15 ` bugzilla-daemon
2017-10-20 15:54 ` bugzilla-daemon
2017-10-24 10:12 ` bugzilla-daemon
2017-10-24 10:21 ` bugzilla-daemon
2017-10-24 10:30 ` bugzilla-daemon
2017-10-24 10:32 ` bugzilla-daemon
2017-10-24 10:44 ` bugzilla-daemon
2017-10-24 11:03 ` bugzilla-daemon
2017-10-24 11:37 ` bugzilla-daemon
2017-10-24 11:38 ` bugzilla-daemon
2017-10-25  4:31 ` bugzilla-daemon
2017-10-25  4:54 ` bugzilla-daemon
2017-10-25 22:23 ` bugzilla-daemon
2017-10-26  4:14 ` bugzilla-daemon
2017-10-26  4:15 ` bugzilla-daemon
2017-10-26  4:17 ` bugzilla-daemon
2017-10-26  8:41 ` bugzilla-daemon
2017-11-15  4:43 ` bugzilla-daemon
2017-11-15  8:02 ` bugzilla-daemon
2017-11-17  9:56 ` bugzilla-daemon
2017-11-17 10:12 ` bugzilla-daemon
2017-11-17 11:11 ` bugzilla-daemon
2017-11-17 11:12 ` [Bug 103370] `DRI_PRIME=1 glxgears -info` halts the system with Intel Graphics [8086:5917] + AMD Graphics [1002:6665] (rev c3) bugzilla-daemon
2017-11-17 11:13 ` [Bug 103370] `vblank_mode=0 DRI_PRIME=1 glxgears` will introduce GPU lock up on " bugzilla-daemon
2017-11-17 11:14 ` bugzilla-daemon
2017-11-17 15:37 ` bugzilla-daemon
2017-11-17 15:39 ` bugzilla-daemon
2017-11-20  7:56 ` bugzilla-daemon
2017-11-20 15:41 ` bugzilla-daemon
2017-11-20 15:48 ` bugzilla-daemon
2017-11-20 15:52 ` bugzilla-daemon
2017-11-21  8:05 ` bugzilla-daemon [this message]
2017-11-21  9:21 ` bugzilla-daemon
2017-11-21 17:13 ` bugzilla-daemon
2017-11-21 17:13 ` bugzilla-daemon
2017-11-22  8:59 ` bugzilla-daemon
2017-11-24  7:02 ` bugzilla-daemon
2017-11-24  8:55 ` bugzilla-daemon
2018-01-19  8:59 ` bugzilla-daemon
2018-01-29  4:35 ` bugzilla-daemon
2018-03-15  4:18 ` bugzilla-daemon
2018-03-15  6:45 ` 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-103370-502-bS6VyuoYp8@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.