From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Samuel Morris <samorris@lexmark•com>, Tejun Heo <tj@kernel•org>
Cc: Tony Lindgren <tony@atomide•com>, Roger Quadros <rogerq@ti•com>,
Naresh Kamboju <naresh.kamboju@linaro•org>,
linux-omap@vger•kernel.org,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
open list <linux-kernel@vger•kernel.org>,
Arnd Bergmann <arnd@arndb•de>,
ssantosh@kernel•org, Olof Johansson <olof@lixom•net>,
Tero Kristo <t-kristo@ti•com>,
"Rafael J. Wysocki" <rafael@kernel•org>
Subject: Re: 4.18.0-rc1-next-20180619 boot failed on beagle board x15
Date: Mon, 6 Aug 2018 09:30:15 +1000 [thread overview]
Message-ID: <20180806093015.6099ef5c@canb.auug.org.au> (raw)
In-Reply-To: <CAFY_6qo83Ui6_xRkuTYZUduUJSK2dLKhzd+B_nQ-XW5ciDH-7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
Hi Samuel,
On Mon, 2 Jul 2018 09:31:56 -0400 Samuel Morris <samorris@lexmark•com> wrote:
>
> On Mon, Jul 2, 2018 at 5:32 AM, Tony Lindgren <tony@atomide•com> wrote:
> > Hi,
> >
> > * Roger Quadros <rogerq@ti•com> [180621 14:56]:
> >> On 21/06/18 17:31, Samuel Morris wrote:
> >> > On Thu, Jun 21, 2018 at 3:58 AM, Roger Quadros <rogerq@ti•com> wrote:
> >> >> +Rafael
> >> >>
> >> >> On 20/06/18 18:30, Samuel Morris wrote:
> >> >>> On Wed, Jun 20, 2018 at 8:58 AM, Roger Quadros <rogerq@ti•com> wrote:
> >> >>>> Tony,
> >> >>>>
> >> >>>> On 20/06/18 13:29, Tony Lindgren wrote:
> >> >>>>> Hi,
> >> >>>>>
> >> >>>>> * Naresh Kamboju <naresh.kamboju@linaro•org> [180620 05:55]:
> >> >>>>>> Linux next (4.18.0-rc1-next-20180619) boot failed on beagle board x15.
> >> >>>>>
> >> >>>>> Bisect points to commit aece27a2f01b ("ata: ahci_platform: allow disabling of
> >> >>>>> hotplug to save power").
> >> >>>>>
> >> >>>>> Reverting the patch makes things work again. Any ideas what
> >> >>>>> might be going wrong here? Things clearly idle but then there
> >> >>>>> seems to be some register access with clocks disabled.
> >
> > So this issue is still happening as of next-20180702. Can you guys
> > please revert the commit above while working on a better solution?
>
> That's fine with me. I'm not very familiar with the process here, does
> this require anything on my end? And would that require the
> accompanying patch to be reverted: "ata: ahci: rpm_put port on
> port_stop to match rpm_get in port_start"? There shouldn't be any
> problem leaving that one in, but I just want to know before submitting
> my next patch set.
I am still reverting that commit from linux-next myself. Has this
issue been fixed some other way, or is it still ongoing?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-05 23:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 5:52 4.18.0-rc1-next-20180619 boot failed on beagle board x15 Naresh Kamboju
2018-06-20 10:29 ` Tony Lindgren
2018-06-20 12:57 ` Samuel Morris
2018-06-20 12:58 ` Roger Quadros
2018-06-20 15:30 ` Samuel Morris
2018-06-21 7:58 ` Roger Quadros
2018-06-21 12:02 ` Rafael J. Wysocki
2018-06-21 14:31 ` Samuel Morris
2018-06-21 14:53 ` Roger Quadros
2018-07-02 9:32 ` Tony Lindgren
2018-07-02 13:31 ` Samuel Morris
2018-07-17 6:08 ` Tony Lindgren
2018-07-17 8:00 ` Stephen Rothwell
2018-07-17 8:03 ` Tony Lindgren
2018-07-18 5:05 ` Keerthy
2018-08-05 23:30 ` Stephen Rothwell [this message]
2018-08-06 17:24 ` Tejun Heo
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=20180806093015.6099ef5c@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=olof@lixom$(echo .)net \
--cc=rafael@kernel$(echo .)org \
--cc=rogerq@ti$(echo .)com \
--cc=samorris@lexmark$(echo .)com \
--cc=ssantosh@kernel$(echo .)org \
--cc=t-kristo@ti$(echo .)com \
--cc=tj@kernel$(echo .)org \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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