Bug#764792: x11-apps: xman not rendering any pages (zsoelim: not found)
Package: x11-apps Version: 7.7+3 Severity: important Dear Maintainer, I was trying out xman on my jessie system, and it turns out it won't render any pages at all. I notice that when I start xman from a terminal, I see sh: 1: zsoelim: not found in the terminal when I tell it to load a man page. Some checking shows that zsoelim was in man-db in wheezy, but that no longer seems to be the case with man-db in jessie on AMD64. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x11-apps depends on: ii cpp 4:4.9.1-1 ii libc62.19-11 ii libpng12-0 1.2.50-2 ii libsm6 2:1.2.2-1 ii libx11-6 2:1.6.2-3 ii libxaw7 2:1.0.12-2 ii libxcursor1 1:1.1.14-1 ii libxext6 2:1.3.2-1 ii libxft2 2.3.2-1 ii libxkbfile1 1:1.0.8-1 ii libxmu6 2:1.1.2-1 ii libxmuu1 2:1.1.2-1 ii libxrender1 1:0.9.8-1 ii libxt6 1:1.1.4-1 Versions of packages x11-apps recommends: ii xbitmaps 1.1.1-2 Versions of packages x11-apps suggests: ii mesa-utils 8.2.0-1 -- no debconf information
Bug#761877: xserver-xorg: Updated Xorg from Testing fails to start correctly
Yes, that seems to have fixed it here. X now starts and runs on the Compaq with RenderAccel on. -lee On Tue, Oct 7, 2014 at 5:45 AM, Julien Cristau jcris...@debian.org wrote: On Tue, Sep 16, 2014 at 08:08:19 -0500, Pat Parson wrote: Package: xserver-xorg Version: 1:7.7+7 Severity: important Dear Maintainer, After updating the Xorg packages from Stable to Testing xorg will no longer start and bring up the desktop. If I run the script to set the resolution as part of launching the display manager the gtk-greeter loads momentarily and then crashes immediately repeatedly as apparently Xorg then restarts. Logs seem to indicate that the display manager cannot find a display to use. I am unable to determine if this is a problem with the ATI drivers. Still using display manager from stable so there should be no problem there. Please test xserver-xorg-video-mach64 6.9.4-2, I'm hoping this is the same as bug#726585. Thanks, Julien
Bug#761877: xserver-xorg: Updated Xorg from Testing fails to start correctly
I did some more fiddling, and the culprit seems to be render acceleration. Setting Option RenderAccel False in xorg.conf makes X work again on the Compaq. -lee
Bug#484049: More info on the crashes
- Scorched3d crashing on start is due to a null pointer dereference in its shader handling code (specifically, while loading the vertex shader for animated water). I'm not sure if this is a Scorched3d bug, a Mesa bug, or a bug with the Intel driver; I have machines at home with nVidia and ATI video cards, and can check later today. In any case, turning off shaders makes this crash go away. - The display corruption and X crashes are being tickled specifically by scorch3d's cube mapping code (GL_ARB_texture_cube_map). Ticking disable cube maps makes things work no matter what other extensions are enabled. Again, I'm not sure if this is a scorched3d bug, a Mesa bug, or an Intel bug. More as I find it... -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484049: xserver-xorg-video-intel: [G965] Ring buffer overflow after starting scorched3d in Normal or Faster mode
Brice Goglin wrote: Lee Cremeans wrote: Package: xserver-xorg-video-intel Version: 2:2.3.1-1 Severity: important I'm running Debian lenny amd64 on a Gateway ML6720 laptop with 1024 MB RAM. The Intel video in this laptop works well in 2D mode with either acceleration engine, but when I use 3D, things get trickier. If I start scorched3d with default settings, the X server will eventually crash and leave the screen in a corrupted state. Depending on what state the crash leaves the hardware in, it may also leave me with a black screen. The console is black and unusable, but SSH still works. Turning scorched3d down to either Safe or Fastest modes seems to avoid the crash. Does it occur with intel 2.3.2 and libgl1-mesa-dri 7.0.3-4 from unstable? Brice I installed the new packages and tested again. Here's what I found: Normal mode: scorched3d crashes, X is not affected. Faster mode: same as before: Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x ipeir: 0x iphdr: 0x0203 LP ring tail: 0xaf60 head: aa64 len: 0x0001f001 start 0x Err ID (eir): 0x Err Status (esr): 0x0001 Err Mask (emr): 0xffdf instdone: 0xffc5f83d instdone_1: 0x000f instpm: 0x memmode: 0x instps: 0x8001e035 HW Status mask (hwstam): 0xfff8dffe IRQ enable (ier): 0x0002 imr: 0xfff8 iir: 0x0030 acthd: 0x0040aa64 dma_fadd_p: 0xaa90 ecoskpd: 0x0307 excc: 0x cache_mode: 0x6800/0x0180 mi_arb_state: 0x0044 IA_VERTICES_COUNT_QW 0x/0x IA_PRIMITIVES_COUNT_QW 0x/0x VS_INVOCATION_COUNT_QW 0x/0x GS_INVOCATION_COUNT_QW 0x/0x GS_PRIMITIVES_COUNT_QW 0x/0x CL_INVOCATION_COUNT_QW 0x/0x CL_PRIMITIVES_COUNT_QW 0x/0x PS_INVOCATION_COUNT_QW 0x/0x PS_DEPTH_COUNT_QW 0x/0x WIZ_CTL 0x TS_CTL 0x TS_DEBUG_DATA 0x5dfe6bfa TD_CTL 0x / 0x space: 129788 wanted 131064 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0x2efff000 at 0x2afa13bfd000 (II) intel(0): [drm] Closed DRM master. Fatal server error: lockup Fastest and Safe modes work as before. HOWEVER: No matter what mode I have loaded, if I tick Disable GL extensions, the game runs perfectly (if a bit slow; this is an X3100 after all). This seems to be an important clue. If I untick it with the Safe or Fastest settings loaded, scorched3d itself will crash before it can change to 3D mode, as with the unadorned Normal mode. -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481345: My bug (484049) may be a duplicate of this
Sam, can you reproduce the bug, then SSH into the target machine and look for a block of text that mentions Error in I830WaitLpRing(), timeout for 2 seconds? I think this bug and my bug with scorched3d are related, but I'm not quite ready to mark mine as a duplicate yet. For what it's worth, the G965 seems to be upset because of an invalid command, most likely because either the intel driver or Mesa overwhelmed it and overran the ring buffer, sending the G965's command sequencer spinning off into space. I'll do more investigating tonight to see who the guilty party is. -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484049: xserver-xorg-video-intel: [G965] Ring buffer overflow after starting scorched3d in Normal or Faster mode
Package: xserver-xorg-video-intel Version: 2:2.3.1-1 Severity: important I'm running Debian lenny amd64 on a Gateway ML6720 laptop with 1024 MB RAM. The Intel video in this laptop works well in 2D mode with either acceleration engine, but when I use 3D, things get trickier. If I start scorched3d with default settings, the X server will eventually crash and leave the screen in a corrupted state. Depending on what state the crash leaves the hardware in, it may also leave me with a black screen. The console is black and unusable, but SSH still works. Turning scorched3d down to either Safe or Fastest modes seems to avoid the crash. The messages I get when the driver crashes seem to indicate that the driver is running out of ring buffer space, and has thus confused the G965 in some way: Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x ipeir: 0x iphdr: 0x0203 LP ring tail: 0x9760 head: 9234 len: 0x0001f001 start 0x Err ID (eir): 0x Err Status (esr): 0x0001 Err Mask (emr): 0xffdf instdone: 0xffc5d83d instdone_1: 0x000f instpm: 0x memmode: 0x instps: 0x8001e035 HW Status mask (hwstam): 0xfff8dffe IRQ enable (ier): 0x0002 imr: 0xfff8 iir: 0x0030 acthd: 0x1cc09234 dma_fadd_p: 0x9248 ecoskpd: 0x0307 excc: 0x cache_mode: 0x6800/0x0180 mi_arb_state: 0x0044 IA_VERTICES_COUNT_QW 0x/0x IA_PRIMITIVES_COUNT_QW 0x/0x VS_INVOCATION_COUNT_QW 0x/0x GS_INVOCATION_COUNT_QW 0x/0x GS_PRIMITIVES_COUNT_QW 0x/0x CL_INVOCATION_COUNT_QW 0x/0x CL_PRIMITIVES_COUNT_QW 0x/0x PS_INVOCATION_COUNT_QW 0x/0x PS_DEPTH_COUNT_QW 0x/0x WIZ_CTL 0x TS_CTL 0x TS_DEBUG_DATA 0x5dfe6bfa TD_CTL 0x / 0x space: 129740 wanted 131064 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0x2efff000 at 0x2acfa4e69000 (II) intel(0): [drm] Closed DRM master. Fatal server error: lockup (II) AIGLX: Suspending AIGLX clients for VT switch Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x ipeir: 0x iphdr: 0x0203 LP ring tail: 0x9768 head: 9234 len: 0x0001f001 start 0x Err ID (eir): 0x Err Status (esr): 0x0001 Err Mask (emr): 0xffdf instdone: 0xffc5d83d instdone_1: 0x000f instpm: 0x memmode: 0x instps: 0x8001e035 HW Status mask (hwstam): 0xfff8dffe IRQ enable (ier): 0x0002 imr: 0xfff8 iir: 0x0030 acthd: 0x1cc09234 dma_fadd_p: 0x9248 ecoskpd: 0x0307 excc: 0x cache_mode: 0x6800/0x0180 mi_arb_state: 0x0044 IA_VERTICES_COUNT_QW 0x/0x IA_PRIMITIVES_COUNT_QW 0x/0x VS_INVOCATION_COUNT_QW 0x/0x GS_INVOCATION_COUNT_QW 0x/0x GS_PRIMITIVES_COUNT_QW 0x/0x CL_INVOCATION_COUNT_QW 0x/0x CL_PRIMITIVES_COUNT_QW 0x/0x PS_INVOCATION_COUNT_QW 0x/0x PS_DEPTH_COUNT_QW 0x/0x WIZ_CTL 0x TS_CTL 0x TS_DEBUG_DATA 0x5dfe6bfa TD_CTL 0x / 0x space: 129732 wanted 131064 FatalError re-entered, aborting lockup When gdm tries to restart X after this, the driver fails to load, stating that the ring buffer has not been flushed (this is in the Xorg.log.0 given below). I notice in the FatalError logs that it wants 131064 bytes of ring buffer space, which is only 8 bytes less than the total space (131072 bytes). I cannot get my screen back unless I reboot. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-05-08 03:59 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1831872 2008-05-18 08:57 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1375 2008-06-01 23:23 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org 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 xorg.conf manual page. # (Type man 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: #
Bug#353494: xserver-xorg: fails to start on Cyrix 6x86L CPU (SIGILL)
Brice Goglin wrote: Hi, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding the X server not starting on a Cyrix 6x86 processor. Did any of you guys reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? Thanks, Brice I haven't checked recently because I decided to upgrade the machine in question from a Cyrix 486DX2 (which, I've since found out, doesn't support CPUID at all and should be excluded from any CPUID-based checks...) to a Pentium OverDrive, which works with no problems (aside from being slow, of course). -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353494: (no subject)
I did some more checking, and I can reproduce the bug running kernel-image-2.4.27-586tsc on the same machine. I also cross-checked with another OS (FreeBSD 6.1-RELEASE) to see if this is an upstream problem, and X.org crashed in the same place (while drawing the default stipple) with a SIGSEGV; this may be due to differences in how FreeBSD handle illegal instructions in user mode. In any case, it would seem CPUID is unusable from user mode on the Cyrix chips, and the Cx486/586/6x86 don't have MMX, so the fix would be to make fbHaveMMX check for a Cyrix processor before trying to use CPUID. I'll look at the X.org code again and see what I can do. -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353494: Cyrix CPUID disabled on newer 2.6 kernels?
I think I may have found the part that's causing trouble here. In fb/fbpict.c, there's a function fbHaveMMX that uses inline assembler, and appears to check for a 486 before trying to use CPUID. The Cyrix chips support CPUID, but it's turned off by default (!!), so trying to use it here makes the processor throw a SIGILL. (The kernel should be enabling this, but in 2.6.16 it's not fsr...) I'm going to check my kernel config to make sure the Cyrix hacks haven't been removed or disabled; if that's the case, I'll check with that kernel and report back. In any case, this doesn't appear to be a problem with X.org as much as it is a faulty kernel config. -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353494: xserver-xorg: fails to start on Cx486DX2 as well (SIGILL)
Package: xserver-xorg Version: 1:7.0.20 Followup-For: Bug #353494 I'm playing with unstable on an old 486 (Cyrix 486DX2) and it's giving me the same problem -- a SIGILL in the server while trying to draw the default stipple. I have the latest Xorg.log.0 attached. X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.12-1-686 i686 Current Operating System: Linux debian 2.6.16-1-486 #2 Thu May 4 18:15:54 UTC 2006 i486 Build Date: 16 March 2006 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: Mon May 29 02:45:22 2006 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device S3 Inc. ViRGE/DX or /GX (**) |--Input Device Generic Keyboard (**) Option XkbRules xorg (**) XKB: rules: xorg (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/lib/X11/fonts/CID does not exist. Entry deleted from font path. (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,/usr/share/fonts/X11/misc/,/usr/share/fonts/X11/TTF/,/usr/share/fonts/X11/OTF,/usr/share/fonts/X11/Type1/,/usr/share/fonts/X11/CID/,/usr/share/fonts/X11/100dpi/,/usr/share/fonts/X11/75dpi/ (==) RgbPath set to /usr/share/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.8 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 7.0.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 7.0.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:05:0: chip 1039,0496 card , rev 31 class 06,00,00 hdr 00 (II) PCI: 00:07:0: chip 5333,8a01 card 10b4,1717 rev 01 class 03,00,00 hdr 00 (II) PCI: 00:0b:0: chip 1045,c861 card 1045,c861 rev 10 class 0c,03,10 hdr 00 (II) PCI: 00:0d:0: chip 1000,000f card 1000,1000 rev 14 class 01,00,00 hdr 80 (II) PCI: 00:0d:1: chip 1000,000f card 1000,1000 rev 14 class 01,00,00 hdr 80 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:5:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (--) PCI:*(0:7:0) S3 Inc. ViRGE/DX or /GX rev 1, Mem @ 0xf800/26 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0x - 0x (0x1) IX[B] [6] -1 0 0x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xfedfc000 - 0xfedfcfff (0x1000) MX[B] [1] -1 0 0xfedfd800 - 0xfedfd8ff (0x100) MX[B] [2] -1 0 0xfedfe000 - 0xfedfefff (0x1000) MX[B] [3] -1 0 0xfedfdc00 - 0xfedfdcff (0x100) MX[B] [4] -1 0 0xfedff000 - 0xfedf (0x1000) MX[B] [5] -1 0 0xf800 - 0xfbff (0x400) MX[B](B) [6] -1 0 0xf400 - 0xf4ff (0x100) IX[B] [7] -1 0 0xfc00 - 0xfcff (0x100) IX[B] (II) Active PCI resource ranges after removing overlaps:
