Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Nov 2005 18:04:10 -0500
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-current@freebsd.org
Cc:        Mark Atkinson <atkin901@yahoo.com>
Subject:   Re: problems with -current
Message-ID:  <200511291804.11041.jhb@freebsd.org>
In-Reply-To: <dmim0r$acn$1@sea.gmane.org>
References:  <438C9FCF.7080405@savvis.net> <200511291741.27945.jhb@freebsd.org> <dmim0r$acn$1@sea.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <maksim.yevmenkin@savvis.net> 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.
> >>>>
> >>>>--->  /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.

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511291804.11041.jhb>