All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
To: Peter Wu <peter-VTkQYDcBqhK7DlmcbJSQ7g@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	"Mr.ze" <mr.ze-g/b1ySJe57IN+BqQ9rBEUg@public.gmane.org>
Subject: Re: Nvidia recent drivers
Date: Sat, 28 Jan 2017 07:58:32 +0100	[thread overview]
Message-ID: <20170128065832.GA27774@wunner.de> (raw)
In-Reply-To: <4813CD8E-8E01-48BE-B4AA-8B57E6A4531C-VTkQYDcBqhK7DlmcbJSQ7g@public.gmane.org>

On Fri, Jan 27, 2017 at 04:06:38PM +0100, Peter Wu wrote:
> Also note that many laptops with these card suffer from a problem
> that cause lockups when runpm kicks in.
> See https://bugzilla.kernel.org/show_bug.cgi?id=156341

Peter, I notice you weren't cc'ed on the last few messages of the
'PCI: Revert "PCI: Add runtime PM support for PCIe ports"' thread,
the similar bug https://bugzilla.kernel.org/show_bug.cgi?id=190861
turned out to be caused by locking issues in nouveau which were
fixed with 3846fd9b8600 in Linus' tree.  That commit swiftly got
reverted because it lacked prerequisites, and replaced by the
temporary fix cae9ff036eea + 15266ae38fe0.  These two will be
reverted in 4.11 and replaced with the proper solution (which was
3846fd9b8600).  Long story short, the issue seems solved, the revert
of PCIe port PM is dequeued.  Perhaps this also fixes the issues in
the bugzilla entry you mentioned above, at least for some laptops?

Thanks,

Lukas
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-01-28  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 19:50 Nvidia recent drivers Mr.ze
2017-01-27 15:06 ` Peter Wu
     [not found]   ` <4813CD8E-8E01-48BE-B4AA-8B57E6A4531C-VTkQYDcBqhK7DlmcbJSQ7g@public.gmane.org>
2017-01-28  6:58     ` Lukas Wunner [this message]
     [not found]       ` <20170128065832.GA27774-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2017-01-28 10:48         ` Peter Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170128065832.GA27774@wunner.de \
    --to=lukas-jfq808j9c/izqb+pc5nmwq@public.gmane.org \
    --cc=mr.ze-g/b1ySJe57IN+BqQ9rBEUg@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=peter-VTkQYDcBqhK7DlmcbJSQ7g@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.