Summary: | SIGABRT when starting firefox with debug=full [SNA] | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Clemens Eisserer <linuxhippy> | ||||||
Component: | Driver/intel | Assignee: | Chris Wilson <chris> | ||||||
Status: | RESOLVED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | git | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Clemens Eisserer
2013-06-27 09:05:50 UTC
And please attach the debug log. Created attachment 81538 [details]
debug log
2.21.10-34-g8f6dcc1... Realised my mistake moments before you sent the bug, sorry. Created attachment 81540 [details]
debug log 2
Is this the same issue? Program received signal SIGABRT, Aborted. 0x00000035b9e35819 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt #0 0x00000035b9e35819 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00000035b9e36f28 in __GI_abort () at abort.c:90 #2 0x00000035b9e2e7f6 in __assert_fail_base (fmt=0x35b9f7d2e8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f62f9257aef "bo", file=file@entry=0x7f62f925760e "sna_accel.c", line=line@entry=3889, function=function@entry=0x7f62f925dc00 <__PRETTY_FUNCTION__.25563> "can_upload_tiled_x") at assert.c:92 #3 0x00000035b9e2e8a2 in __GI___assert_fail (assertion=0x7f62f9257aef "bo", file=0x7f62f925760e "sna_accel.c", line=3889, function=0x7f62f925dc00 <__PRETTY_FUNCTION__.25563> "can_upload_tiled_x") at assert.c:101 #4 0x00007f62f913a88f in can_upload_tiled_x (kgem=0x7f62f7873000, priv=0x2deae40) at sna_accel.c:3889 #5 0x00007f62f913aafe in try_upload_tiled_x (pixmap=0x2e26260, region=0x7fff6cf5d810, x=0, y=0, w=669, h=97, bits=0x7f62f6339028 "\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377"..., stride=2676) at sna_accel.c:3955 #6 0x00007f62f913b082 in sna_put_zpixmap_blt (drawable=0x2e26260, gc=0x2e078e0, region=0x7fff6cf5d810, x=0, y=0, w=669, h=97, bits=0x7f62f6339028 "\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377"..., stride=2676) at sna_accel.c:4055 #7 0x00007f62f913c6bc in sna_put_image (drawable=0x2e26260, gc=0x2e078e0, depth=32, x=0, y=0, w=669, h=97, left=0, format=2, bits=0x7f62f6339028 "\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377\210߬\377"...) at sna_accel.c:4433 #8 0x0000000000433cd9 in ProcPutImage (client=0x2df9dc0) at dispatch.c:1966 #9 0x0000000000436df7 in Dispatch () at dispatch.c:432 #10 0x00000000004263fa in main (argc=8, argv=0x7fff6cf5da48, envp=<optimized out>) at main.c:298 :wq Almost... Just the DBG was left broken. Now fixed. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.