Re: MACH64: Caught signal 11 (Segmentation fault)

[Morgan Wesström]

On 2023-04-18 23:06, Alex Deucher wrote:

Make sure the PCI register BAR is properly mapped in the ddx.  Those old ddxes 
required direct access to the hardware in the X server.

Alex



Thank you for replying, Alex. My knowledge of hardware on this level is rather 
limited and I humbly ask for some help understanding exactly what I need to do. 
Do I need to hardcode the video cards memory and I/O regions into the driver 
itself somewhere and recompile or do I need to add them to the Xorg.conf? Or do 
I need to tell the kernel somehow, when it loads, to configure the card in some 
special way?

I tried adding the following lines to Xorg.conf after looking in the output 
from lspci and dmesg but there was no difference in behaviour.

MemBase 0xfd00
IOBase  0x2000

I'm most likely misunderstanding what I need to do because since lspci and 
dmesg can extract such info from the system itself I would assume the driver 
could too.

Here is the output from lspci -vv:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage 
Mobility AGP 2x Series (rev 64) (prog-if 00 [VGA controller])
Subsystem: Fujitsu Limited. Rage Mobility AGP 2x Series
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
Capabilities: [5c] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: atyfb
Kernel modules: atyfb

And the video related lines from dmesg:

[0.936593] pci_bus :01: extended config space not accessible
[0.936998] pci :01:00.0: [1002:4c4d] type 00 class 0x03
[0.937119] pci :01:00.0: reg 0x10: [mem 0xfd00-0xfdff]
[0.937213] pci :01:00.0: reg 0x14: [io  0x2000-0x20ff]
[0.937306] pci :01:00.0: reg 0x18: [mem 0xfc10-0xfc100fff]
[0.937422] pci :01:00.0: reg 0x30: [mem 0x-0x0001 pref]
[0.937577] pci :01:00.0: Video device with shadowed ROM at [mem 
0x000c-0x000d]
[0.937724] pci :01:00.0: supports D1 D2
[0.979622] pci :01:00.0: vgaarb: setting as boot VGA device
[0.979722] pci :01:00.0: vgaarb: bridge control possible
[0.979795] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.979893] vgaarb: loaded
[1.345963] pci :00:01.0: PCI bridge to [bus 01]
[1.346040] pci :00:01.0:   bridge window [io  0x2000-0x2fff]
[1.346123] pci :00:01.0:   bridge window [mem 0xfc10-0xfdff]
[1.347203] pci_bus :01: resource 0 [io  0x2000-0x2fff]
[1.347280] pci_bus :01: resource 1 [mem 0xfc10-0xfdff]
[1.451734] agpgart-intel :00:00.0: Intel 440BX Chipset
[1.458124] agpgart-intel :00:00.0: AGP aperture is 64M @ 0xe000
[  153.358059] atyfb :01:00.0: vgaarb: deactivate vga console
[  153.360579] Console: switching to colour dummy device 80x25
[  153.366184] ACPI: \_SB_.LNKB: Enabled at IRQ 9
[  153.366255] atyfb: using auxiliary register aperture
[  153.367078] atyfb: 3D RAGE Mobility P/M (Mach64 LM, AGP 2x) [0x4c4d rev 0x64]
[  153.367121] atyfb: Mach64 BIOS is located at c, mapped at cca4.
[  153.367136] atyfb: BIOS frequency table:
[  153.367143] atyfb: PCLK_min_freq 984, PCLK_max_freq 23600, ref_freq 2950, 
ref_divider 64
[  153.367158] atyfb: MCLK_pwd 4200, MCLK_max_freq 8300, XCLK_max_freq 12500, 
SCLK_freq 5000
[  153.367173] atyfb: BIOS contains driver information table.
[  153.367186] atyfb: colour active matrix monitor detected: LG LP141XA
[  153.367199] atyfb:id=1, 1024x768 pixels, 262144 colours (LT mode)
[  153.367215] atyfb:supports refresh rates [60], default 60 Hz
[  153.367231] atyfb:LCD CRTC parameters: 65.40  1024 1048 1184 1344  
768 770 776 806
[  153.367253] atyfb:   : 15384 160 1024 24 136 30 768 
2 6
[  153.367312] atyfb: 4M SDRAM (2:1) (32-bit), 29.498928 MHz XTAL, 236 MHz PLL, 
83 Mhz MCLK, 63 MHz XCLK
[  153.385617] fbcon: ATY Mach64 (fb0) is primary device
[  153.459847] Console: switching to colour frame buffer device 128x48
[  153.42] atyfb: fb0: ATY Mach64 frame buffer device on PCI

Please let me know if you need any other info and thank you again for helping 
me. :)

/Morgan

Re: MACH64: Caught signal 11 (Segmentation fault)

[Alex Deucher]

 Make sure the PCI register BAR is properly mapped in the ddx.  Those old ddxes 
required direct access to the hardware in the X server.  

Alex

On Monday, April 17, 2023 at 04:18:16 PM EDT, Morgan Wesström 
 wrote:  
 
 Dear list,

This is a small hobby project of mine so it's no big deal if it can't be 
resolved but I don't mind digging a little deeper into it myself if I can only 
get a few pointers.

I've been a Gentoo Linux user for 15+ years so I'm fairly confident in 
compiling things in various ways but I'm no C programmer and definitely don't 
have the deep technical knowledge needed to create device drivers.

With that said, I needed a challenge and went on to install Gentoo on the 
oldest machine still in my possession - a 22 year old laptop with a 32-bit 
Pentium III Celeron. It's quite restricted hardware wise (maxed out RAM is 
196MB) but I got it running. I even made Xorg run with the generic fbdev driver 
but was hoping to unlock at least some 2D acceleration.

The video card is an ATI Rage Mobility AGP 2x Series (1002:4c4d) and after some 
digging I understood that this was a mach64 card. Driver is included and 
activated in my kernel (atyfb, Linux 6.1.19) but I also needed 
xf86-video-mach64 for Xorg. Unfortunately that driver seems to have been ripped 
out of the main tree around 2010 or so but apparently it's still maintained and 
version 6.9.7 was released last year.

I downloaded it from 
https://gitlab.freedesktop.org/xorg/driver/xf86-video-mach64.git, compiled and 
installed it but X segfaults with a signal 11 when I try to use it. I've 
compiled it with debug symbols so I can get a proper backtrace but after that 
I'm stuck. I don't know what the driver is doing or what it's supposed to do at 
this point.

Here's some info from the debugger:

Program received signal SIGSEGV, Segmentation fault.
ATIMach64Detect (Chip=77, ChipType=19533, pATI=0x1c74110) at atiprobe.c:143
143        bus_cntl = inr(BUS_CNTL);
(gdb) bt
#0  ATIMach64Detect (Chip=77, ChipType=19533, pATI=0x1c74110) at atiprobe.c:143
#1  ATIMach64Probe (Chip=77, pVideo=0x1c7dbe0, pATI=0x1c74110) at atiprobe.c:278
#2  ATIMach64ProbeIO (pVideo=0x1c7dbe0, pATI=0x1c74110) at atiprobe.c:454
#3  0xb75639c7 in ATIPreInit (pScreenInfo=0x1c83940, flags=0) at 
atipreinit.c:644
#4  0x00607ab7 in InitOutput (pScreenInfo=pScreenInfo@entry=0x707300 
, argc=argc@entry=1, argv=argv@entry=0xbfa90e44) at 
../xorg-server-21.1.8/hw/xfree86/common/xf86Init.c:478
#5  0x004fd765 in dix_main (argc=, argc@entry=1, argv=, argv@entry=0xbfa90e44, envp=, envp@entry=0xbfa90e4c) at 
../xorg-server-21.1.8/dix/main.c:190
#6  0x004ba84e in main (argc=1, argv=0xbfa90e44, envp=0xbfa90e4c) at 
../xorg-server-21.1.8/dix/stubmain.c:34
(gdb) list
138        }
139    
140    #endif /* AVOID_CPIO */
141    
142        /* Make sure any Mach64 is not in some weird state */
143        bus_cntl = inr(BUS_CNTL);
144        if (Chip < ATI_CHIP_264VTB)
145            outr(BUS_CNTL,
146                (bus_cntl & ~(BUS_HOST_ERR_INT_EN | BUS_FIFO_ERR_INT_EN)) |
147                (BUS_HOST_ERR_INT | BUS_FIFO_ERR_INT));

Can anything be deduced from this? What other information is of interest? Any 
suggestions are welcome.

Regards
Morgan Wesström
  

MACH64: Caught signal 11 (Segmentation fault)

[Morgan Wesström]

Dear list,

This is a small hobby project of mine so it's no big deal if it can't be 
resolved but I don't mind digging a little deeper into it myself if I can only 
get a few pointers.

I've been a Gentoo Linux user for 15+ years so I'm fairly confident in 
compiling things in various ways but I'm no C programmer and definitely don't 
have the deep technical knowledge needed to create device drivers.

With that said, I needed a challenge and went on to install Gentoo on the 
oldest machine still in my possession - a 22 year old laptop with a 32-bit 
Pentium III Celeron. It's quite restricted hardware wise (maxed out RAM is 
196MB) but I got it running. I even made Xorg run with the generic fbdev driver 
but was hoping to unlock at least some 2D acceleration.

The video card is an ATI Rage Mobility AGP 2x Series (1002:4c4d) and after some 
digging I understood that this was a mach64 card. Driver is included and 
activated in my kernel (atyfb, Linux 6.1.19) but I also needed 
xf86-video-mach64 for Xorg. Unfortunately that driver seems to have been ripped 
out of the main tree around 2010 or so but apparently it's still maintained and 
version 6.9.7 was released last year.

I downloaded it from 
https://gitlab.freedesktop.org/xorg/driver/xf86-video-mach64.git, compiled and 
installed it but X segfaults with a signal 11 when I try to use it. I've 
compiled it with debug symbols so I can get a proper backtrace but after that 
I'm stuck. I don't know what the driver is doing or what it's supposed to do at 
this point.

Here's some info from the debugger:

Program received signal SIGSEGV, Segmentation fault.
ATIMach64Detect (Chip=77, ChipType=19533, pATI=0x1c74110) at atiprobe.c:143
143 bus_cntl = inr(BUS_CNTL);
(gdb) bt
#0  ATIMach64Detect (Chip=77, ChipType=19533, pATI=0x1c74110) at atiprobe.c:143
#1  ATIMach64Probe (Chip=77, pVideo=0x1c7dbe0, pATI=0x1c74110) at atiprobe.c:278
#2  ATIMach64ProbeIO (pVideo=0x1c7dbe0, pATI=0x1c74110) at atiprobe.c:454
#3  0xb75639c7 in ATIPreInit (pScreenInfo=0x1c83940, flags=0) at 
atipreinit.c:644
#4  0x00607ab7 in InitOutput (pScreenInfo=pScreenInfo@entry=0x707300 
, argc=argc@entry=1, argv=argv@entry=0xbfa90e44) at 
../xorg-server-21.1.8/hw/xfree86/common/xf86Init.c:478
#5  0x004fd765 in dix_main (argc=, argc@entry=1, argv=, 
argv@entry=0xbfa90e44, envp=, envp@entry=0xbfa90e4c) at 
../xorg-server-21.1.8/dix/main.c:190
#6  0x004ba84e in main (argc=1, argv=0xbfa90e44, envp=0xbfa90e4c) at 
../xorg-server-21.1.8/dix/stubmain.c:34
(gdb) list
138 }
139 
140 #endif /* AVOID_CPIO */
141 
142 /* Make sure any Mach64 is not in some weird state */
143 bus_cntl = inr(BUS_CNTL);
144 if (Chip < ATI_CHIP_264VTB)
145 outr(BUS_CNTL,
146  (bus_cntl & ~(BUS_HOST_ERR_INT_EN | BUS_FIFO_ERR_INT_EN)) |
147  (BUS_HOST_ERR_INT | BUS_FIFO_ERR_INT));

Can anything be deduced from this? What other information is of interest? Any 
suggestions are welcome.

Regards
Morgan Wesström

Re: Segmentation fault on XpmCreateImageFromData(3)

[Matthieu Herrb]

On Thu, Mar 25, 2021 at 06:28:40PM +0100, Matthieu Herrb wrote:
> On Wed, Mar 24, 2021 at 08:12:34PM -0300, Phillip Bushee wrote:
> > I'm am writing a window manager which uses XpmCreateImageFromData(3)
> > to read a .xpm file containing the theme of the decoration of the
> > windows.  The program segfaults when calling this function.  I use this
> > function rather than XpmCreatePixmapFromData(3) in order for me to get
> > a pixel color from the .xpm with XGetPixel(3).
> 
> Hi,
> 
> I've the impression that this is happening because xa->valuemask is
> being used unitialized in libXpm in the way you're calling it.

PS : I forgot to mention that this is mentionned in xpm.PS.gz page 14:

  NOTE: In any case the XpmAttributes valuemask must be set to some
  valid value, at least zero, otherwise unpredictable errors can
  occur.


> 
> This seems to fix the crash for me:
> 
> diff --git shod.c shod.c
> index 5dcb450..26865d7 100644
> --- shod.c
> +++ shod.c
> @@ -467,6 +467,7 @@ settheme(void)
>   unsigned int i, j;
>   int status;
>  
> + memset(, 0, sizeof(xa));
>   if (config.theme_path)  /* if the we have specified a file, read it 
> instead */
>   status = XpmReadFileToImage(dpy, config.theme_path, , NULL, 
> );
>   else/* else use the default theme */
> 
> > 
> > This is the code of the window manager:
> > https://github.com/phillbush/shod/blob/master/shod.c
> > 
> > This is the .xpm I am reading:
> > https://github.com/phillbush/shod/blob/master/theme.xpm
> > 
> > This is what I get running the program under gdb.
> > 
> > GNU gdb 6.3
> > Copyright 2004 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you
> > are
> > welcome to change it and/or distribute copies of it under certain
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for 
> > details.
> > This GDB was configured as "amd64-unknown-openbsd6.8"...
> > (gdb) run
> > Starting program: /home/phil/proj/shod/shod
> > Error while reading shared library symbols:
> > Dwarf Error: wrong version in compilation unit header (is 4, should be 
> > 2)
> > [in module /usr/libexec/ld.so]
> > Error while reading shared library symbols:
> > Dwarf Error: wrong version in compilation unit header (is 4, should be 
> > 2)
> > [in module /usr/libexec/ld.so]
> > Error while reading shared library symbols:
> > Dwarf Error: wrong version in compilation unit header (is 4, should be 
> > 2)
> > [in module /usr/libexec/ld.so]
> > Error while reading shared library symbols:
> > Dwarf Error: wrong version in compilation unit header (is 4, should be 
> > 2)
> > [in module /usr/libexec/ld.so]
> > Error while reading shared library symbols:
> > Dwarf Error: wrong version in compilation unit header (is 4, should be 
> > 2)
> > [in module /usr/libexec/ld.so]
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x7f7f2600 in ?? ()
> > (gdb) bt
> > #0  0x7f7f2600 in ?? ()
> > #1  0x0960a406b734 in SetColor () from /usr/X11R6/lib/libXpm.so.9.0
> > #2  0x0960a4067ce6 in CreateColors () from 
> > /usr/X11R6/lib/libXpm.so.9.0
> > #3  0x0960a4069916 in xpmParseDataAndCreate () from
> > /usr/X11R6/lib/libXpm.so.9.0
> > #4  0x0960a4065437 in XpmCreateImageFromData () from
> > /usr/X11R6/lib/libXpm.so.9.0
> > #5  0x095e5e85f5db in settheme () at shod.c:473
> > #6  0x095e5e85bb58 in main () at shod.c:3465
> > 
> > I'm running OpenBSD Xenocara.
> > This is what I get running `X -version`:
> > 
> > X.Org X Server 1.20.8
> > X Protocol Version 11, Revision 0
> > Build Operating System: OpenBSD 6.8 amd64
> > Current Operating System: OpenBSD thinkbsd.my.domain 6.8 GENERIC.MP#5 
> > amd64
> > Build Date: 24 November 2020  06:57:35AM
> > 
> > Current version of pixman: 0.38.4
> > Before reporting problems, check http://wiki.x.org
> > to make sure that you have the latest version.
> > 
> > ___
> > xorg@lists.x.org: X.Org support
> > Archives: http://lists.freedesktop.org/archives/xorg
> > Info: https://lists.x.org/mailman/listinfo/xorg
> > Your subscription address: %(user_address)s
> 
> -- 
> Matthieu Herrb

-- 
Matthieu Herrb
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Segmentation fault on XpmCreateImageFromData(3)

[Matthieu Herrb]

On Wed, Mar 24, 2021 at 08:12:34PM -0300, Phillip Bushee wrote:
> I'm am writing a window manager which uses XpmCreateImageFromData(3)
> to read a .xpm file containing the theme of the decoration of the
> windows.  The program segfaults when calling this function.  I use this
> function rather than XpmCreatePixmapFromData(3) in order for me to get
> a pixel color from the .xpm with XGetPixel(3).

Hi,

I've the impression that this is happening because xa->valuemask is
being used unitialized in libXpm in the way you're calling it.

This seems to fix the crash for me:

diff --git shod.c shod.c
index 5dcb450..26865d7 100644
--- shod.c
+++ shod.c
@@ -467,6 +467,7 @@ settheme(void)
unsigned int i, j;
int status;
 
+   memset(, 0, sizeof(xa));
if (config.theme_path)  /* if the we have specified a file, read it 
instead */
status = XpmReadFileToImage(dpy, config.theme_path, , NULL, 
);
else/* else use the default theme */

