public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: "Christopher M. Riedl" <cmr@bluescreens.de>,
	Benjamin Gray <bgray@linux.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: boot failure after merge of the powerpc tree
Date: Fri, 02 Dec 2022 20:36:12 +1100	[thread overview]
Message-ID: <87o7sm171v.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20221202143110.0f00c3e5@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> After merging all the trees, today's linux-next qemu run (powerpc
> pseries_le_defconfig with kvm) crashed like this:
>
> Memory: 2029504K/2097152K available (14592K kernel code, 2944K rwdata, 18176K rodata, 5120K init, 1468K bss, 67648K reserved, 0K cma-reserved)
> SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> BUG: Kernel NULL pointer dereference on read at 0x0000001c
> Faulting instruction address: 0xc00000000047e9bc
> Oops: Kernel access of bad area, sig: 7 [#1]
> LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Not tainted 6.1.0-rc7 #1
> Hardware name: IBM pSeries (emulated by qemu) POWER9 (raw) 0x4e1202 0xf000005 of:SLOF,HEAD hv:linux,kvm pSeries
> NIP:  c00000000047e9bc LR: c000000000e06718 CTR: c00000000047e970
> REGS: c000000002773770 TRAP: 0300   Not tainted  (6.1.0-rc7)
> MSR:  8000000002001033 <SF,VEC,ME,IR,DR,RI,LE>  CR: 22004220  XER: 00000000
> CFAR: c000000000070508 DAR: 000000000000001c DSISR: 00080000 IRQMASK: 3 
> GPR00: c000000000e06718 c000000002773a10 c00000000116fc00 0000000000000000 
> GPR04: 0000000000002900 0000000000002800 0000000000000000 0000000000000000 
> GPR08: 000000000000000e c0000000027afc00 0000000000000000 0000000000004000 
> GPR12: c00000000047e970 c000000002950000 0000000000000000 00000000013c8ff0 
> GPR16: 000000000000000d 0000000002be00d0 0000000000000001 00000000013c8e60 
> GPR20: 00000000013c8fa8 00000000013c8d90 c0000000027b2160 0000000000000000 
> GPR24: 0000000000000005 c0000000027b3568 c000000000e06718 0000000000002900 
> GPR28: 0000000000002900 0000000007fff33f 0000000000000000 c000000002773bc8 
> NIP [c00000000047e9bc] kmem_cache_alloc+0x5c/0x610
> LR [c000000000e06718] mas_alloc_nodes+0xe8/0x350
> Call Trace:
> [c000000002773a10] [0040000000000000] 0x40000000000000 (unreliable)
> [c000000002773a70] [c000000000e06718] mas_alloc_nodes+0xe8/0x350
> [c000000002773ad0] [c000000000e0f7f4] mas_expected_entries+0x94/0x110
> [c000000002773b10] [c00000000012cc44] dup_mmap+0x194/0x730
> [c000000002773c80] [c00000000012d260] dup_mm+0x80/0x180
> [c000000002773cc0] [c00000000008e7c0] text_area_cpu_up_mm+0x20/0x1a0
> [c000000002773d20] [c00000000013367c] cpuhp_invoke_callback+0x15c/0x810
> [c000000002773db0] [c0000000001348dc] cpuhp_issue_call+0x28c/0x2a0
> [c000000002773e00] [c000000000134e44] __cpuhp_setup_state_cpuslocked+0x154/0x3e0
> [c000000002773eb0] [c000000000135180] __cpuhp_setup_state+0xb0/0x1d0
> [c000000002773f10] [c000000002016f9c] poking_init+0x40/0x9c
> [c000000002773f30] [c00000000200434c] start_kernel+0x598/0x914
> [c000000002773fe0] [c00000000000d990] start_here_common+0x1c/0x20
> Code: fb81ffe0 7c9b2378 3b293968 fbc1fff0 f8010010 7c7e1b78 fba1ffe8 fbe1fff8 91610008 f821ffa1 f8410018 83b90000 <83e3001c> 7fbd2038 7bbc0020 7f84e378 
> ---[ end trace 0000000000000000 ]---
>
> Kernel panic - not syncing: Attempted to kill the idle task!
>
> Reverting commits
>
>   55a02e6ea958 ("powerpc/code-patching: Use temporary mm for Radix MMU")

Looks like this is related to the conflict you got merging tip.

If I switch the powerpc code to use mm_alloc() then I don't see the
above crash.

I needed to rebase anyway so I've squashed that change in for Monday.

cheers

      reply	other threads:[~2022-12-02  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  3:31 linux-next: boot failure after merge of the powerpc tree Stephen Rothwell
2022-12-02  9:36 ` Michael Ellerman [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=87o7sm171v.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=bgray@linux.ibm.com \
    --cc=cmr@bluescreens.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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