From mboxrd@z Thu Jan 1 00:00:00 1970 From: Conor Dooley Date: Wed, 19 Jul 2023 08:07:31 +0100 Subject: Boot failure after QEMU's upgrade to OpenSBI v1.3 (was Re: [PATCH for-8.2 6/7] target/riscv: add 'max' CPU type) In-Reply-To: References: <744cbde6-7ce5-c327-3c5a-3858e994cc39@ventanamicro.com> <20230712-superhero-rabid-578605f52927@spud> <5dd3366d-13ba-c7fb-554f-549d97e7d4f9@ventanamicro.com> <20230712-fancied-aviator-270f51166407@spud> <20230713-craziness-lankiness-8aec3db24993@spud> <20230714-reoccur-confined-4b37494b1201@spud> <20230714-hash-handwrite-339817b93ba1@spud> Message-ID: <20230719-dioxide-panic-cda48b1d8d1b@wendy> List-Id: To: opensbi@lists.infradead.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, Jul 19, 2023 at 11:32:55AM +1000, Alistair Francis wrote: > If there is no OpenSBI 1.3.1 release we should add something to the > release notes. @Conor Dooley are you able to give a clear sentence on > how the boot fails? Uhh, I'll give it a shot, but hopefully it is not required :) In version v1.3, OpenSBI's aclint drivers fail to initialise if they encounter a disabled CPU node in the devicetree. Attempting to boot using, for example, the Linux kernel's PolarFire SoC or Freedom U540 devicetrees, will fail with the error: "init_coldboot: ipi init failed (error -1009)" Please see OpenSBI commit c6a3573 ("lib: utils: Fix sbi_hartid_to_scratch() usage in ACLINT drivers") for the fix. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: not available URL: