https://bugzilla.kernel.org/show_bug.cgi?id=65761 --- Comment #57 from Christoph Haag <haagch.christoph@xxxxxxxxxxxxxx> --- Long time, no update from me. Using 3.19-rc2: rmmod radeon works fine modprobe radeon after rmmod stalls once: [ 53.031311] radeon 0000:01:00.0: ring 5 stalled for more than 10000msec [ 53.032230] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000000 last fence id 0x0000000000000002 on ring 5) [ 53.032322] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). [ 53.033262] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-35). [ 53.037997] [drm] Radeon Display Connectors [ 53.041287] radeon 0000:01:00.0: No connectors reported connected with modes [ 53.041289] [drm] Cannot find any crtc or sizes - going 1024x768 [ 53.041834] [drm] fb mappable at 0xE0479000 [ 53.041835] [drm] vram apper at 0xE0000000 [ 53.041835] [drm] size 3145728 [ 53.041836] [drm] fb depth is 24 [ 53.041837] [drm] pitch is 4096 [ 53.041941] radeon 0000:01:00.0: fb1: radeondrmfb frame buffer device [ 53.042347] [drm] Initialized radeon 2.40.0 20080528 for 0000:01:00.0 on minor 1 but it recovers and then works. So rmmod radeon and modprobe radeon do not cause any critical errors anymore, it only is a bit annoying that modprobe radeon takes 10 seconds. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
