11:00 <apalos> sjg1: commit 53fab13a7b11630ae seems to break qemuarm64 for me (in -next)

11:01 <apalos> Failed to write SMBIOS table

11:01 <apalos> initcall failed at event 10/(unknown) (err=-22)

11:01 <apalos> ### ERROR ### Please RESET the board ###

11:01 <apalos> This is what the blowup looks like if it helps

12:22 <sjg1> Oh dear...does it print this? WARNING: SMBIOS table_address overflow %llx

12:23 <sjg1> apalos: ^ It seems to pass CI

13:20 <apalos> sjg1: no it doesn't print that, only what I pasted

13:20 <apalos> Let me put that to a pastebin so you have the qemu cmdline as well

13:21 <apalos> sjg1: it does print the overflow btw, I just missed it

13:21 <apalos> WARNING: SMBIOS table_address overflow 13e69f020

13:21 <apalos> https://pastebin.com/2HySC2FF

13:37 <sjg1> apalos: So the table is being placed above 4GB...is that OK?

14:01 <apalos> sjg1: I dont know, it works fine without this commit, but i didnt find any time to dig deeper

14:05 <deathcamel57> Hey everyone, I'm stuck in my U-Boot porting project for an obscure Arm SoC. I'm using the OEM U-Boot to load my U-Boot build into RAM, then using `go` to start my build. When I set `CFG_SYS_INIT_RAM_ADDR` to a location in DRAM, it starts, but gets stuck on a memset in `reserve_board`. I think that config option should be set to the internal SoC's RAM, and when I use the starting address for that (according to OEM's

14:05 <deathcamel57> build), and according to the datasheet's info, it gets stuck even earlier in the boot. Any tips on where to look would be greatly appreciated.

15:23 <deathcamel57> Nevermind about my previous question, figured it out finally.

17:24 <sjg1> apalos: OK I will take a look

19:07 <apalos> sjg1: ok, let me know if anything can help, e.g qemu version etc,