Description of problem: X server hangs after a short time of interactive use. Magic SysRq task dump shows that Xorg is in an uninterruptable sleep (waiting on IO that never happens?) in a syscall to the radeon and drm drivers. Version-Release number of selected component (if applicable): Linux palomino.walls.org 2.6.27.9-159.fc10.x86_64 #1 SMP Tue Dec 16 14:47:52 EST 2008 x86_64 x86_64 x86_64 GNU/Linux How reproducible: On demand, within 30 seconds, from within a logged in Gnome session. Steps to Reproduce: 1. Log into X/Gnome as a normal user 2. Bring up a Gnome Terminal window 3. "man smartctl" or some other long manpage in the window to fill with text 4. Grab the bottom left or right window corner and move the pointer around in a wide circle constantly resizing the terminal window 5. When X freezes: alt-sysrq-t alt-sysrq-s altsysrq-u alt-sysrq-b to dump the tasks, sync, unmount, and reboot Actual results: X hangs. The dumped task state from the alt-sysrq-t press shows Xorg in state D, uninterruptable: Xorg D 0000000000000000 0 2381 2380 ffff880031465918 0000000000000086 0000000000000000 ffff880000013888 ffffffff816e1500 ffffffff816e1500 ffff880034524530 ffffffff814ac340 ffff8800345248a8 0000000081768900 ffff8800314658c8 ffff8800345248a8 Call Trace: [<ffffffff8104b66b>] ? __mod_timer+0xbb/0xcd [<ffffffff813315eb>] schedule_timeout+0x8d/0xb4 [<ffffffff8104b034>] ? process_timeout+0x0/0xb [<ffffffff8104b5cc>] ? __mod_timer+0x1c/0xcd [<ffffffffa001aff5>] drm_fence_object_wait+0x1d5/0x22c [drm] [<ffffffff810551e1>] ? autoremove_wake_function+0x0/0x38 [<ffffffffa001ea6c>] drm_bo_move_accel_cleanup+0xb9/0x1db [drm] [<ffffffffa0051fc3>] radeon_move_zero_fill+0x63/0x6b [radeon] [<ffffffffa0052274>] radeon_move+0x3c/0x1f6 [radeon] [<ffffffffa001c413>] drm_bo_handle_move_mem+0x1ae/0x2a6 [drm] [<ffffffffa001d30d>] drm_bo_move_buffer+0xb1/0x174 [drm] [<ffffffff81031033>] ? need_resched+0x1e/0x28 [<ffffffffa001d6b5>] drm_bo_do_validate+0x2e5/0x54a [drm] [<ffffffff81031033>] ? need_resched+0x1e/0x28 [<ffffffffa004fa81>] radeon_gem_set_domain+0x100/0x147 [radeon] [<ffffffffa004faf3>] radeon_gem_do_relocate+0x2b/0x89 [radeon] [<ffffffffa0013019>] ? drm_gem_object_lookup+0x43/0x50 [drm] [<ffffffffa004fc0e>] radeon_gem_prelocate+0xbd/0x147 [radeon] [<ffffffffa00536fc>] radeon_cs2_ioctl+0x2b4/0x364 [radeon] [<ffffffffa0011d1d>] drm_ioctl+0x1d6/0x25e [drm] [<ffffffffa0053448>] ? radeon_cs2_ioctl+0x0/0x364 [radeon] [<ffffffff810cba87>] vfs_ioctl+0x5f/0x78 [<ffffffff810cbcda>] do_vfs_ioctl+0x23a/0x24b [<ffffffff810cbd40>] sys_ioctl+0x55/0x79 [<ffffffff8101024a>] system_call_fastpath+0x16/0x1b Expected results: X shouldn't hang. :) Additional info: I had to prevent drm.ko and radeon.ko from loading in modprobe.conf: install drm /bin/false install radeon /bin/false and also had to remove drm.ko and radeon.ko from the initrd image and remove the modprobe lines from the init script in the initrd image to get a reliable system that could use X. Of the numerous ATI/Xorg related bugs with Fedora 10, Bug 473175 caught my eye as maybe being related. $ lspci -tvnn -[0000:00]-+-00.0 ATI Technologies Inc RS480 Host Bridge [1002:5950] +-01.0-[0000:01]----05.0 ATI Technologies Inc RS480 [Radeon Xpress 200G Series] [1002:5954] +-12.0 ATI Technologies Inc IXP SB400 Serial ATA Controller [1002:4379] +-13.0 ATI Technologies Inc IXP SB400 USB Host Controller [1002:4374] +-13.1 ATI Technologies Inc IXP SB400 USB Host Controller [1002:4375] +-13.2 ATI Technologies Inc IXP SB400 USB2 Host Controller [1002:4373] +-14.0 ATI Technologies Inc IXP SB400 SMBus Controller [1002:4372] +-14.1 ATI Technologies Inc IXP SB400 IDE Controller [1002:4376] +-14.3 ATI Technologies Inc IXP SB400 PCI-ISA Bridge [1002:4377] +-14.4-[0000:02]--+-00.0 RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] | +-01.0 Agere Systems Device [11c1:0620] | +-02.0 Conexant CX23418 Single-Chip MPEG-2 Encoder with Integrated Analog Video/Broadcast Audio Decoder [14f1:5b7a] | \-03.0 Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] +-14.5 ATI Technologies Inc IXP SB400 AC'97 Audio Controller [1002:4370] +-18.0 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] +-18.1 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] +-18.2 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] \-18.3 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
Can you test with fedora 12 livecd and report if it works with it, if it doesn't work try to get dmesg of the livecd.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.