Project

General

Profile

Actions
Copy link

Bug #596

open

Allocate resources from top down AND extend PCIe resource window above 4G together breaks libgfxinit bootscreen

Added by Walter Sonius about 2 months ago. Updated 10 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
none
Start date:
05/19/2025
Due date:
% Done:

0%

Estimated time:
Affected versions:
25.03
Needs backport to:
Affected hardware:
Affected OS:

Description

When enabling both Allocate resources from top down enabled by default and fixed recently and Extend resource window for PCIe devices above 4G libgfxinit will break during bootscreen and other PCIe issues like failing wifi drivers may occur.

Tested coreboot-25.03-519-ga2010cf5eeea (a2010cf5eeea6ad4a154cfb13760092f0865af3f) with Dell_Optiplex_5040_sff (i3-6100) and earlier Coreboot 25.03-467-gf0ad05b57ebe with Lenovo x201 with MrChromeBox EDK2 2502.

Can/should these 2 options be used together, if I understand correctly when using a modern efi GOP dGPU together with resizeable-bar all 3 options(+Support PCIe Resizable BARs) need to be enabled?

Only using Allocate resources from top down or Extend resource window for PCIe devices above 4G does not lead up to this issue.

Files

Download all files
cb-log-dell-5040-sff-notd-a4b-ok-bootscreen.txt (41 KB) cb-log-dell-5040-sff-notd-a4b-ok-bootscreen.txt Walter Sonius, 05/19/2025 03:12 PM
cb-log-dell-5040-sff-td-noa4b-ok-bootscreen.txt (41 KB) cb-log-dell-5040-sff-td-noa4b-ok-bootscreen.txt Walter Sonius, 05/19/2025 03:12 PM
cb-log-dell-5040-sff-td-a4b-no-bootscreen.txt (40.5 KB) cb-log-dell-5040-sff-td-a4b-no-bootscreen.txt Walter Sonius, 05/19/2025 03:12 PM
Actions
Copy link
 #1

Updated by Paul Menzel about 2 months ago

Thank you for reporting the issue. For the attachment naming, I assume td refers to top down, and a4b for above 4G?

Unfortunately, in the failure case, the log is not helpful for my ignorant eyes:

[DEBUG]  PCI: 00:00:02.0 init
[INFO ]  CBFS: Found 'vbt.bin' @0xcf780 size 0x48e in mcache @0x7abdd1e4
[INFO ]  Found a VBT of 6144 bytes
[INFO ]  GMA: Found VBT in CBFS
[INFO ]  GMA: Found valid VBT in CBFS
[DEBUG]  PCI: 00:00:02.0 init finished in 40 msecs

Could you enable libgfxinit debug logs? Maybe that shows something.

Actions
Copy link
 #2

Updated by Walter Sonius 10 days ago

Your are correct about the abbreviations.

Is there a specific libgfxinit debug log option, since the debug options in "make menuconfig" didn't reveal any libgfxinit related output in the log.

Could you hint which conf/makefile I should edit to force it during the next build, or is there something like cbmemtool after boot to dig into libgfxinit issues during boot/post?

Actions
Copy link

Also available in: Atom PDF