You are not logged in.

#1 2014-11-09 08:02:48

lvlrdka22
Member
Registered: 2013-08-08
Posts: 5

[SOLVED] Xorg Not Starting Correctly Under 3.17/3.18

I start X by running startx. This is on a Samsung XE700T1C-A02US.
Under 3.17/3.18, if I run startx (rootless), awesome WM starts up fine, but I get absolutely no input from anything I've tried (dock keyboard, dock mouse, stylus, touch, USB keyboard, USB mouse).

[   111.507] (EE) systemd-logind: failed to take device /dev/input/event14: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   111.507] (II) Using input driver 'wacom' for 'Wacom ISDv4 EC Pen'
[   111.507] (**) Wacom ISDv4 EC Pen: always reports core events
[   111.507] (**) Option "Device" "/dev/input/event14"
[   111.507] (EE) xf86OpenSerial: Cannot open device /dev/input/event14
        Permission denied.
[   111.507] (EE) Wacom ISDv4 EC Pen: Error opening /dev/input/event14 (Permission denied)
[   111.507] (EE) PreInit returned 8 for "Wacom ISDv4 EC Pen"
[   111.507] (II) UnloadModule: "wacom"
[   111.508] (II) config/udev: Adding input device Wacom ISDv4 EC Pen (/dev/input/mouse2)
[   111.508] (II) No input driver specified, ignoring this device.
[   111.508] (II) This device may have been added with another device file.
[   111.508] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/event13)
[   111.508] (**) Atmel Atmel maXTouch Digitizer: Applying InputClass "evdev touchscreen catchall"
[   112.009] (EE) systemd-logind: failed to take device /dev/input/event13: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   112.009] (II) Using input driver 'evdev' for 'Atmel Atmel maXTouch Digitizer'
[   112.009] (**) Atmel Atmel maXTouch Digitizer: always reports core events
[   112.009] (**) evdev: Atmel Atmel maXTouch Digitizer: Device: "/dev/input/event13"
[   112.009] (EE) evdev: Atmel Atmel maXTouch Digitizer: Unable to open evdev device "/dev/input/event13".
[   112.010] (EE) PreInit returned 2 for "Atmel Atmel maXTouch Digitizer"
[   112.010] (II) UnloadModule: "evdev"
[   112.011] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/mouse1)
[   112.011] (II) No input driver specified, ignoring this device.
[   112.011] (II) This device may have been added with another device file.
[   112.011] (II) config/udev: Adding input device WebCam SC-50AFL11C54N (/dev/input/event9)
[   112.012] (**) WebCam SC-50AFL11C54N: Applying InputClass "evdev keyboard catchall"
[   112.512] (EE) systemd-logind: failed to take device /dev/input/event9: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   112.513] (II) Using input driver 'evdev' for 'WebCam SC-50AFL11C54N'
[   112.513] (**) WebCam SC-50AFL11C54N: always reports core events
[   112.513] (**) evdev: WebCam SC-50AFL11C54N: Device: "/dev/input/event9"
[   112.513] (EE) evdev: WebCam SC-50AFL11C54N: Unable to open evdev device "/dev/input/event9".
[   112.513] (EE) PreInit returned 2 for "WebCam SC-50AFL11C54N"
[   112.513] (II) UnloadModule: "evdev"
[   112.514] (II) config/udev: Adding input device USB Keyboard+SmartPad (/dev/input/event11)
[   112.514] (**) USB Keyboard+SmartPad: Applying InputClass "evdev keyboard catchall"
[   113.015] (EE) systemd-logind: failed to take device /dev/input/event11: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   113.015] (II) Using input driver 'evdev' for 'USB Keyboard+SmartPad'
[   113.015] (**) USB Keyboard+SmartPad: always reports core events
[   113.015] (**) evdev: USB Keyboard+SmartPad: Device: "/dev/input/event11"
[   113.015] (EE) evdev: USB Keyboard+SmartPad: Unable to open evdev device "/dev/input/event11".
[   113.015] (EE) PreInit returned 2 for "USB Keyboard+SmartPad"
[   113.015] (II) UnloadModule: "evdev"
[   113.016] (II) config/udev: Adding input device USB Keyboard+SmartPad (/dev/input/event12)
[   113.016] (**) USB Keyboard+SmartPad: Applying InputClass "evdev pointer catchall"
[   113.016] (**) USB Keyboard+SmartPad: Applying InputClass "evdev keyboard catchall"
[   113.517] (EE) systemd-logind: failed to take device /dev/input/event12: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   113.517] (II) Using input driver 'evdev' for 'USB Keyboard+SmartPad'
[   113.517] (**) USB Keyboard+SmartPad: always reports core events
[   113.517] (**) evdev: USB Keyboard+SmartPad: Device: "/dev/input/event12"
[   113.517] (EE) evdev: USB Keyboard+SmartPad: Unable to open evdev device "/dev/input/event12".
[   113.517] (EE) PreInit returned 2 for "USB Keyboard+SmartPad"
[   113.517] (II) UnloadModule: "evdev"
[   113.518] (II) config/udev: Adding input device USB Keyboard+SmartPad (/dev/input/mouse0)
[   113.519] (II) No input driver specified, ignoring this device.
[   113.519] (II) This device may have been added with another device file.
[   113.519] (II) config/udev: Adding input device WebCam SC-20HDM12347N (/dev/input/event10)
[   113.520] (**) WebCam SC-20HDM12347N: Applying InputClass "evdev keyboard catchall"
[   114.020] (EE) systemd-logind: failed to take device /dev/input/event10: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   114.021] (II) Using input driver 'evdev' for 'WebCam SC-20HDM12347N'
[   114.021] (**) WebCam SC-20HDM12347N: always reports core events
[   114.021] (**) evdev: WebCam SC-20HDM12347N: Device: "/dev/input/event10"
[   114.021] (EE) evdev: WebCam SC-20HDM12347N: Unable to open evdev device "/dev/input/event10".
[   114.021] (EE) PreInit returned 2 for "WebCam SC-20HDM12347N"
[   114.021] (II) UnloadModule: "evdev"
[   114.022] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event5)
[   114.022] (II) No input driver specified, ignoring this device.
[   114.022] (II) This device may have been added with another device file.
[   114.022] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event6)
[   114.022] (II) No input driver specified, ignoring this device.
[   114.022] (II) This device may have been added with another device file.
[   114.023] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event7)
[   114.023] (II) No input driver specified, ignoring this device.
[   114.023] (II) This device may have been added with another device file.
[   114.024] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
[   114.024] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[   114.525] (EE) systemd-logind: failed to take device /dev/input/event4: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   114.525] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[   114.525] (**) AT Translated Set 2 keyboard: always reports core events
[   114.525] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event4"
[   114.525] (EE) evdev: AT Translated Set 2 keyboard: Unable to open evdev device "/dev/input/event4".
[   114.525] (EE) PreInit returned 2 for "AT Translated Set 2 keyboard"
[   114.525] (II) UnloadModule: "evdev"

