From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76046] New: [r600g][RV635][LLVM shader] Chrome aborts GPU acceleration
Date: Tue, 11 Mar 2014 23:14:41 +0000 [thread overview]
Message-ID: <bug-76046-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3047 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76046
Priority: medium
Bug ID: 76046
Assignee: dri-devel@lists.freedesktop.org
Summary: [r600g][RV635][LLVM shader] Chrome aborts GPU
acceleration
Severity: normal
Classification: Unclassified
OS: All
Reporter: shawn.starr@rogers.com
Hardware: Other
Status: NEW
Version: unspecified
Component: Drivers/Gallium/r600
Product: Mesa
Forcing GPU accelration on r600g w/ (now using LLVM R600_LLVM=1 default it
seems) causes an assert to be thrown.
Components:
kernel-3.14.0-0.rc5.git2.2.fc21.x86_64
mesa-dri-drivers-10.1-1.20140305.fc21.x86_64
llvm-libs-3.4-4.fc21.x86_64
libdrm-2.4.52-1.fc21.x86_64
$ google-chrome --ignore-gpu-blacklist &
[1] 6174
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[6206:6206:0311/190002:ERROR:sandbox_linux.cc(268)] InitializeSandbox() called
with multiple threads in process gpu-process
/chrome/chrome --type=gpu-process --channel=6174.0.484233088
--user-data-dir=/home/spstarr/.config/google-chrome-beta --disable-breakpad
--supports-dual-gpus=false --gpu-driver-bug-workarounds=0,1,28
--gpu-vendor-id=0x1002 --gpu-device-id=0x9591 --gpu-driver-vendor
--gpu-driver-version --user-data-dir=/h: sb/sb_bc_parser.cpp:265: int
r600_sb::bc_parser::decode_alu_group(r600_sb::cf_node*, unsigned int&, unsigned
int&): Assertion `!"alu slot assignment failed"' failed.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[6348:6348:0311/190007:ERROR:sandbox_linux.cc(268)] InitializeSandbox() called
with multiple threads in process gpu-process
/chrome/chrome --type=gpu-process --channel=6174.7.1540935881
--user-data-dir=/home/spstarr/.config/google-chrome-beta --disable-breakpad
--supports-dual-gpus=false --gpu-driver-bug-workarounds=0,1,2,28
--gpu-vendor-id=0x1002 --gpu-device-id=0x9591 --gpu-driver-vendor=Mesa
--gpu-driver-version=10.1.0 --user-data-dir=/h: sb/sb_bc_parser.cpp:265: int
r600_sb::bc_parser::decode_alu_group(r600_sb::cf_node*, unsigned int&, unsigned
int&): Assertion `!"alu slot assignment failed"' failed.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[6354:6354:0311/190008:ERROR:sandbox_linux.cc(268)] InitializeSandbox() called
with multiple threads in process gpu-process
/chrome/chrome --type=gpu-process --channel=6174.8.352379127
--user-data-dir=/home/spstarr/.config/google-chrome-beta --disable-breakpad
--supports-dual-gpus=false --gpu-driver-bug-workarounds=0,1,2,28
--gpu-vendor-id=0x1002 --gpu-device-id=0x9591 --gpu-driver-vendor=Mesa
--gpu-driver-version=10.1.0 --user-data-dir=/h: sb/sb_bc_parser.cpp:265: int
r600_sb::bc_parser::decode_alu_group(r600_sb::cf_node*, unsigned int&, unsigned
int&): Assertion `!"alu slot assignment failed"' failed.
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4399 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
next reply other threads:[~2014-03-11 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 23:14 bugzilla-daemon [this message]
2014-03-12 3:38 ` [Bug 76046] [r600g][RV635][LLVM shader] Chrome aborts GPU acceleration 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-76046-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.