From owner-freebsd-stable@FreeBSD.ORG Sat Feb 24 23:23:56 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F02C416A403 for ; Sat, 24 Feb 2007 23:23:56 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id ACC4213C491 for ; Sat, 24 Feb 2007 23:23:56 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l1ONNr4e088660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 24 Feb 2007 15:23:54 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <45E0C909.4080808@errno.com> Date: Sat, 24 Feb 2007 15:23:53 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.9 (X11/20070208) MIME-Version: 1.0 To: Hugo Silva References: <45D204F0.2070001@barafranca.com> In-Reply-To: <45D204F0.2070001@barafranca.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Panic: 6.2-STABLE/RELEASE, sysctl (on boot) -- ath related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Feb 2007 23:23:57 -0000 Hugo Silva wrote: > Hi, > > > While upgrading a fileserver / home wireless access point to > 6.2-RELEASE, it wouldn't come back after the regular > build/installworld/mergemaster procedures. > > I attached a keyboard and monitor to the server and noticed it was > panicking on boot, current process being sysctl: > > > Feb 13 18:27:51 hyperblast kernel: Fatal trap 12: page fault while in > kernel mode > Feb 13 18:27:51 hyperblast kernel: fault virtual address = 0x0 > Feb 13 18:27:51 hyperblast kernel: fault code = supervisor > read, page not present > Feb 13 18:27:51 hyperblast kernel: instruction pointer = 0x20:0xc06fb2a6 > Feb 13 18:27:51 hyperblast kernel: stack pointer = > 0x28:0xd9734ad8 > Feb 13 18:27:51 hyperblast kernel: frame pointer = > 0x28:0xc3383000 > Feb 13 18:27:51 hyperblast kernel: code segment = base 0x0, > limit 0xfffff, type 0x1b > Feb 13 18:27:51 hyperblast kernel: = DPL 0, pres 1, def32 1, gran 1 > Feb 13 18:27:51 hyperblast kernel: processor eflags = interrupt > enabled, resume, IOPL = 0 > Feb 13 18:27:51 hyperblast kernel: current process = 186 > (sysctl) > Feb 13 18:27:51 hyperblast kernel: trap number = 12 > Feb 13 18:27:51 hyperblast kernel: panic: page fault > Feb 13 18:27:51 hyperblast kernel: Uptime: 3s > Feb 13 18:27:51 hyperblast kernel: Cannot dump. No dump device defined. > Feb 13 18:27:51 hyperblast kernel: Automatic reboot in 15 seconds - > press a key on the console to abort > Feb 13 18:27:51 hyperblast kernel: --> Press a key on the console to > reboot, > Feb 13 18:27:51 hyperblast kernel: --> or switch off the system now. > Feb 13 18:27:51 hyperblast kernel: Rebooting... > > > The last line seen before the panic is sysctl adjusting values > (according to sysctl.conf): > > # tail /etc/sysctl.conf > > dev.ath.0.tpscale=1 > dev.ath.0.diversity=0 > > > Now, there are two interesting things to note: > > a) If I uncomment these lines with the system running and reload > (/etc/rc.d/sysctl reload), there's no panic. > > b) It used to work just fine on 6.0-RELEASE-p5. > > > It is not a big deal, but just something that perhaps should be fixed. > > For the records, I tried -RELEASE and -STABLE. Currently running -STABLE > (as of 2007-02-12 @ about 2AM GMT) Fixed in HEAD; will MFC in a week or so. Thanks for pointing this out. Sam