From: Emil Velikov <emil.l.velikov@gmail.com>
To: Roland Singer <roland.singer@desertbit.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
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, Ilia Mirkin <imirkin@alum.mit.edu>
Subject: Re: Kernel Freeze with American Megatrends BIOS
Date: Tue, 30 Aug 2016 19:10:31 +0100 [thread overview]
Message-ID: <CACvgo51OodZGqnrBCusXGycdibR8PY4wBfUZOjEhQ=1TyPenrg@mail.gmail.com> (raw)
In-Reply-To: <CACvgo52qA9YyaskNObO_f_gg51MqBZHN7mubshJhDUcgO8SZaQ@mail.gmail.com>
On 30 August 2016 at 19:09, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> On 30 August 2016 at 18:37, Roland Singer <roland.singer@desertbit.com> wrote:
>> I am running 4.7.2, but I also just tried the 4.8.0-rc4 mainline kernel.
>> The result is the same. There is no difference if bbswitch of acpi_call
>> is used. However I noticed following:
>>
>> 1. The nouveau driver is broken in both kernel version and is responsible
>> for the freezes while gathering power state information with bbswitch.
>> Sometimes while shutting the system down, everything except the LCD
>> screen is switched off. This only happens with nouveau.
>> I noticed following error log messages:
>>
> I second Ilia here. Using bbswitch in conjunction with any driver (be
> that nouveau or the proprietary one) is a bad idea.
>
>> kernel: nouveau 0000:01:00.0: fb: 6144 MiB GDDR5
>> kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1e40822c)
>> kernel: nouveau 0000:01:00.0: DRM: VRAM: 6144 MiB
>> kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
>> kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
>> kernel: nouveau 0000:01:00.0: DRM: DCB version 4.1
>> kernel: nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
>>
>> 2. -> Boot with nouveau module loaded
>> -> switch off the discrete GPU with bbswitch or acpi_call
>> -> start X11
>> -> obtaining power state with bbswitch freezes the system
>> -> or working with the system for some minutes freezes the system
>>
> (If Ilia's suggestions does not help) Confirm if the freeze is due
> to/as the GPU is powered on or off.
>
>> 3. -> Boot with nouveau module blacklisted
>> -> switch off the discrete GPU
>> -> start X11
>> -> system immediately freezes
>>
> It's perfectly possible that the discrete GPU is set as boot one and X
> goes angry since there's no driver/way to bring it up.
>
>> 4. -> Boot with nouveau module blacklisted
>> -> switch off the discrete GPU
>> -> start Wayland
>> -> system runs - Note: I tried this for couple of days with 4.6 and 4.7 mainline
>> and the system freezed randomly after some time.
>> However I have to test if this is still present with 4.7.2
>> and 4.8 mainline. Right now it seams to be fine.
>> -> running Xwayland (does not depend on the GPU power state) kills performance!
>> the system freezes for several seconds...
>> So working with Wayland is also no solution.
>>
>> My conclusion:
>>
>> 1. Nouveau has couple of problems with GTX 9** M Nvidia GPUs.
>> I would love to help here.
>>
>> 2. X11 is just broken and is not capable to start the graphical session
>> if the nvidia GPU is not handled by any video driver (kernel module).
>> Even forcing X11 to ignore the discrete GPU doesn't help.
>>
> Out of curiosity: how did you force X to ignore the device ?
>
>> Setting the command line arguments to:
>>
>> acpi_osi=! acpi_osi="Windows 2009"
>>
>> fixes the issues with X11 but other things break...
>> What the hell is going on?! :/
>>
> You can check if it's the boot_vga assumption with
>
[Sorry about that] ...
cat /sys/class/drm/card*/device/{boot_vga,vendor}
If the output changes them my assumption holds true.
-Emil
next prev parent reply other threads:[~2016-08-30 18:10 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
2016-08-30 18:09 ` Emil Velikov
2016-08-30 18:10 ` Emil Velikov [this message]
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='CACvgo51OodZGqnrBCusXGycdibR8PY4wBfUZOjEhQ=1TyPenrg@mail.gmail.com' \
--to=emil.l.velikov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--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=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).