dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99316] Radeon crash when laptop on AC power
Date: Tue, 01 Aug 2017 17:31:12 +0000	[thread overview]
Message-ID: <bug-99316-502-KiMDQHFSM8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99316-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Samuel Anderson <LordSamanon@gmail.com> ---
(In reply to Mathias from comment #10)
> I have also a Dell notebook with the same dGPU, but cannot reproduce your
> error with Ubuntu 16.04 kernel 4.10.0.
> 
> Instead I have the problem, that the dGPU only gets powered at a low
> frequency, and becomes slower than the Intel GPU by doing so. 
> 
> When I run glmark2, I look at "/sys/kernel/debug/dri/0/radeon_pm_info" and
> always see the following output:
> 
> default engine clock: 925000 kHz
> current engine clock: 299990 kHz
> default memory clock: 1000000 kHz
> current memory clock: 148990 kHz
> voltage: 1225 mV
> PCIE lanes: 16
> 
> Btw.: This dGPU cannot be connected to a CRT directly, as there seems to be
> no connection available at all.

Is the GPU at low power while plugged in, or always?

glmark2 while plugged in instantly crashes for me, but on battery I get a score
of 1395 which is horrible compared to the 3680 from my integrated card. Plus
horrible rendering artifacts. But I'm not sure if that is really related to my
main problem.

This is "/sys/kernel/debug/dri/0/radeon_pm_info" on battery with glmark2 for
me:

uvd    vclk: 0 dclk: 0
power level 2    sclk: 40000 mclk: 30000 vddc: 900 vddci: 0 pcie gen: 3

Oddly enough, a completely different format than yours.

This card seems to have a multitude of problems

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

[-- Attachment #1.2: Type: text/html, Size: 2431 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-08-01 17:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07 21:05 [Bug 99316] Radeon crash when laptop on AC power bugzilla-daemon
2017-01-07 21:06 ` bugzilla-daemon
2017-01-07 21:19 ` bugzilla-daemon
2017-01-07 21:51 ` bugzilla-daemon
2017-01-08  0:35 ` bugzilla-daemon
2017-01-08  0:50 ` bugzilla-daemon
2017-01-08  1:03 ` bugzilla-daemon
2017-07-22 18:57 ` bugzilla-daemon
2017-07-22 19:00 ` bugzilla-daemon
2017-07-22 19:02 ` bugzilla-daemon
2017-07-24 19:20 ` bugzilla-daemon
2017-07-25  6:35 ` bugzilla-daemon
2017-08-01 17:31 ` bugzilla-daemon [this message]
2017-08-01 17:34 ` bugzilla-daemon
2018-01-14 19:50 ` bugzilla-daemon
2018-01-22 23:38 ` bugzilla-daemon
2019-11-19  9:22 ` 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-99316-502-KiMDQHFSM8@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