From owner-freebsd-current Mon Jan 7 6:27:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from router.hackerheaven.org (qn-213-73-194-22.quicknet.nl [213.73.194.22]) by hub.freebsd.org (Postfix) with ESMTP id A86D837B405; Mon, 7 Jan 2002 06:27:35 -0800 (PST) Received: by router.hackerheaven.org (Postfix, from userid 1000) id B1F9D1C1C; Mon, 7 Jan 2002 15:27:04 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by router.hackerheaven.org (Postfix) with ESMTP id 6521773DA; Mon, 7 Jan 2002 15:27:04 +0100 (CET) Date: Mon, 7 Jan 2002 15:27:03 +0100 (CET) From: Emiel Kollof X-X-Sender: coolvibe@azazel.ipv6.hackerheaven.org To: John Baldwin Cc: current@FreeBSD.org, Makoto Matsushita Subject: Re: kernel compile fails... In-Reply-To: Message-ID: <20020107151854.B56259-100000@azazel.ipv6.hackerheaven.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 On Mon, 7 Jan 2002, John Baldwin wrote: > You must have cvsup'd at a bad time. I removed SWI_NOSWITCH from cam and > everywhere else in one big commit Friday or Saturday. I have other problems with the cvsup upgrade from STABLE to CURRENT on my machine. One of em is that my machine won't go past the fsck -p step and consitently claims that my superblock is borked, tries fo fix it and then resets my ATA controller after which it deadlocks. I have boot up into single user and do a fsck -y and then type 'exit' to get my box up. Will a fresh cvsup and building a new world/kernel solve these annoying niggles? I don't have any fs corruption (well, at least I'm not noticing any, my box works fine) and some apps suddenly segfault suddenly on me as well (like mutt, which seems to have problems with the __ftello() call (I sent a PR about that, oh, and mutt is the latest version from ports). But otherwise all is fine. :-) Cheers, Emiel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message