From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107955] AMDGPU driver keeps reloading on hybrid graphics system causing stuttering.
Date: Thu, 08 Nov 2018 15:58:13 +0000 [thread overview]
Message-ID: <bug-107955-502-jjahbul0Zj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107955-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2932 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107955
--- Comment #26 from Ransu <gero3977@gmail.com> ---
Sorry for the lack of updates, life got in the way and then this week I made a
stupid mistake on where I was sending data with 'dd'. I didn't lose any
important data but it did force me to have to setup my laptop from scratch.
Good news! As of kernel 4.18.16 I no longer see an issue, knock on wood. I'm
going to give it a week and report back but the AMDGPU driver does not seem to
be reloading like mad anymore.
Linux Y40-80 4.18.16-arch1-1-ARCH #1 SMP PREEMPT Sat Oct 20 22:06:45 UTC 2018
x86_64 GNU/Linux
I get the following two messages whenever I request the AMD GPU with
"PRIME_DRI=1" and only when I request the AMD GPU. When I'm not making use of
the discrete graphics and only the dedicated Intel of my laptop I do not see
the below two messages repeated over and over anymore, nor do I see any
stuttering.
> [drm] PCIE gen 2 link speeds already enabled
> amdgpu 0000:05:00.0: PCIE GART of 1024M enabled (table at 0x000000F400000000).
One other thing I should note before I set up the system with AMDGPU by putting
the following kernel command line arguments into my grub config
"radeon.si_support=0 amdgpu.si_support=1" radeon alone would crash my
system. I needed to go into a different TTY before login into XFCE to get
things setup following this page https://wiki.archlinux.org/index.php/AMDGPU
>Nov 08 00:56:06 Y40-80 kernel: radeon 0000:05:00.0: fence driver on ring 4 use >gpu addr 0x0000000080000c10 and cpu addr 0x000000006a0bf82f
>Nov 08 00:56:06 Y40-80 kernel: radeon 0000:05:00.0: fence driver on ring 5 use >gpu addr 0x0000000000075a18 and cpu addr 0x000000003d1f62f3
>Nov 08 00:56:06 Y40-80 kernel: radeon 0000:05:00.0: failed VCE resume (-22).
>Nov 08 00:56:07 Y40-80 kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon: >ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
>Nov 08 00:56:07 Y40-80 kernel: [drm:si_resume [radeon]] *ERROR* si startup >failed on resume
>Nov 08 00:56:22 Y40-80 kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios >stuck in loop for more than 5secs aborting
>Nov 08 00:56:22 Y40-80 kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* >atombios stuck executing C078 (len 237, WS 0, PS 4) @ 0xC086
>Nov 08 00:56:22 Y40-80 kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* >atombios stuck executing B99E (len 78, WS 12, PS 8) @ 0xB9D7
So now that things appear to be working I just have a few more questions.
Does this mean that the discrete GPU should be making use of power saving
features and shouldn't be draining too much power if I'm not making use of it?
and
Does my card support AMDGPU-PRO drivers? If so is there any real advantage of
using the "PRO" extras over the standard open source driver?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3963 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-11-08 15:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-107955-502@http.bugs.freedesktop.org/>
2018-09-17 9:56 ` [Bug 107955] AMDGPU driver keeps reloading on hybrid graphics system causing stuttering bugzilla-daemon
2018-09-17 9:58 ` bugzilla-daemon
2018-09-17 10:48 ` bugzilla-daemon
2018-09-17 10:49 ` bugzilla-daemon
2018-09-17 10:49 ` bugzilla-daemon
2018-09-17 10:50 ` bugzilla-daemon
2018-09-17 10:52 ` bugzilla-daemon
2018-09-17 10:52 ` bugzilla-daemon
2018-09-17 11:05 ` bugzilla-daemon
2018-09-17 12:30 ` bugzilla-daemon
2018-09-17 12:36 ` bugzilla-daemon
2018-09-17 14:23 ` bugzilla-daemon
2018-09-17 14:53 ` bugzilla-daemon
2018-09-17 14:55 ` bugzilla-daemon
2018-09-17 15:52 ` bugzilla-daemon
2018-09-18 8:06 ` bugzilla-daemon
2018-09-18 9:32 ` bugzilla-daemon
2018-09-18 9:36 ` bugzilla-daemon
2018-09-18 9:56 ` bugzilla-daemon
2018-09-18 10:37 ` bugzilla-daemon
2018-09-18 14:22 ` bugzilla-daemon
2018-09-18 14:22 ` bugzilla-daemon
2018-09-18 14:24 ` bugzilla-daemon
2018-10-05 9:15 ` bugzilla-daemon
2018-10-05 9:49 ` bugzilla-daemon
2018-10-05 10:22 ` bugzilla-daemon
2018-10-05 10:24 ` bugzilla-daemon
2018-11-08 15:58 ` bugzilla-daemon [this message]
2018-11-08 16:05 ` bugzilla-daemon
2018-11-08 16:28 ` bugzilla-daemon
2018-11-16 14:01 ` bugzilla-daemon
2018-11-21 5:08 ` 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-107955-502-jjahbul0Zj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).