> 
> This is the code of the window manager:
>   https://github.com/phillbush/shod/blob/master/shod.c
> 
> This is the .xpm I am reading:
>   https://github.com/phillbush/shod/blob/master/theme.xpm
> 
> This is what I get running the program under gdb.
> 
>   GNU gdb 6.3
>   Copyright 2004 Free Software Foundation, Inc.
>   GDB is free software, covered by the GNU General Public License, and you
> are
>   welcome to change it and/or distribute copies of it under certain
> conditions.
>   Type "show copying" to see the conditions.
>   There is absolutely no warranty for GDB.  Type "show warranty" for 
> details.
>   This GDB was configured as "amd64-unknown-openbsd6.8"...
>   (gdb) run
>   Starting program: /home/phil/proj/shod/shod
>   Error while reading shared library symbols:
>   Dwarf Error: wrong version in compilation unit header (is 4, should be 
> 2)
> [in module /usr/libexec/ld.so]
>   Error while reading shared library symbols:
>   Dwarf Error: wrong version in compilation unit header (is 4, should be 
> 2)
> [in module /usr/libexec/ld.so]
>   Error while reading shared library symbols:
>   Dwarf Error: wrong version in compilation unit header (is 4, should be 
> 2)
> [in module /usr/libexec/ld.so]
>   Error while reading shared library symbols:
>   Dwarf Error: wrong version in compilation unit header (is 4, should be 
> 2)
> [in module /usr/libexec/ld.so]
>   Error while reading shared library symbols:
>   Dwarf Error: wrong version in compilation unit header (is 4, should be 
> 2)
> [in module /usr/libexec/ld.so]
> 
>   Program received signal SIGSEGV, Segmentation fault.
>   0x7f7f2600 in ?? ()
>   (gdb) bt
>   #0  0x7f7f2600 in ?? ()
>   #1  0x0960a406b734 in SetColor () from /usr/X11R6/lib/libXpm.so.9.0
>   #2  0x0960a4067ce6 in CreateColors () from 
> /usr/X11R6/lib/libXpm.so.9.0
>   #3  0x0960a4069916 in xpmParseDataAndCreate () from
> /usr/X11R6/lib/libXpm.so.9.0
>   #4  0x0960a4065437 in XpmCreateImageFromData () from
> /usr/X11R6/lib/libXpm.so.9.0
>   #5  0x095e5e85f5db in settheme () at shod.c:473
>   #6  0x095e5e85bb58 in main () at shod.c:3465
> 
> I'm running OpenBSD Xenocara.
> This is what I get running `X -version`:
> 
>   X.Org X Server 1.20.8
>   X Protocol Version 11, Revision 0
>   Build Operating System: OpenBSD 6.8 amd64
>   Current Operating System: OpenBSD thinkbsd.my.domain 6.8 GENERIC.MP#5 
> amd64
>   Build Date: 24 November 2020  06:57:35AM
> 
>   Current version of pixman: 0.38.4
>   Before reporting problems, check http://wiki.x.org
>   to make sure that you have the latest version.
> 
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s

-- 
Matthieu Herrb
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Segmentation fault on XpmCreateImageFromData(3)

[Phillip Bushee]

I'm am writing a window manager which uses XpmCreateImageFromData(3)
to read a .xpm file containing the theme of the decoration of the
windows.  The program segfaults when calling this function.  I use this
function rather than XpmCreatePixmapFromData(3) in order for me to get
a pixel color from the .xpm with XGetPixel(3).

This is the code of the window manager:
https://github.com/phillbush/shod/blob/master/shod.c

This is the .xpm I am reading:
https://github.com/phillbush/shod/blob/master/theme.xpm

This is what I get running the program under gdb.

GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
	GDB is free software, covered by the GNU General Public License, and 
you are
	welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.
	There is absolutely no warranty for GDB.  Type "show warranty" for 
details.

This GDB was configured as "amd64-unknown-openbsd6.8"...
(gdb) run
Starting program: /home/phil/proj/shod/shod
Error while reading shared library symbols:
	Dwarf Error: wrong version in compilation unit header (is 4, should be 
2) [in module /usr/libexec/ld.so]

Error while reading shared library symbols:
	Dwarf Error: wrong version in compilation unit header (is 4, should be 
2) [in module /usr/libexec/ld.so]

Error while reading shared library symbols:
	Dwarf Error: wrong version in compilation unit header (is 4, should be 
2) [in module /usr/libexec/ld.so]

Error while reading shared library symbols:
	Dwarf Error: wrong version in compilation unit header (is 4, should be 
2) [in module /usr/libexec/ld.so]

Error while reading shared library symbols:
	Dwarf Error: wrong version in compilation unit header (is 4, should be 
2) [in module /usr/libexec/ld.so]


Program received signal SIGSEGV, Segmentation fault.
0x7f7f2600 in ?? ()
(gdb) bt
#0  0x7f7f2600 in ?? ()
#1  0x0960a406b734 in SetColor () from /usr/X11R6/lib/libXpm.so.9.0
	#2  0x0960a4067ce6 in CreateColors () from 
/usr/X11R6/lib/libXpm.so.9.0
	#3  0x0960a4069916 in xpmParseDataAndCreate () from 
/usr/X11R6/lib/libXpm.so.9.0
	#4  0x0960a4065437 in XpmCreateImageFromData () from 
/usr/X11R6/lib/libXpm.so.9.0

#5  0x095e5e85f5db in settheme () at shod.c:473
#6  0x095e5e85bb58 in main () at shod.c:3465

I'm running OpenBSD Xenocara.
This is what I get running `X -version`:

X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 6.8 amd64
	Current Operating System: OpenBSD thinkbsd.my.domain 6.8 GENERIC.MP#5 
amd64

Build Date: 24 November 2020  06:57:35AM

Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

[Bug 102884] Xorg + Radeon = Segmentation fault at address 0x0

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102884

Martin Peres  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEEDINFO|RESOLVED

--- Comment #2 from Martin Peres  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/176.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 100751] Radeon HD 7770 - No Screens - DRM Error Failed to open, invalid argument - Segmentation Fault 0x50

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=100751

Martin Peres  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #2 from Martin Peres  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/171.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=109680

--- Comment #5 from toberepla...@gmail.com ---
Thank you for all of the help. I have come to a resolution based on your hunch
about removing Screen lines in the device sections.

The segmentation fault appears to occur if there is no "Screen 0" for a given
BusID. The core misunderstanding was that the screen number in the ServerLayout
section is *not* related to the screen number in the Device section.

My comment about ZaphodHeads was because I originally had a third screen based
off of the second bus id, but I removed it from the configuration since it was
not required to cause a Segmentation Fault. My end goal was display :0.0 on one
card, :0.1 on another card, and :0.2 on that second card.

A working configuration, with comments for the "surprises" I had is below, in
case it is useful for anyone in the future or for improving existing
documentaiton.

Section "ServerLayout" 
Identifier "Example" 
Screen 0 "A" 
Screen 1 "B" 
Screen 2 "C" 
EndSection 

Section "Device" 
Identifier "A Card" 
Driver "modesetting" 
Screen 0 
BusID "PCI:16@0:0:0" 
Option "kmsdev" "/dev/dri/card1"
Option "Monitor-DVI-D-1" 
EndSection 

Section "Monitor" 
Identifier "A Monitor" 
EndSection 

Section "Screen" 
Identifier "A" 
Device "A Card" 
Monitor "A Monitor" 
EndSection 

Section "Device" 
Identifier "B Card" 
Driver "modesetting" 
Screen 0 # 1st screen for bus, 2nd screen in layout
BusID "PCI:56@0:0:0" 
Option "kmsdev" "/dev/dri/card0"
Option "Monitor-HDMI-1" 
EndSection 

Section "Monitor" 
Identifier "B Monitor" 
EndSection 

Section "Screen" 
Identifier "B" 
Device "B Card" 
Monitor "B Monitor" 
EndSection 

Section "Device"
Identifier "C Card"
Driver "modesetting"
Screen 1 # 2nd screen for bus, 3rd screen in layout
BusID "PCI:56@0:0:0"
Option "kmsdev" "/dev/dri/card0"
Option "Monitor-HDMI-2"
Option "ZaphodHeads" "HDMI-2"
EndSection

Section "Monitor"
Identifier "C Monitor"
EndSection

Section "Screen"
Identifier "C"
Device "C Card"
Monitor "C Monitor"
EndSection

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=109680

--- Comment #4 from Michel Dänzer  ---
(In reply to ToBeReplaced from comment #3)
> Thank you for the quick reply. I'll post an issue there, then close this one.

This one's already resolved, no need to close it.


> Removing the Screen sections does not help, unfortunately.

That's not what I mean. I mean the

 Screen 0/1

stanzas in Section "Device".


> The end goal is to use it with ZaphodHeads actually, so when moving the issue
> I'll include the ZaphodHeads lines and a log with those included.

Like the Screen stanza, Option "ZaphodHeads" is (as the name suggests) only
relevant with a Zaphod configuration, not with a single screen per GPU as in
your case.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=109680

--- Comment #3 from toberepla...@gmail.com ---
Thank you for the quick reply. I'll post an issue there, then close this one.

Removing the Screen sections does not help, unfortunately. I'll post another
log in a bit. The end goal is to use it with ZaphodHeads actually, so when
moving the issue I'll include the ZaphodHeads lines and a log with those
included.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=109680

Michel Dänzer  changed:

   What|Removed |Added

 Resolution|--- |NOTOURBUG
 Status|NEW |RESOLVED

--- Comment #2 from Michel Dänzer  ---
modesetting driver issues need to be reported at
https://gitlab.freedesktop.org/xorg/xserver/issues/new .

That said, does removing the Screen stanzas from Section "Device" help? That is
for a so-called "Zaphod" configuration with multiple "Device" and "Screen"
sections for the same GPU.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=109680

--- Comment #1 from toberepla...@gmail.com ---
Whoops, forgot to add that I attempted to receive support through #xorg on
freenode (no responses), then later at
https://superuser.com/questions/1406211/xorg-multi-card-modesetting-configuration-segmentation-fault
(no answers). If this is not the appropriate channel for escalation please let
me know where would be more appropriate.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 109680] New: Multiple cards with modesetting results in Segmentation Fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=109680

Bug ID: 109680
   Summary: Multiple cards with modesetting results in
Segmentation Fault
   Product: xorg
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: Driver/AMDgpu
  Assignee: xorg-driver-ati@lists.x.org
  Reporter: toberepla...@gmail.com
QA Contact: xorg-t...@lists.x.org

I am attempting to use modesetting with the following two devices, one AGPU,
one Graphics Card. Both cards are working fine if the configuration is modified
to omit the other.

10:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Caicos PRO [Radeon HD 7450] (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 212f
Flags: bus master, fast devsel, latency 0, IRQ 320
Memory at e000 (64-bit, prefetchable) [size=256M]
Memory at fe92 (64-bit, non-prefetchable) [size=128K]
I/O ports at f000 [size=256]
Expansion ROM at fe90 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010

Capabilities: [150] Advanced Error Reporting
Kernel driver in use: radeon
Kernel modules: radeon


38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven
Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) (prog-if 00
[VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon
Vega Series / Radeon Vega Mobile Series]
Flags: bus master, fast devsel, latency 0, IRQ 57
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=2M]
I/O ports at d000 [size=256]
Memory at fe40 (32-bit, non-prefetchable) [size=512K]
Expansion ROM at  [disabled]
Capabilities: [48] Vendor Specific Information: Len=08 
Capabilities: [50] Power Management version 3
Capabilities: [64] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/4 Maskable- 64bit+
Capabilities: [c0] MSI-X: Enable- Count=3 Masked-
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010

Capabilities: [200] #15
Capabilities: [270] #19
Capabilities: [2a0] Access Control Services
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] Page Request Interface (PRI)
Capabilities: [2d0] Process Address Space ID (PASID)
Capabilities: [320] Latency Tolerance Reporting
Kernel driver in use: amdgpu
Kernel modules: amdgpu

Configuration:

Section "ServerLayout" 
Identifier "Example" 
Screen 0 "A" 
Screen 1 "B" 
EndSection 

Section "Device" 
Identifier "A Card" 
Driver "modesetting" 
Screen 0 
BusID "PCI:16@0:0:0" 
Option "kmsdev" "/dev/dri/card1" 
Option "Monitor-DVI-D-1" 
EndSection 

Section "Monitor" 
Identifier "A Monitor" 
EndSection 

Section "Screen" 
Identifier "A" 
Device "A Card" 
Monitor "A Monitor" 
EndSection 

Section "Device" 
Identifier "B Card" 
Driver "modesetting" 
Screen 1 
BusID "PCI:56@0:0:0" 
Option "kmsdev" "/dev/dri/card0" 
Option "Monitor-HDMI-1" 
EndSection 

Section "Monitor" 
Identifier "B Monitor" 
EndSection 

Section "Screen" 
Identifier "B" 
Device "B Card" 
Monitor "B Monitor" 
EndSection 

Xorg.log.0:

X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
[430291.775] Build Operating System:  3.10.0-693.17.1.el7.x86_64 
[430291.775] Current Operating System: Linux localhost.localdomain
3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64
[430291.775] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-957.5.1.el7.x86_64
root=/dev/mapper/centos_localhost-root ro crashkernel=auto
rd.lvm.lv=centos_localhost/root rd.lvm.lv=centos_localhost/swap rhgb qui
et
[430291.776] Build Date: 29 January 2019  06:03:26PM
[430291.776] Build ID: xorg-x11-server 1.20.1-5.2.el7_6 
[430291.776] Current version of pixman: 0.34.0
[430291.776]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[430291.776] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (

Bug#910846: X server "Segmentation fault at address 0x0" when using about:support in Firefox-based browsers.

[Michel Dänzer]

On 2018-10-12 6:40 a.m., Gong S. wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:18.1.0-1
> 
> I am using a standalone AMD HD 7670. "firmware-amd-graphics" is installed and 
> loaded during boot.
> It seems that whenever I tries to query information about hardware 
> acceleration, X segfaults.
> "dmesg" does not show any error or warning after segfault.
> Sometimes other programs or games trigger it as well, with the same problem 
> described in the file Xorg.0.log.

[...]

> [   324.504] (EE) Backtrace:
> [   324.505] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x562764468de9]
> [   324.505] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) 
> [0x7f100883292f]
> [   324.506] (EE) 2: /usr/lib/xorg/modules/drivers/radeon_drv.so 
> (_init+0x1592) [0x7f10073d4b24]
> [   324.506] (EE) 3: /usr/lib/xorg/Xorg (dri3_send_open_reply+0x55d) 
> [0x562764438b4d]
> [   324.506] (EE) 4: /usr/lib/xorg/Xorg (drm_format_for_depth+0x93b) 
> [0x56276443827b]
> [   324.506] (EE) 5: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) 
> [0x56276430a97e]
> [   324.506] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x56276430e906]
> [   324.506] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
> [0x7f1008683b17]
> [   324.506] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2a) [0x5627642f867a]
> [   324.506] (EE) 
> [   324.506] (EE) Segmentation fault at address 0x0

Please make sure the xserver-xorg-video-radeon-dbgsym and
xserver-xorg-core-dbgsym packages are installed, and either get a
backtrace with gdb or another log file.


Does the problem also happen without Option "AccelMethod" "EXA"? That's
the default and recommended configuration for your GPU.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

Bug#910846: X server "Segmentation fault at address 0x0" when using about:support in Firefox-based browsers.

[Gong S.]

 Applying InputClass "My Mouse"
[   303.641] (II) No input driver specified, ignoring this device.
[   303.641] (II) This device may have been added with another device file.
[   303.641] (II) config/udev: Adding input device HID 0430:0005 (/dev/input/event2)
[   303.641] (**) HID 0430:0005: Applying InputClass "evdev keyboard catchall"
[   303.641] (II) Using input driver 'evdev' for 'HID 0430:0005'
[   303.641] (**) HID 0430:0005: always reports core events
[   303.641] (**) evdev: HID 0430:0005: Device: "/dev/input/event2"
[   303.642] (--) evdev: HID 0430:0005: Vendor 0x430 Product 0x5
[   303.642] (--) evdev: HID 0430:0005: Found keys
[   303.642] (II) evdev: HID 0430:0005: Configuring as keyboard
[   303.642] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:0430:0005.0004/input/input5/event2"
[   303.642] (II) XINPUT: Adding extended input device "HID 0430:0005" (type: KEYBOARD, id 12)
[   303.642] (**) Option "xkb_rules" "evdev"
[   303.642] (**) Option "xkb_model" "sun_type6_usb"
[   303.642] (**) Option "xkb_layout" "us"
[   303.642] (**) Option "xkb_options" "compose:rwin,terminate:ctrl_alt_bksp"
[   303.642] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
[   303.642] (II) No input driver specified, ignoring this device.
[   303.642] (II) This device may have been added with another device file.
[   303.643] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event8)
[   303.643] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[   303.643] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[   303.643] (**) HP WMI hotkeys: always reports core events
[   303.643] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event8"
[   303.643] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[   303.643] (--) evdev: HP WMI hotkeys: Found keys
[   303.643] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[   303.643] (**) Option "config_info" "udev:/sys/devices/virtual/input/input11/event8"
[   303.643] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 13)
[   303.643] (**) Option "xkb_rules" "evdev"
[   303.643] (**) Option "xkb_model" "sun_type6_usb"
[   303.643] (**) Option "xkb_layout" "us"
[   303.643] (**) Option "xkb_options" "compose:rwin,terminate:ctrl_alt_bksp"
[   324.504] (EE) 
[   324.504] (EE) Backtrace:
[   324.505] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x562764468de9]
[   324.505] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f100883292f]
[   324.506] (EE) 2: /usr/lib/xorg/modules/drivers/radeon_drv.so (_init+0x1592) [0x7f10073d4b24]
[   324.506] (EE) 3: /usr/lib/xorg/Xorg (dri3_send_open_reply+0x55d) [0x562764438b4d]
[   324.506] (EE) 4: /usr/lib/xorg/Xorg (drm_format_for_depth+0x93b) [0x56276443827b]
[   324.506] (EE) 5: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) [0x56276430a97e]
[   324.506] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x56276430e906]
[   324.506] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f1008683b17]
[   324.506] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2a) [0x5627642f867a]
[   324.506] (EE) 
[   324.506] (EE) Segmentation fault at address 0x0
[   324.506] (EE) 
Fatal server error:
[   324.506] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   324.506] (EE) 
[   324.506] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   324.506] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   324.506] (EE) 
[   324.506] (II) AIGLX: Suspending AIGLX clients for VT switch
[   324.512] (EE) Server terminated with error (1). Closing log file.


Xorg.0.log.sig
Description: PGP signature
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11"
FontPath "built-ins"
EndSection
Section "Device"
Identifier "Card0"
Driver "radeon"
BusID "PCI:1:0:0"
Option "ColorTiling" "on"
Option "ColorTiling2D" "on"
Option "DRI" "3"
Option "EnablePageFlip" "on"
Option "AccelMethod" "EXA"
Option "AccelDFS" "1"
Option "GARTSize" "64"
EndSection
Section "InputClass"
Identifier "My Mouse"
MatchIsPointer "yes"
Option "AccelerationNumerator" "4"
Option "AccelerationDenominator" "1"
Option "AccelerationThreshold" "10"
EndSection


xorg.conf.sig
Description: PGP signature


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Xorg-driver-geode] [Bug 107422] New: Segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=107422

Bug ID: 107422
   Summary: Segmentation fault
   Product: xorg
   Version: unspecified
  Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
  Severity: major
  Priority: medium
 Component: Driver/geode
  Assignee: xorg-driver-geode@lists.x.org
  Reporter: sad@gmail.com
QA Contact: xorg-driver-geode@lists.x.org

Created attachment 140878
  --> https://bugs.freedesktop.org/attachment.cgi?id=140878=edit
log with segfault

After update Debian 9 to 10.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
Xorg-driver-geode mailing list
Xorg-driver-geode@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-geode

[Bug 50441] Segmentation fault in Xorg Server version 1.12.1.902

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=50441

Adam Jackson  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED

