From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74121] New: [3.15-rc1] Exynos: Sandbox report fatal error "Unexpected 64bit argument detected"
Date: Tue, 15 Apr 2014 09:02:08 +0000 [thread overview]
Message-ID: <bug-74121-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=74121
Bug ID: 74121
Summary: [3.15-rc1] Exynos: Sandbox report fatal error
"Unexpected 64bit argument detected"
Product: Drivers
Version: 2.5
Kernel Version: 3.15-rc1
Hardware: Other
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: r.sh.open@gmail.com
Regression: No
Sandbox crashing with 3.15-rc1 stating below fatal error. This was working in
till 3.14 Stable.
---------------------------------------------------------------------------
[1925:1925:0101/000305:FATAL:sandbox_bpf.cc(202)] Unexpected 64bit argument
detected
[1860:1860:1231/160305:FATAL:gpu_process_transport_factory.cc(210)] Failed to
create UI context, but can't use software compositing with browser threaded
compositing. Aborting.
Handling SIGCHLD.
Successfully wrote to child pipe.
bootstrap_helper: ReserveBottomPages: NULL pointer guard page errno=22
---------------------------------------------------------------------------
[This is my first bug. Please let me know if thing are not upto the mark.]
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-04-15 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 9:02 bugzilla-daemon [this message]
2014-04-15 9:09 ` [Bug 74121] New: [3.15-rc1] Exynos: Sandbox report fatal error "Unexpected 64bit argument detected" Rahul Sharma
2014-04-15 9:09 ` [Bug 74121] " bugzilla-daemon
2014-04-22 16:25 ` bugzilla-daemon
2014-04-22 16: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-74121-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox