From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103370] `DRI_PRIME=1 glxgears -info` halts the system with Intel Graphics [8086:5917] + AMD Graphics [1002:6665].
Date: Wed, 25 Oct 2017 04:31:56 +0000 [thread overview]
Message-ID: <bug-103370-502-0yBm72pLAH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103370-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103370
--- Comment #17 from Shih-Yuan Lee <fourdollars@gmail.com> ---
Created attachment 135027
--> https://bugs.freedesktop.org/attachment.cgi?id=135027&action=edit
Xorg.0.log
(In reply to Mike Lothian from comment #15)
> Are there any changes when you boot the system with radeon.runpm=0, this
> will mean the card never powers down
>
> What distro are you running?
>
> You mention trying older kernel version, did you try older mesa versions too?
>
> Can you attach your Xorg.0.log too
radeon.runpm=0 doesn't make any change.
I am running Ubuntu 16.04 LTS which using Linux kernel 4.4 and Mesa 11.2.0
before upgrading the system.
After the system upgraded, it uses Mesa 17.0.7 instead.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1947 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:[~2017-10-25 4:31 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 [this message]
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
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-0yBm72pLAH@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.