All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Christoffer Dall <cdall@linaro.org>,
	kvm@vger.kernel.org, Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	marc.zyngier@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
	kvmarm@lists.cs.columbia.edu,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Vexpress TC2 no longer booting on v4.12-rc1
Date: Fri, 2 Jun 2017 23:24:50 +0100	[thread overview]
Message-ID: <20170602222449.GB4902@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CANLsYkz3dcVArStN2GJguYfJbWc_4dC4vvTE1KVtYpVWipEYjg@mail.gmail.com>

On Fri, Jun 02, 2017 at 04:16:59PM -0600, Mathieu Poirier wrote:
> Good afternoon Russell and friends,
> 
> I noticed that my vexpress-TC2 platform stopped booting when moving to
> kernel v4.12-rc1 (same with -rc2 and 3).  The last time things worked
> properly was on v4.11.  I did a bisect between v4.11 and v4.12-rc1 and
> ended up on [1], hence this email.
> 
> Since CONFIG_ARM_VIRT_EXT is selected by  default I removed the
> "#ifdef CONFIG_ARM_VIRT_EXT" section in the last hunk of the patch and
> the system sprung up to life again.

Hmm, this doesn't make much sense.  The code in last hunk of the patch
you refer to should only get run during system shutdown, not during
system boot, so I think something else is going on...

Please could you test again, this time rather than removing the #ifdef,
add two "mov r0, r0" there?  (So replacing the two instructions that
removing the ifdef would have exposed.)

Thanks.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

WARNING: multiple messages have this Message-ID (diff)
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Vexpress TC2 no longer booting on v4.12-rc1
Date: Fri, 2 Jun 2017 23:24:50 +0100	[thread overview]
Message-ID: <20170602222449.GB4902@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CANLsYkz3dcVArStN2GJguYfJbWc_4dC4vvTE1KVtYpVWipEYjg@mail.gmail.com>

On Fri, Jun 02, 2017 at 04:16:59PM -0600, Mathieu Poirier wrote:
> Good afternoon Russell and friends,
> 
> I noticed that my vexpress-TC2 platform stopped booting when moving to
> kernel v4.12-rc1 (same with -rc2 and 3).  The last time things worked
> properly was on v4.11.  I did a bisect between v4.11 and v4.12-rc1 and
> ended up on [1], hence this email.
> 
> Since CONFIG_ARM_VIRT_EXT is selected by  default I removed the
> "#ifdef CONFIG_ARM_VIRT_EXT" section in the last hunk of the patch and
> the system sprung up to life again.

Hmm, this doesn't make much sense.  The code in last hunk of the patch
you refer to should only get run during system shutdown, not during
system boot, so I think something else is going on...

Please could you test again, this time rather than removing the #ifdef,
add two "mov r0, r0" there?  (So replacing the two instructions that
removing the ifdef would have exposed.)

Thanks.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-06-02 22:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 22:16 Vexpress TC2 no longer booting on v4.12-rc1 Mathieu Poirier
2017-06-02 22:16 ` Mathieu Poirier
2017-06-02 22:24 ` Russell King - ARM Linux [this message]
2017-06-02 22:24   ` Russell King - ARM Linux
2017-06-05  1:47   ` Mathieu Poirier
2017-06-05  1:47     ` Mathieu Poirier
2017-06-05  7:43     ` Marc Zyngier
2017-06-05  7:43       ` Marc Zyngier
2017-06-05  9:18 ` Sudeep Holla
2017-06-05  9:18   ` Sudeep Holla
2017-06-05  9:27   ` Marc Zyngier
2017-06-05  9:27     ` Marc Zyngier

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=20170602222449.GB4902@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=cdall@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=mathieu.poirier@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.