Basically, for each input device, I get "systemd-logind: failed to take device /dev/input/eventXX: Did not receive a reply."
I don't see anything relevant in the journal
This happens with both systemd 216 and 217.

If I use "needs_root_rights=yes" in /etc/X11/Xwrapper.config, I don't even get the GUI. It just hangs at the short bit of text that lists X/OS/kernel information, with this call trace in the journal:

Nov 08 23:30:02 test-tablet systemd[1]: systemd-logind.service watchdog timeout (limit 1min)!
Nov 08 23:31:32 test-tablet kernel: INFO: task systemd-logind:377 blocked for more than 120 seconds.
Nov 08 23:31:32 test-tablet kernel:       Tainted: G     U         3.18.0-1-mainline #1
Nov 08 23:31:32 test-tablet kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 23:31:32 test-tablet kernel: systemd-logind  D 0000000000000001     0   377      1 0x00000004
Nov 08 23:31:32 test-tablet kernel:  ffff8800cedcf7f8 0000000000000082 ffff8800d1365a90 0000000000014640
Nov 08 23:31:32 test-tablet kernel:  ffff8800cedcffd8 0000000000014640 ffff8801192deeb0 ffff8800d1365a90
Nov 08 23:31:32 test-tablet kernel:  ffff8800cedcf7b8 0000000000000204 0000000000000001 0000000000000292
Nov 08 23:31:32 test-tablet kernel: Call Trace:
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff81548619>] ? schedule+0x29/0x70
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff81548a96>] ? schedule_preempt_disabled+0x16/0x20
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff81548619>] schedule+0x29/0x70
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff81548a96>] schedule_preempt_disabled+0x16/0x20
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff8154a1d5>] __mutex_lock_slowpath+0xd5/0x140
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff8154a25b>] mutex_lock+0x1b/0x30
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa08d749b>] wacom_resume+0x2b/0x60 [wacom]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa02d5c8d>] hid_resume_common+0xad/0x100 [usbhid]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa018c571>] ? usb_port_resume+0x171/0x7b0 [usbcore]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa0199150>] ? usb_runtime_suspend+0x80/0x80 [usbcore]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa02d5d21>] hid_resume+0x41/0x80 [usbhid]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa0197d36>] usb_resume_interface.isra.6+0xb6/0x120 [usbcore]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa0198004>] usb_resume_both+0x74/0x140 [usbcore]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa019916a>] usb_runtime_resume+0x1a/0x20 [usbcore]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff813bc226>] __rpm_callback+0x36/0x90
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff813bc2a6>] rpm_callback+0x26/0xa0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff813bd6b1>] rpm_resume+0x4b1/0x690
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff813bd55a>] rpm_resume+0x35a/0x690
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff8115fa0b>] ? lru_cache_add_active_or_unevictable+0x2b/0xb0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff813bd8d0>] __pm_runtime_resume+0x40/0x60
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa0197af6>] usb_autopm_get_interface+0x26/0x70 [usbcore]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa02d5b09>] usbhid_open+0x69/0xe0 [usbhid]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa08d5875>] wacom_open+0x35/0x50 [wacom]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff813e2ce9>] input_open_device+0x79/0xa0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffffa0407211>] evdev_open+0x1b1/0x200 [evdev]
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811ccb3e>] chrdev_open+0xae/0x1f0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811cca90>] ? cdev_put+0x30/0x30
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811c5732>] do_dentry_open+0x1d2/0x320
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811c5ba9>] vfs_open+0x49/0x50
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811d6847>] do_last.isra.35+0x347/0xea0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff8115ef6e>] ? release_pages+0x20e/0x2b0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811d7462>] path_openat+0xc2/0x6e0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff8117bde4>] ? tlb_flush_mmu_free+0x34/0x60
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811d8b09>] do_filp_open+0x49/0xd0
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811e6137>] ? __alloc_fd+0xa7/0x130
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811c6f5e>] do_sys_open+0x14e/0x250
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff811c707e>] SyS_open+0x1e/0x20
Nov 08 23:31:32 test-tablet kernel:  [<ffffffff8154c769>] system_call_fastpath+0x12/0x17
Nov 08 23:31:32 test-tablet systemd[1]: systemd-logind.service stop-sigterm timed out. Killing.

This happens to both systemd 216 and 217 as well.

Everything appears fine under 3.16.4, regardless of whether I run systemd 216 or 217, rootless or not.

Any ideas on how I can get X working properly under the newer kernels?

Last edited by lvlrdka22 (2014-12-04 18:10:57)

Offline

#2 2014-11-11 05:32:34

lvlrdka22
Member
Registered: 2013-08-08
Posts: 5

Re: [SOLVED] Xorg Not Starting Correctly Under 3.17/3.18

If it's a bug, any idea who I should file the with, kernel, xorg, or something else?

Offline

#3 2014-12-04 18:10:33

lvlrdka22
Member
Registered: 2013-08-08
Posts: 5

Re: [SOLVED] Xorg Not Starting Correctly Under 3.17/3.18

It's finally been fixed with this patch.

Offline

Board footer

Powered by FluxBB