#16055 closed bug (fixed)
Only one CPU core is detected
Reported by: | MatejHorvat | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta3 |
Component: | System/Boot Loader/BIOS | Version: | R1/Development |
Keywords: | Cc: | tqh | |
Blocked By: | Blocking: | ||
Platform: | All |
Attachments (1)
Change History (12)
by , 4 years ago
comment:2 by , 4 years ago
If it helps, this is what FreeBSD's dmesg says:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) Firmware Warning (ACPI): Incorrect checksum in table [XSDT] - 0x89, should be 0xFD (20171214/tbprint-337) Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20171214/tbfadt-796) ioapic0: Changing APIC ID to 0 ioapic0 <Version 2.1> irqs 0-23 on motherboard SMP: AP CPU #1 Launched! <...> cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0
comment:3 by , 4 years ago
Cc: | added |
---|
So, FreeBSD also says the checksum is invalid, but continues anyway. I'm not sure that's very wise...
tqh, what do you think we should do here?
comment:4 by , 4 years ago
We don't use ACPICA for that I think. It is some early Haiku specific kernel code, so I think someone that knows about the multiprocessor config needs to take a look. Or we'd need to use ACPICA early in boot process instead.
comment:7 by , 4 years ago
Use of ACPI tables to init hardware is parts where others know better. Not sure what the implications of ignoring a broken checksum would be. I probably would fail, but add a boot flag to circumvent failing.
comment:9 by , 4 years ago
Both cores are detected now. If this is a satisfactory solution, then this ticket can be closed.
comment:10 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:11 by , 4 years ago
Milestone: | Unscheduled → R1/beta3 |
---|