All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 75776] [NV50 gallium] Hearthstone displays corrupted buffers
Date: Sat, 19 Apr 2014 17:30:44 +0000	[thread overview]
Message-ID: <bug-75776-8800-7nkdj3TvRY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75776-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #14 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to comment #13)
> I also face this issue, I have NV4x card

No, you don't. You face an entirely different and unrelated issue. You can open
a separate bug for it.

> [  175.238926] nouveau E[  PGRAPH][0000:01:00.0]  ERROR nsource: DATA_ERROR
> nstatus: BAD_ARGUMENT
> [  175.238962] nouveau E[  PGRAPH][0000:01:00.0] ch 3 [0x0013c000
> Hearthstone.exe[734]] subc 7 class 0x4097 mthd 0x0208 data 0x04040242

Hmmmm....

$ lookup -a 49 -d NV01_SUBCHAN -- -v obj-class NV40_3D 208 0x04040242
RT_FORMAT => { COLOR = 0x2 | ZETA = Z24S8 | TYPE = SWIZZLED | LOG2_WIDTH = 4 |
LOG2_HEIGHT = 4 }

COLOR = 0x2? That's odd. Might need to investigate how this can happen... might
just be something missing in rnndb.

> [  175.248385] nouveau E[  PGRAPH][0000:01:00.0]  ERROR nsource: DATA_ERROR
> nstatus: BAD_ARGUMENT
> [  175.248420] nouveau E[  PGRAPH][0000:01:00.0] ch 3 [0x0013c000
> Hearthstone.exe[734]] subc 7 class 0x4097 mthd 0x0208 data 0x04040243

$ lookup -a 49 -d NV01_SUBCHAN -- -v obj-class NV40_3D 208 0x04040243
RT_FORMAT => { COLOR = R5G6B5 | ZETA = Z24S8 | TYPE = SWIZZLED | LOG2_WIDTH = 4
| LOG2_HEIGHT = 4 }

Ah yes, I know this issue well. Mixing 16-bit color and 32-bit zeta
(depth/stencil) attachments to an FBO. Not supported by the hardware, and the
driver doesn't "fix" it up either.

In any case, totally unrelated to the issue on the nva5 originally reported.

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

[-- Attachment #1.2: Type: text/html, Size: 2523 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-04-19 17:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 22:18 [Bug 75776] New: Hearthstone displays corrupted buffers on NVA5 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-75776-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-04 22:20   ` [Bug 75776] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-04 22:23   ` [Bug 75776] [NVA5] Hearthstone displays corrupted buffers bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-04 22:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-04 22:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05  0:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05  3:39   ` [Bug 75776] [NV50 gallium] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05  3:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05  5:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 21:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-10  7:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-10  7:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-10  8:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-10 10:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-19 10:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-19 17:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-04-20 12:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-18 20:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-28  6:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-75776-8800-7nkdj3TvRY@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.