--- Comment #2 from Adam Jackson  ---
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you
continue to experience issues with current releases.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

Re: segmentation fault

[sawbona]

Hello:

On 8 Jan 2018 at 11:55, François Patte wrote:

> I try to install a multihead config with 2 video cards and 3 monitors,
> using xinerama in order to have a unique screen.

I'll see if I can help you with this.

I am running PCLinuxOS:
4.12.10-pclos1 #1 SMP Wed Aug 30 08:17:56 CDT 2017 x86_64 x86_64 x86_64 
GNU/Linux

The desktop is MATE and I use two Nvidia video cards and three monitors,.but I 
do not use the 
Nouveau drivers.

The driver I use is the is NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 
14 17:13:13 
PDT 2017 and Xinerama.

The installed cards are Quadro FX 370 and Quadro FX 580.

Here's my xorg.conf for this setup.
Some of the commented sections are for my control.

---

# Revision 10
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 340.104  (tex@localhost.localdomain)  Tue Oct  3 
03:43:15 CDT 2017

# File generated by XFdrake (rev 262502)

# **
# Refer to the xorg.conf man page for details about the format of
# this file.
# **
# ---
#
# xorg.conf modified by CIV 20171016 for two Nvidia cards and three monitors
# First slot: Quadro FX 370 - Second slot: Quadro FX 580
# See http://www.instructables.com/id/How-to-set-up-multiple-monitors-in-linux/
# See https://gist.github.com/mikaelj/5884579
#
# Cards and bus addresses output from lspci
# 01:00.0 VGA compatible controller: NVIDIA Corporation G84GL [Quadro FX 370] 
(rev a1)
# 02:00.0 VGA compatible controller: NVIDIA Corporation G96GL [Quadro FX 580] 
(rev a1)
#
# Physical layout
#  _  __ __  
# | || || |
# |  Screen 0  ||  Screen 1  ||  Screen 2  |
# |   19" SM   ||  19" Dell||   19" SM   | 
# |___ __||__ ___||__ ___|
#
# ---

Section "ServerLayout"
Identifier"layout0"

Screen   0"ScreenLeft" LeftOf "ScreenCenter"
Screen   1"ScreenCenter" 0 0
Screen   2"ScreenRight" RightOf "ScreenCenter"
Option"Xinerama" "1"
EndSection

Section "Extensions"
#Option "Composite" "0"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "Monitor"

Identifier "Monitor0"
VendorName "Samsung"
ModelName  "Samsung SyncMaster 940N"
Option "DPMS" 
EndSection

Section "Monitor"

Identifier "Monitor1"
VendorName "Dell"
ModelName  "Dell P1914S"
Option "DPMS" 
EndSection

Section "Monitor"

Identifier "Monitor2"
VendorName "Samsung"
ModelName  "Samsung SyncMaster 940N"
Option "DPMS"
EndSection

Section "Device"
Identifier "DeviceLeft" #card 1
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "NVIDIA GeForce 8100 to GeForce 415" #NVIDIA G84GL Quadro FX 370
BusID  "PCI:1:0:0"
Screen  0
EndSection

Section "Device"
Identifier "DeviceCenter"   #card 2
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "NVIDIA GeForce 8100 to GeForce 415" #NVIDIA G96GL Quadro FX 580
BusID  "PCI:2:0:0"
EndSection

Section "Device"
Identifier "DeviceRight"#card 1
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "NVIDIA GeForce 8100 to GeForce 415" #NVIDIA G84GL Quadro FX 370
BusID  "PCI:1:0:0"
Screen  1
EndSection

Section "Screen"
Identifier "ScreenLeft"
Device "DeviceLeft"
Monitor"Monitor0"
DefaultDepth24
Option "DPMS"
SubSection "Display"
Depth   24
Modes  "1280x1024" "1024x768"
EndSubSection
EndSection

Section "Screen"
Identifier "ScreenCenter"
Device "DeviceCenter"
Monitor"Monitor1"
DefaultDepth24
Option "DPMS"
SubSection "Display"
Depth   24
Modes  "1280x1024" "1024x768"
EndSubSection
EndSection

Section "Screen"
Identifier "ScreenRight"
Device "DeviceRight"
Monitor"Monitor2"
DefaultDepth24
Option "DPMS"
SubSection "Display"
Depth   24
Modes  "1280x1024" "1024x768"
EndSubSection
EndSection

Section "Module"
Load   "v4l" # Video for Linux
EndSection

Section "ServerFlags"

Option "allowmouseopenfail" "False"  # default False allows server to start 
even if without 
mouse
Option "DontZap" "False" # default False  disables 
 (server abort)
Option "DontZoom" "False"# default False disables 
/ 
(resolution switching)
Option "AllowEmptyInput" "False" # default True if 

segmentation fault

[François Patte]

Bonjour,

I try to install a multihead config with 2 video cards and 3 monitors,
using xinerama in order to have a unique screen.

But this does not work and end with a segmentation fault Here are
the xorg.conf file and the corresponding log file.

Thank you for helping.


Here is my xorg.conf:

<-xorg.conf-
# essai xinerama

Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0" 0 0
Screen  1  "Screen1" RightOf "Screen0"
Screen  2  "Screen2" RightOf "Screen1"
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection

Section "Files"
FontPath"/usr/share/fonts/default/Type1"
EndSection

Section "Module"
Load   "dbe"
Load   "extmod"
Load   "type1"
Load   "freetype"
Load   "glx"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "LG"
ModelName  "LG Electronics L1952TQ"
HorizSync   30.0 - 71.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection

Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor1"
VendorName "LG"
ModelName  "LG Electronics L1952TQ"
HorizSync   30.0 - 71.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection

Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor2"
VendorName "LG"
ModelName  "LG Electronics L1920P"
HorizSync   30.0 - 71.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nouveau"
BusId  "PCI:1:0:0"
VendorName "NVIDIA Corporation"
BoardName  "GeForce 8800 GT"
Screen 0
EndSection

Section "Device"
Identifier "Device1"
Driver "nouveau"
BusId  "PCI:1:0:0"
VendorName "NVIDIA Corporation"
BoardName  "GeForce 8800 GT"
Screen 1
EndSection

Section "Device"
Identifier  "intel0"
Driver  "intel"
BusId   "PCI:0:2:0"
VendorName  "Intel Corporation"
BoardName   "Xeon E3-1200 v2/3rd Gen Core processor Graphics
Controller"
Screen  0
#Option  "AccelMethod" "uxa"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
#Option "Stereo" "0"
#Option "nvidiaXineramaInfoOrder" "DFP-0"
#Option "metamodes" "DVI-I-2: nvidia-auto-select +0+0,
DVI-I-3: nvidia-auto-select +1280+0"
#Option "SLI" "Off"
#Option "MultiGPU" "Off"
#Option "BaseMosaic" "off"
SubSection "Display"
Depth   24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor"Monitor1"
DefaultDepth24
#Option "Stereo" "0"
#Option "nvidiaXineramaInfoOrder" "DFP-0"
#Option "metamodes" "DVI-I-2: nvidia-auto-select +0+0,
DVI-I-3: nvidia-auto-select +1280+0"
#Option "SLI" "Off"
#Option "MultiGPU" "Off"
#Option "BaseMosaic" "off"
SubSection "Display"
Depth   24
EndSubSection
EndSection

Section "S

Re: Segmentation fault at adress 0x0 | nvidia Quadro K620M

[Hi-Angel]

To me it looks like something with Intel DDX driver. To check if it's
true try creating a file /etc/X11/xorg.conf.d/20-modesetting.conf with
content like:

Section "Device"
Identifier  "Intel Graphics"
Driver  "modesetting"
Option  "Backlight"  "intel_backlight"
EndSection

Then restart Xorg (alternatively reboot), it should stop crashing.

On 23 October 2017 at 16:12, Christoph Hollizeck
 wrote:
> Well hello there, I am kinda at the end of my wits as my Xserver broke again
> after a restart (probably apt-get upgrade again) I tried all the stuff that
> made it work last time again such as purging nvidia drivers, re-installing
> gdm3 and gnome ( I usually don't use gnome, I use i3 but I have gnome as a
> backup) I tried re-installing the xserver-xorg aswell but nothing really
> worked googling the errors didn't help either and the log file told me to
> ask the x.org support so here I am. Sadly I can't post my logfile cause
> neither my git nor dropbox is working for some reason, and I can't mount my
> /dev/sdb1 aswell otherwise I would have just reinstalled the whole system.
>
> Even tho I kinda know my way around linux I don't know what to do next I
> would really appreciate some help
>
> Best regards Chris
> --
> Sent from my phone. Please excuse my brevity.
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

[Bug 102884] Xorg + Radeon = Segmentation fault at address 0x0

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102884

Michel Dänzer  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #1 from Michel Dänzer  ---
We cannot do anything about this without information about the crash: Ideally a
gdb backtrace, but at least the corresponding Xorg log file (which may be in
~/.local/share/xorg/).

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 102884] Xorg + Radeon = Segmentation fault at address 0x0

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102884

Alex Deucher  changed:

   What|Removed |Added

 Attachment #134346|application/x-trash |text/plain
  mime type||

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 102884] New: Xorg + Radeon = Segmentation fault at address 0x0

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102884

Bug ID: 102884
   Summary: Xorg + Radeon = Segmentation fault at address 0x0
   Product: xorg
   Version: git
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: Driver/Radeon
  Assignee: xorg-driver-ati@lists.x.org
  Reporter: ielki...@outlook.com
QA Contact: xorg-t...@lists.x.org

Created attachment 134346
  --> https://bugs.freedesktop.org/attachment.cgi?id=134346=edit
Old Xorg.0.log because I've tried to find the location of it so i've made a
configure option, which failed because of socket errors.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

Re: xcb_writev: Segmentation fault

[YuGiOhJCJ Mailing-List]

OK, I found how to fix the problem: I need to use the '-O1' gcc optimization 
flag instead of '-O2' when building libxcb.
Well, in fact, it is just a workaround and not a fix because I prefer the '-O2' 
optimization flag but unfortunately I can't use it for building libxcb.
Thanks to Ilya Lipnitskiy (lipnitsk) for this idea: 
https://bugs.archlinux.org/task/49560

On Thu, 31 Aug 2017 16:54:44 +0200
YuGiOhJCJ Mailing-List <yugiohjcj-mailingl...@laposte.net> wrote:

> Hello,
> 
> I built libX11 1.6.5 32-bit on my 64-bit machine and I try to run a 32-bit 
> application:
> ---
> $ gdb 25Assist
> GNU gdb (GDB) 7.11.1
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-slackware-linux".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from 25Assist...(no debugging symbols found)...done.
> (gdb) run
> Starting program: /opt/25assist-20151223/25Assist 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> warning: File "/usr/lib/libstdc++.so.6.0.23-gdb.py" auto-loading has been 
> declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
> To enable execution of this file add
>   add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.23-gdb.py
> line to your configuration file "/home/yugiohjcj/.gdbinit".
> To completely disable this security protection add
>   set auto-load safe-path /
> line to your configuration file "/home/yugiohjcj/.gdbinit".
> For more information about this security protection see the
> "Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
>   info "(gdb)Auto-loading safe path"
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, 
> requests=73) at xcb_out.c:405
> 405   c->out.request += requests;
> (gdb) bt
> #0  0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, 
> requests=73) at xcb_out.c:405
> #1  0xf767f85e in _XSend (dpy=0x82cb400, data=0x0, size=0) at xcb_io.c:486
> #2  0xf767fe19 in _XReply (dpy=0x82cb400, rep=0x9ec4, extra=0, discard=1) 
> at xcb_io.c:573
> #3  0xf767b943 in XSync (dpy=0x82cb400, discard=0) at Sync.c:44
> #4  0xf7a537b2 in IA__gdk_flush () at gdkevents-x11.c:2606
> #5  0xf7a23170 in alloc_scratch_image (image_info=) at 
> gdkimage.c:527
> #6  _gdk_image_get_scratch (screen=0x82da0b8, width=160, height=23, depth=24, 
> x=0x9fbc, y=0x9fc0) at gdkimage.c:592
> #7  0xf7a30fbe in gdk_draw_rgb_image_core (image_info=0x83f3bf8, 
> drawable=drawable@entry=0x82c6c00, gc=gc@entry=0x82d8e80, x=0, y=0, 
> width=160, height=23, 
> buf=0x840bc48 "\371\371\371nnn\022\022\022", pixstride=3, rowstride=480, 
> conv=0xf7a2f0a0 , cmap=0x0, xdith=0, ydith=0) at 
> gdkrgb.c:3327
> #8  0xf7a329e9 in IA__gdk_draw_rgb_image (drawable=0x82c6c00, gc=0x82d8e80, 
> x=0, y=0, width=160, height=23, dith=GDK_RGB_DITHER_MAX, rgb_buf=0x840bc48 
> "\371\371\371nnn\022\022\022", 
> rowstride=480) at gdkrgb.c:3393
> #9  0x0809d97e in ?? ()
> #10 0x081124a0 in ?? ()
> #11 0x081124d5 in ?? ()
> #12 0xf6252292 in ?? ()
> #13 0xf60cf138 in ?? ()
> #14 0xf60cf3a3 in ?? ()
> #15 0xf62d3f00 in ?? ()
> #16 0xf62ceb8b in ?? ()
> #17 0x0807077d in ?? ()
> #18 0x08070888 in ?? ()
> #19 0x08179267 in ?? ()
> #20 0xf6100128 in ?? ()
> #21 0x0816d65a in ?? ()
> #22 0x0816d64e in ?? ()
> #23 0x0816d75f in ?? ()
> #24 0xf668681b in ?? ()
> #25 0xf60b5308 in ?? ()
> #26 0xf60b53b4 in ?? ()
> #27 0xf6255333 in ?? ()
> #28 0xf60b5469 in ?? ()
> #29 0xf60b5024 in ?? ()
> #30 0x080d2592 in ?? ()
> #31 0x0816c1b1 in ?? ()
> #32 0xf72be4d3 in __libc_start_main () from /lib/libc.so.6
> #33 0x08052b21 in ?? ()
> (gdb) quit
> A debugging session is active.
> 
>   Inferior 1 [process 18645] will be killed.
> 
> Quit anyway? (y or n) y
> ---
> 
> As you can see I get a segmentation fault after the call to the xcb_writev 
>

xcb_writev: Segmentation fault

[YuGiOhJCJ Mailing-List]

Hello,

I built libX11 1.6.5 32-bit on my 64-bit machine and I try to run a 32-bit 
application:
---
$ gdb 25Assist
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-slackware-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 25Assist...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/25assist-20151223/25Assist 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: File "/usr/lib/libstdc++.so.6.0.23-gdb.py" auto-loading has been 
declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.23-gdb.py
line to your configuration file "/home/yugiohjcj/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/yugiohjcj/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"

Program received signal SIGSEGV, Segmentation fault.
0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, requests=73) 
at xcb_out.c:405
405 c->out.request += requests;
(gdb) bt
#0  0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, 
requests=73) at xcb_out.c:405
#1  0xf767f85e in _XSend (dpy=0x82cb400, data=0x0, size=0) at xcb_io.c:486
#2  0xf767fe19 in _XReply (dpy=0x82cb400, rep=0x9ec4, extra=0, discard=1) 
at xcb_io.c:573
#3  0xf767b943 in XSync (dpy=0x82cb400, discard=0) at Sync.c:44
#4  0xf7a537b2 in IA__gdk_flush () at gdkevents-x11.c:2606
#5  0xf7a23170 in alloc_scratch_image (image_info=) at 
gdkimage.c:527
#6  _gdk_image_get_scratch (screen=0x82da0b8, width=160, height=23, depth=24, 
x=0x9fbc, y=0x9fc0) at gdkimage.c:592
#7  0xf7a30fbe in gdk_draw_rgb_image_core (image_info=0x83f3bf8, 
drawable=drawable@entry=0x82c6c00, gc=gc@entry=0x82d8e80, x=0, y=0, width=160, 
height=23, 
buf=0x840bc48 "\371\371\371nnn\022\022\022", pixstride=3, rowstride=480, 
conv=0xf7a2f0a0 , cmap=0x0, xdith=0, ydith=0) at 
gdkrgb.c:3327
#8  0xf7a329e9 in IA__gdk_draw_rgb_image (drawable=0x82c6c00, gc=0x82d8e80, 
x=0, y=0, width=160, height=23, dith=GDK_RGB_DITHER_MAX, rgb_buf=0x840bc48 
"\371\371\371nnn\022\022\022", 
rowstride=480) at gdkrgb.c:3393
#9  0x0809d97e in ?? ()
#10 0x081124a0 in ?? ()
#11 0x081124d5 in ?? ()
#12 0xf6252292 in ?? ()
#13 0xf60cf138 in ?? ()
#14 0xf60cf3a3 in ?? ()
#15 0xf62d3f00 in ?? ()
#16 0xf62ceb8b in ?? ()
#17 0x0807077d in ?? ()
#18 0x08070888 in ?? ()
#19 0x08179267 in ?? ()
#20 0xf6100128 in ?? ()
#21 0x0816d65a in ?? ()
#22 0x0816d64e in ?? ()
#23 0x0816d75f in ?? ()
#24 0xf668681b in ?? ()
#25 0xf60b5308 in ?? ()
#26 0xf60b53b4 in ?? ()
#27 0xf6255333 in ?? ()
#28 0xf60b5469 in ?? ()
#29 0xf60b5024 in ?? ()
#30 0x080d2592 in ?? ()
#31 0x0816c1b1 in ?? ()
#32 0xf72be4d3 in __libc_start_main () from /lib/libc.so.6
#33 0x08052b21 in ?? ()
(gdb) quit
A debugging session is active.

Inferior 1 [process 18645] will be killed.

Quit anyway? (y or n) y
---

As you can see I get a segmentation fault after the call to the xcb_writev 
function.
From this program stack, I am unable to guess what could be the problem.
Maybe a communication problem between libX11 and libxcb but why?
I was able to run this application in the past so I think I did something wrong 
when I built my 32-bit libX11 this time.

Can you guess where the problem is from this backtrace?

Thank you.
Best regards.

Remark: I rebuilt gtk+2, libX11 and libxcb with the '-g' flag to have a nice 
backtrace so that's why you see the debugging symbols.

32-bit programs used:
atk-2.20.0
cairo-1.14.10
expat-2.1.0
fontconfig-2.12.1
freetype-2.6.3
gdk-pixbuf2-2.36.6
glib2-2.52.3
glibc-2.23
gtk+2-2.24.30
harfbuzz-1.2.7
icu4c-56.1
libdrm-2.4.80
libffi-3.2.1
libjpeg-turbo-1.5.0
libpciaccess-0.13.5
libpng-1.6.25
libtiff-4.0.6
libX11-1.6.5
libXau-1.0.8
libxcb-1.12
libXcomposite-0.4.4
libXcursor-1.1.14
libXdamage-1.1.4
libXext-1.3.3
libXfixes-5.0.3
libXft-2.3.2
libXi-1.7.9
libXi

