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: Mon, 20 Nov 2017 15:41:11 +0000	[thread overview]
Message-ID: <bug-103370-502-a8x6CDJJgh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103370-502@http.bugs.freedesktop.org/>


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

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

--- Comment #33 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Michel Dänzer from comment #27)
> Thanks for bisecting, but I don't think that commit can be directly
> responsible for a GPU hang. Before that commit, the DRI3 code in Mesa would
> only use one back buffer for glxgears, which means that the GPU could only
> start rendering a new frame after the previous one had finished presenting.
> Maybe that somehow prevented the hang.

That commit "fixed" a performance regression at the time because it ended up
causing enough of a delay that the clocks didn't ramp up.  So it probably
exposed a kernel dpm issue.  Without it, the clocks never ramped up enough to
cause an issue.  With it, they did.


(In reply to Timo Aaltonen from comment #32)
> forwarding a comment from an engineer:
> 
> "During viewing the source code of radeon module, I found there is a bug [1]
> related to the dpm and clocks. So I decided to do some experiments.
> Tried to set different max_sclk and max_mclk to see if the issue is gone.
> 1. max_sclk: 70000, max_mclk: 75000 --> have the same issue
> 2. max_sclk: 50000, max_mclk: 60000 --> pass multi-run test (more than 50
> runs)
> 
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=76490
> "

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?

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

[-- Attachment #1.2: Type: text/html, Size: 3019 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-20 15:41 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 [this message]
2017-11-20 15:48 ` bugzilla-daemon
2017-11-20 15:52 ` bugzilla-daemon
2017-11-21  8:05 ` bugzilla-daemon
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-a8x6CDJJgh@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.