[Bug 65761] New: HD 7970M Hybrid - hangs and errors and rmmod causes crash

[bugzilla-daemon at bugzilla.kernel.org]

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

            Bug ID: 65761
           Summary: HD 7970M Hybrid - hangs and errors and rmmod causes
                    crash
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.13-rc1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: haagch.christoph at googlemail.com
        Regression: No

Created attachment 115961
  --> https://bugzilla.kernel.org/attachment.cgi?id=115961&action=edit
dmesg with multiple issues

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Wimbledon XT [Radeon HD 7970M]
muxless, so there's no display outputs on the radeon gpu.

With 3.13 and dpm and runtime power management enabled by default this should
be getting usable.
I did not start X this time.
(when starting X on the intel gpu quickly after booting (presumably before
radeon is initialized) the display output hangs, which is yet another problem).

Dmesg seems to contain several issues.

1. While booting it already produces these before even "dpm initialized" is
logged:

[   20.120137] WARNING: CPU: 0 PID: 53 at drivers/gpu/drm/drm_mm.c:578
drm_mm_takedown+0x2e/0x30 [drm]()
[   20.120138] Memory manager not clean during takedown.

2. These are just periodically displayed in the tty:

[   79.179928] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
[   79.181378] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
GFX ring (-35).
[   79.182790] [drm:radeon_resume_kms] *ERROR* ib ring test failed (-35).

3. After some time in a tty, I did "rmmod radeon" and got some other issues
ending with

[  192.663059] Fixing recursive fault but reboot is needed!

and then, after a little while a lot of other errors happen, but they are not
captured here in the dmesg.

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