Hi Samuel,
On Mon, 2 Jul 2018 09:31:56 -0400 Samuel Morris <samor...@lexmark.com> wrote:
>
> On Mon, Jul 2, 2018 at 5:32 AM, Tony Lindgren <t...@atomide.com> wrote:
> > Hi,
> >
> > * Roger Quadros <rog...@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 <rog...@ti.com> wrote:
> >> >> +Rafael
> >> >>
> >> >> On 20/06/18 18:30, Samuel Morris wrote:
> >> >>> On Wed, Jun 20, 2018 at 8:58 AM, Roger Quadros <rog...@ti.com> wrote:
> >> >>>> Tony,
> >> >>>>
> >> >>>> On 20/06/18 13:29, Tony Lindgren wrote:
> >> >>>>> Hi,
> >> >>>>>
> >> >>>>> * Naresh Kamboju <naresh.kamb...@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
pgp3jTcoeyHyQ.pgp
Description: OpenPGP digital signature
