From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 19:41:05 2005 Return-Path: X-Original-To: freebsd-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 513DA16A41F for ; Tue, 29 Nov 2005 19:41:05 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9690343D95 for ; Tue, 29 Nov 2005 19:40:53 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 29 Nov 2005 19:40:43 -0000 Received: from h081217094006.dyn.cm.kabsi.at (EHLO h081217094006.dyn.cm.kabsi.at) [81.217.94.6] by mail.gmx.net (mp019) with SMTP; 29 Nov 2005 20:40:43 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Maksim Yevmenkin In-Reply-To: <438C9FCF.7080405@savvis.net> References: <438C9FCF.7080405@savvis.net> Content-Type: text/plain Date: Tue, 29 Nov 2005 20:40:06 +0100 Message-Id: <1133293206.1392.6.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org 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 19:41:05 -0000 On Tue, 2005-11-29 at 10:37 -0800, 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. > > 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. I've seen the problem with the ro-only / fs too. I can't get it to mount rw manually either - only rebooting helps. I remember seeing some changes to mount some days ago, I guess they cause this. CVS log says: Remove UFS-specific parts from mount(8). For mounting UFS, all mount options are passed directly to nmount(), without any UFS-specific logic.