From: Zhigang Gong <zhigang.gong@linux.intel.com>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: intel-gfx@lists.freedesktop.org,
"beignet@lists.freedesktop.org" <beignet@lists.freedesktop.org>
Subject: Re: [Intel-gfx] Beignet crashes on vanilla 3.17.1 with IVB hardware
Date: Fri, 24 Oct 2014 17:13:03 +0800 [thread overview]
Message-ID: <20141024091303.GC2987@ivb-gt2-rev4> (raw)
In-Reply-To: <CA+E=qVf2uhv4M-VZNA232zObqWREDg9mpH541mzFadoah5nWWg@mail.gmail.com>
Hi,
Luxmark (both 2.0/2.1) works fine on my IVB machine. The back trace
you provided below doesn't indicate it's a beignet related problem.
It hadn't enter beignet domain and just crashed in luxmark internal.
On Fri, Oct 24, 2014 at 12:04:29PM +0300, Vasily Khoruzhick wrote:
> Hi Zhigang,
>
> Luxmark crashes with following backtrace:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000000004cd8b0 in slg::PathOCLRenderEngine::StopLockLess() ()
> (gdb) bt
> #0 0x00000000004cd8b0 in slg::PathOCLRenderEngine::StopLockLess() ()
> #1 0x0000000000482236 in slg::RenderEngine::Stop() ()
> #2 0x000000000047be9b in slg::RenderSession::~RenderSession() ()
> #3 0x0000000000468a77 in LuxMarkApp::Stop() ()
> #4 0x0000000000468b46 in LuxMarkApp::InitRendering(LuxMarkAppMode,
> char const*) ()
After a quick analysis, I confirm that the second case is indeed a beignet
bug. Beignet lacks of some llvm intrinsics support such as
llvm.uadd.with.overflow.i32().
Will fix it next week.
Thanks,
Zhigang Gong.
>
> And convert from imagemagick crashes in libgbe.so:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007fffeb0df18c in gbe::buildRegInfo(gbe::ir::BasicBlock&,
> gbe::vector<gbe::RegInfoForMov>&) () from /usr/lib/beignet//libgbe.so
> (gdb) bt
> #0 0x00007fffeb0df18c in gbe::buildRegInfo(gbe::ir::BasicBlock&,
> gbe::vector<gbe::RegInfoForMov>&) () from /usr/lib/beignet//libgbe.so
> #1 0x00007fffeb0e048d in
> gbe::GenWriter::removeLOADIs(gbe::ir::Liveness const&,
> gbe::ir::Function&) () from /usr/lib/beignet//libgbe.so
> #2 0x00007fffeb0fb823 in
> gbe::GenWriter::emitFunction(llvm::Function&) () from
> /usr/lib/beignet//libgbe.so
> #3 0x00007fffeb100b63 in
next prev parent reply other threads:[~2014-10-24 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+E=qVd613U6Shw5vqgFNJWyJEkknzZ=hpk5nGgdJacwCe3qPQ@mail.gmail.com>
2014-10-24 2:27 ` [Beignet] Beignet crashes on vanilla 3.17.1 with IVB hardware Zhigang Gong
2014-10-24 7:05 ` Zhigang Gong
2014-10-24 9:04 ` [Intel-gfx] " Vasily Khoruzhick
2014-10-24 9:13 ` Zhigang Gong [this message]
2014-10-24 13:36 ` Vasily Khoruzhick
2014-10-28 4:31 ` Zhigang Gong
2014-10-28 8:31 ` Vasily Khoruzhick
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=20141024091303.GC2987@ivb-gt2-rev4 \
--to=zhigang.gong@linux.intel.com \
--cc=anarsoul@gmail.com \
--cc=beignet@lists.freedesktop.org \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox