From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 22:11:39 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 5A358106566B; Sat, 13 Nov 2010 22:11:39 +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 8E7DA8FC21; Sat, 13 Nov 2010 22:11:38 +0000 (UTC) Received: by wwj40 with SMTP id 40so1245308wwj.31 for ; Sat, 13 Nov 2010 14:11:37 -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=0ltOnmB3srhFtLRBJIgB5lCSIqxOKAQC/RdVziGZJqk=; b=viZngxfW/XmhuLJNtHpTMQFNnGqdNSTyArGk4i8vVqXz1V+63kJ8aioDbRD1Vr25Mq G0NKVvntj9hIXgTXBuhUDxitxe54vVAgXAVrpwZJGh/lW7Ff6+mQxvr0Hv4YHz0f9xzB knPiEV6EDtIIlVHY4KjHgXj2vVt8DhDaiYQDY= 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=i82fqCwk3dF2mWMVUVMTmPRzZo6DDwG6YyGAgEv4SL3+qsthpDaowkifwh9kIj+4tK AWZvdmq7OyJXZkWC82Tmq7C9fd8V/WzFl1A7ftBOwPH7Tj9Zbz6hp/IrCxzw+jxCXTpc 3qOlLctxhHpodnI6wzxBbqHWEqVO8cSe9o3Ms= MIME-Version: 1.0 Received: by 10.216.175.18 with SMTP id y18mr4030283wel.30.1289686296543; Sat, 13 Nov 2010 14:11:36 -0800 (PST) Sender: yanegomi@gmail.com Received: by 10.216.198.27 with HTTP; Sat, 13 Nov 2010 14:11:36 -0800 (PST) In-Reply-To: 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 14:11:36 -0800 X-Google-Sender-Auth: JEuPzbCbORrt9tK6C6l6NFfGLrs Message-ID: From: Garrett Cooper To: Robert Watson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Kostik Belousov , Alexander Best , 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 22:11:39 -0000 On Sat, Nov 13, 2010 at 2:08 PM, Robert Watson wrote: > > On Sat, 13 Nov 2010, Alexander Best wrote: > >>>> 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 >>>> everything 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 >> problem most regular users have. we don't own any serial/firewire consol= es. >> all i can offer is to add kernel OPTIONS. however none of them seem to b= e >> able to prevent 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 >> hope for is that maybe at some point a kernel dump does make it to disk. > > Do you have a second box you can run X11 on, and SSH into the box that wi= ll > run Chromium? =A0If it is really Chromium triggering the crash, this migh= t > allow you to access the console when it crashes. =A0However, if it's Chro= mium > triggering an X11-related crash, it might well not. =A0(Also, it might we= ll > not because of timing differences, but it is worth a try). > > Another thing to consider is starting Chromium when switched to a text > virtual console from X11, which would leave you in text mode for DDB, or = at > least let you see something interesting on the console. > > If regular crashdumps appear unreliable, try setting up a textdump with a= n > automatic reboot, that might provde more reliable (small chance, but it > could). Isn't there also DEADLKRES that might be helpful in this case (if Alex is really dealing with a livelock in the kernel)...? Thanks, -Garrett