From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36952] segfault in crackberg xscreensaver on ATI RS482 in mesa git running kms & gallium
Date: Mon, 16 May 2011 06:49:15 -0700 (PDT) [thread overview]
Message-ID: <20110516134915.897B913004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36952-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36952
--- Comment #13 from dri tester <writemeanddie@hotmail.com> 2011-05-16 06:49:15 PDT ---
(In reply to comment #12)
> (In reply to comment #11)
> > It would be better to experiment with the patch and try smaller buffer sizes.
> > Please let me know when you find a size which works.
>
> The current mesa-git value for the R300_MAX_DRAW_VBO_SIZE is 1024 * 1024 and
> your patch dropped it down to 512 * 1024. I tried with 64 * 1024 (which is the
> value that worked before the commit that I bisected above) and crackberg works,
> the animation is smooth and the cpu usage is 50% on one cpu, but it segfaults
> after 13-18 seconds. I really think there is another bug being uncovered here.
> I do not know which buffer size to recommend for R300_MAX_DRAW_VBO_SIZE, 512 *
> 1024 as per your attached patch worked as well as 64 * 1024. I assume that the
> value must be a power of 2, or are there some other values to test? Should I
> test the values between 64 and 512 for completeness?
Disregard my last comment above, I was totally incorrect. A value for
R300_MAX_DRAW_VBO_SIZE of 32 * 1024 fixed crackberg completely for me. I will
attach the working patch as 0003-r300g-allocate-smaller-upload-buffers.patch.
Thanks Marek.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-05-16 13:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 0:20 [Bug 36952] New: segfault in crackberg xscreensaver on ATI RS482 in mesa git running kms & gallium bugzilla-daemon
2011-05-08 15:35 ` [Bug 36952] " bugzilla-daemon
2011-05-08 15:35 ` bugzilla-daemon
2011-05-09 2:11 ` bugzilla-daemon
2011-05-09 13:22 ` bugzilla-daemon
2011-05-09 13:28 ` bugzilla-daemon
2011-05-09 16:52 ` bugzilla-daemon
2011-05-09 16:57 ` bugzilla-daemon
2011-05-13 10:45 ` bugzilla-daemon
2011-05-13 22:23 ` bugzilla-daemon
2011-05-15 0:55 ` bugzilla-daemon
2011-05-15 1:08 ` bugzilla-daemon
2011-05-16 13:14 ` bugzilla-daemon
2011-05-16 13:49 ` bugzilla-daemon [this message]
2011-05-16 13:52 ` bugzilla-daemon
2011-05-16 13:56 ` bugzilla-daemon
2011-05-17 0:19 ` bugzilla-daemon
2012-12-04 16:55 ` bugzilla-daemon
2012-12-05 16:12 ` 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=20110516134915.897B913004F@annarchy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).