From owner-freebsd-current@FreeBSD.ORG Wed Jul 28 18:23:11 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD6C51065673; Wed, 28 Jul 2010 18:23:11 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 82DD48FC1C; Wed, 28 Jul 2010 18:23:11 +0000 (UTC) Received: by pxi8 with SMTP id 8so1249083pxi.13 for ; Wed, 28 Jul 2010 11:23:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=ZJU3PpswPXROsIazZkwxsaDp8c/TEjvj4oZjHMCjKBo=; b=stL5HjW+gHwnEuDM50KBIhB3TixtBK1u+juCzDc39JieSWRuXweqlwzBRyJFZo9ir6 mdV8eRgc3H4mlOJJHwD7Vc7OaSWKr5KpDPOpaSekh0pPJsgXfkSZFHCAW9X6CHzQgwyL 5wdJppTlr3akOUiT9mRgfZBkQkBExIqf2vJaM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=g3pfSWCREyUQG2uVAKI1b/DX2oa+Js56Av1dEp+bXbSpe31eETVp1p1tVgsf9tYQ7D zi4x0Gtd8k1vRYdzZ6fPjYMgksrhUo+78LzbZInmK183LE2GkgaklTvpFPAaoOQbyC3S GWVoL2pRG7xSkB3Q/aD3stI7+zmEt87hyZaCw= MIME-Version: 1.0 Received: by 10.143.155.12 with SMTP id h12mr991268wfo.333.1280341391091; Wed, 28 Jul 2010 11:23:11 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.42.6.85 with HTTP; Wed, 28 Jul 2010 11:23:11 -0700 (PDT) In-Reply-To: References: Date: Wed, 28 Jul 2010 11:23:11 -0700 X-Google-Sender-Auth: VP5wNNFTfKAu3GGKiinJCKmYptQ Message-ID: From: mdf@FreeBSD.org To: mdf@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: Panic booting vmware i386 after SRAT update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2010 18:23:11 -0000 On Wed, Jul 28, 2010 at 10:37 AM, 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