From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:50:08 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B2B610656B2; Tue, 16 Nov 2010 07:50:08 +0000 (UTC) (envelope-from rwatson@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DCF788FC29; Tue, 16 Nov 2010 07:50:07 +0000 (UTC) Received: from [192.168.2.105] (host86-161-142-149.range86-161.btcentralplus.com [86.161.142.149]) by cyrus.watson.org (Postfix) with ESMTPSA id AEA5546B58; Tue, 16 Nov 2010 02:50:06 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <20101115221924.GA38676@freebsd.org> Date: Tue, 16 Nov 2010 07:50:05 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: 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> <4CDF0F03.10703@freebsd.org> <20101115221924.GA38676@freebsd.org> To: Alexander Best X-Mailer: Apple Mail (2.1082) Cc: Kostik Belousov , freebsd-current@freebsd.org, Garrett Cooper 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 07:50:08 -0000 On 15 Nov 2010, at 22:19, Alexander Best wrote: > thanks for all your help. i've recently switched to chromium = 6.0.472.63 > and so far my computer has been very stable. >=20 > 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. I'd prefer we try to figure out why your system was crashing now -- the = kernel bug has not gone away just because Chromium is no longer = triggering it. Working around the bug means someone else gets to run = into it later -- perhaps when it's 9.0-RELEASE rather than 9-CURRENT... Robert=