similar to: [Bug 102840] nouveau PGRAPH - ERROR nsource: ILLEGAL_MTHD nstatus: PROTECTION_FAULT

https://bugs.freedesktop.org/show_bug.cgi?id=102840 --- Comment #2 from Pierre Moreau <pierre.morrow at free.fr> --- We are a few French Nouveau developers, so feel free to come to our IRC channel #nouveau on freenode, if you would rather speak French than English; those conversations would be held privately, as not everyone speaks French on the channel. -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=102840 --- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> --- Nouveau has been rewritten 5 times since kernel 3.2 came out some short 5.5 years ago, both userspace and kernel driver. Your issue is some kind of problem with binding a class to a subchannel (that 0x8800004 value is not a valid class id). But I have no idea what might cause

https://bugs.freedesktop.org/show_bug.cgi?id=102840 --- Comment #3 from Philippe Neyrat <philippe.neyrat at mailz.org> --- Created attachment 134479 --> https://bugs.freedesktop.org/attachment.cgi?id=134479&action=edit dmesg log running nouveau on Fedora-Workstation-Live-i386-26-1.5 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=102840 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #4 from Martin Peres

Switching focus to a previously idle firefox and starting to type in the google bar, the screen locked up (and the display went black and showed 'no signal'). Ssh'ing into the machine, I found this in dmesg: [drm] nouveau 0000:01:00.0: Allocating FIFO number 1 [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1 [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on

https://bugs.freedesktop.org/show_bug.cgi?id=68854 Priority: medium Bug ID: 68854 Assignee: nouveau at lists.freedesktop.org Summary: [NV04] PROTECTION_ERROR / PROTECTION_FAULT QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mauromol at tiscali.it

https://bugs.freedesktop.org/show_bug.cgi?id=54910 Bug #: 54910 Summary: Problems with nouveau and Gforce 2MX Classification: Unclassified Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=101323 Bug ID: 101323 Summary: [nv20] glx-swap-event hangs X server Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

Hi, Trying a new kernel on old [NV04] system I get tons of nouveau 0000:01:00.0: gr: intr 00000001 [NOTIFY] nsource 00000040 [ILLEGAL_MTHD] nstatus 00004000 [PROTECTION_FAULT] ch 0 [DRM] subc 3 class 004a mthd 02fc data 00000003 errors when operating on console. As I updated from 4.3 kernel, a bisect does not feel like the best start. What is that 02fc method which fbcon is probably

http://bugs.freedesktop.org/show_bug.cgi?id=15276 Summary: text rendering, PGRAPH_ERROR/ILLEGAL_MTHD/PROTECTION_FAULT spam in syslog Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

On Mon, Nov 25, 2019 at 9:08 AM Bruno Prémont <bonbons at sysophe.eu> wrote: > > Hi, > > Trying a new kernel on old [NV04] system I get tons of > nouveau 0000:01:00.0: gr: intr 00000001 [NOTIFY] nsource 00000040 > [ILLEGAL_MTHD] nstatus 00004000 [PROTECTION_FAULT] ch 0 > [DRM] subc 3 class 004a mthd 02fc data 00000003 > errors when operating on console. >

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=73358 Priority: medium Bug ID: 73358 Assignee: nouveau at lists.freedesktop.org Summary: [nv34] adobe flash + firefox -> DATA_ERROR QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: ronald645 at gmail.com

This makes nouveau recognise and report more kinds of PGRAPH errors, as well as prevent GPU lockups resulting from some of them. Lots of guesswork was involved and some part of this is probably incorrect. Some potential-lockuop situations are handled by just resetting a whole PGRAPH subunit, which doesn't sound like a "proper" solution, but seems to work just fine... for now.

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

Am 2013-10-28 15:42, schrieb Ilia Mirkin: > On Mon, Oct 28, 2013 at 3:45 AM, Martin Kaffanke <martin.kaffanke at gmx.at> wrote: >> Hi there, >> >> Sometimes my computer crashes since i use now ubuntu 13.10 with >> unity/compiz. > > You're on NV4C. Do you have mesa 9.2.1 or later (or pre-9.2)? If you > have 9.2.0, there are known issues with shader

https://bugs.freedesktop.org/show_bug.cgi?id=49727 Bug #: 49727 Summary: wine 1.5.2 and 3Dmark2001se displays only black screen with FPS, on nv43/AGP Classification: Unclassified Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal

https://bugs.freedesktop.org/show_bug.cgi?id=67161 Priority: medium Bug ID: 67161 Assignee: nouveau at lists.freedesktop.org Summary: Blank video after resuming from S3 or S4 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mauromol at tiscali.it

Commit 7110c89bb8852ff8b0f88ce05b332b3fe22bd11e ("mmu: swap out round for ALIGN") replaced two calls to round/rounddown with ALIGN/ALIGN_DOWN, but erroneously applied ALIGN_DOWN to a different variable (addr) and left intended variable (tail) not rounded/ALIGNed. As a result screen corruption, X lockups are observable. An example of kernel log of affected system with NV98 card where it

https://bugs.freedesktop.org/show_bug.cgi?id=81690 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|DRM/other |Driver/nouveau Assignee|dri-devel at lists.freedesktop |nouveau at lists.freedesktop.o