All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84627] (bisected) 32bit corruption with PIPE_USAGE_STREAM reverted
Date: Sun, 23 Nov 2014 17:33:45 +0000	[thread overview]
Message-ID: <bug-84627-502-blChInGeFi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84627-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=84627

--- Comment #28 from Nils Holland <nholland@tisys.org> ---
I first started seeing this bug after upgrading my (completely 32 bit) system
from Mesa 10.3.1 to Mesa 10.3.4. Previously I was using version 3.17.3 of the
kernel, but upon seeing that there were quite a few changes made to the radeon
code between kernels 3.17.3 and 3.17.4, I decided to try 3.17.4 for a change.
It seems that the corruption I'm seeing is not as bad when using Mesa 10.3.4
with kernel 3.17.4 compared to 3.17.3, but it is still there and makes things
barely usable. I'm downgarding to Mesa 10.3.1 again which makes things work
properly for me - still, any more help needed in diagnosing this, and if so,
anything I can do to help?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1620 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

  parent reply	other threads:[~2014-11-23 17:33 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03  9:21 [Bug 84627] New: (bisected) 32bit corruption with PIPE_USAGE_STREAM reverted bugzilla-daemon
2014-10-03  9:37 ` [Bug 84627] " bugzilla-daemon
2014-10-06  6:56 ` bugzilla-daemon
2014-10-06  7:02 ` bugzilla-daemon
2014-10-06  7:27 ` bugzilla-daemon
2014-10-06  8:17 ` bugzilla-daemon
2014-10-06  8:24 ` bugzilla-daemon
2014-10-06  8:40 ` bugzilla-daemon
2014-10-06  9:53 ` bugzilla-daemon
2014-10-06 10:07 ` bugzilla-daemon
2014-10-06 10:09 ` bugzilla-daemon
2014-10-07  4:01 ` bugzilla-daemon
2014-10-07  9:40 ` bugzilla-daemon
2014-10-07 10:33 ` bugzilla-daemon
2014-10-09 23:34 ` bugzilla-daemon
2014-10-10  9:48 ` bugzilla-daemon
2014-10-10 16:20 ` bugzilla-daemon
2014-10-15  1:28 ` bugzilla-daemon
2014-10-15  1:58 ` bugzilla-daemon
2014-10-15  7:05 ` bugzilla-daemon
2014-10-15 13:53 ` bugzilla-daemon
2014-10-15 15:21 ` bugzilla-daemon
2014-10-16  3:22 ` bugzilla-daemon
2014-10-16  4:13 ` bugzilla-daemon
2014-10-16  4:28 ` bugzilla-daemon
2014-10-16  6:45 ` bugzilla-daemon
2014-10-29  2:08 ` bugzilla-daemon
2014-11-08 23:17 ` bugzilla-daemon
2014-11-23 17:33 ` bugzilla-daemon [this message]
2014-11-25  7:33 ` bugzilla-daemon
2014-11-26  0:05 ` bugzilla-daemon
2014-11-26  2:52 ` bugzilla-daemon
2014-11-26  2:54 ` bugzilla-daemon
2014-11-26  6:55 ` bugzilla-daemon
2014-11-26 21:56 ` bugzilla-daemon
2014-11-27  8:07 ` bugzilla-daemon
2014-11-27  8:52 ` bugzilla-daemon
2014-11-27 18:39 ` bugzilla-daemon
2014-12-04 13:56 ` bugzilla-daemon
2014-12-04 18:27 ` bugzilla-daemon
2015-01-08 19:29 ` bugzilla-daemon
2015-01-08 20:17 ` bugzilla-daemon
2015-08-02 11:33 ` bugzilla-daemon
2019-07-22  4:00 ` 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-84627-502-blChInGeFi@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.