Arch Linux

smpolymen

Member

Registered: 2010-03-21

Posts: 12

[SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

I just rebooted my desktop after a couple of months and now I cannot run Xorg. When I run startx, I get a black screen for two minutes and then a backtrace pops up. At that point I can no longer interact with the console, but I can still ssh and run commands. I've tried setting Xwrapper.conf to needs_root_rights = yes and I have tried just running startx as root, with no help. I'm not sure how to isolate what would have broken this as I have updated so many packages in the last two months. Any ideas what I can try next?

If it helps, I am using the open source ati driver and my xorg.conf.d is empty.

Here is the dmesg showing the oops and the backtrace:

[   72.778340] BUG: unable to handle kernel paging request at ffffec2003fffe00
[   72.778368] IP: [<ffffffff811ac636>] kfree+0x56/0x1a0
[   72.778389] PGD 0
[   72.778397] Oops: 0000 [#1] PREEMPT SMP
[   72.778413] Modules linked in: cfg80211 it87 hwmon_vid xpad ff_memless fuse mousedev joydev eeepc_wmi asus_wmi sparse_keymap led_class rfkill video evdev mxm_wmi mac_hid kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse serio_raw radeon r8169 snd_hda_codec_realtek edac_core fam15h_power mii k10temp snd_hda_codec_generic edac_mce_amd sp5100_tco ttm snd_hda_codec_hdmi drm_kms_helper i2c_piix4 snd_hda_intel snd_hda_controller drm snd_hda_codec snd_hwdep snd_pcm hwmon i2c_algo_bit snd_timer i2c_core snd soundcore tpm_infineon tpm_tis tpm wmi shpchp button processor sch_fq_codel vboxnetflt(O) vboxnetadp(O) vboxdrv(O) ext4 crc16 mbcache jbd2 hid_generic usbhid hid sd_mod crc_t10dif crct10dif_common sr_mod
[   72.778702]  cdrom atkbd libps2 ohci_pci ohci_hcd ehci_pci ahci sata_sil libahci xhci_hcd ehci_hcd libata usbcore usb_common scsi_mod i8042 serio zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O)
[   72.779931] CPU: 7 PID: 1534 Comm: Xorg.bin Tainted: P           O   3.17.4-1-ARCH #1
[   72.781110] Hardware name: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 1503 01/11/2013
[   72.782332] task: ffff880808b264a0 ti: ffff8807fcd30000 task.ti: ffff8807fcd30000
[   72.783574] RIP: 0010:[<ffffffff811ac636>]  [<ffffffff811ac636>] kfree+0x56/0x1a0
[   72.784796] RSP: 0018:ffff8807fcd33a30  EFLAGS: 00010286
[   72.786010] RAX: 0000022003fffe00 RBX: 00001000ffff8807 RCX: 0000000000010005
[   72.787227] RDX: 000077ff80000000 RSI: 0000000000000007 RDI: 00001000ffff8807
[   72.788446] RBP: ffff8807fcd33a48 R08: 0000000000000007 R09: ffffec2003fffe00
[   72.789714] R10: 0000000000000017 R11: 0000000000000000 R12: ffff88080887a400
[   72.790978] R13: ffffffffa0678f8c R14: 00000000000108f0 R15: 0000000000001800
[   72.792211] FS:  00007f0dd095e8c0(0000) GS:ffff88083edc0000(0000) knlGS:0000000000000000
[   72.793455] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   72.794680] CR2: ffffec2003fffe00 CR3: 00000000b7c0c000 CR4: 00000000000407e0
[   72.795924] Stack:
[   72.797140]  ffff880811db0000 ffff88080887a400 ffff880811db0000 ffff8807fcd33b30
[   72.798358]  ffffffffa0678f8c 000000000000004c 000108480001092c ffff880700000008
[   72.799584]  0000ffff00010844 000000000001092c 0000000000010848 0000000000010844
[   72.800809] Call Trace:
[   72.802053]  [<ffffffffa0678f8c>] evergreen_hdmi_setmode+0xd8c/0x1970 [radeon]
[   72.803320]  [<ffffffffa052b8d4>] ? drm_detect_hdmi_monitor+0x74/0xc0 [drm]
[   72.804555]  [<ffffffffa0681488>] radeon_atom_encoder_mode_set+0x178/0x3c0 [radeon]
[   72.805789]  [<ffffffffa0563986>] drm_crtc_helper_set_mode+0x356/0x530 [drm_kms_helper]
[   72.807017]  [<ffffffffa061b97c>] radeon_property_change_mode.isra.1+0x3c/0x40 [radeon]
[   72.808240]  [<ffffffffa061bb2e>] radeon_connector_set_property+0x1ae/0x3f0 [radeon]
[   72.809490]  [<ffffffffa05284e2>] drm_mode_obj_set_property_ioctl+0x1b2/0x3a0 [drm]
[   72.810736]  [<ffffffffa052870f>] drm_mode_connector_property_set_ioctl+0x3f/0x60 [drm]
[   72.811961]  [<ffffffffa0518fef>] drm_ioctl+0x1df/0x680 [drm]
[   72.813175]  [<ffffffff8105e9ac>] ? __do_page_fault+0x2ec/0x600
[   72.814402]  [<ffffffffa05f404c>] radeon_drm_ioctl+0x4c/0x80 [radeon]
[   72.815649]  [<ffffffff811da5f0>] do_vfs_ioctl+0x2d0/0x4b0
[   72.816899]  [<ffffffff811ca161>] ? __sb_end_write+0x31/0x60
[   72.818124]  [<ffffffff811da851>] SyS_ioctl+0x81/0xa0
[   72.819332]  [<ffffffff8153db29>] system_call_fastpath+0x16/0x1b
[   72.820528] Code: 00 00 00 80 ff 77 00 00 49 b9 00 00 00 00 00 ea ff ff 48 01 d8 48 0f 42 15 e8 b9 66 00 48 01 d0 48 c1 e8 0c 48 c1 e0 06 49 01 c1 <49> 8b 01 f6 c4 80 0f 85 0e 01 00 00 49 8b 01 a8 80 0f 84 83 00
[   72.823135] RIP  [<ffffffff811ac636>] kfree+0x56/0x1a0
[   72.824394]  RSP <ffff8807fcd33a30>
[   72.825653] CR2: ffffec2003fffe00
[  240.461007] INFO: task Xorg.bin:1534 blocked for more than 120 seconds.
[  240.462414]       Tainted: P           O   3.17.4-1-ARCH #1
[  240.463701] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  240.465017] Xorg.bin        D 0000000000000007     0  1534   1533 0x00000000
[  240.466325]  ffff8807fcd333b0 0000000000000082 ffff880808b264a0 00000000000145c0
[  240.467623]  ffff8807fcd33fd8 00000000000145c0 ffff880812e73250 ffff880808b264a0
[  240.468886]  0000000000000080 0000000000000140 0000000000001e00 000000000000000a
[  240.470155] Call Trace:
[  240.471435]  [<ffffffff813113db>] ? bit_putcs+0x30b/0x590
[  240.472702]  [<ffffffff81539519>] schedule+0x29/0x70
[  240.473964]  [<ffffffff81539986>] schedule_preempt_disabled+0x16/0x20
[  240.475239]  [<ffffffff8153b445>] __mutex_lock_slowpath+0xe5/0x250
[  240.476495]  [<ffffffff8153b5c7>] mutex_lock+0x17/0x30
[  240.477770]  [<ffffffffa0522f32>] drm_modeset_lock_all+0x42/0xd0 [drm]
[  240.479016]  [<ffffffffa056d07f>] drm_fb_helper_pan_display+0x2f/0xf0 [drm_kms_helper]
[  240.480257]  [<ffffffff8131683a>] fb_pan_display+0x9a/0x160
[  240.481508]  [<ffffffff81310950>] bit_update_start+0x20/0x50
[  240.482732]  [<ffffffff8130e15e>] fbcon_switch+0x3ae/0x5e0
[  240.483936]  [<ffffffff81385899>] redraw_screen+0x1a9/0x250
[  240.485175]  [<ffffffff8130d54a>] fbcon_blank+0x23a/0x340
[  240.486375]  [<ffffffff8113e74f>] ? irq_work_queue+0xf/0xa0
[  240.487587]  [<ffffffff810c476c>] ? wake_up_klogd+0x3c/0x60
[  240.488771]  [<ffffffff810c4a12>] ? console_unlock+0x282/0x460
[  240.489894]  [<ffffffff810d5d33>] ? internal_add_timer+0x63/0x80
[  240.490988]  [<ffffffff810d6c54>] ? mod_timer+0x114/0x250
[  240.492058]  [<ffffffff813863ba>] do_unblank_screen+0xaa/0x1d0
[  240.493075]  [<ffffffff813864f0>] unblank_screen+0x10/0x20
[  240.494053]  [<ffffffff812b7019>] bust_spinlocks+0x19/0x40
[  240.495011]  [<ffffffff810186b4>] oops_end+0x34/0xe0
[  240.495982]  [<ffffffff8105df4c>] no_context+0x17c/0x3c0
[  240.496934]  [<ffffffff8105e2bd>] __bad_area_nosemaphore+0x12d/0x250
[  240.497886]  [<ffffffff8105e3f3>] bad_area_nosemaphore+0x13/0x20
[  240.498842]  [<ffffffff8105ea04>] __do_page_fault+0x344/0x600
[  240.499769]  [<ffffffffa060fb4b>] ? atom_execute_table_locked+0x12b/0x3f0 [radeon]
[  240.500709]  [<ffffffffa060e7c0>] ? atom_put_dst+0x480/0x560 [radeon]
[  240.501673]  [<ffffffffa060dabb>] ? atom_op_test+0x9b/0x1b0 [radeon]
[  240.502640]  [<ffffffffa0678f8c>] ? evergreen_hdmi_setmode+0xd8c/0x1970 [radeon]
[  240.503558]  [<ffffffff8105ece2>] do_page_fault+0x22/0x30
[  240.504494]  [<ffffffff8153f9f8>] page_fault+0x28/0x30
[  240.505441]  [<ffffffffa0678f8c>] ? evergreen_hdmi_setmode+0xd8c/0x1970 [radeon]
[  240.506373]  [<ffffffff811ac636>] ? kfree+0x56/0x1a0
[  240.507266]  [<ffffffffa0678f8c>] evergreen_hdmi_setmode+0xd8c/0x1970 [radeon]
[  240.508204]  [<ffffffffa052b8d4>] ? drm_detect_hdmi_monitor+0x74/0xc0 [drm]
[  240.509155]  [<ffffffffa0681488>] radeon_atom_encoder_mode_set+0x178/0x3c0 [radeon]
[  240.510085]  [<ffffffffa0563986>] drm_crtc_helper_set_mode+0x356/0x530 [drm_kms_helper]
[  240.511021]  [<ffffffffa061b97c>] radeon_property_change_mode.isra.1+0x3c/0x40 [radeon]
[  240.511944]  [<ffffffffa061bb2e>] radeon_connector_set_property+0x1ae/0x3f0 [radeon]
[  240.512875]  [<ffffffffa05284e2>] drm_mode_obj_set_property_ioctl+0x1b2/0x3a0 [drm]
[  240.513791]  [<ffffffffa052870f>] drm_mode_connector_property_set_ioctl+0x3f/0x60 [drm]
[  240.514728]  [<ffffffffa0518fef>] drm_ioctl+0x1df/0x680 [drm]
[  240.515632]  [<ffffffff8105e9ac>] ? __do_page_fault+0x2ec/0x600
[  240.516555]  [<ffffffffa05f404c>] radeon_drm_ioctl+0x4c/0x80 [radeon]
[  240.517455]  [<ffffffff811da5f0>] do_vfs_ioctl+0x2d0/0x4b0
[  240.518369]  [<ffffffff811ca161>] ? __sb_end_write+0x31/0x60
[  240.519267]  [<ffffffff811da851>] SyS_ioctl+0x81/0xa0
[  240.520176]  [<ffffffff8153db29>] system_call_fastpath+0x16/0x1b
[  360.455851] INFO: task Xorg.bin:1534 blocked for more than 120 seconds.
[  360.456839]       Tainted: P           O   3.17.4-1-ARCH #1
[  360.457713] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  360.458629] Xorg.bin        D 0000000000000007     0  1534   1533 0x00000000
[  360.459548]  ffff8807fcd333b0 0000000000000082 ffff880808b264a0 00000000000145c0
[  360.460442]  ffff8807fcd33fd8 00000000000145c0 ffff880812e73250 ffff880808b264a0
[  360.461294]  0000000000000080 0000000000000140 0000000000001e00 000000000000000a
[  360.462160] Call Trace:
[  360.463040]  [<ffffffff813113db>] ? bit_putcs+0x30b/0x590
[  360.463880]  [<ffffffff81539519>] schedule+0x29/0x70
...

