From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29062] New: hp dv5000: xpress 200m 5955 + KMS does not resume from suspend
Date: Wed, 14 Jul 2010 12:00:47 -0700 (PDT) [thread overview]
Message-ID: <bug-29062-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29062
Summary: hp dv5000: xpress 200m 5955 + KMS does not resume from
suspend
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: acimmarusti@gmail.com
Created an attachment (id=37046)
--> (https://bugs.freedesktop.org/attachment.cgi?id=37046)
dmesg just after failed resume
When I try suspending using KMS my computer (an HP Pavilion dv5035nr laptop)
does not resume. Furthermore I've tried logging into it remotely to obtain a
backtrace from X with no success (following this procedure:
http://ubuntuforums.org/showthread.php?t=1228332). I'm letting NetworkManager
handle my network interfaces, however, I also tried using dhcp directly in the
/etc/network/interfaces file. The laptop screen is completely blank
so I can't switch to another session. The keyboard doesn't respond so it seems
like the kernel crashed.
When using UMS the resume process happens perfectly.
I dedicated a large portion of the day to finding a clue to this one.
Following this advice:
http://lxr.linux.no/#linux+v2.6.34.1/Documentation/power/s2ram.txt
I was able to extract a trace from the failed resume process:
Magic number: 0:981:799
hash matches drivers/base/power/main.c:523
pci 0000:01:05.0: hash matches
ec PNP0C09:00: hash matches
The first hash match is none other than my ATI Radeon card as I easily
verified with lspci:
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M
5955 (PCIE)
However, the above link says that the likely culprit in the failed resume
process is the last hash match. This corresponds to the EC driver:
http://lxr.free-electrons.com/source/drivers/acpi/ec.c
My card was, till recently, listed under embedded graphics at the AMD/ATI
website. So there appears to be some conflict when using KMS between radeon
and ec that causes the kernel to hang (that explains why I can't ssh into my
computer to get a trace).
I would appreciate some advice and guidance in further debugging this issue,
since I'm flying half-blind. I have compiled my kernel with support for
ACPI_DEBUG and I included a quirk David Airlie used to get suspend to work with
a HP nx6125 laptop but applied for my model
(http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=580b4fffbbdc3c899ee1f8189ba321bd60b48840)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-07-14 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 19:00 bugzilla-daemon [this message]
2010-07-14 19:01 ` [Bug 29062] hp dv5000: xpress 200m 5955 + KMS does not resume from suspend bugzilla-daemon
2010-07-14 19:03 ` bugzilla-daemon
2010-07-14 19:05 ` bugzilla-daemon
2010-07-14 19:13 ` bugzilla-daemon
2010-07-14 21:13 ` bugzilla-daemon
2010-07-16 3:57 ` bugzilla-daemon
2010-07-16 3:58 ` bugzilla-daemon
2010-07-22 3:55 ` 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-29062-502@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.