From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2F6F3ECDFB1 for ; Tue, 17 Jul 2018 08:03:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DC2532086E for ; Tue, 17 Jul 2018 08:03:40 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DC2532086E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=atomide.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729706AbeGQIe7 convert rfc822-to-8bit (ORCPT ); Tue, 17 Jul 2018 04:34:59 -0400 Received: from muru.com ([72.249.23.125]:51802 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727796AbeGQIe7 (ORCPT ); Tue, 17 Jul 2018 04:34:59 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 1CDA1814A; Tue, 17 Jul 2018 08:06:48 +0000 (UTC) Date: Tue, 17 Jul 2018 01:03:35 -0700 From: Tony Lindgren To: Stephen Rothwell Cc: Tejun Heo , Roger Quadros , Naresh Kamboju , linux-omap@vger.kernel.org, Linux-Next Mailing List , open list , Arnd Bergmann , ssantosh@kernel.org, Olof Johansson , Tero Kristo , "Rafael J. Wysocki" , Samuel Morris Subject: Re: 4.18.0-rc1-next-20180619 boot failed on beagle board x15 Message-ID: <20180717080335.GD99251@atomide.com> References: <20180620102904.GC112168@atomide.com> <6c15a753-c4a8-ff89-f5c0-0fd19c817c91@ti.com> <5206d66d-56d0-2edc-8dd0-00eedbaac3db@ti.com> <20180702093243.GO112168@atomide.com> <20180717060808.GW99251@atomide.com> <20180717180028.0ba098f6@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <20180717180028.0ba098f6@canb.auug.org.au> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Stephen Rothwell [180717 08:03]: > Hi Tony, > > On Mon, 16 Jul 2018 23:08:08 -0700 Tony Lindgren wrote: > > > > The following regression is still pending in next, see below. > > > > * Samuel Morris [180702 13:35]: > > > On Mon, Jul 2, 2018 at 5:32 AM, Tony Lindgren wrote: > > > > Hi, > > > > > > > > * Roger Quadros [180621 14:56]: > > > >> On 21/06/18 17:31, Samuel Morris wrote: > > > >> > On Thu, Jun 21, 2018 at 3:58 AM, Roger Quadros wrote: > > > >> >> +Rafael > > > >> >> > > > >> >> On 20/06/18 18:30, Samuel Morris wrote: > > > >> >>> On Wed, Jun 20, 2018 at 8:58 AM, Roger Quadros wrote: > > > >> >>>> Tony, > > > >> >>>> > > > >> >>>> On 20/06/18 13:29, Tony Lindgren wrote: > > > >> >>>>> Hi, > > > >> >>>>> > > > >> >>>>> * Naresh Kamboju [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. > > > > Well usually the maintainer just reverts the regression causing > > patch in the related branch and that's it. > > > > Stephen, can you please revert in next until we hear back from > > Tejun? > > OK, I have reverted that commit from today. Please let me know when the > problem is fixed in the libata tree ... Thanks! Tony