From owner-freebsd-current Thu Jun 10 14:56: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 22E391506D; Thu, 10 Jun 1999 14:56:01 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id RAA15728; Thu, 10 Jun 1999 17:56:01 -0400 (EDT) (envelope-from luoqi) Date: Thu, 10 Jun 1999 17:56:01 -0400 (EDT) From: Luoqi Chen Message-Id: <199906102156.RAA15728@lor.watermarkgroup.com> To: tich@ma.ikos.com Subject: Re: 4-way SMP broken ? Cc: freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have added more debugging messages, and the crash appears to be inside > mp_start(). I don't have a log because this is too early in the boot > to get the messages saved anywhere, and they go by too quickly to > write it down. The evidence that this is an SMP problem is simple - > with 2 cpu's plugged in, it works fine; with 3 or 4 cpu's plugged in, > it crashes. > Could you narrow down the crash further inside mp_start()? I'd like to know whether the crash occurred inside start_all_aps(). One or two lines of debug messages would be really helpful, you don't have to write down the exact words. Do you have options DDB enabled in the kernel? It helps to stop the last few lines of console messages to scroll of the screen. > I believe the hardware is fine because I was previously running > 19990421-CURRENT with all 4 cpu's without serious problems (it was > a little unstable, but always booted ok). > If possible, could you try a kernel built from sources with the POST_SMP_VMSHARE tag? I may have broken something during the commit. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message