Date: Wed, 28 Jul 2010 11:23:11 -0700 From: mdf@FreeBSD.org To: mdf@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: Panic booting vmware i386 after SRAT update Message-ID: <AANLkTi=0Z9_NNN%2BmByHfDk-g%2Br2vR1nQNW20_wu8_gAA@mail.gmail.com> In-Reply-To: <AANLkTimZj4ocqiiUzXJhwkY6nRj_sGJ2h%2BQAQKvC9wWi@mail.gmail.com> References: <AANLkTimZj4ocqiiUzXJhwkY6nRj_sGJ2h%2BQAQKvC9wWi@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 28, 2010 at 10:37 AM, <mdf@freebsd.org> wrote: > I have a 2 cpu virtual image of FreeBSD current. =A0It 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 > > =A0cpu0 (BSP): APIC ID: =A00 > =A0cpu1 (AP): APIC ID: =A01 > 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. Okay, apparently VMWare is providing two entries of type ACPI_SRAT_TYPE_MEMORY_AFFINITY but no entries of type ACPI_SRAT_TYPE_CPU_AFFINITY. This leads to the assert since no CPUs are "enabled"; that is there's no affinity information for them. This is probably a VMWare bug. Setting hint.srat.0.disabled=3D"1" in /boot/device.hints works around the i= ssue. Thanks, matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=0Z9_NNN%2BmByHfDk-g%2Br2vR1nQNW20_wu8_gAA>