Date: Sat, 13 Nov 2010 22:13:43 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Garrett Cooper <gcooper@FreeBSD.org> Cc: Kostik Belousov <kostikbel@gmail.com>, Alexander Best <arundel@freebsd.org>, freebsd-current@freebsd.org Subject: Re: www/chromium crashing whole system Message-ID: <alpine.BSF.2.00.1011132212400.12353@fledge.watson.org> In-Reply-To: <AANLkTim7ZGLFTj_3WZiC9hAsAaOVrz6yhKcMURV%2BsKvu@mail.gmail.com> References: <20101112223715.GA1356@freebsd.org> <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%2BsKvu@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1011132212400.12353>