regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>,
	 open list <linux-kernel@vger.kernel.org>,
	Will Deacon <will@kernel.org>,
	 lkft-triage@lists.linaro.org, regressions@lists.linux.dev
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	 Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	 Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [next] [arm64] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000068
Date: Tue, 15 Jun 2021 16:56:31 +0530	[thread overview]
Message-ID: <CA+G9fYschBRxbugv19pZegUG6+Y10dJfJr7RHQE7M+Z_3RgqrQ@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYurEcTfV7Z=co2Ki-TubF4d-Ext7ivZPaQT9SR5XazUtQ@mail.gmail.com>

On Tue, 15 Jun 2021 at 16:49, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Following kernel crash reported while booting linux next 20210615 tag
> on qemu_arm64.

Similar crash reported while booting Linux next 20210615 tag kernel on
the qemu arm.

https://lkft.validation.linaro.org/scheduler/job/2901326#L441

>
> Crash log:
> -------------
> [    0.767379] Unable to handle kernel NULL pointer dereference at
> virtual address 0000000000000068
> [    0.769815] Mem abort info:
> [    0.770735]   ESR = 0x96000004
> [    0.771598]   EC = 0x25: DABT (current EL), IL = 32 bits
> [    0.773008]   SET = 0, FnV = 0
> [    0.773865]   EA = 0, S1PTW = 0
> [    0.774844]   FSC = 0x04: level 0 translation fault
> [    0.776195] Data abort info:
> [    0.776968]   ISV = 0, ISS = 0x00000004
> [    0.778010]   CM = 0, WnR = 0
> [    0.778961] [0000000000000068] user address but active_mm is swapper
> [    0.780643] Internal error: Oops: 96000004 [#1] PREEMPT SMP
> [    0.782189] Modules linked in:
> [    0.783098] CPU: 2 PID: 1 Comm: swapper/0 Not tainted
> 5.13.0-rc6-next-20210615 #1
> [    0.785239] Hardware name: linux,dummy-virt (DT)
> [    0.786626] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--)
> [    0.788352] pc : blk_finish_plug+0x88/0x270
> [    0.789598] lr : blk_queue_write_cache+0x34/0x80
d.com/1tyksDCCPiTvc0x6psxC3JvSWqJ/config

- Naresh

  reply	other threads:[~2021-06-15 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 11:19 [next] [arm64] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000068 Naresh Kamboju
2021-06-15 11:26 ` Naresh Kamboju [this message]
2021-06-15 23:26 ` Andrew Morton
2021-06-16 12:55   ` Jens Axboe

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=CA+G9fYschBRxbugv19pZegUG6+Y10dJfJr7RHQE7M+Z_3RgqrQ@mail.gmail.com \
    --to=naresh.kamboju@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=rppt@linux.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --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).