similar to: [REGRESSION] system does not resume from ram due to commit "drm/nv50/fifo: prevent races between clients updating playlists"

Many people using nv50+ hardware are aware of gpu lockups when a fifo closes under certain conditions. Based on a mmio-trace and some trail and error testing i've come up with a patch that improves the situation on my NV96. This patch needs testing on NV50+ hardware and regression testing on older hardware, since i did change some of the common codepaths. This is very much a work in progress,

So, I wrote a generator for ctxprogs on NV50, NV84, NV86, NV92, NV94, NV96, NV98. Atm it's only tested with NV86 and I'd like to see if it works for all the other cards, especially NV50. NVAx support is still missing due to some differences, but should be coming soon. Address is http://0x04.net/~mwk/gen.diff , please test it with all mentioned cards, and involve as much gallium as

I think we had the wrong culprit: I just tried PCI-disabling the NVAC card (and keeping the NV96 one), and it just works: no garbage screen, and moreover, I get no hangs nor errors when enabling acceleration! I'll spend some time comparing both outputs (without NVAC, and without NV96) to find out what the NVAC is doing wrong. Pierre > On 31 Jan 2014, at 23:58, Ilia Mirkin <imirkin at

----- Mail original ----- > De: "Ilia Mirkin" <imirkin at alum.mit.edu> > ?: "pierre morrow" <pierre.morrow at free.fr> > Cc: nouveau at lists.freedesktop.org > Envoy?: Vendredi 31 Janvier 2014 21:16:40 > Objet: Re: [Nouveau] Help needed for bug 58556 > Unfortunately this is a *massive* bug... and confused by the "other" > very

Hello List, I am trying to solve bug 58556 [1], but I will need some help as I don't understand all that is going on. The system is composed of an NV96 (9600 GT) and an NVAC (9400 M) card; acceleration is disabled, otherwise the system hangs at boot after initialising the NV96 card. The problem consist of a complete garbage screen in console mode, and a one-third gabage screen in GUI.

Add NV96 in NV9X_GRCLASS8297_CHIPSETS bitmask and remove the test blocking NV9x (another test is already present above) --- src/gallium/drivers/nv50/nv50_screen.c | 8 +------- 1 files changed, 1 insertions(+), 7 deletions(-) diff --git a/src/gallium/drivers/nv50/nv50_screen.c b/src/gallium/drivers/nv50/nv50_screen.c index 9bf5e8c..4130ede 100644 --- a/src/gallium/drivers/nv50/nv50_screen.c

On 18.10.2016 09:35, Karol Herbst wrote: > how sure are you, that this is needed for _every_ nvac? > Thank you for asking. If you consider, as relevant, referring to the original commit: "drm/nouveau/disp/g94: implement workaround for dvi issue on fx380" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a <quote> Fixes the second DVI output

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

https://bugs.freedesktop.org/show_bug.cgi?id=69350 Priority: medium Bug ID: 69350 Assignee: nouveau at lists.freedesktop.org Summary: [NV96] Second card output corrupted after suspend QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: thomas.bettler

https://bugs.freedesktop.org/show_bug.cgi?id=43939 Bug #: 43939 Summary: DVI monitor connected via HDMI is blank / standby (NV96 / 9500GS) Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal

On 17.11.2013 00:22, Emil Velikov wrote: > On 04/10/13 01:54, Christoph Rudorff wrote: >> Am Donnerstag, den 03.10.2013, 23:50 +0100 schrieb Emil Velikov: >>> I'm not entirely sure this is correct. One needs to save and disable >>> accleration before suspending the fb. Please try the following >>> >>> - if (state == 0) >>> + if (state == 1)

https://bugs.freedesktop.org/show_bug.cgi?id=87543 Bug ID: 87543 Summary: "unmatched output device 0x0103010201010100" when connecting to hdmi Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

http://bugs.freedesktop.org/show_bug.cgi?id=25952 Summary: GeForce 9800 GTX - nouveau_init takes ~ 1 minute to complete Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: major Priority: high Component: Driver/nouveau AssignedTo: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=86566 Bug ID: 86566 Summary: [NV96] nouveau_pmops_suspend returns -16 Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=82726 Priority: medium Bug ID: 82726 Assignee: nouveau at lists.freedesktop.org Summary: [NV96][NVAC] [Regression] [Bisected] Probe failed with error -12 QA Contact: xorg-team at lists.x.org Severity: blocker Classification: Unclassified OS: Linux (All)

On Fri, Jan 31, 2014 at 5:39 PM, <pierre.morrow at free.fr> wrote: > De: "Ilia Mirkin" <imirkin at alum.mit.edu> > > Unfortunately this is a *massive* bug... and confused by the "other" > > very similar but apparently not identical bug in the system. > > > > What happens if you only enable acceleration on the NVAC card? (e.g. > > by

Hello, I've started seeing the following warning in 3.11-rc2. [In the interest of full disclosure, I do have a patch applied that tries to implement drm_planes, which I might have done completely incorrectly, but looking around it doesn't seem related. I'm definitely not invoking any of the planes functionality right now. See http://paste.debian.net/hidden/cf8b3a2, plus a call to the

https://bugs.freedesktop.org/show_bug.cgi?id=86537 Bug ID: 86537 Summary: [NV96] Unable to handle page request from nv50_crtc_prepare Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Am Donnerstag, den 03.10.2013, 23:50 +0100 schrieb Emil Velikov: > I'm not entirely sure this is correct. One needs to save and disable > accleration before suspending the fb. Please try the following > > - if (state == 0) > + if (state == 1) > nouveau_fbcon_save_disable_accel(dev); > fb_set_suspend(drm->fbcon->helper.fbdev, state); > - if (state == 1) > +

This removes dependence on external firmware for NV50 generation cards. If the generated ctxprogs don't work for you for some reason, please report it. Signed-off-by: Marcin Ko?cielnicki <koriakin at 0x04.net> --- drivers/gpu/drm/nouveau/Makefile | 2 +- drivers/gpu/drm/nouveau/nouveau_drv.h | 1 + drivers/gpu/drm/nouveau/nv50_graph.c | 74 +-