similar to: [Bug 91557] New: [NVE4] freezes: HUB_INIT timed out

https://bugs.freedesktop.org/show_bug.cgi?id=91722 Bug ID: 91722 Summary: [NVE4] PGRAPH - grctx template channel unload timeout, failed to construct context, init failed, -16 Product: Mesa Version: 10.6 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major

https://bugs.freedesktop.org/show_bug.cgi?id=80627 Priority: medium Bug ID: 80627 Assignee: nouveau at lists.freedesktop.org Summary: [NVE6] 'HUB_INIT timed out' 'Watchdog detected hard LOCKUP on cpu 7' QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

https://bugs.freedesktop.org/show_bug.cgi?id=90632 Bug ID: 90632 Summary: DRI_PRIME=1 has no effect with GK106M Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

After 5addcf0a (nouveau: add runtime PM support (v0.9)) I'm getting kernel panics immediately after resuming from suspend. Unfortunately it happens so early that I don't get any more info than the blinking keyboard lights... The nouveau tree still panics up to 2fb9d6c, which fails before I can test it. Any ideas? Martin $ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core

https://bugs.freedesktop.org/show_bug.cgi?id=70354 Priority: medium Bug ID: 70354 Assignee: nouveau at lists.freedesktop.org Summary: Failed to initialise context object: 2D_NVC0 (0) (for my GeForce GT 750M) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS:

I have the issue when loading nouveau with runpm=0 set, that further nouveau loads without runpm set or runpm=1 don't put the card into sleep state. This is caused by calling pm_runtime_get_sync in drm_device.unload when the usage_counter isn't 0. pm_runtime_get_sync always increases the suage_counter and so the usage_counter gets increased allthough runpm=0 is set, meaning nouveau leaves

----- Original Message ----- > From: "Ilia Mirkin" <imirkin at alum.mit.edu> > To: "David Airlie" <airlied at redhat.com> > Cc: "Ben Skeggs" <skeggsb at gmail.com>, "Ben Skeggs" <bskeggs at redhat.com>, nouveau at lists.freedesktop.org > Sent: Thursday, 20 March, 2014 9:49:47 AM > Subject: Re: [Nouveau] [PATCH] drm:

Fixes runpm breakage mainly on Nvidia GPUs as they are not able to resume. Works perfectly with this workaround applied. RFC comment: We are quite sure that there is a higher amount of bridges affected by this, but I was only testing it on my own machine for now. I've stresstested runpm by doing 5000 runpm cycles with that patch applied and never saw it fail. I mainly wanted to get a

https://bugs.freedesktop.org/show_bug.cgi?id=70464 Priority: medium Bug ID: 70464 Assignee: nouveau at lists.freedesktop.org Summary: [NVC3] runpm not working QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: michele.cane at gmail.com

On Tue, May 24, 2016 at 06:03:27PM +0200, Lukas Wunner wrote: > nouveau_drm_load() calls pm_runtime_put() if nouveau_runtime_pm != 0, > but nouveau_drm_unload() calls pm_runtime_get_sync() unconditionally. > We therefore leak a runtime pm ref whenever nouveau is loaded with > runpm=0 and then unloaded. The GPU will subsequently never runtime > suspend even if nouveau is loaded again

getting same error message. can you address this as well? Here is output from lspci 1:00.0 3D controller [0302]: NVIDIA Corporation GK107M [GeForce GT 745M] [10de:0fe3] (rev a1) Subsystem: Lenovo GK107M [GeForce GT 745M] [17aa:3809] Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at d0000000 (32-bit, non-prefetchable) [size=16M] Memory at a0000000 (64-bit,

https://bugs.freedesktop.org/show_bug.cgi?id=82152 Priority: medium Bug ID: 82152 Assignee: nouveau at lists.freedesktop.org Summary: any OpenGL application crashes X, locks up machine with nouveau and PRIME Severity: normal Classification: Unclassified OS: Linux (All) Reporter: celticmadman at

On 20 May 2015 at 15:56, Alexandre Courbot <acourbot at nvidia.com> wrote: > Add a module option allowing to enable staging/unstable APIs. This will > allow us to experiment freely with experimental APIs for a while before > setting them in stone. > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- > drm/nouveau/nouveau_drm.c | 18

> On Thu, Mar 20, 2014 at 1:28 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > There was a proliferation of duplicated checks for runpm == -1 && > > optimus. Instead of continuing that tradition, get rid of all of them, > > only doing the optimus computation once on load. > > > > This should hopefully fix secondary cards suspending and then being

On 21 May 2015 at 15:49, Alexandre Courbot <gnurou at gmail.com> wrote: > On Thu, May 21, 2015 at 1:48 PM, Ben Skeggs <skeggsb at gmail.com> wrote: >> On 20 May 2015 at 15:56, Alexandre Courbot <acourbot at nvidia.com> wrote: >>> Add a module option allowing to enable staging/unstable APIs. This will >>> allow us to experiment freely with experimental

There was a proliferation of duplicated checks for runpm == -1 && optimus. Instead of continuing that tradition, get rid of all of them, only doing the optimus computation once on load. This should hopefully fix secondary cards suspending and then being unable to come back in non-optimus setups. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: <stable at

For the purposes of the module parameters, specifies the permissions of the corresponding files in sysfs in predefined S_I* form rather than in octal notation. Withal it makes the source code more consistent. Moreover, because all parameters are readable to everyone, it is more user-friendly. $ grep S_IRUGO include/linux/stat.h #define S_IRUGO (S_IRUSR|S_IRGRP|S_IROTH) $ grep

CCing linux-pci and Bjorn Helgaas. Maybe we could get better insights on how a reasonable fix would look like. Anyway, to me this entire issue looks like something which has to be fixed on a PCI level instead of inside a driver, so it makes sense to ask the pci folks if they have any better suggestions. Original cover letter: While investigating the runpm issues on my GP107 I noticed that

pm_runtime_get*() may return -EACCESS to indicate a device does not have runtime PM enabled. This is the case when the nouveau.runpm parameter is set to 0, and is not an error in that context. Handle this case without failure. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drivers/gpu/drm/nouveau/dispnv04/crtc.c | 2 +- drivers/gpu/drm/nouveau/nouveau_connector.c | 2 +-

On Fri, Jul 15, 2016 at 12:41:49PM -0400, Ilia Mirkin wrote: > On Fri, Jul 15, 2016 at 12:36 PM, Peter Wu <peter at lekensteyn.nl> wrote: > > On Fri, Jul 15, 2016 at 12:10:23PM -0400, Ilia Mirkin wrote: > >> On Fri, Jul 15, 2016 at 9:12 AM, Peter Wu <peter at lekensteyn.nl> wrote: > >> > Hi, > >> > > >> > Here are two patches to fix