Date: Wed, 28 Jul 2010 09:32:00 -1000 From: David Cornejo <dave@dogwood.com> To: mdf@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: Panic booting vmware i386 after SRAT update Message-ID: <AANLkTimUm34D=LMO9v2vBr1WKJpDf95i4KhZXnxQN5_O@mail.gmail.com> In-Reply-To: <AANLkTi=0Z9_NNN%2BmByHfDk-g%2Br2vR1nQNW20_wu8_gAA@mail.gmail.com> References: <AANLkTimZj4ocqiiUzXJhwkY6nRj_sGJ2h%2BQAQKvC9wWi@mail.gmail.com> <AANLkTi=0Z9_NNN%2BmByHfDk-g%2Br2vR1nQNW20_wu8_gAA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 28, 2010 at 8:23 AM, <mdf@freebsd.org> wrote: > On Wed, Jul 28, 2010 at 10:37 AM, <mdf@freebsd.org> 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. > > 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="1" in /boot/device.hints works around the > issue. > > Thanks, > matthew > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > GENERIC amd64 kernel with the hint dies earlier: WARNING: WITNESS option enabled, expect reduced performance panic: witness_init: pending locks list is too small, bump it cpuid = 0 KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at kdb_enter+0x3d: movq $0,0x6d6fb0(%rip) db>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimUm34D=LMO9v2vBr1WKJpDf95i4KhZXnxQN5_O>