All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81907] New: Unreal Engine "Effects Cave" Demo crashes in __memcpy_sse2_unaligned
Date: Wed, 30 Jul 2014 08:43:54 +0000	[thread overview]
Message-ID: <bug-81907-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2247 bytes --]

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

          Priority: medium
            Bug ID: 81907
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Unreal Engine "Effects Cave" Demo crashes in
                    __memcpy_sse2_unaligned
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: haagch@frickel.club
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 103673
  --> https://bugs.freedesktop.org/attachment.cgi?id=103673&action=edit
full backtrace

llvm-svn 214022
mesa git master from today without f4b0ab7afd83c811329211eae8167c9bf238870c
linux 3.16-rc7

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Wimbledon XT [Radeon HD 7970M] (rev ff)

intel with render nodes, tearfree and DRI3 and I run it with DRI_PRIME=1.

Because of bug 81834 I reverted f4b0ab7afd83c811329211eae8167c9bf238870c.

Now I get this crash in the "Effects Cave" demo of the unreal engine. More
rarely (?) I get bug 80880 instead/first. In other demos (perhaps less complex)
like TappyChicken I always get bug 80880 and never (?) this crash here:

0x00007ffff6a15859 in __memcpy_sse2_unaligned () from /usr/lib/libc.so.6


It seems to run for a few seconds, the music is playing, but the window
contents are black (it seems nothing at all is rendered, sometimes there are
white stripes that do not vanish until it crashes). Then it crashes with the
attached backtrace.

The "binary" struct seem to be always one of the same few. Others are:

binary = {code = 0x7fffb9ced270
"~\n\376\276\t\003\374\276\002\003\002\310\002\002\006\310\001\001", code_size
= 76, config = 0x7fffb9cf1a90 "(\260", config_size = 24, rodata = 0x0,
rodata_size = 0, disassembled = 0}

and

binary = {code = 0x7fffb9f85a10 "~\n\376\276\t", <incomplete sequence
\374\276>, code_size = 4160, config = 0x7fffb9e33840 "(\260", config_size = 24,
rodata = 0x0, rodata_size = 0, disassembled = 0}

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-07-30  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  8:43 bugzilla-daemon [this message]
2014-07-30  9:04 ` [Bug 81907] Unreal Engine "Effects Cave" Demo crashes with SIGBUS in __memcpy_sse2_unaligned bugzilla-daemon
2014-08-01 10:24 ` bugzilla-daemon
2014-08-01 14:38 ` bugzilla-daemon
2014-08-01 15:31 ` bugzilla-daemon
2014-08-13 10:25 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-81907-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.