I do not see any errors in my Xorg.0.log file, but I've posted it here

Last edited by smpolymen (2014-12-06 04:04:55)

Xezlec

Member

Registered: 2014-11-30

Posts: 41

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

My first attempt at isolating it would be to run X directly without startx or anything.  Have you tried something like "X --retro --nolisten tcp vt1"?  (This must be typed at tty1.)  That should give you an X cursor and a stipple pattern.  If it does, you're not totally hosed yet.  If you have the same problem even there, then I guess the problem has to be X, the video driver, or the kernel.

smpolymen

Member

Registered: 2010-03-21

Posts: 12

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

No dice on running X manually, but I tried blacklisting the radeon driver to force it to fallback to fbdev and X starts up now, but this is far from optimal. At this point it looks like a driver issue. I'll attack it from that angle, maybe try compiling a newer driver from the AUR.

Xezlec

Member

Registered: 2014-11-30

Posts: 41

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

That sounds like a good idea.  Good luck!

smpolymen

Member

Registered: 2010-03-21

Posts: 12

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

Ok, so I tried unplugging my HDMI monitor and that seems to prevent the hang. When I plug the monitor back in and try to have it detect, it hangs again. I tried connecting via DVI (desktop)-HDMI (monitor) cable instead and have the same issue. I wonder if my monitor is causing the issue (it is pretty flaky, taking several tries to turn it on,) although I find it odd that a bad monitor would cause the driver to hang. Maybe the monitor is not sending the right data to the driver to set the mode. I'll try to find another monitor and see if that resolves the issue.

