From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72921] DPM Power Cycle with AMD A8-6600K & MSI FM2-A55M-E33
Date: Sun, 08 Jun 2014 20:18:17 +0000 [thread overview]
Message-ID: <bug-72921-502-pT17ai5IB7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72921-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72921
--- Comment #10 from Kertesz Laszlo <laszlo.kertesz@infobenefic.ro> ---
Since this bug seems to be restricted to specific boards, without your help
will be hard to solve it.
You could try adjusting BIOS settings. Maybe you have some proprietary MSI
specific "performance booster" settings or OC activated?
Did you try resetting the BIOS to defaults?
Do you have some special brand of memory?
Also, looking at that dmesg output i see some lines beginning with "#" such as
Jun 3 15:24:01 172.22.15.56 [ 51.381984] #011ui class:
Jun 3 15:24:01 none
etc.
I dont have any of those in my dmesg and never had (A8-5500 and A8-6500 APUs on
Gigabyte boards).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1607 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-06-08 20:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 15:52 [Bug 72921] New: DPM Power Cycle with AMD A8-6600K & MSI FM2-A55M-E33 bugzilla-daemon
2013-12-20 15:58 ` [Bug 72921] " bugzilla-daemon
2013-12-20 15:59 ` bugzilla-daemon
2014-02-08 21:09 ` bugzilla-daemon
2014-06-03 13:44 ` bugzilla-daemon
2014-06-03 13:47 ` bugzilla-daemon
2014-06-03 13:57 ` bugzilla-daemon
2014-06-03 18:44 ` bugzilla-daemon
2014-06-05 11:08 ` bugzilla-daemon
2014-06-07 16:21 ` bugzilla-daemon
2014-06-08 6:51 ` bugzilla-daemon
2014-06-08 20:18 ` bugzilla-daemon [this message]
2014-06-08 23:39 ` bugzilla-daemon
2014-06-09 9:08 ` bugzilla-daemon
2014-06-09 10:03 ` bugzilla-daemon
2014-06-14 6:12 ` bugzilla-daemon
2014-06-16 14:34 ` bugzilla-daemon
2014-06-16 14:51 ` bugzilla-daemon
2014-06-16 19:24 ` bugzilla-daemon
2014-06-16 19:38 ` bugzilla-daemon
2014-06-16 19:40 ` bugzilla-daemon
2014-06-17 15:27 ` bugzilla-daemon
2014-06-17 19:43 ` bugzilla-daemon
2014-06-17 20:06 ` bugzilla-daemon
2014-06-17 20:17 ` bugzilla-daemon
2014-06-20 9:11 ` bugzilla-daemon
2014-06-20 13:30 ` bugzilla-daemon
2014-06-20 14:11 ` Laszlo Kertesz
2014-06-20 14:20 ` Alex Deucher
2014-06-23 10:05 ` bugzilla-daemon
2014-06-23 14:32 ` bugzilla-daemon
2014-06-30 19:04 ` bugzilla-daemon
2014-07-01 13:45 ` bugzilla-daemon
2014-07-03 12:24 ` bugzilla-daemon
2014-07-10 13:05 ` bugzilla-daemon
2014-07-10 17:06 ` bugzilla-daemon
2014-07-19 21:51 ` bugzilla-daemon
2014-07-21 4:08 ` bugzilla-daemon
2014-08-20 18:09 ` bugzilla-daemon
2014-08-20 18:54 ` bugzilla-daemon
2014-08-24 18:59 ` bugzilla-daemon
2014-09-04 3:33 ` bugzilla-daemon
2014-09-08 4:25 ` bugzilla-daemon
2014-09-08 4:45 ` bugzilla-daemon
2014-09-09 7:53 ` 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-72921-502-pT17ai5IB7@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).