[Bug 100968] xf86-video-amdgpu-1.3.0 — Xorg: Segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=100968

Michel Dänzer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Michel Dänzer  ---
Thanks for the report, fixed in Git master:

commit e900e48a11a93cde7d8d2d7bdb4a15ec705c56b1
Author: Michel Dänzer 
Date:   Wed May 10 18:37:56 2017 +0900

Don't enable DRI3 without glamor

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 100968] xf86-video-amdgpu-1.3.0 — Xorg: Segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=100968

Floyd Anderson  changed:

   What|Removed |Added

 Attachment #131260|text/x-log  |text/plain
  mime type||

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 100968] xf86-video-amdgpu-1.3.0 — Xorg: Segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=100968

Floyd Anderson  changed:

   What|Removed |Added

 Attachment #131259|text/x-log  |text/plain
  mime type||

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 100968] xf86-video-amdgpu-1.3.0 — Xorg: Segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=100968

--- Comment #1 from Floyd Anderson <bts+freedesk...@31c0.net> ---
Created attachment 131260
  --> https://bugs.freedesktop.org/attachment.cgi?id=131260=edit
Xorg.0_segfault.log

Additionally the ‘Xorg.0.log’ file with the segmentation fault error.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 100751] Radeon HD 7770 - No Screens - DRM Error Failed to open, invalid argument - Segmentation Fault 0x50

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=100751

--- Comment #1 from Alex Deucher  ---
possibly a duplicate of bug 100673.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 100751] New: Radeon HD 7770 - No Screens - DRM Error Failed to open, invalid argument - Segmentation Fault 0x50

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=100751

Bug ID: 100751
   Summary: Radeon HD 7770 - No Screens - DRM Error Failed to
open, invalid argument - Segmentation Fault 0x50
   Product: xorg
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: Driver/Radeon
  Assignee: xorg-driver-ati@lists.x.org
  Reporter: larry_w_robe...@msn.com
QA Contact: xorg-t...@lists.x.org

Created attachment 130962
  --> https://bugs.freedesktop.org/attachment.cgi?id=130962=edit
Xorg.*.log + uname + lspci

Using Fedora 25, X windows will not start. Xorg - configure results in a
segmentation fault.  The system was working until April 18th.  On boot up, the
monitor displays graphics okay, but just as the final screen during linux boot
up completes, the screen reverts to text mode. Windows X can not be started
with startx. Using Xorg, the screen turns black and the computer must be
manually reset to regain control. I've attached the files /var/log/Xorg.*.log. 
At the end of those, I've appended uname -a , and lspci.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

Re: [Mesa-dev] UDL & Modeset with Mesa 13.0.1 - Segmentation fault

[poma]

On 18.11.2016 14:45, Emil Velikov wrote:
> On 17 November 2016 at 20:15, poma <pomidorabelis...@gmail.com> wrote:
>>
>> Airlie solved everything concerning the kernel,
>> so it seems, now it's user space turn.
>>
>> = mesa-libgbm-12.0.3 - works OK
>> ...
>> [   714.429] (II) Loading sub module "glamoregl"
>> [   714.429] (II) LoadModule: "glamoregl"
>> [   714.430] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
>> [   714.480] (II) Module glamoregl: vendor="X.Org Foundation"
>> [   714.481]compiled for 1.19.0, module version = 1.0.0
>> [   714.481]ABI class: X.Org ANSI C Emulation, version 0.4
>> ...
>> [   714.481] (II) glamor: OpenGL accelerated X.org driver based.
>> [   714.633] (II) glamor: EGL version 1.4 (DRI2):
>> [   714.633] EGL_MESA_drm_image required.
>> [   714.634] (EE) modeset(0): glamor initialization failed
>> [   714.634] (II) modeset(0): ShadowFB: preferred NO, enabled NO
>> ...
>> [   714.643] (==) Depth 24 pixmap format is 32 bpp
>> [   714.645] (==) modeset(0): Backing store enabled
>> [   714.645] (==) modeset(0): Silken mouse enabled
>> [   714.645] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR 
>> disabled message.
>> [   714.646] (==) modeset(0): DPMS enabled
>> [   714.646] (--) RandR disabled
>> [   714.669] (II) AIGLX: Screen 0 is not DRI2 capable
>> [   714.669] (EE) AIGLX: reverting to software rendering
>> [   714.683] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
>> [   714.686] (II) IGLX: Loaded and initialized swrast
>> [   714.686] (II) GLX: Initialized DRISWRAST GL provider for screen 0
>> [   714.691] (II) modeset(0): Damage tracking initialized
>> ...
>>
>> = mesa-libgbm-13.0.1 - not quite
>> ...
>> [  2324.953] (II) Loading sub module "glamoregl"
>> [  2324.953] (II) LoadModule: "glamoregl"
>> [  2324.953] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
>> [  2325.000] (II) Module glamoregl: vendor="X.Org Foundation"
>> [  2325.000]compiled for 1.19.0, module version = 1.0.0
>> [  2325.000]ABI class: X.Org ANSI C Emulation, version 0.4
>> ...
>> [  2325.001] (II) glamor: OpenGL accelerated X.org driver based.
>> [  2325.002] (EE)
>> [  2325.002] (EE) Backtrace:
>> [  2325.006] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59e389]
>> [  2325.008] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) 
>> [0x7f69d836ac2f]
>> [  2325.009] (EE) 2: /lib64/libgbm.so.1 
>> (gbm_surface_has_free_buffers+0x1505) [0x7f69d2b64685]
>> [  2325.010] (EE) 3: /lib64/libgbm.so.1 
>> (gbm_surface_has_free_buffers+0x1b98) [0x7f69d2b653b8]
>> [  2325.011] (EE) 4: /lib64/libgbm.so.1 
>> (gbm_surface_has_free_buffers+0x1498) [0x7f69d2b644c8]
>> [  2325.012] (EE) 5: /lib64/libgbm.so.1 (gbm_create_device+0x4c) 
>> [0x7f69d2b61a4c]
>> [  2325.014] (EE) 6: /usr/lib64/xorg/modules/libglamoregl.so 
>> (glamor_egl_init+0x83) [0x7f69d2d73fb3]
>> [  2325.015] (EE) 7: /usr/lib64/xorg/modules/drivers/modesetting_drv.so 
>> (_init+0x4d21) [0x7f69d2facfd1]
>> [  2325.016] (EE) 8: /usr/libexec/Xorg (InitOutput+0xa82) [0x47d6c2]
>> [  2325.017] (EE) 9: /usr/libexec/Xorg (InitFonts+0x216) [0x43ae36]
>> [  2325.020] (EE) 10: /lib64/libc.so.6 (__libc_start_main+0xf1) 
>> [0x7f69d7fb8731]
>> [  2325.022] (EE) 11: /usr/libexec/Xorg (_start+0x29) [0x424d29]
>> [  2325.024] (EE) 12: ? (?+0x29) [0x29]
>> [  2325.025] (EE)
>> [  2325.025] (EE) Segmentation fault at address 0xc
>> [  2325.025] (EE)
>> Fatal server error:
>> [  2325.025] (EE) Caught signal 11 (Segmentation fault). Server aborting
>> [  2325.026] (EE)
>> [  2325.026] (EE)
>> ...
>> [  2325.027] (EE) Server terminated with error (1). Closing log file.
>>
>>
>> A call to not load the module(s) is not at all useful:
>> Section "Module"
>> Disable  "glx"
>> Disable  "glamoregl"
>> EndSection
>>
>> ...
>> (WW) "glx" will not be loaded unless you've specified it to be loaded 
>> elsewhere.
>> (WW) "glamoregl" will not be loaded unless you've specified it to be loaded 
>> elsewhere.
>> (II) "glx" will be loaded even though the default is to disable it.
>> ...
>> (II) Loading sub module "glamoregl"
>> (II) LoadModule: "glamoregl"
>> (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
>> (II) Module glamoregl: vendor="X.Org Foundation"
>> compiled for 1.19.0, module version

Re: [Mesa-dev] UDL & Modeset with Mesa 13.0.1 - Segmentation fault

[Emil Velikov]

On 17 November 2016 at 20:15, poma <pomidorabelis...@gmail.com> wrote:
>
> Airlie solved everything concerning the kernel,
> so it seems, now it's user space turn.
>
> = mesa-libgbm-12.0.3 - works OK
> ...
> [   714.429] (II) Loading sub module "glamoregl"
> [   714.429] (II) LoadModule: "glamoregl"
> [   714.430] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> [   714.480] (II) Module glamoregl: vendor="X.Org Foundation"
> [   714.481]compiled for 1.19.0, module version = 1.0.0
> [   714.481]ABI class: X.Org ANSI C Emulation, version 0.4
> ...
> [   714.481] (II) glamor: OpenGL accelerated X.org driver based.
> [   714.633] (II) glamor: EGL version 1.4 (DRI2):
> [   714.633] EGL_MESA_drm_image required.
> [   714.634] (EE) modeset(0): glamor initialization failed
> [   714.634] (II) modeset(0): ShadowFB: preferred NO, enabled NO
> ...
> [   714.643] (==) Depth 24 pixmap format is 32 bpp
> [   714.645] (==) modeset(0): Backing store enabled
> [   714.645] (==) modeset(0): Silken mouse enabled
> [   714.645] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR 
> disabled message.
> [   714.646] (==) modeset(0): DPMS enabled
> [   714.646] (--) RandR disabled
> [   714.669] (II) AIGLX: Screen 0 is not DRI2 capable
> [   714.669] (EE) AIGLX: reverting to software rendering
> [   714.683] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
> [   714.686] (II) IGLX: Loaded and initialized swrast
> [   714.686] (II) GLX: Initialized DRISWRAST GL provider for screen 0
> [   714.691] (II) modeset(0): Damage tracking initialized
> ...
>
> = mesa-libgbm-13.0.1 - not quite
> ...
> [  2324.953] (II) Loading sub module "glamoregl"
> [  2324.953] (II) LoadModule: "glamoregl"
> [  2324.953] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> [  2325.000] (II) Module glamoregl: vendor="X.Org Foundation"
> [  2325.000]compiled for 1.19.0, module version = 1.0.0
> [  2325.000]ABI class: X.Org ANSI C Emulation, version 0.4
> ...
> [  2325.001] (II) glamor: OpenGL accelerated X.org driver based.
> [  2325.002] (EE)
> [  2325.002] (EE) Backtrace:
> [  2325.006] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59e389]
> [  2325.008] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) 
> [0x7f69d836ac2f]
> [  2325.009] (EE) 2: /lib64/libgbm.so.1 (gbm_surface_has_free_buffers+0x1505) 
> [0x7f69d2b64685]
> [  2325.010] (EE) 3: /lib64/libgbm.so.1 (gbm_surface_has_free_buffers+0x1b98) 
> [0x7f69d2b653b8]
> [  2325.011] (EE) 4: /lib64/libgbm.so.1 (gbm_surface_has_free_buffers+0x1498) 
> [0x7f69d2b644c8]
> [  2325.012] (EE) 5: /lib64/libgbm.so.1 (gbm_create_device+0x4c) 
> [0x7f69d2b61a4c]
> [  2325.014] (EE) 6: /usr/lib64/xorg/modules/libglamoregl.so 
> (glamor_egl_init+0x83) [0x7f69d2d73fb3]
> [  2325.015] (EE) 7: /usr/lib64/xorg/modules/drivers/modesetting_drv.so 
> (_init+0x4d21) [0x7f69d2facfd1]
> [  2325.016] (EE) 8: /usr/libexec/Xorg (InitOutput+0xa82) [0x47d6c2]
> [  2325.017] (EE) 9: /usr/libexec/Xorg (InitFonts+0x216) [0x43ae36]
> [  2325.020] (EE) 10: /lib64/libc.so.6 (__libc_start_main+0xf1) 
> [0x7f69d7fb8731]
> [  2325.022] (EE) 11: /usr/libexec/Xorg (_start+0x29) [0x424d29]
> [  2325.024] (EE) 12: ? (?+0x29) [0x29]
> [  2325.025] (EE)
> [  2325.025] (EE) Segmentation fault at address 0xc
> [  2325.025] (EE)
> Fatal server error:
> [  2325.025] (EE) Caught signal 11 (Segmentation fault). Server aborting
> [  2325.026] (EE)
> [  2325.026] (EE)
> ...
> [  2325.027] (EE) Server terminated with error (1). Closing log file.
>
>
> A call to not load the module(s) is not at all useful:
> Section "Module"
> Disable  "glx"
> Disable  "glamoregl"
> EndSection
>
> ...
> (WW) "glx" will not be loaded unless you've specified it to be loaded 
> elsewhere.
> (WW) "glamoregl" will not be loaded unless you've specified it to be loaded 
> elsewhere.
> (II) "glx" will be loaded even though the default is to disable it.
> ...
> (II) Loading sub module "glamoregl"
> (II) LoadModule: "glamoregl"
> (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> (II) Module glamoregl: vendor="X.Org Foundation"
> compiled for 1.19.0, module version = 1.0.0
> ABI class: X.Org ANSI C Emulation, version 0.4
> (II) glamor: OpenGL accelerated X.org driver based.
> (EE)
> (EE) Backtrace:
> ...
>
> Therefore, until the issue resolved, there remain two workarounds:
> downgrade mesa to 12.0.3, what works
> OR
> leave mesa 13.0.1 and:
> # rm /usr/lib64/xorg/modules/libglamoregl.so
>
Is that with libdrm 2.4.72 or later ? Older ones are known to be
broken with non-pci devices.
Additionally ensure that your pthread-stubs package does _not_ have
the following commit/patch [1].

Thanks
Emil

[1] 
https://cgit.freedesktop.org/xcb/pthread-stubs/commit/?id=fa6db2f9c018c54a47e94c0175450303d700aa92
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

UDL & Modeset with Mesa 13.0.1 - Segmentation fault

[poma]

Airlie solved everything concerning the kernel,
so it seems, now it's user space turn.

= mesa-libgbm-12.0.3 - works OK
...
[   714.429] (II) Loading sub module "glamoregl"
[   714.429] (II) LoadModule: "glamoregl"
[   714.430] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[   714.480] (II) Module glamoregl: vendor="X.Org Foundation"
[   714.481]compiled for 1.19.0, module version = 1.0.0
[   714.481]ABI class: X.Org ANSI C Emulation, version 0.4
...
[   714.481] (II) glamor: OpenGL accelerated X.org driver based.
[   714.633] (II) glamor: EGL version 1.4 (DRI2):
[   714.633] EGL_MESA_drm_image required.
[   714.634] (EE) modeset(0): glamor initialization failed
[   714.634] (II) modeset(0): ShadowFB: preferred NO, enabled NO
...
[   714.643] (==) Depth 24 pixmap format is 32 bpp
[   714.645] (==) modeset(0): Backing store enabled
[   714.645] (==) modeset(0): Silken mouse enabled
[   714.645] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR 
disabled message.
[   714.646] (==) modeset(0): DPMS enabled
[   714.646] (--) RandR disabled
[   714.669] (II) AIGLX: Screen 0 is not DRI2 capable
[   714.669] (EE) AIGLX: reverting to software rendering
[   714.683] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[   714.686] (II) IGLX: Loaded and initialized swrast
[   714.686] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[   714.691] (II) modeset(0): Damage tracking initialized
...

= mesa-libgbm-13.0.1 - not quite
...
[  2324.953] (II) Loading sub module "glamoregl"
[  2324.953] (II) LoadModule: "glamoregl"
[  2324.953] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[  2325.000] (II) Module glamoregl: vendor="X.Org Foundation"
[  2325.000]compiled for 1.19.0, module version = 1.0.0
[  2325.000]ABI class: X.Org ANSI C Emulation, version 0.4
...
[  2325.001] (II) glamor: OpenGL accelerated X.org driver based.
[  2325.002] (EE) 
[  2325.002] (EE) Backtrace:
[  2325.006] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59e389]
[  2325.008] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7f69d836ac2f]
[  2325.009] (EE) 2: /lib64/libgbm.so.1 (gbm_surface_has_free_buffers+0x1505) 
[0x7f69d2b64685]
[  2325.010] (EE) 3: /lib64/libgbm.so.1 (gbm_surface_has_free_buffers+0x1b98) 
[0x7f69d2b653b8]
[  2325.011] (EE) 4: /lib64/libgbm.so.1 (gbm_surface_has_free_buffers+0x1498) 
[0x7f69d2b644c8]
[  2325.012] (EE) 5: /lib64/libgbm.so.1 (gbm_create_device+0x4c) 
[0x7f69d2b61a4c]
[  2325.014] (EE) 6: /usr/lib64/xorg/modules/libglamoregl.so 
(glamor_egl_init+0x83) [0x7f69d2d73fb3]
[  2325.015] (EE) 7: /usr/lib64/xorg/modules/drivers/modesetting_drv.so 
(_init+0x4d21) [0x7f69d2facfd1]
[  2325.016] (EE) 8: /usr/libexec/Xorg (InitOutput+0xa82) [0x47d6c2]
[  2325.017] (EE) 9: /usr/libexec/Xorg (InitFonts+0x216) [0x43ae36]
[  2325.020] (EE) 10: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7f69d7fb8731]
[  2325.022] (EE) 11: /usr/libexec/Xorg (_start+0x29) [0x424d29]
[  2325.024] (EE) 12: ? (?+0x29) [0x29]
[  2325.025] (EE) 
[  2325.025] (EE) Segmentation fault at address 0xc
[  2325.025] (EE) 
Fatal server error:
[  2325.025] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  2325.026] (EE) 
[  2325.026] (EE) 
...
[  2325.027] (EE) Server terminated with error (1). Closing log file.


A call to not load the module(s) is not at all useful:
Section "Module"
Disable  "glx"
Disable  "glamoregl"
EndSection

...
(WW) "glx" will not be loaded unless you've specified it to be loaded elsewhere.
(WW) "glamoregl" will not be loaded unless you've specified it to be loaded 
elsewhere.
(II) "glx" will be loaded even though the default is to disable it.
...
(II) Loading sub module "glamoregl"
(II) LoadModule: "glamoregl"
(II) Loading /usr/lib64/xorg/modules/libglamoregl.so
(II) Module glamoregl: vendor="X.Org Foundation"
compiled for 1.19.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) glamor: OpenGL accelerated X.org driver based.
(EE) 
(EE) Backtrace:
...

Therefore, until the issue resolved, there remain two workarounds:
downgrade mesa to 12.0.3, what works
OR
leave mesa 13.0.1 and:
# rm /usr/lib64/xorg/modules/libglamoregl.so


Trick or treat
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

[Bug 39557] Intermittent segmentation fault on locking screen

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=39557

