From owner-freebsd-current Fri Mar 22 23:59: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id 5C77B37B417 for ; Fri, 22 Mar 2002 23:58:57 -0800 (PST) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id B4B9B62D1A for ; Fri, 22 Mar 2002 23:58:56 -0800 (PST) Date: Fri, 22 Mar 2002 23:59:34 -0800 (PST) From: Lamont Granquist To: Subject: Re: SMP ffs_mountfs() broken? In-Reply-To: <20020322230415.G123-100000@coredump.scriptkiddie.org> Message-ID: <20020322235230.U206-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG GENERIC works, so this looks like an SMP problem. Its happening right after the CPU initializes. This is probably the first SMP code the machine runs? Is hardware incompatibility a good guess? I would have expected that if someone broke ffs_mountfs() that someone else would have noticed by now... Oh, I forgot to say in my previous message that my motherboard is a Asus K7M266D. It runs 4.5-STABLE with SMP turned on fine, but only with MP spec 1.1 and not 1.4. There's a BIOS upgrade which is supposed to fix Linux + MP spec 1.4 issues which might fix 1.4 for FreeBSD as well. It could fix this as well maybe? On Fri, 22 Mar 2002, Lamont Granquist wrote: > I'll try to see if this was due to the cvsup or due to SMP. I've got a UP > kernel from a few weeks ago that works fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message