similar to: [Bug 77230] New: NV40 PGRAPH "unknown bits" - windows render in white

Hello, I have been working on a kernel and a user layer for the nv40 mpeg2 video decoding hardware: * The decode hw accepts commands written to a fifo along with a set of registers for firing (put) and queries (get). * The fifo can be mapped in vram or agp (though, agp isn't working right now). * The fifo does not support dma jumps and such like the 3d fifo. Well, I have some questions about

https://bugs.freedesktop.org/show_bug.cgi?id=48954 Bug #: 48954 Summary: nv25 PGRAPH error and X freeze Classification: Unclassified Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Try booting with `nouveau.nofbaccel=1` and see if that helps. Some many kernels ago, acceleration of the console on fb resume got fixed, and is now causing issues for you and a few others. This will turn off fbcon accel, which should hopefully sidestep the issue. On Sun, Jan 4, 2015 at 5:32 AM, Lukasz Stelmach <stlman at poczta.fm> wrote: > Hello, > > I'd like to bring to your

Hello, I'd like to bring to your attention a bug report[1] I have filed on the Gentoo bugzilla about a regression (quite an old one) in the nouveau driver. If there is anything missing in the report that could help fixing the problem, please feel free to ask. [1] https://bugs.gentoo.org/show_bug.cgi?id=534038 -- Było mi bardzo miło. Twoje oczy lubią mnie >Łukasz<

https://bugs.freedesktop.org/show_bug.cgi?id=69465 Priority: medium Bug ID: 69465 Assignee: nouveau at lists.freedesktop.org Summary: Kernel freeze with NVA3 kernel 3.11.1 / PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail QA Contact: xorg-team at lists.x.org Severity: critical

Hi everyone, I was wondering what to do to dig into this problem further.The kernel is several weeks old (nouveau tree), it's at commit 000463f13fba6b2f94a5bfcb0d615751ae9c34a0. As you can see from the mesages below the problem is reproducable to the point of getting exactly the same error. Nov 25 17:57:51 madman kernel: [548360.773743] nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle

According to http://wiki.winehq.org/WineReleasePlan the new release date for Wine 1.0 is set to June 17. However the Firefox 3.0 release date is also set to June 17. http://developer.mozilla.org/devnews/index.php/2008/06/11/coming-tuesday-june-17th-firefox-3/ Their release is planned to be high profile and they even plan to set a Guinness world record for downloads in a single day!

The problem affects nv40 cards during booting. It comes from there being two places where subdev arrays are maintained. A commit was recently added to make the two equal. However, the struct nouveau_device version ends up being referenced before it is initialized. The problem arises during the creation of the INSTMEM and THERM subdevs. ' Signed off by: Bob Gleitsmann rjgleits at bellsouth.net

Some archs defconfigs have CONFIG_FRAME_WARN set to 1024, which lead to this warning: drivers/gpu/drm/nouveau/core/engine/graph/ctxnv40.c: warning: the frame size of 1184 bytes is larger than 1024 bytes Reported-by: Geert Uytterhoeven <geert at linux-m68k.org> Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/engine/graph/ctxnv40.c | 12

On Tue, Jan 14, 2014 at 1:22 PM, Bob Gleitsmann <rjgleits at bellsouth.net> wrote: > I should have mentioned that this applies to Linus' 3.13.0-rc7 and rc8 > git. Maybe it's obvious. Hey Bob, Thanks for reporting this. Can you try the attached patch instead and report if it helps you? Ben. > > Sorry about that. > > Bob > -------- Forwarded Message --------

Now it outputs: nouveau E[ PGRAPH][0000:02:00.0] PGRAPH TLB flush idle timeout fail nouveau E[ PGRAPH][0000:02:00.0] PGRAPH_STATUS: BUSY DISPATCH VFETCH CCACHE_UNK4 STRMOUT_GSCHED_UNK5 UNK14XX UNK1CXX CLIPID ZCULL ENG2D UNK34XX TPRAST TPROP ROP (0x011fde03) nouveau E[ PGRAPH][0000:02:00.0] PGRAPH_VSTATUS_0: CCACHE (0x00145b4d) nouveau E[ PGRAPH][0000:02:00.0] PGRAPH_VSTATUS_1: (0x0000002d)

Current uninitialized sensor detection does not work for me on nv4b and sensor returns crazy values (>190?C). It stabilises later, but it's too late - therm code shutdowns the machine... Let's just reset it on init. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/subdev/therm/nv40.c | 12 +++++++++++- 1 file changed, 11

My main question is, do the error messages accurately reflect the situation. Anything else wrong with this patch? A (n)ack by darktama would be nice. Maarten. -------------- next part -------------- A non-text attachment was scrubbed... Name: test.patch Type: application/octet-stream Size: 1690 bytes Desc: not available Url :

https://bugs.freedesktop.org/show_bug.cgi?id=56718 Priority: medium Bug ID: 56718 Assignee: nouveau at lists.freedesktop.org Summary: PGRAPH - TRAP_TEXTURE errors and graphic corruptions Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jmoronat at gmail.com Hardware: x86 (IA32)

--- src/gallium/drivers/nv40/nv40_fragprog.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/src/gallium/drivers/nv40/nv40_fragprog.c b/src/gallium/drivers/nv40/nv40_fragprog.c index 1237066..209d211 100644 --- a/src/gallium/drivers/nv40/nv40_fragprog.c +++ b/src/gallium/drivers/nv40/nv40_fragprog.c @@ -843,7 +843,8 @@ nv40_fragprog_translate(struct nv40_context *nv40,

nv40_sensor_setup() is never called in atomic context. It calls mdelay() to busily wait, which is not necessary. mdelay() can be replaced with msleep(). This is found by a static analysis tool named DCNS written by myself Signed-off-by: Jia-Ju Bai <baijiaju1990 at gmail.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/therm/nv40.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

--- rnndb/nv50_pgraph.xml | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/rnndb/nv50_pgraph.xml b/rnndb/nv50_pgraph.xml index 92d69ea..6499631 100644 --- a/rnndb/nv50_pgraph.xml +++ b/rnndb/nv50_pgraph.xml @@ -93,6 +93,9 @@ <value value="0x23" name="XY_OUT_OF_BOUNDS"> <!-- m2mf at least. 2d too? --> <brief>Your x/y coords

Hi all, I have what I think is a nouveau-related bug, but don't have all the information they as for on the support page, so thought I'd ask for help here first. My computer will hang after resuming from hibernate/suspend, sometimes showing a normal lock screen and other times just a white screen. I have some extracts from /var/log/messages, but no kernel logs since I cannot get anything

The blob does not seem to write at that place for my NVAC, though it does for my NV96, agreeing with what is done in the if/else structure below. I guess someone forgot to remove the line when the if/else was put in place. Signed-off-by: Pierre Moreau <pierre.morrow at free.fr> --- drivers/gpu/drm/nouveau/core/engine/graph/nv50.c | 1 - 1 file changed, 1 deletion(-) diff --git

https://bugs.freedesktop.org/show_bug.cgi?id=102840 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|DRM/other |Driver/nouveau QA Contact| |xorg-team at lists.x.org