From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68301] New: [bisected] Headless OpenCL broken
Date: Wed, 08 Jan 2014 19:41:56 +0000 [thread overview]
Message-ID: <bug-68301-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=68301
Bug ID: 68301
Summary: [bisected] Headless OpenCL broken
Product: Drivers
Version: 2.5
Kernel Version: 3.13
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: niels_ole@salscheider-online.de
Regression: No
Created attachment 121331
--> https://bugzilla.kernel.org/attachment.cgi?id=121331&action=edit
dmesg output
Since 10ebc0bc09344ab6310309169efc73dfe6c23d72, headless OpenCL is broken on my
university's Radeon S7000 unless I pass "radeon.runpm=0".
The first OpenCL program after a reboot seems to work, but all after that
output an error similar to the following:
radeon: Failed to allocate virtual address for buffer:
radeon: size : 4352 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 4352 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
In dmesg, I can see that some parts of the initialization routine are repeated:
[ 348.906146] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
[ 348.906151] [drm] PCIE gen 3 link speeds already enabled
[ 348.909465] [drm] PCIE GART of 1024M enabled (table at 0x0000000000478000).
[...]
After that, the GPU keeps locking up.
I have attached the dmesg output.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-01-08 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 19:41 bugzilla-daemon [this message]
2014-01-13 19:52 ` [Bug 68301] [bisected] Headless OpenCL broken bugzilla-daemon
2014-01-13 19:56 ` bugzilla-daemon
2014-01-13 21:54 ` 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-68301-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 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.