netdev - Re: next-20250129: rk3399-rock-pi-4b NFS mount and boot failed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8548ba31-762a-4ccb-b832-3365c9d5caf4@lunn.ch>
Date: Fri, 31 Jan 2025 15:20:02 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
	Linux Regressions <regressions@...ts.linux.dev>,
	Netdev <netdev@...r.kernel.org>,
	Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>,
	Yanteng Si <si.yanteng@...ux.dev>, Paolo Abeni <pabeni@...hat.com>,
	Arnd Bergmann <arnd@...db.de>,
	Dan Carpenter <dan.carpenter@...aro.org>,
	Theodore Grey <theodore.grey@...aro.org>,
	Anders Roxell <anders.roxell@...aro.org>,
	Steven Price <steven.price@....com>
Subject: Re: next-20250129: rk3399-rock-pi-4b NFS mount and boot failed

On Fri, Jan 31, 2025 at 04:07:24PM +0530, Naresh Kamboju wrote:
> The arm64 rk3399-rock-pi-4b boot failed on Linux next-20250129
> while mounting rootfs via NFS. Whereas other arm64 devices boot fine.
> 
> rk3399-rock-pi-4b:
>   boot:
>     * gcc-13-lkftconfig
> 
> First seen on the the Linux next-20250129..next-20250130
> Good: next-20250128
> Bad: next-20250129
> 
> Theodore Grey bisected this to,
> first bad commit:
>   [8865d22656b442b8d0fb019e6acb2292b99a9c3c]
>   net: stmmac: Specify hardware capability value when FIFO size isn't specified
> 
> Anyone have noticed this boot problem on rk3399-rock-pi-4b running the
> Linux next-20250129 and next-20250130 kernel.

Thanks for the report. Steven Price <steven.price@....com> also
noticed it, and there is a thread started about this issue.

	Andrew