From: Vicente Bergas <vicencb@gmail.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Will Deacon <will@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>, <marc.zyngier@arm.com>
Subject: Re: d_lookup: Unable to handle kernel paging request
Date: Tue, 25 Jun 2019 12:48:17 +0200 [thread overview]
Message-ID: <c53a0fb8-d640-4d58-b339-0a7ea10aa621@gmail.com> (raw)
In-Reply-To: <20190625094602.GC13263@fuggles.cambridge.arm.com>
On Tuesday, June 25, 2019 11:46:02 AM CEST, Will Deacon wrote:
> [+Marc]
>
> Hi again, Vicente,
>
> On Mon, Jun 24, 2019 at 12:47:41PM +0100, Will Deacon wrote:
>> On Sat, Jun 22, 2019 at 08:02:19PM +0200, Vicente Bergas wrote: ...
>
> Before you rush over to LAKML, please could you provide your full dmesg
> output from the kernel that was crashing (i.e. the dmesg you see in the
> kexec'd kernel)? We've got a theory that the issue may be related to the
> interrupt controller, and the dmesg output should help to establish whether
> that is plausible or not.
>
> Thanks,
>
> Will
Hi Will,
the memtest test is still pending...
Regarding interrupts, the kernel before kexec has this parameter:
irqchip.gicv3_nolpi=1
Thanks to Marc:
https://freenode.irclog.whitequark.org/linux-rockchip/2018-11-20#23524255
The kernel messages are here:
https://paste.debian.net/1089170/
https://paste.debian.net/1089171/
Regards,
Vicenç.
next prev parent reply other threads:[~2019-06-25 10:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 10:40 d_lookup: Unable to handle kernel paging request Vicente Bergas
2019-05-22 13:53 ` Al Viro
2019-05-22 15:44 ` Vicente Bergas
2019-05-22 16:29 ` Al Viro
2019-05-24 22:21 ` Vicente Bergas
2019-05-28 9:38 ` Vicente Bergas
2019-06-18 18:35 ` Al Viro
2019-06-18 18:48 ` Al Viro
2019-06-19 12:42 ` Vicente Bergas
2019-06-19 16:28 ` Al Viro
2019-06-19 16:51 ` Vicente Bergas
2019-06-19 17:06 ` Will Deacon
2019-06-19 17:09 ` Al Viro
2019-06-22 18:02 ` Vicente Bergas
2019-06-24 11:47 ` Will Deacon
2019-06-25 9:46 ` Will Deacon
2019-06-25 10:48 ` Vicente Bergas [this message]
2019-06-29 22:56 ` Vicente Bergas
2019-06-19 17:04 ` Will Deacon
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=c53a0fb8-d640-4d58-b339-0a7ea10aa621@gmail.com \
--to=vicencb@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will.deacon@arm.com \
--cc=will@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).