From owner-freebsd-questions@FreeBSD.ORG Fri Nov 12 13:44:45 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04481106566C for ; Fri, 12 Nov 2010 13:44:45 +0000 (UTC) (envelope-from freebsd@rakhesh.net) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id D0F6C8FC08 for ; Fri, 12 Nov 2010 13:44:44 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 93D246FB for ; Fri, 12 Nov 2010 08:26:39 -0500 (EST) Received: from web2.messagingengine.com ([10.202.2.212]) by compute2.internal (MEProxy); Fri, 12 Nov 2010 08:26:39 -0500 Received: by web2.messagingengine.com (Postfix, from userid 99) id 74FE4B344F6; Fri, 12 Nov 2010 08:26:39 -0500 (EST) Message-Id: <1289568399.7673.1404953861@webmail.messagingengine.com> X-Sasl-Enc: lmCLzU55v/dIl1LCa9mGbN3QHXIIxrUm7a+hzdLpoCGe 1289568399 From: "Rakhesh Sasidharan" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Mailer: MessagingEngine.com Webmail Interface Date: Fri, 12 Nov 2010 17:26:39 +0400 Subject: FreeBSD crashed - trying to find out why X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2010 13:44:45 -0000 Hello, I have a FreeBSD 8.1-RELEASE machine running inside a KVM VPS. I installed tmux a few days back, and today I was trying to update all my ports via portupgrade. Everything was going fine, so after a while I detached from the tmux session and disconnected from the machine (was connected via SSH). When I returned a few hours later, I see that the machine had rebooted. It appears that the machine rebooted due to a kernel fault. From the timestamps I see that the machine rebooted some 10-15 minutes before I returned, so it looks like portupgrade and tmux etc were working fine until then. Here's the messages from /var/log/messages - -8<--- kernel: Fatal trap 12: page fault while in kernel mode kernel: cpuid = 0; apic id = 00 kernel: fault virtual address = 0x250 kernel: fault code = supervisor read data, page not present kernel: instruction pointer = 0x20:0xffffffff8052e574 kernel: stack pointer = 0x28:0xffffff800019c8a0 kernel: frame pointer = 0x28:0xffffff800019c8c0 kernel: code segment = base 0x0, limit 0xfffff, type 0x1b kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 kernel: current process = 50496 (tmux) kernel: trap number = 12 kernel: panic: page fault kernel: cpuid = 0 kernel: Uptime: 3d22h30m42s kernel: Cannot dump. Device not defined or unavailable. kernel: Automatic reboot in 15 seconds - press a key on the console to abort -8<--- I went into all the background about tmux above since the logs highlight tmux as the currently running process. Any idea why kernel crashed, or what I can do to prevent this in future? I understand from the forums that this could be due to bad memory or bad hard disk, but I was wondering whether this could also be due to any incompatibilities with KVM (triggered by tmux perhaps). Thanks, Rakhesh