| What | Removed | Added |
|---|---|---|
| Status | NEW | ASSIGNED |
Comment # 4
on bug 66714
from Marco Trevisan (Treviño)
So, I've tried the patch on a 3.10 kernel that was affected and... Great, it Works! :) FYI, I've also added a couple of error logs in the code to see where exactly the failure was and this was the result: [ 2.073137] [drm] fb mappable at 0xC035F000 [ 2.073139] [drm] vram apper at 0xC0000000 [ 2.073140] [drm] size 8294400 [ 2.073141] [drm] fb depth is 24 [ 2.073142] [drm] pitch is 7680 [ 2.073252] fbcon: radeondrmfb (fb0) is primary device [ 2.073323] [drm:evergreen_hdmi_enable] *ERROR* Invalid DIG (dig: ffff880229d0fc00, dig->afmt: (null)) /home/marco/Dev/debs/linux-3.10.0/drivers/gpu/drm/radeon/evergreen_hdmi.c:298 [ 2.573589] [drm:evergreen_hdmi_enable] *ERROR* Invalid DIG (dig: ffff880229d0fc00, dig->afmt: (null)) /home/marco/Dev/debs/linux-3.10.0/drivers/gpu/drm/radeon/evergreen_hdmi.c:298 [ 2.607449] Console: switching to colour frame buffer device 170x48 [ 2.610160] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [ 2.610162] radeon 0000:01:00.0: registered panic notifier [ 2.610237] [drm] Initialized radeon 2.33.0 20080528 for 0000:01:00.0 on minor 0 Full dmesg at http://pastebin.ubuntu.com/5873667/ I don't know if this may be only the side effect of another issue (wrong initialization order?). One more thing I discovered in the past days, is that the kernel crash was not happening in case that the HDMI was plugged after that ligthtdm was running (attaching it anytime before was leading to a freeze).
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
