From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 20:58:23 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01CF816A434 for ; Tue, 29 Nov 2005 20:58:22 +0000 (GMT) (envelope-from pete@altadena.net) Received: from gooney.altadena.net (gooney.altadena.net [207.215.170.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC50D43E5E for ; Tue, 29 Nov 2005 20:56:05 +0000 (GMT) (envelope-from pete@altadena.net) Received: from nat-gw.home.altadena.net ([66.127.158.99] helo=[192.168.169.28]) by gooney.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1EhCVE-000B1C-78 for current@freebsd.org; Tue, 29 Nov 2005 12:55:04 -0800 Message-ID: <438CC026.9080908@altadena.net> Date: Tue, 29 Nov 2005 12:55:02 -0800 From: Pete Carah Organization: Altadena Internet Communications User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <438C9FCF.7080405@savvis.net> In-Reply-To: <438C9FCF.7080405@savvis.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: problems with -current 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: Tue, 29 Nov 2005 20:58:23 -0000 Maksim Yevmenkin wrote: > dear hackers, > > after cvsup'ing recent current (as of yesterday evening pst) and > building/installing new kernel/world i started having problems: > > problem 1: startx simply reboots my laptop. i can see x coming up, then > after just a few seconds my laptop reboots. no window manager, no > nothing. my laptop is a dell with some radeon video card. will provide > more details on request. On mine (I865 integrated controller) the system hangs on startx; I did see one panic but couldn't tell what it was since system booted directly from graphics mode. > > problem 2: when system is booted and filesystem is not clean fsck is > started and checks all dirty filesystems. then boot process continues as > usual, however root filesystem is still mounted read-only, i.e. > > ---> /dev/ad0s1a on / (ufs, local, read-only) <--- > devfs on /dev (devfs, local) > /dev/ad0s1d on /tmp (ufs, local, soft-updates) > /dev/ad0s1f on /usr (ufs, local, soft-updates) > /dev/ad0s1e on /var (ufs, local, soft-updates) > linprocfs on /usr/compat/linux/proc (linprocfs, local) > devfs on /var/named/dev (devfs, local) The RW update happens right if there was no fsck, but fails if there was one. This goes back to the pre-mid-1990's thing about doing an immediate reboot after any fsck... In addition, there was an API change that didn't make it into UPDATING: if mount(8) and friends (mount_*) are recompiled and tried with an old kernel, NOTHING related to mount options seems to work; the interface for options changed. (this has happened slowly; mount_msdos picked up the change last week sometime but ufs only recently). Made things so that I couldn't use noauto since it got presented to the driver which rejected the mount. Not serious for usb drives since all it does with msdosfs is not mount anyhow, and not hang the boot or drop into single-user. BUT this kind of change is supposed to go into UPDATING *BEFORE COMMIT*, since it requires sync between userland and kernel. Not to speak of apparently not being finished!!!! > > so, anyone sees this as well or its just me. Yes. -- Pete