From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 12:51:12 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 CF8281065673; Sat, 13 Nov 2010 12:51:12 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 33AAA8FC14; Sat, 13 Nov 2010 12:51:11 +0000 (UTC) Received: by wwj40 with SMTP id 40so921915wwj.31 for ; Sat, 13 Nov 2010 04:51:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=JH2rj0CV5prt+tLmAh9FmgTVc961F5O56uWGKl//ZNI=; b=bpf3Umg1nHRab2shMufpXVwaOJC4QQrl+ii1G+YfzuUo/OFdsTihkDFEm99pwkw7bu wsPgz0/ZxVHoI87OV3taPwyULX0llemUGyqJ8cSPgg4nTu2shM+bBfQ8F5NsgnlKp7Wn DPBCTTPv+PlaKHkIA/Jm92RZIxioOdQ2ifYvg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=bIdqxRMz4lVX+X4WpuzoRcA4peq/voTUVZANqLMOfWJvEqP0GfxIQx0iPk3S+JfkbZ OArFR8Acr0gvzfqjYFs3V2cqK3J8u8//mnBYtTtfrJa0Np24YRqoArVoglCQUKHs02wF lKzC0jsEmbInoY9yQJSPk+KoX0+yYaTKCdmhQ= MIME-Version: 1.0 Received: by 10.216.175.18 with SMTP id y18mr3542678wel.30.1289652670829; Sat, 13 Nov 2010 04:51:10 -0800 (PST) Sender: yanegomi@gmail.com Received: by 10.216.198.27 with HTTP; Sat, 13 Nov 2010 04:51:10 -0800 (PST) In-Reply-To: <20101113124758.GA23469@freebsd.org> 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> Date: Sat, 13 Nov 2010 04:51:10 -0800 X-Google-Sender-Auth: kjOT7IJVBEYk2W8cxWemKS1PlLk Message-ID: From: Garrett Cooper To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Kostik Belousov , freebsd-current@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2010 12:51:12 -0000 On Sat, Nov 13, 2010 at 4:47 AM, Alexander Best wrote= : > On Sat Nov 13 10, Kostik Belousov wrote: >> On Sat, Nov 13, 2010 at 12:38:46PM +0000, Alexander Best wrote: >> > On Sat Nov 13 10, Kostik Belousov wrote: >> > > On Sat, Nov 13, 2010 at 11:59:00AM +0000, Alexander Best wrote: >> > > > On Sat Nov 13 10, Kostik Belousov wrote: >> > > > > On Fri, Nov 12, 2010 at 10:37:15PM +0000, Alexander Best wrote: >> > > > > > hi there, >> > > > > > >> > > > > > i'm having an issue with www/chromium. sometimes it will compl= etely lock up my >> > > > > > system without producing a core dump. i'm running HEAD (r21510= 2; amd64). >> > > > > Core dump of the kernel or the process ? >> > > > >> > > > a kernel core dump never gets produced. and this is the first time= a process >> > > > dump made it to disk. >> > > > >> > > > > >> > > > > You probably should follow the usual procedure for the deadlock >> > > > > debugging, see dev handbook. >> > > > >> > > > i have all those options in my kernel conf. still the computer jus= t locks up >> > > > without any chance to enter the debugger. nothing works any longer= . >> > > Do you use serial or firewire console ? Since you run chromium, you >> > > should run X server, and you cannot use syscons for ddb while in X. >> > >> > nope. all i have is a usb mouse and a usb keyboard. ;) >> > >> > > >> > > > >> > > > > >> > > > > > >> > > > > > this time however chrome.core made it to disk somehow: >> > > > > > >> > > > > ... >> > > > > >> > > > > > Loaded symbols for /libexec/ld-elf.so.1 >> > > > > > #0 =A00x00000008026d76a2 in symlook_default (name=3D0x806797db= c "__sys_sigreturn", hash=3D92647454, refobj=3D0x802722c00, defobj_out=3D0x= 7fffffbfe160, ventry=3D0x802717790, flags=3D1) at /usr/src/libexec/rtld-elf= /rtld.c:2675 >> > > > > Please show the output of "info locals" in the frame 0. >> > > > >> > > > (gdb) frame 0 >> > > > #0 =A00x00000008026d76a2 in symlook_default (name=3D0x806797dbc "_= _sys_sigreturn", hash=3D92647454, refobj=3D0x802722c00, defobj_out=3D0x7fff= ffbfe160, ventry=3D0x802717790, flags=3D1) at /usr/src/libexec/rtld-elf/rtl= d.c:2675 >> > > > 2675 =A0 =A0 =A0 =A0 =A0 =A0symp =3D symlook_list(name, hash, &lis= t_main, &obj, ventry, flags, >> > > > (gdb) info locals >> > > > donelist =3D {objs =3D 0x7fffffbfde90, num_alloc =3D 64, num_used = =3D 0} >> > > > def =3D (const Elf_Sym *) 0x0 >> > > Right, this is what I suspected. def is NULL, but the code path sele= cted >> > > seems to be the one which happens when def !=3D NULL. This is either= a >> > > random memory corruption inside the process, or might be some other >> > > usermode issue. It is very unlikely that it has anything with kernel >> > > deadlock. >> > >> > hmmm...but isn't the concept of UNIX that user applications cannot cau= se a >> > system to crash (protected mode)? >> > >> > i tried detaching and attaching my keyboard after chromium crashed my = system >> > and the lights of the keyboard didn't even went on. so in fact everyth= ing >> > crashed and not just X. >> If I said it unclear, let me repeat, the usermode crash dump you got >> probably has nothing common with the kernel issue. > > oh sorry. indeed i misunderstood you there. well i guess this is the prob= lem > most regular users have. we don't own any serial/firewire consoles. all i= can > offer is to add kernel OPTIONS. however none of them seem to be able to p= revent > the lock up and instead letting me enter the debugger or trigger a kernel= core > dump. > > i even have watchdog running, but without any sucess. i guess all i can h= ope > for is that maybe at some point a kernel dump does make it to disk. If userland hasn't completely locked up, you could login remotely, i.e. ssh, and poke at the box (if even for a brief period of time before it goes down). HTH, -Garrett