From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 19:16:41 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 058291065670; Thu, 18 Nov 2010 19:16:41 +0000 (UTC) Date: Thu, 18 Nov 2010 19:16:41 +0000 From: Alexander Best To: "Robert N. M. Watson" Message-ID: <20101118191640.GA48394@freebsd.org> References: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Thu, 18 Nov 2010 19:16:41 -0000 On Tue Nov 16 10, Robert N. M. Watson wrote: > > 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. > > > > 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... i'm really sorry, but this is a problem ~ 90% of desktop users have: 1) we only have 1 computer 2) we can't access our computer via some other box via ssh or something 3) we don't have serial cables or firewire cables so it seems in this situation a complete deadlock *cannot* be analyzed. the idea of dumping the memory to a usb stick after a hard reboot thus seems so attractive to users like me. still the question is: how can we use such a complete memory dump? i don't think it's as easy as loading it into kdb, is it? cheers. alex > > Robert -- a13x