Christopher M. Penalver  changed:

   What|Removed |Added

 CC||christopher.m.penalver@gmai
   ||l.com
 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #4 from Christopher M. Penalver  
---
Wim De Smet, Ubuntu 11.04 reached EOL on October 28, 2012. For more on this,
please see https://wiki.ubuntu.com/Releases .

If this is reproducible in a supported release, it will help immensely if you
filed a new report with Ubuntu by ensuring you have the package xdiagnose
installed, and that you click the Yes button for attaching additional debugging
information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 92453] amdgpu startx segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92453

Michel Dänzer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Michel Dänzer  ---
Glad it's working again, resolving as a setup issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 92453] amdgpu startx segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92453

--- Comment #2 from Brian Paterni  ---
I think you're right, Michel! The self-built radeonsi_dri.so is actually
installed to /usr/local/lib/dri, and I'm relying on
LD_LIBRARY_PATH/LIBGL_DRIVERS_PATH to hopefully pick up the local libraries. As
soon as I backup the debian-provided
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so and overwrite with the local
radeonsi_dri.so, startx works once again! Not only that, but hardware
acceleration seems to run much faster than my previous working compile! No more
slow redraws when I swap windows across screens, YAY!

Thank You, Michel! :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 92453] New: amdgpu startx segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92453

Bug ID: 92453
   Summary: amdgpu startx segmentation fault
   Product: xorg
   Version: unspecified
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: Driver/AMDgpu
  Assignee: xorg-driver-ati@lists.x.org
  Reporter: bpate...@gmail.com
QA Contact: xorg-t...@lists.x.org

Created attachment 118864
  --> https://bugs.freedesktop.org/attachment.cgi?id=118864=edit
failing Xorg.0.log -- non-root X

X had been working fine (aside from performance) using compiled-from-source
xf86-video-amdgpu and mesa. This morning, however, I was greeted with a
segfault upon startx. The only thing that seems to have changed though, is an
upgrade to debian's xserver-xorg packages which look to have introduced
non-root X. Would this be the cause of the following segfault cut from the
attached Xorg.0.log? I do have the xserver-xorg-legacy wrapper installed, but
startx still fails (unsure if additional configuration might be needed for
xserverxorg-legacy?)

Please let me know if additional information is needed. I have
xserver-xorg-core-dbg debugging symbols installed, but some locations in the
backtrace are not resolved...

[   169.888] (==) AMDGPU(0): Silken mouse enabled
[   169.888] (II) AMDGPU(0): Set up textured video (glamor)
[   169.888] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR
disabled message.
[   169.961] (--) RandR disabled
[   169.965] (II) SELinux: Disabled on system
[   170.012] (EE) 
[   170.012] (EE) Backtrace:
[   170.017] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x56358be445be]
[   170.017] (EE) 1: /usr/lib/xorg/Xorg (0x56358bc8f000+0x1b9809)
[0x56358be48809]
[   170.017] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f86b0077000+0x35180)
[0x7f86b00ac180]
[   170.017] (EE) 3: /usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
(_ZN4llvm2cl16AddLiteralOptionERNS0_6OptionEPKc+0x31) [0x7f86a97131e1]
[   170.018] (EE) 4: /usr/lib/x86_64-linux-gnu/libLLVM-3.5.so.1
(_ZN4llvm12PassRegistry13enumerateWithEPNS_24PassRegistrationListenerE+0x129)
[0x7f86a2b4e179]
[   170.018] (EE) 5: /usr/lib/x86_64-linux-gnu/libLLVM-3.5.so.1
(0x7f86a251f000+0x3b2141) [0x7f86a28d1141]
[   170.018] (EE) 6: /lib64/ld-linux-x86-64.so.2 (0x7f86b21a1000+0xea0a)
[0x7f86b21afa0a]
[   170.018] (EE) 7: /lib64/ld-linux-x86-64.so.2 (0x7f86b21a1000+0xeaf3)
[0x7f86b21afaf3]
[   170.018] (EE) 8: /lib64/ld-linux-x86-64.so.2 (0x7f86b21a1000+0x12c58)
[0x7f86b21b3c58]
[   170.018] (EE) 9: /lib64/ld-linux-x86-64.so.2 (0x7f86b21a1000+0xe8c4)
[0x7f86b21af8c4]
[   170.018] (EE) 10: /lib64/ld-linux-x86-64.so.2 (0x7f86b21a1000+0x1244b)
[0x7f86b21b344b]
[   170.018] (EE) 11: /lib/x86_64-linux-gnu/libdl.so.2 (0x7f86b1846000+0x102b)
[0x7f86b184702b]
[   170.018] (EE) 12: /lib64/ld-linux-x86-64.so.2 (0x7f86b21a1000+0xe8c4)
[0x7f86b21af8c4]
[   170.018] (EE) 13: /lib/x86_64-linux-gnu/libdl.so.2 (0x7f86b1846000+0x15dd)
[0x7f86b18475dd]
[   170.018] (EE) 14: /lib/x86_64-linux-gnu/libdl.so.2 (dlopen+0x31)
[0x7f86b18470c1]
[   170.018] (EE) 15: /usr/lib/xorg/modules/extensions/libglx.so
(0x7f86ae02b000+0x28116) [0x7f86ae053116]
[   170.018] (EE) 16: /usr/lib/xorg/modules/extensions/libglx.so
(0x7f86ae02b000+0x2f12e) [0x7f86ae05a12e]
[   170.018] (EE) 17: /usr/lib/xorg/modules/extensions/libglx.so
(0x7f86ae02b000+0x270da) [0x7f86ae0520da]
[   170.018] (EE) 18: /usr/lib/xorg/Xorg (InitExtensions+0x43) [0x56358bd5bf33]
[   170.018] (EE) 19: /usr/lib/xorg/Xorg (0x56358bc8f000+0x5c82f)
[0x56358bceb82f]
[   170.018] (EE) 20: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5)
[0x7f86b0098b45]
[   170.018] (EE) 21: /usr/lib/xorg/Xorg (0x56358bc8f000+0x46dee)
[0x56358bcd5dee]
[   170.018] (EE) 
[   170.018] (EE) Segmentation fault at address 0x19
[   170.018] (EE) 
Fatal server error:
[   170.018] (EE) Caught signal 11 (Segmentation fault). Server aborting

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 92453] amdgpu startx segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92453

--- Comment #1 from Michel Dänzer  ---
(In reply to Brian Paterni from comment #0)
> 
> [   170.017] (EE) 3: /usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1 [...]
> [   170.018] (EE) 4: /usr/lib/x86_64-linux-gnu/libLLVM-3.5.so.1 [...]

Looks like both 3.8 and 3.5 versions of LLVM are getting pulled in, and LLVM
3.5 wasn't safe against this yet.

Is your self-built radeonsi_dri.so available in /usr/lib/x86_64-linux-gnu/dri/
as well? That's where the Xorg glx module looks for the DRI drivers. I suspect
it's failing to load radeonsi_dri.so from there and falling back to
swrast_dri.so, which is linked against LLVM 3.5.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 90728] New: dvd playback with vlc and vdpau causes segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=90728

Bug ID: 90728
   Summary: dvd playback with vlc and vdpau causes segmentation
fault
   Product: xorg
   Version: unspecified
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: Driver/Radeon
  Assignee: xorg-driver-ati@lists.x.org
  Reporter: mehmet.giri...@gmail.com
QA Contact: xorg-t...@lists.x.org

Created attachment 116123
  -- https://bugs.freedesktop.org/attachment.cgi?id=116123action=edit
vdpau trace from vlc

I've already run this by vlc bugzilla and they are sure taht this is a radeon
bug.

With many dvd iso images I have, I frequently get seg faults when I try to play
them if I'm using vdpau hw acceleration with vlc. Turning vdpau off stops
crashes. The crashes happen at the menu stages, for example if you choose the
main language and it is supposed to show you the real menu after that, you get
the crash after you select the language. Or when it is displaying FBI warnings
or similar and when it is done and it is going to change to another
menu/screeen or whatever, I get a crash. But if I manage to manually select the
main title from the playback menu (not always works depending on the dvd
structure I guess), I can watch the entire movie without any problems. So, the
problem seems to be fixable...

Also, vlc plays all my other files like mkv files without any problem through
vdpau...

I don't know how to provide more data. If you instruct me how to get extra
data, I'll do my best.

I'm attaching vdpau traces and a backtrace from vlc. I hope they help.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=90728

--- Comment #2 from mehmet.giri...@gmail.com ---
I realise that the backtrace is not detailed enough but dont really know how to
get a more detailed version. Any help with that would be highly appreciated!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=90728

--- Comment #1 from mehmet.giri...@gmail.com ---
Created attachment 116124
  -- https://bugs.freedesktop.org/attachment.cgi?id=116124action=edit
gdb backtrace

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=90728

--- Comment #3 from mehmet.giri...@gmail.com ---
Also,

I'm running mesa 10.4.6, xorg-server 1.16.4 and kernel 4.0.4. My card is Radeon
HD3650 on a laptop.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=90728

--- Comment #4 from Alex Deucher alexdeuc...@gmail.com ---
Install the debug symbol packages if you are using distro packages.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=90728

Michel Dänzer mic...@daenzer.net changed:

   What|Removed |Added

  Component|Driver/Radeon   |Drivers/Gallium/r600
Version|unspecified |10.4
   Assignee|xorg-driver-ati@lists.x.org |dri-devel@lists.freedesktop
   ||.org
Product|xorg|Mesa
 QA Contact|xorg-t...@lists.x.org   |dri-devel@lists.freedesktop
   ||.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 90198] Segmentation fault at system boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=90198

Michel Dänzer mic...@daenzer.net changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Michel Dänzer mic...@daenzer.net ---
Please try the patch attached to bug 90187.

*** This bug has been marked as a duplicate of bug 90187 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

Bug#757982: xserver segmentation fault

[Julien Cristau]

On Thu, Sep 11, 2014 at 21:17:34 +0200, repron wrote:

 Dnia 9 września 2014 5:13 Michel Dänzer mic...@daenzer.net napisał(a):
 
  On 08.09.2014 20:32, repron wrote:
Last several freezes of Xorg, coused that Xorg.o.log file ended 
suddenly, without SIGSEGV.
   I am still trying to reproduce exactly the same state of freeze as 
   mentioned in the bug.
   Of course it can be a bug in kernel or somewhere else but if I had 
   uninstalled packages
   xserver-xorg-video-radeon, xserver-xorg-video-iti
   and installed in that place packages:
   fglrx-modules-dkms and firmware-linux-nonfree
   the error of  freezing did not appeared.
  
  (Note that the firmware-linux-nonfree package is required for the radeon 
  driver, not for fglrx, but the information you've provided shows that it 
  was installed)
  
  
  It seems like the crashes you're experiencing are more or less random 
  and all over the place. I can think of two basic explanations for that: 
  Either the GPU is scribbling over random system memory locations, or 
  there is a problem with the RAM or some other hardware component in the 
  system.
  
  You can test for the latter with the memtest86(+) or memtester package.
  
  
  -- 
  Earthling Michel Dänzer|  http://www.amd.com
  Libre software enthusiast  |Mesa and X developer
  
 
 Thanks much for suggestions concerning memtest.
 In both cases (radeon or fglrx)  I had firmware-linux-nonfree
 package installed.
 The last freeze was coused by SIGPIPE broken and I was able
 to get a full backtrace with gdb - enclosed here as a txt file: 
 sigpipe_backtrace.txt.
 Could you have a look at it and say somthing about it. ? 

SIGPIPE in the X server is not an issue, it's expected whenever a client
goes away.  You should continue past that signal, or tell gdb not to
stop on it.

Cheers,
Julien


signature.asc
Description: Digital signature
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

Bug#757982: xserver segmentation fault

[Michel Dänzer]

On 07.09.2014 04:39, repron wrote:



Dnia 13 sierpnia 2014 3:05 Michel Dänzer mic...@daenzer.net wrote:


On 13.08.2014 09:37, repron wrote:

[  5884.303] (EE) Backtrace:

[  5884.303] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x7fcf5241b3f9]
[  5884.303] (EE) 1: /usr/bin/X (0x7fcf5227+0x1af469) [0x7fcf5241f469]
[  5884.304] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcf4ff78000+0x35480) 
[0x7fcf4ffad480]
[  5884.304] (EE) 3: /usr/bin/X (0x7fcf5227+0x12b70d) [0x7fcf5239b70d]
[  5884.304] (EE) 4: /usr/bin/X (0x7fcf5227+0x55ee7) [0x7fcf522c5ee7]
[  5884.304] (EE) 5: /usr/bin/X (0x7fcf5227+0x59f16) [0x7fcf522c9f16]
[  5884.304] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
[0x7fcf4ff99b45]
[  5884.304] (EE) 7: /usr/bin/X (0x7fcf5227+0x4549e) [0x7fcf522b549e]
[  5884.304] (EE)
[  5884.304] (EE) Segmentation fault at address 0x0
[  5884.304] (EE)
Fatal server error:
[  5884.304] (EE) Caught signal 11 (Segmentation fault). Server aborting


It would be good to see a full backtrace from gdb, but this doesn't look
directly related to the driver.


--
Earthling Michel Dänzer|  http://www.amd.com
Libre software enthusiast  |Mesa and X developer


Attempting to get backtrace from gdb by ssh from other machine
is still  unsuccessfull. During Xorg  freeze on remote host, gdb screen on main 
machine says nothing.
On the screen still:
---
(gdb) continue
Continuing.
--
As you can see, no info about receiving signal SIGSEGV.
I would appreciate any suggestions how to get a miningfull backtrace of Xorg
(maybe any trick).


You should be able to get a backtrace like this if you can reproduce the 
crash from your original report.




But I got somthing like this, when instead of freezing Xorg disappeared and 
screen switched
to this:
[1812.375053]  CPU: 7   PID: 1   Comm: systemd Not tained3.14-2-amd64  #1 
Debian 3.14.15-2
[1812.375090]  Hardware name:  To Be Filled By O.E.M.  /960GM-GS3 FX,   BIOS  
P1.40  02/05/2013
[1812.375135]  task: 880129ec71b0   ti:880129ec8000   task.ti 
880129ec8000
[1812.375170]  RIP: 0010:[811a2ba4]   [811a2ba4]
__fget+0x14/0x80
[1812.375210]  RSP: 0018:880129ec9f00 EFLAGS: 00010202
[1812.375235]  RAX: 00ff00ff   RBX: 880129ec9f2c
RCX: 
[1812.375269]  RDX: 00ff RSI: 4000RDI: 
0043
[1812.375302]  RBP: 880129ec9f28 R08: 7fff374b55e4  R09: 
0009
[1812.375335]  R10: R11: 0293   R12: 
4000
[1812.375368]  R13: 7fff374b5540   R14: 7fff374b55e4  R15: 
7fff374b5760
[1812.375403]  FS:  7f3eb16ab880()   GS:88012edc()   
kn1GS:
[1812.375442]  CS:  0010   DS:    ES:    CR0: 80050033
[1812.375469]  CR2: 0007f8d80cf6e38   CR3: c8aab000   CR4: 
000407e0
[1812.375503]   Stack:
[1812.375514] 811a304c   813c669d 
7fff374b5550 7fff374b5550
[1812.375556] 813c8c0b    
8800c89c5cc0   7fff374b5760
[1812.375597] 0001   811cc474 814d33fa  
 2754
[1812.375639]  Call Trace:
[1812.375656] [811a304c]   ?   __fget_light+0x1c/0x60
[1812.375686] [813c669d]   ?   sockfd_lookup_light+0xd/0x70
[1812.375718] [813c8c0b]   ?   __sys_recvmsg+0x1b/0x70
[1812.375747] [811cc474]   ?   sys_epoll_wait+0xb4/0xe0
[1812.375778] [814d33fa]?   int_signal+0x12/0x17
[1812.375806] [814d313d ]  ?   
system_call_fast_compare_end+0x10/0x15
[1812.375840]  Code: 48 89 df e8 7f d9 ff ff 48 89 df 5b e9 96 ed ff ff 66 0f 
1f 44 00 00 65
48 8b 04 25 80 c8 00 00 48 8b 80 98 05 00 00 48 8b 40 08 3b 38 73 40 48 8b 40 
08 89 ff 48
8d 04 f8 48 8b 10 48 85 c2 74
[1812.376011]  RIP [811a2ba4]__fget+0x14/0x80
[1812.376040]  RSP 880129ec9f00
[1812.387056]  Kernel Panic - not syncing:  Attempted to kill init!
exitcode=0x000b
[1812.387056]
[1812.387107]  Kernel Offset: 0x0 from 0x8100   (relocation range: 
0x8000-0x9fff)
[1812.387153]  drm_kms_helper: panic occured,  switching back to text console


This kernel panic looks unrelated to the radeon driver. Maybe this bug 
report should be reassigned to the kernel.



--
Earthling Michel Dänzer|  http://www.amd.com
Libre software enthusiast  |Mesa and X developer

___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

Bug#757982: xserver segmentation fault

[Michel Dänzer]

On 08.09.2014 20:32, repron wrote:


Last several freezes of Xorg, coused that Xorg.o.log file ended suddenly, 
without SIGSEGV.
I am still trying to reproduce exactly the same state of freeze as mentioned 
in the bug.
Of course it can be a bug in kernel or somewhere else but if I had uninstalled 
packages
xserver-xorg-video-radeon, xserver-xorg-video-iti
and installed in that place packages:
fglrx-modules-dkms and firmware-linux-nonfree
the error of  freezing did not appeared.


(Note that the firmware-linux-nonfree package is required for the radeon 
driver, not for fglrx, but the information you've provided shows that it 
was installed)



It seems like the crashes you're experiencing are more or less random 
and all over the place. I can think of two basic explanations for that: 
Either the GPU is scribbling over random system memory locations, or 
there is a problem with the RAM or some other hardware component in the 
system.


You can test for the latter with the memtest86(+) or memtester package.


--
Earthling Michel Dänzer|  http://www.amd.com
Libre software enthusiast  |Mesa and X developer

___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

Re: EE Xorg.bin xf86PlatformMatchDriver - Segmentation fault - Server aborting

[poma]

...

- xorg-x11-server-Xorg-1.16.99.1-1.fc21.x86_64
  commit 3a51418
  *auto-detection* PASSED

- xorg-x11-server-Xorg-1.16.99.1-2.fc21.x86_64
  commit 3a51418 + xorg-non-pci-v2.patch[1] (rebased xorg-non-pci.patch)
  *auto-detection* BROKEN

