From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28342] New: When cold-booting gfx is messed up with latest drm-radeon-testing kernel
Date: Tue, 1 Jun 2010 04:08:02 -0700 (PDT) [thread overview]
Message-ID: <bug-28342-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28342
Summary: When cold-booting gfx is messed up with latest
drm-radeon-testing kernel
Product: DRI
Version: DRI CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: magnus@jensenligan.se
This only occurs when computer has been of for a long time (e.g over night)
Does not work either when booting into gdm, or booting into console and loading
radeon module manually.
If i first boot an vanilla kernel and go into X then warm-boot into d-r-t
kernel it will not show up anymore until next time i cold-boot.
It seems like the drm is having troubles initializing my gfx output.
My gfx card is an agp hd3650 (rv635)
--
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-06-01 11:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 11:08 bugzilla-daemon [this message]
2010-06-01 15:23 ` [Bug 28342] When cold-booting gfx is messed up with latest drm-radeon-testing kernel bugzilla-daemon
2010-06-01 15:56 ` bugzilla-daemon
2010-06-01 18:32 ` bugzilla-daemon
2010-06-02 9:26 ` bugzilla-daemon
2010-06-02 17:04 ` bugzilla-daemon
2010-06-02 17:07 ` bugzilla-daemon
2010-06-02 17:16 ` bugzilla-daemon
2010-06-02 17:52 ` bugzilla-daemon
2010-06-02 17:55 ` bugzilla-daemon
2010-06-02 21:17 ` bugzilla-daemon
2010-06-02 21:19 ` bugzilla-daemon
2010-06-02 21:28 ` bugzilla-daemon
2010-06-02 22:29 ` bugzilla-daemon
2010-06-02 22:46 ` bugzilla-daemon
2010-06-02 23:14 ` bugzilla-daemon
2010-06-03 9:52 ` bugzilla-daemon
2010-06-03 10:15 ` bugzilla-daemon
2010-06-03 14:22 ` bugzilla-daemon
2010-06-03 15:29 ` bugzilla-daemon
2010-06-03 20:43 ` bugzilla-daemon
2010-06-03 20:43 ` bugzilla-daemon
2010-06-03 20:44 ` bugzilla-daemon
2010-06-03 20:44 ` bugzilla-daemon
2010-06-03 20:55 ` bugzilla-daemon
2010-06-03 21:52 ` bugzilla-daemon
2010-06-03 21:52 ` bugzilla-daemon
2010-06-03 21:54 ` bugzilla-daemon
2010-06-03 22:34 ` bugzilla-daemon
2010-06-04 6:43 ` bugzilla-daemon
2010-06-06 16:00 ` bugzilla-daemon
2010-11-05 14:03 ` 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-28342-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.