Hide Forgot
Description of problem: system appears to hang somewhere in X11 (display). noticed these messages; added drm.debug=0x04 to kernel line Version-Release number of selected component (if applicable): libdrm-2.4.22-2.fc14.x86_64 How reproducible: Always. Steps to Reproduce: 1.Just leave the system alone for a while, til power saver turns down the monitor 2. 3. Actual results: Display freezes showing the desktop. ctrl-alt-f2 switches to tty2; alt right arrow goes back to tty7; sometimes freeze is resolved. Expected results: Additional info: noticed the libdrm i686 and x86_64 versions installed. This is x86_64 system. rpm -qa | grep drm libdrm-2.4.22-2.fc14.i686 libdrm-devel-2.4.22-2.fc14.x86_64 libdrm-2.4.22-2.fc14.x86_64 libdrm-debuginfo-2.4.22-2.fc14.x86_64 tail /var/log/messages Nov 7 19:38:26 clipper kernel: [ 1136.019412] sd 11:0:0:0: [sdd] Assuming drive cache: write through Nov 7 19:38:26 clipper kernel: [ 1136.019425] sdd: sdd1 Nov 7 19:38:26 clipper kernel: [ 1136.073916] sd 11:0:0:0: [sdd] Assuming drive cache: write through Nov 7 19:38:26 clipper kernel: [ 1136.073927] sd 11:0:0:0: [sdd] Attached SCSI disk Nov 7 19:38:44 clipper kernel: [ 1153.677198] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Nov 7 19:38:44 clipper kernel: [ 1154.047302] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) Nov 7 19:38:44 clipper kernel: [ 1154.375729] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null) Nov 7 20:16:38 clipper kernel: [ 3427.690267] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:16:38 clipper kernel: [ 3427.690278] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297 Nov 7 20:16:39 clipper kernel: [ 3428.737266] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:16:39 clipper kernel: [ 3428.737278] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297 Nov 7 20:21:40 clipper kernel: [ 3730.286016] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:21:40 clipper kernel: [ 3730.286028] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297 Nov 7 20:26:39 clipper kernel: [ 4029.355267] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:26:39 clipper kernel: [ 4029.355279] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297 Nov 7 20:30:47 clipper kernel: [ 4276.574573] hrtimer: interrupt took 2241976 ns Nov 7 20:43:50 clipper kernel: [ 5059.706016] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:43:50 clipper kernel: [ 5059.706028] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297 Nov 7 20:43:51 clipper kernel: [ 5060.718013] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:43:51 clipper kernel: [ 5060.718025] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297 Nov 7 20:48:52 clipper kernel: [ 5362.250265] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:48:52 clipper kernel: [ 5362.250278] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297 Nov 7 20:53:51 clipper kernel: [ 5661.459016] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting Nov 7 20:53:51 clipper kernel: [ 5661.459029] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E266 (len 82, WS 4, PS 4) @ 0xE297
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping