Re: [Intel-gfx] Intel Crash

2013-07-17 Thread Chris Wilson 
On Tue, Jul 16, 2013 at 09:51:43PM -0600, Oscar Dario Trujillo Tejada wrote:
I send what you want(I guess), online and as attach
[1]Xorg Log

Found it, we were requesting a upload buffer of size 0, due to using a
bad alignment value as a result of setting a bad default value for
unknown cpu cache size.

Fixed by commit 7f76a2bf319f59d463a1f96974b03d7c651847dd
Author: Chris Wilson ch...@chris-wilson.co.uk
Date:   Wed Jul 17 10:22:17 2013 +0100

sna: Fall back to /proc/cpuinfo parsing if cpuid cache size probe fails
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-17 Thread Oscar Dario Trujillo Tejada 
I updated and all seems to be fine, thanks


2013/7/17 Chris Wilson ch...@chris-wilson.co.uk

 On Tue, Jul 16, 2013 at 09:51:43PM -0600, Oscar Dario Trujillo Tejada
 wrote:
 I send what you want(I guess), online and as attach
 [1]Xorg Log

 Found it, we were requesting a upload buffer of size 0, due to using a
 bad alignment value as a result of setting a bad default value for
 unknown cpu cache size.

 Fixed by commit 7f76a2bf319f59d463a1f96974b03d7c651847dd
 Author: Chris Wilson ch...@chris-wilson.co.uk
 Date:   Wed Jul 17 10:22:17 2013 +0100

 sna: Fall back to /proc/cpuinfo parsing if cpuid cache size probe fails
 -Chris

 --
 Chris Wilson, Intel Open Source Technology Centre

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-16 Thread Chris Wilson 
On Mon, Jul 15, 2013 at 10:23:51PM -0600, Oscar Dario Trujillo Tejada wrote:
I put those commits because in the moment that they have been pushed my
system crash, should I make the bug report in [1]bugs.freedesktop.org or
with the one in the arch bugs, I'm fine?

Neither of those are likely (directly) related to the crash. You want to
run addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x39c1b
0x3e64b 0x3eb3b 0x3ec2f 0x80bfe 0xb4fd4 0xbcb10 0x6a074. If that
reports a lot of '???' install debug symbols and try again.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-16 Thread Oscar Dario Trujillo Tejada 
This is what I got

/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/blt.c:734
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:2602
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:3742
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.h:526
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:1667
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:2608
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:1903
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:14581
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:3062
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:3098
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:305
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:657
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:7355
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:11574
/var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:12497


I don't know if this is usefull


2013/7/16 Chris Wilson ch...@chris-wilson.co.uk

 On Mon, Jul 15, 2013 at 10:23:51PM -0600, Oscar Dario Trujillo Tejada
 wrote:
 I put those commits because in the moment that they have been pushed
 my
 system crash, should I make the bug report in [1]bugs.freedesktop.orgor
 with the one in the arch bugs, I'm fine?

 Neither of those are likely (directly) related to the crash. You want to
 run addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x39c1b
 0x3e64b 0x3eb3b 0x3ec2f 0x80bfe 0xb4fd4 0xbcb10 0x6a074. If that
 reports a lot of '???' install debug symbols and try again.
 -Chris

 --
 Chris Wilson, Intel Open Source Technology Centre

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-16 Thread Chris Wilson 
On Tue, Jul 16, 2013 at 08:13:59AM -0600, Oscar Dario Trujillo Tejada wrote:
This is what I got
 

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/blt.c:734

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:2602

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:3742

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.h:526

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:1667

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:2608

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:1903

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:14581

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:3062

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:3098

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:305

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:657

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:7355

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:11574

 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:12497

Very jumbled, I suspect the debug symbols did not match the stack trace.
Please do recompile your ddx with --enable-debug and see if you can
trigger the fault again. Beware that this will enable assertions and
potentially make the Xserver die much earlier - if you can capture the
fault in gdb (use a second PC!) that would be ideal.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-16 Thread Oscar Dario Trujillo Tejada 
I really hope that this help if don't, I don't know what to do

(EE) Backtrace:
(EE) 0: X (xorg_backtrace+0x49) [0x81d7eb9]
(EE) 1: X (0x8048000+0x193c24) [0x81dbc24]
(EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb77bb40c]
(EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x41ea5)
[0xb70e1ea5]
(EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x4ad4e)
[0xb70ead4e]
(EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x4af0b)
[0xb70eaf0b]
(EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0xa5e16)
[0xb7145e16]
(EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x86053)
[0xb7126053]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x8f0a9)
[0xb712f0a9]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x9f311)
[0xb713f311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0xa29af)
[0xb71429af]
(EE) 11: X (0x8048000+0x113a01) [0x815ba01]
(EE) 12: X (CompositeGlyphs+0xa6) [0x8149f66]
(EE) 13: X (0x8048000+0x10d1cc) [0x81551cc]
(EE) 14: X (0x8048000+0x108c6d) [0x8150c6d]
(EE) 15: X (0x8048000+0x3149d) [0x807949d]
(EE) 16: X (0x8048000+0x1f645) [0x8067645]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf3) [0xb74037c3]
(EE) 18: X (0x8048000+0x1fa19) [0x8067a19]
(EE)
(EE) Segmentation fault at address 0x6efcaf30
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)