aussieoni

Member

Registered: 2014-12-06

Posts: 3

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

I have this exact same problem. I am also using the open source ati driver and have an HDMI TV connected.

This problem started from kernel upgrade linux-3.17.3-1 and can be (temporarily) fixed by downgrading to  linux-3.17.2-1.

I will have to try disconnecting my TV and see if this effects things for the better.

aussieoni

Member

Registered: 2014-12-06

Posts: 3

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

Unplugging my HDMI TV allows startx to get me to my desktop (KDE) but it takes a lot longer than usual and the desktop isn't fully/correctly loaded.

Once in I tried reconnecting the TV, KDE detects it and when it tries to auto-configure it the system just hangs again.

This was done with linux-3.17.4-1. Something changed after linux-3.17.2-1. Anyone know what that change might be?

squig

Member

Registered: 2014-12-13

Posts: 1

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

I am having the same problem with kernel 3.17.3 and 3.17.4, older versions work fine. Im also using the Ati open source video drivers (radeon r9280x). Since this thread is marked as solved i registered to ask if you had found a fix for this issue?

To get around this problem temporarily I booted with the nomodeset parameter which got me access to the console and rolled back to an earlier kernel (3.17.2-1).

edit: nm, works fine with 3.17.6-1 .

Last edited by squig (2014-12-15 04:33:59)

aussieoni

Member

Registered: 2014-12-06

Posts: 3

Re: [SOLVED] Cannot start X: Xorg.bin blocked for more than 120 seconds

Thanks squig. I upgraded to linux-3.17.6-1 and all is well again.