reopen 603469 submitter 603469 ! retitle 603469 radeon: atombios stuck executing F6D8 (screen randomly goes black with no way to get it back) quit
Hi again, lauren wrote: > no problem and thanks for following up On second thought, I'm reopening this as an excuse to consider drm patches for backporting. I've set myself as submitter so hopefully you won't get any spam from it after this message. While I have your attention, could you help with one puzzle? The X log from the initial report contains: | Current Operating System: Linux BUZZ 2.6.32-5-686 #1 SMP Sat Oct 30 22:47:19 UTC 2010 i686 Which sounds like 2.6.32-27. But dmesg contains: | [ 7.120450] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0 | [ 949.420558] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting | [ 949.420570] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing F6D8 (len 487, WS 0, PS 4) @ 0xF719 This doesn't look like the standard squeeze kernel, since squeeze doesn't contain v2.6.34-rc4~12^2~50^2~17 (drm/radeon/kms: catch atombios infinite loop and break out of it, 2010-03-02). It can't be a mainline kernel, since the just-mentioned infinite loop checker was not introduced until after a radeon ABI bump (2.1.0). What did I miss? Puzzled, Jonathan (That mystery aside, here are some bugfix patches to consider backporting. - v2.6.34-rc4~12^2~50^2~17 (drm/radeon/kms: catch atombios infinite loop and break out of it, 2010-03-02) - v2.6.36-rc3~9^2~79^2~24 (drm/radeon/kms/atom: bump atom loop timeout from 1 sec to 5 secs, 2010-06-30) - v2.6.37-rc8~26^2~2 (drm/radeon/kms: reorder display resume to avoid problems, 2010-12-20): "This fixes the infamous atombios timeouts on resume.") -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110912224817.gb2...@elie.chipublib.org