/var/log/Xorg.0.log
[29.408] 
This is a pre-release version of the X server from Fedora Project.
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.
[29.409] 
X.Org X Server 1.16.99.1
Release Date: 2014-07-17
[29.409] X Protocol Version 11, Revision 0
[29.409] Build Operating System: lnx 3.17.0-0.rc3.git0.1.fc22.x86_64 
[29.409] Current Operating System: Linux rawhide642 
3.17.0-0.rc3.git0.1.fc22.x86_64 #1 SMP Mon Sep 1 14:47:34 UTC 2014 x86_64
[29.409] Kernel command line: 
BOOT_IMAGE=/vmlinuz-3.17.0-0.rc3.git0.1.fc22.x86_64 
root=UUID=a07556d2-6fe2-417f-8202-c54c07fd9386 
drm_kms_helper.edid_firmware=DVI-I-1:edid/848x480.bin  
initrd=/initramfs-3.17.0-0.rc3.git0.1.fc22.x86_64.img
[29.409] Build Date: 05 September 2014  09:11:28PM
[29.410] Build ID: xorg-x11-server 1.16.99.1-2.fc21 
[29.410] Current version of pixman: 0.32.6
[29.410]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[29.410] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[29.411] (==) Log file: /var/log/Xorg.0.log, Time: Fri Sep  5 22:40:21 
2014
[29.411] (==) Using system config directory /usr/share/X11/xorg.conf.d
[29.426] (==) No Layout section.  Using the first Screen section.
[29.426] (==) No screen section available. Using defaults.
[29.426] (**) |--Screen Default Screen Section (0)
[29.427] (**) |   |--Monitor default monitor
[29.427] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[29.427] (==) Automatically adding devices
[29.427] (==) Automatically enabling devices
[29.427] (==) Automatically adding GPU devices
[29.428] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[29.428] (==) ModulePath set to /usr/lib64/xorg/modules
[29.428] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[29.428] (II) Loader magic: 0x81be40
[29.428] (II) Module ABI versions:
[29.428]X.Org ANSI C Emulation: 0.4
[29.428]X.Org Video Driver: 18.0
[29.428]X.Org XInput driver : 21.0
[29.428]X.Org Server Extension : 8.0
[29.434] (EE) systemd-logind: failed to get session: PID 655 does not 
belong to any known session
[29.435] (II) xfree86: Adding drm device (/dev/dri/card1)
[29.436] (II) xfree86: Adding drm device (/dev/dri/card0)
[29.460] (--) PCI:*(0:1:0:0) 10de:087d:1849:087d rev 177, Mem @ 
0xfb00/16777216, 0xe000/268435456, 0xf600/33554432, I/O @ 
0xec00/128, BIOS @ 0x/131072
[29.461] (II) LoadModule: glx
[29.462] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[29.487] (II) Module glx: vendor=X.Org Foundation
[29.487]compiled for 1.16.99.1, module version = 1.0.0
[29.488]ABI class: X.Org Server Extension, version 8.0
[29.488] (==) AIGLX enabled
[29.488] (EE) 
[29.488] (EE) Backtrace:
[29.490] (EE) 0: /usr/libexec/Xorg.bin (OsSigHandler+0x29) [0x59ab89]
[29.491] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7f0d482947cf]
[29.492] (EE) 2: /usr/libexec/Xorg.bin (xf86PlatformMatchDriver+0x31d) 
[0x49a3fd]
[29.494] (EE) 3: /usr/libexec/Xorg.bin 
(listPossibleVideoDrivers.constprop.0+0x3d) [0x49d54d]
[29.508] (EE) 4: /usr/libexec/Xorg.bin (autoConfigDevice+0xfe) [0x49da3e]
[29.509] (EE) 5: /usr/libexec/Xorg.bin (InitOutput+0xb56) [0x47b9e6]
[29.510] (EE) 6: /usr/libexec/Xorg.bin (dix_main+0x1ea) [0x43cd5a]
[29.512] (EE) 7: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f0d47edd0e0]
[29.514] (EE) 8: /usr/libexec/Xorg.bin (_start+0x29) [0x4273ae]
[29.516] (EE) 9: ? (?+0x29) [0x29]
[29.516] (EE) 
[29.516] (EE) Segmentation fault at address 0x0
[29.517] (EE) 
Fatal server error:
[29.517] (EE) Caught signal 11 (Segmentation fault). Server aborting
[29.517] (EE) 
[29.517] (EE) 
Please consult the Fedora Project support 
 at http://wiki.x.org
 for help. 
[29.517] (EE) Please also check the log file at /var/log/Xorg.0.log for 
additional information.
[29.517] (EE) 


[1] xorg-non-pci-v2.patch

diff -ur a/hw/xfree86/common/xf86Init.c b/hw

Re: EE Xorg.bin xf86PlatformMatchDriver - Segmentation fault - Server aborting

[poma]

...

Rebased[1] patch[2] for the modesetting also didn't help, 
- xorg-x11-drv-modesetting-0.9.0-4.fc21.x86_64

[1] 
RFC-modesetting-Add_workaround_for_platform_devices_and_supreme_xserver.patch

--- a/src/driver.c  2014-06-26 10:20:17.0 +0200
+++ b/src/driver.c  2014-09-06 06:56:32.862956426 +0200
@@ -136,6 +136,8 @@
 
 int modesettingEntityIndex = -1;
 
+static Bool supports_non_pci_platform_devs = FALSE;
+
 static MODULESETUPPROTO(Setup);
 
 static XF86ModuleVersionInfo VersRec = {
@@ -229,6 +231,28 @@
 fd = open_hw(dev);
 if (fd != -1) {
 int ret = check_outputs(fd);
+/* if called in platformProbe path, and server does not
+ * supports_non_pci_platform_devs then we need to reject
+ * and fallback to old probe.   Otherwise things won't
+ * even work if user has a .conf file, thanks to autoAddGPU
+ * loop.
+ */
+if (platform_dev  !supports_non_pci_platform_devs) {
+drmSetVersion sv;
+char *busid;
+
+sv.drm_di_major = 1;
+sv.drm_di_minor = 4;
+sv.drm_dd_major = -1;   /* Don't care */
+sv.drm_dd_minor = -1;   /* Don't care */
+
+drmSetInterfaceVersion(fd, sv);
+
+busid = drmGetBusid(fd);
+if (busid  !strncmp(busid, platform:, 9))
+ret = FALSE;
+drmFreeBusid(busid);
+}
 close(fd);
 return ret;
 }
@@ -284,6 +308,10 @@
 return Options;
 }
 
+#if 1 /* XORG_VERSION_CURRENT = XORG_VERSION_NUMERIC(???) */
+#  define SERVER_SUPPORTS_NON_PCI_PLATFORM_DEVS 12
+#endif
+
 static Bool
 ms_driver_func(ScrnInfoPtr scrn, xorgDriverFuncOp op, void *data)
 {
@@ -298,6 +326,9 @@
 case SUPPORTS_SERVER_FDS:
 return TRUE;
 #endif
+case SERVER_SUPPORTS_NON_PCI_PLATFORM_DEVS:
+supports_non_pci_platform_devs = TRUE;
+return TRUE;
default:
return FALSE;
 }


I wonder whether this has anything to do with DisplayLink USB Display Adapter 
per se, and are these devices properly supported from day one.
Mr. Keith I see[3] you also have one such device, can you help with advice?


poma


[2] http://lists.x.org/archives/xorg-devel/2014-June/042819.html
[3] http://keithp.com/blogs/hotplug-displaylink/

___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Re: EE Xorg.bin xf86PlatformMatchDriver - Segmentation fault - Server aborting

[Hans de Goede]

Hi poma,

On 09/05/2014 11:19 PM, poma wrote:
 ...
 
 - xorg-x11-server-Xorg-1.16.99.1-1.fc21.x86_64
   commit 3a51418
   *auto-detection* PASSED
 
 - xorg-x11-server-Xorg-1.16.99.1-2.fc21.x86_64
   commit 3a51418 + xorg-non-pci-v2.patch[1] (rebased xorg-non-pci.patch)
   *auto-detection* BROKEN

As discussed in another email discussion, we're dropping xorg-non-pci.patch,
as upstream has a different solution. I've just kicked of builds for F-21+
with this patch dropped, which should resolve your issue.

Regards,

Hans



 
 /var/log/Xorg.0.log
 [29.408] 
 This is a pre-release version of the X server from Fedora Project.
 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.
 [29.409] 
 X.Org X Server 1.16.99.1
 Release Date: 2014-07-17
 [29.409] X Protocol Version 11, Revision 0
 [29.409] Build Operating System: lnx 3.17.0-0.rc3.git0.1.fc22.x86_64 
 [29.409] Current Operating System: Linux rawhide642 
 3.17.0-0.rc3.git0.1.fc22.x86_64 #1 SMP Mon Sep 1 14:47:34 UTC 2014 x86_64
 [29.409] Kernel command line: 
 BOOT_IMAGE=/vmlinuz-3.17.0-0.rc3.git0.1.fc22.x86_64 
 root=UUID=a07556d2-6fe2-417f-8202-c54c07fd9386 
 drm_kms_helper.edid_firmware=DVI-I-1:edid/848x480.bin  
 initrd=/initramfs-3.17.0-0.rc3.git0.1.fc22.x86_64.img
 [29.409] Build Date: 05 September 2014  09:11:28PM
 [29.410] Build ID: xorg-x11-server 1.16.99.1-2.fc21 
 [29.410] Current version of pixman: 0.32.6
 [29.410]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
 [29.410] Markers: (--) probed, (**) from config file, (==) default 
 setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 [29.411] (==) Log file: /var/log/Xorg.0.log, Time: Fri Sep  5 22:40:21 
 2014
 [29.411] (==) Using system config directory /usr/share/X11/xorg.conf.d
 [29.426] (==) No Layout section.  Using the first Screen section.
 [29.426] (==) No screen section available. Using defaults.
 [29.426] (**) |--Screen Default Screen Section (0)
 [29.427] (**) |   |--Monitor default monitor
 [29.427] (==) No monitor specified for screen Default Screen Section.
   Using a default monitor configuration.
 [29.427] (==) Automatically adding devices
 [29.427] (==) Automatically enabling devices
 [29.427] (==) Automatically adding GPU devices
 [29.428] (==) FontPath set to:
   catalogue:/etc/X11/fontpath.d,
   built-ins
 [29.428] (==) ModulePath set to /usr/lib64/xorg/modules
 [29.428] (II) The server relies on udev to provide the list of input 
 devices.
   If no devices become available, reconfigure udev or disable 
 AutoAddDevices.
 [29.428] (II) Loader magic: 0x81be40
 [29.428] (II) Module ABI versions:
 [29.428]  X.Org ANSI C Emulation: 0.4
 [29.428]  X.Org Video Driver: 18.0
 [29.428]  X.Org XInput driver : 21.0
 [29.428]  X.Org Server Extension : 8.0
 [29.434] (EE) systemd-logind: failed to get session: PID 655 does not 
 belong to any known session
 [29.435] (II) xfree86: Adding drm device (/dev/dri/card1)
 [29.436] (II) xfree86: Adding drm device (/dev/dri/card0)
 [29.460] (--) PCI:*(0:1:0:0) 10de:087d:1849:087d rev 177, Mem @ 
 0xfb00/16777216, 0xe000/268435456, 0xf600/33554432, I/O @ 
 0xec00/128, BIOS @ 0x/131072
 [29.461] (II) LoadModule: glx
 [29.462] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
 [29.487] (II) Module glx: vendor=X.Org Foundation
 [29.487]  compiled for 1.16.99.1, module version = 1.0.0
 [29.488]  ABI class: X.Org Server Extension, version 8.0
 [29.488] (==) AIGLX enabled
 [29.488] (EE) 
 [29.488] (EE) Backtrace:
 [29.490] (EE) 0: /usr/libexec/Xorg.bin (OsSigHandler+0x29) [0x59ab89]
 [29.491] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) 
 [0x7f0d482947cf]
 [29.492] (EE) 2: /usr/libexec/Xorg.bin (xf86PlatformMatchDriver+0x31d) 
 [0x49a3fd]
 [29.494] (EE) 3: /usr/libexec/Xorg.bin 
 (listPossibleVideoDrivers.constprop.0+0x3d) [0x49d54d]
 [29.508] (EE) 4: /usr/libexec/Xorg.bin (autoConfigDevice+0xfe) [0x49da3e]
 [29.509] (EE) 5: /usr/libexec/Xorg.bin (InitOutput+0xb56) [0x47b9e6]
 [29.510] (EE) 6: /usr/libexec/Xorg.bin (dix_main+0x1ea) [0x43cd5a]
 [29.512] (EE) 7: /lib64/libc.so.6 (__libc_start_main+0xf0) 
 [0x7f0d47edd0e0]
 [29.514] (EE) 8: /usr/libexec/Xorg.bin (_start+0x29) [0x4273ae]
 [29.516] (EE) 9: ? (?+0x29) [0x29]
 [29.516] (EE) 
 [29.516] (EE) Segmentation fault at address 0x0
 [29.517] (EE) 
 Fatal server error:
 [29.517] (EE) Caught signal 11

Re: EE Xorg.bin xf86PlatformMatchDriver - Segmentation fault - Server aborting

[poma]

On 06.09.2014 10:21, Hans de Goede wrote:
 Hi poma,
 
 On 09/05/2014 11:19 PM, poma wrote:
 ...

 - xorg-x11-server-Xorg-1.16.99.1-1.fc21.x86_64
   commit 3a51418
   *auto-detection* PASSED

 - xorg-x11-server-Xorg-1.16.99.1-2.fc21.x86_64
   commit 3a51418 + xorg-non-pci-v2.patch[1] (rebased xorg-non-pci.patch)
   *auto-detection* BROKEN
 
 As discussed in another email discussion, we're dropping xorg-non-pci.patch,
 as upstream has a different solution. I've just kicked of builds for F-21+
 with this patch dropped, which should resolve your issue.
 
 Regards,
 
 Hans
 

Thanks!


poma


___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

EE Xorg.bin xf86PlatformMatchDriver - Segmentation fault - Server aborting

[poma]

First of all, I welcome the revered readership.
Graciously invite you to help me figure out what's going on here.

With:
- xorg-x11-server-Xorg-1.16.0-5.fc22.x86_64
- xorg-x11-server-Xorg-1.16.0-6.fc22.x86_64
including:
http://pkgs.fedoraproject.org/cgit/xorg-x11-server.git/commit/?id=5556cee
  ...
  # submitted http://lists.x.org/archives/xorg-devel/2014-June/042826.html
  # needed to allow X to start on arm and other devices without video on pci 
buses
  # There's a slight variant upstream but it doesn't build against 1.16.0 atm
  # rebase of Rob Clark's patches
  Patch10300: xorg-non-pci.patch
  ...
  %changelog
  ...
  * Mon Aug 25 2014 Peter Robinson pbrobin...@fedoraproject.org 1.16.0-5
  - re-add support for non pci platform devices
  ...
i.e.
http://pkgs.fedoraproject.org/cgit/xorg-x11-server.git/plain/xorg-non-pci.patch

