similar to: Recommendation for cherry-pick between 3.12 and 4.2: 0a363e85cdaf

Hi, On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: > I'd like to recommend backporting this commit: > > commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 > Author: Hans de Goede <hdegoede at redhat.com> > Date: Thu Jul 23 17:20:12 2015 +0200 > > drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c > > This disables MSI by default on G72 (NV46)

On Tue, Jan 19, 2016 at 5:22 AM, Jiri Slaby <jslaby at suse.cz> wrote: > Hi, > > On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: >> I'd like to recommend backporting this commit: >> >> commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 >> Author: Hans de Goede <hdegoede at redhat.com> >> Date: Thu Jul 23 17:20:12 2015 +0200 >> >>

MSI interrupts appear to not work for nv46 based cards. Change the mc subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is identical to the nv44 mc code except that it does not use msi (it does not define a msi_rearm callback). BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=90435 Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---

Hi, On 24-07-15 04:32, Ben Skeggs wrote: > On 24 July 2015 at 01:20, Hans de Goede <hdegoede at redhat.com> wrote: >> MSI interrupts appear to not work for nv46 based cards. Change the mc >> subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is >> identical to the nv44 mc code except that it does not use msi >> (it does not define a msi_rearm

On Sun, Jan 17, 2016 at 02:28:13PM -0500, Ilia Mirkin wrote: > Hello, > > I'd like to recommend backporting this commit: > > commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 > Author: Hans de Goede <hdegoede at redhat.com> > Date: Thu Jul 23 17:20:12 2015 +0200 > > drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c It doesn't apply to

https://bugs.freedesktop.org/show_bug.cgi?id=78441 Priority: medium Bug ID: 78441 Assignee: nouveau at lists.freedesktop.org Summary: X does not start under kernel 3.13.x QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: aebenjam at opentext.com

https://bugs.freedesktop.org/show_bug.cgi?id=73342 Priority: medium Bug ID: 73342 Assignee: nouveau at lists.freedesktop.org Summary: nouveau not working with yuy2 overlay QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: fbs777 at gmail.com

Hi This patch correct on usb keyboard acces on number when enter via Ctrl + Alt + F12 on vt after Xorg running.Without this patch when enter on vt vas unable to use numbers from NumLock an only numbers from main keyboard. nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046f00a3 nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) nouveau [ DEVICE][0000:01:00.0] Family : NV40 nouveau [

https://bugs.freedesktop.org/show_bug.cgi?id=56474 Priority: medium Bug ID: 56474 Assignee: nouveau at lists.freedesktop.org Summary: 3D app segfaults on NV46 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: 1o5g4r8o at gmail.com Hardware: x86 (IA32) Status: NEW

See https://bugs.freedesktop.org/show_bug.cgi?id=74492 Reported-by: Ronald <ronald645 at gmail.com> Suggested-by: Marcin Ko?cielnicki <koriakin at 0x04.net> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/Makefile | 1 + drivers/gpu/drm/nouveau/core/engine/device/nv40.c | 10 ++---

http://bugs.freedesktop.org/show_bug.cgi?id=21124 Summary: nouveau: fonts "chipped" on NV44 Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

http://bugs.freedesktop.org/show_bug.cgi?id=22179 Summary: [KMS] Black screen with KMS enabled Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=83168 Priority: medium Bug ID: 83168 Assignee: nouveau at lists.freedesktop.org Summary: No display after suspend to RAM QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: nsajko at gmail.com

https://bugs.freedesktop.org/show_bug.cgi?id=95095 Bug ID: 95095 Summary: NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

Hi, On 30-07-15 16:09, Ilia Mirkin wrote: > FWIW this is a fail on nv50+ as well. See for example > https://bugs.freedesktop.org/show_bug.cgi?id=91445 > > My suspicion is that this is due to the lack of PUSH_KICK in the *Done > exa handlers -- works fine with DRI2, but DRI3 has no synchronization > and so the commands never get flushed out. Easily verified by sticking >

On my GP107 when I load nouveau after unloading it, for some reason the GPU stopped sending or the CPU stopped receiving interrupts if MSI was enabled. Doing a rearm once before getting any interrupts fixes this. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/subdev/pci/base.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git

Hi Maarten, xf86-video-nouveau causes a garbled display when running gnome-shell on nv4x (tested with nv43 and nv46) since this commit: http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=241e7289f25a342a457952b9b0e539c2f0b81d99 I've seen some discussion about issues caused by enabling dri, but AFAIK no solution let. I have time to help with debugging / fixing this, but I

Hi, recently we tried to enable MSI interrupts with nouveau. Unfortunately there have been some reports of things failing with certain cards, where it isn't entirely clear if this is a GPU errata or some other component in the PCIe chain failing. Could you perhaps investigate if there are any known Nvidia GPU erratas with regard to MSI interrupts, or maybe tell us the generations of cards

https://nouveau.freedesktop.org/wiki/CodeNames/ > If you're running a recent version nouveau, you can find your chipset by doing dmesg | grep -i chipset. This will always be correct, whereas the lists below are approximate. # dmesg | grep -i chipset # Not true anymore I guess. What is the 'GP' in 'GP107' if 'NV...' are the code names? # dmesg | grep -i nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=89571 Bug ID: 89571 Summary: XFX 7300 GS - Black screen with DVI when KMS(nouveau) starts - VGA working Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: blocker Priority: medium