From owner-freebsd-stable@FreeBSD.ORG Sun Apr 10 08:27:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BFF416A4CE for ; Sun, 10 Apr 2005 08:27:56 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39D6A43D2F for ; Sun, 10 Apr 2005 08:27:56 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from localhost ([127.0.0.1] ident=www) by anduin.net with esmtp (Exim 4.50 (FreeBSD)) id 1DKXnN-00033C-Rn for stable@freebsd.org; Sun, 10 Apr 2005 10:27:55 +0200 Received: from ranger.anduin.net (ranger.anduin.net [81.0.162.52]) by anduin.net (Horde) with HTTP for ; Sun, 10 Apr 2005 10:27:53 +0200 Message-ID: <20050410102753.d63hhe8vpcs8wsgg@anduin.net> Date: Sun, 10 Apr 2005 10:27:53 +0200 From: ltning@anduin.net To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.1) X-Spam-Score: -2.9 X-Spam-Level: -- Subject: Panic when logging out from serial console X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 08:27:56 -0000 Hi all, warning: This report might be somewhat vague. For quite a while now I`ve been plagued with the problem that logging out from a serial console causes the box to panic. For a while I`ve been sure this was isolated to one of my boxen, because it`s been acting up in other ways as well, but today it happened on two other boxes too! And these boxes have been rock stable for the last two years. I`m running a fairly recent variation of RELENG-5 on all the boxes; one of them is amd64, the two others - including the one I`ve pasted from - are plain old p3 machines. They are all dual-CPU though. I have no clue what I can do from here; has anyone seen this before? I can`t always reproduce it, but the risk is fairly high - around 33% I`d say. Anyone? Thanks for your attention, details below. Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 00 fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc0620b5f stack pointer = 0x10:0xdadbd988 frame pointer = 0x10:0xdadbd994 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 51999 (getty) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#0 Uptime: 66d11h24m50s /Eirik ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.