linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Tony Lindgren <tony@atomide.com>
Cc: David Howells <dhowells@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Regression in next with filesystem context concept
Date: Mon, 10 Sep 2018 12:32:35 -0700	[thread overview]
Message-ID: <20180910193235.GA8769@roeck-us.net> (raw)
In-Reply-To: <20180910192658.GX5662@atomide.com>

On Mon, Sep 10, 2018 at 12:26:58PM -0700, Tony Lindgren wrote:
> * Guenter Roeck <linux@roeck-us.net> [180910 18:35]:
> > On Mon, Sep 10, 2018 at 09:08:36AM -0700, Tony Lindgren wrote:
> > > OK thanks for tracking that down, next-20180910 boots again
> > > for me.
> > > 
> > 
> > Did you try to shutdown and/or reboot ?
> > 
> > You might see something like the attached if you try.
> 
> Hmm not seeing that here with next-20180910 on ARM at least.
> 

Correct, the problem doesn't happen on arm. That is the one
and only exception as far as I can see.

On arm, the only boot failure is witherspoon-bmc with
aspeed_g5_defconfig, but that doesn't crash but simply hang
during boot.

arm64 still fails to build, so I don't have any data there.

Guenter

      reply	other threads:[~2018-09-11  0:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 16:43 Tony Lindgren
2018-09-06 18:11 ` Naresh Kamboju
2018-09-07  8:47 ` David Howells
2018-09-07 16:10   ` Tony Lindgren
2018-09-07 17:35     ` Andreas Kemnade
2018-09-08 15:24   ` David Howells
2018-09-10 16:08     ` Tony Lindgren
2018-09-10 18:31       ` Guenter Roeck
2018-09-10 19:26         ` Tony Lindgren
2018-09-10 19:32           ` Guenter Roeck [this message]

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=20180910193235.GA8769@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dhowells@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tony@atomide.com \
    --subject='Re: Regression in next with filesystem context concept' \
    /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

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).