From: Bjorn Helgaas <helgaas@kernel.org>
To: Roland Singer <roland.singer@desertbit.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernel Freeze with American Megatrends BIOS
Date: Mon, 29 Aug 2016 11:02:10 -0500 [thread overview]
Message-ID: <20160829160210.GA24451@localhost> (raw)
In-Reply-To: <004c7dbe-2014-c691-29d1-7a45f3b73dfa@desertbit.com>
[+cc linux-acpi, linux-kernel, dri-devel]
Hi Roland,
I have no idea how to debug this problem. Are you seeing something
that suggests it may be a PCI problem?
On Tue, Aug 23, 2016 at 11:23:45AM +0200, Roland Singer wrote:
> Hi,
>
> hope somebody can help me fix this kernel problem which affects the following machines:
>
> - Clevo P651RA (i7-6700HQ/GTX 965M, part of the P6xxRx family which are also affected)
> - MSI GE62 Apache Pro (i7-6700HQ/GTX 960M)
> - Gigabyte P35V5 (i7-6700HQ/GTX 970M)
> - Razer Blade 14" (2016) (i7-6700HQ/GTX 970M) (BIOS 5.11, 04/07/2016)
>
>
> The kernel freezes if the graphical user session (Xorg & Wayland) is
> started with a switched off discrete GPU card (NVIDIA).
> If the discrete GPU is switched off after the graphical session start,
> then everything works as expected, until the graphical session is restarted.
>
> This problem seams to be linked to specific BIOS settings. If the computer
> is started with the following command line:
>
> acpi_osi=! acpi_osi="Windows 2009"
>
> then the kernel freeze does not occur anymore. However this required a special
> ACPI DSDT firmware patch for the Razer Blade 2016 laptop:
>
> https://github.com/m4ng0squ4sh/razer_blade_14_2016_acpi_dsdt
>
> I strongly recommend to fix this in the kernel and I am ready to help and solve
> this problem with some help.
>
> Here is a link to the GitHub issue with further information:
>
> https://github.com/Bumblebee-Project/Bumblebee/issues/764#issuecomment-241212595
>
> Here are some more detailed information:
>
> https://github.com/Lekensteyn/acpi-stuff/blob/master/Clevo-P651RA/notes.txt
>
> Hope somebody can help.
next parent reply other threads:[~2016-08-29 16:02 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 ` Bjorn Helgaas [this message]
2016-08-29 18:46 ` Kernel Freeze with American Megatrends BIOS 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
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=20160829160210.GA24451@localhost \
--to=helgaas@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=roland.singer@desertbit.com \
/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).