this happens *with* *auto-detection* i.e. without xorg.conf[.d/*.conf] 
configuration files:

$ cat /var/log/Xorg.0.log
[29.277] 
X.Org X Server 1.16.0
Release Date: 2014-07-16
[29.277] X Protocol Version 11, Revision 0
[29.277] Build Operating System:  3.15.8-200.fc20.x86_64 
[29.277] Current Operating System: Linux rawhide642 
3.17.0-0.rc3.git0.1.fc22.x86_64 #1 SMP Mon Sep 1 14:47:34 UTC 2014 x86_64
[29.277] Kernel command line: 
BOOT_IMAGE=/vmlinuz-3.17.0-0.rc3.git0.1.fc22.x86_64 
root=UUID=a07556d2-6fe2-417f-8202-c54c07fd9386 
drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin 
drm_kms_helper.edid_firmware=DVI-I-1:edid/848x480.bin  
initrd=/initramfs-3.17.0-0.rc3.git0.1.fc22.x86_64.img
[29.278] Build Date: 26 August 2014  07:34:52PM
[29.278] Build ID: xorg-x11-server 1.16.0-5.fc22 
[29.278] Current version of pixman: 0.32.6
[29.278]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[29.278] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[29.279] (==) Log file: /var/log/Xorg.0.log, Time: Thu Sep  4 23:22:47 
2014
[29.296] (==) Using system config directory /usr/share/X11/xorg.conf.d
[29.296] (==) No Layout section.  Using the first Screen section.
[29.296] (==) No screen section available. Using defaults.
[29.297] (**) |--Screen Default Screen Section (0)
[29.297] (**) |   |--Monitor default monitor
[29.297] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[29.297] (==) Automatically adding devices
[29.298] (==) Automatically enabling devices
[29.298] (==) Automatically adding GPU devices
[29.298] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[29.298] (==) ModulePath set to /usr/lib64/xorg/modules
[29.298] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[29.298] (II) Loader magic: 0x81de40
[29.298] (II) Module ABI versions:
[29.298]X.Org ANSI C Emulation: 0.4
[29.298]X.Org Video Driver: 18.0
[29.298]X.Org XInput driver : 21.0
[29.298]X.Org Server Extension : 8.0
[29.324] (EE) systemd-logind: failed to get session: PID 712 does not 
belong to any known session
[29.326] (II) xfree86: Adding drm device (/dev/dri/card1)
[29.328] (II) xfree86: Adding drm device (/dev/dri/card0)
[29.380] (--) PCI:*(0:1:0:0) 10de:087d:1849:087d rev 177, Mem @ 
0xfb00/16777216, 0xe000/268435456, 0xf600/33554432, I/O @ 
0xec00/128, BIOS @ 0x/131072
[29.383] (II) LoadModule: glx
[29.384] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[29.421] (II) Module glx: vendor=X.Org Foundation
[29.430]compiled for 1.16.0, module version = 1.0.0
[29.430]ABI class: X.Org Server Extension, version 8.0
[29.430] (==) AIGLX enabled
[29.430] (EE) 
[29.430] (EE) Backtrace:
[29.432] (EE) 0: /usr/libexec/Xorg.bin (OsLookupColor+0x119) [0x59bea9]
[29.456] (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7fb5636ae98f]
[29.457] (EE) 2: /usr/libexec/Xorg.bin (xf86PlatformMatchDriver+0x253) 
[0x49a8b3]
[29.470] (EE) 3: /usr/libexec/Xorg.bin (config_fini+0x1bcd) [0x49f9fd]
[29.471] (EE) 4: /usr/libexec/Xorg.bin (config_fini+0x20be) [0x4a031e]
[29.472] (EE) 5: /usr/libexec/Xorg.bin (InitOutput+0xb56) [0x47bc06]
[29.499] (EE) 6: /usr/libexec/Xorg.bin (remove_fs_handlers+0x22a) [0x43cfca]
[29.526] (EE) 7: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fb5636990e0]
[29.527] (EE) 8: /usr/libexec/Xorg.bin (_start+0x29) [0x42761e]
[29.551] (EE) 9: ? (?+0x29) [0x29]
[29.552] (EE) 
[29.552] (EE) Segmentation fault at address 0x0
[29.552] (EE) 
Fatal server error:
[29.552] (EE) Caught signal 11 (Segmentation fault). Server aborting
[29.552] (EE

Bug#757982: xserver segmentation fault

[repron]

Package: xserver-xorg-video-radeon
Version: 1:7.4.0-2
Severity: grave

Dear Maintainer,

With installed packages:
 xserver-xorg-video-radeon
 xserver-xorg-video-ati 
 firmware-linux-nonfree
very often randomly X-server freezes with the error: segmentation fault.
I use X-window system: xfce4. 
This didn't happen when I had installed debian non-free driver: fglrx-driver
 for my Radeon HD6670 graphic card.

Please, find the bug in the packages xserver-xorg-video-radeon, 
xserver-xorg-video-ati
or in modules: ati_drv.so, radeon_drv.so
to stop freezing the system. 
 
with regards
Richi

Xorg.0.log says:
---
[  4706.896] 
X.Org X Server 1.16.0
Release Date: 2014-07-16
[  4706.896] X Protocol Version 11, Revision 0
[  4706.896] Build Operating System: Linux 3.14-1-amd64 x86_64 Debian
[  4706.896] Current Operating System: Linux sypialnia 3.14-2-amd64 #1 SMP 
Debian 3.14.15-2 (2014-08-09) x86_64
[  4706.896] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 
root=UUID=e129d003-4dda-476d-bd58-b7b00c3e0abe ro initrd=/install/initrd.gz 
quiet
[  4706.896] Build Date: 17 July 2014  10:22:36PM
[  4706.896] xorg-server 2:1.16.0-1 (http://www.debian.org/support) 
[  4706.896] Current version of pixman: 0.32.6
[  4706.896]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  4706.896] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  4706.897] (==) Log file: /var/log/Xorg.0.log, Time: Tue Aug 12 10:52:55 
2014
[  4706.897] (==) Using system config directory /usr/share/X11/xorg.conf.d
[  4706.897] (==) No Layout section.  Using the first Screen section.
[  4706.897] (==) No screen section available. Using defaults.
[  4706.897] (**) |--Screen Default Screen Section (0)
[  4706.897] (**) |   |--Monitor default monitor
[  4706.897] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[  4706.897] (==) Automatically adding devices
[  4706.897] (==) Automatically enabling devices
[  4706.897] (==) Automatically adding GPU devices
[  4706.897] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[  4706.897]Entry deleted from font path.
[  4706.897] (==) 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,
built-ins
[  4706.897] (==) ModulePath set to /usr/lib/xorg/modules
[  4706.897] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  4706.897] (II) Loader magic: 0x7fcf526a2d80
[  4706.897] (II) Module ABI versions:
[  4706.897]X.Org ANSI C Emulation: 0.4
[  4706.897]X.Org Video Driver: 18.0
[  4706.897]X.Org XInput driver : 21.0
[  4706.897]X.Org Server Extension : 8.0
[  4706.897] (II) xfree86: Adding drm device (/dev/dri/card0)
[  4706.899] (--) PCI:*(0:1:0:0) 1002:6758:1458:2545 rev 0, Mem @ 
0xd000/268435456, 0xfebe/131072, I/O @ 0xd000/256, BIOS @ 
0x/131072
[  4706.899] (II) LoadModule: glx
[  4706.899] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  4706.900] (II) Module glx: vendor=X.Org Foundation
[  4706.900]compiled for 1.16.0, module version = 1.0.0
[  4706.900]ABI class: X.Org Server Extension, version 8.0
[  4706.900] (==) AIGLX enabled
[  4706.900] (==) Matched ati as autoconfigured driver 0
[  4706.900] (==) Matched ati as autoconfigured driver 1
[  4706.900] (==) Matched modesetting as autoconfigured driver 2
[  4706.900] (==) Matched fbdev as autoconfigured driver 3
[  4706.900] (==) Matched vesa as autoconfigured driver 4
[  4706.900] (==) Assigned the driver to the xf86ConfigLayout
[  4706.900] (II) LoadModule: ati
[  4706.900] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[  4706.900] (II) Module ati: vendor=X.Org Foundation
[  4706.900]compiled for 1.15.99.904, module version = 7.4.0
[  4706.900]Module class: X.Org Video Driver
[  4706.900]ABI class: X.Org Video Driver, version 18.0
[  4706.900] (II) LoadModule: radeon
[  4706.900] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[  4706.900] (II) Module radeon: vendor=X.Org Foundation
[  4706.900]compiled for 1.15.99.904, module version = 7.4.0
[  4706.900]Module class: X.Org Video Driver
[  4706.900]ABI class: X.Org Video Driver, version 18.0
[  4706.900] (II) LoadModule: modesetting
[  4706.900] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  4706.900] (II) Module modesetting: vendor=X.Org Foundation
[  4706.900]compiled for 1.15.99.904, module version = 0.9.0
[  4706.900]Module class: X.Org Video Driver
[  4706.900

Bug#757982: xserver segmentation fault

[Michel Dänzer]

On 13.08.2014 09:37, repron wrote:
 
 [  5884.303] (EE) Backtrace:
 [  5884.303] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x7fcf5241b3f9]
 [  5884.303] (EE) 1: /usr/bin/X (0x7fcf5227+0x1af469) [0x7fcf5241f469]
 [  5884.304] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcf4ff78000+0x35480) 
 [0x7fcf4ffad480]
 [  5884.304] (EE) 3: /usr/bin/X (0x7fcf5227+0x12b70d) [0x7fcf5239b70d]
 [  5884.304] (EE) 4: /usr/bin/X (0x7fcf5227+0x55ee7) [0x7fcf522c5ee7]
 [  5884.304] (EE) 5: /usr/bin/X (0x7fcf5227+0x59f16) [0x7fcf522c9f16]
 [  5884.304] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
 [0x7fcf4ff99b45]
 [  5884.304] (EE) 7: /usr/bin/X (0x7fcf5227+0x4549e) [0x7fcf522b549e]
 [  5884.304] (EE) 
 [  5884.304] (EE) Segmentation fault at address 0x0
 [  5884.304] (EE) 
 Fatal server error:
 [  5884.304] (EE) Caught signal 11 (Segmentation fault). Server aborting

It would be good to see a full backtrace from gdb, but this doesn't look
directly related to the driver.


-- 
Earthling Michel Dänzer|  http://www.amd.com
Libre software enthusiast  |Mesa and X developer

___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

Segmentation Fault on X server while Guvcview is capturing video.

[Gustavo Duarte]

Hi folks

I'm having a random problem, when i'm capturing video using guvcview,
sometimes, the sessions is closed.

Taking a look on Xorg.0.log I'm seeing a segmentation fault.

Could anybody address me where is the best place to find out a solution for
that ?

Bellow are the latest lines of Xorg.O.log.old.



[  1648.239] (II) intel(0): Modeline 1024x600x0.0   54.20  1024 1048 1184
1344  600 603 609 670 -hsync -vsync (40.3 kHz eP)
[  1665.125] (II) intel(0): EDID vendor SEC, prod id 12336
[  1665.125] (II) intel(0): Printing DDC gathered Modelines:
[  1665.125] (II) intel(0): Modeline 1024x600x0.0   54.20  1024 1048 1184
1344  600 603 609 670 -hsync -vsync (40.3 kHz eP)
[  2025.019] (II) XKB: reuse xkmfile
/var/lib/xkb/server-0207BD317285BAB8C582C092D73D9AF2E4A9FCF5.xkm
[  2076.470] (EE)
[  2076.470] (EE) Backtrace:
[  2076.471] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb7716eb9]
[  2076.471] (EE) 1: /usr/bin/X (0xb755f000+0x1bbcba) [0xb771acba]
[  2076.472] (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb753c40c]
[  2076.472] (EE) 3: /lib/i386-linux-gnu/libc.so.6 (0xb7197000+0x1374ed)
[0xb72ce4ed]
[  2076.472] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so
(0xb6ebc000+0x9d26d) [0xb6f5926d]
[  2076.472] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so
(0xb6ebc000+0x9fae2) [0xb6f5bae2]
[  2076.472] (EE) 6: /usr/bin/X (0xb755f000+0x9e550) [0xb75fd550]
[  2076.473] (EE) 7: /usr/bin/X (XvdiPutImage+0x20f) [0xb764e1df]
[  2076.473] (EE) 8: /usr/bin/X (0xb755f000+0xf240f) [0xb765140f]
[  2076.473] (EE) 9: /usr/bin/X (ProcXvDispatch+0x3b) [0xb7652b5b]
[  2076.473] (EE) 10: /usr/bin/X (0xb755f000+0x3c55d) [0xb759b55d]
[  2076.474] (EE) 11: /usr/bin/X (0xb755f000+0x299ac) [0xb75889ac]
[  2076.474] (EE) 12: /lib/i386-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0xb71b04d3]
[  2076.474] (EE) 13: /usr/bin/X (0xb755f000+0x29d69) [0xb7588d69]
[  2076.474] (EE)
[  2076.475] (EE) Segmentation fault at address 0xb66a4000
[  2076.475]
Fatal server error:
[  2076.475] Caught signal 11 (Segmentation fault). Server aborting
[  2076.475]
[  2076.475] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[  2076.475] (EE) Please also check the log file at /var/log/Xorg.0.log
for additional information.
[  2076.475] (EE)
[  2076.496] (II) evdev: Power Button: Close
[  2076.497] (II) UnloadModule: evdev
[  2076.512] (II) evdev: Video Bus: Close
[  2076.513] (II) UnloadModule: evdev
[  2076.528] (II) evdev: Power Button: Close
[  2076.528] (II) UnloadModule: evdev
[  2076.529] (II) evdev: cmpc_keys: Close
[  2076.530] (II) UnloadModule: evdev
[  2076.531] (II) evdev: Sleep Button: Close
[  2076.531] (II) UnloadModule: evdev
[  2076.532] (II) evdev: USB 2.0 Camera: Close
[  2076.532] (II) UnloadModule: evdev
[  2076.533] (II) evdev: AT Translated Set 2 keyboard: Close
[  2076.533] (II) UnloadModule: evdev
[  2076.536] (II) UnloadModule: synaptics
[  2076.537] (II) AIGLX: Suspending AIGLX clients for VT switch
[  2076.605] Server terminated with error (1). Closing log file.


Thanks in advance.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Re: Caught signal 11 (Segmentation fault). Server aborting

[christophe . jarry]

I finally got this segmentation fault problem fixed.
I uninstalled the following drivers:

xf86-input-keyboard-1.7.0
xf86-input-mouse-1.9.0
xf86-input-synaptics-1.7.1
xf86-video-ati-7.2.0
xf86-video-modesetting-0.8.0
xf86-video-vesa-2.3.3

Only the two drivers below remained:

xf86-input-evdev-2.8.2
xf86-video-fbdev-0.4.4

Now, startx works as expected.

I think the segmentation fault I had came from the ati video
driver. Because I use the kernel Linux-libre
(http://www.fsfla.org/ikiwiki/selibre/linux-libre/) from which binary
blobs and non-free files are removed, the binary firmware
(firmware/radeon in the kernel Linux sources) used by the ati video
driver to provide hardware acceleration was not present, hence the
segmentation fault.

Christophe

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Caught signal 11 (Segmentation fault). Server aborting

[Christophe Jarry]

I followed Version 1 of
http://www.x.org/wiki/Development/Documentation/ServerDebugging/#OneMachine and
the complete gdb_log.1034 is attached. The interesting part of this file seems
to be:

Program received signal SIGSEGV, Segmentation fault.
0x2b25060c in memset () from /lib/libc.so.6
#0  0x2b25060c in memset () from /lib/libc.so.6
No symbol table info available.
#1  0x2b4bafd0 in drmmode_copy_fb (pScrn=0x1024cbb0, drmmode=optimized out)
at drmmode_display.c:434 xf86_config = optimized out
info = 0x1024d0c8
src = 0x10228c58 serverClient
dst = optimized out
pScreen = 0x10252760
fbcon_id = optimized out
i = optimized out
pitch = optimized out
tiling_flags = 0
ret = optimized out
#2  0x2b4bc214 in drmmode_set_desired_modes (pScrn=0x1024cbb0,
drmmode=0x1024d240) at drmmode_display.c:1823 config = 0x1024e9a0
c = optimized out
#3  0x2b4b559c in RADEONCreateScreenResources_KMS (pScreen=0x10252760) at
radeon_kms.c:223 pScrn = 0x1024cbb0
info = 0x1024d0c8
pixmap = optimized out
#4  0x100c7198 in xf86CrtcCreateScreenResources (screen=0x10252760) at
xf86Crtc.c:707 scrn = optimized out
config = optimized out
#5  0x10021f54 in main (argc=1, argv=0x7faa81c4, envp=optimized out) at
main.c:225 pScreen = 0x10252760
i = optimized out
alwaysCheckForInput = {0, 1}
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/Xorg (xorg_backtrace+0x68) [0x101d29a8]
(EE) 
(EE) Segmentation fault at address 0x0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at /var/log/Xorg.0.log for additional
information. (EE) 
(EE) Server terminated with error (1). Closing log file.

Program received signal SIGABRT, Aborted.
0x2b1fa578 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:66
66  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.

Does someone understand where the problem comes from?

Thans,

Christophe

gdb_log.1034
Description: Binary data
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Caught signal 11 (Segmentation fault). Server aborting

[christophe . jarry]

Dear list,

I built Xorg and dependancies. When I try to launch X with startx, it does not  
start.

The failure message in /var/log/Xorg.0.log is:

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x68) [0x10194fd8]

Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

The complete Xorg.0.log is attached.

Do you know how to fix this issue?

Thanks,

Christophe

Xorg.0.log
Description: Binary data
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #12 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #10)
 radeonsi_drv.so belongs to x11-drivers/xf86-video-ati-7.0.0
[...]
 /usr/lib64/xorg/modules/drivers/radeon_drv.so

radeonsi_drv.so != radeon_drv.so

Frankly, your distro shouldn't ship the former at all at this point. It
definitely can't properly support your card.

xf86-video-ati 7.0.0 doesn't support your card yet either, you need 7.2.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #13 from Tom neatno...@gmail.com ---
Created attachment 85315
  -- https://bugs.freedesktop.org/attachment.cgi?id=85315action=edit
Xorg radeon_drv.so

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #14 from Michel Dänzer mic...@daenzer.net ---
More distro / setup issues:

Looks like your X server loads the glx module ahead of time by default, which
is known to break glamor. You'll have to talk to Gentoo folks about how to fix
this.

Also, glamor was built with GLES2 support, which is bad. This may be partly due
to your USE flags containing gles2 and/or gles.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #15 from Tom neatno...@gmail.com ---
(In reply to comment #14)
 More distro / setup issues:
 
 Looks like your X server loads the glx module ahead of time by default,
 which is known to break glamor. You'll have to talk to Gentoo folks about
 how to fix this.
 
 Also, glamor was built with GLES2 support, which is bad. This may be partly
 due to your USE flags containing gles2 and/or gles.

Ok, I finally got it working. 2D metacity desktop works good, compiz desktop
too (except the window shadows that are not rendered). There is a problem with
stability - any use of 3d acceleration (even in 2D desktop environment) in web
browser, compiz, glxgears, basic games leads to GPU hang/freeze for about 0.5
minute. Could it be a kernel issue or userspace mesa issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

Michel Dänzer mic...@daenzer.net changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #16 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #15)
 There is a problem with stability - any use of 3d acceleration (even in 2D
 desktop environment) in web browser, compiz, glxgears, basic games leads to
 GPU hang/freeze for about 0.5 minute. Could it be a kernel issue or userspace
 mesa issue?

We are currently investigating this, so far it looks like it's most likely a
Mesa / libdrm issue.

Please file another report for tracking that though, I'm closing this one as
there was no bug here.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

Tom neatno...@gmail.com changed:

   What|Removed |Added

   Priority|medium  |high

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

Alex Deucher ag...@yahoo.com changed:

   What|Removed |Added

   Priority|high|medium

--- Comment #3 from Alex Deucher ag...@yahoo.com ---
I think you'll need a newer version of llvm.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #2 from Tom neatno...@gmail.com ---
Created attachment 85259
  -- https://bugs.freedesktop.org/attachment.cgi?id=85259action=edit
xorg.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] New: X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

  Priority: medium
Bug ID: 68984
  Assignee: xorg-driver-ati@lists.x.org
   Summary: X11 doesn't start, Segmentation fault when using
Radeon BONAIRE 7790 graphics card
QA Contact: xorg-t...@lists.x.org
  Severity: major
Classification: Unclassified
OS: Linux (All)
  Reporter: neatno...@gmail.com
  Hardware: x86-64 (AMD64)
Status: NEW
   Version: 7.0.0
 Component: Driver/Radeon
   Product: xorg

Created attachment 85257
  -- https://bugs.freedesktop.org/attachment.cgi?id=85257action=edit
Xorg log

Hello, I've recently switched graphics card from Radeon 4850 to Radeon 7790
(BONAIRE). Xorg doesn't work with a new card. Probably, the reason of crashing
Xorg is an older package that doesn't include support of 7790 GPUs. I have no
idea which one that could be (xorg log points to crashing dri2 module). I'm
using distribution Gentoo Linux. I've rebuilt packages with radeonsi, glamor,
opencl, llvm-compiler flags.
When I startx manually, I also get:

'bonaire' is not a recognized processor for this target
'bonaire' is not a recognized processor for this target
'bonaire' is not a recognized processor for this target
Stack dump:
0. Running pass 'Function Pass Manager' on module 'tgsi'
1. Running passs 'AMDGPU DAG-DAG Pattern Instruction Selection' on function
'@main'

Installed packages' versions:
- kernel 3.11
- xorg-server 1.13.4 (also failed with 1.14.2.902)
- xf86-video-ati 7.0.0 (built with glamor, udev) (also failed with version
7.2.0)
- glamor 0.5
- mesa 9.2.0 (built with egl, opencl, llvm-compiler, vdpau, radeonsi)
- libdrm 2.4.46

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #5 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #4)
 (In reply to comment #3)
  I think you'll need a newer version of llvm.
 
 I forgot to write llvm version, It is llvm 3.3. Should I install llvm from
 git?

Yes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #4 from Tom neatno...@gmail.com ---
(In reply to comment #3)
 I think you'll need a newer version of llvm.

I forgot to write llvm version, It is llvm 3.3. Should I install llvm from git?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #8 from Alex Deucher ag...@yahoo.com ---
Does updating to glamor 0.5.1 help?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #9 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #8)
 - xf86-video-ati 7.0.0 (built with glamor, udev) (also failed with version
 7.2.0)

The attached Xorg.0.log shows you're not using radeon_drv.so from
xf86-video-ati but radeonsi_drv.so from Mesa. Please make sure you're using the
former from xf86-video-ati 7.2.0.


 - glamor 0.5

I strongly recommend a newer version of glamor as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #6 from Tom neatno...@gmail.com ---
It after update to the latest llvm, I'm back again on Linux, but... there are
lots of graphic artifacts.
On 2D desktop (gnome 2 metacity):
- mouse cursor is displayed with artifacts
- metacity itself doesn't load a right theme (gnome settings deamon
crash/problem, even with a newly created user)
- not readable sites in google chrome (hardware acceleration problem)
- while moving windows it refreshes so slowly (like without any hardware
acceleration)

On 3d desktop (gnome 2 compiz)
- completely not readable whole desktop (windows, task bars, etc.)
- also the theme problem
I'm attaching a screenshot

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #7 from Tom neatno...@gmail.com ---
Created attachment 85266
  -- https://bugs.freedesktop.org/attachment.cgi?id=85266action=edit
compiz desktop

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #10 from Tom neatno...@gmail.com ---
(In reply to comment #9)
 (In reply to comment #8)
  - xf86-video-ati 7.0.0 (built with glamor, udev) (also failed with version
  7.2.0)
 
 The attached Xorg.0.log shows you're not using radeon_drv.so from
 xf86-video-ati but radeonsi_drv.so from Mesa. Please make sure you're using
 the former from xf86-video-ati 7.2.0.
 
 
  - glamor 0.5
 
 I strongly recommend a newer version of glamor as well.

radeonsi_drv.so belongs to x11-drivers/xf86-video-ati-7.0.0

 * Contents of x11-drivers/xf86-video-ati-7.0.0:
/usr
/usr/lib64
/usr/lib64/xorg
/usr/lib64/xorg/modules
/usr/lib64/xorg/modules/drivers
/usr/lib64/xorg/modules/drivers/ati_drv.so
/usr/lib64/xorg/modules/drivers/radeon_drv.so
/usr/share
/usr/share/doc
/usr/share/doc/xf86-video-ati-7.0.0
/usr/share/doc/xf86-video-ati-7.0.0/ChangeLog.bz2

the update to glamor 0.5.1 didn't change anything

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 68984] X11 doesn't start, Segmentation fault when using Radeon BONAIRE 7790 graphics card

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=68984

--- Comment #11 from Tom neatno...@gmail.com ---
The command X -configure suggests X11 driver options: ati, r600g, radeon,
radeonsi. The one that only works is radeonsi.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

Michel Dänzer mic...@daenzer.net changed:

   What|Removed |Added

   Assignee|xorg-driver-ati@lists.x.org |zhigang.g...@gmail.com
 QA Contact|xorg-t...@lists.x.org   |
  Component|Driver/Radeon   |Driver/glamor

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

--- Comment #4 from Bryce Harrington b.harring...@samsung.com ---
xTrapezoidValid() is:

#define xTrapezoidValid(t)  ((t)-left.p1.y != (t)-left.p2.y  \
 (t)-right.p1.y != (t)-right.p2.y  \
 (int) ((t)-bottom - (t)-top)  0)

Maybe try printing out traps when it's in a crashed state?  (Doing a 'bt full'
after a crash would gather values of other variables that might be of interest
too.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

--- Comment #3 from Mauro Carvalho Chehab mche...@infradead.org ---
Created attachment 83300
  -- https://bugs.freedesktop.org/attachment.cgi?id=83300action=edit
Additional dmesg

I did an upgrade to Kernel 10.3 and to the latest radeon firmwares found at
linux-firmware tree.

The bug seems to be happening often when claws-mail is being used, in general
when doing operations that would require it to popup some selection box.

I'm enclosing the dmesg after one of such crashes.

Sometimes, the bug is serious enough to hang up the system. Other times, it
affects only the X screen - e. g. switching to a console window works, but
returning back to X doesn't.

At X, it enters into a loop where the screen disappears for a while... then it
returns to show the last image for a while and everything happens again.
Most of the time, the machine is still live, and can be accessed via ssh.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

Philipp Knechtges philipp-...@knechtges.com changed:

   What|Removed |Added

 CC||philipp-...@knechtges.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

Alex B alex.teor...@gmail.com changed:

   What|Removed |Added

 CC||alex.teor...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66796] radeon dual card configure segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66796

Michel Dänzer mic...@daenzer.net changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #2 from Michel Dänzer mic...@daenzer.net ---
Xorg -configure shouldn't be used anymore. No xorg.conf is needed in most
cases, and in other cases a minimal xorg.conf can be used these days.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66796] New: radeon dual card configure segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66796

  Priority: medium
Bug ID: 66796
  Assignee: xorg-driver-ati@lists.x.org
   Summary: radeon dual card configure segmentation fault
QA Contact: xorg-t...@lists.x.org
  Severity: normal
Classification: Unclassified
OS: Linux (All)
  Reporter: dua...@gmail.com
  Hardware: x86-64 (AMD64)
Status: NEW
   Version: unspecified
 Component: Driver/Radeon
   Product: xorg

Created attachment 82298
  -- https://bugs.freedesktop.org/attachment.cgi?id=82298action=edit
lspci, Xorg.*.log, dmesg

Xorg exhibits 3 problems possibly because of Dual 4550 Radeon cards.
1) (this bug report)  Xorg -configure   ends with segmentation violation.
2) Not using mode 1920x1080 (height too large for virtual size).
3) (after #2 is fixed)  xrandr -q   lists only one card.
(search for me dua...@gmail.com to find other possibly related bug reports)


# uname -a
Linux lavoe 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:45:16 CEST 2013 x86_64
GNU/Linux
# pacman -Q ...
xorg-server 1.14.2-2
xorg-server-common 1.14.2-2
ati-dri 9.1.4-3
xf86-video-ati 1:7.1.0-3


# Xorg :1 -configure
X.Org X Server 1.14.2
Release Date: 2013-06-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.9.7-1-ARCH x86_64
Current Operating System: Linux lavoe 3.9.8-1-ARCH #1 SMP PREEMPT Thu Jun 27
21:37:31 CEST 2013 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=e689f6d7 ro
quiet
Build Date: 01 July 2013  10:48:42AM

Current version of pixman: 0.30.0
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.1.log, Time: Wed Jul 10 10:58:58 2013
List of video drivers:
ati
radeon
(++) Using config file: /root/xorg.conf.new
(==) Using config directory: /etc/X11/xorg.conf.d
(==) Using system config directory /usr/share/X11/xorg.conf.d
(II) [KMS] Kernel modesetting enabled.
(II) [KMS] Kernel modesetting enabled.
(EE)
(EE) Backtrace:
(EE) 0: Xorg (xorg_backtrace+0x3d) [0x57f71d]
(EE) 1: Xorg (0x40+0x183489) [0x583489]
(EE) 2: /usr/lib/libpthread.so.0 (0x7f97d7fb1000+0xf0e0) [0x7f97d7fc00e0]
(EE) 3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f97d4057000+0x440b4)
[0x7f97d409b0b4]
(EE) 4: Xorg (DoConfigure+0xd46) [0x469426]
(EE) 5: Xorg (0x40+0x7869a) [0x47869a]
(EE) 6: Xorg (0x40+0x266d0) [0x4266d0]
(EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f97d6e2ca15]
(EE) 8: Xorg (0x40+0x26bfd) [0x426bfd]
(EE)
(EE) Segmentation fault at address 0x18
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66796] radeon dual card configure segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66796

--- Comment #1 from Duane Voth dua...@gmail.com ---
The other possibly related bug reports are:
https://bugs.freedesktop.org/show_bug.cgi?id=66799
https://bugs.freedesktop.org/show_bug.cgi?id=66801

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] New: X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

  Priority: medium
Bug ID: 66515
  Assignee: xorg-driver-ati@lists.x.org
   Summary: X is crashing with segmentation fault
QA Contact: xorg-t...@lists.x.org
  Severity: normal
Classification: Unclassified
OS: All
  Reporter: mche...@infradead.org
  Hardware: Other
Status: NEW
   Version: git
 Component: Driver/Radeon
   Product: xorg

Created attachment 81896
  -- https://bugs.freedesktop.org/attachment.cgi?id=81896action=edit
Crash backtrace with a gdb list of the called functions

From time to time, I'm getting crashes while using Xorg with the radeon driver
and 3 monitors.

The crash happens randomly. It was noticed twice today, one while running
firefox/Java. The second one while editing an email on claws-mail.

I'm running Fedora 19, with the following packages:

xorg-x11-server-Xorg-1.14.1-4.fc19.x86_64
xorg-x11-drv-ati-7.1.0-5.20130408git6e74aacc5.fc19.x86_64
xorg-x11-glamor-0.5.0-5.20130401git81aadb8.fc19.x86_64
xorg-x11-glamor-debuginfo-0.5.0-5.20130401git81aadb8.fc19.x86_64
kernel-3.9.6-200.fc18.x86_64

Xorg relevant most relevant log:

[  2928.438] (EE) Backtrace:
[  2928.439] (EE) 0: /usr/bin/X (OsLookupColor+0x129) [0x46e539]
[  2928.439] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x396c60ef9f]
[  2928.439] (EE) 2: /usr/bin/X (miTrapezoidBounds+0x7d) [0x51262d]
[  2928.439] (EE) 3: /lib64/libglamor.so.0 (glamor_composite_rects_nf+0x4540)
[0x7f894a185710]
[  2928.439] (EE) 4: /usr/bin/X (AddTraps+0x46f3) [0x51ecb3]
[  2928.439] (EE) 5: /usr/bin/X (SendErrorToClient+0x3f7) [0x436e47]
[  2928.439] (EE) 6: /usr/bin/X (_init+0x3ab2) [0x429ae2]
[  2928.439] (EE) 7: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x396be21b75]
[  2928.440] (EE) 8: /usr/bin/X (_start+0x29) [0x426741]
[  2928.440] (EE) 9: ? (?+0x29) [0x29]

PS.: when the system boots, I suspect that the X server crashes, and then it
re-starts.

Every time a crash happens, it seems

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

--- Comment #1 from Mauro Carvalho Chehab mche...@infradead.org ---
Created attachment 81897
  -- https://bugs.freedesktop.org/attachment.cgi?id=81897action=edit
Radeon dmesg stuff

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

--- Comment #2 from Mauro Carvalho Chehab mche...@infradead.org ---
Created attachment 81898
  -- https://bugs.freedesktop.org/attachment.cgi?id=81898action=edit
Xorg.0.log

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 66515] X is crashing with segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=66515

raj...@gmail.com changed:

   What|Removed |Added

 CC||raj...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 56986] xf86-video-ati 7.0.0.-1: segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=56986

Michel Dänzer mic...@daenzer.net changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
   Assignee|xorg-driver-ati@lists.x.org |xorg-t...@lists.x.org
  Component|Driver/Radeon   |Server/DDX/Xorg

--- Comment #24 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #21)
 Just updated to xorg-server 1.13.1 and this solved the issue for me, now
 radeon drivers version 7.0.0 run fine here - does anybody still have
 problems with radeon or can the status be set to resolved?

As the submitter of this report, you don't need to ask anyone. :)

Those still having problems should create separate reports.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 56986] xf86-video-ati 7.0.0.-1: segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=56986

--- Comment #21 from Mathias Anselmann mathias.anselm...@linux.com ---
Just updated to xorg-server 1.13.1 and this solved the issue for me, now radeon
drivers version 7.0.0 run fine here - does anybody still have problems with
radeon or can the status be set to resolved?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 56986] xf86-video-ati 7.0.0.-1: segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=56986

--- Comment #22 from Adam Reichold adamreich...@myopera.com ---
(In reply to comment #21)
 Just updated to xorg-server 1.13.1 and this solved the issue for me, now
 radeon drivers version 7.0.0 run fine here - does anybody still have
 problems with radeon or can the status be set to resolved?

For me, the problem persists using version 1.13.1 of the X server.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

[Bug 56986] xf86-video-ati 7.0.0.-1: segmentation fault

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=56986

--- Comment #23 from phanisvara das listm...@phanisvara.com ---
for me the latest xorg-server (1.13.1) fixes the problem.

(Advanced Micro Devices [AMD] nee ATI Whistler LE [AMD Radeon HD 6625M
on 3.7.0-1-ARCH / x86_64)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati

Re: Segmentation fault

[stompdagg...@yahoo.com]

On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: 

 On Sun, Dec 9, 2012 at 12:16 PM,  olivier.e.am...@gmail.com wrote:
  When starting openSuse 12.2, the X-server terminates with a
 segmentation fault (see attached log file).
 
 The open source driver should support your card just fine.  Can you
 install debugging symbols and get a proper backtrace with GDB?
 http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
 
 Alex, looking at his log, I don't see the card in the support list,
 his card is the v7700?

As you can see in the lspci output, it's a 7500, which is Turks
(Northern Islands generation) based.

If the driver didn't support the card, it would bail much earlier. 

looking at the xorg log, I see Turks only as part of the AMD Radeon HD 6700 
Series, does this means that 7500 Series is part of the 6700 Series?___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Segmentation fault

[stompdagg...@yahoo.com]

On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: 

 On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: 
  On Sun, Dec 9, 2012 at 12:16 PM,  olivier.e.am...@gmail.com
 wrote:
   When starting openSuse 12.2, the X-server terminates with a
  segmentation fault (see attached log file).
  
  The open source driver should support your card just fine.  Can
 you
  install debugging symbols and get a proper backtrace with GDB?
  http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
  
  Alex, looking at his log, I don't see the card in the support list,
  his card is the v7700?
 
 As you can see in the lspci output, it's a 7500, which is Turks
 (Northern Islands generation) based.
 
 If the driver didn't support the card, it would bail much earlier. 
 
 looking at the xorg log, I see Turks only as part of the AMD Radeon HD
 6700 Series, does this means that 7500 Series is part of the 6700
 Series?

It's complicated. :\

7xx0 and 6xx0 are marketing names, which are mostly irrelevant for
driver support, in contrast to code names such as Turks, Northern
Islands etc.

I see, so maybe it is a good idea to fix the radeon output? if I had this 
problem, I'd assume that the driver doesn't supports the card, this would have 
wasted a lot of time.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Segmentation fault

[Michel Dänzer]

On Die, 2012-12-11 at 02:48 -0800, stompdagg...@yahoo.com wrote: 
 On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: 
  On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: 
   On Sun, Dec 9, 2012 at 12:16 PM,  olivier.e.am...@gmail.com
  wrote:
When starting openSuse 12.2, the X-server terminates with a
   segmentation fault (see attached log file).
   
   The open source driver should support your card just fine.  Can
  you
   install debugging symbols and get a proper backtrace with GDB?
  
 http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
   
   Alex, looking at his log, I don't see the card in the support
 list,
   his card is the v7700?
  
  As you can see in the lspci output, it's a 7500, which is Turks
  (Northern Islands generation) based.
  
  If the driver didn't support the card, it would bail much
 earlier. 
  
  looking at the xorg log, I see Turks only as part of the AMD Radeon
 HD
  6700 Series, does this means that 7500 Series is part of the 6700
  Series?
 
 It's complicated. :\
 
 7xx0 and 6xx0 are marketing names, which are mostly irrelevant for
 driver support, in contrast to code names such as Turks, Northern
 Islands etc.
 
 I see, so maybe it is a good idea to fix the radeon output?

Can you make a specific suggestion, or even a patch?


 if I had this problem, I'd assume that the driver doesn't supports the
 card, this would have wasted a lot of time.

Why would you assume that? Again, if the driver doesn't support a card,
it bails much earlier, in a totally different way. 

-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast |  Debian, X and DRI developer
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Segmentation fault

[Alex Deucher]

On Tue, Dec 11, 2012 at 5:48 AM, stompdagg...@yahoo.com
stompdagg...@yahoo.com wrote:
On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote:
 On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
  On Sun, Dec 9, 2012 at 12:16 PM,  olivier.e.am...@gmail.com
 wrote:
   When starting openSuse 12.2, the X-server terminates with a
  segmentation fault (see attached log file).
 
  The open source driver should support your card just fine.  Can
 you
  install debugging symbols and get a proper backtrace with GDB?
  http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
 
  Alex, looking at his log, I don't see the card in the support list,
  his card is the v7700?

 As you can see in the lspci output, it's a 7500, which is Turks
 (Northern Islands generation) based.

 If the driver didn't support the card, it would bail much earlier.

 looking at the xorg log, I see Turks only as part of the AMD Radeon HD
 6700 Series, does this means that 7500 Series is part of the 6700
 Series?

It's complicated. :\

7xx0 and 6xx0 are marketing names, which are mostly irrelevant for
driver support, in contrast to code names such as Turks, Northern
Islands etc.

 I see, so maybe it is a good idea to fix the radeon output? if I had this
 problem, I'd assume that the driver doesn't supports the card, this would
 have wasted a lot of time.


Marketing and OEMs come up with so many different names, it's hard to
keep track.  Best bet it to look at the pci ids, or check wikipedia:
http://en.wikipedia.org/wiki/Ati_gpu

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Segmentation fault

[stompdagg...@yahoo.com]

On Tue, Dec 11, 2012 at 5:48 AM, stompdagg...@yahoo.com 
stompdagg...@yahoo.com wrote:
On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote:
 On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
  On Sun, Dec 9, 2012 at 12:16 PM,  olivier.e.am...@gmail.com
 wrote:
   When starting openSuse 12.2, the X-server terminates with a
  segmentation fault (see attached log file).
 
  The open source driver should support your card just fine.  Can
 you
  install debugging symbols and get a proper backtrace with GDB?
  http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
 
  Alex, looking at his log, I don't see the card in the support list,
  his card is the v7700?

 As you can see in the lspci output, it's a 7500, which is Turks
 (Northern Islands generation) based.

 If the driver didn't support the card, it would bail much earlier.

 looking at the xorg log, I see Turks only as part of the AMD Radeon HD
 6700 Series, does this means that 7500 Series is part of the 6700
 Series?

It's complicated. :\

7xx0 and 6xx0 are marketing names, which are mostly irrelevant for
driver support, in contrast to code names such as Turks, Northern
Islands etc.

 I see, so maybe it is a good idea to fix the radeon output? if I had this
 problem, I'd assume that the driver doesn't supports the card, this would
 have wasted a lot of time.


Marketing and OEMs come up with so many different names, it's hard to
keep track.  Best bet it to look at the pci ids, or check wikipedia:
http://en.wikipedia.org/wiki/Ati_gpu

Alex

I see, thanks for the explanation.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Segmentation fault

[Alex Deucher]

On Sun, Dec 9, 2012 at 12:16 PM,  olivier.e.am...@gmail.com wrote:
 When starting openSuse 12.2, the X-server terminates with a segmentation 
 fault (see attached log file).

The open source driver should support your card just fine.  Can you
install debugging symbols and get a proper backtrace with GDB?
http://wiki.x.org/wiki/Development/Documentation/ServerDebugging

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com