From owner-freebsd-stable@FreeBSD.ORG Tue Feb 13 18:36:10 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 3407516A402 for ; Tue, 13 Feb 2007 18:36:10 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.19.101.164]) by mx1.freebsd.org (Postfix) with ESMTP id 1A1A813C4D5 for ; Tue, 13 Feb 2007 18:36:10 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from localhost (localhost [127.0.0.1]) by mail.barafranca.com (Postfix) with ESMTP id F0B3DC40DE for ; Tue, 13 Feb 2007 18:56:38 +0000 (UTC) Received: from mail.barafranca.com ([67.19.101.164]) by localhost (mail.barafranca.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30423-01 for ; Tue, 13 Feb 2007 18:56:00 +0000 (UTC) Received: from [192.168.0.1] (a213-22-26-4.cpe.netcabo.pt [213.22.26.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTP id 44ABEC4641 for ; Tue, 13 Feb 2007 18:56:00 +0000 (UTC) Message-ID: <45D204F0.2070001@barafranca.com> Date: Tue, 13 Feb 2007 18:35:28 +0000 From: Hugo Silva User-Agent: Thunderbird 1.5.0.7 (X11/20061007) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at barafranca.com X-Spam-Status: No, score=0 tagged_above=-1 required=4 tests=[none] X-Spam-Score: 0 X-Spam-Level: Subject: 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: Tue, 13 Feb 2007 18:36:10 -0000 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) Best regards, Hugo