public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Chris Chiu <chiu@endlessm.com>
Cc: linux-acpi@vger.kernel.org, Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: Can't even enter X after kernel 4.12
Date: Tue, 5 Dec 2017 20:09:25 +0100	[thread overview]
Message-ID: <7634b10f-cc73-4e82-1bef-b0ba837e6ccb@redhat.com> (raw)
In-Reply-To: <CAB4CAwerG4eOFAPP9bWP_cQiKmcmB7bEwTjSag9dzdkWy5E12g@mail.gmail.com>

Hi,

On 05-12-17 16:42, Chris Chiu wrote:
> On Tue, Dec 5, 2017 at 6:40 AM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Hi Chris,
>>
>> On 30-11-17 07:27, Chris Chiu wrote:
>>>
>>> Hi,
>>>       I have a Intel cherry trail machine Haier HR101CW (CPU: x5-Z8350)
>>> which used to work fine in kernel 4.11, fails to enter X after I
>>> upgrade to kernel version later than 4.12. Even the latest 4.15, it
>>> can't even enter X now. There's no panic, oops and even no obvious
>>> error log. The panel backlight seems to be off but keyboard still
>>> responds.
>>>
>>>       Then I tried to do bisect, it tells me the commit
>>> [b7ecf663c75eed1e764f57281f9508c49c18516e] ACPI / bus: Introduce a
>>> list of ids for "always present" devices is the one which causes this.
>>> After I revert this commit, the display back to normal.
>>>
>>>       Maybe the DSDT file would help for your reference.
>>> https://gist.github.com/mschiu77/e84687cc928ac644117baf05aef47f16
>>
>>
>> Hmm, Daniel Drake from Endless send me a Vios LTH17 machine which
>> has similar symptoms. If this is indeed the same issue then adding:
>> i915.fastboot=1 to the kernel commandline should fix this.
>>
>> This is going to be the default for newer kernels soon-ish (4.16
>> I think), so we can use this as a workaround for now.
>>
>> As for the commit you bisected this to, can you try just commenting
>> out the: "80862288" entry in always_present_ids in
>> drivers/acpi/x86/utils.c ? I think that is triggering the problem.
>>
>> Without that entry we don't get backlight control, so if you
>> comment it you will likely not be able to control brightness,
>> so i915.fastboot=1 is a better fix, but it would be good to know
>> if commenting out just that entry fixes things (and breaks
>> brightness control).
>>
>> Without i915.fastboot=1 the i915 driver quickly turns the
>> backlight off and on again at boot, which I guess is confusing
>> the LCD panel...
>>
>> Regards,
>>
>> Hans
>>
> 
> Hmm...the i915.fastboot=1 seems not work on my Haier machine here.
> However, comment out the: "80862288" entry in always_present_ids in
> drivers/acpi/x86/utils.c do work. Do you need anything on this special
> machine?

On the VIOS LTH17 I just need i915.fastboot=1 and then things work
(with a 4.14 kernel) the 80862288 entry in that table makes Linux bind
to the pwm controller in the Z8350, which is usually used for brightness
control.

Do you get a brightness slider in gnome3 with the 80862288 entry commented
out? And does it work ?

Regards,

Hans


      reply	other threads:[~2017-12-05 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  6:27 Can't even enter X after kernel 4.12 Chris Chiu
2017-12-04 22:40 ` Hans de Goede
2017-12-05 15:42   ` Chris Chiu
2017-12-05 19:09     ` Hans de Goede [this message]

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=7634b10f-cc73-4e82-1bef-b0ba837e6ccb@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=chiu@endlessm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux@endlessm.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