Received-SPF: pass (google.com: domain of linux-kernel+bounces-88384-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Fri, 1 Mar 2024 12:07:56 +0000
From: Mark Brown <broonie@kernel.org>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [broonie-ci:regmap-test-format] [regmap]  af560701e3:
 RIP:__regmap_init
Message-ID: <53c9f248-84d3-4b85-bf25-59055db7eb54@sirena.org.uk>
References: <202402292329.a1c8a83f-lkp@intel.com>
 <2d5fdeda-868d-457f-b462-8d5552a7fe1b@sirena.org.uk>
 <ZeExUW2XjKjuzd5p@xsang-OptiPlex-9020>
 <ZeFLxcfz5PvHutU/@xsang-OptiPlex-9020>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="feeHdGAruMinPZx+"
Content-Disposition: inline
In-Reply-To: <ZeFLxcfz5PvHutU/@xsang-OptiPlex-9020>


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

On Fri, Mar 01, 2024 at 11:30:13AM +0800, Oliver Sang wrote:
> On Fri, Mar 01, 2024 at 09:37:21AM +0800, Oliver Sang wrote:
> > On Thu, Feb 29, 2024 at 03:47:33PM +0000, Mark Brown wrote:
> > > On Thu, Feb 29, 2024 at 11:43:55PM +0800, kernel test robot wrote:

> > and we noticed there is changes in __regmap_init(), we also noticed the=
 issue
> > seems happen before the test even starts to run. not sure if the detail=
 dmesg in

The patch adds a callback but nothing yet provides that callback, it is
very difficult to see how that might be an issue.

> > https://download.01.org/0day-ci/archive/20240229/202402292329.a1c8a83f-=
lkp@intel.com/dmesg.xz
> > could supply more information?

> > if you still think this is a wrong report, or you want us to test any p=
atch,
> > please just let us know. it's always our great pleasure. Thanks!

> we checked this issue more, and found it could be platform specific.
>=20
> we just try a simple boot with af560701e3 on below machine which we made =
origial
> report and reproduced the issue (dmesg is attached).
>=20
> test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz=
 (Kaby Lake) with 32G memory

My best guess would be that this has somehow managed to trigger a
preexisting issue which happens to manifest on whatever platform you're
running.  I can't from the backtrace alone tell where that might be,
there's not enough information about where regmap_init() is being called
=66rom.

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

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmXhxRwACgkQJNaLcl1U
h9CqJAf/fMk4J4sgDE26Fl4b7oT0hlhuY0YFTG2QQJ+wpiowxrzTQ2saQ/3ppXmr
jf43FRhc+TByyFm5qufb8BtAuH7zP8sQIdCxZQY2CkdgwfSUGOjH9m/8zIbMKhnH
cZhoS9HvvJFloGYKYnYfnCr4KeNLDf4iF7HE8YqQTn1741pNd7W0C3g8IBkDXtnq
nYjczD8hIROXntE8MPsSOo8gHGsHB1H+IAnrlVrgJj1+u6t8KKFsRH1MK3n+olkz
7CwZLzAxCe0hboDSv0uHkPMVX/1TZcc5wZ5NnH8NovO8Jqx3a2VFolCLzoTy3byY
bBQOf1l4yJ/biWbbMqA49Y91Yy2M0Q==
=A/0C
-----END PGP SIGNATURE-----

--feeHdGAruMinPZx+--