linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <rogerq@ti.com>
Cc: Samuel Morris <samorris@lexmark.com>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	Tejun Heo <tj@kernel.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, 2 Jul 2018 02:32:43 -0700	[thread overview]
Message-ID: <20180702093243.GO112168@atomide.com> (raw)
In-Reply-To: <5206d66d-56d0-2edc-8dd0-00eedbaac3db@ti.com>

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?

Regards,

Tony

  reply	other threads:[~2018-07-02  9:32 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 [this message]
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
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=20180702093243.GO112168@atomide.com \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=olof@lixom.net \
    --cc=rafael@kernel.org \
    --cc=rogerq@ti.com \
    --cc=samorris@lexmark.com \
    --cc=ssantosh@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=tj@kernel.org \
    /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).