Description of problem: starting mate-session after killing it Additional info: reporter: libreport-2.2.0 WARNING: CPU: 0 PID: 577 at drivers/gpu/drm/drm_crtc.c:2051 drm_mode_set_config_internal+0xb0/0xc0 [drm]() Modules linked in: ccm btusb fuse ipt_MASQUERADE xt_CHECKSUM tun bnep ip6t_rpfilter bluetooth ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec arc4 brcmsmac cordic brcmutil b43 mac80211 cfg80211 snd_hwdep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core ssb snd_seq mmc_core videodev media snd_seq_device hp_wmi kvm_amd sparse_keymap kvm snd_pcm rfkill snd_page_alloc microcode joydev snd_timer snd serio_raw soundcore k10temp wmi bcma r8169 sp5100_tco mii video i2c_piix4 acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc radeon i2c_algo_bit drm_kms_helper ttm drm i2c_core usb_storage CPU: 0 PID: 577 Comm: Xorg Not tainted 3.13.6-200.fc20.i686+PAE #1 Hardware name: Hewlett-Packard HP 625/1475, BIOS 68DVA Ver. F.06 12/07/2010 00000000 00000000 ed86fd6c c09c34dd 00000000 ed86fd9c c045607e c0b65018 00000000 00000241 f7efa41c 00000803 f7ee1fb0 f7ee1fb0 ebdf3900 f061f000 00000000 ed86fdac c0456142 00000009 00000000 ed86fdc0 f7ee1fb0 ebdf3900 Call Trace: [<c09c34dd>] dump_stack+0x41/0x52 [<c045607e>] warn_slowpath_common+0x7e/0xa0 [<f7ee1fb0>] ? drm_mode_set_config_internal+0xb0/0xc0 [drm] [<f7ee1fb0>] ? drm_mode_set_config_internal+0xb0/0xc0 [drm] [<c0456142>] warn_slowpath_null+0x22/0x30 [<f7ee1fb0>] drm_mode_set_config_internal+0xb0/0xc0 [drm] [<f7ee49ef>] drm_mode_setcrtc+0xdf/0x560 [drm] [<f7ee4910>] ? drm_mode_setplane+0x400/0x400 [drm] [<f7ed76f2>] drm_ioctl+0x472/0x500 [drm] [<f7ee4910>] ? drm_mode_setplane+0x400/0x400 [drm] [<c06864a2>] ? amiga_partition+0x362/0x4c0 [<c079e611>] ? __pm_runtime_resume+0x51/0x70 [<c06864a2>] ? amiga_partition+0x362/0x4c0 [<f809903e>] radeon_drm_ioctl+0x3e/0x70 [radeon] [<f8099000>] ? 0xf8098fff [<c0578222>] do_vfs_ioctl+0x2e2/0x4c0 [<c0642a72>] ? inode_has_perm.isra.32+0x32/0x40 [<c0642b8f>] ? file_has_perm+0x7f/0x90 [<c064357c>] ? selinux_file_ioctl+0x4c/0xf0 [<c0578460>] SyS_ioctl+0x60/0x80 [<c06864a2>] ? amiga_partition+0x362/0x4c0 [<c06864a2>] ? amiga_partition+0x362/0x4c0 [<c09d070d>] sysenter_do_call+0x12/0x28 [<c06864a2>] ? amiga_partition+0x362/0x4c0 [<c06864a2>] ? amiga_partition+0x362/0x4c0
Created attachment 877166 [details] File: dmesg
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.