Panic booting vmware i386 after SRAT update

mdf at mdf at
Wed Jul 28 18:50:05 UTC 2010

On Wed, Jul 28, 2010 at 11:19 AM, David Cornejo <dave at> wrote:
> On Wed, Jul 28, 2010 at 7:37 AM, <mdf at> wrote:
>> I have a 2 cpu virtual image of FreeBSD current.  It panics during
>> boot after building in the NUMA support.
>> I'll transcribe the SRAT bootverbose messages and panic message as best I
>> can.
>> Table 'SRAT' at 0xfef07f6
>> SRAT: Found table at 0xfef07f6
>> SRAT: Found memory domain 0 addr 0 len a0000: enabled
>> SRAT: Found memory domain 0 addr 100000 len ff00000: enabled
>> then some MADT: messages about finding cpu 0 and 1
>>  cpu0 (BSP): APIC ID:  0
>>  cpu1 (AP): APIC ID:  1
>> panic: SRAT: CPU with APIC ID 0 is not known
>> I'm playing around now with trying to figure out what went missing,
>> but I thought I'd send this out now.
> I have been seeing this since yesterday with amd64 custom kernels - just
> compiled a GENERIC kernel a few minutes ago and it shows the same symptom.

Is this on VMWare or physical hardware?  I isolated my issue to VMWare
reporting memory domains properties but not CPU affinity.  Setting
hint.srat.0.disabled="1" in /boot/device.hints fixes the issue for me.


More information about the freebsd-current mailing list