From owner-freebsd-current Fri Sep 1 21:21:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id E7A3D37B422 for ; Fri, 1 Sep 2000 21:21:27 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13V4vT-000065-00; Fri, 01 Sep 2000 22:29:07 -0600 Message-ID: <39B08213.7A34FCC4@softweyr.com> Date: Fri, 01 Sep 2000 22:29:07 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Hocking Cc: current@freebsd.org Subject: Re: Problems with sym device driver? References: <200008291433.e7TEXMV13326@bloop.craftncomp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking wrote: > > I just updated my sources after a few days and reconfiged, recompiled & booted > a machine with with a NCR810a card. It panicked partway through the boot > messages (prior to mounting filesystems) saying that it couldn't allocate > space for sym1's data. The previous kernel correctly found only one sym > device. The dmesg from the older working kernel is attached. I'm still seeing this with my -current cvsup'ed as of about 0800 GMT today. The problem goes away if I compile a non-SMP kernel, so it may be an SMP initialization problem. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message