linux-kernel - Re: 4.18.0-rc1-next-20180619 boot failed on beagle board x15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFY_6qo83Ui6_xRkuTYZUduUJSK2dLKhzd+B_nQ-XW5ciDH-7A@mail.gmail.com>
Date:   Mon, 2 Jul 2018 09:31:56 -0400
From:   Samuel Morris <samorris@...mark.com>
To:     Tony Lindgren <tony@...mide.com>
Cc:     Roger Quadros <rogerq@...com>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        Tejun Heo <tj@...nel.org>, linux-omap@...r.kernel.org,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>, ssantosh@...nel.org,
        Olof Johansson <olof@...om.net>, Tero Kristo <t-kristo@...com>,
        "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: 4.18.0-rc1-next-20180619 boot failed on beagle board x15

On Mon, Jul 2, 2018 at 5:32 AM, Tony Lindgren <tony@...mide.com> wrote:
> Hi,
>
> * Roger Quadros <rogerq@...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@...com> wrote:
>> >> +Rafael
>> >>
>> >> On 20/06/18 18:30, Samuel Morris wrote:
>> >>> On Wed, Jun 20, 2018 at 8:58 AM, Roger Quadros <rogerq@...com> wrote:
>> >>>> Tony,
>> >>>>
>> >>>> On 20/06/18 13:29, Tony Lindgren wrote:
>> >>>>> Hi,
>> >>>>>
>> >>>>> * Naresh Kamboju <naresh.kamboju@...aro.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.

>
> Regards,
>
> Tony