Bug#616089: Switching from text modus back to Xorg impossible
On Wed, Mar 02, 2011 at 01:53:28PM +0100, Michel Dänzer wrote: > The X server is running on VT 9, so you're not expected to see it on VT > 7. :) Oh --- sorry. I did not expect it to change the "VT" (does that mean virtual terminal?) from 7 to another in a restart. So this bug is invalid. But shouldnt't the X server always run on VT 7? Olaf -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110302133508.GA3899@olaf
Bug#616089: Switching from text modus back to Xorg impossible
Package: xserver-xorg-core Version: 1.7.7-11 System info: squeeze amd64, linux-image-2.6.32-5-amd64, gdm3 Description: After switching to text modus login screen with Ctrl-Alt-F1 and switching back with Alt-F7, the screen is black (text modus, with a blinking curser in upper left corner). This does only happen after a user was already logged in with gdm3 and has logged out again; but then it seems to happen always, even after "/etc/init.d/gdm3 restart". While it happens, a backtrace of Xorg with gdb (probably not much use, not compiled with debugging symbols?): (gdb) bt #0 0x7f8cf9c838b3 in select () from /lib/libc.so.6 #1 0x0046577a in WaitForSomething () #2 0x004330f2 in ?? () #3 0x00425c35 in _start () (gdb) and also while it happens: olaf:~# ps ax | grep gdm 1504 ?Sl 0:00 /usr/sbin/gdm3 4999 ?Sl 0:00 /usr/lib/gdm3/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1 5000 tty9 Ss+0:00 /usr/bin/Xorg :0 -br -verbose -audit 0 -novtswitch -auth /var/run/gdm3/auth-for-Debian-gdm-ch5K3k/database -nolisten tcp vt9 5025 ?Ssl0:00 /usr/bin/gnome-session --autostart=/usr/share/gdm/autostart/LoginWindow/ 5032 ?Ss 0:02 /usr/lib/gnome-settings-daemon/gnome-settings-daemon --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins 5042 ?S 0:00 /usr/lib/gdm3/gdm-simple-greeter 5044 ?S 0:00 /usr/lib/gdm3/gdm-session-worker 5094 tty1 S+ 0:00 grep gdm olaf:~# Xorg.0.log during this state is: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian Current Operating System: Linux olaf.iswbio.uni-jena.de 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=f0ea1315-ab33-4c54-96e9-681d88acefcf ro Build Date: 12 January 2011 02:59:50AM xorg-server 2:1.7.7-11 (Cyril Brulebois ) Current version of pixman: 0.16.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: Wed Mar 2 12:23:10 2011 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c8a00 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 9 (--) PCI:*(0:1:5:0) 1002:9614:1043:834d ATI Technologies Inc Radeon HD 3300 Graphics rev 0, Mem @ 0xd000/268435456, 0xfbde/65536, 0xfbc0/1048576, I/O @ 0xc000/256 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor="X.Org Foundation"
Bug#419986: server lockups related to dri
On Mon, Jun 04, 2007 at 11:15:08PM +0200, Brice Goglin wrote: > Brice Goglin wrote: > > If you think you might be able to upgrade to libc 2.5 in the near > > future, for instance when it enters testing, don't bother recompiling, > > just wait a couple weeks. Recompiling might be a pain since you might > > need lots of dependencies first... > > > > Ok thanks, this looks like a plain Debian Etch. Since at least > > xserver-xorg-core, the ATI driver, mesa and libdrm got a major upgrade > > (all of them in unstable, except the ATI driver which is in > > experimental), I would rather wait until you get a chance to upgrade... > > > > Hi Olaf, > > libc6 2.5 entered testing a couple days ago. Did you have a chance to > upgrade it and then upgrade xserver-xorg-core and drivers/mesa/... and > see whether this bug still happens? > > Thanks, > Brice Hi Brice, the problem persists after upgrading to - libc6_2.5-9+b1_i386.deb (and new tzdata) (testing) - libdrm2_2.3.0-4_i386.deb (testing) - libgl1-mesa-dri_6.5.2-5_i386.deb (and new ligl1-mesa-gly) (unstable) - xserver-xorg-core_1.3.0.0.dfsg-6_i386.deb (unstable) (ignoring an unmet dependency of xserver-xorg-core on a newer libgcc1). I am sorry, I know that you spend a lot of your spare time for these problems, but I will not be able to help you much further in the next time, I could not manage not to delay other things too much ... Olaf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419986: output of 'ps ax'
On Tue, Apr 24, 2007 at 12:22:11PM +0200, Michel Dänzer wrote: > On Tue, 2007-04-24 at 12:21 +0200, Olaf Till wrote: > > On Mon, Apr 23, 2007 at 09:53:35PM +0200, Brice Goglin wrote: > > > Olaf Till wrote: > > > > > > With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies > > > > except libc6) X behaved correctly without drm, but did not even come > > > > up with drm, there was no process X afterwards. Installing > > > > xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. > > > > > > > > > > This is strange too. Installing the -dbg package should not change > > > anything regarding "does it start successfully or not?". It only > > > provides some debugging symbols for gdb. > > > > Sorry, a typo, and further misread to 'dbg', probably. I meant without > > or with the line 'dri' in the module-section of xorg.conf (not > > 'drm'). BTW there was an unsatisfied dependency of the experimental > > X-server of a newer libdrm2 (don't know it, but sounds as if it had > > something to do with direct rendering) than installed. > > > > > > I again attach the xorg.conf used for all this and the log of the > > > > experimental X-server with dri. > > > > > > > > > > The log is pretty small and doesn't show any problem. Is this the right > > > one? > > > > I think the log stops after loading the module dri. Seemingly X was > > not able to log anything else after this. Compare to the attached > > respective log (also experimental server) after commenting out "dri" > > in the module-section of xorg.conf. As I said, there was no process X > > present after trying to start this experimental server with "dri". > > It probably dies trying to call an unresolved function due to the > unsatisfied libdrm2 dependency. See the X server's stderr output. > Yes: olaf:~/debs# startx ... Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X Window System Version 1.2.99.905 (1.3.0 RC 5) Release Date: 05 April 2007 X Protocol Version 11, Revision 0, Release 1.2.99.905 Build Operating System: Linux Debian Current Operating System: Linux olaf 2.6.18-4-amd64 #1 SMP Mon Mar 26 19:17:44 UTC 2007 x86_64 Build Date: 09 April 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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: Tue Apr 24 14:58:10 2007 (==) Using config file: "/etc/X11/xorg.conf" /usr/bin/X11/X: symbol lookup error: /usr/lib/xorg/modules/extensions//libdri.so: undefined symbol: drmSetServerInfo XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. olaf:~/debs# Installing new libdrm2 from same archive as experimental xserver-xorg-core solved that problem. There were no unsatisfied dependencies any more. The experimental xserver shows the same lockup as the one in etch. Attaching with dbg to X of etch while locked up (only a manual transcript was possible from that machine): olaf:~# ps ax ... 3175 tty7 R
Bug#419986: output of 'ps ax'
On Mon, Apr 23, 2007 at 09:53:35PM +0200, Brice Goglin wrote: > Olaf Till wrote: > > Unfortunately, though I could ssh to the machine from at home in a > > first test, I got no connection and no ping-answers when I tried > > later. Anyway my gdb was unable to attach to a running X even when I > > tried locally at home, though it could attach to other programs (also > > with no debugging symbols). So this probably will not work. > > > > This is strange. As long as you don't try to attach gdb from a terminal > running inside X, of course not > attaching should work fine (with gdb -p $(pidof X)). > If you see the X process in ps, there's no reason you couldn't attach. At home, I got no prompt and something like 'ptrace - operation not allowed' after killing gdb. But it _does_ work now on this machine here. I will try again after work, causing X to lock again and connecting from the machine at home. (BTW hitting ctrl-C a couple of times produces new gdb-prompts, but does not change the output of 'bt'.) > > With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies > > except libc6) X behaved correctly without drm, but did not even come > > up with drm, there was no process X afterwards. Installing > > xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. > > > > This is strange too. Installing the -dbg package should not change > anything regarding "does it start successfully or not?". It only > provides some debugging symbols for gdb. Sorry, a typo, and further misread to 'dbg', probably. I meant without or with the line 'dri' in the module-section of xorg.conf (not 'drm'). BTW there was an unsatisfied dependency of the experimental X-server of a newer libdrm2 (don't know it, but sounds as if it had something to do with direct rendering) than installed. > > I again attach the xorg.conf used for all this and the log of the > > experimental X-server with dri. > > > > The log is pretty small and doesn't show any problem. Is this the right one? I think the log stops after loading the module dri. Seemingly X was not able to log anything else after this. Compare to the attached respective log (also experimental server) after commenting out "dri" in the module-section of xorg.conf. As I said, there was no process X present after trying to start this experimental server with "dri". Olaf This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X Window System Version 1.2.99.905 (1.3.0 RC 5) Release Date: 05 April 2007 X Protocol Version 11, Revision 0, Release 1.2.99.905 Build Operating System: Linux Debian Current Operating System: Linux olaf 2.6.18-4-amd64 #1 SMP Mon Mar 26 19:17:44 UTC 2007 x86_64 Build Date: 09 April 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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: Tue Apr 24 12:12:53 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "LS902U" (**) | |-->Device "ATI Technologies Inc RV350 AS [Radeon 9550]" (**) |-->Input Device "Generic Keyboard" (**) |-->Input Device "Configured Mouse" (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/Type1". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/Type1"). (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/X11R6/lib/X11/fonts/misc, /usr/X11R6/lib/X11/fonts/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/X11R6/lib/X11/fonts/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/X11R6/lib/X11/fonts/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/X11R6/lib/X11/fonts/100dpi, /usr/share/fonts/X11/75dpi, /usr/X11R6/lib/X11/fonts/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueT
Bug#419986: output of 'ps ax'
On Fri, Apr 20, 2007 at 06:41:53AM +, olaf wrote: > On Thu, Apr 19, 2007 at 08:34:46PM +0200, Brice Goglin wrote: > > Olaf Till wrote: > > > Sorry, I should have thought of that before. > > > > > > Checked output of 'ps ax' with a background job (ps ax | grep > > > '/usr/bin/X ' > lt.out, repeated each second) during the lockup > > > (timestamp of file 'lt.out' has been checked): > > > > > > 4088 tty7 R > > /var/lib/xdm/authdir/authfiles/A:0-sJSBJL > > > > > > So the server is not sleeping. While not locked up, this line is, e.g.: > > > > > > 2980 tty7 S > > /var/lib/xdm/authdir/authfiles/A:0-CWZXVL > > > > > > > Attaching a gdb with > > gdb -p $(pidof X) > > and looking at the backtrace after hitting ctrl-c a couple times might > > help more. But, you will have to do that through ssh from another host. > > > > Brice > > > > I will do that today after work, because it is difficult to find ssh > installations on the computers here around ... > > Olaf Have deleted the lines in xorg.conf you asked to delete, no effect, except maybe the lockup came earlier. Unfortunately, though I could ssh to the machine from at home in a first test, I got no connection and no ping-answers when I tried later. Anyway my gdb was unable to attach to a running X even when I tried locally at home, though it could attach to other programs (also with no debugging symbols). So this probably will not work. With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies except libc6) X behaved correctly without drm, but did not even come up with drm, there was no process X afterwards. Installing xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. I again attach the xorg.conf used for all this and the log of the experimental X-server with dri. I fear this all will not be much helpful ... Olaf # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/X11R6/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/X11R6/lib/X11/fonts/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/X11R6/lib/X11/fonts/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/X11R6/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/75dpi" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" # Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" # Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "XkbVariant""nodeadkeys" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device"
Bug#419986: output of 'ps ax'
Sorry, I should have thought of that before. Checked output of 'ps ax' with a background job (ps ax | grep '/usr/bin/X ' > lt.out, repeated each second) during the lockup (timestamp of file 'lt.out' has been checked): 4088 tty7 R
