From: Roland Singer <roland.singer@desertbit.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Emil Velikov <emil.l.velikov@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Kernel Freeze with American Megatrends BIOS
Date: Tue, 30 Aug 2016 20:02:11 +0200 [thread overview]
Message-ID: <1c761bab-f82b-3f43-c4f0-c7a8eff94f25@desertbit.com> (raw)
In-Reply-To: <CAKb7UviZ0qKp3PRR+iHr+KiOU9Sadeeb6PyydWN-FUL0RzyCPA@mail.gmail.com>
I configured bbswitch to not set any states automatically...
So it's possible to obtain and verify the GPU power state.
However I removed the bbswitch module and booted with nouveau.
Kernel 4.7.2: nouveau switches the discrete GPU off.
I can't trigger the freeze, because bbswitch is missing.
I'll work with the system and see if it will freeze.
Kernel 4.8-rc4: nouveau does not care about the power state and
the discrete GPU is never switched off. I will notice
this, because the second cooling FAN will stop...
Same log messages as send before.
Am 30.08.2016 um 19:43 schrieb Ilia Mirkin:
> On Tue, Aug 30, 2016 at 1:37 PM, Roland Singer
> <roland.singer@desertbit.com> wrote:
>> My conclusion:
>>
>> 1. Nouveau has couple of problems with GTX 9** M Nvidia GPUs.
>> I would love to help here.
>
> nouveau + bbswitch will always end in tears. You're going behind the
> driver's back and messing around with state it believes it is
> managing. What if you just use nouveau and let it auto-power-off the
> GPU like it's designed to, with v4.8-rc?
>
> -ilia
>
next prev parent reply other threads:[~2016-08-30 18:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <004c7dbe-2014-c691-29d1-7a45f3b73dfa@desertbit.com>
2016-08-29 16:02 ` Kernel Freeze with American Megatrends BIOS Bjorn Helgaas
2016-08-29 18:46 ` Roland Singer
2016-08-29 19:07 ` Bjorn Helgaas
2016-08-29 19:55 ` Roland Singer
2016-08-29 23:54 ` Bjorn Helgaas
2016-08-30 10:08 ` Roland Singer
2016-08-30 13:06 ` Bjorn Helgaas
2016-08-30 14:08 ` Emil Velikov
2016-08-30 15:25 ` Roland Singer
2016-08-30 15:44 ` Ilia Mirkin
2016-08-30 15:48 ` Ilia Mirkin
2016-08-30 15:48 ` Emil Velikov
2016-08-30 17:37 ` Roland Singer
2016-08-30 17:43 ` Ilia Mirkin
2016-08-30 18:02 ` Roland Singer [this message]
2016-08-30 18:13 ` Ilia Mirkin
2016-08-30 19:21 ` Peter Wu
2016-08-31 11:12 ` Roland Singer
2016-08-31 11:11 ` Roland Singer
2016-08-30 18:09 ` Emil Velikov
2016-08-30 18:10 ` Emil Velikov
2016-08-31 10:51 ` Roland Singer
2016-08-30 19:53 ` Peter Wu
2016-08-31 11:27 ` Roland Singer
2016-08-31 11:46 ` Peter Wu
2016-08-31 12:21 ` Roland Singer
2016-08-31 12:34 ` Peter Wu
2016-08-31 13:13 ` Roland Singer
2016-08-31 20:06 ` Roland Singer
2016-08-31 20:16 ` Roland Singer
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=1c761bab-f82b-3f43-c4f0-c7a8eff94f25@desertbit.com \
--to=roland.singer@desertbit.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=helgaas@kernel.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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).