Hide Forgot
Created attachment 537542 [details] dmesg output after the gnome 3 freezed Description of problem: Version-Release number of selected component (if applicable): `uname -a` Linux mikolaj 3.1.2-1.fc16.i686 #1 SMP Tue Nov 22 08:56:28 UTC 2011 i686 i686 i386 GNU/Linux How reproducible: Start X environment login, wait until gnome 3 has started, then login to your account, press ctrl + alt + F8 , then press alt+F1 to return to X11.Gnome 3 is not responding , gnome shell is freezed, however I can move mouse around. Steps to Reproduce: 1. Login using gdm ( session gnome 3 ) 2. press ctrl + alt + F8 3. press alt + F1 Alternative Steps to Reproduce 1. Perform any operation that involves switching to framebuffer and back to X11 ( such as suspend-to-ram, suspend-to-disk etc.), the bug still occurs. Actual results: Window manager freezes ( however mouse pointer is 'movable' ) Expected results: Window manager should be usable after returning back to X. Additional info: Here is message ( full dmesg attached ) that pops up every time I reproduce this bug: '[drm:drm_mode_getfb] *ERROR* invalid framebuffer id' `lsmod`: ----------------------------- Module Size Used by ppdev 6176 0 parport_pc 16520 0 lp 6933 0 parport 26550 3 ppdev,parport_pc,lp fuse 53291 3 8021q 14099 0 garp 4938 1 8021q stp 1391 1 garp llc 3726 2 garp,stp fcoe 16098 0 libfcoe 26276 1 fcoe libfc 77580 2 fcoe,libfcoe scsi_transport_fc 35394 2 fcoe,libfc scsi_tgt 8879 1 scsi_transport_fc nf_conntrack_ftp 8223 0 ip6t_REJECT 3395 2 nf_conntrack_ipv4 6874 3 nf_defrag_ipv4 1093 1 nf_conntrack_ipv4 nf_conntrack_ipv6 6429 3 nf_defrag_ipv6 7174 1 nf_conntrack_ipv6 xt_state 942 6 nf_conntrack 56146 4 nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state ip6table_filter 1215 1 ip6_tables 9828 1 ip6table_filter arc4 1085 2 snd_hda_codec_analog 63109 1 snd_hda_intel 20691 2 snd_hda_codec 73778 2 snd_hda_codec_analog,snd_hda_intel snd_hwdep 4821 1 snd_hda_codec iwl3945 86060 0 iwl_legacy 108492 1 iwl3945 joydev 7179 0 snd_seq 43428 0 snd_seq_device 5033 1 snd_seq snd_pcm 63551 2 snd_hda_intel,snd_hda_codec snd_timer 15209 2 snd_seq,snd_pcm iTCO_wdt 9956 0 iTCO_vendor_support 2070 1 iTCO_wdt microcode 11041 0 i2c_i801 8021 0 e1000e 154800 0 thinkpad_acpi 57481 0 uinput 5397 0 irda 86499 0 snd 48367 13 snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer,thinkpad_acpi crc_ccitt 1245 1 irda snd_page_alloc 6031 2 snd_hda_intel,snd_pcm binfmt_misc 5379 1 soundcore 5027 1 snd mac80211 215740 2 iwl3945,iwl_legacy cfg80211 129051 3 iwl3945,iwl_legacy,mac80211 rfkill 12939 3 thinkpad_acpi,cfg80211 yenta_socket 19550 0 video 10740 0 radeon 625372 5 ttm 45950 1 radeon drm_kms_helper 23190 1 radeon drm 157196 7 radeon,ttm,drm_kms_helper i2c_algo_bit 4166 1 radeon i2c_core 21588 5 i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit -----------------------------
I didnt include the decription for this bug: Description of problem: After switching from X11 to console ( ctrl + alt + F8 ) and returning back ( alt + F1 ) window manager freezes and is not responding to any kind of interaction ( however I can move mouse pointer around ).Same thing happens after returning from suspend to ram or suspend to disk.
does booting with radeon.msi=0 on the kernel command line help?
I stopped using fedora 2 months ago ( too buggy on my thinkpad T60 :( ).When 17 is out I will try it again.
I decided to try out out fedora 16 once again and this bug is fixed/not triggered at all. Later this week I will check out that exact kernel version that I reported bug with.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.