From owner-freebsd-current@FreeBSD.ORG Wed Nov 30 00:02:54 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 8FBD716A41F for ; Wed, 30 Nov 2005 00:02:54 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FFF143D5D for ; Wed, 30 Nov 2005 00:02:34 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2836083 for multiple; Tue, 29 Nov 2005 19:01:55 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAU02O0p075876; Tue, 29 Nov 2005 19:02:24 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 29 Nov 2005 19:01:30 -0500 User-Agent: KMail/1.8.3 References: <438C9FCF.7080405@savvis.net> <200511291804.11041.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200511291901.31545.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Mark Atkinson 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: Wed, 30 Nov 2005 00:02:55 -0000 On Tuesday 29 November 2005 06:44 pm, Mark Atkinson wrote: > John Baldwin wrote: > > On Tuesday 29 November 2005 05:51 pm, Mark Atkinson wrote: > >>John Baldwin wrote: > >>>On Tuesday 29 November 2005 05:04 pm, Mark Atkinson wrote: > >>>>Rainer Alves wrote: > >>>>>On 11/29/05, 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 continu= es > >>>>>>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) > >>>>>> > >>>>>>so, anyone sees this as well or its just me. > >>>>>> > >>>>>>thanks, > >>>>>>max > >>>>> > >>>>>Same thing here.. it's probably related to the huge DRM changes > >>>>>commited yesterday by anholt@. > >>>>>I'll try to enable some debugging stuff and see what's going on... > >>>> > >>>>I just cvsup'd to 2005.11.28.23.00.00, rebuilt and reinstalled, which > >>>>should be just before the commit: > >>>> > >>>>anholt 2005-11-28 23:13:57 UTC > >>>> > >>>>and starting X still reboots my machine. I'm reverting the kernel now > >>>>to 8am UTC from the 28th, and if that still fails I'm going back about > >>>> 7 to 10 days. > >>> > >>>Hook up a serial console so you can see the panic message. Make sure > >>>kdb/ddb, etc. are in your kernel so you can get a trace. > >> > >>the box is out and out resetting. I already have ddb, etc.. (which is > >>why I noticed the LOR on so_snd earlier with the same kernel. Will > >>setting up comconsole on this box really give me a panic and not reset > >>with X running? > > > > Yes. When X is running, we don't drop into the debugger, it just > > reboots. > > Very good to know! I'm curious why we don't dump to the dumpdev at this > point however? That's a bug. :) My guess is it comes from the KDB stuff and kdb_trap() i= s=20 probably bailing too early and not doing the dump if it can't get a console. > I just finished a kernel from Nov 28 0800 UTC and no reset with > comconsole. It is possible that my update to 23:00:00 caught part but > not all of a big commit finished at 23:13 UTC. > > Now trying with the old 23:00:00 kernel... [boots.. startx] Hehe. > Guess what? > > it's the uipc_socket panic. Hah, yes, X uses sockets, so it should hopefully be fixed now. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org