Can't exit X11 on 4.5.1 & 4.5.0 (4.4.1 OK)

All other questions
Ptolemarch
Posts: 1
Joined: 09 Feb 2015, 16:15

Can't exit X11 on 4.5.1 & 4.5.0 (4.4.1 OK)

Postby Ptolemarch » 09 Feb 2015, 17:36

On SystemRescueCd 4.5.1 (and 4.5.0), I can't exit X11. I am able to exit X11 normally on 4.4.1.

Before starting X11, I connected to wifi using nmcli, set a root password, and SSHed in.

Here's the output of startx:

Code: Select all

[email protected] /root % startx
xauth:  file /root/.serverauth.4156 does not exist
xauth:  file /root/.Xauthority does not exist
xauth:  file /root/.Xauthority does not exist


X.Org X Server 1.15.2
Release Date: 2014-06-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.10.60-fd01 i686 Gentoo
Current Operating System: Linux sysresccd 3.14.31-std451-amd64 #2 SMP Wed Feb 4 07:55:05 UTC 2015 x86_64
Kernel command line: BOOT_IMAGE=/syslinux/rescue64 docache
Build Date: 06 February 2015  04:14:49AM

Current version of pixman: 0.32.4
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb  9 17:06:47 2015
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
xinit: connection to X server lost

waiting for X server to shut down ..........
xinit: X server slow to shut down, sending KILL signal

waiting for server to die ...
xinit: X server refuses to die
[email protected] /root %

After this, the X process takes up 100% of cpu for a while, and shortly the system becomes completely unresponsive.

I was able to save the above output by starting X over SSH, but the behavior appears identical when I do everything locally, from a console. I can't confirm this, because once X freezes, I can't use CTRL-ALT-F1 (etc) to switch back to a virtual console.

There is something that showed up in /var/log/messages immediately (to the second) as I started X. Perhaps it's related:

Code: Select all

Feb  9 17:06:47 sysresccd kernel: [  506.342414] nouveau E[    PBUS][0000:01:00.0] MMIO write of 0x00000000 FAULT at 0x418880 [ IBUS ]
Feb  9 17:06:47 sysresccd kernel: [  506.342569] nouveau E[   PIBUS][0000:01:00.0] GPC1: 0x419eb4 0xbadf1000 (0x3800820c)
Feb  9 17:06:47 sysresccd kernel: [  506.342594] nouveau E[   PIBUS][0000:01:00.0] GPC2: 0x419eb4 0xbadf1000 (0x3800820c)
Feb  9 17:06:47 sysresccd kernel: [  506.342996] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0x404170 0x00000012 (0x0e008201)
Feb  9 17:06:49 sysresccd kernel: [  508.344628] nouveau E[  PGRAPH][0000:01:00.0] HUB_INIT timed out
Feb  9 17:06:49 sysresccd kernel: [  508.344632] nouveau E[  PGRAPH][0000:01:00.0] 409000 - done 0x00000204
Feb  9 17:06:49 sysresccd kernel: [  508.344636] nouveau E[  PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Feb  9 17:06:49 sysresccd kernel: [  508.344640] nouveau E[  PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000002 0x00000009
Feb  9 17:06:49 sysresccd kernel: [  508.344642] nouveau E[  PGRAPH][0000:01:00.0] 502000 - done 0x00000300
Feb  9 17:06:49 sysresccd kernel: [  508.344648] nouveau E[  PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Feb  9 17:06:49 sysresccd kernel: [  508.344654] nouveau E[  PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Feb  9 17:06:49 sysresccd kernel: [  508.344656] nouveau E[  PGRAPH][0000:01:00.0] 50a000 - done 0x00000300
Feb  9 17:06:49 sysresccd kernel: [  508.344662] nouveau E[  PGRAPH][0000:01:00.0] 50a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Feb  9 17:06:49 sysresccd kernel: [  508.344668] nouveau E[  PGRAPH][0000:01:00.0] 50a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Feb  9 17:06:49 sysresccd kernel: [  508.344670] nouveau E[  PGRAPH][0000:01:00.0] 512000 - done 0x00000300
Feb  9 17:06:49 sysresccd kernel: [  508.344676] nouveau E[  PGRAPH][0000:01:00.0] 512000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Feb  9 17:06:49 sysresccd kernel: [  508.344682] nouveau E[  PGRAPH][0000:01:00.0] 512000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Feb  9 17:06:49 sysresccd kernel: [  508.344683] nouveau E[  PGRAPH][0000:01:00.0] init failed, -16
Feb  9 17:06:50 sysresccd vmusr[4236]: [ warning] [GLib-GObject] invalid (NULL) pointer instance
Feb  9 17:06:50 sysresccd vmusr[4236]: [critical] [GLib-GObject] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Feb  9 17:06:50 sysresccd vmusr[4237]: [ warning] [GLib-GObject] invalid (NULL) pointer instance
Feb  9 17:06:50 sysresccd vmusr[4237]: [critical] [GLib-GObject] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Feb  9 17:06:50 sysresccd vmusr[4236]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-app-ctx after class was initialised
Feb  9 17:06:50 sysresccd vmusr[4237]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-app-ctx after class was initialised
Feb  9 17:06:50 sysresccd vmusr[4236]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-prop-thread-pool after class was initialised
Feb  9 17:06:50 sysresccd vmusr[4237]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-prop-thread-pool after class was initialised
Feb  9 17:06:51 sysresccd vmusr[4236]: [ warning] [desktopEvents] Another instance of vmware-user already running. Exiting.
Feb  9 17:06:52 sysresccd dbus[1635]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Feb  9 17:06:52 sysresccd dbus[1635]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb  9 17:06:54 sysresccd kernel: [  513.367042] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Feb  9 17:06:54 sysresccd kernel: [  513.367218] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
Feb  9 17:06:54 sysresccd kernel: [  513.367226] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)

I have no idea how or why vmware seems to come into this log. Neither the strings "vmware" nor "vmuser" appear in the log before this snippet. (I'm not quite sure whether messages halted at this point, or whether the script I wrote to copy messages.log failed after this point.)

Return to “Other”

Who is online

Users browsing this forum: Bing [Bot] and 6 guests