Well my system have only 4.10-637 coreboot version, so I don't know if it is relevant.
My Kontron 986LCD-M (supported by coreboot) does the SMP without a problem. Kernel 4.20.0-rc2 (I didn't see any problem with current slackware kernel too). GPU is radeon RX460, kernel parameters "amdgpu.ppfeaturemask=0xfffffffb amdgpu.dc=1 earlyprintk=serial,ttyS0,115200,keep pci=assign-busses,pcie_scan_all,realloc raid=noautodetect acpi_enforce_resources =lax video=1440x900MR fbcon=map:0 memory_corruption_check=0 resume=/dev/sda1 resume_offset=260096" (but there are most likely some redundant ones - accumulated from testing). Suspend to HDD doesn't work (I think).
I've had to modify coreboot's devicetree as some superio devices requires to be defined even if not used (otherwise the resource allocator goes mad).
Dne 17. 01. 20 v 13:58 Paul Menzel napsal(a):
Dear coreboot folks,
On 2019-12-15 11:54, Paul Menzel wrote:
On the Lenovo T60 (with AMD/ATI graphics) the Linux kernel (4.9, 4.19, 5.3, 5.4) hangs after starting user space. As SeaBIOS, GRUB, payloads and FreeDOS work, I tried to limit the number of CPUs, and booting Linux with `nosmp` gave me a booting system. It worked with older coreboot versions, so I think it’s a regression. I am able to reproduce this with coreboot 4.11 and 4.11-422-g1a5c3bb7fa.
Is somebody else seeing this issue? Maybe on some i945 desktop board, so it would be easier to bisect?
Just as an update, here is the description.
nosmp [SMP] Tells an SMP kernel to act as a UP kernel, and disable the IO APIC. legacy for "maxcpus=0".
So, after seeing some IRC discussion in #email@example.com, the tests below were done.
System *boots* with one of:
- maxcpus=0 (equivalent nosmp)
- nolapic (with e1000 warning about missing MSI-X
System does *not* boot with one of:
But first, it’d be great if other i945 device users could confirm this.
coreboot mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com