mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <>
To: Ahmad Fatoum <>,
	Barebox List <>
Subject: Re: [v2022.10.0] initcall of of_probe_memory failed (EBUSY)
Date: Mon, 17 Oct 2022 14:10:16 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 17/10/2022 13:24, Ahmad Fatoum wrote:
> On 17.10.22 14:03, Ian Abbott wrote:
>> Barebox v2022.10.0 seems to work for me, but I now get this (harmless?) error during initialization:
>> initcall of_probe_memory+0x1/0x34 failed: Device or resource busy
>> (This is on a 32-bit ARM SoCFPGA/CycloneV based system.)
>> git bisect is blaming commit d0b5f6bde15b ("of: reserved-mem: reserve regions prior to mmu_initcall()").
> Can you define #define DEBUG at the top of common/resource.c and paste
> the output?

Here is what I get for a Terasic DE0-Nano-SoC.  (I was using a custom 
board for the original report, but the symptoms are the same.)

lowlevel init done
SDRAM setup...
SDRAM calibration...

barebox 2022.10.0-dirty #31 Mon Oct 17 13:58:34 BST 2022

Board: Terasic DE-0(Atlas)
__request_region ok: 0x00000000:0x3fffffff flags=0x0
__request_region ok: 0xffd04000:0xffd04fff flags=0x0
__request_region ok: 0xffd05000:0xffd05fff flags=0x0
__request_region ok: 0xffc02000:0xffc02fff flags=0x0
__request_region ok: 0xffc03000:0xffc03fff flags=0x0
__request_region: 0x00000000:0x3fffffff (ram0) conflicts with 
0x00000000:0x3fffffff (ram0)
initcall of_probe_memory+0x1/0x34 failed: Device or resource busy
__request_region ok: 0x00000000:0x00000fff flags=0x80000200
__request_region ok: 0x3ffe4000:0x3ffe7fff flags=0x200
__request_region: 0x00000000:0x00000fff (zero page) conflicts with 
0x00000000:0x00000fff (fdt-memreserve-0)
__request_region ok: 0x1fefd960:0x3fdfb2bf flags=0x200
__request_region ok: 0x3fe00000:0x3fe71e0b flags=0x200
__request_region ok: 0x3fe71e0c:0x3fe8272f flags=0x200
__request_region ok: 0x3fe82730:0x3fe85d1f flags=0x200
__request_region ok: 0xffc04000:0xffc04fff flags=0x0
__request_region ok: 0xfffec600:0xfffec6ff flags=0x0
__request_region ok: 0x3ffe8000:0x3ffeffff flags=0x200
__request_region ok: 0xff702000:0xff703fff flags=0x0
socfpga_designware_eth ff702000.ethernet@ff702000.of: user ID: 0x10, 
Synopsys ID: 0x37
mdio_bus: miibus0: probed
__request_region ok: 0xff704000:0xff704fff flags=0x0
dw_mmc ff704000.dwmmc0@ff704000.of: registered as mmc0
__request_region ok: 0xffd02000:0xffd02fff flags=0x0
__request_region ok: 0xff706000:0xff706fff flags=0x0
__request_region ok: 0xffb90000:0xffb90003 flags=0x0
__request_region ok: 0x3fdfb2c0:0x3fdfffc9 flags=0x200
malloc space: 0x1fefd960 -> 0x3fdfb2bf (size 511 MiB)
mmc0: detected SD card version 2.0
mmc0: registered mmc0

Hit any to stop autoboot:    3

-=( Ian Abbott <> || MEV Ltd. is a company  )=-
-=( registered in England & Wales.  Regd. number: 02862268.  )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || )=-

  reply	other threads:[~2022-10-17 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 12:03 Ian Abbott
2022-10-17 12:24 ` Ahmad Fatoum
2022-10-17 13:10   ` Ian Abbott [this message]
2022-10-17 13:31     ` Ian Abbott
2022-10-17 13:41     ` Ahmad Fatoum
2022-10-17 14:32       ` Ian Abbott
2022-10-17 14:45         ` Ahmad Fatoum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox