[Bug 83731] New: dpm still not working on radeon TURKS 1002:6840

[Bug 83731] New: dpm still not working on radeon TURKS 1002:6840

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=83731

            Bug ID: 83731
           Summary: dpm still not working on radeon TURKS 1002:6840
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.17-rc
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: giancarlo.formicuccia@gmail.com
        Regression: No

Created attachment 149011
  --> https://bugzilla.kernel.org/attachment.cgi?id=149011&action=edit
kernel messages with dpm enabled

Now that dpm is enabled by default on TURKS cards, I'd like to give another try
to get it working on my card.

Booting a 3.17-rc3 kernel results in a blank screen; the computer is not locked
up, I still can ssh into the machine and grab the kernel messages.

lspci reports:

01:00.0 0300: 1002:6840 (rev ff) (prog-if ff)
        !!! Unknown header type 7f
        Kernel driver in use: radeon
        Kernel modules: radeon

01:00.1 0403: 1002:aa90 (rev ff) (prog-if ff)
        !!! Unknown header type 7f
        Kernel modules: snd_hda_intel

Loading the radeon module with dpm=0 works without problems.

Note that dpm *did* work correctly until 3.13 kernels (using dpm=1); then it
broke during the 3.14 delopement cycle. I bisected the bad commit in
6c7bccea390853bdec5b76fe31fc50f3b36f75d5
drm/radeon/pm: move pm handling into the asic specific code
and reported the problem on the dri-devel ml, without luck.
My guess is that something changed during the initialization of the card which
is confusing this GPU, but I was unable to identify the problem by myself.

Attached the kernel messages after loading the radeon module on 3.17-rc3.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 83731] dpm still not working on radeon TURKS 1002:6840

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=83731

--- Comment #1 from Giancarlo Formicuccia <giancarlo.formicuccia@gmail.com> ---
Kernel 3.17 is out and now radeon.dpm=0 is required in order to boot this
system.

Can I receive a comment about this problem? Why is this card special?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 83731] dpm still not working on radeon TURKS 1002:6840

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=83731

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com

--- Comment #2 from Alex Deucher <alexdeucher@gmail.com> ---
Does it work properly with radeon.runpm=0

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 83731] dpm still not working on radeon TURKS 1002:6840

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=83731

--- Comment #3 from Giancarlo Formicuccia <giancarlo.formicuccia@gmail.com> ---
No runpm=0 doesn't help.

I read from your comments on 6c7bccea390853bdec5b76fe31fc50f3b36f75d5 that the
initialization order changed, and it's possibly related to my problem.

FWIW, (last time I checked, more than one year ago), fglrx seems to have a
similar 'Unknown header type 7f' issue on this GPU. My bugreport on ATI
bugzilla is here:
http://ati.cchtml.com/show_bug.cgi?id=743

-- 
You are receiving this mail because:
You are watching the assignee of the bug.