dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 54662] New: [bisected] Kernel 3.6 breaks KMS on Radeon RV530 (black screen)
Date: Sat, 08 Sep 2012 06:42:16 +0000	[thread overview]
Message-ID: <bug-54662-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=54662

             Bug #: 54662
           Summary: [bisected] Kernel 3.6 breaks KMS on Radeon RV530
                    (black screen)
    Classification: Unclassified
           Product: DRI
           Version: unspecified
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: skitching@apache.org


Created attachment 66826
  --> https://bugs.freedesktop.org/attachment.cgi?id=66826
Dmesg output from a kernel that does not show black screen problem

The following commit (merged in 3.6 rc series) makes the screen go black
immediately after Plymouth completes (ie just before greeter screen):

876dc9f32907e57e0298bcd0f1607cb7a2582f63 is the first bad commit
commit 876dc9f32907e57e0298bcd0f1607cb7a2582f63
Author: Christian König <deathsimple@vodafone.de>
Date:   Tue May 8 14:24:01 2012 +0200

    drm/radeon: remove radeon_fence_create

Note that this is a different bug than
https://bugs.freedesktop.org/show_bug.cgi?id=54129 (which I'm also getting) but
might be related.

The same kernel boots without problems using "nomodeset".

System is an x86-32 laptop (about 5 years old) with Radeon mobility X1600,
running Ubuntu 12.04.

lspci reports:
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M56P
[Radeon Mobility X1600]

Attached is full dmesg output from a *different* (ie earlier, working) kernel.
Some relevant bits include:
[    2.978637] [drm] Initialized drm 1.1.0 20060810
[    3.052940] [drm] radeon defaulting to kernel modesetting.
[    3.052945] [drm] radeon kernel modesetting enabled.
[    3.053261] [drm] initializing kernel modesetting (RV530 0x1002:0x71C5
0x103C:0x30A3).
..
[    3.245417] [drm] Loading R500 Microcode
[    3.247401] [drm] radeon: ring at 0x0000000010001000
[    3.247441] [drm] ring test succeeded in 9 usecs
...
[    4.064745] [drm] Initialized radeon 2.17.0 20080528 for 0000:01:00.0 on
minor 0

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2012-09-08  6:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  6:42 bugzilla-daemon [this message]
2012-09-08 15:36 ` [Bug 54662] [bisected] Kernel 3.6 breaks KMS on Radeon RV530 (black screen) bugzilla-daemon
2012-09-08 15:37 ` bugzilla-daemon
2012-09-08 15:38 ` bugzilla-daemon
2012-09-09 13:43 ` bugzilla-daemon
2012-09-11 15:52 ` bugzilla-daemon
2012-09-16  7:20 ` bugzilla-daemon
2012-10-03 10:54 ` 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-54662-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).