[Bug 21851] New: drm-next-radeon: r250 card unstable (regression)

[<bug...@fr...>]

http://bugs.freedesktop.org/show_bug.cgi?id=21851

           Summary: drm-next-radeon: r250 card unstable (regression)
           Product: DRI
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri...@li...
        ReportedBy: ste...@gm...


I've updated my KMS test setup to jglisse's drm-next-radeon
branch(b1e6187f5ad3c8b836a68009006584337d914e99) and
DDX(fba534017e581fcd9b9e49ba0b281fb500f576a7), and now the framebuffer console
and X server became highly unstable.

The framebuffer console very often causes kernel panics. When I compile the
modules into the kernel and boot with radeon.modeset=1, the kernel switches
successfully to the DRM provided framebuffer, writes "Initialized radeon 2.0.0
20080528 for 0000:01:00.0 on minor 0" and then panics.

I can successfully load the module with modesetting enabled by hand after a
full bootup(without an X server). However, the kernel panics whenever I run a
gentoo init script from /etc/init.d/. I suspect the crashes are related - right
after the kernel boot my initrd would show the password prompt for the LUKS
harddrive encryption.

If I avoid running one of the scripts and start the X server, the X server
complains that it cannot find any mode. Sometimes the framebuffer is restored
correctly, and sometimes I get another fault, but the system is still usable
via ssh.

I'll attach dmesg, Xorg output and lspci output.

This is a regression from David Airlie's modesetting kernel and DDX. Those ran
stably, and the X server started successfully. Is there a direct relation
between these versions? Might a git bisect work?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.