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 33436] New: data error on channel 128 when running piglit
Date: Mon, 24 Jan 2011 14:42:44 -0800 (PST)	[thread overview]
Message-ID: <bug-33436-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: data error on channel 128 when running piglit
           Product: xorg
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: shiningxc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=42413)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=42413)
dmesg

I get the following message associated with screen freeze every time I do a
piglit run :
[  512.205375] [drm] nouveau 0000:01:00.0: PGRAPH - DATA_ERROR INVALID_OBJECT
[  512.205381] [drm] nouveau 0000:01:00.0: PGRAPH - DATA_ERROR
[  512.205387] [drm] nouveau 0000:01:00.0: PGRAPH - ch 128 (0x0002d30000) subc
3 class 0x5039 mthd 0x0184 data 0x00000e02

Previously I got vanishing text/pictures rather than freeze, but this behavior
has been there for a long time now.

I think it was introduced in October after the 2.6.36-rc7 merge but not 100%
sure.

This commit makes the problem appear less quickly, but it is still reproducible
:
drm/nv50: Fix race with PFIFO during PGRAPH context destruction.

git as of today:
kernel: 64b792
drm: 550fe2
ddx: 38e880

01:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600M GT]
(rev a1)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-01-24 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 22:42 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-33436-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-01-24 22:44   ` [Bug 33436] data error on channel 128 when running piglit bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-15 11:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-27 17:28   ` 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-33436-8800@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.