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>,
Peter Wu <peter@lekensteyn.nl>
Subject: Re: Kernel Freeze with American Megatrends BIOS
Date: Wed, 31 Aug 2016 13:11:54 +0200 [thread overview]
Message-ID: <ae547108-57bb-11a0-620b-f930ce8bf660@desertbit.com> (raw)
In-Reply-To: <CAKb7Uvjzhog27TUPTn5OOqXviyD_z3UV0qvskZDEO8CAB2-i2w@mail.gmail.com>
Am 30.08.2016 um 20:13 schrieb Ilia Mirkin:
> On Tue, Aug 30, 2016 at 2:02 PM, Roland Singer
> <roland.singer@desertbit.com> wrote:
>> 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.
>
> That's surprising. I believe there's an issue with the new logic when
> there's an HDMI audio subdevice. However that only appears if there's
> a cable plugged in, at least in the systems Peter tested. You should
> be able to see whether it's there or not with 'lspci'.
>
> You can check for sure by looking in the vgaswitcheroo state. It
> should say DynOff when it's powered off.
>
> Either way, I think using bbswitch + nouveau isn't supported by
> anyone, so if you want to use it that way, you're on your own. (You
> may want to load nouveau with runpm=0 so that nouveau doesn't try to
> manage the GPU suspend stuff.)
>
> -ilia
>
Kernel 4.8-rc4:
While running lspci, following kernel log message was printed on the TTY:
nouveau: 0000:01:00:0: priv: HUB0: 6013d4 0000573f (1f408200)
nouveau: 0000:01:00:0: priv: HUB0: 10ecc0 ffffffff (1940822c)
This is my output of lspci:
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #6 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO UART #0 (rev 31)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1)
3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)
next prev parent reply other threads:[~2016-08-31 11:13 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
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 [this message]
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=ae547108-57bb-11a0-620b-f930ce8bf660@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 \
--cc=peter@lekensteyn.nl \
/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).