From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: Diagnosing ACPI trouble related to pinctr_cherryview on 4.8.x
Date: Tue, 7 Feb 2017 16:52:01 +0200 [thread overview]
Message-ID: <20170207145201.GL19313@lahna.fi.intel.com> (raw)
In-Reply-To: <CACPiFC+zgmZkE3RDEHQfEFEq21zF9xz1_uoO9NQ7k=EU+rPJgg@mail.gmail.com>
On Tue, Feb 07, 2017 at 09:37:52AM -0500, Martin Langhoff wrote:
> About a year ago, I tried to get this laptop going with Fedora's 4.4
> kernel, and we had this thread -
> http://www.spinics.net/lists/linux-gpio/msg13139.html
>
> Now I have that laptop back, and it only boots with the custom-built
> 4.4 I prepared back then.
>
> The exact same behaviour is observed with 4.8.x (4.8.15 from latest
> Fedora at the moment). Won't boot. Disabling ACPI won't do it.
>
> Has there been any progress on pinctrl_cherryview, is there perhaps a
> branch/tree with new configs I should test?
I remember this and I ordered the same Acer Aspire One 11 Cloudbook here
but I did not see any issues with it. I still have the machine here so I
can debug if any problems are found.
Just to be sure, can you first boot the mainline kernel v4.10-rc7 (or
close) and let me know how it fails (including dmesg if you can extract
one)?
next prev parent reply other threads:[~2017-02-07 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:37 Diagnosing ACPI trouble related to pinctr_cherryview on 4.8.x Martin Langhoff
2017-02-07 14:52 ` Mika Westerberg [this message]
2017-02-07 15:13 ` Martin Langhoff
2017-02-07 15:29 ` Martin Langhoff
2017-02-07 15:48 ` Mika Westerberg
2017-02-07 16:11 ` Martin Langhoff
2017-02-07 16:30 ` Mika Westerberg
2017-02-08 19:27 ` Martin Langhoff
2017-02-09 9:10 ` Mika Westerberg
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=20170207145201.GL19313@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=martin.langhoff@gmail.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).