Bug 595655 - radeon [M24] Broken KMS support
Summary: radeon [M24] Broken KMS support
Status: RESOLVED DUPLICATE of bug 595653
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Factory
Hardware: i586 openSUSE 11.3
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-12 08:47 UTC by Robin Knapp
Modified: 2010-04-12 15:58 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Knapp 2010-04-12 08:47:29 UTC 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

I've tested Live CD/USB Build 553 (M5) on a notebook with a Radeon X600 Mobility.
The radeon module does not get loaded automatically during boot (see Bug 595653), but if I boot into runlevel 3 and modprobe radeon manually, KMS gets activated (switches automatically to native LCD resolution).

If I start X after loading the module, the screen first gets corrupted (looks like some random memory content), and a few seconds later I see the KDE splash screen.
So in general this works, but it is painfully slow and the GPU fan turns up.

After a while, GPU reset messages are shown on the console:

[  124.160085] [drm:radeon_fence_wait] *ERROR* fence(f6a14e60:0x00000005) 508ms timeout going to reset GPU
[  124.161490] [drm] CP reset succeed (RBBM_STATUS=0x00000140)
[  124.161496] [drm] radeon: cp idle (0x10000000)
[  124.161532] [drm] radeon: ring at 0x00000000B0000000
[  124.161557] [drm] ring test succeeded in 0 usecs
[  124.161563] [drm] GPU reset succeed (RBBM_STATUS=0x00000140)
[  124.161571] [drm:radeon_fence_wait] *ERROR* fence(f6a14e60:0x00000005) 516ms timeout
[  124.161577] [drm:radeon_fence_wait] *ERROR* last signaled fence(0x00000005)

See attachment 353616 [details] of bug 574749 for full dmesg output

Reproducible: Always

Steps to Reproduce:
1. boot live cd/usb into runlevel 3 on notebook with X600 Mobility
2. modprobe radeon
3. init 5
Comment 1 Robin Knapp 2010-04-12 08:49:50 UTC 
Forgot the hwinfo:

25: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.318]
  Unique ID: VCu0.OEBUnlVxQI8
  Parent ID: vSkL.RA714lUVE7D
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "ATI Radeon Mobility X600 (M24) 3150 (PCIE)"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x3150 "Radeon Mobility X600 (M24) 3150 (PCIE)"
  SubVendor: pci 0x10cf "Fujitsu Limited."
  SubDevice: pci 0x12f5 
  Driver: "radeon"
  Driver Modules: "drm"
  Memory Range: 0xd0000000-0xd7ffffff (ro,non-prefetchable)
  I/O Ports: 0x3000-0x3fff (rw)
  Memory Range: 0xc8100000-0xc810ffff (rw,non-prefetchable)
  Memory Range: 0xc8120000-0xc813ffff (ro,non-prefetchable,disabled)
  IRQ: 27 (1377 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00001002d00003150sv000010CFsd000012F5bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: radeon
  Driver Info #1:
    XFree86 v4 Server Module: radeon
    3D Support: yes
    Extensions: dri
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #10 (PCI bridge)

Primary display adapter: #25
Comment 2 Robin Knapp 2010-04-12 09:04:44 UTC 
Could it be a problem with fb vga mode which is set when booting the live cd?
Will test a real installation later this week...
Comment 3 Stefan Dirsch 2010-04-12 09:11:43 UTC 
(In reply to comment #2)
> Could it be a problem with fb vga mode which is set when booting the live cd?

Need to check that.
Comment 4 Stefan Dirsch 2010-04-12 15:34:52 UTC 
I don't see that issue with my M24 card.
Comment 5 Stefan Dirsch 2010-04-12 15:56:33 UTC 
Meanwhile I *do* see this issue with my M24 card with KMS enabled.
Comment 6 Stefan Dirsch 2010-04-12 15:58:10 UTC 
Finally close as duplicate.

*** This bug has been marked as a duplicate of bug 595653 ***