From owner-freebsd-current@FreeBSD.ORG Wed Jul 28 18:50:05 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 8709F106567D; Wed, 28 Jul 2010 18:50:05 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 51F898FC19; Wed, 28 Jul 2010 18:50:05 +0000 (UTC) Received: by pzk7 with SMTP id 7so2334740pzk.13 for ; Wed, 28 Jul 2010 11:50:05 -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=Uw+SGoO+yzXxDE851g9KV3bwwqDMr5o4qh3ysng4TXo=; b=sscjeciTo/K2hVF1K+bL9LdIlb6o5a1gk+6zd05cymFymVGkrma10//KZKChHV/FYd nhYPSwv3yIo6q4A1Yn07qV4u9Un/y8LAiUBT3TxUVWo1iJSUBdqSAb0+wBPD0X0imGKl 3Pv6TAX/aazfSq+7GxVwlukyzO/UtGqdx6HQ8= 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=vPliut4Bx8hJXdxXmfbEmZyAocge8txHLdAb3Nfn30PXltNC3raHkmGL9IRR70R43r TV6Kaz410AIfge7O7A0fhojQTw7VdgSPHTgXweXAne6JzqSkomjdxOHhbph5+lwaarBb W26v1emGsCt2Na92GjkI1haRgDsWl0FNLoirA= MIME-Version: 1.0 Received: by 10.142.171.7 with SMTP id t7mr12266808wfe.212.1280343004977; Wed, 28 Jul 2010 11:50:04 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.42.6.85 with HTTP; Wed, 28 Jul 2010 11:50:04 -0700 (PDT) In-Reply-To: References: Date: Wed, 28 Jul 2010 11:50:04 -0700 X-Google-Sender-Auth: N2mmw0f1zMI6YMF9eo7WMFMIYkE Message-ID: From: mdf@FreeBSD.org To: David Cornejo 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:50:05 -0000 On Wed, Jul 28, 2010 at 11:19 AM, David Cornejo wrote: > On Wed, Jul 28, 2010 at 7: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. > > 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