From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 17692] New: Intermittent failure to resume from suspend-to-ram in radeon_resume
Date: Thu, 2 Sep 2010 23:46:13 GMT [thread overview]
Message-ID: <bug-17692-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=17692
Summary: Intermittent failure to resume from suspend-to-ram in
radeon_resume
Product: Drivers
Version: 2.5
Kernel Version: 2.6.35.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: bugs+kernel@karlt.net
Regression: No
TRACE_RESUMEs around this line indicate that it gets as far as radeon_resume,
but not as far as radeon_pm_resume:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.35.y.git;a=blob;f=drivers/gpu/drm/radeon/radeon_device.c;h=a7184636dcb494b36d470af30c2b513382d38019;hb=1506707a6c740db316e422239a53ae5df1727591#l798
Adding additional TRACE_RESUMEs earlier in radeon_resume_kms (and using them)
seems to make failure less frequent, as if there is a timing issue involved.
Possibly interesting messages on startup:
[drm] initializing kernel modesetting (RV515 0x1002:0x7145).
ATOM BIOS: M54CSP/M52CSP
[drm] Loading R500 Microcode
[drm] Initialized radeon 2.5.0 20080528 for 0000:01:00.0 on minor 0
and during successful resume:
radeon 0000:01:00.0: power state changed by ACPI to D0
radeon 0000:01:00.0: power state changed by ACPI to D0
radeon 0000:01:00.0: setting latency timer to 64
radeon 0000:01:00.0: ffff8800bfba5e00 unpin not necessary
[drm] radeon: 1 quad pipes, 1 z pipes initialized.
[drm] PCIE GART of 512M enabled (table at 0x00040000).
[drm] radeon: ring at 0x0000000008000000
[drm] ring test succeeded in 2 usecs
[drm] ib test succeeded in 0 usecs
ata1: EH complete
[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing EC38 (len 86,
WS 4, PS 0) @ 0xEC6B
PM: resume of devices complete after 1660.086 msecs
http://bugs.freedesktop.org/show_bug.cgi?id=27744
I have radeon.dynclks=1 on the command line.
I had intermittent resume failures even without this, though I haven't
confirmed that the failure is at the same point.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
--
next reply other threads:[~2010-09-02 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 23:46 bugzilla-daemon [this message]
2010-09-02 23:47 ` [Bug 17692] Intermittent failure to resume from suspend-to-ram in radeon_resume bugzilla-daemon
2010-09-03 4:41 ` bugzilla-daemon
2010-09-05 21:31 ` bugzilla-daemon
2010-09-10 5:56 ` bugzilla-daemon
2010-09-10 9:04 ` [Bug 17692] Intermittent failure to resume from suspend-to-ram in radeon_surface_init with RV515 bugzilla-daemon
2010-09-19 23:50 ` [Bug 17692] Intermittent failure to resume from suspend-to-ram in radeon_bo_get_surface_reg " bugzilla-daemon
2010-10-07 22:19 ` [Bug 17692] Intermittent failure to resume from suspend-to-ram in radeon_bo_get_surface_reg with RV515 and ColorTiling bugzilla-daemon
2010-10-07 22:21 ` bugzilla-daemon
2012-08-13 16:24 ` 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-17692-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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