Created attachment 364787 [details] lspci My fedora 12 box get stucked after resume. I still able to reboot machine by ctrl+atl+del and have capslock activity.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 364955 [details] dmesg
Created attachment 364956 [details] messages
Created attachment 364957 [details] Xorg.0.log
======================================================= [ INFO: possible circular locking dependency detected ] 2.6.31.1-56.fc12.i686.PAE #1 ------------------------------------------------------- Xorg/1779 is trying to acquire lock: (&dev->struct_mutex){+.+.+.}, at: [<f7ea403f>] drm_mmap+0x38/0x65 [drm] but task is already holding lock: (&mm->mmap_sem){++++++}, at: [<c040dbe9>] sys_mmap2+0x72/0xb9 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #4 (&mm->mmap_sem){++++++}: [<c0478dd7>] __lock_acquire+0x9b3/0xb25 [<c0479000>] lock_acquire+0xb7/0xeb [<c04df4ed>] might_fault+0x73/0xa4 [<c060b00c>] copy_to_user+0x41/0x12b [<c050fbb8>] filldir64+0xc8/0x10d [<c0552abc>] sysfs_readdir+0x11a/0x161 [<c050fe3e>] vfs_readdir+0x7b/0xb8 [<c050fef6>] sys_getdents64+0x7b/0xcb [<c04099cb>] sysenter_do_call+0x12/0x38 [<ffffffff>] 0xffffffff -> #3 (sysfs_mutex){+.+.+.}: [<c0478dd7>] __lock_acquire+0x9b3/0xb25 [<c0479000>] lock_acquire+0xb7/0xeb [<c083a57c>] __mutex_lock_common+0x43/0x32b [<c083a957>] mutex_lock_nested+0x41/0x5a [<c0552e86>] sysfs_addrm_start+0x34/0xb2 [<c0551779>] sysfs_hash_and_remove+0x2d/0x71 [<c0553d00>] sysfs_remove_link+0x29/0x3c [<c04fab09>] sysfs_slab_add+0x57/0x189 [<c04fac7b>] sysfs_add_func+0x40/0x74 [<c045ff52>] worker_thread+0x194/0x275 [<c0464b25>] kthread+0x7b/0x80 [<c040a6bf>] kernel_thread_helper+0x7/0x10 [<ffffffff>] 0xffffffff -> #2 (slub_lock){+++++.}: [<c0478dd7>] __lock_acquire+0x9b3/0xb25 [<c0479000>] lock_acquire+0xb7/0xeb [<c083ac92>] down_read+0x45/0x93 [<c083820a>] slab_cpuup_callback+0x50/0x13e [<c083e457>] notifier_call_chain+0x5d/0x95 [<c0469dc6>] __raw_notifier_call_chain+0x23/0x39 [<c083717e>] _cpu_up+0x6d/0x121 [<c0837289>] cpu_up+0x57/0x78 [<c0a9d42a>] kernel_init+0xba/0x211 [<c040a6bf>] kernel_thread_helper+0x7/0x10 [<ffffffff>] 0xffffffff -> #1 (cpu_hotplug.lock){+.+.+.}: [<c0478dd7>] __lock_acquire+0x9b3/0xb25 [<c0479000>] lock_acquire+0xb7/0xeb [<c083a57c>] __mutex_lock_common+0x43/0x32b [<c083a957>] mutex_lock_nested+0x41/0x5a [<c044dc15>] get_online_cpus+0x44/0x67 [<c0419681>] mtrr_del_page+0x40/0x131 [<c04197b6>] mtrr_del+0x44/0x5b [<f7e9bb62>] drm_rmmap_locked+0xc4/0x186 [drm] [<f7ea29fa>] drm_master_destroy+0x61/0xe1 [drm] [<c06051c7>] kref_put+0x47/0x62 [<f7ea2905>] drm_master_put+0x25/0x40 [drm] [<f7e9f588>] drm_release+0x37b/0x45b [drm] [<c05036de>] __fput+0x101/0x1a9 [<c05037ad>] fput+0x27/0x3a [<c04ffe96>] filp_close+0x64/0x7f [<c04fff2d>] sys_close+0x7c/0xc2 [<c04099cb>] sysenter_do_call+0x12/0x38 [<ffffffff>] 0xffffffff -> #0 (&dev->struct_mutex){+.+.+.}: [<c0478cde>] __lock_acquire+0x8ba/0xb25 [<c0479000>] lock_acquire+0xb7/0xeb [<c083a57c>] __mutex_lock_common+0x43/0x32b [<c083a957>] mutex_lock_nested+0x41/0x5a [<f7ea403f>] drm_mmap+0x38/0x65 [drm] [<c04e7924>] mmap_region+0x26e/0x40d [<c04e7d4c>] do_mmap_pgoff+0x289/0x2ec [<c040dbfd>] sys_mmap2+0x86/0xb9 [<c04099cb>] sysenter_do_call+0x12/0x38 [<ffffffff>] 0xffffffff other info that might help us debug this: 1 lock held by Xorg/1779: #0: (&mm->mmap_sem){++++++}, at: [<c040dbe9>] sys_mmap2+0x72/0xb9 stack backtrace: Pid: 1779, comm: Xorg Not tainted 2.6.31.1-56.fc12.i686.PAE #1 Call Trace: [<c0839114>] ? printk+0x22/0x36 [<c047810c>] print_circular_bug_tail+0x68/0x84 [<c0478cde>] __lock_acquire+0x8ba/0xb25 [<c0479000>] lock_acquire+0xb7/0xeb [<f7ea403f>] ? drm_mmap+0x38/0x65 [drm] [<f7ea403f>] ? drm_mmap+0x38/0x65 [drm] [<c083a57c>] __mutex_lock_common+0x43/0x32b [<f7ea403f>] ? drm_mmap+0x38/0x65 [drm] [<f7ea403f>] ? drm_mmap+0x38/0x65 [drm] [<c04f9b13>] ? kmem_cache_alloc+0xcb/0x159 [<c0477a39>] ? trace_hardirqs_on_caller+0x122/0x155 [<c083a957>] mutex_lock_nested+0x41/0x5a [<f7ea403f>] ? drm_mmap+0x38/0x65 [drm] [<f7ea403f>] drm_mmap+0x38/0x65 [drm] [<c04e7924>] mmap_region+0x26e/0x40d [<c04e7d4c>] do_mmap_pgoff+0x289/0x2ec [<c040dbfd>] sys_mmap2+0x86/0xb9 [<c04099cb>] sysenter_do_call+0x12/0x38 [drm] Setting GART location based on new memory map [drm] Loading R500 Microcode platform radeon_cp.0: firmware: requesting radeon/R520_cp.bin [drm] Num pipes: 1 [drm] writeback test succeeded in 1 usecs fuse init (API version 7.12) SELinux: initialized (dev fuse, type fuse), uses genfs_contexts wlan0: authenticate with AP 00:1c:f0:bd:01:06 wlan0: authenticated wlan0: associate with AP 00:1c:f0:bd:01:06 wlan0: RX AssocResp from 00:1c:f0:bd:01:06 (capab=0x431 status=0 aid=1) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready padlock: VIA PadLock not detected.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
i configm this issue for f12 with last updates. still unable to resume from suspend within UMS mode
f12 now fine (at least for x64 arch, i did reinstall my fedora to x64 version)
i was too fast. fedora can resume machine only once. after suspend/resume all tty consoles are broken, if i try to switch to one machine going to hang. it hang again if i try to suspend second time (because fedora trying to switch to console before go suspend)
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.