From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Thomas Voegtle <tv@lio96.de>, daniel.vetter@ffwll.ch
Cc: liviu@dudau.co.uk, john.stultz@linaro.org, treding@nvidia.com,
linux-kernel@vger.kernel.org
Subject: Re: v4.14/v4.15-rc1: deferred setup in drm/fb-helper breaks entering pc3
Date: Tue, 28 Nov 2017 10:18:33 +0100 [thread overview]
Message-ID: <575fff87-908c-c1d6-b504-54ec1f342662@linux.intel.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1711271859120.24103@er-systems.de>
Op 27-11-17 om 19:09 schreef Thomas Voegtle:
>
> Hello,
>
> with v4.14 I recognized that my file server (headless haswell system)
> doesn't enter packages pc3 anymore and only enters pc2 according to
> powertop.
> In v4.13 the system used pc2 and pc3.
>
> So I bisected that down to:
>
> ca91a2758fcef6635626993557dd51cfbb6dd134 is the first bad commit
> commit ca91a2758fcef6635626993557dd51cfbb6dd134
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Thu Jul 6 15:00:21 2017 +0200
>
> drm/fb-helper: Support deferred setup
>
>
> Reverting this commit on top of v4.14 and v4.15-rc1 fixes the problem and
> the system uses package states pc2 and pc3 again.
>
> Nothing is connected to the VGA and DVI port.
> I'm using a kernel without modules on openSUSE 42.3.
> I have no "vga=xxx" or something like that on the cmdline.
>
>
> Thanks,
>
> Thomas
>
Could you send some logs with drm.debug=0x1f ?
~Maarten
next prev parent reply other threads:[~2017-11-28 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 18:09 Thomas Voegtle
2017-11-28 9:18 ` Maarten Lankhorst [this message]
2017-11-28 9:30 ` Thomas Voegtle
2017-11-28 9:48 ` Maarten Lankhorst
2017-11-28 10:28 ` Thomas Voegtle
2017-11-28 11:16 ` [PATCH] drm/fb_helper: Disable all crtc's when initial setup fails Maarten Lankhorst
2017-11-28 11:49 ` Daniel Vetter
2017-11-28 15:13 ` Thomas Voegtle
2017-11-29 14:40 ` Maarten Lankhorst
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=575fff87-908c-c1d6-b504-54ec1f342662@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu@dudau.co.uk \
--cc=treding@nvidia.com \
--cc=tv@lio96.de \
/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
Powered by JetHome