Date: Wed, 28 Jul 2010 11:50:04 -0700 From: mdf@FreeBSD.org To: David Cornejo <dave@dogwood.com> Cc: freebsd-current@freebsd.org Subject: Re: Panic booting vmware i386 after SRAT update Message-ID: <AANLkTim0xvzZfqEm2dYPSCK3w8-pyTjWQZ77s9=-NmfC@mail.gmail.com> In-Reply-To: <AANLkTik_hL7ka9_94oGJLAxkQAzWRWppvTP=%2BseEQHLD@mail.gmail.com> References: <AANLkTimZj4ocqiiUzXJhwkY6nRj_sGJ2h%2BQAQKvC9wWi@mail.gmail.com> <AANLkTik_hL7ka9_94oGJLAxkQAzWRWppvTP=%2BseEQHLD@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 28, 2010 at 11:19 AM, David Cornejo <dave@dogwood.com> wrote: > On Wed, Jul 28, 2010 at 7: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. > > 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=3D"1" in /boot/device.hints fixes the issue for me. Thanks, matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim0xvzZfqEm2dYPSCK3w8-pyTjWQZ77s9=-NmfC>