From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37939] New: Xorg crashes with radeon KMS after resume from suspend if card in gfx
Date: Sat, 4 Jun 2011 22:25:41 -0700 (PDT) [thread overview]
Message-ID: <bug-37939-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=37939
Summary: Xorg crashes with radeon KMS after resume from suspend
if card in gfx
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Keywords: regression
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: hramrach@gmail.com
cards: 220m rv515gl rv530 EG
problem 2: suspend kernel using uswsusp, cancel suspend by key or due to
insufficient memory -> X spinning in drm
tested on some combination of rv515 / rv530 and kernel somewhere around
2.6.37-2.6.38, EG on 2.6.39 (on 2.6.38 suspend has to be stopped manually, with
insufficient memory it locks up)
problem 1: suspend kernel using uswsusp, start framebuffer and splashy/usplash
before resume -> unusable graphics
tested with some old kernels on 220m and rv515gl, possibly related to problem 2
In general it seems resume can only happen from text mode, not graphics. In
response to this Debian disabled splash in early boot.
This is a Xorg regression compared to UMS.
--
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:[~2011-06-05 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 5:25 bugzilla-daemon [this message]
2011-09-05 13:17 ` [Bug 37939] Xorg crashes with radeon KMS after resume from suspend if card in gfx bugzilla-daemon
2011-09-05 13:18 ` bugzilla-daemon
2019-11-19 8:19 ` 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-37939-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.