Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 17 Jan 2023 11:16:56 +0100
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Guenter Roeck <linux@roeck-us.net>
Cc:     stable@vger.kernel.org, patches@lists.linux.dev,
        linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
        akpm@linux-foundation.org, shuah@kernel.org, patches@kernelci.org,
        lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com,
        f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
        srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.4 000/658] 5.4.229-rc1 review
Message-ID: <Y8Z1mBZCwQuv/clZ@kroah.com>
References: <20230116154909.645460653@linuxfoundation.org>
 <20230116202025.GA3397667@roeck-us.net>
 <Y8Zt42qAQ2BQdxL2@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Y8Zt42qAQ2BQdxL2@kroah.com>
Precedence: bulk

On Tue, Jan 17, 2023 at 10:44:03AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 16, 2023 at 12:20:25PM -0800, Guenter Roeck wrote:
> > Runtime:
> > 
> > Building ppc64:pseries:pseries_defconfig:smp2:net,pcnet:initrd ... running ......R... failed (crashed)
> > 
> > BUG: Kernel NULL pointer dereference at 0x00000000
> > Faulting instruction address: 0xc000000000046cc8
> > Oops: Kernel access of bad area, sig: 11 [#1]
> > BE SMP NR_CPUS=2048 NUMA pSeries
> > Modules linked in:
> > CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.19.270-rc1-00522-gc75d2b5524ab #1
> > NIP:  c000000000046cc8 LR: c000000000046ca4 CTR: 0000000000000000
> > REGS: c00000003e6878f0 TRAP: 0380   Not tainted  (4.19.270-rc1-00522-gc75d2b5524ab)
> > MSR:  8000000002009032 <SF,VEC,EE,ME,IR,DR,RI>  CR: 84000882  XER: 00000000
> > CFAR: c000000000162cf8 IRQMASK: 0
> > GPR00: c000000000046ca4 c00000003e687b70 c000000001772000 0000000000000000
> > GPR04: 0000000000000001 0000000000000001 c00000003e687990 00000000bc24d52c
> > GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000003
> > GPR12: 0000000024000882 c00000003ffff300 c000000000010e34 0000000000000000
> > GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > GPR20: 0000000000000000 0000000000000000 c00000000125eea8 0000000000000001
> > GPR24: c000000001379cd8 c000000001419f20 c0000000017b7d68 c0000000017b7d68
> > GPR28: 0000000000000000 0000000000000002 c00000000160efe8 c00000000168ac60
> > NIP [c000000000046cc8] .eeh_init+0x48/0x220
> > LR [c000000000046ca4] .eeh_init+0x24/0x220
> > Call Trace:
> > [c00000003e687b70] [c000000000046ca4] .eeh_init+0x24/0x220 (unreliable)
> > [c00000003e687c00] [c00000000001065c] .do_one_initcall+0x7c/0x430
> > [c00000003e687ce0] [c000000001394db4] .kernel_init_freeable+0x538/0x62c
> > [c00000003e687dc0] [c000000000010e4c] .kernel_init+0x18/0x14c
> > [c00000003e687e30] [c00000000000c0d0] .ret_from_kernel_thread+0x58/0x68
> > Instruction dump:
> > 3c62ffd7 38631c10 4811c021 60000000 2c030000 408201c8 3d22000b e92904e0
> > 2c290000 41820198 f8410028 e9290008 <e9490000> 7d4903a6 e8490008 4e800421
> > ---[ end trace 8912d02d3e80c4ae ]---
> 
> This is odd, and I don't know how to track that down.  Any hints?

Let me pull out some powerpc patches that are in this area and push out
a -rc2 to see if that resolves the issue.

thanks,

greg k-h