From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73947] [DPM] Cape Verde PRO - GPU lockup when dpm is enabled
Date: Sun, 26 Jan 2014 20:36:53 +0000 [thread overview]
Message-ID: <bug-73947-502-tIyYBrRhrd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73947-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73947
--- Comment #5 from Alexander Tsoy <alexander@tsoy.me> ---
Created attachment 92823
--> https://bugs.freedesktop.org/attachment.cgi?id=92823&action=edit
lspci-vvvnn.log
Looks like a hardware related problem. fglrx is also failing for me. According
to lspci, x16 PCI Express port is capable to provide only 25W, which is not
enough for CAPE VERDE. Also additional x8 PCI-E lines which is shared between
this port and the neighbour x8 port are not active. The motherboard is
Supermicro H8SCM.
LnkCap: Port #0, Speed 5GT/s, Width x8, ASPM L0s L1, Latency L0 <1us, L1
<8us
ClockPM- Surprise- LLActRep+ BwNot+
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
Slot #7, PowerLimit 25.000W; Interlock- NoCompl+
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1775 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-01-26 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 21:04 [Bug 73947] New: [DPM] Cape Verde PRO - GPU lockup when dpm is enabled bugzilla-daemon
2014-01-22 21:04 ` [Bug 73947] " bugzilla-daemon
2014-01-22 22:12 ` bugzilla-daemon
2014-01-23 20:03 ` bugzilla-daemon
2014-01-23 21:49 ` bugzilla-daemon
2014-01-26 20:36 ` bugzilla-daemon [this message]
2014-01-26 20:37 ` 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-73947-502-tIyYBrRhrd@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