driver issueshttps://gitlab.freedesktop.org/groups/xorg/driver/-/issues2018-08-10T20:40:27Zhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-armsoc/-/issues/1xf86-video-armsoc: causes X server crash in IgnoreClient upon VT switch (patc...2018-08-10T20:40:27ZBugzilla Migration Userxf86-video-armsoc: causes X server crash in IgnoreClient upon VT switch (patch drafted)## Submitted by Alexei Colin
Assigned to **Paul Geary `@pgeary`**
**[Link to original bug (#88312)](https://bugs.freedesktop.org/show_bug.cgi?id=88312)**
## Description
Created attachment 112112
Proposed patch that makes the probl...## Submitted by Alexei Colin
Assigned to **Paul Geary `@pgeary`**
**[Link to original bug (#88312)](https://bugs.freedesktop.org/show_bug.cgi?id=88312)**
## Description
Created attachment 112112
Proposed patch that makes the problem go away
X server dies with a segfault when attempting to switch VT out of the X session into a console with Ctrl-Alt-Fn, after having started xserver from a VT with 'startx'.
Xserver version: 1.16.3, armsoc driver: latest git 459fcb44e, hardware: Hardkernel Odroid U3 (Exynos 4412). This happened for 'awesome' window manager, but not for other root clients (e.g. xterm), for the reason explained below. A patch is attached.
Upon VT enter/leave, the armsoc driver calls AttendClient/IgnoreClient for all clients present in the clients array. Some of these clients may be 'gone', ie. for which CloseDownConnection had been called, which cleared their private osPrivate pointer to NULL. IgnoreClient will dereference this pointer if called on a gone client.
The reason this manifested with 'awesome' WM is because it creates two connections to the server: one long lived, and another one only for setting the wallpaper. The latter one is closed and becomes the 'gone' client. As a confirmation, disabling wallpaper in user config script, disables this bug.
The attached patch adds a check of the client state before calling AttendClient/IgnoreClient. The patched version switches between VTs fine.
**Attachment 112112**, "Proposed patch that makes the problem go away":
[0001-armsoc_driver-do-not-Attend-Ignore-gone-clients.patch](/uploads/f3930659628aa3762f85dd2021963cd1/0001-armsoc_driver-do-not-Attend-Ignore-gone-clients.patch)
Version: gitPaul GearyPaul Gearyhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-ast/-/issues/1[xf86-video-ast-0.99.9]:编译错误2018-08-17T05:42:54ZBugzilla Migration User[xf86-video-ast-0.99.9]:编译错误## Submitted by JerryDai
Assigned to **Y.C. Chen `@yc_chen`**
**[Link to original bug (#95321)](https://bugs.freedesktop.org/show_bug.cgi?id=95321)**
## Description
编译时不使用libpciaccess库(取消/usr/include/xorg/xorg-server.h 中#define XS...## Submitted by JerryDai
Assigned to **Y.C. Chen `@yc_chen`**
**[Link to original bug (#95321)](https://bugs.freedesktop.org/show_bug.cgi?id=95321)**
## Description
编译时不使用libpciaccess库(取消/usr/include/xorg/xorg-server.h 中#define XSERVER_LIBPCIACCESS定义):
编译输出:
```
make all-recursive
make[1]: Entering directory `/root/xf86-video-ast'
Making all in src
make[2]: Entering directory `/root/xf86-video-ast/src'
CC ast_2dtool.lo
In file included from ast_2dtool.c:39:
/usr/include/xorg/xf86PciInfo.h:50:2: warning: #warning "xf86PciInfo.h is deprecated. For greater compatibility, drivers should include necessary PCI IDs locally rather than relying on this file from xorg-server."
In file included from ast_2dtool.c:51:
ast.h:220: error: expected specifier-qualifier-list before 'pciVideoPtr'
ast_2dtool.c: In function 'bInitCMDQInfo':
ast_2dtool.c:73: error: 'struct _ASTRec' has no member named 'MMIO2D'
ast_2dtool.c:74: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:79: error: 'struct _ASTRec' has no member named 'pCMDQPtr'
ast_2dtool.c:79: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:81: error: 'struct _ASTRec' has no member named 'pCMDQPtr'
ast_2dtool.c:83: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:85: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:87: error: 'struct _ASTRec' has no member named 'pCMDQPtr'
ast_2dtool.c:89: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:91: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:91: error: 'struct _ASTRec' has no member named 'pCMDQPtr'
ast_2dtool.c:92: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:92: error: 'struct _ASTRec' has no member named 'FBVirtualAddr'
ast_2dtool.c:92: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:94: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:94: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:95: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:95: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:101: error: 'struct _ASTRec' has no member named 'MMIO2D'
ast_2dtool.c:107: error: 'struct _ASTRec' has no member named 'MMIO2D'
ast_2dtool.c:108: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c: In function 'bEnableCMDQ':
ast_2dtool.c:122: error: 'struct _ASTRec' has no member named 'DBGSelect'
ast_2dtool.c:124: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:124: error: 'struct _ASTRec' has no member named 'DBGSelect'
ast_2dtool.c:128: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:131: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:137: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:160: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:161: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:161: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:169: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c: In function 'bEnableCMDQ2300':
ast_2dtool.c:188: error: 'struct _ASTRec' has no member named 'DBGSelect'
ast_2dtool.c:190: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:190: error: 'struct _ASTRec' has no member named 'DBGSelect'
ast_2dtool.c:194: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:200: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:222: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:225: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:226: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:227: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:227: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:233: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c: In function 'bEnable2D':
ast_2dtool.c:251: error: 'struct _ASTRec' has no member named 'jChipType'
ast_2dtool.c:251: error: 'struct _ASTRec' has no member named 'jChipType'
ast_2dtool.c:254: error: 'struct _ASTRec' has no member named 'jChipType'
ast_2dtool.c:262: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:263: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:265: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:266: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:269: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:269: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:269: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:269: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c: In function 'vDisable2D':
ast_2dtool.c:297: error: 'struct _ASTRec' has no member named 'jChipType'
ast_2dtool.c:299: error: 'struct _ASTRec' has no member named 'SavedReg'
ast_2dtool.c:301: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:301: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:301: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:301: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:302: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:302: error: 'struct _ASTRec' has no member named 'SavedReg'
ast_2dtool.c:306: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:306: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:306: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:306: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c: In function 'vWaitEngIdle':
ast_2dtool.c:319: error: 'struct _ASTRec' has no member named 'jChipType'
ast_2dtool.c:323: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:323: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:327: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:327: error: 'struct _ASTRec' has no member named 'MMIOVirtualAddr'
ast_2dtool.c:331: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:336: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:337: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:338: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:339: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:340: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:341: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c: In function 'ulGetCMDQLength':
ast_2dtool.c:355: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:356: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:357: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:358: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:359: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:360: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c: In function 'pjRequestCMDQ':
ast_2dtool.c:372: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:373: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:374: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:379: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:391: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:395: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:396: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:397: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:404: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:416: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:420: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:427: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:428: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:431: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:443: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:447: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:448: error: 'struct _ASTRec' has no member named 'CMDQInfo'
ast_2dtool.c:449: error: 'struct _ASTRec' has no member named 'CMDQInfo'
make[2]: *** [ast_2dtool.lo] Error 1
make[2]: Leaving directory `/root/xf86-video-ast/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/xf86-video-ast'
make: *** [all] Error 2
```
Version: 7.7 (2012.06)Y.C. ChenY.C. Chenhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-cirrus/-/issues/1The cirrus driver crashes on CL-GD54642018-08-10T20:41:03ZBugzilla Migration UserThe cirrus driver crashes on CL-GD5464## Submitted by rm+..@..rm.net
Assigned to **Xorg Project Team**
**[Link to original bug (#25885)](https://bugs.freedesktop.org/show_bug.cgi?id=25885)**
## Description
Complete Xorg.log is attached. Last lines from the log are cop...## Submitted by rm+..@..rm.net
Assigned to **Xorg Project Team**
**[Link to original bug (#25885)](https://bugs.freedesktop.org/show_bug.cgi?id=25885)**
## Description
Complete Xorg.log is attached. Last lines from the log are copied below. Also tried 16bpp, does not work either.
I could get this CL-GD5464 video card to run only with the vesa driver (but obviously slower and not at the top resolution).
The same X Server runs fine on the same PC when using any of the two other PCI video cards I tried, using their mga and nv drivers correspondingly.
This PC has a Cyrix 6x86L CPU which is not 686, but is closer to being a 486-class CPU (could this be the issue?). The OS installed is the current Debian Testing.
-------------------------------
LgScreenInit
(II) CIRRUS(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
LgSave
LgModeInit 24 bpp, 135000 1280 1296 1440 1688 1024 1025 1028 1066
LgModeInit: depth 24 bits
SynthClock = 135000
LgSetClock freq=135.000MHz
LgSetClock: nom=42 den=e ffreq=134.998MHz
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x81314cb]
1: /usr/bin/X(xf86SigHandler+0x51) [0x80c1df1]
2: [0xb76ff400]
3: /usr/lib/xorg/modules/drivers//cirrus_laguna.so(LgAdjustFrame+0xb6) [0xb71dfc46]
4: /usr/lib/xorg/modules/drivers//cirrus_laguna.so(LgScreenInit+0x30f) [0xb71e02ff]
5: /usr/bin/X(AddScreen+0x19d) [0x80712cd]
6: /usr/bin/X(InitOutput+0x206) [0x80adfa6]
7: /usr/bin/X(main+0x1db) [0x80719bb]
8: /lib/libc.so.6(__libc_start_main+0xe5) [0xb73c2b55]
9: /usr/bin/X [0x8071051]
Fatal server error:
Caught signal 11. Server aborting
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
LgLeaveVT
LgRestore pScrn = 0x9f72248
Version: 7.4 (2008.09)https://gitlab.freedesktop.org/xorg/driver/xf86-video-fbdev/-/issues/1fbdev + offb 8bit colormap problems2018-08-10T20:41:29ZBugzilla Migration Userfbdev + offb 8bit colormap problems## Submitted by Peter Samuelson
Assigned to **Xorg Project Team**
**[Link to original bug (#9564)](https://bugs.freedesktop.org/show_bug.cgi?id=9564)**
## Description
fbdev 0.3.1 with Linux offb (kernel 2.6.17), 1280x1024_8bit, ha...## Submitted by Peter Samuelson
Assigned to **Xorg Project Team**
**[Link to original bug (#9564)](https://bugs.freedesktop.org/show_bug.cgi?id=9564)**
## Description
fbdev 0.3.1 with Linux offb (kernel 2.6.17), 1280x1024_8bit, hardware is IBM
GXT2000P on RS/6000 (PowerPC). Most colors show up as black. White shows up as
blue (perhaps #0000FF). I can also get something that looks like #FF80FF or so
- this is when xterm is trying to display bold green.
The Linux text console (also using offb) works fine, with the full range of 16
ANSI colors.
I'd be happy to provide logfiles and test patches.
Version: 7.1 (2006.05)https://gitlab.freedesktop.org/xorg/driver/xf86-video-geode/-/issues/1AMD/NSC Geode driver integration2018-08-10T20:42:05ZBugzilla Migration UserAMD/NSC Geode driver integration## Submitted by ajax `@ajax`
Assigned to **Xorg Project Team**
**[Link to original bug (#2088)](https://bugs.freedesktop.org/show_bug.cgi?id=2088)**
## Description
The Geode series chips are embedded graphics solutions, formerly f...## Submitted by ajax `@ajax`
Assigned to **Xorg Project Team**
**[Link to original bug (#2088)](https://bugs.freedesktop.org/show_bug.cgi?id=2088)**
## Description
The Geode series chips are embedded graphics solutions, formerly from National
Semiconductor and currently sold by AMD. AMD has various X drivers for the
Geode series on its website:
http://www.amd.com/us-en/ConnectivitySolutions/ProductInformation/0,,50_2330_9863_11363,00.html
There is also a Geode driver on the geode-0-0-1-branch of DRI's xc tree, last
touched by Alah Hourihane sometime in 2002.
There is already an nsc(4) driver in the tree, which supports much of the same
hardware (but perhaps not all). Someone should investigate AMD's drivers and,
if they provide any additional support, merge them to the tree.
### Blocking
* [Bug 1903](https://bugs.freedesktop.org/show_bug.cgi?id=1903)https://gitlab.freedesktop.org/xorg/driver/xf86-video-mach64/-/issues/1Xorg Segfaults when certain X apps (Gtk ones?) are invoked2019-10-06T18:26:25ZBugzilla Migration UserXorg Segfaults when certain X apps (Gtk ones?) are invoked## Submitted by Tom Crane
Assigned to **Xorg Project Team**
**[Link to original bug (#70556)](https://bugs.freedesktop.org/show_bug.cgi?id=70556)**
## Description
Created attachment 87768
Xorg.0.log logfile and GDB session tarball...## Submitted by Tom Crane
Assigned to **Xorg Project Team**
**[Link to original bug (#70556)](https://bugs.freedesktop.org/show_bug.cgi?id=70556)**
## Description
Created attachment 87768
Xorg.0.log logfile and GDB session tarball
The X server segfaults when certain X apps are invoked (eg. the Gimp, Firefox, Thunderbird which all use Gtk). With simple X apps (eg. xterm, xcalc) there is no problem.
```
H/W + S/W details:
Distro: Slackware current.
Kernel: 3.9.9
Graphics adapter: SuperMicro X5DPA onboard graphics. Results from lspci,
# lspci -s 01:04.0 -vv
01:04.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Rage XL (rev 27) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices [AMD] nee ATI Rage XL
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- `<MAbort- >`SERR- <PERR- INTx-
Latency: 64 (2000ns min), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at b000 [size=256]
Region 2: Memory at fe6ff000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at fe6c0000 [disabled] [size=128K]
Capabilities: [5c] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Xorg S/W configuration:
# /usr/bin/X -version
X.Org X Server 1.14.3
Release Date: 2013-09-12
X Protocol Version 11, Revision 0
Build Operating System: Slackware 14.1 Slackware Linux Project
Current Operating System: Linux mklab 3.9.9-smp #1 SMP Fri Jul 5 20:07:07 CDT 2013 i686
Kernel command line: auto BOOT_IMAGE=lin-smp-3.9.9 ro root=fd00
Build Date: 15 October 2013 03:19:29AM
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
```
I have rebuilt the X server from source using the Distro's build scripts but with CFLAGS=-g -O0. I have no /etc/X11/xorg.conf or /etc/X11/xorg.conf.d files. Xorg is invoked by kdm using '/usr/bin/X -br -novtswitch -quiet :0 vt7 -nolisten tcp -auth /var/run/xauth/A:0-2EbFha'. Following is the last part of the Xorg.0.log file. The complete file is included as an attachment.
```
[399059.006] (EE)
[399059.006] (EE) Backtrace:
[399059.006] (EE) 0: /usr/bin/X (xorg_backtrace+0x47) [0x822813b]
[399059.006] (EE) 1: /usr/bin/X (0x8048000+0x1e4f95) [0x822cf95]
[399059.006] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xffffe40c]
[399059.006] (EE) 3: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6fff000+0x2cd97) [0xb702bd97]
[399059.006] (EE) 4: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6fff000+0x2ce7c) [0xb702be7c]
[399059.006] (EE) 5: /usr/lib/xorg/modules/libexa.so (0xb6647000+0x104e1) [0xb66574e1]
[399059.006] (EE) 6: /usr/lib/xorg/modules/libexa.so (0xb6647000+0x10c50) [0xb6657c50]
[399059.006] (EE) 7: /usr/lib/xorg/modules/libexa.so (0xb6647000+0xdd14) [0xb6654d14]
[399059.006] (EE) 8: /usr/lib/xorg/modules/libexa.so (0xb6647000+0xe640) [0xb6655640]
[399059.006] (EE) 9: /usr/bin/X (0x8048000+0x1483c8) [0x81903c8]
[399059.006] (EE) 10: /usr/bin/X (CompositeGlyphs+0xaa) [0x817cbb1]
[399059.007] (EE) 11: /usr/bin/X (0x8048000+0x13f25b) [0x818725b]
[399059.007] (EE) 12: /usr/bin/X (0x8048000+0x140c5c) [0x8188c5c]
[399059.007] (EE) 13: /usr/bin/X (0x8048000+0x2afd6) [0x8072fd6]
[399059.007] (EE) 14: /usr/bin/X (0x8048000+0x1d23a) [0x806523a]
[399059.007] (EE) 15: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb713f7a3]
[399059.007] (EE) 16: /usr/bin/X (0x8048000+0x1cb61) [0x8064b61]
[399059.007] (EE)
[399059.007] (EE) Segmentation fault at address 0xc
[399059.007] (EE)
Fatal server error:
[399059.007] (EE) Caught signal 11 (Segmentation fault). Server aborting
[399059.007] (EE)
[399059.007] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[399059.007] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[399059.007] (EE)
[399059.023] (EE) Server terminated with error (1). Closing log file.
```
Gdb debugging session: Attaching gdb to the running /usr/bin/X process and starting the Gimp to trigger the segfault reveals more information. Please see the attached file.
Please let me know if any other information is needed.
Thanks for your help.
Tom Crane.
**Attachment 87768**, "Xorg.0.log logfile and GDB session tarball":
[attachments.tar.gz](/uploads/243f144d72a23788f890e44ccead3fbe/attachments.tar.gz)
Version: 7.7 (2012.06)https://gitlab.freedesktop.org/xorg/driver/xf86-video-mga/-/issues/1mga(4) man page is incomplete2018-08-10T20:43:01ZBugzilla Migration Usermga(4) man page is incomplete## Submitted by ATek
Assigned to **Xorg Project Team**
**[Link to original bug (#2038)](https://bugs.freedesktop.org/show_bug.cgi?id=2038)**
## Description
I've installed MDK10.1 with xorg server on a PC with Matrox G550 Dual Head...## Submitted by ATek
Assigned to **Xorg Project Team**
**[Link to original bug (#2038)](https://bugs.freedesktop.org/show_bug.cgi?id=2038)**
## Description
I've installed MDK10.1 with xorg server on a PC with Matrox G550 Dual Head.
I've a CRT on head 0 and LCD on head 1.
When linux start it use head 0 but when X server start head 0 and head 1 are
swapped. I've tried to swap "Screen 0" and "Screen 1" in Section "Device" for
device 1 and device 2 but no solution.
What can I do?
Thanxhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-neomagic/-/issues/1High CPU Usage, Poor Acceleration, and Limited Size with Neomagic NM23802018-08-10T20:44:16ZBugzilla Migration UserHigh CPU Usage, Poor Acceleration, and Limited Size with Neomagic NM2380## Submitted by Chris Johnson
Assigned to **Xorg Project Team**
**[Link to original bug (#28041)](https://bugs.freedesktop.org/show_bug.cgi?id=28041)**
## Description
Created attachment 35527
Xorg.0.log
The current OS is Ubuntu 1...## Submitted by Chris Johnson
Assigned to **Xorg Project Team**
**[Link to original bug (#28041)](https://bugs.freedesktop.org/show_bug.cgi?id=28041)**
## Description
Created attachment 35527
Xorg.0.log
The current OS is Ubuntu 10.04 but the problems exist in other operating systems. The system is a Sony Notebook PCG-F580k with a 700 MHz Pentium III processor, 384 MB of RAM, and a Neomagic Corporation NM2380 [MagicMedia 256XL+] video chip. The NM2380 is capable of much better performance as shown in Windows 2000.
When playing a DVD video the CPU usage by the X server is about 20%. It is closer to 10% in Ubuntu Hardy.
The Option "OverlayMem" had to be enabled in Xorg.conf. to play any video.
The MTRR range "reg02: base=0x0fc000000 (4032MB), size= 8MB, count=1: write-combining" has to be manually enabled by adding the appropriate lines to etc/rc.local.
Attempting to play any video larger than DVD resolution results in a garbled image unless the window is made smaller. Windows 2000 is able to play a 960 X 540 H264 video with deblocking disabled.
**Attachment 35527**, "Xorg.0.log":
[Xorg.0.log](/uploads/6c30659b341dab868b81ceb2ca83f936/Xorg.0.log)https://gitlab.freedesktop.org/xorg/driver/xf86-video-newport/-/issues/1xf86-video-newport: driver doesn't build2022-01-30T23:30:26ZBugzilla Migration Userxf86-video-newport: driver doesn't build## Submitted by Imre Deak `@ideak`
Assigned to **Xorg Project Team**
**[Link to original bug (#54124)](https://bugs.freedesktop.org/show_bug.cgi?id=54124)**
## Description
Building this drivers fails due to at least missing xaa.h ...## Submitted by Imre Deak `@ideak`
Assigned to **Xorg Project Team**
**[Link to original bug (#54124)](https://bugs.freedesktop.org/show_bug.cgi?id=54124)**
## Description
Building this drivers fails due to at least missing xaa.h and using an outdated interface for pScreen.
Version: githttps://gitlab.freedesktop.org/xorg/driver/xf86-video-omap/-/issues/1xf86-video-omap access request2022-01-30T23:46:32ZBugzilla Migration Userxf86-video-omap access request## Submitted by Robert Nelson
Assigned to **fd.o Admin Massive**
**[Link to original bug (#87115)](https://bugs.freedesktop.org/show_bug.cgi?id=87115)**
## Description
Created attachment 110583
gpg public key
Access request for g...## Submitted by Robert Nelson
Assigned to **fd.o Admin Massive**
**[Link to original bug (#87115)](https://bugs.freedesktop.org/show_bug.cgi?id=87115)**
## Description
Created attachment 110583
gpg public key
Access request for git access to xf86-video-omap for beagleboard.org
**Attachment 110583**, "gpg public key":
[rcn-ee-gpg.pub](/uploads/38893943397a1aa4bb091553af2f7fc2/rcn-ee-gpg.pub)
Version: githttps://gitlab.freedesktop.org/xorg/driver/xf86-video-s3/-/issues/1blank screen with S3 driver v0.6.0 and with "86C775 Trio64V2/DX, 86C785 Trio6...2018-08-10T20:45:34ZBugzilla Migration Userblank screen with S3 driver v0.6.0 and with "86C775 Trio64V2/DX, 86C785 Trio64V2/GX" chipset## Submitted by Uwe Galle
Assigned to **Xorg Project Team**
**[Link to original bug (#16859)](https://bugs.freedesktop.org/show_bug.cgi?id=16859)**
## Description
Created attachment 17906
Xorg.0.log generated by sax2
I am using o...## Submitted by Uwe Galle
Assigned to **Xorg Project Team**
**[Link to original bug (#16859)](https://bugs.freedesktop.org/show_bug.cgi?id=16859)**
## Description
Created attachment 17906
Xorg.0.log generated by sax2
I am using openSUSE 10.3 with Xorg 7.2.0. According to hwinfo --gfxcard I have a "86C775 Trio64V2/DX, 86C785 Trio64V2/GX" on board controller. I cloned the latest git commit (with git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-s3), qgit shows that this is the version of 07.07.08. I compiled this driver with
autoreconf -fi
./configure --prefix=/usr
make
make install
I restarted the system in runlevel 3 and invoked sax2 what results in a blank screen. This shows that the system is not configurable with the S3 driver. With Ctrl-Alt-del the system can be restarted.
My hwinfo --gfxcard shows
15: PCI 0f.0: 0300 VGA compatible controller (VGA)
[Created at pci.301]
UDI: /org/freedesktop/Hal/devices/pci_5333_8901
Unique ID: _+Pw.zRTkGjKA2qF
SysFS ID: /devices/pci0000:00/0000:00:0f.0
SysFS BusID: 0000:00:0f.0
Hardware Class: graphics card
Model: "S3 86C775 Trio64V2/DX, 86C785 Trio64V2/GX"
Vendor: pci 0x5333 "S3 Inc."
Device: pci 0x8901 "Trio 64V2/DX or /GX"
SubVendor: pci 0x5333 "S3 Inc."
SubDevice: pci 0x8901 "86C775 Trio64V2/DX, 86C785 Trio64V2/GX"
Revision: 0x16
Memory Range: 0xf8000000-0xfbffffff (rw,non-prefetchable)
Memory Range: 0x70100000-0x7010ffff (ro,prefetchable,disabled)
IRQ: 18 (15 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00005333d00008901sv00005333sd00008901bc03sc00i00"
Driver Info #0:
XFree86 v4 Server Module: s3
Config Status: cfg=no, avail=yes, need=no, active=unknown
Primary display adapter: #15
The essential parts of My Xorg.0.log are
(II) Host-to-PCI bridge:
(II) Bus 1: bridge is at (0:0:0), (1,1,0), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(--) PCI:*(0:15:0) S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] rev 22, Mem @ 0xf8000000/26
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
...
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.2.0
ABI class: X.Org Video Driver, version 1.2
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xf8000000 - 0xfbffffff (0x4000000) MS[B]
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xf7e00000 - 0xf7efffff (0x100000) MX[B]
[6] -1 0 0xf7fffc00 - 0xf7fffcff (0x100) MX[B]
[7] -1 0 0xfebfdc00 - 0xfebfdc1f (0x20) MX[B]
[8] -1 0 0xfebfe000 - 0xfebfffff (0x2000) MX[B]
[9] -1 0 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B)
[10] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[11] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[12] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[15] -1 0 0x00004800 - 0x000048ff (0x100) IX[B]
[16] -1 0 0x00004700 - 0x000047ff (0x100) IX[B]
[17] -1 0 0x0000ff00 - 0x0000ff1f (0x20) IX[B]
[18] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[19] -1 0 0x00002180 - 0x0000219f (0x20) IX[B]
[20] -1 0 0x00002000 - 0x000020ff (0x100) IX[B]
[21] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[22] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(==) s3(0): Write-combining range (0xf8000000,0x100000)
Here stops Xorg.0.log without preceding error message.
At the moment I don't want to upgrade to openSUSE 11.0 and Xorg 7.3.x because I have an application what is not fully tested on this release. So I need a solution for 7.2.0.
I attach the complete Xorg.0.log. Note that the configuration already hangs with sax2 so that I cannot provide a xorg.conf. I can start my X server with the vesa driver. I also tested the version 0.6.0 as of 19.03.08.
**Attachment 17906**, "Xorg.0.log generated by sax2":
[Xorg.0.log](/uploads/7299b689bd775b9ef30619a9232f467f/Xorg.0.log)
Version: 7.2 (2007.02)https://gitlab.freedesktop.org/xorg/driver/xf86-video-s3virge/-/issues/1s3virge driver segfaults with PROBE_DETECT2018-08-10T20:45:51ZBugzilla Migration Users3virge driver segfaults with PROBE_DETECT## Submitted by Fernando Carrijo
Assigned to **Xorg Project Team**
**[Link to original bug (#28485)](https://bugs.freedesktop.org/show_bug.cgi?id=28485)**
## Description
Created attachment 36202
All the aforementioned logs
Runnin...## Submitted by Fernando Carrijo
Assigned to **Xorg Project Team**
**[Link to original bug (#28485)](https://bugs.freedesktop.org/show_bug.cgi?id=28485)**
## Description
Created attachment 36202
All the aforementioned logs
Running the X Server with "sudo /opt/xorg/bin/Xorg :1 -configure -verbose" causes the the s3virge driver to segfault during system probe. The corresponding log file is attached as Xorg.1.log.
Running the X Server with "sudo startx -- /opt/xorg/bin/Xorg :1 -verbose" does not cause the s3virge driver to segfault, albeit it renders the screen garbled and logs an error message related to IA-32 MTRR registers. That message can be found attached in Xorg.2.log.
Both the X Server and the s3virge driver are unstable versions cloned from the official Freedesktop's git repositories, whose SHAs are 8e97e5f9425639a and 11fc32f5f06d20c respectively.
Attached is also the output of lspci.
**Attachment 36202**, "All the aforementioned logs":
[s3virge-logs.tar.gz](/uploads/dbfc2ef0fe12671896572bd0340fad16/s3virge-logs.tar.gz)
Version: githttps://gitlab.freedesktop.org/xorg/driver/xf86-video-savage/-/issues/1DRI functionality is not completely restored after software suspend2018-08-10T20:46:04ZBugzilla Migration UserDRI functionality is not completely restored after software suspend## Submitted by Slava Gorbunov
Assigned to **Tormod Volden**
**[Link to original bug (#6612)](https://bugs.freedesktop.org/show_bug.cgi?id=6612)**
## Description
After resuming from software suspend (which involves switching to te...## Submitted by Slava Gorbunov
Assigned to **Tormod Volden**
**[Link to original bug (#6612)](https://bugs.freedesktop.org/show_bug.cgi?id=6612)**
## Description
After resuming from software suspend (which involves switching to text VT and
back) DRI works only partialy. Simple applications (like glxgears or gl-117 (the
3d game with rather simple 3d graphics)) work well, but more complex
applications don't. For example, Blender doesn't draw labels on buttons, draws
some garbage instead of menus and outputs some garbage in the top left coner of
the screen (above all other windows). More complex 3d games (like tuxracer)
cause immediate lockup. Before suspending (and after restart of Xserver)
everything works well.
Version: 6.8.99.901 (6.9 RC1)https://gitlab.freedesktop.org/xorg/driver/xf86-video-siliconmotion/-/issues/1black screen and no keyboard on Silicon Motion with Xserver 1.32018-08-10T20:46:32ZBugzilla Migration Userblack screen and no keyboard on Silicon Motion with Xserver 1.3## Submitted by Brice Goglin `@bgoglin`
Assigned to **Xorg Project Team**
**[Link to original bug (#11845)](https://bugs.freedesktop.org/show_bug.cgi?id=11845)**
## Description
Reported by Clayton <ckoeni@gmail.com> on the Debian ...## Submitted by Brice Goglin `@bgoglin`
Assigned to **Xorg Project Team**
**[Link to original bug (#11845)](https://bugs.freedesktop.org/show_bug.cgi?id=11845)**
## Description
Reported by Clayton <ckoeni@gmail.com> on the Debian BTS 2 months ago. Upgrading to Xserver 1.3 broke X on his "Silicon Motion, Inc. SM712 LynxEM+ (rev a0)" board. It gives a black screen. The config and log with Xserver 1.3 are both available in http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=428711
I thought it could be related to the VBE filtering problems that ajax fixed for the VESA driver, but Clayton tried a recent Debian Xserver with this patch and it didn't help.
I am assigning to the server for now since it was working fine with Xserver 1.1. But I don't know whether the server or driver actually needs to be fixed here.
Brice
Version: 7.2 (2007.02)https://gitlab.freedesktop.org/xorg/driver/xf86-video-sis/-/issues/1Switching to text console and back hangs X server2018-08-10T20:47:08ZBugzilla Migration UserSwitching to text console and back hangs X server## Submitted by Pawel Salek
Assigned to **Xorg Project Team**
**[Link to original bug (#5842)](https://bugs.freedesktop.org/show_bug.cgi?id=5842)**
## Description
It appears that this is probably a bug in the SiS driver not
saving...## Submitted by Pawel Salek
Assigned to **Xorg Project Team**
**[Link to original bug (#5842)](https://bugs.freedesktop.org/show_bug.cgi?id=5842)**
## Description
It appears that this is probably a bug in the SiS driver not
saving/restoring properly. Switching the virtual console to text mode and back
leaves the Xorg process unresponsive and the screen white. This problem has
appearead in Fedora rawhide in the last month, I believe. The box as such is
alive and one can connect via ssh to it. See also
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180465 for the original report.
After the hang, the Xorg process gets stuck. It utilizes 100% CPU. When I
connect gdb to Xorg, I get following stack trace:
```
(gdb) where
#0 0x00000036286bd900 in __write_nocancel () from /lib64/libc.so.6
#1 0x0000003628667793 in _IO_new_file_write () from /lib64/libc.so.6
#2 0x0000003628668bef in _IO_new_file_xsputn () from /lib64/libc.so.6
#3 0x000000362865e89b in fwrite () from /lib64/libc.so.6
#4 0x00000000005666a2 in LogVWrite ()
#5 0x000000000056717d in LogVMessageVerb ()
#6 0x0000000000481f2c in xf86VDrvMsgVerb ()
#7 0x00002b59ab2893c2 in sisRestoreExtRegisterLock ()
from /usr/lib64/xorg/modules/drivers/sis_drv.so
#8 0x00002b59ab28b2f5 in sisSaveUnlockExtRegisterLock ()
from /usr/lib64/xorg/modules/drivers/sis_drv.so
#9 0x00002b59ab28f4d9 in SiS_SetSISTVedgeenhance ()
from /usr/lib64/xorg/modules/drivers/sis_drv.so
#10 0x00002b59ab29b3cd in SISAdjustFrame ()
from /usr/lib64/xorg/modules/drivers/sis_drv.so
#11 0x00002b59ab29b850 in SISAdjustFrame ()
from /usr/lib64/xorg/modules/drivers/sis_drv.so
#12 0x00002b59ab5fa69b in xf86ForceHWCursor ()
from /usr/lib64/xorg/modules/libramdac.so
#13 0x000000000047f7d1 in xf86InitFBManagerArea ()
#14 0x000000000048c152 in xf86XVScreenInit ()
#15 0x0000000000479714 in xf86Wakeup ()
#16 0x000000000044e2a5 in WakeupHandler ()
#17 0x0000000000559cb4 in WaitForSomething ()
#18 0x000000000044a33a in Dispatch ()
#19 0x0000000000432c95 in main ()
```
Version: 7.0.0https://gitlab.freedesktop.org/xorg/driver/xf86-video-trident/-/issues/1cyber9320 on the Thinkpad 365X[D] DSTN - "orange lines" and system crash/freeze2018-08-10T20:48:04ZBugzilla Migration Usercyber9320 on the Thinkpad 365X[D] DSTN - "orange lines" and system crash/freeze## Submitted by James
Assigned to **Egbert Eich**
**[Link to original bug (#2323)](https://bugs.freedesktop.org/show_bug.cgi?id=2323)**
## Description
The XFree86 trident driver has always had a problem with the Thinkpad 365XD Tri...## Submitted by James
Assigned to **Egbert Eich**
**[Link to original bug (#2323)](https://bugs.freedesktop.org/show_bug.cgi?id=2323)**
## Description
The XFree86 trident driver has always had a problem with the Thinkpad 365XD Trident
TGUI 9320 "Cyber" chipset interacting with IBM's DSTN 800x600 LCD. On startup, the
screen would only display two horizontal orange lines and "burn" the LCD, physically
damaging the display - with some recovery over time, as if each section of the dual
scan display had lost the vertical scan signal.
The traditional work-around has been to press Fn and F7, the LCD/external-monitor
switching function, after the X server is started. The result would be a normal
display after a few second delay. This was possible with the XFree86 SVGA driver
version 3.3.6 at least.
The new Xorg trident driver still shows the same problem with the burning orange
lines, but the "Fn and F7" hack has a problem - the system freezes / crashes
instantly. The laptop must be powered down to recover.
Starting with the external display, the situation is the same (without the horizontal
lines of course) - after the X server is started, the screen is blank, and screen
switching freezes / crashes the system, requiring a hard reset.
Starting with the dual display mode is again the same. Starting the X server leaves
both screens blank, with burning orange lines on the LCD. Screen switching to LCD-
only freezes / crashes the system.
Killing the X server without switching displays returns a blank virtual terminal that
can be recovered using "setfont". Leaving the X server for a virtual terminal first,
Fn F7 rotates through the displays normally. Changing back to the X server and,
again, using Fn F7 freezes / crashes the system.
I would infer that this system freeze problem has less to do with the blank X server
startup screen, and more to do with the interaction between the Thinkpad screen-
switching and the Xorg X server.
Trying different trident driver options seems to make no difference. Trying different
bpp options is slightly different. At 16 bpp, instead of 8 bpp - the 365XD has only
1MB of video ram and the driver insists on using a 1024 byte pitch - the X server
starts with a visible display on the left half, and blank or with half-hight vertical
lines on the right half of the LCD, and blank on the external display. Still, trying
the Fn F7 hack fails to switch screens, or, with the option "NoCyberShadow" suggested
in the trident man page, again the system freezes.
Now, the XFree86 version 4 driver has these same problems, so they are inherited.
Something was lost going from version 3 to version 4. What's different? Could
someone please take a look at this. This is a problem here because the vesa bios is
version 1.2 instead of the version 2 needed to use the vesa framebuffer driver.
BTW, the Linux "drivers/video/tridentfb" driver acts similarly, showing the burning
orange lines and blank screen on start up, and freezing the system with Fn F7.
Version: 6.8.1https://gitlab.freedesktop.org/xorg/driver/xf86-video-vesa/-/issues/1Text corruption in XEmacs using vesa driver on ATI X15502018-08-29T15:55:47ZBugzilla Migration UserText corruption in XEmacs using vesa driver on ATI X1550## Submitted by 3rg..@..il.com
Assigned to **Xorg Project Team**
**[Link to original bug (#15357)](https://bugs.freedesktop.org/show_bug.cgi?id=15357)**
## Description
Created attachment 15691
Screenshot showing corruption (middle...## Submitted by 3rg..@..il.com
Assigned to **Xorg Project Team**
**[Link to original bug (#15357)](https://bugs.freedesktop.org/show_bug.cgi?id=15357)**
## Description
Created attachment 15691
Screenshot showing corruption (middle of right side window)
Using Mandriva 2008, vesa driver version x11-driver-video-vesa-1.3.0-3mdv2008.0 with x11-server-xorg-1.3.0.0-24.1mdv2008.0 and xorg-x11-7.2.0-2mdv2008.0, I get text corruption in Xemacs (see attached screenshot, though this is less bad than it sometimes is). More information is available at <http://ati.cchtml.com/show_bug.cgi?id=927> (I have the same problem with fglrx driver). This problem doesn't occur with the radeonhd driver (but many others do).
**Attachment 15691**, "Screenshot showing corruption (middle of right side window)":
![xemacs1](/uploads/88146895dea59b87fd904ad83832288d/xemacs1.png)
Version: 7.2 (2007.02)https://gitlab.freedesktop.org/xorg/driver/xf86-video-voodoo/-/issues/1Onchip buffer overflow (solution included)2018-08-10T20:49:13ZBugzilla Migration UserOnchip buffer overflow (solution included)## Submitted by M8R..@..or.com
Assigned to **Xorg Project Team**
**[Link to original bug (#67180)](https://bugs.freedesktop.org/show_bug.cgi?id=67180)**
## Description
On modern mainboards, voodoo is not fast enough to process dat...## Submitted by M8R..@..or.com
Assigned to **Xorg Project Team**
**[Link to original bug (#67180)](https://bugs.freedesktop.org/show_bug.cgi?id=67180)**
## Description
On modern mainboards, voodoo is not fast enough to process data faster than they come from a mainboard unless buffer state is checked as it should be (due to the official 3dfx .PDF) and in case of PCIe damage, no voodoo cards can be used for those mainboards.
The solution is here http://www.lubuntu.ru/forum/viewtopic.php?f=12&t=523&p=9941#p9902
First block of code is "before" and second is "after". Not to be confused with another pair of blocks later on the page.https://gitlab.freedesktop.org/xorg/driver/xf86-video-xgi/-/issues/1xgi volari Z7 bad performance2018-10-16T18:01:19ZBugzilla Migration Userxgi volari Z7 bad performance## Submitted by smr
Assigned to **Xorg Project Team**
**[Link to original bug (#12379)](https://bugs.freedesktop.org/show_bug.cgi?id=12379)**
## Description
I tried using this driver on my volari z7 card.
I found performance of ve...## Submitted by smr
Assigned to **Xorg Project Team**
**[Link to original bug (#12379)](https://bugs.freedesktop.org/show_bug.cgi?id=12379)**
## Description
I tried using this driver on my volari z7 card.
I found performance of vesa driver much better.
On glxgears vesa gives 650fps, while this driver gave me only 150fps.
Is it like this only, or am i doing something wrong ?https://gitlab.freedesktop.org/xorg/driver/xf86-video-r128/-/issues/1[r128] XVideo broken with interlaced modeline2018-08-10T20:50:04ZBugzilla Migration User[r128] XVideo broken with interlaced modeline## Submitted by Cory Papenfuss
Assigned to **Xorg Project Team**
**[Link to original bug (#4587)](https://bugs.freedesktop.org/show_bug.cgi?id=4587)**
## Description
I've followed this problem from Redhat9 through FC4, and it has ...## Submitted by Cory Papenfuss
Assigned to **Xorg Project Team**
**[Link to original bug (#4587)](https://bugs.freedesktop.org/show_bug.cgi?id=4587)**
## Description
I've followed this problem from Redhat9 through FC4, and it has stayed
consistent. I use direct NTSC frequencies out of the VGA port for tvout. When
playing a video using XVideo extention, only the top half of the video plays,
but it takes up the full screen. At one point, (still XFree86-based distro) I
used the GATOS driver to fix the problem. Both the 'ati' and 'r128' driver
exhibit this problem on a r128 card. The Mach64 and radeon appear to work now
(with 6.8.2 at least).
Version: 6.8.2