linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: julien.grall@citrix.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add support for hardware updates of the access and dirty pte bits
Date: Wed, 9 Sep 2015 19:27:43 +0100	[thread overview]
Message-ID: <55F07A1F.3030809@citrix.com> (raw)
In-Reply-To: <20150909182246.GA1491@leverpostej>

On 09/09/15 19:22, Mark Rutland wrote:
> On Wed, Sep 09, 2015 at 06:21:11PM +0100, Julien Grall wrote:
>> The bisector pointed me to this patch. When I disable
>> CONFIG_ARM64_HW_AFDBM, I'm able to boot the kernel and use it
>> without any issue.
> 
> Is the failure identical each time (e.g. is it always in the same
> location)?

Yes, the failure and the stack trace is identical every time. It's
occurring quickly after the userspace is starting.

Note that I was able to reproduce the problem on baremetal too.

I didn't know it when I send the first email as I was hunting down
another issue while booting linux/master on baremetal on xgene.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-09-09 18:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 16:24 [PATCH] arm64: Add support for hardware updates of the access and dirty pte bits Catalin Marinas
2015-09-09 17:21 ` Julien Grall
2015-09-09 18:22   ` Mark Rutland
2015-09-09 18:27     ` Julien Grall [this message]
2015-09-10 10:07   ` Catalin Marinas
2015-09-10 10:41     ` Will Deacon
2015-09-10 14:45     ` Julien Grall
2015-09-10 14:54       ` Marc Zyngier
2015-09-10 15:10         ` Julien Grall
2015-09-10 15:21           ` Marc Zyngier
2015-09-10 15:38       ` Will Deacon
2015-09-11 15:43         ` Julien Grall
2015-09-10 13:01   ` Marc Zyngier
2015-09-10 14:29     ` Julien Grall
2015-09-10 14:49       ` Marc Zyngier
2015-09-10 14:58         ` Julien Grall

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=55F07A1F.3030809@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=linux-arm-kernel@lists.infradead.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).