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, 9 May 2023 22:30:44 +0100
From:   Conor Dooley <conor@kernel.org>
To:     Guenter Roeck <linux@roeck-us.net>
Cc:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        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 6.1 000/610] 6.1.28-rc2 review
Message-ID: <20230509-tacking-polo-d841ebfffcd0@spud>
References: <20230509030653.039732630@linuxfoundation.org>
 <0837e157-8615-418a-a3d3-1c14af11aba5@roeck-us.net>
 <20230509-robust-crate-5fe128d00e6d@spud>
 <ce667220-5803-4b6a-a2d2-f538289af584@roeck-us.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="XZAFXv1xCRIWO+qY"
Content-Disposition: inline
In-Reply-To: <ce667220-5803-4b6a-a2d2-f538289af584@roeck-us.net>
Precedence: bulk


--XZAFXv1xCRIWO+qY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 09, 2023 at 02:18:35PM -0700, Guenter Roeck wrote:
> On Tue, May 09, 2023 at 09:41:42PM +0100, Conor Dooley wrote:
> > On Tue, May 09, 2023 at 12:57:58PM -0700, Guenter Roeck wrote:
> > > On Tue, May 09, 2023 at 05:26:31AM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.28 release.
> > > > There are 610 patches in this series, all will be posted as a respo=
nse
> > > > to this one.  If anyone has any issues with these being applied, pl=
ease
> > > > let me know.
> > > >=20
> > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000.
> > > > Anything received after that time might be too late.
> > > >=20
> > >=20
> > > Build results:
> > > 	total: 155 pass: 155 fail: 0
> > > Qemu test results:
> > > 	total: 519 pass: 519 fail: 0
> > >=20
> > > New persistent runtime warning when booting riscv32/64 images:
> >=20
> > You sure this is new? I seem to be able to reproduce for QEMU (which I
>=20
> New for my tests, yes.
>=20
> > don't usually test) in several versions of 6.1. Don't see it in (my)
> > hardware though, as the particular platform doesn't end up calling the
> > offending function. Out of curiosity, what's your QEMU invocation?
>=20
> Example boot from initrd:
>=20
> qemu-system-riscv64 -M virt -m 512M \
>      -no-reboot -kernel arch/riscv/boot/Image \
>      -initrd rootfs.cpio \
>      -device e1000,netdev=3Dnet0 \
>      -netdev user,id=3Dnet0 -bios default \
>      -append "panic=3D-1 rdinit=3D/sbin/init console=3DttyS0,115200 early=
con=3Duart8250,mmio,0x10000000,115200" \
>      -nographic -monitor none

Cool, was mainly interested in seeing if you were explicitly enabling
any ISA extensions. NGL, I expected to see some.

> qemu version is 8.0, but I don't think that makes a difference.

I'm on 7.2.50 (v7.2.0-2653-g7080c3ab79-dirty) as it is where I ended
during my last bisection of QEMU. But aye, makes no odds - I see it on a
more recent 8.0.50 version too.

> What does your command line look like ?

In this particular instance:
	qemu-system-riscv64 -M virt \
		-m 2G -smp 5 \
		-nographic \
		-kernel $(vmlinux_bin) \
		-initrd $(initramfs)

> > Anyways, looks like a partial backport is the cause. How's it look with:

> This fixes the problem for me.

Cool, shall send it as a real patch. Thanks.

--XZAFXv1xCRIWO+qY
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZFq7gwAKCRB4tDGHoIJi
0pWvAQDpsknEvAm568mJ3lmPfIERipnx+EYNfwlScWRVYAPZTgD/UnSqcJTWGhHz
An66ZI9Yfv3VaPqoUvYIezKns6Xa/w0=
=LNau
-----END PGP SIGNATURE-----

--XZAFXv1xCRIWO+qY--