From owner-freebsd-current@FreeBSD.ORG Sat Jan 28 15:36:15 2012 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 E7D851065672; Sat, 28 Jan 2012 15:36:15 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 51AB08FC14; Sat, 28 Jan 2012 15:36:15 +0000 (UTC) Received: by wibhn14 with SMTP id hn14so3267829wib.13 for ; Sat, 28 Jan 2012 07:36:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=lpYX7EqXwouQbNoNcz61R1/hyDV3vonpIrIwSHPPIaQ=; b=CtR3y7c5L8LhfVEDQg0zvAl4SS/4YX6N4969aqIjDoz968Tjy65GGeImQNObJjsj+V 3IXXZyWmStAJhACNfCfEt7kyrDkDglMpPR2aqoOm7gWDSGegCSmlyOld+O0L3weyJ4z8 PNCjT49JVvQj3gIzLVWIIFcVV5wD3G/aemOok= MIME-Version: 1.0 Received: by 10.180.82.41 with SMTP id f9mr17635110wiy.7.1327763450081; Sat, 28 Jan 2012 07:10:50 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.216.177.73 with HTTP; Sat, 28 Jan 2012 07:10:49 -0800 (PST) In-Reply-To: <201201191123.06109.jhb@freebsd.org> References: <20120118220136.GA1862@glenbarber.us> <201201191050.45477.jhb@freebsd.org> <20120119160257.GD1953@glenbarber.us> <201201191123.06109.jhb@freebsd.org> Date: Sat, 28 Jan 2012 16:10:49 +0100 X-Google-Sender-Auth: hN-902rb3FHjuWwO55G_duNleto Message-ID: From: Attilio Rao To: John Baldwin , freebsd-current@freebsd.org, gjb@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: [panic] intr_event_execute_handlers() - Corrupted DWARF expression 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, 28 Jan 2012 15:36:16 -0000 2012/1/19 John Baldwin : > On Thursday, January 19, 2012 11:02:57 am Glen Barber wrote: >> On Thu, Jan 19, 2012 at 10:50:45AM -0500, John Baldwin wrote: >> > On Wednesday, January 18, 2012 5:01:37 pm Glen Barber wrote: >> > > Hi, >> > > >> > > I'm running -CURRENT from about 5 days ago: >> > > >> > > nucleus# uname -a >> > > FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #3 r230037M: Fri J= an >> > > 13 17:48:14 EST 2012 =C2=A0 =C2=A0 gjb@nucleus:/usr/obj/usr/src/sys/= NUCLEUS =C2=A0amd64 >> > > >> > > (The 'M' is kib's DRM patches for Intel GPU.) >> > > >> > > So far, I haven't had much problem with this laptop, but just had th= e >> > > machine panic. >> > > >> > > I have kgdb output attached, and I'll be happy to provide whatever >> > > additional information that may be needed. >> > > >> > > I have core.txt.N available here: >> > > >> > > =C2=A0 http://people.freebsd.org/~gjb/core.txt >> > >> > In kgdb, can you go to frame 6 and 'p td->td_lock'. =C2=A0If that is n= on-null, can >> > you do 'p *td->td_lock'? >> > >> >> Sure, script(1) output is attached. > > Hmm, I don't think td->td_lock is ever supposed to be NULL. No, never, it is initialized in sched_fork_thread() and can point to containers lock or blocked_lock. I think the memory page of the pointer could have been zeroed or it is an hw bug. Attilio --=20 Peace can only be achieved by understanding - A. Einstein