From owner-freebsd-current@FreeBSD.ORG Fri Jul 18 23:27:06 2008 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 34ABA1065677 for ; Fri, 18 Jul 2008 23:27:06 +0000 (UTC) (envelope-from smallhand@crawblog.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id 219E08FC1C for ; Fri, 18 Jul 2008 23:27:06 +0000 (UTC) (envelope-from smallhand@crawblog.com) Received: by rv-out-0506.google.com with SMTP id b25so617008rvf.43 for ; Fri, 18 Jul 2008 16:27:05 -0700 (PDT) Received: by 10.141.170.9 with SMTP id x9mr396536rvo.90.1216423625880; Fri, 18 Jul 2008 16:27:05 -0700 (PDT) Received: by 10.141.97.9 with HTTP; Fri, 18 Jul 2008 16:27:05 -0700 (PDT) Message-ID: <919383240807181627y6b198e5bx160af1df9229181@mail.gmail.com> Date: Fri, 18 Jul 2008 19:27:05 -0400 From: "Edward Ruggeri" To: "Robert Watson" In-Reply-To: <20080718121102.D69806@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <919383240807172100j35e1c796q513fa34d83f8e8e0@mail.gmail.com> <20080718121102.D69806@fledge.watson.org> Cc: freebsd-current@freebsd.org Subject: Re: 7.0 CURRENT kernel's ath driver causes page fault, kernel panic (debugging kernel) 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: Fri, 18 Jul 2008 23:27:06 -0000 On Fri, Jul 18, 2008 at 7:25 PM, Edward Ruggeri wrote: > On Fri, Jul 18, 2008 at 7:13 AM, Robert Watson wrote: >> This is a NULL pointer dereference in the kernel, which almost certainly >> means a kernel bug. Per e-mail you've already received from Garrett Cooper, >> we need some further debugging information, such as a kernel astack trace. >> If you're unable to get a dump, a DDB stack trace would probably help quite >> a bit (options DDB, when it drops into the debugger, save the results of the >> command "trace"). Please do a file a PR with those results. > > Will do. I'll recompile the kernel tonight with the options Garrett's > recommended, get a trace, and file a PR. Thanks! > >> I'm a bit puzzled that your box is syncing after a panic -- normally the >> kernel is configured not to do that -- could kern.sync_on_panic be set in >> your loader.conf or sysctl.conf? > > Ah, I wondered if it was supposed to do that. There's nothing in > /etc/sysctl.conf, and only nvidia_load="YES" in /boot/loader.conf. I > ran sysctl -a subsequently, and it indicates that kern.sync_on_panic > is (currently) zero. I sent this to Robert Watson only, by mistake. My apologies for sending this twice to you now, Robert. Thank you very much for your help! -- Ned Ruggeri