From owner-freebsd-current@FreeBSD.ORG  Mon Nov 15 22:19:24 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1233)
	id 76A821065675; Mon, 15 Nov 2010 22:19:24 +0000 (UTC)
Date: Mon, 15 Nov 2010 22:19:24 +0000
From: Alexander Best <arundel@freebsd.org>
To: Julian Elischer <julian@freebsd.org>
Message-ID: <20101115221924.GA38676@freebsd.org>
References: <20101113112447.GF2392@deviant.kiev.zoral.com.ua>
	<20101113115900.GA14975@freebsd.org>
	<20101113122853.GG2392@deviant.kiev.zoral.com.ua>
	<20101113123846.GA21390@freebsd.org>
	<20101113124146.GH2392@deviant.kiev.zoral.com.ua>
	<20101113124758.GA23469@freebsd.org>
	<alpine.BSF.2.00.1011132206380.12353@fledge.watson.org>
	<AANLkTim7ZGLFTj_3WZiC9hAsAaOVrz6yhKcMURV+sKvu@mail.gmail.com>
	<alpine.BSF.2.00.1011132212400.12353@fledge.watson.org>
	<4CDF0F03.10703@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4CDF0F03.10703@freebsd.org>
Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org,
	Robert Watson <rwatson@freebsd.org>, Garrett Cooper <gcooper@freebsd.org>
Subject: Re: www/chromium crashing whole system
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Nov 2010 22:19:24 -0000

On Sat Nov 13 10, Julian Elischer wrote:
> On 11/13/10 2:13 PM, Robert Watson wrote:
> >
> >On Sat, 13 Nov 2010, Garrett Cooper wrote:
> >
> >>   Isn't there also DEADLKRES that might be helpful in this case (if
> >>Alex is really dealing with a livelock in the kernel)...?
> >
> >The deadlock resolver is compiled into the GENERIC kernel on 
> >-CURRENT, so I'm assuming it hasn't helped (or perhaps is even part 
> >of the problem).  I think the best thing to do at this point is to 
> >try to get into DDB.  Of the schemes I suggested to work around the 
> >X11 issue, switching to a virtual console before starting Chromium 
> >may work best, since it will continue to use the local X server, etc.
> An alternate way of handling this:
> Turn on the VNC X server and use that from a remote place, leaving the 
> console free.

thanks for all your help. i've recently switched to chromium 6.0.472.63
and so far my computer has been very stable.

if i experience more lock ups i'll let you know and try to figure out a way to
gain access to some more debugging data.

cheers.
alex

> >
> >Robert
> >_______________________________________________
> >freebsd-current@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to 
> >"freebsd-current-unsubscribe@freebsd.org"
> >

-- 
a13x