From: Lyude Paul <lyude@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: David Ober <dober@lenovo.com>,
linux-pci@vger.kernel.org, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Karol Herbst <kherbst@redhat.com>, Ben Skeggs <skeggsb@gmail.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] pci/quirks: Add quirk to reset nvgpu at boot for the Lenovo ThinkPad P50
Date: Wed, 03 Apr 2019 13:27:25 -0400 [thread overview]
Message-ID: <59dbed40fc0fad4a945cbfe09c9f622b81c7bd94.camel@redhat.com> (raw)
In-Reply-To: <20190322113015.GM251185@google.com>
Hi, any update on this/do you guys need any more information here? Would very
much like to get this upstream
On Fri, 2019-03-22 at 06:30 -0500, Bjorn Helgaas wrote:
> On Thu, Mar 21, 2019 at 05:48:19PM -0500, Bjorn Helgaas wrote:
> > On Wed, Mar 13, 2019 at 06:25:02PM -0400, Lyude Paul wrote:
> > > On Fri, 2019-02-15 at 16:17 -0500, Lyude Paul wrote:
> > > > On Thu, 2019-02-14 at 18:43 -0600, Bjorn Helgaas wrote:
> > > > > On Tue, Feb 12, 2019 at 05:02:30PM -0500, Lyude Paul wrote:
> > > > > > On a very specific subset of ThinkPad P50 SKUs, particularly
> > > > > > ones that come with a Quadro M1000M chip instead of the M2000M
> > > > > > variant, the BIOS seems to have a very nasty habit of not
> > > > > > always resetting the secondary Nvidia GPU between full reboots
> > > > > > if the laptop is configured in Hybrid Graphics mode. The
> > > > > > reason for this happening is unknown, but the following steps
> > > > > > and possibly a good bit of patience will reproduce the issue:
> > > > > >
> > > > > > 1. Boot up the laptop normally in Hybrid graphics mode
> > > > > > 2. Make sure nouveau is loaded and that the GPU is awake
> > > > > > 2. Allow the nvidia GPU to runtime suspend itself after being idle
> > > > > > 3. Reboot the machine, the more sudden the better (e.g sysrq-b may
> > > > > > help)
> > > > > > 4. If nouveau loads up properly, reboot the machine again and go
> > > > > > back to
> > > > > > step 2 until you reproduce the issue
> > > > > >
> > > > > > This results in some very strange behavior: the GPU will quite
> > > > > > literally be left in exactly the same state it was in when the
> > > > > > previously booted kernel started the reboot. This has all
> > > > > > sorts of bad sideaffects: for starters, this completely breaks
> > > > > > nouveau starting with a mysterious EVO channel failure that
> > > > > > happens well before we've actually used the EVO channel for
> > > > > > anything:
> >
> > Thanks for the hybrid tutorial (snipped from this response). IIUC,
> > what you said was that in hybrid mode, the Intel GPU drives the
> > built-in display and the Nvidia GPU drives any external displays and
> > may be used for DRI PRIME rendering (whatever that is). But since you
> > say the Nvidia device gets runtime suspended, I assume there's no
> > external display here and you're not using DRI PRIME.
> >
> > I wonder if it's related to the fact that the Nvidia GPU has been
> > runtime suspended before you do the reboot. Can you try turning of
> > runtime power management for the GPU by setting the runpm module
> > parameter to 0? I *think* this would be booting with
> > "nouveau.runpm=0".
>
> Sorry, I wasn't really thinking here. You already *said* this is
> related to runtime suspend. It only happens when the Nvidia GPU has
> been suspended.
>
> I don't know that much about suspend, but ISTR seeing comments about
> resuming devices before we shutdown. If we do that, maybe there's
> some kind of race between that resume and the reboot?
>
> Bjorn
--
Cheers,
Lyude Paul
next prev parent reply other threads:[~2019-04-03 17:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 22:02 [PATCH] pci/quirks: Add quirk to reset nvgpu at boot for the Lenovo ThinkPad P50 Lyude Paul
2019-02-15 0:43 ` Bjorn Helgaas
2019-02-15 21:17 ` Lyude Paul
2019-03-13 22:25 ` Lyude Paul
2019-03-19 20:56 ` Lyude Paul
2019-03-21 22:48 ` Bjorn Helgaas
2019-03-22 11:30 ` Bjorn Helgaas
2019-04-03 17:27 ` Lyude Paul [this message]
2019-04-04 14:17 ` Bjorn Helgaas
2019-04-15 18:07 ` Lyude Paul
2019-04-24 18:59 ` Bjorn Helgaas
2019-04-24 19:16 ` Lyude Paul
2019-04-24 22:36 ` Bjorn Helgaas
2019-04-24 23:03 ` Lyude Paul
2019-04-24 17:31 ` Lyude Paul
2019-04-24 18:28 ` Bjorn Helgaas
2019-03-22 23:50 ` Lyude Paul
2019-04-25 13:01 ` Bjorn Helgaas
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=59dbed40fc0fad4a945cbfe09c9f622b81c7bd94.camel@redhat.com \
--to=lyude@redhat.com \
--cc=dober@lenovo.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=helgaas@kernel.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rjw@rjwysocki.net \
--cc=skeggsb@gmail.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).