All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 screen freeze
Date: Sat, 5 Mar 2011 09:56:01 GMT	[thread overview]
Message-ID: <201103050956.p259u141015002@demeter2.kernel.org> (raw)
In-Reply-To: <bug-29022-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=29022


Marc <marc@osknowledge.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[REGRESSION? 2.6.38-rc4]    |[REGRESSION? 2.6.38-rc4]
                   |nouveau NV50 screen freeze  |nouveau NV50/NVA8 screen
                   |                            |freeze




--- Comment #7 from Marc <marc@osknowledge.org>  2011-03-05 09:55:56 ---
Hey, we have somthing in the logs:

Mar  5 09:57:44 marc kernel: [71218.224538] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar  5 09:57:44 marc kernel: [71218.224554] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar  5 09:57:44 marc kernel: [71218.224705] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar  5 09:57:44 marc kernel: [71218.224717] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar  5 09:57:44 marc kernel: [71218.224726] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 083008 warp 1, opcode
00f8f3e6 00f8f3e6
Mar  5 09:57:44 marc kernel: [71218.224899] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar  5 09:57:44 marc kernel: [71218.224911] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar  5 09:57:44 marc kernel: [71218.224921] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 083008 warp 1, opcode
00f8f3e6 00f8f3e6
Mar  5 09:57:44 marc kernel: [71218.224992] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar  5 09:57:44 marc kernel: [71218.225003] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar  5 09:57:44 marc kernel: [71218.225013] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 083008 warp 1, opcode
00f8f3e6 00f8f3e6
Mar  5 09:57:44 marc kernel: [71218.225162] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar  5 09:57:44 marc kernel: [71218.225168] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP - TP0: Unhandled ustatus 0x00020000
Mar  5 09:58:11 marc kernel: [71246.831804] [drm] nouveau 0000:01:00.0:
nouveau_channel_free: freeing fifo 4
Mar  5 09:58:24 marc kernel: [71259.463319] [drm] nouveau 0000:01:00.0:
Allocating FIFO number 4
Mar  5 09:58:24 marc kernel: [71259.473828] [drm] nouveau 0000:01:00.0:
nouveau_channel_alloc: initialised FIFO 4

This, however, seems to be something different. When I reported the bug there
were no such logs. Maybe they just didn't get into kern.log or there are two
bugs.

If you need more info on something, please ask.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  parent reply	other threads:[~2011-03-05  9:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29022-2300@https.bugzilla.kernel.org/>
2011-02-14 23:38 ` [Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50 screen freeze bugzilla-daemon
2011-02-14 23:51 ` bugzilla-daemon
2011-02-15  4:38 ` bugzilla-daemon
2011-02-25 10:14 ` bugzilla-daemon
2011-03-05  9:46 ` bugzilla-daemon
2011-03-05  9:56 ` bugzilla-daemon [this message]
2011-03-05 10:16 ` [Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 " bugzilla-daemon
2011-03-06 11:42 ` bugzilla-daemon
2011-03-06 12:01 ` bugzilla-daemon
2011-03-06 13:03 ` bugzilla-daemon
2011-03-08  8:42 ` bugzilla-daemon
2011-03-08 11:26 ` bugzilla-daemon
2011-03-08 12:46 ` bugzilla-daemon
2011-03-08 15:36 ` bugzilla-daemon
2011-03-08 15:41 ` bugzilla-daemon
2011-03-08 20:38 ` bugzilla-daemon
2011-03-08 20:47 ` bugzilla-daemon
2011-04-05 20:00 ` bugzilla-daemon
2012-08-15 22:15 ` bugzilla-daemon
2011-03-06 12:08 2.6.38-rc7-git4: Reported regressions from 2.6.37 Rafael J. Wysocki
2011-03-06 12:10 ` [Bug #29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 screen freeze Rafael J. Wysocki

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=201103050956.p259u141015002@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.