From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 78717] radeon: Failed to allocate a buffer
Date: Thu, 15 May 2014 03:05:20 +0000 [thread overview]
Message-ID: <bug-78717-502-21zvpTpA3R@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-78717-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=78717
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|Mesa |DRI
Version|10.1 |unspecified
Component|Drivers/Gallium/radeonsi |DRM/Radeon
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
This is probably due to the kernel radeon driver refusing to allocate BOs
larger than the CPU mappable part of VRAM. Please attach the output of dmesg
after the problem occurs.
> MSAA also seems to hang the entire machine
That would need to be tracked in a separate report.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2399 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 prev parent reply other threads:[~2014-05-15 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 1:21 [Bug 78717] New: radeon: Failed to allocate a buffer bugzilla-daemon
2014-05-15 3:05 ` bugzilla-daemon [this message]
2014-05-15 3:16 ` [Bug 78717] " bugzilla-daemon
2014-05-15 21:18 ` [Bug 78717] radeon: Failed to allocate a buffer with Tesseract bugzilla-daemon
2014-06-12 1:21 ` bugzilla-daemon
2014-07-19 7:40 ` bugzilla-daemon
2016-04-02 21:09 ` bugzilla-daemon
2016-04-04 8:29 ` bugzilla-daemon
2016-04-04 12:41 ` bugzilla-daemon
2016-04-05 7:24 ` 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-78717-502-21zvpTpA3R@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.