From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16104] New: Radeon KMS does not start after merge of the new PM-Code
Date: Wed, 2 Jun 2010 07:47:24 GMT [thread overview]
Message-ID: <bug-16104-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16104
Summary: Radeon KMS does not start after merge of the new
PM-Code
Product: Drivers
Version: 2.5
Kernel Version: 2.6.35-rc1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: kontrollator@gmx.de
Regression: Yes
Created an attachment (id=26611)
--> (https://bugzilla.kernel.org/attachment.cgi?id=26611)
gitbisectresult
Using kernels after 2.6.34 with Radeon KMS does not work. Whenever the radeon
modeule becomes active the screen goes black with vertical dottet lines.
Disabling modeset lets the kernel start. KMS worked with the old code okay on
this machine. Its an latop from Fujitsu-Siemens with an x700 Mobility PCIE.
I tried an bisect run, bisect log said that
ce8a3eb20c4cb7d9e0c33e7560070688cd9066fc is the first bad commit. I tried to
revert it ontop of 2.6.35-rc1, the vertical dotted lines disappeared, however
system hangs forever with an black screen.
I attach bisect-log. If more Information is needed please tell me so.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
--
next reply other threads:[~2010-06-02 7:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 7:47 bugzilla-daemon [this message]
2010-06-02 7:48 ` [Bug 16104] Radeon KMS does not start after merge of the new PM-Code bugzilla-daemon
2010-06-02 8:19 ` bugzilla-daemon
2010-06-02 11:59 ` bugzilla-daemon
2010-06-02 12:40 ` bugzilla-daemon
2010-06-02 14:13 ` bugzilla-daemon
2010-06-02 14:16 ` bugzilla-daemon
2010-06-02 14:17 ` bugzilla-daemon
2010-06-02 15:02 ` bugzilla-daemon
2010-06-03 7:39 ` bugzilla-daemon
2010-06-03 11:09 ` bugzilla-daemon
2010-06-03 15:12 ` bugzilla-daemon
2010-06-03 15:42 ` bugzilla-daemon
2010-06-04 6:51 ` bugzilla-daemon
2010-06-04 9:24 ` bugzilla-daemon
2010-06-04 15:49 ` bugzilla-daemon
2010-06-04 20:15 ` bugzilla-daemon
2010-06-04 20:31 ` bugzilla-daemon
2010-06-05 6:01 ` bugzilla-daemon
2010-06-05 6:36 ` bugzilla-daemon
2010-06-05 21:05 ` bugzilla-daemon
2010-06-09 9:04 ` bugzilla-daemon
2010-06-09 9:04 ` 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-16104-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 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.