2013/7/16 Chris Wilson ch...@chris-wilson.co.uk

 On Tue, Jul 16, 2013 at 08:13:59AM -0600, Oscar Dario Trujillo Tejada
 wrote:
 This is what I got
 
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/blt.c:734
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:2602
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:3742
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.h:526
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:1667
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:2608
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/kgem.c:1903
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:14581
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:3062
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:3098
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:305
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:657
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_trapezoids.c:7355
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:11574
 
  
 /var/abs/local/yaourtbuild/xf86-video-intel-git/src/xf86-video-intel-git/src/sna/sna_accel.c:12497

 Very jumbled, I suspect the debug symbols did not match the stack trace.
 Please do recompile your ddx with --enable-debug and see if you can
 trigger the fault again. Beware that this will enable assertions and
 potentially make the Xserver die much earlier - if you can capture the
 fault in gdb (use a second PC!) that would be ideal.
 -Chris

 --
 Chris Wilson, Intel Open Source Technology Centre

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-16 Thread Chris Wilson 
On Tue, Jul 16, 2013 at 09:58:45AM -0600, Oscar Dario Trujillo Tejada wrote:
I really hope that this help if don't, I don't know what to do
 
(EE) Backtrace:
(EE) 0: X (xorg_backtrace+0x49) [0x81d7eb9]
(EE) 1: X (0x8048000+0x193c24) [0x81dbc24]
(EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb77bb40c]
(EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x41ea5)
[0xb70e1ea5]
(EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x4ad4e)
[0xb70ead4e]
(EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x4af0b)
[0xb70eaf0b]
(EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0xa5e16)
[0xb7145e16]
(EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x86053)
[0xb7126053]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x8f0a9)
[0xb712f0a9]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0x9f311)
[0xb713f311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb70a+0xa29af)
[0xb71429af]
(EE) 11: X (0x8048000+0x113a01) [0x815ba01]
(EE) 12: X (CompositeGlyphs+0xa6) [0x8149f66]
(EE) 13: X (0x8048000+0x10d1cc) [0x81551cc]
(EE) 14: X (0x8048000+0x108c6d) [0x8150c6d]
(EE) 15: X (0x8048000+0x3149d) [0x807949d]
(EE) 16: X (0x8048000+0x1f645) [0x8067645]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf3) [0xb74037c3]
(EE) 18: X (0x8048000+0x1fa19) [0x8067a19]
(EE)
(EE) Segmentation fault at address 0x6efcaf30
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)

Now run please:

addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x41ea5
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x4ad4e
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x4af0b
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0xa5e16
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x86053
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x8f0a9
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x9f311
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0xa29af

And please include the command in the typescript along with the full
Xorg.0.log.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-15 Thread Ben Widawsky 
On Mon, 15 Jul 2013 21:59:09 -0600
Oscar Dario Trujillo Tejada oscard...@gmail.com wrote:

 Sorry about this but, I dont know a better place to send it
 please read the bug report that I put in archlinux bug tracker
 
 https://bugs.archlinux.org/task/36155?project=1cat%5B0%5D=10string=xf86-video-intel
 

I am far from equipped to debug ddx problems without debug symbols,
though Chris can probably make something of it when he wakes up.
Generally you should file bugs on bugs.freedesktop.org - with more or
less what you included.

See:
https://01.org/linuxgraphics/documentation/how-report-bugs-0

I will say that if it is indeed cpuid related - I am going to have a
good, long, laugh. But from the CompositePicture in the bt, I assume
it's unlikely.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Intel Crash

2013-07-15 Thread Oscar Dario Trujillo Tejada 
I put those commits because in the moment that they have been pushed my
system crash, should I make the bug report in bugs.freedesktop.org or with
the one in the arch bugs, I'm fine?


2013/7/15 Ben Widawsky b...@bwidawsk.net

 On Mon, 15 Jul 2013 21:59:09 -0600
 Oscar Dario Trujillo Tejada oscard...@gmail.com wrote:

  Sorry about this but, I dont know a better place to send it
  please read the bug report that I put in archlinux bug tracker
 
 
 https://bugs.archlinux.org/task/36155?project=1cat%5B0%5D=10string=xf86-video-intel
 

 I am far from equipped to debug ddx problems without debug symbols,
 though Chris can probably make something of it when he wakes up.
 Generally you should file bugs on bugs.freedesktop.org - with more or
 less what you included.

 See:
 https://01.org/linuxgraphics/documentation/how-report-bugs-0

 I will say that if it is indeed cpuid related - I am going to have a
 good, long, laugh. But from the CompositePicture in the bt, I assume
 it's unlikely.

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx